Is there a chance for RK3588s (aarch64) to run kaios ?

[yorkfly]

Is your feature request related to a problem? Please describe.

 There are  Nvidia AGX Orin and RaspberryPi supported in the ARM hardware list of kairos , are the any chance for RK3588s to run kairos?
* I have RaspberryPi4 and a RK3588s box, now I can use kairos on RaspberryPi 4, thanks for your hard works.*
 *I also want to see kairos runing on the box: RK3588s*

Describe the solution you'd like

A new model for RK3588s like Nvidia AGX Orin Describe alternatives you've considered

Additional context

[jimmykarily]

@yorkfly we don't have a board like that around. Feel free to work on it and we can provide some guidance and some tip based on the work that we did for nvidia and qcs6490 (qualcomm).

[yorkfly]

I have a try, but blocked by the bootefi in uboot. (try in u-boot mode, not UEFI mode) The following is error message:

=> bootefi - Boots an EFI payload from memory

Usage: bootefi [fdt address]

• boot EFI payload stored at address . If specified, the device tree located at gets exposed as EFI configuration table.

=> bootefi 0x00400000 0x08300000

Starting EFI application at 00400000 ...

Scanning disk ramdisk-ro.blk... "Synchronous Abort" handler, esr 0x96000010

• Reason: Exception from a Data abort, from current exception level
• PC = 00000000002c6188
• LR = 00000000002474a8
• SP = 00000000eb7f94c0
• ESR_EL2 = 0000000096000010
• Reloc Off = 00000000ed9f7000

x0 : 00000000eb7f96c0 x1 : 0000000000000000 x2 : 0000000000000200 x3 : 0000000000000000 x4 : 0000000000000200 x5 : 0000000000000020 x6 : 000000000000000d x7 : 00000000edce82f8 x8 : 00000000eb7f9978 x9 : 0000000000000008 x10: 00000000ffffffd0 x11: 0000000008300000 x12: 0000000000000000 x13: 0000000000000200 x14: 0000000000000007 x15: 0000000000000021 x16: 00000000edc3e47c x17: 00000000ebc5d8b8 x18: 00000000eb7ffce8 x19: 0000000000000001 x20: 00000000ebbf41d0 x21: 00000000ebbf41d0 x22: 00000000edcf34b4 x23: 00000000edd05221 x24: 0000000000000003 x25: 0000000000000000 x26: 0000000000000000 x27: 0000000000000000 x28: 00000000ebc7a2a0 x29: 00000000eb7f96a0

Call trace: PC: [< 002c6188 >] LR: [< 002474a8 >]

Stack: [< 002c6188 >] [< 002333f8 >] [< 002314e0 >] [< 00231a48 >] [< 002a8d10 >] [< 00209e74 >] [< 0020a118 >] [< 0022ffa4 >] [< 00218600 >] [< 002187b4 >] [< 00218ce8 >] [< 0022f668 >] [< 00216ce0 >] [< 002194c8 >] [< 002acc30 >] [< 00219730 >] [< 00201da8 >]

Copy info from "Call trace..." to a file(eg. dump.txt), and run command in your U-Boot project: ./scripts/stacktrace.sh dump.txt

[areitz86]

@yorkfly we don't have a board like that around. Feel free to work on it and we can provide some guidance and some tip based on the work that we did for nvidia and qcs6490 (qualcomm).

I hope that I have some time next year. I could provide you guys a rock 5b for a couple of months, if you want to work on this one.

[jimmykarily]

@areitz86 thanks for offering this option! If there is time available to work on this we'll let you know.