i'm now on my second FRDM-K64F board; and i don't want to destroy the K2x processor along the way....
the getting started guide (https://www.nxp.com/document/guide/get-started-with-the-frdm-k64f:NGS-FRDM-K64F) has a pop-up warning about windows 10 issues with older versions of the OpenSDA firmware.... here are the critical steps which still didn't work on my FRDM-K64F board:
my board enumerated as BOOTLOADER (which indicates an older firmware version), so i followed step #7 above.... after copying this .bin file, the led next to the USB connector started blinking faster (2-3 Hz); previously, it was blinking at 1 Hz which is typical of "bootloader mode".... more important, the board did NOT automatically re-enumerate as MAINTENANCE.... re-inserting the board with the reset button pressed caused to board to (again!!!) enumerate as BOOTLOADER....
before i try loading the K2x directly through Jlink, perhaps someone could suggest an alternative here.... i do recall getting my first (now broken) FRDM-K64F board to actually enumerate correctly -- though MCUxpresso complained when it tried to load an image....
suggestions on how to proceed???
Hi biosbob,
the led next to the USB connector started blinking faster (2-3 Hz);
Check if it's Bootloader error state.
Please follow the DAPLink bootloader update.
If still enumerate as BOOTLOADER, try to program a simple demo into K64 using external debugger connect to J9. The reset signal from K64 may push the OpenSDA enter bootloader mode.
Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
Hi biosbob,
the led next to the USB connector started blinking faster (2-3 Hz);
Check if it's Bootloader error state.
Please follow the DAPLink bootloader update.
If still enumerate as BOOTLOADER, try to program a simple demo into K64 using external debugger connect to J9. The reset signal from K64 may push the OpenSDA enter bootloader mode.
Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
