mfc

Hmm, I did recompile to make the change effective. While playing with it, /boot/boot.cmd got reset to default values at some point. I supected the armbian-config script (probably while enabling some device tree overlay). I could not reproduce it later on, but was a bit afraid of this happening at some point in time in "productive" use. Decided for me to go with booting via SD card until I find a better solution... Hmm, they mostly suggest not to use armbian, which would be a pity, though

I have recently managed to get SPI boot to USB SSD working on my Odroid N2+. However, to get there, I had to manually set setenv rootdev "/dev/sda1" in my /boot/boot.cmd With that set, SPI boot works. However, obviously I should not set it manually there, and the setting gets overwritten by armbian-config. My understanding is, that I should let boot.cmd unchanged (rootdev "/dev/mmcblk0p1") and armbianEnv.txt should do its magic, but the rootdev setting in armbianEnv.txt is simply ignored upon SPI boot and it fails to boot, as it tries to load the root fs from SD card... Any pointers, what might go wrong here or how to persist the boot.cmd change?

Adding more info here, would be glad if anyone more knowledgeable than me could point me in the right direction. I just updated to the latest Armbian 22.11.4 Bullseye with Linux 6.0.13-meson64 and enabled uartA and uartC overlays via armbian-config (and confirmed they are set in armbianEnv.txt). Still I don't get the uartA to show up, dmesg has only ff803000.serial: ttyAML0 at MMIO 0xff803000 (irq = 14, base_baud = 1500000) is a meson_uart which is uartC. Anything I might have missed or is this a bug? Is anyone around who could give me hint what to look for? I'm new to the topic, haven't used overlays before.. Maybe @martinayotte, I saw that you could help another user in an older thread for the Odroid C2 with a serial port issues, any ideas? Highly appreciate any help 🙂

Did you get any further with your issue? I'd like to use uartA, but can't figure out how. dmesg does not show anything, can't even find out which /dev/tty... device could be correct...