ROOBI OS was not installed from factory and flashing it did not work - however was able to install the Radxa Version of Debian 12 Bookworm onto a MicroSD and everything booted fine – also installed this same OS onto the eMMC and it also boots fine as well took it a step further and installed same OS on a SATA drive connected to the M.2 M Hexa SATA Adapter also booted from this location as but non of these installs could locate the SATA connected to the M.2 E Key. Connecting 12 SATA drives to 2 M.2 M Hexa SATA Adapters and all those drives were found with no issues.
There is very little info for installing this breakout board on the Rock 5 itx+ and there are no overlays for this device were found running rsetup.
Anyone have this issue and found how to fix?
Note: This board is installed on a full size ATX case with 700W power supply and the board is powered from the 40 pin connector. All SATA drives are connected from this power supply as well via the standard SATA power connectors
or (what I do) use Tianocore EDK2 UEFI v1.1 and in the setup select SATA instead PCIe2x1 for that lane.
ROCK5ITX+ is quite new, so I think one of the rockchip-rk3588-sata?.dtbo should work. Look in blockdiagram/schematics which multiphy/lane is it, might be different from ROCK5B. I always forget the number.
Alternative is to keep function on M.2 E-key multiphy PCIe2x1 and order a E-Key adaptor with own/extra SATA chip. I have one, is 2-port JM chipset, but unused as I only need 1 SATA port and extra chip adds power consumption. Which might not matter at all for ITX board, but I use battery operation as well.
Is this about the passive M.2 E-key to SATA adapter? I have it working just fine with u-boot and mainline kernel v7.0, but I’m not booting from it.
This is the overlay .dtso that I wrote:
/dts-v1/;
/plugin/;
&pcie2x1l0 {
status = "disabled";
};
&sata1 {
status = "okay";
};
To use it, you need to (1) compile the base device tree file for the board with symbols included (the linux kernel “make” does not do that), (2) compile this overlay, also with symbols, and then (3) instruct u-boot to load them. I don’t know if Radxa u-boot is capable of applying the overlay. In case it doesn’t, then you need to (4) compile and install your own u-boot OR you can forget about (1)-(4) and insert modifications above directly into the base device tree, recompile it (symbols not needed) and replace the file u-boot loads.
This is how you compile a device tree with symbols. It took me a while to find out how. It seems the kernel devs won’t respect the device tree specs they themselves wrote. The .dts needs pre-processing by cpp to convert it into specs-compliant device tree code. The dtc -@ parameter adds symbols.