From: Mihaita Ivascu <mihaita_ivascu@trimble.com>
To: jlu@pengutronix.de
Cc: o.rempel@pengutronix.de, barebox@lists.infradead.org,
bst@pengutronix.de, linux@rempel-privat.de
Subject: Re: MFGtools support in barebox
Date: Thu, 19 Jul 2018 12:08:41 +0200 [thread overview]
Message-ID: <CAEp+FuBpbv=xVAijE+jOB2fQjofVgHoVC-zksvNe9sKCNqNBfA@mail.gmail.com> (raw)
In-Reply-To: <1531993986.3511.144.camel@pengutronix.de>
Hi,
Yes, thanks for your answer. That is true. Also I think mtd-utils
from withing Linux will not work also to update barebox mtd partition?
I have tried using kobs-ng init command from with Linux(as an
alternative to barebox_update) and it did seem it writes additional
BBU and other tables but unfortunately would stuck at some point and
not complete the update.
Best regards,
Mihaita
On Thu, Jul 19, 2018 at 11:53 AM Jan Lübbe <jlu@pengutronix.de> wrote:
>
> On Thu, 2018-07-19 at 07:08 +0200, Oleksij Rempel wrote:
> > > Aside from this issue, are you aware of any method of
> > > flashing the barebox on NAND from Linux(after the kernel was loaded
> > > successfully on the target) ?
> > > barebox_update does not exist in Linux obviously and porting it is not
> > > so trivial, on top of that I don't think I am able to access the nand
> > > device from Linux, but only MTD partitions .
> > > I have tried nandwrite and kobs-ng commands but I was not successful.
> >
> > barebox_update is a wrapper to: take a image and write it to predefined
> > project or board specific location.
> > If you have access to this location from linux, you can do it from linux
> > as well.
>
> Note that i.MX6, barebox_update also generates additional headers for
> the ROM loader (such as a small bad block table). A raw barebox image
> without these headers cannot be booted by the ROM from NAND. This is
> the reason why simple nandwrite doesn't work.
>
> 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
next prev parent reply other threads:[~2018-07-19 10:09 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
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 [this message]
-- 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+FuBpbv=xVAijE+jOB2fQjofVgHoVC-zksvNe9sKCNqNBfA@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 \
--cc=o.rempel@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