AnsweredAssumed Answered

FRDM-K22F Bootloader not working on Win10

Question asked by Augusto Panecatl on May 9, 2019
Latest reply on May 13, 2019 by Augusto Panecatl

I just acquired a couple of FRDM-K22F dev boards, as soon as I connected them both, the freaking bootloader got corrupted (I'm working on a Win10 PC), I started researching some and then more regarding the issue, I already checked Erich Styger posts and eclipse site regarding the problem. I downloaded his K20_dx128 Bootloader s19 file from the Github site and programmed the freedom boards using a Multilink Universal debugger in a dummy Kinetis IDE project using the corresping launch config. (so far so good) once I unplug-plug the board it enumerates as bootloader (without having pressed de RST before plugging it) and shows the appropiate 2 files:

 

Bootloader

 

Details.txt

# DAPLink Firmware - see https://mbed.com/daplink
Unique ID: 0000000050234e45002d0006eaee000608e1000097969900
HIC ID: 97969900
Auto Reset: 0
Automation allowed: 1
Daplink Mode: Bootloader
Bootloader Version: 0241
Git SHA: be5afd34db2efe1e08d72fa23b3a68ab2625d9a3
Local Mods: 1
USB Interfaces: MSD
Bootloader CRC: 0x439c8da1
Interface CRC: 0xb5ee299c

 

As far as I can tell it looks good, after that I plug it holding the RST button to enter make sure I'm entering bootloader so I can add the OpenSDA debug tool I dragged the bin: "DEBUG_OpenSDA_for_MBED_Bootloader_by_Pemicro_v2.1.bin" I got from the P&E Micro website, the file transfer seems succesful (green led blinking), once the file transfer is completed the board disconnects, the browser window closes and the red led the middle of the board turns on. If I plug it and unplug it the board fails to enumerate. If I plug it while pressing RST, it enumerates in bootloader mode (previous image).

 

I also tried using some other files like "DEBUG-FRDM-K22F_Pemicro_v108b_for_OpenSDA_v2.1.bin" and "MSD-DEBUG-FRDM-K22F_Pemicro_v114.SDA", when I use that file, after the file transfer the board disconnects-connect again it enumerates as bootloader, this time including a third file:

 

Fail.txt

There was am error during file transfer

or

Tranfer timeout

 

(Sorry I dont have a screenshot for this)

 

Since the original problem was the fact that the bootloader was being overwritten by Win10 during the enumeration I disabled the option by which WIn creates a System Volume Information folder in external drives by executing:

gpedit.msc (Local Group Policy Editor)

Computer Configuration -> Administrative Templates -> Windows Components -> Search

Do not allow locations on removable drives to be added to libraries (click on enable)

Apply >> OK

 

services.msc (windows startup services)

Windows search (double click)

Startup type (Disabled)

 

This of course affects the way some drives enumerate, but so far I have had no problems with any device, however I still have the same issue, has anyone been able to solve it succesfully? I keep reading discouraging posts regarding this...

Outcomes