My k64F board just has a bootloader on it now, I cant find a mbed file to put it back into normal mode so I can get a com port in my windows device manager. and whenever I search it keeps redirecting me to the same page(https://developer.mbed.org/handbook/Firmware-FRDM-K64F) which asks for an anomalous "interface firmware file" whatever that is, no link provided. The bootloader on F: disappears after about 5 seconds and I keep having to replug the board in while holding the button down. This is very confusing and the instructions on https://developer.mbed.org/handbook/Firmware-FRDM-K64F don't clarify how to get the proper files installed.
Solved! Go to Solution.
Hi Stephen brsay,
If you still need to use the MBED, please download my attached file to your board in the win7 system, and follow these steps:
TAKE frdm-k64 as an example.
1. Power off the board, press the reset button on the board, and hold on it, then plug your board to your PC, you will find you board is a device named as "BOOTLOADER".
release the reset button.
2. Send attached file"k20dx128_k64f_if_mbed.bin" to your "BOOTLOADER", and wait it is finished.
3. power off and power on the board again, you will find your board is a device named as "MBED".
Have a great day,
Kerry
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi Stephen brsay,
If you still need to use the MBED, please download my attached file to your board in the win7 system, and follow these steps:
TAKE frdm-k64 as an example.
1. Power off the board, press the reset button on the board, and hold on it, then plug your board to your PC, you will find you board is a device named as "BOOTLOADER".
release the reset button.
2. Send attached file"k20dx128_k64f_if_mbed.bin" to your "BOOTLOADER", and wait it is finished.
3. power off and power on the board again, you will find your board is a device named as "MBED".
Have a great day,
Kerry
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Kerry, that mostly worked! Not sure where this .bin file came from as I tried several that didn't work but thank you! anyway I still have a "fail note" on my F: drive and i can't upload mbed programs but this is at least the initial state I got the board in from the AT&T kit so its a good start. It also is showing up now in my device manager on a COM port so that's good
thanks
Hi Stephen Brsay,
That's good to hear it works on your side.
This .bin is the old mbed bootloader firmware which I keep it before.
Actually, I prefer to use the JLINK firmware, if you can, you also can use the JLINK firmware which can be download from :
SEGGER - The Embedded Experts - Downloads
If your problem is solved, please help to mark the correct answer to close this question, thank you!
Wish it helps you!
Have a great day,
Kerry
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi
I would try some files from here: OpenSDA Serial and Debug Adapter|NXP
The mbed version is not recommended since it doesn't allow debugging and doesn't work with Windows 10. Presently the Segger J-Link one is performing best.
Regards
Mark
Hi Mark,
I already tried it, no luck wotht he openSDA. The P&E one actually connected but wouldn't open a path.