Got this board and am a novice (developer but not microcontrollers much) I went down the rabbit hole of windows and it stuck fast flashing got the boot loader to stop that on win 10.
But now I get it in bootloader mode, copy an elf file for the bubble demo, unplug, plug, and doesn't work. The file is gone but I have no idea if the file flashed, errored out or what.
So it may well be I built it wrong, does anyone have the binary for the bubble demo? I should just be able to copy it to the mounted drive, cycle power and it should work right?
I know the board is good because the demo was on it when I first powered it up and it worked. The board just stopped once I plugged into the other port.
已解决! 转到解答。
It seems that FRDM boards still get shipped with an outdated OpenSDA bootloader which does not work under Windows 10.
Copy demo a file to the 'bootloader mode' does not work, as it only accepts a debug (or bootloader) file.
What you need is to update the P&E OpenSDA bootloader on it to a newer version, capable to work with Windows 10. The ideal solution for this is to use a Windows 7 (not VM) machine, see or to deal with the registry, see https://mcuoneclipse.com/2018/04/10/recovering-opensda-boards-with-windows-10/
Then you can update the debug firmware too:
I hope this helps,
Erich
It seems that FRDM boards still get shipped with an outdated OpenSDA bootloader which does not work under Windows 10.
Copy demo a file to the 'bootloader mode' does not work, as it only accepts a debug (or bootloader) file.
What you need is to update the P&E OpenSDA bootloader on it to a newer version, capable to work with Windows 10. The ideal solution for this is to use a Windows 7 (not VM) machine, see or to deal with the registry, see https://mcuoneclipse.com/2018/04/10/recovering-opensda-boards-with-windows-10/
Then you can update the debug firmware too:
I hope this helps,
Erich