mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: Patrick Schneider <patrick.schneider@bhtronik.de>,
	"barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Loading Barebox to RAM
Date: Sat, 2 Mar 2019 15:36:51 +0100	[thread overview]
Message-ID: <3429d555-f746-f248-af2f-7e41022cf055@rempel-privat.de> (raw)
In-Reply-To: <AM0PR08MB38426E671D56BFE16ACA65C1EB770@AM0PR08MB3842.eurprd08.prod.outlook.com>

Hi,

Am 02.03.19 um 13:49 schrieb Patrick Schneider:
> Hey guys,
> I have a question about a way of "emergency flashing" the device.
> So I have a fully operational linux system with barebox as bootloader. In production environment I have no access to the serial console but I have a USB OTG port.
> For security reasons I don't want USB active in my "normal" barebox environment, so it's off by config.
> For support, to gain access to a barebox and bootloader functionality is there a way to load another barebox (with usb active) from linux userspace into RAM and start/reboot into that?
> Have a nice weekend!

Let me rephrase: you disabled every thing in a bootloader which can be
accessed only locally and provided functional to nuke complete system
from linux which can be accessed locally and remotely?
I assume, it would make sense to review the thread model of this project.

Any way. "is it possible to run barebox from linux", the answer would
be: theoretically it should be possible to do it from kexec. I never
tried it before.
-- 
Regards,
Oleksij

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

  reply	other threads:[~2019-03-02 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02 12:49 Patrick Schneider
2019-03-02 14:36 ` Oleksij Rempel [this message]
2019-03-04  8:11   ` 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=3429d555-f746-f248-af2f-7e41022cf055@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --cc=barebox@lists.infradead.org \
    --cc=patrick.schneider@bhtronik.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