Problems during load of MCF51AC256.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Problems during load of MCF51AC256.

Jump to solution
1,763 Views
JHLG
Contributor II

Hi,

 

I'm using a MCF51AC256 on a new prototype.

 

I get an error message in Command window when loading the target.

 

...

FP: Run applet (WaitUntilStopped).
GDI:   Writing Register: PC (id:16): 0x080000C
GDI:   DiRegisterWrite()==> DI_OK
EXEC_Run();
GDI:   DiExecContinue()==> DI_OK
<Timeout>
FP: WaitUntilStopped failure begin report.
GDI:   Reading From Memory Address: 0x0100, count: 4, memSpace: 4
GDI:   DiMemoryRead()==> DI_ERR_FATAL
GDI:   DiErrorGetMessage()==> 1
GDI:   Error Message ==> The Debugger can not read memory.
...

 

I don't understand why this timeout appears.

Can you help me.

 

JHLG.

Labels (1)
0 Kudos
1 Solution
719 Views
JHLG
Contributor II

Thank you for your answer.

 

But I get an answer from Freescale Support.

They tell me to download and install "CW MCU v6.2 CFV1 AC256A Service Pack" from their website and it works fine now.

 

Regards.

JH.

View solution in original post

0 Kudos
6 Replies
719 Views
JHLG
Contributor II

Sorry I forgot:

    - I use "P&E micro USB Multilink" with "True Time Simulator & RealTime Debugger".

    - I have no external oscillator on my PCB (but I can mount one), because i would like to use the internal oscillator.

 

Thank you.

JHLG.

0 Kudos
719 Views
JHLG
Contributor II

No one has an idea.

 

I continue my research so i can give you more details.

 

The process of connection with the MCF51AC256B via my  P&E USB BDM Multilink is OK.

 

And if I well understand : it loads and executes some codes in RAM memory before loads codes in Flash memory.

 

But when I try to load my .abs file I loose the connection and some Popup message appears :

     - "The debugger can not red memory"

     - "Error while writing to 3FC..5FC"

     - "Error while writing to 40C..60C"

     - "Error loading".

 

 

Can someone help me.

Please.

JHLG.

 

0 Kudos
719 Views
Kopone
Contributor IV

I am using the same MCU on a project and also with the internal oscillator.

I didnt encounter any similar problems though. Whenever i had odd problems with this project, it always turned out the MCU wasnt properly soldered (by me).

 

I guess your problem may either lie in your MCU getting halted by the surrounding peripherals or maybe you have a voltage drop during programming. Also the ribbon cable might just be too long or it may be simply be a slack joint.

 

Regards,

 Sven

0 Kudos
720 Views
JHLG
Contributor II

Thank you for your answer.

 

But I get an answer from Freescale Support.

They tell me to download and install "CW MCU v6.2 CFV1 AC256A Service Pack" from their website and it works fine now.

 

Regards.

JH.

0 Kudos
719 Views
wrljet
Contributor II
"CW MCU v6.2 CFV1 AC256A Service Pack" worked for me, too. I have a hand-soldered and hand-wired 51AC256A connected to the BDM on the DEMOJM board. Couldn't connect to the debugger until I installed that service pack. Thank you for sharing that tidbid. Bill
0 Kudos
719 Views
wrljet
Contributor II

I spoke too soon.

 

After installing that patch, I theUSB-ML-12 from the DEMOJM board does connect to the

F51AC256, and it can program the Flash.   But the debugger locks up.


I can single step after a reset, for a while, but if I just let it rip it hangs in the ProcessorExpert

supplied startup code.   The debugger says Running.  I click Stop and it stops, in a weird

place.   Then any additional single step, etc. commands it says "The Debugger can not read memory".

 

Perhaps the USB-ML-12 that's embedded in the DEMOJM can't handle the F51AC256.

One thing's for sure, I'm not buying anything from PE Micro.   Next stop for me is the USBDM.

 

 

0 Kudos