[Howto] 2430 kernel,uboot and filesystem

[Howto] 2430 kernel,uboot and filesystem

[Nishanth Menon]

[-- Attachment #1: Type: text/plain, Size: 628 bytes --]

Hi All,
Looking through some of the queries happening in the list, I had been
playing around trying to use as little of the pre-build files as
possible to do a 2430 boot up from scratch.
In the process of this, I decided to document all the steps I had done..
attached is a txt and pdf version of the same. I hope it will be useful
to someone who is starting off on the board for the first time.

Most of the document was written with a sleepy eye, so please let me
know if you find any bugs or ways to improve the document (the txt
version is a generated file so it will lack the images of the pdf...).
Regards,
Nishanth Menon

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Help: OMAP5912 RS232 dies after kernel uncompressing.

[Juergen Sievers]

Hello. 

After I modified the environment by using setenv/saveenv I got the following
problem.

The terminal connected to the OMAP5912 rs232 at 115200n8 is working as long
as the kernel is uploaded and decompressing. The last message shown is
".booting."

After that message the rs232 line seems to be dead.

The kernel is mounting its root from nfs-server and is running normally
except the console device could be used.

I tried several kernels (2.6.16/2.6.19) including the pre-build kernel 2.4
from the distribution CD All the same, the rs232 line dies after
uncompressing the kernel.

My bootags setting are:

Bootargs = "mem=32 console=ttyS0,115200n8 ip=dhcp root=/dev/nfs rw
nfsroot=192.168.0.50:/nfsroot"

Has anybody an idea what I could do to get back my rs232 console ?

Regards

Juergen

RE: Help: OMAP5912 RS232 dies after kernel uncompressing.

[Abot Botbot]

Juergen,

  Perhaps your NFS Share isn't set up correctly? I had that problem before I 
had set up my NFS share with the right perms and whatnot. Maybe look into 
the particulars of the config file and make sure all is well. Try mounting 
the target NFS with another machine other than the board.

Hope this helps,
Andy

>From: "Juergen Sievers" <JSievers@nadine-software.com>
>Reply-To: JSievers@nadine-software.com
>To: "'Linux OMAP List'" <linux-omap-open-source@linux.omap.com>
>Subject: Help: OMAP5912 RS232 dies after kernel uncompressing.
>Date: Mon, 15 Jan 2007 16:22:26 +0100
>
>
>Hello.
>
>After I modified the environment by using setenv/saveenv I got the 
>following
>problem.
>
>The terminal connected to the OMAP5912 rs232 at 115200n8 is working as long
>as the kernel is uploaded and decompressing. The last message shown is
>".booting."
>
>After that message the rs232 line seems to be dead.
>
>The kernel is mounting its root from nfs-server and is running normally
>except the console device could be used.
>
>I tried several kernels (2.6.16/2.6.19) including the pre-build kernel 2.4
>from the distribution CD All the same, the rs232 line dies after
>uncompressing the kernel.
>
>My bootags setting are:
>
>Bootargs = "mem=32 console=ttyS0,115200n8 ip=dhcp root=/dev/nfs rw
>nfsroot=192.168.0.50:/nfsroot"
>
>Has anybody an idea what I could do to get back my rs232 console ?
>
>Regards
>
>Juergen
>
>
>_______________________________________________
>Linux-omap-open-source mailing list
>Linux-omap-open-source@linux.omap.com
>http://linux.omap.com/mailman/listinfo/linux-omap-open-source

_________________________________________________________________
Find sales, coupons, and free shipping, all in one place!  MSN Shopping 
Sales & Deals 
http://shopping.msn.com/content/shp/?ctid=198,ptnrid=176,ptnrdata=200639

AW: Help: OMAP5912 RS232 dies after kernel uncompressing.

[Juergen Sievers]

Hi Andy.


Hem unbelievable.

But the omap mounts its nfs-root and I can login on the omap by using telnet

So I can not understand how a wrong configured nfs-server might stop the
ttyS0 

Could it be that you did not read that the system boots completely or do I
not understand what you mean?

Mfg.
j.


-----Ursprüngliche Nachricht-----
Von: Abot Botbot [mailto:dejanigma@hotmail.com] 
Gesendet: Montag, 15. Januar 2007 16:53
An: JSievers@nadine-software.com; linux-omap-open-source@linux.omap.com
Betreff: RE: Help: OMAP5912 RS232 dies after kernel uncompressing.

Juergen,

  Perhaps your NFS Share isn't set up correctly? I had that problem before I

had set up my NFS share with the right perms and whatnot. Maybe look into 
the particulars of the config file and make sure all is well. Try mounting 
the target NFS with another machine other than the board.

Hope this helps,
Andy

>From: "Juergen Sievers" <JSievers@nadine-software.com>
>Reply-To: JSievers@nadine-software.com
>To: "'Linux OMAP List'" <linux-omap-open-source@linux.omap.com>
>Subject: Help: OMAP5912 RS232 dies after kernel uncompressing.
>Date: Mon, 15 Jan 2007 16:22:26 +0100
>
>
>Hello.
>
>After I modified the environment by using setenv/saveenv I got the 
>following
>problem.
>
>The terminal connected to the OMAP5912 rs232 at 115200n8 is working as long
>as the kernel is uploaded and decompressing. The last message shown is
>".booting."
>
>After that message the rs232 line seems to be dead.
>
>The kernel is mounting its root from nfs-server and is running normally
>except the console device could be used.
>
>I tried several kernels (2.6.16/2.6.19) including the pre-build kernel 2.4
>from the distribution CD All the same, the rs232 line dies after
>uncompressing the kernel.
>
>My bootags setting are:
>
>Bootargs = "mem=32 console=ttyS0,115200n8 ip=dhcp root=/dev/nfs rw
>nfsroot=192.168.0.50:/nfsroot"
>
>Has anybody an idea what I could do to get back my rs232 console ?
>
>Regards
>
>Juergen
>
>
>_______________________________________________
>Linux-omap-open-source mailing list
>Linux-omap-open-source@linux.omap.com
>http://linux.omap.com/mailman/listinfo/linux-omap-open-source

_________________________________________________________________
Find sales, coupons, and free shipping, all in one place!  MSN Shopping 
Sales & Deals 
http://shopping.msn.com/content/shp/?ctid=198,ptnrid=176,ptnrdata=200639

Re: AW: Help: OMAP5912 RS232 dies after kernel uncompressing.

[Nishanth Menon]

Juergen Sievers stated on 1/15/2007 2:50 PM:
> But the omap mounts its nfs-root and I can login on the omap by using telnet
>
> So I can not understand how a wrong configured nfs-server might stop the
> ttyS0 
>
>   
Opinion: check your /etc/inittab in the filesystem. maybe you have told
getty to hook on to the wrong terminal... some common issues is the
getty given wrong baud rate OR given tty0 while ttyS0 is being used
etc.. that is a nice place to check.. but do try this: give
"init=/bin/sh" along with ur boot options(given the rest of the
symptoms, this should work).. if u manage to boot off that.. u need to
look deep into ur boot sequence of filesystem -such as rc scripts etc if
you have any.

Regards,
Nishanth Menon

AW: AW: Help: OMAP5912 RS232 dies after kernel uncompressing.

[Juergen Sievers]

Hi Nishanth.

That is a good hint and I did this already but it was not the reason.

Normal, before the ttyS0 was missing, the kernel's initializing messages
were shown on the rs323 line. But now - nothing appears after the kernel
code gets control.

I will try to reset the whole environment block to create a new and well
formatted environment. It seems to me something is wrong on these persistent
environment settings. Possible I have typed in an invisible control
character in one of these settings.

Mfg.
Juergen


> Opinion: check your /etc/inittab in the filesystem. maybe you have told
> getty to hook on to the wrong terminal... some common issues is the
> getty given wrong baud rate OR given tty0 while ttyS0 is being used
> etc.. that is a nice place to check.. but do try this: give
> "init=/bin/sh" along with ur boot options(given the rest of the
> symptoms, this should work).. if u manage to boot off that.. u need to
> look deep into ur boot sequence of filesystem -such as rc scripts etc if
> you have any.
> 
> Regards,
> Nishanth Menon

Re: Help: OMAP5912 RS232 dies after kernel uncompressing.

[Liem Pham Tan]

hi Juergen,
please re-check that there is no gaps in the "console=ttyS0,115200n8". If you write "console=ttyS0,_115200n8", the rs232 connection seems to be dead.
BR,
Liem Pham


> Hello. 
>
> After I modified the environment by using setenv/saveenv I got the following
> problem.
>
> The terminal connected to the OMAP5912 rs232 at 115200n8 is working as long
> as the kernel is uploaded and decompressing. The last message shown is
> ".booting."
>
> After that message the rs232 line seems to be dead.
>
> The kernel is mounting its root from nfs-server and is running normally
> except the console device could be used.
>
> I tried several kernels (2.6.16/2.6.19) including the pre-build kernel 2.4
> from the distribution CD All the same, the rs232 line dies after
> uncompressing the kernel.
>
> My bootags setting are:
>
> Bootargs = "mem=32 console=ttyS0,115200n8 ip=dhcp root=/dev/nfs rw
> nfsroot=192.168.0.50:/nfsroot"
>
> Has anybody an idea what I could do to get back my rs232 console ?
>
> Regards
>
> Juergen
>
>
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>
>   

Re: [Howto] 2430 kernel,uboot and filesystem

[Dirk Behme]

Nishanth Menon wrote:
> Looking through some of the queries happening in the list, I had been
> playing around trying to use as little of the pre-build files as
> possible to do a 2430 boot up from scratch.
> In the process of this, I decided to document all the steps I had done..
> attached is a txt and pdf version of the same. I hope it will be useful
> to someone who is starting off on the board for the first time.
> 
> Most of the document was written with a sleepy eye, so please let me
> know if you find any bugs or ways to improve the document (the txt
> version is a generated file so it will lack the images of the pdf...).

Can sleepy eye check if attachments are really there? Or are 
my eyes too sleepy? ;)

Cheers

Dirk

Help: OMAP5912 RS232 dies after kernel uncompressing.

[Juergen Sievers]

Oh, Oh!  

 

That is really embarrassing but I found my mistake. 

 

I have forgotten to append a ‘M’ to the ‘mem=xy’ statement. So my kernel was
thinking there is only 32 byte of memory.  

Why it still was booting is a miracle too but with ‘mem=32M’ it works proper
again.

 

Regards   0(°^°)0

J.