From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: George Pontis <GPontis@z9.com>
Cc: barebox@lists.infradead.org
Subject: Re: New user: need a hand booting the kernel from NAND
Date: Thu, 19 Apr 2012 09:55:00 +0200 [thread overview]
Message-ID: <20120419075500.GB20601@game.jcrosoft.org> (raw)
In-Reply-To: <037201cd1df7$94b2b600$be182200$@com>
On 23:42 Wed 18 Apr , George Pontis wrote:
> Machine is a custom at91sam9g45 board with NOR and NAND flash. The
> bootstrap loader and barebox, and barebox environment are in the NOR
> flash. All seems to be working well there. The NAND is partitioned into 2
> chunks: 2560K(kernel),-(root)
>
>
>
> I used ubimkvol to create a volume on root and the nfs command to put a
> root filesystem on it. Seems to work fine if I get the kernel via NFS.
>
>
>
> I have a good working kernel in uImage format, and used "nfs
> /var/share/uImage /dev/nand0.kernel.bb" in an attempt to write it to the
> 2560K partition. The nfs copy seemed to work fine. However, it will not
> accept the image. I get messages about an unknown format, suggesting to
> try -f. Was it the wrong procedure that I used to copy the uImage ?
>
>
>
> Thanks for any help or pointers.
I recommand you to use upate command to bo so
update -t kernel -d nand -m nfs -f /var/share/uImage
I recommand you also to drop the uImage support and boot the zImage directly
you will boot more fast
and I also recommand you to boot from nor if you can
so you don't need the bootstrap
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-04-19 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 6:42 George Pontis
2012-04-19 7:13 ` Sascha Hauer
2012-04-19 7:55 ` Jean-Christophe PLAGNIOL-VILLARD [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=20120419075500.GB20601@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=GPontis@z9.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