00:37 <sdfgsdfs> maybe not exactly a linux question, but I have this orangepi zero3 that doesn't start at all, not even the power LED comes on, if I try to boot with an SD card in. the SD card has armbian on it, and I saw a forum post saying that the wrong version of armbian could cause that, but how??? why won't it get to uboot regardless?

00:39 <sdfgsdfs> does sunxi not have its bootloader integrated with the SoC itself?

00:41 <sdfgsdfs> https://pastebin.com/raw/j4rpWQa9

00:42 <sdfgsdfs> seems to function normally if booted without the SD card

01:08 <tokyovigilante> sdfgsdfs: are you sure the SD has u-boot on it? the SoC bootloader is limited to enabling FEL or just jumping to the correct SD card sector to load AFAIK

01:09 <sdfgsdfs> oh i didnt know i needed to supply uboot

01:10 <sdfgsdfs> FEL==Front End Loading>

01:10 <sdfgsdfs> ?*

01:12 <sdfgsdfs> nvm reading https://linux-sunxi.org/BROM

16:48 <apritzel> sdfgsdfs: the SoC itself just contains the BootROM, which just checks various media (SD card, eMMC, SPI flash) for a specific signature, loads some KBytes of code from there into SRAM and executes that

16:49 <apritzel> sdfgsdfs: and while the OPi Zero3 has SPI flash, where you can put U-Boot into, the SD card takes precedence in this BROM routine, so if it finds a valid signature, it will load and execute the code from the SD card

16:50 <apritzel> Armbian always bundles bootloader and kernel and rootfs, so you load everything from the SD card in your case

16:51 <apritzel> you could put mainline U-Boot to the SPI flash, then just have a normal SD card (without the magic signature), with a kernel and rootfs, and then it would boot from SPI flash and load the rest from the SD card

17:04 <macromorgan> apritzel: I can't speak to the phy pin mapping, I guess that's a you/Jernej question. For the device tree do you just want me to drop the OF_UPSTREAM (as well as prune the defconfig) and resubmit, or should I wait for your mainline piece to be finished?

17:07 <apritzel> well, there is no real rush: I won't push those changes for v2024.10 anyway

17:07 <apritzel> macromorgan: if you want a clean and functional series on the list now, I'd suggest you stick to the arch/arm/dts tree for now - I updated that in mainline, to pull the .dts files in

17:08 <apritzel> same with bootstd, just stick to what's in the tree now, and you will get the update for free

17:08 <apritzel> and don't worry, I can take care of adjusting your series to whatever landed before, when it comes to merging

17:18 <macromorgan> okay

17:18 <macromorgan> all that matters is cherry picking 2 commits, and I can do that to both the mainline and u-boot DTS if needed

17:19 <macromorgan> as far as the RAM the only commentary I can provide is "I know this works for me". I guess I'll wait for more comments there.

17:38 <apritzel> yeah, I am as clueless as you, I guess. I will try to find some time to run the code on the other H616 boards I have

18:39 <macromorgan> okay, I guess I'll give it a day and then post my fixes. I switched back to a U-Boot tree and pruned the defconfig so I hope that works.

23:00 <apritzel> macromorgan: you mentioned a size problem in U-Boot for the Anbernic boards, where is that, exactly? In the SPL or in U-Boot proper?