Can't debug

[timotay01]

When trying to move from the MCF5208EVB to our target board using CF5208 I get the following error when attempting to debug (our board)

"Could not set PC to entry point". This error comes up everytime after it downloads the code to the RAM. I have created a .cfg file to match the differences between the EVB board and ours and using it in a new target profile. Has anyone seen this error before or have some insight into what I could do to try find out what might be wrong on our board?

[ElectricMonk]

Long time since your post, but I've just had this problem.  It went away once I erased the lowest block of FLASH.  It looks like the processor was running some code (perhaps in user mode) which prevented access to the PC.

[armish]

Hi dear,

I am using Coldfire mcf5329 mcu and codewarrior version 5.7. I am also facing the error 'Cant set PC to entry point' 9 out of 10 times, I want to download the code to SRAM of MCU. Could you pls elaborate how did you resolve this problem?

Thanks in advance

[J2MEJediMaster]

OK, just to make sure I got this straight: the program downloads without problems on the eval (EVB) board, but not on your prototype? The error message tends to hint that the debugger isn't getting control of the processor. Are you certain that the debug interface is working properly?

---Tom

[timotay01]

[TOM] OK, just to make sure I got this straight: the program downloads without problems on the eval (EVB) board, but not on your prototype?

[TIM] Correct

[TOM]The error message tends to hint that the debugger isn't getting control of the processor.

[TIM] Agreed, I will look more closely at the signals from the BDM to the processor.

[TOM] Are you certain that the debug interface is working properly?

[TIM] I assumed it was because it downloads the code fine (Blue downloaad progress bar completes), then the error happens once it tries to start running. Also in my .cfg file I can change the status of an onboard LED (on or off) and it does turn the LED on or off.

---Tom