2011-08-01 03:58:27     ucLinux kernel bootup stalls on BF526 custom board

2011-08-01 03:58:27     ucLinux kernel bootup stalls on BF526 custom board

Swarnamala Sankaranarayanan (INDIA)

Message: 102743   

Hi,

I am loading the uImage through UARTand trying to boot kernel with bootm command. I get the following response:

---------------------------------------------------------

bfin> loady

## Ready for binary (ymodem) download to 0x01000000 at 57600 bps...                                                 

C## Total Size      = 0x003f2234 = 4137524 Bytes

bfin> bootm

## Booting kernel from Legacy Image at 01000000 ...

   Image Name:   bf527-2.6.34.7-ADI-2010R1

   Created:      2010-11-29   9:28:19 UTC

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    4137460 Bytes = 3.9 MiB

   Load Address: 00001000

   Entry Point:  001f46bc

   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

Starting Kernel at = 001f46bc

-----------------------------------------------------------

There is no further boot progress message. Display hangs after this message. Pl. suggest possible cause.

Thanks

Mala

QuoteReplyEditDelete

2011-08-01 06:12:11     Re: ucLinux kernel bootup stalls on BF526 custom board

Aaron Wu (CHINA)

Message: 102747   

Your kernel does not run properly on this board, either because something is wrong with the kernel itself or the bootargs are not correct, you may check your bootargs to see if proper serial port and baudrate are given out.

QuoteReplyEditDelete

2011-08-02 02:27:07     Re: ucLinux kernel bootup stalls on BF526 custom board

Swarnamala Sankaranarayanan (INDIA)

Message: 102759   

Aaron,

Yes bootargs seems to be okay. Here is the environment setting fro "bootargs"

bootargs=root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console=ttyBF0,57600

To create image I am using bf526 ezbrd configs as reference. The custom kit varies from the BF526 Ezbrd in following:

SDRAM - 32 MB not 64,

Flash - spi not pARA

Phy chip is RTM8201 (MII) not RMII

I have configured these in uboot board configuration.

-mala

QuoteReplyEditDelete

2011-08-02 02:55:03     Re: ucLinux kernel bootup stalls on BF526 custom board

Aaron Wu (CHINA)

Message: 102761   

You may want to doulbe check your u-boot environment settings, especially the console according to your actual customer board design, maybe you can try ttyBF1.  Here is my env values for a BF548 board for ram boot:

bfin> print

addip=set bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:off

autoload=no

baudrate=57600

bootargs=root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF1,57600

bootcmd=run ramboot

bootdelay=5

dnsip=10.99.27.40

ethact=smc911x-0

flashboot=bootm 0x20100000

gatewayip=10.99.22.1

hostname=bf548-ezkit

ipaddr=10.99.22.116

loadaddr=0x1000000

loads_echo=1

nandargs=set bootargs root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF1,57600

nandboot=nand read $(loadaddr) 0x20000 0x100000;run nandargs;bootm

netmask=255.255.255.0

nfsargs=set bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath),tcp,nfsvers=3

nfsboot=tftp $(loadaddr) $(nfsfile);run nfsargs;run addip;bootm

nfsfile=vmImage

ramargs=set bootargs root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF1,57600

ramboot=tftp $(loadaddr) $(ramfile);run ramargs;run addip;bootm

ramfile=uImage

rootpath=/romfs

serverip=192.168.0.2

stderr=serial

stdin=serial

stdout=serial

ubootfile=u-boot.ldr

update=tftp $(loadaddr) $(ubootfile);protect off 0x20000000 +$(filesize);erase 0x20000000 +$(filesize);cp.b $(loadaddr) 0x20000000 $(filesize)

QuoteReplyEditDelete

2011-08-04 10:09:45     Re: ucLinux kernel bootup stalls on BF526 custom board

Swarnamala Sankaranarayanan (INDIA)

Message: 102815   

Thanks Aaron.

Kernel booting also got resolved on the cutom BF526 kit. The problem wasn't with the configured console as UART0 and environment variables close to yours set for BF548. . The board specific configuration under verdor/board was for BF526ezbrd . some of the features like para flash, RTC not supported in custom board. After I updated the file with board specific changes, Kernel bootup from RAM tested Okay. I should'nt have overlooked this step. I appologise for the same.

Thanks

Mala

QuoteReplyEditDelete