f_ changed the topic of ##raspberrypi-internals to: The inner workings of the Raspberry Pi (Low level VPU/HW) -- for general queries please visit #raspberrypi -- open firmware: https://librerpi.github.io/ -- VC4 VPU Programmers Manual: https://github.com/hermanhermitage/videocoreiv/wiki -- chat logs: https://libera.irclog.whitequark.org/~h~raspberrypi-internals -- bridged to matrix and discord
jcea has quit [Ping timeout: 256 seconds]
jcea has joined ##raspberrypi-internals
_whitelogger has joined ##raspberrypi-internals
<Ad0> hm my image boots on the dev board with HDMI on my CM3+ but not on a board without HDMI ...
<Ad0> could that be something that has to be disabled in u-boot or something?
<f_> UART :)
<Ad0> hm ?
<f_> Get some logs
<clever> Ad0: it should boot just fine without hdmi, how do you know its not booting?
<Ad0> no light on ACT, serial not outputting anything. stick it in the stock dev board for CM , boots fine and works with serial output
<clever> what about a stock dev board, with the hdmi unplugged?
<Ad0> it just has some early activity flashes and is then dead on the custom board, which worked on previous uboot/kernel
<Ad0> hm I will try that
<clever> your changing too many variables at once
<clever> and then blaming just one of them
<Ad0> doesn't work with the HDMI disconnected
<Ad0> I read similar post that a PI4 won't boot unless the HDMI is connected.
<clever> it will boot just fine without hdmi
<clever> but it wont create a framebuffer
<clever> and X wont run on boot
<Ad0> "Adding hdmi_force_hotplug=1 to /boot/config.txt seems to have solved the problem. The Pi4 is running headless,
<Ad0> "
<clever> and some people use the desktop env to run things on boot
<clever> so when X doesnt run on boot, they assume its not booting
<Ad0> I don't have X or anything
<clever> hdmi_force_hotplug=1 forces it to generate an hdmi signal, so it acts like it does have a head
<Ad0> trying force_hotplug=1
<clever> thats generally a problem with your software, expecting a video output
<Ad0> it's in the uboot stage
<Ad0> it's a headless yocto image
<clever> add moar debug to u-boot!
<Ad0> the hdmi_force_hotplug=1
<Ad0> id it ...
<Ad0> that's kinda messed up lol. yeah there was NO serial output whatsoever and I maxed out the log levels in config
<Ad0> got output as fast as the HDMI issue was resolved though
<Ad0> u-boot 2022.01 btw
<clever> Ad0: i think you need to add more debug logging to u-boot then?
f_ has quit [Remote host closed the connection]
f_ has joined ##raspberrypi-internals
<Ad0> clever, it doesn't even get to log anything it happens at the earliest possible stage I think `
<Ad0> also my logging config is this https://pastebin.com/3jZU9nKL
<clever> Ad0: it may be that u-boot tries to get a framebuffer before printing things
<clever> you need to edit the code, to log even earlier
<Ad0> haha
<Ad0> I got around it with the hotplug and it seems to be semi-common
<clever> id say that is a bug in u-boot
johnjaye has quit [Ping timeout: 264 seconds]