[U-Boot] Linux hangs when uncompressing kernel image: linux-2.6.26
Hello
I've been working on building a 2.6.26 linux kernel to the mpc5200Lite
PowerPc board. However, I am unable to boot the system using the
generated image.
I am using what seems to be the latest U-Boot for the job. Got it from
www.denx.de/git/u-boot.git.
I'm using the device tree compiler dtc-v1.2.0 to compile the device tree
source into a device tree blob. Got it at:
http://jdl.com/software/dtc-latest.tgz
For the device, my design procedure is the following:
1. In the first step I generate the uImage file ('make ARCH=powerpc
zImage'), the corresponding lite5200b.dts and compile it to
lite5200b.dtb.
2. Afterwards, I do the U-Boot configs. I define 0x0060 as the device
tree address and 0x0020 as the uImage's.
3. Finally, I transfer them all (using tftp for each, of course) and try
to boot: 'bootm 0x0020 - 0x0060'
The result is that the console hangs...
Does anyone have any idea of why it happens? I checked a similar problem
at the
http://www.denx.de/wiki/view/DULG/LinuxHangsAfterUncompressingKernel, and
I'm almost convinced that it is probably a bd_info problem, concerning
the definitions of the kernel's IMAP_ADDR and the CFG_IMMR of U-Boot to
be unmatching.
If that is the case, how/where can I correct it? Which files should I
look for?
Thanks for the attention.
Marco Antônio Possamai
Universidade Federal de Santa Catarina
--
It's News. It's Reviews. It's Interviews. It's Free. What Are You Waiting For?
www.movieline.com
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-Boot hangs after uncompressing kernel image on MPC5200B
Thank you for your reply Mr. Likely! I was indeed using the wrong image file. So I've tried the uImage generated by the kernel build, and it still hangs. It might be the addresses I'm using. I've read some FAQs sections that seemed to give me some hope, but they all were related to wrong RAM addresses or not related to device trees at all, just to the old cuImage booting procedures. Anyway, thanks for your interest, Mr. Likely. - Original Message - From: Grant Likely To: Marco Antônio Possamai Cc: U-Boot Subject: Re: [U-Boot] U-Boot hangs after uncompressing kernel image on MPC5200B Date: Thu, 22 Jan 2009 07:30:01 -0700 On Thu, Jan 22, 2009 at 4:05 AM, Marco Antônio Possamai wrote: Hello, all. My goal is to succesfully pass a 2.6.26 linux kernel to the MPC5200B using the three-argument command bootm. [...] I've built the image using the make ARCH=powerpc zImage command. It creates the cuImage.lite5200b along with the lite5200.dts (which I've compiled to a lite5200.dtb using the above mentioned dtc). If you want to use the 3 argument bootm (kerneladdr, rootfsaddr, dtbaddr) then you need to use the uImage produced by the kernel build, *not* the cuImage. The cuImage is a backwards compatible image for the older 2 argument bootm command. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. Marco Antônio Possamai Universidade Federal de Santa Catarina -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] U-Boot hangs after uncompressing kernel image on MPC5200B
Hello, all.
My goal is to succesfully pass a 2.6.26 linux kernel to the MPC5200B
using the three-argument command bootm.
I'm using the DENX ELDK toolchain, the U-Boot v1.2.0, the dtc-v1.2.0
(latest device tree compiler), and a suitable tftp-server pointing to
/tftpboot/5200.
I've built the image using the make ARCH=powerpc zImage command. It
creates the cuImage.lite5200b along with the lite5200.dts (which I've
compiled to a lite5200.dtb using the above mentioned dtc).
The bootloader stalls after uncompressing the kernel image. Check the
snippet below after I've configured the bootloader (using GtkTerm for
PC-board communications):
= tftp 0x0100 ${bootfile}
Using FEC ETHERNET device
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename '5200/uImage'.
Load address: 0x100
Loading:
#
done
Bytes transferred = 1352689 (14a3f1 hex)
= bootm 0x0100 - ${fdtaddr}
## Booting kernel from Legacy Image at 0100 ...
Image Name: Linux-2.6.26.8-dirty
Created: 2009-01-21 14:33:22 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size:1352625 Bytes = 1.3 MB
Load Address: 0040
Entry Point: 00400550
Verifying Checksum ... OK
## Flattened Device Tree blob at 0004
Booting using the fdt blob at 0x4
Uncompressing Kernel Image ... OK
Please notice that the 5200/uImage (renamed from cuImage.lite5200b) is
the bootfile. The fdtaddr bears the device tree blob address at
0x0004.
One of my doubts is that I'm unsure to where the device tree and the
image addresses should be. Obviously they should not overwrite each
other, and that is exactly what I take care of when assigning the
addresses' values. Still, I'm experiencing these stalls.
Any help would be highly appreciated.
Marco Antônio Possamai
Universidade Federal de Santa Catarina
--
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] device-tree check MPC5200B Lite
Greetings, I've read the FAQ in http://www.denx.de/wiki/view/DULG/LinuxHangsAfterUncompressingKernel, concerning the 'Linux hangs after uncompression' problem. And I'm not sure how to verify if the device tree I've generated (along with the image) is alright or not. I don't know where I can find the mapping of IMMR or PCI in the files present there, for instance. Is there any documentation or literature that could help me? Some specs: Board: MPC5200B Device-tree compiler version: 1.2.0 Kernel image to be passed to the board: Linux-2.6.26.8-dirty Xenomai: 2.4.x U-Boot version: 2008.10 Thanks in advance. Marco Antônio Possamai Universidade Federal de Santa Catarina -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] U-Boot hangs after uncompressing image
Hello, all!
As the title says, it hangs when uncompressing the image. The board is
the MPC5200b Lite.
Got the device-tree blob after compiling it from the lite5200b.dts. Used
the latest device-tree compiler (v1.2.0);
Got the file cuImage.lite5200b to pass it as image.
Stored 0x0001 in fdt_addr_r. Stored the path to the dtb file in
fdt_file and the image file in the bootfile.
Image's at 0x0100.
Some commands I've used:
$ tftp ${fdt_addr_r} ${fdt_file}
$ fdt addr ${fdt_addr_r}
$ tftp 0x0100 ${bootfile}
$ bootm 0x0100 - ${fdt_addr_r}
Here's what the GtkTerm spills:
## Booting kernel from Legacy Image at 0100 ...
Image Name: Linux-2.6.26.8-dirty
Created: 2008-12-10 18:40:18 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size:1741950 Bytes = 1.7 MB
Load Address: 0040
Entry Point: 00400550
Verifying Checksum ... OK
## Flattened Device Tree blob at 0001
Booting using the fdt blob at 0x1
Uncompressing Kernel Image ... OK
Then it hangs...
I've read the FAQ section about it and it simply says it could be a bad
device-tree. I'm not sure how to check it.
I'm using the latest U-Boot and the 2.6.26.8-dirty (as shown above), by
the way.
Thanks for your patience.
My PC specs:
Ubuntu 8.04 (Hardy Heron)
Kernel Linux 2.6.24-22-generic
GNOME 2.22.3
Marco Antônio Possamai
Universidade Federal de Santa Catarina
--
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] dts to dtb generation
Hello, all. I need to get my device-tree blob done, in order to pass it along with the image I've created (bootm command). I'm kind of new on the dtb concept and I'm not sure if I'm doing it right. Have read some stuff about it, though. What I got is that I have to generate a .dtb out of this source file (lite5200b.dts). But I can't get my dtc to work. I've downloaded the latest version (http://jdl.com/software/dtc-latest.tgz) and done the make command, but it points some errors during building. Check the snippet: ... BISON dtc-parser.tab.c DEP dtc-parser.tab.c LEX dtc-lexer.lex.c make: flex: Command not found DEP checks.c DEP srcpos.c DEP treesource.c DEP livetree.c DEP data.c DEP fstree.c DEP flattree.c DEP dtc.c LEX dtc-lexer.lex.c make: flex: Command not found CHK version_gen.h UPD version_gen.h DEP dtc.c LEX dtc-lexer.lex.c make: flex: Command not found CHK version_gen.h CC dtc.o ... And after the 'make install' command it reports the same 'flex: Command not found': LEX dtc-lexer.lex.c make: flex: Command not found CHK version_gen.h I've visited the http://www.embeddedlinuxprimer.com/dtc for the howto steps. Well, I guess it didn't complete the install, the console bashes the dtc as 'not found'. I'm aware there must be some small detail I must be missing in order to get it right, but I'd really appreciate a pointer here. Thanks for the attention. Marco Antônio Possamai Universidade Federal de Santa Catarina P.S: I'm also aware this is possibly not the right mailing list to ask about device-tree compilers... but I haven't found one specific for it. Sorry for the inconvenience. -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
