New FRDM-K22F are bad

[madisonchou]

Prior to a couple of weeks ago, we have quite a few FRDM-K22F.   We recently got 4 FRDM-K22F.  It came in NXP boxes.   When plugs in, it shows up only as "BOOTLOADER" drive, not an "MBED" drive.  These files are on the drive and dated 12/14/2012:

.fseventsd (this is a folder)

.metadata_never_index

.Trashes

mbed.htm

I have enough experience that I was able to load MBED firmware (0221_k20dx128_k22f_0x8000.bin) onto the tiny OpenSDA K20 via J10 (its JTAG).   MBED is now showing up when plugs in.  But MCUXpresso has problem to download my application to start debugging session:

GNU gdb (GNU Tools for ARM Embedded Processors) 7.12.0.20161204-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".

with warning box saying:

02: Failed on connect
Wire ACK Fault in DAP access

Probe(0): Connected&Reset. Was: NotConnected. DpID: 00000000. CpuID: 00000000. Info: <None>

Are these really old boards??  Is there a way to get this problem fixed??   Otherwise, we need to return these boards and get replacement.

Note: on the two microUSB connectors, there is stamp of "6H1".

[madisonchou]

I'm on Win10, which doesn't like 0203.   I am good now.   But I have to jump through many hoops in order for MCUXpresso to like 0221.   Here is what I have to do:

1. Load DEBUG_OpenSDA_for_MBED_Bootloader_by_Pemicro_v108.bin into BOOTLOADER drive.

2. Debug code in KDS.   Debug config is GDB PEMicro Interface.  When launch, msg box saying something like: "Device secured.  Will erase".   Proceed and code developed in KDS will run.   Stop it.

3. Get back to BOOTLOADER drive (press RESET button while powering it up by plugging in USB.)

4. Load 0221_k20dx128_k22f_0x8000.bin.   Then code developed in MCUXpresso will load and be able to proceed with debugging.

Note: Step 4 may not work in times.  Somehow my speedy laptop will pop up msg saying file 0221_k20dx128_k22f_0x8000.bin no longer exist before it is written into the BOOTLOADER drive.   In which case, the board is bricked again.   Go thru the 4 steps again.

[Alice_Yang]

Hi Jei,

Thanks for your sharing.

Have a nice day,

Alice

[Alice_Yang]

Hi Jei,

- Please refer to the below steps update board firmware on bootloader :

1)Press the Reset button (and keep it pressed) while power the board with the OpenSDA USB connector(J5):.
2)  The board will show up as BOOTLOADER drive on your system:
3) Copy" 0203_k20dx128_k22f_0x8000.bin "(I attached it for you) to the BOOTLOADER driver:
4) The copy operation takes about 2-3 seconds, after finished , unpower  the board.
5) Power the board again normally with USB to OpenSDA.

- Import a SDK demo, then refer to my video to debug.

Hope it helps

Have a great day,
TIC

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------