From: "Juergen Sievers" <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 [thread overview]
Message-ID: <000601c738b8$f7f0cd80$0700a8c0@NADHHLT01> (raw)
In-Reply-To: <45A90A27.8030206@gmail.com>
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
next prev parent reply other threads:[~2007-01-15 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 16:34 [Howto] 2430 kernel,uboot and filesystem Nishanth Menon
2007-01-15 15:22 ` Juergen Sievers [this message]
2007-01-15 15:53 ` Help: OMAP5912 RS232 dies after kernel uncompressing Abot Botbot
2007-01-15 20:50 ` AW: " Juergen Sievers
2007-01-16 0:58 ` Nishanth Menon
2007-01-16 12:01 ` AW: " Juergen Sievers
2007-01-15 16:05 ` Liem Pham Tan
2007-01-15 18:00 ` [Howto] 2430 kernel,uboot and filesystem Dirk Behme
-- strict thread matches above, loose matches on Subject: below --
2007-01-16 17:22 Help: OMAP5912 RS232 dies after kernel uncompressing Juergen Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000601c738b8$f7f0cd80$0700a8c0@NADHHLT01' \
--to=jsievers@nadine-software.com \
--cc=linux-omap-open-source@linux.omap.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox