bootloader for the FRDM-K64F

yibinwang · ‎07-12-2015

Dear all,

How are you? Recently, I got my first FRDM-K64 Evaluation board. With some trying, I can successfully build a project of I wanted using PE, such as GPIO control, UART communication, etc.

And I also can debug my code through the GDB OpenOCD Debugging. But, I found a strange thing for the Evaluation board. I can successfully download my code through the debugging. And power up again, the board always can work well. If I put my binary file to copy the “MBED” disk for the code update, it seems the board is not able to work and the reset LED is always lighted when the power up again.

With some testing and looking for the google, I got the latest bootloader file “0221_k20dx128_k64f_0x5000.bin” and updated the bootloader with it. With the latest version bootloader updated, I can update my code regardless of the debugging or the “MBED” disk copying both can make my board works well.

My old bootloader file is k20dx128_k64f_if_mbed.bin. I want to know what the different between these two bootloader files (0221_k20dx128_k64f_0x5000.bin vs. k20dx128_k64f_if_mbed.bin)

Or I am missing something on my software? Because, when I copy the demo code to the board with these two bootloader files respectively, the board always can work well.

Please let me know your comments on my concern.

Thanks in advance!

Jerry Wang | 王宜斌 | Software Engineer | Branson Ultrasonics

T +86 (29) 8928 0532 | M 13891803152

Jerryw.Wang@emerson.com<mailto:Jerryw.Wang@emerson.com>

Kan_Li · ‎07-12-2015

Hi Jerry,

I think the old bootloader on your hand might be rev 0201 or 0202, and the difference between them and latest version can be referred via the following snapshot,

Please refer to Firmware FRDM K64F - Handbook | mbed for more details.

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

yibinwang · ‎07-12-2015

Hi Kan,

Thanks for your response soon.

I also want to know if I am missing something on my code, because the demo software of freescale provided can work well with these different two version bootloaders.

What was reason caused that my code only can be compatible with the latest version bootloader?

Thanks again.

Jerry

Jerry Wang | 王宜斌 | Software Engineer | Branson Ultrasonics

T +86 (29) 8928 0532 | M 13891803152

Jerryw.Wang@emerson.com<mailto:Jerryw.Wang@emerson.com>

Kan_Li · ‎07-13-2015

Hi Jerry,

Would you please send your project for a review? BTW, would you also specify the demo that can work well with both boot loaders? is the outboxdemo? or one of the Kinetis SDK 1.0.0 GA demos? Please kindly help to clarify:-) Thanks for your patience!

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

mjbcswitzerland · ‎07-13-2015

Jerry

If the loading fails, check the error file that records the reason.

In older versions, any flash configuration values that are not 0x00 (apart from the security byte) cause the loader to reject the file - this may be an explanation why your code doesn't work with all loader versions.

Regards

Mark

Kinetis: µTasker Kinetis support

K64: µTasker Kinetis FRDM-K64F support / µTasker Kinetis TWR-K64F120M support / µTasker Kinetis TWR-K65F180M support

For the complete "out-of-the-box" Kinetis experience and faster time to market