* Ebony/440GP boot problems
@ 2003-02-01 17:38 brian.auld
0 siblings, 0 replies; 3+ messages in thread
From: brian.auld @ 2003-02-01 17:38 UTC (permalink / raw)
To: linuxppc-embedded
To recap:
I am trying to get embedded linux running on the Ebony 440GP eval board with
u-boot as the boot loader.
I believe I've successfully programmed u-boot into the upper 0.5MB of the
32bit memory map. I don't want to print out the entire memory dump, but I'll
attach the beginning and end of the top 0.5MB chunk of memory (i.e. u-boot).
When I reset the board, the serial console is dead. I've tried every
imaginable baud rate and the serial console is still dead. Even if I had the
wrong baud, I'd at least expect to see jibberish on the serial console,
which I don't.
Any suggestions? The third clip below, showing the top 256 bytes of the boot
area, has data content of 0x4bfff004. In what I have gotten so far out of
440GP manuals, this address is the reset vector. Well, if that's the case,
0x4bfff0004 does not sound like a good number, does it. Or, am I looking in
the wrong place. I thought the contents of addr 0xfffffffc would point to
the start of u-boot at addr 0xfff80000, which it doesn't appear to.
========= Clip of bdi console on reset ==========
BDI>reset
- TARGET: processing user reset request
- TARGET: reseting target passed
- TARGET: processing target startup ....
- TARGET: processing target startup passed
BDI>
==================================================
========= bottom 256 bytes of boot area ==========
BDI>md 0xfff80000
fff80000 : 27051956 552d426f 6f742030 2e322e30 '..VU-Boot 0.2.0
fff80010 : 20284a61 6e203331 20323030 33202d20 (Jan 31 2003 -
fff80020 : 30353a31 323a3535 29000000 00000000 05:12:55).......
fff80030 : 00000000 00000000 00000000 00000000 ................
fff80040 : 00000000 00000000 00000000 00000000 ................
fff80050 : 00000000 00000000 00000000 00000000 ................
fff80060 : 00000000 00000000 00000000 00000000 ................
fff80070 : 00000000 00000000 00000000 00000000 ................
fff80080 : 00000000 00000000 00000000 00000000 ................
fff80090 : 00000000 00000000 00000000 00000000 ................
fff800a0 : 00000000 00000000 00000000 00000000 ................
fff800b0 : 00000000 00000000 00000000 00000000 ................
fff800c0 : 00000000 00000000 00000000 00000000 ................
fff800d0 : 00000000 00000000 00000000 00000000 ................
fff800e0 : 00000000 00000000 00000000 00000000 ................
fff800f0 : 00000000 00000000 00000000 00000000 ................
BDI>
====================================================
============ Top 256 bytes of boot area ============
BDI>md 0xffffff00
ffffff00 : ffffffff ffffffff ffffffff ffffffff ................
ffffff10 : ffffffff ffffffff ffffffff ffffffff ................
ffffff20 : ffffffff ffffffff ffffffff ffffffff ................
ffffff30 : ffffffff ffffffff ffffffff ffffffff ................
ffffff40 : ffffffff ffffffff ffffffff ffffffff ................
ffffff50 : ffffffff ffffffff ffffffff ffffffff ................
ffffff60 : ffffffff ffffffff ffffffff ffffffff ................
ffffff70 : ffffffff ffffffff ffffffff ffffffff ................
ffffff80 : ffffffff ffffffff ffffffff ffffffff ................
ffffff90 : ffffffff ffffffff ffffffff ffffffff ................
ffffffa0 : ffffffff ffffffff ffffffff ffffffff ................
ffffffb0 : ffffffff ffffffff ffffffff ffffffff ................
ffffffc0 : ffffffff ffffffff ffffffff ffffffff ................
ffffffd0 : ffffffff ffffffff ffffffff ffffffff ................
ffffffe0 : ffffffff ffffffff ffffffff ffffffff ................
fffffff0 : ffffffff ffffffff ffffffff 4bfff004 ............K...
BDI>
========= Clip of bdi console on reset ==========
Any suggestions would be appreciated.
-- Brian
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: Ebony/440GP boot problems
@ 2003-02-01 19:10 brian.auld
2003-02-01 19:31 ` Chris Zimman
0 siblings, 1 reply; 3+ messages in thread
From: brian.auld @ 2003-02-01 19:10 UTC (permalink / raw)
To: linuxppc-embedded
As shown below, after reset, if I enter the 'ti' command, we start single
stepping from 0xfffff000. Each time I 'ti', the PC gets incremented by a 32
bit word. It would then appear that code is not running and I start frozen
at 0xfffff000. Can anyone make sense of this?
==========================================
BDI>reset
- TARGET: processing user reset request
- TARGET: reseting target passed
- TARGET: processing target startup ....
- TARGET: processing target startup passed
BDI>
BDI>
BDI>
BDI>
BDI>
BDI>ti
Target state : debug mode
Debug entry cause : single step
Current PC : 0xfffff000
Current CR : 0xab355bb5
Current MSR : 0x00000000
Current LR : 0x840208d5
BDI>ti
Target state : debug mode
Debug entry cause : single step
Current PC : 0xfffff004
Current CR : 0xab355bb5
Current MSR : 0x00000000
Current LR : 0x840208d5
BDI>ti
Target state : debug mode
Debug entry cause : single step
Current PC : 0xfffff008
Current CR : 0xab355bb5
Current MSR : 0x00000000
Current LR : 0x840208d5
BDI>ti
Target state : debug mode
Debug entry cause : single step
Current PC : 0xfffff00c
Current CR : 0xab355bb5
Current MSR : 0x00000000
Current LR : 0x840208d5
BDI>ti
Target state : debug mode
Debug entry cause : single step
Current PC : 0xfffff010
Current CR : 0xab355bb5
Current MSR : 0x00000000
Current LR : 0x840208d5
BDI>
===========================================
-- Brian
-----Original Message-----
From: Chris Zimman [mailto:chris@cryptoapps.com]
Sent: Saturday, February 01, 2003 1:37 PM
To: brian.auld@adic.com
Subject: Re: Ebony/440GP boot problems
On Sat, Feb 01, 2003 at 09:38:38AM -0800, brian.auld@adic.com wrote:
> To recap:
>
> I am trying to get embedded linux running on the Ebony 440GP eval board
with
> u-boot as the boot loader.
>
> I believe I've successfully programmed u-boot into the upper 0.5MB of the
> 32bit memory map. I don't want to print out the entire memory dump, but
I'll
> attach the beginning and end of the top 0.5MB chunk of memory (i.e.
u-boot).
>
> When I reset the board, the serial console is dead. I've tried every
> imaginable baud rate and the serial console is still dead. Even if I had
the
> wrong baud, I'd at least expect to see jibberish on the serial console,
> which I don't.
>
> Any suggestions? The third clip below, showing the top 256 bytes of the
boot
> area, has data content of 0x4bfff004. In what I have gotten so far out of
> 440GP manuals, this address is the reset vector. Well, if that's the case,
> 0x4bfff0004 does not sound like a good number, does it. Or, am I looking
in
> the wrong place. I thought the contents of addr 0xfffffffc would point to
> the start of u-boot at addr 0xfff80000, which it doesn't appear to.
Go into the debugger and do a "ti" immediately after reset.
BDI> ti
That way you'll see where the next instruction is being executed from.
--Chris
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Ebony/440GP boot problems
2003-02-01 19:10 Ebony/440GP boot problems brian.auld
@ 2003-02-01 19:31 ` Chris Zimman
0 siblings, 0 replies; 3+ messages in thread
From: Chris Zimman @ 2003-02-01 19:31 UTC (permalink / raw)
To: brian.auld; +Cc: linuxppc-embedded
On Sat, Feb 01, 2003 at 11:10:28AM -0800, brian.auld@adic.com wrote:
> As shown below, after reset, if I enter the 'ti' command, we start single
> stepping from 0xfffff000. Each time I 'ti', the PC gets incremented by a 32
> bit word. It would then appear that code is not running and I start frozen
> at 0xfffff000. Can anyone make sense of this?
>
> ==========================================
> BDI>reset
> - TARGET: processing user reset request
> - TARGET: reseting target passed
> - TARGET: processing target startup ....
> - TARGET: processing target startup passed
> BDI>
> BDI>
> BDI>
> BDI>
> BDI>
> BDI>ti
> Target state : debug mode
> Debug entry cause : single step
> Current PC : 0xfffff000
> Current CR : 0xab355bb5
> Current MSR : 0x00000000
> Current LR : 0x840208d5
> BDI>ti
> Target state : debug mode
> Debug entry cause : single step
> Current PC : 0xfffff004
> Current CR : 0xab355bb5
> Current MSR : 0x00000000
> Current LR : 0x840208d5
> BDI>ti
> Target state : debug mode
> Debug entry cause : single step
> Current PC : 0xfffff008
> Current CR : 0xab355bb5
> Current MSR : 0x00000000
> Current LR : 0x840208d5
> BDI>ti
> Target state : debug mode
> Debug entry cause : single step
> Current PC : 0xfffff00c
> Current CR : 0xab355bb5
> Current MSR : 0x00000000
> Current LR : 0x840208d5
> BDI>ti
> Target state : debug mode
> Debug entry cause : single step
> Current PC : 0xfffff010
> Current CR : 0xab355bb5
> Current MSR : 0x00000000
> Current LR : 0x840208d5
> BDI>
> ===========================================
0xfffff000 is the start of ppc/u-boot. Break out a copy of GDB and start
tracing into it to find out where it's blowing up.
Build ppc/u-boot with "-fno-schedule-insns -fno-schedule-insns2" added
to the compile line.
--Chris
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-02-01 19:31 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-02-01 19:10 Ebony/440GP boot problems brian.auld
2003-02-01 19:31 ` Chris Zimman
-- strict thread matches above, loose matches on Subject: below --
2003-02-01 17:38 brian.auld
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).