From: Josef Angermeier <Josef.Angermeier@informatik.stud.uni-erlangen.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] hang after "Transferring Control to Linux": bd_info difference ?
Date: Mon, 20 Feb 2006 10:58:39 +0100 [thread overview]
Message-ID: <20060220095838.GA31756@false> (raw)
Dear u-boot-users,
u-boot works on my custom board (MPC875, 64MB RAM, 16MB flash) but linux
hangs (see debug console output below) when started with bootm-command.
I am using the ELDK 3.1.1 kernel sources (version 2.4.25) and a u-boot CVS
version which is slightly newer than the 1.1.3 release. CLOCKS_IN_MHZ is not
defined in my u-boot board config file and the IMMR define is in kernel and
u-boot board config file identical.
I noticed, that bd_info structure in u-boot/asm-ppc/u-boot.h and eldk/ppc_8xx/
usr/src/linux/include/asm-ppc/ppcboot.h differ abit: in the kernel sources a
mon_fnc_t *bi_mon_fnc; /* Pointer to monitor functions */
} bd_t;
pointer to monitor funcs is defined, which is does not appear in u-boot.h. Is
this intended or a bug ?
What else could i tryout before analyzing kernel log buffer and debugging the
kernel ?
best regards,
Josef
---------------- SERIAL DEBUG OUTPUT ------------------------------
U-Boot 1.1.3 (Feb 20 2006 - 09:31:08)
CPU: MPC885ZPnn at 40 MHz: 8 kB I-Cache 8 kB D-Cache FEC present
clock 40000000Hz != 100000Hz
You made sure it's an ESM this is running on, right?
DRAM: 64 MB
Top of RAM usable for U-Boot at: 04000000
Reserving 203k for U-Boot at: 03fcd000
Reserving 2564k for malloc() at: 03d4c000
Reserving 60 Bytes for Board Info at: 03d4bfc4
Reserving 48 Bytes for Global Data at: 03d4bf94
Stack Pointer at: 03d4bf78
New Stack Pointer is: 03d4bf78
Now running in RAM - U-Boot at: 03fcd000
FLASH: 61.3 MB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
U-Boot relocated to 03fcd000
Net: FEC ETHERNET
=> bootm 0xe0080000
## Booting image at e0080000 ...
Image Name: Linux-2.4.25
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 284357 Bytes = 277.7 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Current stack ends at 0x03D4BCE8 => set upper limit to 0x00800000
## cmdline at 0x007FFF00 ... 0x007FFF00
bd address = 0x03D4BFC4
memstart = 0x00000000
memsize = 0x04000000
flashstart = 0xE0000000
flashsize = 0x03D4BF78
flashoffset = 0x00000000
sramstart = 0x00000000
sramsize = 0x00000000
immr_base = 0xFF000000
bootflags = 0x00000001
intfreq = 40 MHz
busfreq = 40 MHz
ethaddr = D6:60:1B:EF:B4:11
IP addr = 131.188.51.169
baudrate = 38400 bps
No initrd
## Transferring control to Linux (at address 00000000) ...
next reply other threads:[~2006-02-20 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 9:58 Josef Angermeier [this message]
2006-02-20 10:35 ` [U-Boot-Users] hang after "Transferring Control to Linux": bd_info difference ? Wolfgang Denk
2006-02-20 12:18 ` Josef Angermeier
2006-02-20 12:41 ` Wolfgang Denk
2006-02-20 13:02 ` Josef Angermeier
2006-02-20 13:45 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060220095838.GA31756@false \
--to=josef.angermeier@informatik.stud.uni-erlangen.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox