From: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
To: barebox@lists.infradead.org
Subject: Compiled in boot environment and dtbo files
Date: Wed, 16 Jun 2021 10:10:55 +0200 [thread overview]
Message-ID: <FA60DA2B-8C76-4460-8009-88EAB94A0F2C@inside-m2m.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1721 bytes --]
Dear community,
actually I wonder how to prepare a reset/boot up default boot environment compiled in.
Is it correct, that my 1st task to achieve this is to add a new file in defaultenv/defaultenv-2-base/boot
like “insidem2m” for example? I managed to modify the existing “sd” entry to be able to boot
and persist this, thats how my new entry should look:
#!/bin/sh
global.bootm.image=/boot/uImage
global.bootm.oftree=/boot/am335x-boneblack.dtb
global.linux.bootargs.dyn.root="cape_enable=capemgr.enable_partno=BB-UART1,BB-UART4 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait”
right?
I can edit and modify those file and persist them, where is this saved? In my case it looks modified stuff shows
up in barebox.env in my /boot.
Especially my question is, when I add a boot entry compiled in, the boot.default variable should get this entry
and this must be reset/default compiled-in, how is this done?
My second issue is, currently I need to apply two dtbo files to the kernel booting, how do I do this in barebox?
In u-boot this looks like
uboot_overlay_addr0=/lib/firmware/BB-UART1-00A0.dtbo
uboot_overlay_addr1=/lib/firmware/BB-UART4-00A0.dtbo
in uEnv.txt, I did not find a pendant in the barebox world yet. The capemgr/slot kernel commandline stuff is
deprecated, right?
INSIDE M2M GmbH
Konstantin Kletschke
Berenbosteler Straße 76 B
30823 Garbsen
Telefon: +49 (0) 5137 90950136
Mobil: +49 (0) 151 15256238
Fax: +49 (0) 5137 9095010
konstantin.kletschke@inside-m2m.de
http://www.inside-m2m.de
Geschäftsführung: Michael Emmert, Ingo Haase, Dr. Fred Könemann, Derek Uhlig
HRB: 111204, AG Hannover
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4124 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2021-06-16 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 8:10 Konstantin Kletschke [this message]
2021-06-16 12:34 ` Sascha Hauer
2021-06-16 15:57 ` Konstantin Kletschke
2021-06-16 19:55 ` Trent Piepho
2021-06-18 12:43 ` Konstantin Kletschke
2021-06-17 6:41 ` Sascha Hauer
2021-06-18 13:15 ` Konstantin Kletschke
2021-06-21 4:01 ` Sascha Hauer
2021-06-21 14:21 ` Konstantin Kletschke
2021-06-22 10:40 ` Konstantin Kletschke
2021-06-18 6:48 ` Ahmad Fatoum
2021-06-18 13:16 ` Konstantin Kletschke
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=FA60DA2B-8C76-4460-8009-88EAB94A0F2C@inside-m2m.de \
--to=konstantin.kletschke@inside-m2m.de \
--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