From: Sascha Hauer <s.hauer@pengutronix.de>
To: Kamel BOUHARA <k.bouhara@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: NAND Boot Issue
Date: Mon, 17 Oct 2011 21:58:01 +0200 [thread overview]
Message-ID: <20111017195801.GF18141@pengutronix.de> (raw)
In-Reply-To: <CAM9uW_6-A3OSu5PrcM5NoA=CP4YAbOi_YM=_62zPwQvhM1k7gQ@mail.gmail.com>
On Mon, Oct 17, 2011 at 06:03:56PM +0200, Kamel BOUHARA wrote:
> Hi all,
>
> Im working on my own imx27 designed board and wanted to try barebox on
> it.Actually I'm trying it with the phytec board config and it seems to work
> fine booting on my nfs kernel and rootfs.
> But when Im trying to boot from my 128MiB NAND memory then it doesn't work
> and there is no decompression stage from the kernel.
> Here is what Im getting :
>
> Board: Phytec phyCard-i.MX27
> registered netconsole as cs1
> cfi_probe: cfi_flash base: 0xc0000000 size: 0x02000000
> NAND device: Manufacturer ID: 0x2c, Chip ID: 0xac (Micron NAND 512MiB 1,8V
> 8-bit)
> Bad block table found at page 262080, version 0x01
> Bad block table found at page 262016, version 0x01
> Before PHY reset
> After PHY reset
> ULPI Vendor ID 0xffffff92 Product ID 0xffffff92
> No ISP1504 found
> ehci@ehci0: USB EHCI 1.00
> ULPI Vendor ID 0xffffff92 Product ID 0xffffff92
> No ISP1504 found
> ehci@ehci1: USB EHCI 1.00
> Malloc space: 0xa7a00000 -> 0xa7f00000 (size 5 MB)
> Stack space : 0xa79f8000 -> 0xa7a00000 (size 32 kB)
> running /env/bin/init...
>
> Hit any key to stop autoboot: 1
> booting kernel of type uImage from /dev/nand0.kernel.bb
> barebox:/ bootu /dev/nand0.kernel.bb
bootu is for starting raw kernel images. Do you have such an image?
Normally you have an uImage (bootm) or a zImage (bootz)
> commandline: console=ttymxc0,115200 video=imxfb:Chimei-LW700AT9003
> arch_number: 1698
>
> It seems I'm getting some issues with my nand since when I tried to flash it
> and the erase task failed :
>
> erasing partition /dev/nand0.kernel.bb
>
> erase: Invalid argument
Works here. I can't see how erase could return -EINVAL. can you please
post the output of 'ls /dev/nand0*'?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-10-17 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 16:03 Kamel BOUHARA
2011-10-17 19:58 ` Sascha Hauer [this message]
2011-10-17 20:31 ` Kamel BOUHARA
2011-10-18 6:58 ` Sascha Hauer
2011-10-18 7:35 ` Kamel BOUHARA
2011-10-18 8:23 ` Sascha Hauer
2011-10-18 9:44 ` Kamel BOUHARA
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=20111017195801.GF18141@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=k.bouhara@gmail.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