kernel do not boot after enabled virtual terminal

Go To Last Post
2 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello,

i use a ngw100. After enabling virtual terminal in linux26-menuconfig the generated kernel image don't start.
The system get its kernel via tftp and the filesystem via nfs.

Uboot> printenv
bootdelay=1
baudrate=115200
ethaddr=00:04:25:1C:87:F2
hostname=ngwb1
ethact=macb0
eth1addr=00:04:25:1C:87:F3
filesize=12AECB
fileaddr=10200000
serverip=192.168.5.245
tftpserver=192.168.5.245
ipaddr=192.168.5.246
bootcmd=set ipaddr 192.168.5.246;tftp 0x10200000 uImage;bootm
bootargs=root=/dev/nfs ip=dhcp nfsroot=192.168.5.245:/home/lumax/nfs console=ttyS0
stdin=serial
stdout=serial
stderr=serial

Environment size: 398/65532 bytes
Uboot> 

The kernel print the following again and again:

U-Boot 1.3.2 (Sep 16 2008 - 10:57:47) 

U-Boot code: 00000000 -> 00010a80  data: 00016a18 -> 0004d128
SDRAM: 32 MB at address 0x10000000
Testing SDRAM...OK
malloc: Using memory from 0x11f72000 to 0x11fb2000
DMA: Using memory from 0x11f6e000 to 0x11f72000
Flash:  8 MB at address 0x00000000
DRAM Configuration:
Bank #0: 10000000 32 MB
In:    serial
Out:   serial
Err:   serial
Net:   macb0, macb1
Press SPACE to abort autoboot in 1 seconds
macb0: link up, 100Mbps full-duplex (lpa: 0x45e1)
Using macb0 device
TFTP from server 192.168.5.245; our IP address is 192.168.5.246
Filename 'uImage'.
Load address: 0x10200000
Loading: #################################################################
         ######################
done
Bytes transferred = 1264795 (134c9b hex)
## Booting image at 10200000 ...
   Image Name:   Linux-2.6.25.10.atmel.2
   Image Type:   AVR32 Linux Kernel Image (gzip compressed)
   Data Size:    1264731 Bytes =  1.2 MB
   Load Address: 10000000
   Entry Point:  90000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel at 00000000 (params at 11f72008)...

A kernel with the same settings like above but without the virtual terminal starts normal:

U-Boot code: 00000000 -> 00010a80  data: 00016a18 -> 0004d128
SDRAM: 32 MB at address 0x10000000
Testing SDRAM...OK
malloc: Using memory from 0x11f72000 to 0x11fb2000
DMA: Using memory from 0x11f6e000 to 0x11f72000
Flash:  8 MB at address 0x00000000
DRAM Configuration:
Bank #0: 10000000 32 MB
In:    serial
Out:   serial
Err:   serial
Net:   macb0, macb1
Press SPACE to abort autoboot in 1 seconds
macb0: Starting autonegotiation...
macb0: Autonegotiation complete
macb0: link up, 100Mbps full-duplex (lpa: 0x45e1)
Using macb0 device
TFTP from server 192.168.5.245; our IP address is 192.168.5.246
Filename 'uImage'.
Load address: 0x10200000
Loading: #################################################################
         ###################
done
Bytes transferred = 1232979 (12d053 hex)
## Booting image at 10200000 ...
   Image Name:   Linux-2.6.25.10.atmel.2
   Image Type:   AVR32 Linux Kernel Image (gzip compressed)
   Data Size:    1232915 Bytes =  1.2 MB
   Load Address: 10000000
   Entry Point:  90000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel at 90000000 (params at 11f72008)...

Is the Image too big?
Why is the first one starting at 00000000 and the
working one at 90000000 ?

Thank you very much.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Because you load the compressed kernel to 0x10200000, known misconfigured bootloader environment. Change the load address to 0x10400000.

Hans-Christian