From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.z9.com ([64.142.101.243]) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1SKl4f-0006Ue-Fu for barebox@lists.infradead.org; Thu, 19 Apr 2012 06:42:42 +0000 Received: from GPontisPC by z9.com (MDaemon PRO v12.5.4) with ESMTP id md50000201899.msg for ; Wed, 18 Apr 2012 23:42:34 -0700 From: "George Pontis" Date: Wed, 18 Apr 2012 23:42:25 -0700 Message-ID: <037201cd1df7$94b2b600$be182200$@com> MIME-Version: 1.0 Content-Language: en-us List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6575284604572321004==" Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: New user: need a hand booting the kernel from NAND To: barebox@lists.infradead.org This is a multi-part message in MIME format. --===============6575284604572321004== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0373_01CD1DBC.E853DE00" Content-Language: en-us This is a multi-part message in MIME format. ------=_NextPart_000_0373_01CD1DBC.E853DE00 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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. George ------=_NextPart_000_0373_01CD1DBC.E853DE00 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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.

George

------=_NextPart_000_0373_01CD1DBC.E853DE00-- --===============6575284604572321004== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox --===============6575284604572321004==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from metis.ext.pengutronix.de ([2001:6f8:1178:4:290:27ff:fe1d:cc33]) by casper.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1SKlYk-0003Y2-FJ for barebox@lists.infradead.org; Thu, 19 Apr 2012 07:13:48 +0000 Date: Thu, 19 Apr 2012 09:13:25 +0200 From: Sascha Hauer Message-ID: <20120419071325.GB13302@pengutronix.de> References: <037201cd1df7$94b2b600$be182200$@com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <037201cd1df7$94b2b600$be182200$@com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: New user: need a hand booting the kernel from NAND To: George Pontis Cc: barebox@lists.infradead.org On Wed, Apr 18, 2012 at 11:42:25PM -0700, 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 ? Have you erased you nand before (erase /dev/nand0.kernel.bb)? 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from 7.mo3.mail-out.ovh.net ([46.105.57.200] helo=mo3.mail-out.ovh.net) by merlin.infradead.org with esmtp (Exim 4.76 #1 (Red Hat Linux)) id 1SKmUw-0002qu-PZ for barebox@lists.infradead.org; Thu, 19 Apr 2012 08:13:54 +0000 Received: from mail622.ha.ovh.net (b7.ovh.net [213.186.33.57]) by mo3.mail-out.ovh.net (Postfix) with SMTP id 0D090FF89CE for ; Thu, 19 Apr 2012 10:15:12 +0200 (CEST) Date: Thu, 19 Apr 2012 09:55:00 +0200 From: Jean-Christophe PLAGNIOL-VILLARD Message-ID: <20120419075500.GB20601@game.jcrosoft.org> References: <037201cd1df7$94b2b600$be182200$@com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <037201cd1df7$94b2b600$be182200$@com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: New user: need a hand booting the kernel from NAND To: George Pontis Cc: barebox@lists.infradead.org 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