RE: Re: PEMicro PPCBDM strange behaviour

OK, in this case it appears that your internal memory may be enabled
within the flash programming tool (programming) but disabled during the
debugger (nodebug).  The flash is enabled or disabled depending on your
reset configuration (refer to RSTCNFG, etc). FOr a fast check, try
setting the FLEN bit within the IMMR spr in your debugger and see if
your code magically appears.
 
- Allan

________________________________

From: [email protected] [mailto:[email protected]] On Behalf
Of rkaufmanus
Sent: Tuesday, February 06, 2007 5:22 PM
To: [email protected]
Subject: [MPC500] Re: PEMicro PPCBDM strange behaviour



Hi Allan,

the debugger even does not show the correct code / memory data right 
after 'target reset'.
The same address being read with the flashtool works fine.

Some links to show the problem:
http://www.dieselschrauber.de/Temp/mpc556_nodebug.jpg
<http://www.dieselschrauber.de/Temp/mpc556_nodebug.jpg> 
http://www.dieselschrauber.de/Temp/mpc556_programming.jpg
<http://www.dieselschrauber.de/Temp/mpc556_programming.jpg> 

Just compare what is being shown at address 0x100 (internal ECU flash 
memory).

Best regards, Rainer

--- In [email protected] <mailto:MPC500%40yahoogroups.com> ,
"Dobbin Allan-r11834" 
<Allan.Dobbin@...> wrote:
>
> When you say "as soon as you start the debugger", but presumably the
> debug session has already started if reading/writing memory works 
fine.
> Do you really mean 'when you start the CPU running code' ? This is
> relevant and effects the answer.
> 
> Anyway, if the opcodes are invalid data it could mean a number of
> different things and it depends what memory you are using.
> 
> If you are using external memory, perhaps the chip select or EBI 
isn't
> set correctly.
> Perhaps the debugger hasn't loaded your code.
> Perhaps there is no memory available where you are trying to locate 
the
> code.
> If the code is flash, you have to program it first or instruct the
> debugger how to program it.
> If the code started running and then stopped, perhaps the CPU has 
taken
> an exception with no vector and has ended up at an address where 
you
> didn't expect - verify the PC to check this.
> After you download the code to memory and set the PC to the start
> address, do not run any code, do not run until 'main', etc and see 
if
> your very first instruction is correct.
> 
> - Allan
> 
> ________________________________
> 
> From: [email protected] <mailto:MPC500%40yahoogroups.com>
[mailto:[email protected] <mailto:MPC500%40yahoogroups.com> ] On 
Behalf
> Of rkaufmanus
> Sent: Tuesday, February 06, 2007 2:31 PM
> To: [email protected] <mailto:MPC500%40yahoogroups.com> 
> Subject: [MPC500] PEMicro PPCBDM strange behaviour
> 
> 
> 
> Hi,
> 
> I have problems debugging an MPC556 with the PEMicro PPCBDM.
> Reading/writing of the ECU memory seems to work fine.
> 
> As soon as I start the debugger, I see only nonsense instead of the 
> expected program data. The debugger says this nonsense are 'invalid 
> opcodes'?!
> 
> What is going wrong here?
> 
> Thanks + best regards, Rainer
> 
> 
> 
> 
> 
> 
> [Non-text portions of this message have been removed]
>



 


[Non-text portions of this message have been removed]