From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [OT]Need help getting Linux past init
Date: Sat, 27 Mar 2010 22:34:46 +1100 [thread overview]
Message-ID: <4BADED56.1050202@gmail.com> (raw)
In-Reply-To: <1269622538.3376.20442.camel@localhost.localdomain>
Peter Tyser wrote:
>> So it looks like the kernel has no problem locating /bin/sh in the JFFS2
>> partition but then the lights go out. I've also tried /bin/init - same result.
>>
>
> What if you make an init app or script that just creates a file on the
> JFFS2 fs? Then you could verify it was created by rebooting the board
> and inspecting the filesystem from U-Boot. That would tell you that the
Brilliant idea!
After trying to figure out why networking stopped (note to self - don't
accidentally disable PCI Interrupts) I got NFS Root working as well and
created /bin/test_init as:
#!/bin/sh
/bin/echo hello > /tmp/test_hello
and set the kernel command line init=/bin/test_init and lo and behold it
created /tmp/test_hello exactly as expected (well, the kernel then crashed
'cause init died - lol)
I then created a jffs2 image from the NFS Root and got the same result
Very happy :)
> code is executing as expected at least. You could dump debug output to
> this file for later use too. If that works, it'd be interesting to know
> if a statically linked hello world app printed anything out. If not,
> you could narrow the problem down to a serial/console issue.
I think this is where I am at. I think everything really is working except
for the serial console after control is passed to init
>
> A JTAG/XDP debugger could help too. Maybe dumping the printk buffer in
> Linux would show some kernel messages that never made it to your serial
> port.
I think I can debug it using NFS Root
Graeme
prev parent reply other threads:[~2010-03-27 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 12:33 [U-Boot] [OT]Need help getting Linux past init Graeme Russ
2010-03-26 14:24 ` Dennis Semakin
2010-03-26 14:56 ` Detlev Zundel
2010-03-26 16:55 ` Peter Tyser
2010-03-27 11:34 ` Graeme Russ [this message]
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=4BADED56.1050202@gmail.com \
--to=graeme.russ@gmail.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.