Skip to contentSkip to conversation

Why my image isn't boot?

U-Boot-Users richard at uclinux.net 3 participants 7 messages Apr 8, 2003 – Apr 9, 2003 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 00c601c2fe49$d82ab360$fe02a8c0@esd11

richard at uclinux.net

author
#1 lore raw
Quoted 4 lines

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

Quoted 23 lines

----- Original Message -----
From: <[email protected]>
To: "Zhao Hongda" <[email protected]>
Sent: Tuesday, April 08, 2003 5:23 AM
Subject: Re: [U-Boot-Users] Why my image isn't boot?

Quoted 5 lines
Quoted 5 lines

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 vmlinux

linux.bin

Quoted 2 lines
Quoted 2 lines

gzip -9 linux.bin
mkimage -A arm -O linux -T kernel -C gzip -a 0xa0008000 -e

0xa0008000 -n

Quoted 7 lines
Quoted 7 lines

"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>
#2 lore raw

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: <[email protected]>
To: <[email protected]>
Sent: Tuesday, April 08, 2003 5:44 AM
Subject: Re: [U-Boot-Users] Why my image isn't boot?

Quoted 1 line
Quoted 1 line

I want it run from flash, but if I use "loadb 0x00100000", after

transfer

Quoted 48 lines
Quoted 3 lines

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

Quoted 11 lines

----- Original Message -----
From: <[email protected]>
To: "Zhao Hongda" <[email protected]>
Sent: Tuesday, April 08, 2003 5:23 AM
Subject: Re: [U-Boot-Users] Why my image isn't boot?

Quoted 4 lines
Quoted 4 lines

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.

Quoted 12 lines
Quoted 1 line
Quoted 1 line

arm-linux-objcopy -O binary -R .note -R .comment -S vmlinux

linux.bin

Quoted 2 lines
Quoted 2 lines

gzip -9 linux.bin
mkimage -A arm -O linux -T kernel -C gzip -a 0xa0008000 -e

0xa0008000 -n

Quoted 7 lines
Quoted 7 lines

"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 at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users

author
#3 lore raw
Quoted 6 lines

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

Load an uncompressed linux image instead (o;

Rick

#4 lore raw

do you mean that vmlinux?it is too large:(
please give me a sample setp you take to product a workable kernel and load it.
thanks.
Hongda Zhao
----- Original Message -----
From: <[email protected]>
To: <[email protected]>
Sent: Tuesday, April 08, 2003 6:06 AM
Subject: Re: [U-Boot-Users] Why my image isn't boot?

Quoted 1 line
Quoted 1 line

I just want to boot the linux kernel in lubbock, and follow the README

file

Quoted 5 lines
Quoted 5 lines

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

Quoted 17 lines

Load an uncompressed linux image instead (o;

Rick

-------------------------------------------------------
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 at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users

A message that is not in the archive (sent off-list or not yet received): [email protected]

#6 lore raw

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" <[email protected]>
To: "Zhao Hongda" <[email protected]>
Sent: Tuesday, April 08, 2003 6:47 AM
Subject: Re: [U-Boot-Users] Why my image isn't boot?

Quoted 8 lines

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 \

Quoted 11 lines

-d linux.gz linuxgz.image

linuxgz.image is a valid u-boot kernel image and should boot with

=> bootm address_where_loaded

Kyle.

Quoted 1 line · Zhao Hongda

I just want to boot the linux kernel in lubbock, and follow the README

file

Quoted 5 lines
Quoted 5 lines

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

Quoted 11 lines
Quoted 11 lines

Zhao
----- Original Message -----
From: <[email protected]>
To: <[email protected]>
Sent: Tuesday, April 08, 2003 5:44 AM
Subject: Re: [U-Boot-Users] Why my image isn't boot?

Quoted 1 line
Quoted 1 line

I want it run from flash, but if I use "loadb 0x00100000", after

transfer

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 3 lines

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?

Quoted 50 lines
Quoted 50 lines
Quoted 31 lines

It also won't work if you want to run it directly from flash either...

Rick

Quoted 10 lines

----- Original Message -----
From: <[email protected]>
To: "Zhao Hongda" <[email protected]>
Sent: Tuesday, April 08, 2003 5:23 AM
Subject: Re: [U-Boot-Users] Why my image isn't boot?

Quoted 4 lines
Quoted 4 lines

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.

Quoted 15 lines
Quoted 1 line
Quoted 1 line

arm-linux-objcopy -O binary -R .note -R .comment -S vmlinux

linux.bin

Quoted 2 lines
Quoted 2 lines

gzip -9 linux.bin
mkimage -A arm -O linux -T kernel -C gzip -a 0xa0008000 -e

0xa0008000 -n

Quoted 6 lines
Quoted 6 lines

"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>
Quoted 9 lines

-------------------------------------------------------
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 at 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 at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users

#7 lore raw
Quoted 12 lines · 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
Quoted 8 lines

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

Signature · 4 lines
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
What about WRITING it first and rationalizing it afterwords?  :-)
                       - Larry Wall in <[email protected]>
#8 lore raw

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" <[email protected]>
To: "Zhao Hongda" <[email protected]>
Cc: "Kyle Harris" <[email protected]>; <[email protected]>
Sent: Wednesday, April 09, 2003 1:00 AM
Subject: Re: [U-Boot-Users] Why my image isn't boot?

Quoted 35 lines
Quoted 12 lines · 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
Quoted 8 lines

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 at denx.de What about WRITING it first and rationalizing it afterwords? :-)
- Larry Wall in <[email protected]>