AnsweredAssumed Answered

KDS binary does not work but IAR release binary works

Question asked by Tilak Lakshmana on May 11, 2016
Latest reply on May 19, 2016 by Tilak Lakshmana

Dear Community/NXP,

 

On FRDM-K64F, I am using the release binary: NXP_Kinetis_Bootloader_2_0_0\targets\MK64F12\iar\binaries\freedom_bootloader.bin

With this release binary, I can flash NXP_Kinetis_Bootloader_2_0_0\apps\led_demo\MK64F12\iar\binaries\led_demo_freedom_a000.bin using NXP_Kinetis_Bootloader_2_0_0\bin\Tools\KinetisFlashTool\win\KinetisFlashTool.exe

via USB-HID: 0x15A2, 0x0073 at Target Address: 0x0000A0000.

However, when I compile the freedom_bootloader.bin using KDS v 3.2 based on this project: NXP_Kinetis_Bootloader_2_0_0\targets\MK64F12\kds\freedom_bootloader

Then, the binary obtained does not allow flashing via the USB-HID interface even though the KinetisFlashTool.exe can connect via USB-HID, but writing led_demo_freedom_a000.bin fails with error: kStatusMemoryRangeInvalid.

 

I hope I am asking this question in the correct community. This seems like a bug in the release version when compiling using KDS. Any hint on how to successfully write after compiling using KDS for bootloader would be great.

 

Thanks,

Tilak

Outcomes