From: Baruch Siach <baruch@tkos.co.il>
To: Vanalme Filip <F.Vanalme@TELEVIC.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: booting linux
Date: Wed, 2 Mar 2011 12:45:51 +0200 [thread overview]
Message-ID: <20110302104551.GB28548@jasper.tkos.co.il> (raw)
In-Reply-To: <6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B00EFC@SRV-VS06.TELEVIC.COM>
Hi Vanalme,
On Wed, Mar 02, 2011 at 11:31:31AM +0100, Vanalme Filip wrote:
[snip]
> Then I do :
>
> barebox:/ bootz /dev/nand0.kernel.bb
> loaded zImage from /dev/nand0.kernel.bb with size 1777792
> commandline: console=ttymxc0,115200 ip=dhcp root=/dev/mtdblock7 rootfstype=jffs2 mtdparts=mxc_nand:256k(barebox)ro,128k(bareboxenv),5M(kernel),-(root)
> arch_number: 1802
> Uncompressing Linux........................................................................................................................... done, booting the kernel.
If your kernel is recent enough (2.6.33 or newer) try the following:
1. Enable EARLY_PRINTK in your .config
2. Add "earlyprintk" to your bootargs
3. Boot the kernel
Post here what you see.
baruch
> The kernel uncompresses but never starts. Any idea why not ? Does barebox
> expand the kernel to the right place in SDRAM or do I have to specify that
> in the bootz command ?
> I think the kernel is never started at all because I don't see any output at all. In this phase, even having a kernel crash would be great... because at least then I would know the kernel has been running for a while... ;-)
>
> I guess the image is OK because it uncompresses successfully. Maybe a problem in the bootargs that are passed to the kernel ?
> Should I already have a /dev/mtdblock7 device in barebox's /dev ?
>
> Maybe useful information :
>
> barebox:/ printenv
> locals:
> machine=imx27pdk
> ip=dhcp
> kernel_loc=nand
> rootfs_loc=nand
> rootfs_type=jffs2
> rootfsimage=root-jffs2
> kernelimage_type=zimage
> kernelimage=zImage-imx27pdk
> nfsroot=:/path/to/nfs/root
> autoboot_timeout=3
> bootargs=console=ttymxc0,115200
> nand_parts=256k(barebox)ro,128k(bareboxenv),5M(kernel),-(root)
> rootfs_mtdblock_nand=7
> PS1=\e[1;32mbarebox@\e[1;31m\h:\w\e[0m
> bootfile=zImage
> nameserver=10.0.0.44
> domainname=televic.com
> globals:
> PATH=/env/bin
> barebox:/
>
> Filip
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-03-02 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 10:31 Vanalme Filip
2011-03-02 10:45 ` Baruch Siach [this message]
2011-03-02 13:03 ` Vanalme Filip
2011-03-02 13:53 ` Sascha Hauer
2011-03-02 14:37 ` Vanalme Filip
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=20110302104551.GB28548@jasper.tkos.co.il \
--to=baruch@tkos.co.il \
--cc=F.Vanalme@TELEVIC.com \
--cc=barebox@lists.infradead.org \
/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