Booting on Helios64 with arm64 image

Troubleshooting
21

Just to follow on from that…
Is it possible the device tree on/for your board isn’t setting the serial console correctly?

openSUSE (and most other systemd based systems) will use the “stdout-path” parameter in the device tree to set this, but it appears this was only done for the Helios64 very recently

Maybe try adding console=ttyS2,1500000 to your kernel parameters.

4 Likes
22

Hi Matthew

Thanks, I’ve pushed the changes to my Pi, however I got the same non-result. I tried images with the following

kernelcmdline="plymouth.enable=0 rd.kiwi.oem.maxdisk=5000G console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1"

and

kernelcmdline="plymouth.enable=0 rd.kiwi.oem.maxdisk=5000G earlycon console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1"

Could the issue have to do with a wrong u-boot? I’ve seen from the armbian patches that Helios64 (or more specifically the Rockchip64 3399) uses a rather specific u-boot config. [1-3]

If they are relevant, how would I know if these patches are included in the kernel used by Leap15.3? And if they are not, how do I build the kernel with these patches and include it on a image?

[1] https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-rockchip64/add-board-helios64.patch
[2] https://github.com/armbian/build/tree/master/patch/u-boot/u-boot-rockchip64
[3] https://github.com/armbian/build/commit/86abac1fd4e169712a44d245cf7adef4ee17c420

1 Like