Odroid M2 16G

[Kasnoa]

 

Because i need a more recent kernel than 5.10 on my odroid m2, i tried armbian.

i searched for the nearest model and i manage to find Radxa Rock 5C (rocky 3588s2)
i flash emmc with Bleeding edge images with Armbian Linux v6.11/ Debian 12 (Bookworm)Minimal / IOT for the rock 5c
 

in /boot/armbianEnv.txt i changed just one line after installation :

fdtfile=rockchip/rk3588s-odroid-m2.dtb

 

and after a final apt upgrade i can run version 6.12.1-edge-rockchip-rk3588 of the kernel.

 

for now it seems fine to me.

 

[Solskogen]

I'm not sure if you're Jidea on the odroid forums, but I'll reply here as well.

Changing the ftdfile line does not work on my M2. If I change the default, I'm only getting a black screen.

I can still access the machine on ssh to revert it.

[Nicola Zilio]

I would also be interested in, maybe official :), support for this board. What would the procedure be for that?

[Werner]

https://docs.armbian.com/Process_Contribute/

https://docs.armbian.com/User-Guide_Board-Support-Rules/

 

[Walter Zambotti]

@Solskogen

 

You didn't mention whether you also did the final apt upgrade after changing the line /boot/armbianEnv.txt.

 

Did you?

[Solskogen]

I did, but someone on the odroid forum have created a own odroid m2 config file, so I'm using that for now. Everything seem to work just fine except hdmi sound

[Solskogen]

https://github.com/armbian/build/pull/7828

[ysfm]

Hello.
Is it possible to add Type C display alt mode support?

https://lore.kernel.org/linux-rockchip/20250223113036.74252-1-andyshrk@163.com/
https://patchwork.kernel.org/project/linux-arm-kernel/patch/20250312104214.525242-7-andyshrk@163.com/

 

 

****The Display Port driver is not included in 6.14. So we will have to wait now.

Edited March 28 by ysfm
I edited the message because I could not delete it.

[Walter Zambotti]

Testing the M2 16G with trunk 90 (Kernel 6.15) & trunk 38 (Kern 6.14.8) and the USB-C OTG port isn't working.

 

[  +0.245948] usb 7-1: new full-speed USB device number 2 using xhci-hcd
[  +0.124258] usb 7-1: device descriptor read/64, error -71
[  +0.227984] usb 7-1: device descriptor read/64, error -71
[  +0.223715] usb 7-1: new full-speed USB device number 3 using xhci-hcd
[  +0.124295] usb 7-1: device descriptor read/64, error -71
[  +0.223803] usb 7-1: device descriptor read/64, error -71
[  +0.104107] usb usb7-port1: attempt power cycle
[  +0.395844] usb 7-1: new full-speed USB device number 4 using xhci-hcd
[  +0.000112] usb 7-1: Device not responding to setup address.
[  +0.203891] usb 7-1: Device not responding to setup address.
[  +0.203946] usb 7-1: device not accepting address 4, error -71
[  +0.000609] usb 7-1: WARN: invalid context state for evaluate context command.
[  +0.119353] usb 7-1: new full-speed USB device number 5 using xhci-hcd
[  +0.000118] usb 7-1: Device not responding to setup address.
[  +0.204373] usb 7-1: Device not responding to setup address.
[  +0.207473] usb 7-1: device not accepting address 5, error -71
[  +0.000613] usb 7-1: WARN: invalid context state for evaluate context command.
[  +0.000109] usb usb7-port1: unable to enumerate USB device
[ +30.217458] usb 7-1: new full-speed USB device number 6 using xhci-hcd
[  +0.123993] usb 7-1: device descriptor read/64, error -71
[  +0.231951] usb 7-1: device descriptor read/64, error -71
[  +0.223935] usb 7-1: new full-speed USB device number 7 using xhci-hcd
[  +0.120028] usb 7-1: device descriptor read/64, error -71
[  +0.224108] usb 7-1: device descriptor read/64, error -71
[  +0.103939] usb usb7-port1: attempt power cycle
[  +0.396008] usb 7-1: new full-speed USB device number 8 using xhci-hcd
[  +0.000139] usb 7-1: Device not responding to setup address.
[  +0.203807] usb 7-1: Device not responding to setup address.
[  +0.207853] usb 7-1: device not accepting address 8, error -71
[  +0.000608] usb 7-1: WARN: invalid context state for evaluate context command.
[  +0.119394] usb 7-1: new full-speed USB device number 9 using xhci-hcd
[  +0.000140] usb 7-1: Device not responding to setup address.
[  +0.204031] usb 7-1: Device not responding to setup address.
[  +0.203926] usb 7-1: device not accepting address 9, error -71
[  +0.000796] usb 7-1: WARN: invalid context state for evaluate context command.
[  +0.000293] usb usb7-port1: unable to enumerate USB device
[Jun 2 19:50] usb 7-1: new full-speed USB device number 10 using xhci-hcd
[  +0.123926] usb 7-1: device descriptor read/64, error -71
[  +0.116517] xhci-hcd xhci-hcd.7.auto: remove, state 4
[  +0.000011] usb usb8: USB disconnect, device number 1
[  +0.000280] xhci-hcd xhci-hcd.7.auto: USB bus 8 deregistered
[  +0.000009] xhci-hcd xhci-hcd.7.auto: remove, state 1
[  +0.000004] usb usb7: USB disconnect, device number 1
[  +0.055430] usb usb7-port1: attempt power cycle

 

Same USB-C device (CCD camera) tested and working in the USB-3 port.

Edited Wednesday at 01:24 AM by Walter Zambotti

[Walter Zambotti]

After the last update/upgrade USB BUS 7 has completely disappeared!  So no life at all on the USB-C port.  The following packages were upgraded :

 

linux-dtb-edge-rockchip64, armbian-bsp-cli-odroidm2-edge, linux-image-edge-rockchip64, linux-u-boot-odroidm2-edge, armbian-firmware

 

I suspect linux-dtb-edge-rockchip64 is not the M2 specific package and it has over written the dtb.

 

Also I can't seem to install the kernel headers from armbian-config.  It appears to go through the motions but nothing is installed.

 

Also where can I find a documentation on what each device overlay (in armbian-config) is for?

Edited Wednesday at 02:31 PM by Walter Zambotti