Just got an ODroid M1S (8GB), tried current community build, and found it wasn't working (Armbian_community_26.11.0-trunk.120_Odroidm1s_resolute_current_6.18.60_minimal.img.xz).

So, a thread while I'm debugging if anyone's interested. Lets see how far I get.

boot_fail.txt

Found this thread by @Mortimer2003 , who probably deserves some kudos for identifying some fairly major issues, but were never submitted for PR.

Looks like things have been broken for a bit in the build. So, let's take a swing at it: https://github.com/tparys/build/tree/odroid_m1s

First up is the load address. The rk35xx family boot script loads data at 0x9000000, but doesn't seem to be valid for M1S?

Adding a custom boot script that loads 0xc000000 gets us booting and to first boot login.

But Ethernet isn't working (as identified).

rk_gmac-dwmac fe010000.ethernet eth0: cannot attach to PHY (error: -ENODEV)

4 hours ago, tparys said:

Adding a custom boot script

FYI. Might come handy here.
@djurny made generalization / templating of boot scripts. If only loading address is different, it would be cleaner then cp whole script. In case you find time to look into. Not a blocker.

generalization / templating of boot scripts

Any pointers on which boards use this? I'm sure I'll find it, but might save me reading though a few dozen family configs.

In the meantime, I've integrated the above Ethernet tweak as a rockchip64 patch. I'm assuming something moved in the kernel and the M1S's .dts didn't get updated.

   /_\  _ _ _ __ | |__(_)__ _ _ _ ___ _  _ _ _  ___ / _|/ _(_)__(_)__ _| |
  / _ \| '_| '  \| '_ \ / _` | ' \___| || | ' \/ _ \  _|  _| / _| / _` | |
 /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|   \_,_|_||_\___/_| |_| |_\__|_\__,_|_|
                                                                          
 v26.11 rolling for ODROID M1S running Armbian Linux 6.18.62-current-rockchip64

 Packages:     Ubuntu stable (noble)
 Updates:      Kernel upgrade enabled and 7 packages available for upgrade 
 Support:      DIY (custom image)
 IPv4:        (LAN) 10.42.0.119 (WAN) ---.---.---.---

Alright, found a boot.cmd tweak in the config for dshanpi-r1, and followed that. Looks like it's working as expected, so no need for duplicate bootscript.

Other basic functions appear to be working.

• SD Card

• USB

• HDMI

• NVME

Initial PR submitted to get CSC images working. Now to poke at GPIO headers.