Hi Andy, Here is BDI output of the register value after line 212. The value of R6, R7 is 0x20, 0x160. However the value of SRR0(SPR26), SRR1(SPR27) is 0xfff81300 and 0x00001000. Why are they different from r7 and r6? We just did the mtspr, the value should be the same. The rfi jump to 0xfff81300 is because of the value in SRR0.
211 mtspr SRR0, r7 212 mtspr SRR1, r6 213 rfi 214 215 /*4. Clear out PIDs & Search info */ 216 li r6, 0 BDI output: cds8548>bi 0x0000015c Breakpoint identification is 0 cds8548>go - TARGET: stopped cds8548>rd GPR00: 00000000 0ffabd20 00000200 00000008 GPR04: 00000000 00000001 00000020 00000160 GPR08: 1f8b0808 00000148 0ffabace 0ffe08b0 GPR12: 00000006 764deddb 10000300 007fff00 GPR16: 00000001 ffffffff 007fff25 0ffff9d8 GPR20: 007ffeb0 00000000 0fffaa3c 0ffae490 GPR24: 00000000 00000003 02000040 007fff25 GPR28: 007fff00 0ffab3b8 0fcd6000 007ffeb0 CR : 24024022 MSR: 00021200 cds8548>rdspr 26 SPR 26 : 0xfff81300 - 519424 cds8548>rdspr 27 SPR 27 : 0x00001000 4096 cds8548> On 8/15/07, Andy Fleming <[EMAIL PROTECTED]> wrote: > > > On Aug 15, 2007, at 16:12, mike zheng wrote: > > > Here is the PC value before the rfi: > > > > cds8458>halt > > Target CPU: : MPC85xx (e500v2 rev.1) > > Target state : halted > > Debug entry cause : instruction breakpoint > > Current PC : 0x0000015c > > Current CR : 0x24024022 > > Current MSR : 0x00012100 > > Current LR :0x00000148 > > Current CCSRBAR :0x0_e000000 > > > > After the rfi: > > > > #step timeout defected > > cds8458>halt > > Target CPU: : MPC85xx (e500v2 rev.1) > > Target state : halted > > Debug entry cause : COP halt > > Current PC : 0xfff81300 > > Current CR : 0x24024022 > > Current MSR : 0x00001000 > > Current LR :0x00000148 > > Current CCSRBAR :0x0_e000000 > > Ok, I'm sure your problem isn't that SRR0 isn't getting updated > properly. I suspect something is going wrong during the rfi. > Possibly something in your TLBs. However, what is happening is most > likely that you have hit an exception, and SRR0 and SRR1 have been > updated. I'm a little confused by the addresses where you first > invoke "halt". It looks like you're in the middle of flash, which is > an odd place in u-boot to be. The first halt is at 0x0000015c, which is the break point I set after line 212. It is in the memory, not flash. And if you look at your PC, it doesn't seem like you step. It looks > like something goes wrong with the debugging. My suggestion is to > check your TLB setup and your IVOR setup. Find out if the IVORs are > pointing at an exception at fff81300. All the TLB and IVOR setup is from Uboot, the kernel haven't touched them yet. Andy >
_______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
