topic Re: [TWR-K60F120M] Going from Debug to Release / Writing to Flash in MQX Software Solutions

[TWR-K60F120M] Going from Debug to Release / Writing to Flash

michael_wahler — Mon, 14 Jul 2014 13:35:59 GMT

Hi,

I have successfully followed the instructions for writing an application and executing it through the OSJTAG interface (CW 10.6, MQX 4.1).

Now I would like to write the application to flash memory such that it automatically starts when I power on the device. Is there any documentation on how to do this? I could not find anything...

Second question: Do I need to rebuild BSP etc. in release mode in order to program the flash memory?

Kind regards

Michael

Re: [TWR-K60F120M] Going from Debug to Release / Writing to Flash

soledad — Tue, 22 Jul 2014 15:31:21 GMT

Hi Michael,

CodeWarrior development environment enables you to have multiple build configurations, called build targets. All projects in the Freescale MQX RTOS contain at least two build targets:

• Debug target - Compiler optimizations are set low to enable easy debugging.

• Release target - Compiler optimizations are set to maximum, to achieve the smallest code size and fast execution. The resulting code is very hard to debug.

For example:

For the TWR-K70, you can download your project into a DDR or SRAM, if you download a project to DDR you can run it after recycle the power no matter if it was build for debug or release.

I hope this clarifies!!!

Have a great day,
Sol

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

Re: [TWR-K60F120M] Going from Debug to Release / Writing to Flash

michael_wahler — Thu, 24 Jul 2014 07:04:43 GMT

I solved my problem. Actually, debugging the program copies it to the flash memory of the device such that it runs automatically when the device is powered on.

What prevents running the program outside of debug mode is when the BSP expects a debug connection to a PC (as in my case). Jorge from Freescale supported pointed me to this page: https://community.freescale.com/message/391746#391746

However, this did not solve the problem for me, but it pointed me into the right direction. Solution: Replace the line

#define BSP_DEFAULT_IO_CHANNEL "iodebug:"

in user_config.h with

#define BSP_DEFAULT_IO_CHANNEL "ittyf:"