* [U-Boot-Users] bus fault in calling eth_init()
@ 2006-12-04 23:40 Tom Brown
2006-12-04 23:57 ` Tom Brown
0 siblings, 1 reply; 2+ messages in thread
From: Tom Brown @ 2006-12-04 23:40 UTC (permalink / raw)
To: u-boot
Hi,
I've compiled up 1.1.6 and loaded it onto our board. I can't load linux
because I can't do a tftp. I get a bus fault every time I use the tftp
command or the ping command. I put some printf's into u-boot to try to
diagnose the problem. What I've come up with is the call to eth_init() is the
problem. Not the code in eth_init(), but the actuall call. Any ideas on what
the problem may be or what I need to be looking at?
The output of the bootup and result of the ping command is given below.
Thanks,
Tom
U-Boot 1.1.6.2 (Dec 4 2006 - 15:11:37)for the 195Eg
CPU: AMCC PowerPC 405EP Rev. B at 250 MHz (PLB=62, OPB=31, EBC=31 MHz)
I2C boot EEPROM disabled
Internal PCI arbiter enabled
16 kB I-Cache 16 kB D-Cache
I2C: ready
DRAM: 16 MB
Top of RAM usable for U-Boot at: 01000000
Reserving 263k for U-Boot at: 00fbe000
Reserving 256k for malloc() at: 00f7e000
Reserving 144 Bytes for Board Info at: 00f7df70
Reserving 48 Bytes for Global Data at: 00f7df40
Stack Pointer at: 00f7df28
New Stack Pointer is: 00f7df28
Now running in RAM - U-Boot at: 00fbe000
FLASH: manufact type value = 1f8b02
flash_protect ON: from 0xFFFC0000 to 0xFFFFFFFF
protect on 67
protect on 68
protect on 69
protect on 70
4 MB
In: serial
Out: serial
Err: serial
U-Boot relocated to 00fbe000
### main_loop entered: bootdelay=1
### main_loop: bootcmd="bootm ffc20000"
Hit any key to stop autoboot: 0
=> ping 172.16.32.9
find_cmd BEGIN
cmd == ping
find_cmd full match END
cmdtp == 0xff5ec808
do_ping
call NetLoop
NetLoop BEGIN
Setup packet buffers, aligned correctly
PktBuf[0] == 002
Fill NeRxPackets
Setup NetArpWaitTxPacket
eth_halt == 0xfc235408
call eth_halt()
bd == 0xf7df7008
eth_init == 0xfc200c08
call eth_init()
Bus Fault @ 0x00fc2018, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 00f7d828 Unknown values in msr
NIP: 00FC2018 XER: 00000000 LR: 00FC2018 REGS: 00f7d828 TRAP: 0200 DAR:
00F7DF40
MSR: 00001000 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00
GPR00: 00FC20FC 00F7D918 C017F8D0 00000000 00FC2080 00F7E1D8 00000000 00000000
GPR08: 00000002 600022E8 00200000 00FF6358 00000000 00000000 00FFBA00 00FFE000
GPR16: 00000000 00000001 FFFFFFFF 00F7DC48 00001000 00F7D978 00000000 00FC019C
GPR24: 00000000 00000000 FFFFFFFF 600022E8 00000001 00F7DF40 00FFBA98 00200000
Call backtrace:
machine check
^ permalink raw reply [flat|nested] 2+ messages in thread
* [U-Boot-Users] bus fault in calling eth_init()
2006-12-04 23:40 [U-Boot-Users] bus fault in calling eth_init() Tom Brown
@ 2006-12-04 23:57 ` Tom Brown
0 siblings, 0 replies; 2+ messages in thread
From: Tom Brown @ 2006-12-04 23:57 UTC (permalink / raw)
To: u-boot
On Monday 04 December 2006 15:40, Tom Brown wrote:
> Hi,
>
> I've compiled up 1.1.6 and loaded it onto our board. I can't load linux
> because I can't do a tftp. I get a bus fault every time I use the tftp
> command or the ping command. I put some printf's into u-boot to try to
> diagnose the problem. What I've come up with is the call to eth_init() is
> the problem. Not the code in eth_init(), but the actuall call. Any ideas on
> what the problem may be or what I need to be looking at?
Ummm... nevermind. I was looking at the wrong eth_init(). So, this amounted to
a problem in the cockpit.
Thanks,
Tom
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-12-04 23:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-12-04 23:40 [U-Boot-Users] bus fault in calling eth_init() Tom Brown
2006-12-04 23:57 ` Tom Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox