Board:
- FRDM-KW24D512
Problem:
- Out of my four above types of boards, three became unresponsive due to bricking in Windows 10 or while trying to unbrick the bricked ones.or
Condition:
- When Powering through the OpenLink USB No LED Glows or blinks
- No drive appears in the Windows (while keeping the reset button pressed or otherwise)
- When powering through the KW24 USB Two RED LED's Glow
What did I Try:
- Followed the steps mentioned in DAPLink bootloader update | Mbed regarding the problem and possible solutions using External Debug Probe (ULINK Pro).
- Downloaded the DPLink Source from DAPLink/DEVELOPERS-GUIDE.md at master · ARMmbed/DAPLink · GitHub and compiled the solution as per the given instructions correctly for the k20dx_frdmkw24d_if as the board used OpenSDA MCY named K20DX128Vxx5.
- I used the following settings for the Options for the Target:
- The uVision solution compiled correctly without any error, see the Build Window below:
- I Flashed the Program, It again worked without any error. See the Build Window Below.
However, the Board did not come out of the Bricking State. THE SAME Problem Persists.
SAME Boards, SAME CONDITION, SAME PROBLEM. Another Try using another method
What did I Try as the second method:
A. Copied the Bootloader from the Working Board using ULINK Pro into a Hex File.
- Created a uVision Project with the K20DX128Vxx5.
- The following screens show the settings:
Used Save Command as follows to Read the Bootloader into a Hex FIle
SAVE MyFile.hex 0X0, 0X0001FFFF
The hex file was created successfully in the project folder.
B. Flashed the Bricked boards with the copied Hex File.
- Generate a uVision project
- Select ULINKpro as debug interface
- Entered the hex file name into 'Name of Executable' in the dialog 'Options for Target - Output'
- Performed a Flash download.
It showed that the programme has been flashed successfully, but
Same Problem Flashing Successful but the Boards not Working
WHAT NEXT?
