ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Ltib] Ltib - Unable to open an initial console


From: VINAY.G
Subject: RE: [Ltib] Ltib - Unable to open an initial console
Date: Thu, 29 Apr 2010 12:55:56 +0530

Dear  all,

 

On issue may be that, the setting of the kernel command line……

 

Second may be , v can check the File system of the image before loading on to the board, to do this: in the build a directory called rootfs.tmp check here weather all the drivers n build n devices are build in this directory, if u coul’t find the device here then it wont be in the image.

 

Also check ur rc script

 

Third, erase the memory fully, cross check by reading back the contents.

 

Thanks and Regards

 

Vinay.G

 

 

 

From: address@hidden [mailto:address@hidden On Behalf Of Li Yuan-Lung
Sent: Thursday, April 29, 2010 11:43 AM
To: Kevin Wells
Cc: address@hidden
Subject: Re: [Ltib] Ltib - Unable to open an initial console

 

Dear Kevin,

I have similar problem. Below is the situation:

1. I have ltib image build in early March.(old-uImage, old-rootfs, old-uboot.bin)

2. This week I built a new image from ltib(new-uImage, new-rootfs, new-uboot.bin)

The boot parameter is the same as below:

"console=ttyS0,115200n81 root=/dev/mtdblock3 rw rootfstype=jffs2 init=/sbin/init"

 

The symptom is, after uboot uncompress the linux kernel, I lose my console forever. So I take some combination test as below:

 

(1)new-uboot.bin  (133KB)

     new-uImage-->new-rootfs   (X, not work)

     old-uImage-->old-rootfs      (X, not work)

     new-uImage-->oldrootfs     (X, not work)

     old-uImage-->oldrootfs        (X, not work)

(2)old-uboot.bin (144KB)

     new-uImage-->new-rootfs   (O, work!)

     old-uImage-->old-rootfs      (O, work!)

 

The "not work" condition is the same as the symptom.

 

My conclusion is that maybe there is some modification in u-boot source to affect the boot parameter pass to kernel. But I haven't check that yet. Do you have any comment?

 

Henry

2010/4/29 Kevin Wells <address@hidden>

Hi Peter,

Can you paste the output of the kernel with the error and the cmdline
so we can see what's happening?

thanks,
Kevin



> -----Original Message-----
> From: ltib-bounces+kevin.wells=nxp.com@nongnu.org [mailto:ltib-
> bounces+kevin.wells=nxp.com@nongnu.org] On Behalf Of Stuart Hughes
> Sent: Wednesday, April 28, 2010 12:42 AM
> To: Péter
> Cc: address@hidden
> Subject: Re: [Ltib] Ltib - Unable to open an initial console
>
> Hi Peter,
>
> Make sure you have a /dev/console on your target filesystem similar to
> (i.e 5,1):
>
> crw------- 1 root root 5, 1 2010-04-03 11:38 /dev/console
>
> Make sure you pass (or have as a default) some console device in the
> kernel boot arguments, e.g for the first serial port:
>
> console=/dev/ttyS0
>
> There are many more possibilities, but presumably that BSP should work
> in the default configuration? maybe someone with that board can confirm
> this.
>
> Regards, Stuart
>
> Péter wrote:
> > Hi all,
> >
> > I need some help. I have a NXP board with LH7a404 processor.
> > I build the kernel and root file system. After im booting the kernel,
> always I have
> > a warning message.WARNING: Unable to open an initial console.
> >
> > I looked for any help in web but I dont find the good solution.
> >
> > The kernel is running! I can do all command in etc/inittab. (for
> example:
> > ::sysinit:/bin/ls > example.txt)But I cant runnig my programs (for
> example:
> > hello.out <- this program must create a
> > file and write to the file Hello world!)
> > Can anybody help me? :(
> >
> > Péter
> >
>
>
> _______________________________________________
> LTIB home page: http://ltib.org
>
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib


_______________________________________________
LTIB home page: http://ltib.org

Ltib mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/ltib




--
Best Regards,

Henry Li
SW Engineer of Climax Co.
TEL: +886-2-2794-0001 ext.231
FAX: +886-2-2792-6618


reply via email to

[Prev in Thread] Current Thread [Next in Thread]