v0|d` has quit [Remote host closed the connection]
v0|d has joined #u-boot
ac_slater has quit [Ping timeout: 260 seconds]
torez has joined #u-boot
mort has joined #u-boot
<mort>
Hey, so I have a system with a u-boot partition at 0x4000 of some flash. How do I tell fw_printenv about it? I don't quite understand the config file format
<mort>
Is it even enough to know where the uboot partition is or do I have to know where the env vars are? If so, is there a way to figure out where the env vars are?
<matthias_bgg>
vfazio, give me a few more days before I come to it
<vfazio>
matthias_bgg, no problem. I just know it's come up a couple of times on the mailing list. thanks
torez has quit [Ping timeout: 245 seconds]
<milkylainen_>
sjg1: Did using uefi services make it out of efi-working?
<sjg1>
milkylainen_: Some of it. It is taking a while
<milkylainen_>
sjg1: I have a slot again. Still 64-bit app linking issues in efi-working?
<sjg1>
milkylainen_: Yes
<milkylainen_>
Ok. I'll try to dig again. This time with something I can debug.
<milkylainen_>
tnx
<mort>
is there maybe some way to get uboot itself to print all or most of the info I need for fw_env.config?
<mort>
since it already knows everything it needs to be able to read/write env vars
torez has joined #u-boot
<milkylainen_>
mort: What's the issue? You can't find the variables from userspace?
<mort>
milkylainen_: yeah, I don't have a fw_env.config so fw_printenv and such don't know where to find them
<milkylainen_>
mort: I don't think u-boot writes anything conclusive regarding where the variables might be from the perspective of the running userspace no. That can probably vary, depending on what you're running.
<milkylainen_>
I think the idea is that you should write your fw_env.config...
<mort>
based on what?
<milkylainen_>
Based on what you configured u-boot for?
<mort>
so, I didn't configure u-boot, I'm trying to make use of a relatively poorly documented system
<milkylainen_>
Maybe I'm missunderstanding the question. You configure u-boot and where it should place env, ergo you should know what to write in fw_env.config. Since you're likely owner of the userspace configuration.
<milkylainen_>
Ah.
<milkylainen_>
And you don't have access to the code/configuration?
<mort>
I do, I just don't have experience with uboot configuration
ac_slater has joined #u-boot
<mort>
I suppose I'll read the configuration documentation then and try to find everything out that way. I just hoped there was a simpler way
camus1 has joined #u-boot
camus has quit [Ping timeout: 240 seconds]
camus1 is now known as camus
<milkylainen_>
I see. well. Older u-boots have a lot of config hidden in headers. Newer u-boot, you can read most of the configuration through .config
<milkylainen_>
mort: ^
<milkylainen_>
What version are you talking about here?
<milkylainen_>
I think that's recent enough for .config in the env bits?
<milkylainen_>
Sounds like no config for 2017.09.
camus has quit [Ping timeout: 264 seconds]
camus has joined #u-boot
<mort>
is there a way from within u-boot that I can verify that the configuration isn't loaded from disk?
<mort>
to confirm that I'm actually looking at the final config
<mort>
and that it's not being overwritten by some header or something
<mort>
there's soooo much code generation going on in uboot that it's extremely hard to follow where the different config options come from
<mwalle_>
xypron: AFAIK the debian installer doesn't have any watchdog drivers, so even 5min would be too short
torez has quit [Ping timeout: 240 seconds]
torez has joined #u-boot
kroon_ has joined #u-boot
<kroon_>
Hi. I'm trying to understand which block device u-boot saves the environment to. Is there a CONFIG_xxx-setting for that ?
<kroon_>
Or is it inferred from u-boots location itself ?
<rfs613>
mort: the simplest way to determine if it the env is persistent is to add a variable ("setenv myfoo=bar"), then save it ("env save") and then power cycle. Upon restart, check if your env persists ("env print myfoo")
<rfs613>
kroon_: there are many options for storing the environment, start by checking CONFIG_ENV_IS.* in your .config file.
<kroon_>
I have CONFIG_ENV_IS_IN_MMC=y
<kroon_>
but I have two mmc devices
<kroon_>
and one of them has emmc boot partitions
camus1 has joined #u-boot
camus has quit [Ping timeout: 264 seconds]
camus1 is now known as camus
<rfs613>
kroon_: okay, so you'll next want to look at CONFIG_SYS_MMC_ENV_DEV to know which device