After using the O6N device tree, it still fails to boot

[CodeChenL]

I am a systems development engineer at Radxa, and I am very interested in this project.
In my spare time, I wrote sky1-orion-o6n.dts and built sky1-orion-o6n.dtb, and tried to start linux-sky1 but the startup failed.
This is log: https://gist.github.com/CodeChenL/2da9ac4cd3b28c345d3077999311c007?permalink_comment_id=5921460#gistcomment-5921460
Do you have any ideas?

[CodeChenL]

@lwzhenglittle You might be interested

[CodeChenL]

My bootloader is EmbLoader, this is my EFI boot entry:

root@RadxaOrionO6N:/home/radxa# cat /boot/efi/loader/entries/RadxaOS-6.18.2-sky1.conf
title      Debian GNU/Linux 12 (bookworm)
version    6.18.2-sky1
sort-key   debian
options    root=UUID=bca6769e-da9c-4902-99c1-2f098dfc82c8 console=ttyAMA0,115200n8 earlycon=pl011,0x040d0000 quiet splash loglevel=4 rw earlycon consoleblank=0 console=tty1 coherent_pool=2M irqchip.gicv3_pseudo_nmi=0 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 kasan=off acpi=off
linux      /RadxaOS/6.18.2-sky1/linux
initrd     /RadxaOS/6.18.2-sky1/initrd.img-6.18.2-sky1
devicetree     /RadxaOS/6.18.2-sky1/sky1-orion-o6n.dtb

[lwzhenglittle]

I tried boot this using acpi force and i got this dmesg:

https://pastebin.ubuntu.com/p/7QCgK42H3J/

My kernel cmdline is:

linux	/boot/vmlinuz-6.18.2 root=... ro arm-smmu-v3.disable_bypass=0 cma=640M pcie_aspm=off splash acpi=force loglevel=7 kasan=off $vt_handoff nomodeset

I will try your dts later.

[lwzhenglittle]

I can get some kernel log using your dts, but i cannot boot to the system either. It seems that some devices failed to init and caused kernel panics.

I will buy a usb to uart converter and get these logs.

I think the main difference is I am using ubuntu's GRUB, not the loader provided by cix.

[Entrpi]

I compiled latest GRUB from git on my dev system, but I don't believe that's necessary. Please do share when you get UART logs from DT boot.

[Entrpi]

I created some tools to help with this. Can you check and run the scripts here? https://github.com/Sky1-Linux/acpi-to-dts-tools

[CodeChenL]

I compiled latest GRUB from git on my dev system, but I don't believe that's necessary. Please do share when you get UART logs from DT boot.

The log I provided at the beginning is the uart log, but it is using embloader (a systemd-boot alternative)

[CodeChenL]

I created some tools to help with this. Can you check and run the scripts here? https://github.com/Sky1-Linux/acpi-to-dts-tools

The dts generated with it lacks the label, pinctrl definition, and pwm controller node for the gpiochip node

[CodeChenL]

It's worth mentioning that I provided the dts I wrote at the beginning.
It is the modification I made to the o6 device tree you wrote, based on the differences between o6 and o6n device treein the Android SDK. It should be 99% correct.

[Entrpi]

Can you try with this DTS? https://github.com/Sky1-Linux/linux/blob/main/arch/arm64/boot/dts/cix/sky1-orion-o6n.dts

[Entrpi]

Issue: Boot hangs with NOTICE: Send CMD: 0x82000002 loop - this is TF-A waiting for PM core response.

My root cause hypothesis: The em05_modem_power and em05_modem_reset regulators had regulator-boot-on which forces early GPIO/pinctrl initialization. This likely blocked on SCMI clock init before the mailbox was ready.

Fix (commit 19aa5b0ba98f2): Removed regulator-boot-on from modem regulators. They still have regulator-always-on so they'll be enabled when the driver loads.

Test options:

1. Pull latest and rebuild the DTB
2. Or add clk_ignore_unused pd_ignore_unused to kernel cmdline with old DTB
3. Or try O6 DTB on O6N hardware to confirm it's DTB-specific

My grub:

menuentry '0 Mainline 6.18 dev (NVMe)' {
    devicetree /SKY1-ORION-O6-6.18-mainline-cix.DTB
    linux /IMAGE-6.18-mainline-cix \
        loglevel=7 \
        console=tty0 \
        console=ttyAMA2,115200 \
        efi=noruntime \
        earlycon=efifb \
        earlycon=pl011,0x040d0000 \
        acpi=off \
        clk_ignore_unused \
        linlon_dp.enable_fb=1 \
        linlon_dp.enable_render=0 \
        fbcon=map:01111111 \
        panic=30 \
        root=PARTUUID=YOUR-UUID-HERE rootwait rw
}

You can also look at my early commits to the project to see how I handled early board bringup by simplifying and reducing variables in DT.

[HmnSn]

Can you try with this DTS? https://github.com/Sky1-Linux/linux/blob/main/arch/arm64/boot/dts/cix/sky1-orion-o6n.dts

I tried this dts and booted with the following grub parameters

loglevel=7 console=tty0 console=ttyAMA2,115200 efi=noruntime earlycon=efifb earlycon=pl011,0x040d0000 acpi=off clk_ignore_unused linlon_dp.enable_fb=1 linlon_dp.enable_render=0 fbcon=map:01111111 panic=30 rootwait rw

I got this log, and the system automatically rebooted.
https://pastebin.ubuntu.com/p/CscBXtC7gT/

[CodeChenL]

Can you try with this DTS? https://github.com/Sky1-Linux/linux/blob/main/arch/arm64/boot/dts/cix/sky1-orion-o6n.dts

I tried this dts and booted with the following grub parameters

loglevel=7 console=tty0 console=ttyAMA2,115200 efi=noruntime earlycon=efifb earlycon=pl011,0x040d0000 acpi=off clk_ignore_unused linlon_dp.enable_fb=1 linlon_dp.enable_render=0 fbcon=map:01111111 panic=30 rootwait rw

I got this log, and the system automatically rebooted. https://pastebin.ubuntu.com/p/CscBXtC7gT/

After adopting @Entrpi suggestion, my results are basically the same as yours, and I found that the HDMI interface has more information:

output.mp4

[lwzhenglittle]

Using latest commit bbdec4a, i got kernel log like this : https://pastebin.ubuntu.com/p/CscBXtC7gT and it reboot automatically.

Sry the correct log is : https://pastebin.ubuntu.com/p/fNQHWYftMK/