Having trouble with drag & drop programming of FRDM-K22 board

[dsumigar]

We have a collection of K22 FRDM boards. They enumerate the following USB drive names: MBED, DAPLINK, BOOTLOADER. The drop & drag feature only appears to function correctly with the DAPLINK boards. Below are our efforts to find a cause for drop & drag not working for the other boards. We are running on Windows 10.

Currently, we have a working setup of a FRDM-K22 board with our K22 program that mounts as DAPLINK drive with the latest DAPLink Bootloader Firmware 0244 (shown below). However, after performing drop & drag on our other DAPLINK K22 board, we are unable to upload our own program onto the board and read the device COM port when the USB cable is connected to the K22 port.

# DAPLink Firmware - see https://mbed.com/daplink

Unique ID: 0231000050234e45001c0005eaee002308e1000097969900

HIC ID: 97969900

Auto Reset: 0

Automation allowed: 0

Overflow detection: 0

Daplink Mode: Interface

Interface Version: 0253

Bootloader Version: 0244

Git SHA: 64359f5c786363065a41ec15c348e3d53568da03

Local Mods: 0

USB Interfaces: MSD, CDC, HID, WebUSB

Bootloader CRC: 0xbd0abee1

Interface CRC: 0x9027c7dd

Remount count: 0

URL: https://mbed.org/device/?code=@U?version=@V?target_id=@T

On the mbed DAPLink bootloader update forum DAPLink bootloader update | Mbed, there is mentioning of issues with Windows 10 corrupting/bricking several FRDM boards including the K22. They suggest updating the bootloader with their latest DAPLink firmware and dropping the file into the device mounted as MAINTENANCE. Once the file copy is complete, the board should unmount and remount as DAPLINK, indicating the process is complete.

We tried the following:

We reprogrammed the bootloader firmware with OpenSDA V2.2 using JFlash, specifying the start address as 0x0. The K22 board now mounts as DAPLINKBOOT, which is expected from mbed’s documentation. The reported bootloader version is shown below. After copying our program into the DAPLINK drive, we disconnect the USB cable from the SDA port and connect into the K22 port. Here, we are unable to read the COM port associated with our program from device manager.

# DAPLink Firmware - see https://mbed.com/daplink

Unique ID: 0000000050234e45004d0005eaee003408e1000097969900

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: 0xdab2d36e

Another K22 board we have mounts as an MBED drive. We tried drop & drag  with our program into the MBED drive and saw the following message:

SWD ERROR

Any assistance in understanding our problem is greatly appreciated.

[Pavel_Hernandez]

Hello, my name is Pavel, and I will be supporting your case, I reviewed your information page you can find the firmware for your devices.

OpenSDA Serial and Debug Adapter | NXP Semiconductors

Freedom OpenSDA Firmware Issues Reported on Window... - NXP Community

Best regards,
Pavel

[dsumigar]

Thank you Pavel for the information.

I still have some questions on how to program the K22.

We downloaded the binary file: k20dx128_bootloader_v22_0x8000.bin. Programmed the K20 with the SEGGER JLink at address 0.

Holding down the Reset button and plugging in the USB cable brings up the FRDM board with a DAPLINKBOOT drive. The DETAILS.txt file is the following:

# DAPLink Firmware - see https://mbed.com/daplink

Unique ID: 0000000050234e45004d0005eaee003408e1000097969900

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: 0xdab2d36e

The Daplink mode appears to be in Bootloader. Documentation says the name of the drive should be BOOTLOADER. It says DAPLINKBOOT. Is DAPLINKBOOT the same as BOOTLOADER?

Just plugging in the USB cable brings up the FRDM board with a DAPLINKBOOT drive with the same DETAILS.txt file. There doesn’t seem to be a change in mode.

We are not interested in creating a debugger on the K20, we are interested in using drop and drag to program the K22. Is there another application or other steps we have to take to enable this feature as it seems not to be working for us?

[Pavel_Hernandez]

Hello, I apologize, for researching more information, but this method is not involved with the firmware of the debugger on the board. Let me get more details about your case the board that has that function, are you connecting the board to the USB without the name OpenSDA? This app note could give you more information about the Bootloader that you are searching.

USB Mass Storage Device (MSD) Bootloader (nxp.com)

Best regards,
Pavel