INTERNAL_FLASH config does not work on MCF5233DEMO in CodeWarrior !!! ???

[osanz]

Hi to all;

I'm trying to use INTERNAL_FLASH on CodeWarrior for MCF52233DEMO board, but it does not work.

The same source is working without problems on the RAM config.

I suspect there is something wrong on the linker configuration file but i have not found nothing related on internet, neither this forum, etc..

Does any one have the solution to this problem??

As a guide, the problem can be easilly reproduced from the "hello World" project stationary of Codewarrior.

Do a New project, and run it on RAM -> no problem will appear, change to INTERNAL_FLASH and the problem will appear:  "Exception vector name: Address Error".

Thank you in advance.

BR.

Oscar Sanz.

[lambtron]

Ensure that the programm is being correctly programmed to FLASH. This step is not automated ...

Why is this not automated? It is a process that may be repeated hundreds or thousands of times during development. Please consider adding this feature, thus eliminating a most serious bottleneck in the development process.

[osanz]

Yes, it will be a great IMPROVEMENT!!!!, in spite of the debugger in flash is EXCELENT also, the developing process will be much better!!!!

How many times do you have started the debbugger without to re-programming the FLASH???

CodeWarrior people, please consider it.

[regehr]

I have not gotten the INTERNAL_FLASH target to work either.  If I debug from INTERNAL_FLASH I get repeated windows with "Exception vector name: Address error" until I reset the board.  If I run the app from INTERNAL_FLASH then nothing happens at all.

This is using the default "hello world" project where I took out the printf() and added LED blinking in CWCF6.4 on MCF52233DEMO.  The CONSOLE_RAM and RAM targets work fine.  This application never enables or requests interrupts.

John Regehr

[mjbcswitzerland]

Hi

Ensure that the programm is being correctly programmed to FLASH by using either the internal CW FLASH programming utility or the CF FLASHER. This step is not automated and so just connecting to the debugger will not load any program to be executed, even if it gives the impression that it may be doing so.

See also this forum post for more details:

http://www.utasker.com/forum/index.php?topic=47.0

Regards

Mark

PS.
Check out the following tutorial, which may help with a step-by-step programming guide for both tools.
http://www.utasker.com/docs/M5223X/uTaskerV1.3-Tutorial-M5223X_003.PDF
from page 12/34.


Message Edited by mjbcswitzerland on 2007-09-13 02:48 PM

[osanz]

Hi Mark;

Yes, this was my mistake. I just expect to have the same behaviour, as on RAM target, so I only started the debugger, but not to program the flash....

Now is working without problems ( without this problem... ) so i agree so much all your help, on this matter.

Oscar Sanz.