topic Re: Problems starting from internal Flash in CodeWarrior for MCU

Problems starting from internal Flash

tb89 — Fri, 14 Jun 2013 11:27:28 GMT

Hi everybody,

I'm using MPC5604B on XPC56XX EVB Motherboard and XPC560B 100LQFP Minimodule.
I used RAppID Init for MPC560xB Version 1.3.0.6 to generate source Code and added it to CodeWarrior IDE (Version 5.9.0).

Also I use P&E micro USB Multilink Interface and ICDPPCNEXUS Debugger (Version 1.34.00.01) for CodeWarrior.

My program is using DSPI_2 to communicate with an EA DOGS102W-6 Display and also shows a simple "Hello World" on it.

I'm already able to load my program with the "Debug"-Button on RAM and internal Flash and start it with a 'go' command at the Debugger.

I changed the display for my "RAM-program" to differ it from the program on Flash.

So, I'm able to load on RAM and start that display ('go'), change program Counter to the address of Flash and also start that different display with 'go'.

Now I wanted to start the program without Debbuger, by just shutdown the board, unpluck the Debugger and start again.

But nothing is working and the Reset LED glows from shutdown til first reset command of Debugger.

RAppID generated an romcopy.c file for Flash program, which I think should load from ROM to RAM.

Does anybody know what I need to execute my program at startup?

Do I have to turn off an option of the Debugger to just don't need the 'go' command or anything like that?

I appreciate any kind of help.

Regards,

Re: Problems starting from internal Flash

stanish — Thu, 27 Jun 2013 15:40:13 GMT

Hello Tim,

Seems to me like a startup issue. How does your startup sequence looks like? can you post e.g. Internal flash project map file generated by the linker?

Debugger script which is executed before debugger starts includes some actions which are probably not present in your startup code.

E.g.

Did you disable Watchdog timer in your startup? Watchdog is enabled after power on reset by default so if you are not servicing watchdog timer in your code the reset may occurs.

Is the internal SRAM initialized in your startup prior to call romcopy routines? If not then the ECC exception may occur.

Regards

Stan

Re: Problems starting from internal Flash

PatrickMenter — Thu, 27 Jun 2013 16:22:02 GMT

Tim,

Did you submit the issue to RAppID Support (rappid@freescale.com)? They should be able to help you in short order.

Patrick

Re: Problems starting from internal Flash

tb89 — Thu, 18 Jul 2013 11:41:15 GMT

Ok, I had to disable Watchdog. But also I now use the generatet functions from RAppID but with given Code from CodeWarrior. Now it 's working.