AnsweredAssumed Answered

Very slow flash programming when preserving memory area

Question asked by Dee Kay on Oct 17, 2012
Latest reply on Oct 17, 2012 by Dee Kay

Hello!

 

I am using codewarrior and TWR-60 evalatuin board and its USB interface for debugging. I have two projects.

1.     Very simple bootloader that shall jump to main app.

2.     Main app, located at flash 0xC000 (exception vectors starts here). I have modified the linker files accordingly.

    

 

I used the following information as reference Modify linker command files

 

First I erase the whole flash and program the bootloader, no problems there, it takes a couple of sec.

 

Then I try to flash the main app with modified debugger advanced settings to preserve NVM area 0x0 to 0xBFFF.

Once started it takes minutes for the debugger to finish. It halts here (taken from console)

...

INF: ;begin_cs device=$00000000, length=$00080000, ram=$20000000

INF: Loading programming algorithm ...

INF: WARNING - Selected .ARP file has been modified. CRC16 = $347F

INF: Done.

INF: CMD>EM


Then it takes a couple of minutes for the debugger to continue with erasing, programming etc. I have noticed that if I reduce the preserved mem range, this time decreases.


What is taking so long? Have I missed anything?


Happy for answers.

Outcomes