[U-Boot-Users] Linux kernel startup

[U-Boot-Users] Linux kernel startup

[Tiju]

Hi all,

After uboot comes up, I get stuck with the booting of linux kernel. The RAM range is from 0x30000000-0x38000000. Following are the steps I do to get the uImage.bin.

$ arm-linux-objcopy -O binary -R .note -R ..comment -S vmlinux linux.bin
$ gzip -9 linux.bin
$ ../u-boot-1.3.2/tools/mkimage -A arm -O linux -T kernel -C gzip -a 0x30008000 -e 0x30008000 -n "Linux kernel" -d linux.bin.gz uImage.bin
Image Name:   Linux kernel
Created:      Sun Apr  6 12:19:12 2008
Image Type:   ARM Linux Kernel Image (gzip compressed)
Data Size:    4271627 Bytes = 4171.51 kB = 4.07 MB
Load Address: 0x30008000
Entry Point:  0x30008000

After this I put the uImage.bin at 0x33000000, restart uboot and I get:

U-Boot 1.3.2 (Apr  6 2008 - 12:03:10)

DRAM:  128 MB
Flash: 32 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
## Booting image at 33000000 ...
   Image Name:   Linux kernel
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    4271627 Bytes =  4.1 MB
   Load Address: 30008000
   Entry Point:  30008000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

undefined instruction
pc : [<30808004>]          lr : [<3101175c>]
sp : 30fcfaf8  ip : 30fcffb8     fp : 00000000
r10: 00000001  r9 : 30fcfe98     r8 : 30fcffdc
r7 : cf032d24  r6 : 33000040     r5 : 31019544  r4 : 31019541
r3 : 30fcfe55  r2 : 30000100     r1 : 0000016a  r0 : 00000000
Flags: nzCv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...

data abort
pc : [<31010ca8>]          lr : [<31010d40>]
sp : 30fcfa88  ip : 3101b06c     fp : 00000000
r10: 00000001  r9 : 30fcfe98     r8 : 30fcffdc
r7 : cf032d24  r6 : 33000040     r5 : 00658d7f  r4 : 00036042
r3 : 3101b070  r2 : 0000566d     r1 : 00003307  r0 : 000032ff
Flags: nzCv  IRQs on  FIQs on  Mode SVC_32
Resetting CPU ...

data abort
pc : [<31010ca8>]          lr : [<31010cf4>]
sp : 30fcfa10  ip : ffffffff     fp : 00000000
r10: 00000001  r9 : 30fcfe98     r8 : 30fcffdc
r7 : cf032d24  r6 : 33000040     r5 : 30fcfa74  r4 : 00000000
r3 : 3101b070  r2 : 30fcfa30     r1 : 00003307  r0 : 00003200
Flags: nzCv  IRQs on  FIQs on  Mode SVC_32
Resetting CPU ...

And it keeps on resetting the CPU.

Is it the problem with the settings of uboot or the kernel and what should I do to bring the linux kernel up? Where could I find more information regarding this?

Kindly help me out.

Thanks in advance.
Tiju




      Share files, take polls, and make new friends - all under one roof. Go to http://in.promos.yahoo.com/groups/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20080406/0367c8fa/attachment.htm 

[U-Boot-Users] Linux kernel startup

[Tiju]

Hi all,

Afteruboot comes up, I get stuck with the booting of linux kernel. The RAMrange is from 0x30000000-0x38000000. Following are the steps I do toget the uImage.bin.

$ arm-linux-objcopy -O binary -R .note -R .comment -S vmlinux linux.bin
$ gzip -9 linux.bin
$../u-boot-1.3.2/tools/mkimage -A arm -O linux -T kernel -C gzip -a0x30008000 -e 0x30008000 -n "Linux kernel" -d linux.bin.gz uImage.bin
Image Name:   Linux kernel
Created:      Sun Apr  6 12:19:12 2008
Image Type:   ARM Linux Kernel Image (gzip compressed)
Data Size:    4271627 Bytes = 4171.51 kB = 4.07 MB
Load Address: 0x30008000
Entry Point:  0x30008000

After this I put the uImage.bin at 0x33000000, restart uboot and I get:
U-Boot 1.3.2 (Apr  6 2008 - 12:03:10)

DRAM:  128 MB
Flash: 32 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
## Booting image at 33000000 ...
   Image Name:   Linux kernel
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    4271627 Bytes =  4.1 MB
   Load Address: 30008000
   Entry Point:  30008000
   Verifying Checksum ... Bad Data CRC
DPB2440 #

Isit the problem with the settings of uboot or the kernel and what shouldI do to bring the linux kernel up? Where could I find more informationregarding this?

Kindly help me out.

Thanks in advance.
Tiju







      Share files, take polls, and make new friends - all under one roof. Go to http://in.promos.yahoo.com/groups/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20080406/9c8b3e43/attachment.htm 

[U-Boot-Users] Linux kernel startup

[Leon Woestenberg]

Hello,

On Sun, Apr 6, 2008 at 11:03 AM, Tiju <tj_jac@yahoo.co.in> wrote:

We have seen both illegal instructions and crc errors for kernel > 4
MB on PowerPC.

I have to reproduce this, but we suspect the 4 MB boundary. This was
for an old u-boot.

Regards,
-- 
Leon

[U-Boot-Users] Linux kernel startup

[Tiju]

Hi Leon,

> We have seen both illegal instructions and crc errors for kernel > 4
> MB on PowerPC.

Even when the kernel size is 1.09 MB the same BAD CRC error occurs.
Is it the error with the kernel  or the uboot itself. If so what could be the problem?
Output is as follows.

U-Boot 1.3.2 (Apr  7 2008 - 11:05:53)

DRAM:  128 MB
Flash: 32 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
## Booting image at 33000000 ...
   Image Name:   Linux kernel
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    1141366 Bytes =  1.1 MB
   Load Address: 30008000
   Entry Point:  30008000
   Verifying Checksum ... Bad Data CRC


Any help will be appreciated.

Thanks in advance.
Tiju






      Share files, take polls, and make new friends - all under one roof. Go to http://in.promos.yahoo.com/groups/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20080407/2dcfea51/attachment.htm 

[U-Boot-Users] Linux kernel startup

[Tiju]

Hi Harald,

The serial issues were solved. As u said, the problem was with the RTS/CTS. I disabled all the hardware control signals and some modifications with the relocation section in the start.S and it started working.

Now the issue is with the kernel CRC32 check. I compiled a kernel with the smdk2440 architecture and I do the following.

$ arm-linux-objcopy -O binary -R .note -R .comment -S vmlinux linux.bin
$ gzip -9 linux.bin
$../u-boot-1.3.2/tools/mkimage -A arm -O linux -T kernel -C gzip -a0x30008000 -e 0x30008000 -n "Linux kernel" -d linux.bin.gz uImage.bin

The size of vmlinux is around 25MB. When converted to linux.bin it is 3GB, when gziped it is around 4MB and when done an mkimage it remains almost the same..

The output is as follows:

U-Boot 1.3.2 (Apr  7 2008 - 12:14:29)

DRAM:  128 MB
Flash: 32 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
## Booting image at 33000000 ...
   Image Name:   Linux kernel
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    4271633 Bytes =  4.1 MB
   Load Address: 30008000
   Entry Point:  30008000
   Verifying Checksum ... Bad Data CRC

What ever kernel image I load it tells the same ie. "Verifying Checksum ... Bad Data CRC". I even tried the uImage.bin which was available on openmoko site and the same error occurs.

Is the error with the bootloader or the kernel image? If so what are the changes to be done?

Thanks in advance.
Tiju




      Messenger blocked? Want to chat? Go to http://in.messenger.yahoo.com/webmessengerpromo.php
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20080407/a2630758/attachment.htm 

[U-Boot-Users] Linux kernel startup

[Harald Welte]

On Mon, Apr 07, 2008 at 02:31:10PM +0530, Tiju wrote:
> Hi Harald,
> 
> The serial issues were solved. As u said, the problem was with the
> RTS/CTS. I disabled all the hardware control signals and some
> modifications with the relocation section in the start.S and it
> started working.

great.

> Now the issue is with the kernel CRC32 check. I compiled a kernel with
> the smdk2440 architecture and I do the following.

Please see my other e-mail response about this.  I still believe there
might be some wrong memory / bus / core clock timing and or voltage
issues.  please try to use u-boot's built-in memory verification code to
veryify your memory before trying to boot a kernel on it.

What basically happens is that u-boot copies your kernel image from
storage medium to SDRAM, and then tries to checksum it.  If the original
image is correct, and the copy in SDRAM isn't, this means that you
somehow have memory corruption.

Is the hardware a prototype of a new board, or is it proven, verified
hardware?  If it's a new board, there can be dozens of different reasons
why the PLL might run instable, the power lines have too much noise,
etc.

Even if it's verified hardware, the particular PLL speed for memory or
CPU clock used by your u-boot image might not be within whatever your
hardware configuration supports.

So I would reconfigure all memory timings to their most conservative
(slowest) setting, and run the bus at 25 or 50MHz, the CPU core at
100MHz and re-try.  If the memory check and/or system boot works this
way, you can try to increase the timings incrementally up to your
desired configuration.

-- 
- Harald Welte <laforge@gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20080407/2a486379/attachment.pgp 

[U-Boot-Users] Linux kernel startup

[Jerry Van Baren]

Tiju wrote:
> Hi Harald,
> 
> The serial issues were solved. As u said, the problem was with the 
> RTS/CTS. I disabled all the hardware control signals and some 
> modifications with the relocation section in the start..S and it started 
> working.
> 
> Now the issue is with the kernel CRC32 check. I compiled a kernel with 
> the smdk2440 architecture and I do the following.
> 
> $ arm-linux-objcopy -O binary -R .note -R .comment -S vmlinux linux.bin
> $ gzip -9 linux.bin
> $ ../u-boot-1.3.2/tools/mkimage -A arm -O linux -T kernel -C gzip -a 
> 0x30008000 -e 0x30008000 -n "Linux kernel" -d linux.bin.gz uImage.bin
> 
> The size of vmlinux is around 25MB. When converted to linux.bin it is 
> 3GB, when gziped it is around 4MB and when done an mkimage it remains 
> almost the same.

This is indicating you have major link / memory map / coding issue(s). 
vmlinux should be around 1MB, not 25MB!  linux.bin should be around the 
same size as vmlinux.  Having linux.bin grow to be 3GB indicates it has 
major holes in it that objdump is filling with "fill" values.

Loading a 3GB image (compressed to 4MB or not) is simply not going to work.

Use objdump to dump the section headers of the elf file (vmlinux) to see 
what addresses are being used and sizes of the sections.  Figure out why 
it is producing pieces of code/data in widely varying address locations 
and possibly large sections of "bad" stuff.  Until you fix your link, 
you aren't going to have any success loading it.

Good luck,
gvb

[U-Boot-Users] Linux kernel startup

[Tiju]

Hi Jerry,

>This is indicating you have major link / memory map / coding issue(s). 
>vmlinux should be around 1MB, not 25MB!  linux.bin should be around the 
>same size as vmlinux.  Having linux.bin grow to be 3GB indicates it has 
>major holes in it that objdump is filling with "fill" values.

Loading a 3GB image (compressed to 4MB or not) is simply not going to work.

I will look into the kernel sections and try to figure it out. It maybe the problem with my compiler.

But my other major problem is that, what ever be the size of the kernel, it gives me a "Bad Data CRC". I tried with prebuild images from the openmoko (which are working images on openmoko 1.5MB) and still it shows me the same error. We have almost the same architecture as theirs. 

Does this have to do anything with the u-boot or some other issue?

Thank You,
Tiju.




      Meet people who discuss and share your passions. Go to http://in.promos.yahoo.com/groups/bestofyahoo/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20080407/13e4a67f/attachment.htm 

[U-Boot-Users] Linux kernel startup

[Tiju]

Hi Harald,

>Please see my other e-mail response about this.  I still believe there
>might be some wrong memory / bus / core clock timing and or voltage
>issues.  

We changed the memory clock to a lower frequency(90MHz to 67MHz) and the the "Bad Data CRC" error has gone. Thanks alot.
Our settings are: EXTCLK = 12MHz
                                  FCLK = 271 MHz
                                  HCLK = 67.75 MHz

>please try to use u-boot's built-in memory verification code to
>veryify your memory before trying to boot a kernel on it.
We will do this now.

We are writing the kernel image directly to the ram to 33000000. Therefore as for now it is not copied from the flash.

>Is the hardware a prototype of a new board, or is it proven, verified
>hardware? 
Yes, the hardware is a new prototype.

The output now is as follows:

U-Boot 1..3.2 (Apr  7 2008 - 17:25:31)

DRAM:  128 MB
Flash: 32 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
## Booting image at 33000000 ...
   Image Name:   Linux kernel
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    4278410 Bytes =  4.1 MB
   Load Address: 30008000
   Entry Point:  30008000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

undefined instruction
pc : [<30008018>]          lr : [<310117bc>]
sp : 30fcfa78  ip : 30fcffb8     fp : 00000000
r10: 00000001  r9 : 30fcfe18     r8 : 30fcffdc
r7 : 31012ef4  r6 : 33000040     r5 : 31019514  r4 : 31019511
r3 : 30008000  r2 : 30000100     r1 : 0000016a  r0 : 00000000
Flags: nzCv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...


U-Boot 1.3.2 (Apr  7 2008 - 17:25:31)

DRAM:  128 MB
Flash: 32 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
## Booting image at 33000000 ...
   Image Name:   Linux kernel
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    4278410 Bytes =  4.1 MB
   Load Address: 30008000
   Entry Point:  30008000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

undefined instruction
pc : [<30008018>]          lr : [<310117bc>]
sp : 30fcfa78  ip : 30fcffb8     fp : 00000000
r10: 00000001  r9 : 30fcfe18     r8 : 30fcffdc
r7 : 31012ef4  r6 : 33000040     r5 : 31019514  r4 : 31019511
r3 : 30008000  r2 : 30000100     r1 : 0000016a  r0 : 00000000
Flags: nzCv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...

and it keeps on resetting. We further reduced the SDRAM frequency to 45 Mhz, but still the problem persist. Is it still the problem with the u-boot frequency or with the linux kernel?

Thanks again.
Tiju






      Save all your chat conversations.. Find them online at http://in.messenger.yahoo.com/webmessengerpromo.php
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20080407/bff87b70/attachment.htm