Re: [U-Boot-Users] Why my image isn't boot?
Thanks for your help, But when I follow your step, after bootm, u-boot complain that :
=> loadb 0xa0008000 ## Ready for binary (kermit) download to 0xA0008000 at 115200 bps... ## Total Size = 0x000c14aa = 791722 Bytes ## Start Addr = 0xA0008000 => bootm 0xa0008000 ## Booting image at a0008000 ... Image Name: U-boot Linux Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 791658 Bytes = 773.1 kB Load Address: a0008000 Entry Point: a0008000 Verifying Checksum ... OK Uncompressing Kernel Image ... Error: inflate() returned -3 GUNZIP ERROR - must RESET board to recover reseting ...
what should I do? Hongda Zhao ----- Original Message ----- From: "Kyle Harris" kharris@nexus-tech.net To: "Zhao Hongda" zhaohd@vis.cs.tsinghua.edu.cn Sent: Tuesday, April 08, 2003 6:47 AM Subject: Re: [U-Boot-Users] Why my image isn't boot?
Zhao,
This is my procedure. Hope this works for you.
$ make zImage $ arm-linux-objcopy -S -O binary vmlinux linux $ gzip -vf9 linux $ mkimage -n name -A arm -O linux -T kernel -C gzip -a a0008000 -e
a0008000 \
-d linux.gz linuxgz.imagelinuxgz.image is a valid u-boot kernel image and should boot with
=> bootm address_where_loaded
Kyle.
On Wednesday 09 April 2003 12:05 am, Zhao Hongda wrote:
I just want to boot the linux kernel in lubbock, and follow the README
file
in u-boot, then what steps should I take to product a workable uImage file ? and how to load it correctly? please give me a sample procedure.
Hongda
Zhao ----- Original Message ----- From: richard@uclinux.net To: u-boot-users@lists.sourceforge.net Sent: Tuesday, April 08, 2003 5:44 AM Subject: Re: [U-Boot-Users] Why my image isn't boot?
I want it run from flash, but if I use "loadb 0x00100000", after
transfer
the uImage, "md 0x00100000" shows that flash data is wrong, what should I do? Hongda Zhao
My question was:
Why are you trying to directly execute a compressed linux image from
RAM?
It also won't work if you want to run it directly from flash either...
Rick
----- Original Message ----- From: richard@uclinux.net To: "Zhao Hongda" zhaohongda@tsinghua.org.cn Sent: Tuesday, April 08, 2003 5:23 AM Subject: Re: [U-Boot-Users] Why my image isn't boot?
I use the u-boot cvs source, linux-2.4.19 kernel, arm-linux patch, and xscale patch. arm-linux-gcc 3.0 as complier,lubbock(pxa250) as platform.
arm-linux-objcopy -O binary -R .note -R .comment -S vmlinuxlinux.bin
gzip -9 linux.bin mkimage -A arm -O linux -T kernel -C gzip -a 0xa0008000 -e0xa0008000 -n
"Linux Kernel Image" -d linux.bin.gz uImage then under u-boot: =>loadb 0xa0008000 (send the uImage) =>go 0xa0008000 start the application at 0xa0008000 <hang>
This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
In message 014901c2feb4$185ece70$fe02a8c0@esd11 you wrote:
Thanks for your help, But when I follow your step, after bootm, u-boot complain that :
=> loadb 0xa0008000 ## Ready for binary (kermit) download to 0xA0008000 at 115200 bps... ## Total Size = 0x000c14aa = 791722 Bytes ## Start Addr = 0xA0008000 => bootm 0xa0008000 ## Booting image at a0008000 ... Image Name: U-boot Linux Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 791658 Bytes = 773.1 kB Load Address: a0008000 Entry Point: a0008000 Verifying Checksum ... OK Uncompressing Kernel Image ... Error: inflate() returned -3 GUNZIP ERROR - must RESET board to recover reseting ...
what should I do?
Fix your image. The addrress where it is stored in RAM (as used by " bootm 0xa0008000" must be different from the "Load Address: a0008000" and "Entry Point: a0008000" values, or it will overwerite itself when it gets uncompressed.
Wolfgang Denk
I follow these steps: $ make zImage $ arm-linux-objcopy -S -O binary vmlinux linux $ gzip -vf9 linux $ mkimage -n name -A arm -O linux -T kernel -C gzip -a a0008000 -e a0008000 -d linux.gz linuxgz.image
then load it follow these steps: =>loadb 0xa1000000 =>bootm 0xa1000000 ## Booting image at a1000000 ... Image Name: akzhd crazy Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 791658 Bytes = 773.1 kB Load Address: a0008000 Entry Point: a0008000 Verifying Checksum ... OK Uncompressing Kernel Image ... Error: inflateInit2() returned -4 GUNZIP ERROR - must RESET board to recover
please help me, thanks.
Hongda Zhao ----- Original Message ----- From: "Wolfgang Denk" wd@denx.de To: "Zhao Hongda" zhaohd@vis.cs.tsinghua.edu.cn Cc: "Kyle Harris" kharris@nexus-tech.net; u-boot-users@lists.sourceforge.net Sent: Wednesday, April 09, 2003 1:00 AM Subject: Re: [U-Boot-Users] Why my image isn't boot?
In message 014901c2feb4$185ece70$fe02a8c0@esd11 you wrote:
Thanks for your help, But when I follow your step, after bootm, u-boot complain that :
=> loadb 0xa0008000 ## Ready for binary (kermit) download to 0xA0008000 at 115200 bps... ## Total Size = 0x000c14aa = 791722 Bytes ## Start Addr = 0xA0008000 => bootm 0xa0008000 ## Booting image at a0008000 ... Image Name: U-boot Linux Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 791658 Bytes = 773.1 kB Load Address: a0008000 Entry Point: a0008000 Verifying Checksum ... OK Uncompressing Kernel Image ... Error: inflate() returned -3 GUNZIP ERROR - must RESET board to recover reseting ...
what should I do?
Fix your image. The addrress where it is stored in RAM (as used by " bootm 0xa0008000" must be different from the "Load Address: a0008000" and "Entry Point: a0008000" values, or it will overwerite itself when it gets uncompressed.
Wolfgang Denk
-- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de What about WRITING it first and rationalizing it afterwords? :-) - Larry Wall in 8162@jpl-devvax.JPL.NASA.GOV
participants (2)
-
Wolfgang Denk -
Zhao Hongda