hanetzer has quit [Killed (NickServ (GHOST command used by hanetzer1))]
hanetzer1 is now known as hanetzer
hanetzer has quit [Ping timeout: 240 seconds]
hanetzer has joined #u-boot
hanetzer has quit [Ping timeout: 240 seconds]
hanetzer has joined #u-boot
wooosaiiii has quit [Quit: wooosaiiii]
wooosaiiii has joined #u-boot
stefanro has joined #u-boot
macromorgan has quit [Read error: Connection reset by peer]
macromorgan has joined #u-boot
rvalue has quit [Ping timeout: 250 seconds]
rvalue has joined #u-boot
thopiekar has quit [Ping timeout: 268 seconds]
thopiekar has joined #u-boot
monstr has joined #u-boot
runcom has joined #u-boot
runcom has quit [Ping timeout: 265 seconds]
runcom has joined #u-boot
runcom has quit [Ping timeout: 265 seconds]
sszy has joined #u-boot
<__ad>
Tartarus: thanks
<__ad>
marex: testing mcf watchdog driver in the qemu 5208 machine, getting a cyclic warning. It seems normal, since the "time" is totally inconsistent in quemu
<__ad>
a "sleep 1" returns immediately. Do you know a way to have "sleep 1" a real sleep 1 ?
runcom has joined #u-boot
runcom has quit [Ping timeout: 246 seconds]
austriancoder_ has quit []
austriancoder has joined #u-boot
<marex>
__ad: could it be the weird timer driver I wrote ?
<marex>
__ad: that is what I would suspect is the problem with sleep 1
<__ad>
(for another task): when an old removed driver is recreated (starting from the removed original) and sent as a patch (with additions), what should be writtend in the commit message ?
<__ad>
Something as recreated from HASH, is ok ? Should i set/mention any older author ?
goliath has joined #u-boot
prabhakarlad has joined #u-boot
mmu_man has quit [Ping timeout: 260 seconds]
apritzel_ has quit [Ping timeout: 268 seconds]
runcom has joined #u-boot
mmu_man has joined #u-boot
runcom has quit [Ping timeout: 265 seconds]
Blok has joined #u-boot
runcom has joined #u-boot
urja has quit [Read error: Connection reset by peer]
urja has joined #u-boot
<marex>
__ad: likely just "based on driver removed in commit SHA1"
runcom has quit [Ping timeout: 265 seconds]
<__ad>
marex: thanks !
FergusL has quit [Read error: Connection reset by peer]
FergusL has joined #u-boot
slobodan has quit [Quit: Leaving]
d-s-e has quit [Quit: Konversation terminated!]
mmu_man has quit [Ping timeout: 256 seconds]
Blok has quit [Ping timeout: 245 seconds]
<marex>
__ad: sure, sorry for the abysmal delay
<marex>
I should just create me a key binding for "sorry for the abysmal delay" by now 3/
<marex>
sjg1: have you got any suitable substitute word for "abysmal" ? "gruesome" was nice, but I don't think it applies :)
runcom has joined #u-boot
FergusL has quit [Quit: FergusL]
FergusL has joined #u-boot
runcom has quit [Ping timeout: 256 seconds]
antaresgades has quit [Quit: Client closed]
runcom has joined #u-boot
runcom has quit [Ping timeout: 240 seconds]
monstr has quit [Remote host closed the connection]
<Tartarus>
So, I'm trying to build for rockpro64-rk3399, and I built top of arm-trusted-firmware with PLAT=rk3399 and then U-Boot with make .... BL31=../arm-trusted-firmware/.../bl31.elf and, I get no output. But I also get no output on current Debian images, but an older Armbian I have around is giving me something at least, so I have console physically correct. Does anyone have a known good hash for upstream tf-a for rk3399, or a binary they
<Tartarus>
can send me?
goliath has quit [Quit: SIGSEGV]
guillaume_g has quit [Quit: Konversation terminated!]
runcom has quit [Ping timeout: 240 seconds]
<sjg1>
Tartarus: f69a5828b74ca works for me, but that is 3 years old
<sjg1>
Tartarus: Hmm perhaps I should have asked what you mean by no output? Do you mean no output from ATF?
<Tartarus>
Figured it out, crappy uSD car
<Tartarus>
d
<Tartarus>
Also needed one of my better USB serial cables to handle 1500000 rate not just 115200
<Tartarus>
Things are a bit odd, but lemme disconnect HDMI and see if the console behaves better
vagrantc has joined #u-boot
hanetzer has joined #u-boot
<Tartarus>
OK, so, yeah, I'll blame my KVM switch for the input being odd, for the moment
<Tartarus>
but sjg1 you have an rk3399 platform? Running bootflow immediately gets me a reset here
<Tartarus>
(er, to be clearer, run bootcmd)
<Tartarus>
Top of tree
<sjg1>
Tartarus: Yes I have a Bob, and a pine that is not connected to lab at present
<sjg1>
Tartarus: On Bob, I can get as far as Linux booting, but then I either get a hang or strange patterns on the display. I sent an email about it
<Tartarus>
sjg1: As of today or ?
<sjg1>
Tartarus: Wednesday. The subject is 'Mainline Linux on gru / bob'
<sjg1>
Tartarus: I can test something now if it helps
<Tartarus>
Well, I'm confused / concerned about this board just crashing right away
rfs613 has quit [Ping timeout: 248 seconds]
goliath has joined #u-boot
<mps>
I have rk3399 gru-kevin but mainline u-boot doesn't work (last time I tried)
<Tartarus>
and c194aa0c6cac310a54e796f4a4dcf4563cb83128 tf-a
<mps>
huh, paste shortcut made a mess
<alpernebbi>
oh hey
<sjg1>
Tartarus: Hmm sorry, no output from lab. But I can try again when I get home
<alpernebbi>
sjg1: in case you're using u-boot.rom, it doesn't have atf in it
<Tartarus>
Yeah, that's fine sjg1 thanks
<alpernebbi>
I am getting a synchronous abort with debian's shim on my older builds, trying to look into that
<alpernebbi>
I tried v2023.04 while messing with some configs, it didn't get to u-boot so I reverted back to my known working build
<sjg1>
alpernebbi: Yes I am. But I see messages about SDRAM init which I thought came from atf?
<Mis012[m]>
SDRAM init can be done by u-boot just fine, u-boot can even provide PSCI so you wouldn't need atf at all unless you actually want trustlets
<alpernebbi>
no idea about the console messages, but I always had to replace u-boot-img in the binman definition with a u-boot.itb blob to get linux to boot
<alpernebbi>
(sorry I didn't send a patch about that)
<mps>
just built u-boot 2023.04 with arm-trusted-firmware 2.8.6 for gru-kevin on alpine linux
<mps>
didn't tried to install and boot yet
<mps>
but build passed
<mps>
will try boot it in a few hours
rfs613 has joined #u-boot
<alpernebbi>
I get extremely nervous every time I try to externally flash it, can barely align the clip and hold it in place, so I'm very discouraged from working on it :(
samueldr has joined #u-boot
<austriancoder>
what is the proper U-Boot way to disable non existing cpu cores. patch the dtb in U-Boot based on e.g. a register or use different dtb's (one for one core setup and one for dual core setup)?
<Mis012[m]>
if the core literally doesn't exist, it's a different SoC, so it would have a different dtsi file
<Mis012[m]>
if it's just fused off, then status=disabled in board dts seems fair
<Kwiboo>
I just did some runtime testing of top of tree on rk3399 with mixed results. on rockpro64: reset because of "FDT overlap", on rock-pi-4: reset because of "drivers/core/ofnode.c:297: ofnode_read_u32_index: Assertion `ofnode_valid(node)' failed."
<Tartarus>
sjg1: On arm32, bootflow scan just doesn't seem to finish booting linux but distro_bootcmd is fine
<mps>
u-boot 2023.04 still doesn't work on gru-kevin, display stays blank
<alpernebbi>
u-boot proper can boot fine from depthcharge, so expecting something with spl
josch has left #u-boot [#u-boot]
goliath has joined #u-boot
<alpernebbi>
I'm also getting a synchronous abort with debian's shim, looks like immediately after an out of resources error when setting some mok variables
<alpernebbi>
assuming it's on the u-boot side, I'd appreciate it if anyone has advice as to what might be going wrong
<alpernebbi>
(doubling the variable buffer size works, I guess preseeding the variables would also work, but both feel like workarounds)
ikarso has quit [Quit: Connection closed for inactivity]
apteryx has joined #u-boot
<apteryx>
hi! can u-boot decompress a gz'd kernel image transparently?
<marex>
transparently ?
<apteryx>
one that is reported by 'file' as: 'boot/kernel8.img: gzip compressed data, was "Image"'
<apteryx>
like, detect automatically, and decompresses without scripting it
<apteryx>
as it tries to load it via 'ext4load mmc'
<apteryx>
or perhaps there's a different command for that?
<Tartarus>
Yes, it can if the right env vars are set
<Tartarus>
And as for booting, well, my am335x_evm doesn't finish booting wiht bootflow scan, is fine iwth distro_boot, it was the first handy thing to try that on that I knew was otherwise fine
<Tartarus>
bootflow scan fires up grub (from OE), starts linux, nothing after Starting Linux...
<Tartarus>
which sounds like your bob problem?
<Tartarus>
and my rockpro64-rk3399 has Armbian on the uSD card
<sjg1>
Tartarus: Well I can't get anything useful from bob when booting Linux no matter what I try
<sjg1>
Tartarus: but I do have a rockpro64 so will try that
<Tartarus>
wrote that, then replaced u-boot following doc/board/rockchip/rockchip.rst
<Tartarus>
And tangent I've got https://elinux.org/images/8/86/Bootstraping_Local_KernelCI.pdf to at least start looking at what it takes to get a local kernelci up, with the notion of firing off some kernelci smoke tests on real HW, once our test.py suite completes
goliath has quit [Quit: SIGSEGV]
<sjg1>
Tartarus: Hmm on rockpro64 I get a USB crash
<Tartarus>
I didn't look where the crash was, sorry, just that it failed, and then that my next platform to try bootflow scan on was am335x where it never finished booting, but works with distro_bootcmd (and the u-boot side is the same)
<Tartarus>
wasn't sure why it was even in usb at that point since boot_targets is mmc first
<Tartarus>
and I didn't have anything in USB
<sjg1>
Tartarus: If you think the problem isn't with ATF I can try to bisect it
<Kwiboo>
not sure what the issue is with usb, but usb is started because of stdin env contains usbkbd, with CONFIG_USB_KEYBOARD disabled it does not load nor crash at usb
<sjg1>
Tartarus: hmmmm something is wrong with AFT: spl_load_fit_image: Skip load 'atf-5': image size is 0!
<sjg1>
Kwiboo: OK
<Kwiboo>
still not possible to start armbian, it uses boot.scr so need CONFIG_BOOTMETH_SCRIPT=y, with that it finds a bootflow but ends with: Wrong image format for "source" command
<sjg1>
Kwiboo: Ugh. It was working last time I tried it