mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Erwin Rol <mailinglists@erwinrol.com>
To: Barebox List <barebox@lists.infradead.org>
Subject: Re: imx6 usb update
Date: Fri, 30 Nov 2018 16:05:30 +0100	[thread overview]
Message-ID: <1543590330.5085.16.camel@erwinrol.com> (raw)
In-Reply-To: <1543585763.5085.14.camel@erwinrol.com>

Hey all,

the bootmode detection I figured out, but the using DFU to directly
flash barebox bricks my system;

usbgadget -D /dev/nand0.barebox(barebox)s

That doesn't work. 

Is there a way to update barebox via DFU? 

If not directly is it possible to trigger a script after DFU uploaded a
file, so I can call barebox_update ?

Or what would be the "barebox" way to do it ?

TIA,

Erwin

On Fri, 2018-11-30 at 14:49 +0100, Erwin Rol wrote:
> Hallo all,
> 
> I have my barebox running on a iMx6 (phyBOARD-Segin + phyCORE-i.MX 6UL
> Modul).
> 
> Loading via USB works fine, and via DFU I can upload a barebox image
> and use barebox_update to flash barebox in NAND.
> 
> Is it possible to have DFU correctly flash barebox, without first
> upload a image to /tmp/barebox and than use barebox_update ?
> 
> And a second question is it possible to detect if barebox was booted
> from NAND or from USB via imx-loader ? I woud like to use that to start
> the system normal when it boots from NAND but go in DFU update mode
> when it was started via imx-usb-loader.
> 
> As always hints and tips are very welcome,
> 
> Erwin
> 
> 
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2018-11-30 15:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-30 13:49 Erwin Rol
2018-11-30 15:05 ` Erwin Rol [this message]
2018-11-30 21:16   ` Sascha Hauer

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=1543590330.5085.16.camel@erwinrol.com \
    --to=mailinglists@erwinrol.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