[U-Boot-Users] Re: Hang after relocating u-boot code...

Sam Song samsongshu at yahoo.com.cn
Fri Jan 9 03:16:12 CET 2004


Hi,Wolfgang,

Oop,I sent the same topic again for my carelessness.Pls forgive me this time.

After having tried some settings of UPM Burst Read with no obvious improvement
on my custom board,I need to consult with you on this matter.

When using the UPM Burst Read settings whick worked on LITE_DW,I got the
following best result by now.I wrote some UPMA Burst Read Words but without no
better performance. 

1.With "g" commands in BDI regardless of entering debugging mode,it ran again
and was stopped immediately by using "halt":

1)In BDI console:

BDI>re
- TARGET: processing user reset request
- TARGET: resetting target passed
- TARGET: processing target init list ....
- TARGET: processing target init list passed
BDI>g
- TARGET: target has entered debug mode
BDI>i
    Target state      : debug mode
    Debug entry cause : entering check stop state
    Current PC        : 0x00000200
BDI>g
BDI>ha
    Target state      : debug mode
    Debug entry cause : external breakpoint
    Current PC        : 0x03ff5020
BDI>re
- TARGET: processing user reset request
- TARGET: resetting target passed
- TARGET: processing target init list ....
- TARGET: processing target init list passed
BDI>g
- TARGET: target has entered debug mode
BDI>i
    Target state      : debug mode
    Debug entry cause : entering check stop state
    Current PC        : 0x00000200
BDI>g
BDI>ha
    Target state      : debug mode
    Debug entry cause : external breakpoint
    Current PC        : 0x03ff501c
BDI>

2)In minicom console:

U-Boot 1.0.0 (Jan  8 2004 - 20:24:19)

CPU:   PPC823EZTnnB2 at 64 MHz: 16 kB I-Cache 8 kB D-Cache
Board: My_Board
DRAM:  64 MB
Bus Fault @ 0x00000200, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 03fbce88 Unknown values in msr
NIP: 00000200 XER: A000187F LR: 03FE3328 REGS: 03fbce88 TRAP: 0200 DAR:
00000040
MSR: 40000000 EE: 0 PR: 0 FP: 0 ME: 0 IR/DR: 00

GPR00: 03FFB044 03FBCF78 00000000 03FFA0A4 03FFB400 03FFB400 00000010 03FFB3FC
GPR08: FFF1A3FC 03FBCF94 03FE1000 040E1000 00000000 60C5DCB3 04001A00 040E1000
GPR16: 729C1A82 3AA8AFB6 DC8C92B7 8066A981 00001002 00000001 00000000 03FE309C
GPR24: 03FE9170 00000040 00000001 03FE1000 03FBCF94 FA202EC0 04001BB4 03FBCF78
Call backtrace:
machine check
NIP: FFEFFFFC XER: 8000187F LR: 03FE875C REGS: 03fbccc8 TRAP: 1000 DAR:
30303430
MSR: 00000002 EE: 0 PR: 0 FP: 0 ME: 0 IR/DR: 00

GPR00: FFEFFFFC 03FBCDB8 00000000 00000000 00000000 00000000 00000000 005EBEBA
GPR08: 03FE99C8 FFFFEFCF FA202808 02000000 00000000 60C5DCB3 04001A00 040E1000
GPR16: 729C1A82 3AA8AFB6 DC8C92B7 8066A981 00001002 03FBCE78 00000000 03FE309C
GPR24: 03FE8FE8 00000040 00000001 03FE1000 03FBCF94 FA202EC0 04001B60 03FBCE88
Call backtrace:
Software Emulation Exception
NIP: FFEFFFFC XER: 8000187F LR: 03FE875C REGS: 03fbcb08 TRAP: 1000 DAR:
33343330
MSR: 00000002 EE: 0 PR: 0 FP: 0 ME: 0 IR/DR: 00

GPR00: FFEFFFFC 03FBCBF8 00000000 00000000 000

2.When setting DER as 0x51c7000f,I get the "good" results by over 70 continuing
"go" commands:

1)In BDI console

- TARGET: processing user reset request
- TARGET: resetting target passed
- TARGET: processing target init list ....
- TARGET: processing target init list passed
BDI>rm der 0x51c7000f
BDI>g
- TARGET: target has entered debug mode
BDI>i
    Target state      : debug mode
    Debug entry cause : machine check interrupt
    Current PC        : 0xfff106e0
    Data  address     : 0x000420c0
    DSISR value       : 0x00400202
BDI>g
- TARGET: target has entered debug mode
BDI>i
    Target state      : debug mode
    Debug entry cause : machine check interrupt
    Current PC        : 0x03fe3340
    Data  address     : 0x03ffa0d0
    DSISR value       : 0x00004003

BDI>g
- TARGET: target has entered debug mode
BDI>g
- TARGET: target has entered debug mode
.......
BDI>g
- TARGET: target has entered debug mode

2)In minicom console

U-Boot 1.0.0 (Jan  8 2004 - 20:24:19)

CPU:   PPC823EZTnnB2 at 64 MHz: 16 kB I-Cache 8 kB D-Cache
Board: My_Board
DRAM:  64 MB
FLASH: 64 MB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   SCC ETHERNET
u-boot>

It seems that one more step could succeed.However,the truth hurts.I trapped in
settings of UPM RAM Words and want to figure it out.

So,which is perfer to between Burst Read with Auto Precharge and Burst Read
without Auto Percharge or both OK?

Does it matter without hard reset configuration circuit on my board?Is it
related with my UPM settings?

Thanks for reading!

Best regards,

Sam















__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 




More information about the U-Boot mailing list