mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Mihaita Ivascu <mihaita_ivascu@trimble.com>
To: jlu@pengutronix.de
Cc: barebox@lists.infradead.org, bst@pengutronix.de, linux@rempel-privat.de
Subject: Re: MFGtools support in barebox
Date: Wed, 18 Jul 2018 17:11:09 +0200	[thread overview]
Message-ID: <CAEp+FuAsDL9msTeiC=2+bbKHkrEObdKKdctN_G3RdVX8uP=ZsQ@mail.gmail.com> (raw)
In-Reply-To: <1531925793.3511.128.camel@pengutronix.de>

Hi,

    Thanks for answer.
     I think I need it to do it from Windows as we have some boards
that need to be updated in the factory by people that do not necessary
have Linux skills or Linux workstation.
     That is why we thought we could use MFGtools app.
     My problem is that the board we have have only NAND and USB as
boot options. And I need to flash the NAND the first time.
      I have already looked at imx-usb-loader solution but it required
a Linux OS which is not possible in my case
     I have already used barebox_update successfully but only after I
had a working barebox already.
     I was successful into loading barebox image from MFGtools into
RAM and there execute barebox_update to flash on the NAND itself.
     But the barebox won't load afterwards the kernel image with
mfgtools support.

    So I have two options I think:

    i) porting barebox_update to Linux. Is there a way to flash the
barebox on NAND from Linux itself(after the board has booted
successfully) ?
   ii) adding support for MFGtools in barebox. I do not have toom uch
knowledge about it. I know I should add UTP protocol support in usb
gadget code in barebox but was not successful so far.

        How do you guys see a solution to this scenario?

Thanks,
       Mihaita
On Wed, Jul 18, 2018 at 4:56 PM Jan Lübbe <jlu@pengutronix.de> wrote:
>
> On Wed, 2018-07-18 at 15:53 +0200, Bastian Stender wrote:
> > Hi,
> >
> > On 07/18/2018 03:01 PM, Oleksij Rempel wrote:
> > > you email is in the list. (well, different version of it are already
> > > in the list). Please wait if some one can respond here.
> > >
> > > I'm not an expert, but probably what you need is
> > > https://github.com/rauc
> >
> > Have a look here:
> >
> > http://rauc.readthedocs.io/en/latest/advanced.html#updating-the-bootloader
> >
> > Updating barebox on NAND is not yet implemented. It would certainly be a
> > nice feature to have. Have a look in section 7.6.2 if you want to do that.
>
> Speaking with my rauc maintainer hat on...
>
> Writing barebox to NAND on an i.MX6 can't be done by generic methods,
> so for rauc we would want to call something like barebox-update which
> then handles the details. In any case, rauc is not intended for initial
> installation in the factory, but for updating in the field.
>
> Instead of MFGtools, we usually load barebox via imx-usb-loader. That
> is configured to start the fastboot gadget, which we then use to write
> barebox (via barebox_update) and the rootfs.
>
> Regards,
> Jan
> --
> 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:[~2018-07-18 15:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 12:05 Mihaita Ivascu
2018-07-18 13:01 ` Oleksij Rempel
2018-07-18 13:53   ` Bastian Stender
2018-07-18 14:56     ` Jan Lübbe
2018-07-18 15:11       ` Mihaita Ivascu [this message]
2018-07-18 16:35         ` Oleksij Rempel
2018-07-18 17:56           ` Mihaita Ivascu
2018-07-19  5:08             ` Oleksij Rempel
2018-07-19  9:53               ` Jan Lübbe
2018-07-19 10:08                 ` Mihaita Ivascu
  -- strict thread matches above, loose matches on Subject: below --
2018-07-18  7:39 MFGTools " Mihaita Ivascu
2018-07-20  9:11 ` Uwe Kleine-König
2018-07-20  9:32   ` Mihaita Ivascu
2018-07-20  9:57     ` Oleksij Rempel
2018-07-20 18:14       ` Mihaita Ivascu
2018-08-03  8:21         ` Mihaita Ivascu
2018-08-03  8:37           ` Oleksij Rempel
2018-08-03 16:37             ` Mihaita Ivascu
2018-08-03 17:10               ` Oleksij Rempel
     [not found]                 ` <CAEp+FuBAV20+TJOkGTZkbr=yOOLjR2DFN9sM+ZO+E6CgKkYeFw@mail.gmail.com>
2018-08-06  8:42                   ` Oleksij Rempel

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+FuAsDL9msTeiC=2+bbKHkrEObdKKdctN_G3RdVX8uP=ZsQ@mail.gmail.com' \
    --to=mihaita_ivascu@trimble.com \
    --cc=barebox@lists.infradead.org \
    --cc=bst@pengutronix.de \
    --cc=jlu@pengutronix.de \
    --cc=linux@rempel-privat.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