Vlad Blanshey

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

5 years, 10 months ago.

FRDM-K64F : DAPLink does not upgrade from MAINTENANCE bootloader

OpenSDA debug link got corrupted on my FRDM-K64F . I found the supposed solution here: https://os.mbed.com/blog/entry/DAPLink-bootloader-update/  and followed to the letter. I got a MAINTENANCE bootloader onto the board and after that nothing can change it. Step #5 on that upgrade list suppose to upload a new firmware from mbed here https://armmbed.github.io/DAPLink/ upload succeeds but the debug port is still in MAINTENANCE mode which means it is recognized as a storage device but is not recognized by MCUXpresso IDE as a debug probe . Tried to upload to the latest OpenSDA binary from NXP - the same result - the board stuck in MAINTENANCE and no debug probe recognized.

Please help

1 Answer

Karen Yen
5 years, 10 months ago.

Hello Vlad,

We have recently released the latest version of DAPLink firmware which you may have just missed. I had trouble myself with the previous firmware version, causing the K64F to not showing up as a DAPLink drive while I was using Windows 10.

Follow step 1 from https://os.mbed.com/blog/entry/DAPLink-bootloader-update/ and redownload the DAPLink bootloader image for the K64F. Delete all files within your MAINTENANCE drive then drag and drop the .bin file into the drive. Wait for the drive to dismount and remount again as MAINTENANCE (if the drive does not automatically dismount, eject the drive, unplug the board, then plug back in).

Next, search for the K64F interface firmware from https://armmbed.github.io/DAPLink/, download, and drag and drop the .bin file into the MAINTENANCE drive. The drive should dismount and ultimately connect as DAPLink.

These steps worked for me and hopefully they will work for you as well.

-Karen, team Mbed

EDIT::

I have just built the latest DAPLink interface firmware using uVision which hopefully will work. Just drag and drop the file into your MAINTENANCE drive.

Firmware: /media/uploads/karencyen/k20dx_frdmk64f_if.bin

Please let me know if it works for you!

I did just that according to the https://os.mbed.com/blog/entry/DAPLink-bootloader-update/ and the place where I downloaded "the latest" firmware for K64F is the same you suggested. I repeated the same steps now again and the result is the same - MAITENANCE. Didn't work

posted by Vlad Blanshey 14 Jun 2018

Added: I tried the same on two Windows laptops WIndows 7 and Windows 10 - the same result. (I did press reset while connecting to USB)

posted by Vlad Blanshey 14 Jun 2018

Hello Vlad,

I added an edit to my original answer with a recently built firmware (unfortunately I cannot add attachments to comments). Please take a look and let me know if it works!

-Karen, team Mbed

posted by Karen Yen 15 Jun 2018

Karen, thank you for your attention. I tried again downloading firmware from your new link - the same result. It is still listed as MAINTENANCE drive. Windows Device manager shows it as "mbed Composite device" and the details.txt file has this :

  1. DAPLink Firmware - see https://mbed.com/daplink Unique ID: 0000000040214e4500241019c89200549e11000097969900 HIC ID: 97969900 Daplink Mode: Bootloader Bootloader Version: 0244 Git SHA: 39c605031b1e82c34976bc5eeb892bf29f010d6c Local Mods: 0 Bootloader CRC: 0x5f9747b1

Does this match what you get on FRDM-K64F ?

posted by Vlad Blanshey 16 Jun 2018

Can I find and download older version of OpenSDA v2.1 instead of the latest v2.2 ? There are reports that it worked... are there archives somewhere?

posted by Vlad Blanshey 16 Jun 2018

Hello Vlad,

This is what my details.txt file shows:

  • Unique ID: 0000000032044e450018700a997b00226781000097969900
  • HIC ID: 97969900
  • Auto Reset: 0
  • Automation allowed: 1
  • Overflow detection: 0
  • Daplink Mode: Bootloader
  • Bootloader Version: 0246
  • Interface Version: 0246
  • Git SHA: ceccaf98d35951e66e263fbfe1bed91b40745ac7
  • Local Mods: 1
  • USB Interfaces: MSD
  • Bootloader CRC: 0x435eb8b9
  • Interface CRC: 0x3ec402da
  • Remount count: 0

I am not sure if there are any OpenSDA v2.1 archives available, if I find them I will let you know. In the meantime, I will see if there is another way around this problem.

-Karen, team Mbed

posted by Karen Yen 18 Jun 2018

Hello Vlad,

Could you also test the board connection using a different usb connector and a different usb port on your computer? Sometimes those can causes connection problems. You can also try updating DAPLink once again using the different ports/connectors as well as the interface firmware I attached. Thank you!

-Karen, team Mbed

posted by Karen Yen 18 Jun 2018