RE: Startup of MPC5500 (MPC5566)

I'm not sure what could be causing this, some questions and comments
below, maybe you have already solved it since you posted this.
 
- which debugger are you using?
 
- is it possible the debugger init script is doing something
significant?  Try removing as much as possible and see if it still runs.
 
- could it be an SRAM ECC error i.e. related to above, is the debugger
initializing the SRAM?  One test for this is to try running without the
debugger after first running with the debugger but without a power
cycle.  Or an easier way is just to try removing the SRAM init from the
debuggr init script.
 
- could it be a power up issue?  Try a reset after power has stabilised
without th debugger.
 
- most wigglers connect to the 3.3V line.  Look at the 3.3V with and
without the wiggler connected to see if there is any significant change.
 
- you could try using the free GAP debugger from Freescale.  Its a
simple tool but is good because its simple i.e. its easier to determine
exactly what the debugger is doing.
 
- what happens without the debugger?  Can you confirm the clkout is at
correct frequency?  I recollect that the watchdog should also be firing
a reset periodically i.e. possible every 20 seconds or so.

- Allan
 
 
 

________________________________

From: MPC500@... [mailto:MPC500@...] On Behalf
Of stevenaschroeder
Sent: Monday, December 22, 2008 2:40 PM
To: MPC500@...
Subject: [MPC500] Startup of MPC5500 (MPC5566)



I'm just bringing up our first MPC5566 board. Everything is fine with
a debugger. I watch the BAM find the RCHW, jumps to my code, and runs
fine. (I just have a loop wiggling a GPIO--geesh.) Without the
debugger, however, I get nothing.

Can someone point me in the right direction--what I am missing?

Thanks,
Steve



 


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