<clever>
if that goes to gnd, the SoC just completely halts everything its doing, including dram refresh
<clever>
when released, it will start booting from scratch
<clever>
GLOBAL_EN is the reset pin for the power regulator
<clever>
if that goes low, the 1.8v and 3.3v rails will entirely die
delroth has quit [Quit: WeeChat 2.8]
<elvishjerricco>
Hm. I don't think I have anything to act as a button... wonder if I can find something janky
<clever>
i sometimes solder a 2x1 header onto there, and then just grab it with tweezers
apache8080 has quit [Ping timeout: 260 seconds]
delroth has joined #nixos-aarch64
bennofs__ has joined #nixos-aarch64
bennofs_ has quit [Ping timeout: 246 seconds]
h0m1 has quit [Quit: WeeChat 3.1]
h0m1 has joined #nixos-aarch64
superherointj has quit [Quit: Leaving]
h0m1 has quit [Ping timeout: 246 seconds]
h0m1 has joined #nixos-aarch64
<elvishjerricco>
clever: The other day you said u-boot/cmd/log.c could help recover logs after the fact. It's pretty easy to enable. CONFIG_LOG=y CONFIG_CMD_LOG=y (not sure if both are necessary but whatever)
<elvishjerricco>
How were you expecting to use this to recover the logs?
<clever>
i think the problem is that i didnt enable CONFIG_CMD_LOG
<clever>
and didnt bother going back to it after it failed
<elvishjerricco>
I'm not sure how to use this command: `log rec <category> <level> <file> <line> <func> <message>`
<elvishjerricco>
or if that's even the right command to use
<elvishjerricco>
Oh no that's just for outputting new log messages
h0m1 has quit [Ping timeout: 245 seconds]
h0m1 has joined #nixos-aarch64
<elvishjerricco>
clever: Btw, is this usb issue present on all pi 4 variants? Or just the cm4 and pi 400?
<clever>
not sure
<clever>
from what ive seen in the source/config, i suspect usb just doesnt work at all
<elvishjerricco>
I know the kernel needed a patch to support the pi 4's usb. Maybe u-boot needs to port that
<elvishjerricco>
Well I noticed that in the first reply, they get the u-boot messages: `starting USB...` and `No working controllers found`
<clever>
and then it boots normally
<clever>
so the /boot must be on non-usb storage
rajivr has joined #nixos-aarch64
quinn_ has quit [Ping timeout: 240 seconds]
quinn has joined #nixos-aarch64
orivej has joined #nixos-aarch64
alexeyan1 has joined #nixos-aarch64
alexeyan has quit [Read error: Connection reset by peer]
orivej has quit [Ping timeout: 240 seconds]
bennofs__ has quit [Read error: Connection reset by peer]
bennofs_ has joined #nixos-aarch64
bennofs has quit [Remote host closed the connection]
bennofs has joined #nixos-aarch64
bennofs has quit [Client Quit]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
fps has quit [Quit: leaving]
zuh0 has quit [Quit: Idle for 30+ days]
davidak[m] has left #nixos-aarch64 ["User left"]
sysadmin has quit [Ping timeout: 260 seconds]
alpernebbi has joined #nixos-aarch64
Raito_Bezarius has left #nixos-aarch64 ["WeeChat 3.0"]
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Remote host closed the connection]
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Client Quit]
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Client Quit]
orivej has quit [Ping timeout: 246 seconds]
alpernebbi has quit [Read error: Connection reset by peer]
alpernebbi has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has joined #nixos-aarch64
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Client Quit]
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Client Quit]
orivej has quit [Ping timeout: 260 seconds]
monk has left #nixos-aarch64 ["Error from remote client"]
FantasyCookie174 has left #nixos-aarch64 ["User left"]
alpernebbi has quit [Quit: alpernebbi]
monk has joined #nixos-aarch64
taktoa[c] has quit []
blueberrypie has quit [Quit: leaving]
blueberrypie has joined #nixos-aarch64
fooker has quit [Quit: WeeChat 2.8]
rajivr has quit [Quit: Connection closed for inactivity]
aleph- has quit [Quit: WeeChat info:version]
orivej has joined #nixos-aarch64
monk has left #nixos-aarch64 ["Error from remote client"]
apache8080 has joined #nixos-aarch64
blueberrypie has left #nixos-aarch64 ["leaving"]
orivej has quit [Ping timeout: 260 seconds]
bennofs_ has quit [Read error: Connection reset by peer]
bennofs has joined #nixos-aarch64
zupo has joined #nixos-aarch64
<elvishjerricco>
samueldr: Do you have a pi4?
<samueldr>
yeah
<samueldr>
two in fact
<samueldr>
but the early revision
<samueldr>
2GiB and 4GiB
<samueldr>
in retrospect I probably should have gotten only the 2GiB and waited for the 8GiB
<samueldr>
but they said there was no plan for it early on :(
<elvishjerricco>
Have you tested whether tow-boot works with the usb 2.0 port on it?
<samueldr>
tested all usb type-A ports
<samueldr>
it works
<samueldr>
(IIRC)
<samueldr>
been a couple weeks
<elvishjerricco>
alright. And I'm guessing there's no difference between the usb controllers between the revisions?
<samueldr>
¯\_(ツ)_/¯
apache8080 has quit [Ping timeout: 240 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<elvishjerricco>
Well, I decided to try just booting an sd image (as built by cross-system) on a usb drive, and it didn't even find something to boot from the usb drive
<elvishjerricco>
samueldr: Well I don't want to write an overlay, I want to apply one of the overlays from raspberrypi/firmware/boot/overlays onto the cm4 dtb just to see what happens :P
<samueldr>
yeah, you'll have to pick their dts file and copy it like that since it's likely it won't apply with our tooling
<apache8080>
for the buildLinux derivation is there anyway to just build the dtbs?
<elvishjerricco>
`Failed to apply '/build/files/dwc2-overlay.dtbo': FDT_ERR_NOTFOUND`
<elvishjerricco>
Mhmm...
<samueldr>
elvishjerricco: applying on top of mainline?
<samueldr>
that won't work
<samueldr>
you have to apply on top of the vendor kernel
<samueldr>
(linux_rpi4)
<samueldr>
also, it might try to apply to the wrong boards without `filter = "bcm2711-rpi-*.dtb";`
<elvishjerricco>
samueldr: I'm not using the nixos stuff. I'm just trying to get a tow-boot image with the dwc overlay preapplied
<elvishjerricco>
preapplied to the cm4 dtb
<samueldr>
hm, couldn't say then
<samueldr>
FDT not found is re-used for a couple errors I think
<samueldr>
but it might be that it can't find the symbols
<samueldr>
the desired &label
<elvishjerricco>
Hm. Well, rather than copying the source and compiling it, I just took the overlay binary and cm4 dtb both from raspberrypifw and tried to apply it with fdtoverlay, and still got FDT_ERR_NOTFOUND
<elvishjerricco>
so that doesn't sound good :P
<samueldr>
oh
<samueldr>
use `dtc` on both and check `compatible` for `/`
<samueldr>
I suspect it might check?
<samueldr>
there was something in the issue tracker or one PR about hat
<samueldr>
that*
<samueldr>
that maybe fdtoverlay cannot be used for this use case when compatible strings don't match
<elvishjerricco>
samueldr: well when I was compiling a dtbo from source I made sure to set the compatible to match
<elvishjerricco>
but to check, I run `fdtget -t s $dtb / compatible` right?
<samueldr>
that's an option
<samueldr>
using `dtc` on a compiled binary poops out the equivalent source too
<samueldr>
(not 100% sure about fdtget usage, but smells right)
<elvishjerricco>
For the dtb: `compatible = "raspberrypi,4-compute-module\0brcm,bcm2711";`
<elvishjerricco>
and for the dtbo: `compatible = "brcm,bcm2711";`
<elvishjerricco>
That is, after decompiling, changing 2835 to 2711, and recompiling
<samueldr>
and it won't apply?
<elvishjerricco>
right
apache8080 has quit [Ping timeout: 246 seconds]
<samueldr>
couldn't say
<samueldr>
do like me, scream into the void^W IRC^W Matrix about how software that doesn't say why things fail is terrible
<elvishjerricco>
lol
<elvishjerricco>
Maybe I should try asking on #u-boot...