pixdrift

It seems I have confused legacy.. when I built 'current' it's 6.6.12, not sure if 6.1 is still used? as 'legacy' build for zero2 was 4.9.318 I will need to take another look at how patches are done for legacy, or if we just don't support it.

Thanks @Stephen Graf, my branch has been updated with mainline and I have added the patches for both 'legacy' (6.1) and 'current' (6.6) kernels, although I haven't yet created test builds. I will create builds and test zero2, if you can cover off zero3? https://github.com/pixdrift/armbian_build/tree/zero23_spi_menufix In unrelated updates, I also received some mail so I now have the HDMI audio splitter for potentially testing the HDMI audio patch (but the size of the patch is a little daunting), and the Sipeed Longan (not related to this thread other than it's also H618) looks like a great board!

Hi sander, welcome to the forum! Thanks for introducing yourself, always good to know there are others around willing to assist with testing I'd say you're in the right place as I think Zero2W is where (at least my) focus will shift to next, just a bit early as we don't have anything to test. As has been discussed in the thread, @Gunjan Gupta did some preliminary work in his own repo to get the Zero2W working, but I haven't had time to go through it and prepare a more formal patch for Armbian. https://github.com/viraniac/armbian_build/tree/zero2w This repo is provided with no support, as it's in heavy development, but if you wanted something to work with, this may help.

Agreed to leave the LEDs as they are for now. As for the PR, given that Zero2 is a supported board, we should probably also add this change to the other kernels the Zero2 supports (and test), ie. legacy and current. https://github.com/armbian/build/blob/e73c0b6514db5c55d896e62112f578214e7f30cb/config/boards/orangepizero2.conf#L7 We can use the merge request I have and stage it as a PR, or you're more than welcome to create your own (even off mine if you like), let me know how you want to proceed.

Possibly, but the USB end isn't touching anything, and it's consistent/reliable (ie. it impacts every boot). I assume it's something to do with the design of the converter. Anyway, it's a known quantity now so I can rule out those issues. From my perspective, everything is testing successfully on the Zero2 so wondering if we should discuss merging or is there more you want to focus on? I was thinking as I was working with the Zero2 that it might be nice to have an LED enable/disable (or function change) in the hardware menu? Not sure if others would find that useful.

Well.. after some extended testing.. I finally got to the bottom of the issue. It wasn't related to the SD cards at all after all, and it also wasn't related to the heat (managed to push it to 84c+ and then reboot), it is my serial USB converter. So I have discovered that if my serial/USB converter is plugged in to the Zero2 serial pins, but not connected to a PC, the Orange Zero2 fails to boot, and gets 'stuck'. When I plug the serial converter in when it's in this state (just a red LED) I get a u-boot prompt. From here if I issue 'reset' with the serial converter plugged in to the PC (to issue the command) the board reboots cleanly, no issues. This is the same behaviour for mainline and my SPI fix branch in github, so it looks to be strange behaviour if it can see the USB serial converter on the line and it doesn't appear to have anything to do with the patches (apologies for the confusion). The USB serial converter (I have a few, but this is the most reliable) is a 'CP2102 USB to UART Bridge Controller' Not sure what to make of this information, but hoping others may have some thoughts?

I will try and re-create the issue today, and get a serial log. Hoping the summer heat is on my side.