A problem for debugging QorIQ P5020 with codewarrior

[Qiuyun]

Hello,

I was doing bareboard debugging for P5020DS (2 64-bit cores). I started with one core per project. The problem is that when I set up the breakpoint at the first line of 'main', and started the debug view, the program didn't enter into the main function. It jumped into the machine check interrupt. Does anybody meet this problem before? What happend? Is there really a hardware problem with the board that lead to machine check?

Btw, the codewarrior version that I am using is 10.1.1.

Thank you in advance!

[J2MEJediMaster]

OK, what happens when you build and run one of the demo programs that came with the CodeWarrior installation? If it exhbits the same problem, you might have a hardware problem. If this only happens in your program, then something in your setup code is either creating s spurious interrupt, or is failing to set up something propery, which then creates the spurious interrupt.

---Tom

[Qiuyun]

I was trying the sample program in the CodeWarrior: hello_world. Still not working after so many days and so many changes of configuration.

I really doubt there are some hardware problems with the board.

I also tried to configure the tcl file as P5020DS_init_sram.tcl. The machine checking interrupt is gone, but another interrupt occured: IVOR13 Data TLB Miss.

[J2MEJediMaster]

If you try the original setup, do you get the original interrupt problem? If so, that means something is messed up with the debugger initialization of the board. Have you installed the v1.1.1 service pack? (Check under Help > Install New Software.)

---Tom