ways to flash k64

[roymessinger]

I'm designing my own board based on the FRDM-k64F. In the debug phase I will use the SEGGER Base debugger.

After the board will be operational and mass produced, is there a way to flash the ARM without the SEGGER (since it will be placed in a hard to reach area)?

For example, I'm communicating my board via UART (from external host 10 meters away, using USB to RS485, and in my board, using RS485 to UART). Can I flash through this already-exist connection?

I prefer not placing the MK20 for OpenSDA as I do not know the complexity of designing the OpenSDA inside the MK20 (or is it copy-paste of exist code?)

Thank you.

[kerryzhou]

  Hi Roy Messinger,

      Because the K64 don't have the ROM bootloader, then if you want to use the uart bootloader, you just can use the flash uart bootloader.

     But this flash uart bootloader also a section code which you need to program in the K64 before, this still need to use the debugger or the programmer to download the bootloader code.

     In conclusion, even in mass produced, you still need to use the debugger or programmer to download the application code directly, or the uart bootloader code,then use the uart to download the application code.

Wish it helps you!

Have a great day,
Kerry

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[mjbcswitzerland]

Roy

See http://www.utasker.com/docs/uTasker/uTaskerSerialLoader.PDF which can be used on the K64 for field loading (UART, USB, Kboot, Ethernet, SD card, memory stick).

In the factory you can either use SWD/JTAG via a connector or bed of nails for initial programming, or via EzPort. When using EzPort a practical method is EzPort cloning whereby you program your first board (or even a development board) and then let it clone other boards as described here: http://www.utasker.com/docs/uTasker/uTaskerEzPortCloner.pdf

Although I don't find it that interesting for practical use in products, the K64 also supports flash swap, as discussed here: https://community.nxp.com/message/586326#586326 which can also be used as a base for field updates.

For remote, fail-safe field updates (with authentication and encryption protection) the "bare-minimum" loader is also a popular choice: http://www.utasker.com/docs/uTasker/uTasker_BM_Loader.pdf

All of these methods are available integrated in the uTasker project for K64 - see http://www.utasker.com/kinetis/FRDM-K64F.html so solves almost all product development, field maintenance and production requirements out-of-the-box.

Regards

Mark