mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Mihaita Ivascu <mihaita_ivascu@trimble.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: flash barebox to NAND
Date: Fri, 25 Oct 2019 18:43:37 +0200	[thread overview]
Message-ID: <CAEp+FuAx=OSO39sj1coX5tLfZ11xy2ijKmRi2h_L8oAY6tR-EQ@mail.gmail.com> (raw)
In-Reply-To: <20191024065849.wwewim36f3mojkoj@pengutronix.de>

On Thu, Oct 24, 2019 at 8:58 AM Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
> On Wed, Oct 23, 2019 at 03:47:49PM +0200, Mihaita Ivascu wrote:
> > On Wed, Oct 23, 2019 at 3:33 PM Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > >
> > > On Wed, Oct 23, 2019 at 11:39:00AM +0200, Mihaita Ivascu wrote:
> > > > Hello all,
> > > >
> > > >   I would like to know what possibilities do I have to flash a barebox
> > > > image to mtd partition from Linux?
> > > >  Using ubifs commands does not work. the barebox will not boot so
> > > > probably additional info needs to be written except the barebox image
> > > > itself.
> > >
> > > On i.MX a bootloader image can't be written to Nand directly. In barebox
> > > you can update barebox with the barebox_update command which has support
> > > for the special image format requirements of the i.MX6. I currently
> > > don't know any userspace code that can do this, apart from mfgtools or
> > > other tools from the NXP universe that I have never used. Somebody told
> > > me he wanted to port the i.MX6 barebox update code to userspace, but
> > > unfortunately I can't remember who it was and I can't find any pointers
> > > to it.
> > >
> > > Regards,
> > >   Sascha
> > >
> >
> >    Thanks for your detailed answer.
> >    so there is no way to update a barebox on NAND from Linux except
> > from the barebox itself(using barebox_update command) ?
> >    Yes I am trying with mfgtools but no success. NXP does not support
> > barebox just u-boot and I was not successful on adding mfgtools/UTP
> > support in barebox.
> >    And using the u-boot konbs-ng command for flashing bootloader to
> > NAND is faulty and the reason is documented in the NXP community.
> >   Surely somebody from barebox community must have had the need before
> > to update the barebox otherway than using barebox_update from the
> > barebox itself.
>
> One way to update barebox indirectly from Linux is to put the new
> barebox image to some known place in the rootfs. Now in barebox
> write a small script:
>
> /env/init/bbu.sh:
>
> #!/bin/sh
>
> if [ -f /mnt/mmc0.0/boot/barebox-update.bin ]; then
>         barebox_update -y /mnt/mmc0.0/boot/barebox-update.bin
>         reset
> fi
>
> Then again under Linux delete that file when the running barebox version
> (as read from the device tree or kernel commandline) matches the update
> image.
>
> Sascha

Hello,

    Thanks for the tip. In the meantime I am able to load a barebox
using MFTools in RAM and run it. So i can modify that barebox to
include a script that does this barebox_update
from the barebox that is loaded using MFGTools. My issue now is how do
I make barebox_update to read the barebox.bin which was written in
nand(in some mtd0 partition from Linux)
    The problem is that I have no mmc or other mountable device in
barebox. Only the nand
    So I don't know how I should access the nand partition from a
script in the barebox.
    do you have any suggestion?

Thanks,
      Mihaita


>
> --
> 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

      reply	other threads:[~2019-10-25 16:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23  9:39 Mihaita Ivascu
2019-10-23 10:27 ` Andreas Geisenhainer
2019-10-23 10:39   ` Mihaita Ivascu
2019-10-23 13:33 ` Sascha Hauer
2019-10-23 13:47   ` Mihaita Ivascu
2019-10-24  6:58     ` Sascha Hauer
2019-10-25 16:43       ` Mihaita Ivascu [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='CAEp+FuAx=OSO39sj1coX5tLfZ11xy2ijKmRi2h_L8oAY6tR-EQ@mail.gmail.com' \
    --to=mihaita_ivascu@trimble.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox