Rk3582 soc broken ip node check

amazingfate · July 13, 2024, 4:17am

I have written a shell script to check which soc node is broken on rk3582 soc.

You have to flash an armbian 5.10 legacy image of rock5c because it has modified uboot to unblock all good ip cores. If you flash 6.1 vendor image, you will get gpu enabled even you have broken gpu.

How to use:

curl --silent https://cdn.haguro.top/check-rk3582.sh |bash -

Result is in Chinese, you can use google translate for your language.

Altirix · July 13, 2024, 4:08am

possible bug with your script or just some diffrence between our installs. both encoders will return NO as the device to query for me should be:

/sys/devices/platform/fdbd0000.rkvenc
/sys/devices/platform/fdbe0000.rkvenc

rather than

/sys/devices/platform/fdbd0000.rkvenc-core
/sys/devices/platform/fdbe0000.rkvenc-core

it seems only decoders have the -core suffix

the other option for people that dont want to run a script from an unknown source, you can just use journalctl -b | grep <DEVICE_PATH>

amazingfate · July 13, 2024, 4:16am

I don’t know which kernel you are using.
In the devicetree that armbian is using node name is rkvenc-core:

github.com

armbian/linux-rockchip/blob/rk-5.10-rkr6/arch/arm64/boot/dts/rockchip/rk3588s.dtsi#L4005


		reg = <0x0 0xfdbb0800 0x0 0x100>;
		interrupts = <GIC_SPI 117 IRQ_TYPE_LEVEL_HIGH>;
		interrupt-names = "irq_iep_mmu";
		clocks = <&cru ACLK_IEP2P0>, <&cru HCLK_IEP2P0>;
		clock-names = "aclk", "iface";
		#iommu-cells = <0>;
		power-domains = <&power RK3588_PD_VDPU>;
		status = "disabled";
	};


	rkvenc0: rkvenc-core@fdbd0000 {
		compatible = "rockchip,rkv-encoder-v2-core";
		reg = <0x0 0xfdbd0000 0x0 0x6000>;
		interrupts = <GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>;
		interrupt-names = "irq_rkvenc0";
		clocks = <&cru ACLK_RKVENC0>, <&cru HCLK_RKVENC0>, <&cru CLK_RKVENC0_CORE>;
		clock-names = "aclk_vcodec", "hclk_vcodec", "clk_core";
		rockchip,normal-rates = <500000000>, <0>, <800000000>;
		assigned-clocks = <&cru ACLK_RKVENC0>, <&cru CLK_RKVENC0_CORE>;
		assigned-clock-rates = <500000000>, <800000000>;
		resets = <&cru SRST_A_RKVENC0>, <&cru SRST_H_RKVENC0>, <&cru SRST_RKVENC0_CORE>;

github.com

armbian/linux-rockchip/blob/rk-6.1-rkr1/arch/arm64/boot/dts/rockchip/rk3588s.dtsi#L4157


		clocks = <&cru ACLK_RKVENC0>, <&cru HCLK_RKVENC0>;
		clock-names = "aclk", "iface";
		rockchip,disable-mmu-reset;
		rockchip,enable-cmd-retry;
		rockchip,shootdown-entire;
		#iommu-cells = <0>;
		power-domains = <&power RK3588_PD_VENC0>;
		status = "disabled";
	};


	rkvenc1: rkvenc-core@fdbe0000 {
		compatible = "rockchip,rkv-encoder-v2-core";
		reg = <0x0 0xfdbe0000 0x0 0x6000>;
		interrupts = <GIC_SPI 104 IRQ_TYPE_LEVEL_HIGH>;
		interrupt-names = "irq_rkvenc1";
		clocks = <&cru ACLK_RKVENC1>, <&cru HCLK_RKVENC1>, <&cru CLK_RKVENC1_CORE>;
		clock-names = "aclk_vcodec", "hclk_vcodec", "clk_core";
		rockchip,normal-rates = <500000000>, <0>, <800000000>;
		assigned-clocks = <&cru ACLK_RKVENC1>, <&cru CLK_RKVENC1_CORE>;
		assigned-clock-rates = <500000000>, <800000000>;
		resets = <&cru SRST_A_RKVENC1>, <&cru SRST_H_RKVENC1>, <&cru SRST_RKVENC1_CORE>;

Altirix · July 13, 2024, 4:18am

yeah, im wrong… just booted up my other 5c lite and this one has a dead gpu but both encoders and the script works as expected.

the min spec for RK3582 is one encoder core right? possible its getting renamed when theres only one?

amazingfate · July 13, 2024, 4:34am

Yes uboot has renamed the node when disabling one decoder or encoder. I have updated the check script.

Altirix · July 13, 2024, 4:34am

thanks for all your work on this

hexdump0815 · July 14, 2024, 10:02pm

@amazingfate - is there a prebuilt image with 5.10 kernel and adjusted u-boot somewhere downloadable? i’m asking as the armbian downloads seem to focus on v6.1 and mainline only.

a lot of thanks in advance and best wishes - hexdump

amazingfate · July 15, 2024, 1:57am

5.10 kernel can use exactly the same deivcetree from 6.1. There is no 5.10 prebuilt image but you can build one by yourself.

kwankiu · July 15, 2024, 5:10am

If you are interested on Arch Linux, my image have this patch applied for the CM5 and Rock 5C:
https://github.com/kwankiu/archlinux-installer/releases/tag/b07

And here is the patched u-boot package with rk3582 unlocked
https://github.com/kwankiu/archlinux-installer/releases/download/kernel/uboot-radxa-rknext_2017.09-1_arm64.deb

Gino_Accademy · July 15, 2024, 6:20pm

Sorry for the newbie question, how does OS images are created?

Thomas_P · January 11, 2025, 9:05am

@kwankiu You are the only one to provide materials for rk3582 SoC on this forum
Can you please share it as an .img or at least explain how to make it “flashable” on a SPI module?

BR

kwankiu · January 11, 2025, 11:32am

I dont have a u-boot image for SPI since neither rock 5c nor cm5 came with SPI
If you really want to flash it to an SPI module (either on rock 5c’s emmc/spi socket, or an IO board for cm5) you can try dding the u-boot img and loader file contained in the deb package linked above, but it might not be as straight forward, alternatively you can put armbian’s patch to radxa’s build tool and build SPI image following radxa’s documentation.

Or if UEFI works for you, the easiest way is to flash the UEFI EDK2 image on the SPI
https://github.com/kwankiu/edk2-rk3588/releases/tag/debug

Thomas_P · January 16, 2025, 7:08am

Thanks @kwankiu
I’m trying to achieve netbooting on my 5C lite (with a PoE hat).
The idea is to have a U-boot running on the SPI flash module handling OS files from a TFTP & NFS server.
I’ve already done that with Rpi devices.
Unfortunately, no matter the way I tried, I can’t make my board boot.

rsetup tells me it succeed -> no output when powering on and fixed green and blue LEDs
dding idbloader + u-boot.itb on a GPT manually created image (https://wiki.radxa.com/Rock3/install/spi#Create_GPT_U-Boot_image) -> only green light and no output
rkdeveloptool + https://dl.radxa.com/rock5/5c/images/loader/spi/ -> same result as rsetup

The only one which gave me output and blinking blue LED is EDK2-porting firmware, however it seems that netboot options are only provided on REALTEK NIC equipped devices. (https://github.com/edk2-porting/edk2-rk3588/issues/181)

UPDATE