qschulz has quit [Remote host closed the connection]
zibolo has quit [Ping timeout: 268 seconds]
qschulz has joined #u-boot
zibolo has joined #u-boot
<marex>
tlwoerner: isnt there some boot mode register ?
<marex>
tlwoerner: that you can read with 'setexpr foo *address' ?
joeskb7 has quit [Ping timeout: 268 seconds]
mmu_man has quit [Ping timeout: 252 seconds]
joeskb7 has joined #u-boot
rvalue has joined #u-boot
jclsn has quit [Ping timeout: 260 seconds]
jclsn has joined #u-boot
persmule has quit [Remote host closed the connection]
stefanro has joined #u-boot
warpme has joined #u-boot
persmule has joined #u-boot
Forty-Bot has quit [Ping timeout: 272 seconds]
Forty-Bot has joined #u-boot
alan_o has quit [Read error: Connection reset by peer]
alan_o has joined #u-boot
mmu_man has joined #u-boot
linfax has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
alperak has joined #u-boot
rvalue has joined #u-boot
enok has joined #u-boot
Guest3 has joined #u-boot
<Guest3>
Hi everyone,
<Guest3>
Trying to run u-boot-spl on SIM but I'm getting the error "No serial driver found". There is a problem somewhere with the serial but I can't find it. Is there any point you suggest me to look or pay attention to? Log:
<Kwiboo>
tlwoerner: on some rockchip socs mmc0 will be emmc and mmc1 is sd-card, i.e. rk3288, rk3308, rk3328, rk3399 and rk356x. To run scripts U-Boot proper needs to be running, or are you trying to change how SPL load FIT?
<Guest3>
Speaking of eMMC and SD, what exactly determines mmcblockX? I have something like:
<Guest3>
mmc list
<Guest3>
mmc@4020000: 0 (SD)
<Guest3>
mmc@4022000: 1 (eMMC)
<Guest3>
But mmcblockX sometimes changing. I'm trying to understand it.
mckoan|away is now known as mckoan
<urja>
mmcblockX order is arbitrary in linux (like USB devices, it's just whichever it happens to get to initializing first) (there are some setups where it practically is fixed, and I've heard of some patches to make it fixed, but yeah...)
abws has joined #u-boot
ungeskriptet3 has joined #u-boot
ungeskriptet has quit [Ping timeout: 264 seconds]
ungeskriptet3 is now known as ungeskriptet
ungeskriptet3 has joined #u-boot
frieder has joined #u-boot
ungeskriptet has quit [Ping timeout: 268 seconds]
ungeskriptet has joined #u-boot
ungeskriptet3 has quit [Ping timeout: 256 seconds]
ungeskriptet9 has joined #u-boot
ungeskriptet has quit [Ping timeout: 256 seconds]
ungeskriptet9 is now known as ungeskriptet
naoki has quit [Quit: naoki]
<pivi>
urja, Guest3: just add aliases in the DT file, with that you can have a fixed allocation
<pivi>
urja: no additional patches required
<pivi>
urja: as an example, look at arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi
slobodan__ has joined #u-boot
<Guest3>
pivi thanks for knowledge and example. I'm a rookie so example helped me understand. :)
enok has quit [Ping timeout: 255 seconds]
frieder has quit [Ping timeout: 256 seconds]
enok has joined #u-boot
frieder has joined #u-boot
enok has quit [Ping timeout: 268 seconds]
edwinistrator2 has quit [Remote host closed the connection]
edwinistrator2 has joined #u-boot
rvalue has quit [Ping timeout: 268 seconds]
jfsimon1981 has quit [Remote host closed the connection]
jfsimon1981 has joined #u-boot
f_ has joined #u-boot
Guest3 has quit [Quit: Client closed]
f_ has quit [Quit: To contact me, send a memo using MemoServ, PM f_[xmpp], or send an email. See https://vitali64.duckdns.org/.]
enok has joined #u-boot
enok has quit [Client Quit]
enok71 has joined #u-boot
enok71 is now known as enok
enok has quit [Ping timeout: 255 seconds]
rvalue has joined #u-boot
dsimic has quit [Ping timeout: 272 seconds]
dsimic has joined #u-boot
monstr has quit [Read error: Connection reset by peer]
enok has joined #u-boot
tafa has joined #u-boot
enok has quit [Ping timeout: 252 seconds]
thopiekar has quit [Ping timeout: 252 seconds]
alexxy has quit [Ping timeout: 268 seconds]
enok has joined #u-boot
enok has quit [Ping timeout: 255 seconds]
Stat_headcrabed has joined #u-boot
slobodan_ has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
slobodan__ has quit [Ping timeout: 256 seconds]
rvalue has joined #u-boot
<tlwoerner>
Kwiboo: i have rauc working on 2 of my rockchip boards: rock-pi-e (rk3328) and rock-pi-s (rk3308)
<tlwoerner>
i always use sdcards, but i want to accommodate people who prefer using eMMC
<tlwoerner>
the rk3328 boards call the sdcard mmc1 and (it seems like) every other rockchip board calls the sdcard mmc0
<tlwoerner>
to get the A/B logic to work requires a U-Boot (proper) script
<tlwoerner>
the variable "bootdev" is set so that later the script can load the kernel/dt/fitimage from that device
<tlwoerner>
writing a generic script to work for both sdcard and emmc for all rockchip devices requires the user to configure their boot device preference
<tlwoerner>
but with all the work going on in the rockchip devices to be able to save the environment back to the device from which U-Boot proper was booted
<tlwoerner>
i was hoping to take advantage of that trick here in the script as well
<tlwoerner>
then i'm not relying on the user to configure things correctly
alexxy has joined #u-boot
linfax has quit [Ping timeout: 256 seconds]
<tlwoerner>
the choice of mmc0 vs mmc1 could be done programmatically and just say: mmc<bootdevice>
<tlwoerner>
right now, for any given rockchip board, i can use the exact same image to boot either from sdcard or emmc, with support for saving the environment, and everything just works
<tlwoerner>
but if i can't discover the boot device from within a script, then i will need separate images depending on whether the user is booting from emmc vs sdcard
<tlwoerner>
so i'm asking: does this exist already and if so what is it?
<tlwoerner>
or if it doesn't exist, what would be involved to making it, given that we're already doing something very similar wrt saving the environment
<Kwiboo>
tlwoerner: for u-boot control fdt and the socs I mentioned mmc 0 should be emmc (sd-nand on rock-pi-s) and mmc 1 is sd-card, the <soc>-u-boot.dtsi file overrides mmc aliases defined in the board main dts file
cryo_ has joined #u-boot
cryo_ is now known as Guest8174
Guest8174 is now known as MrCryo
rvalue has quit [Ping timeout: 264 seconds]
thopiekar has joined #u-boot
rvalue has joined #u-boot
<Kwiboo>
tlwoerner: the standard boot script bootmeth should set devtype, devnum, distro_bootpart and prefix env vars, similar to old distro boot, that may be what you are looking for?
<Kwiboo>
that would reference from where the bootscript was loaded/run from, not sure that is what you are looking for. tpl+spl / u-boot proper (fit) / bootscript can be loaded from different storage devices
<marex>
tlwoerner: dont you have some stale env loaded from storage ?
<tlwoerner>
marex: this is a completely fresh environment as generated by the build, which i flash into the uboot_env partition as part of my wic image
<Kwiboo>
tlwoerner: the vars is set just before the script executes, since they refer to the devtype/devnum of the bootscript, so you should be able to use them in your scripts