Armbian for Tinkerboard 2 WIP

[DaveWK 0]

Hi

I noticed that Armbian has an experimental start to a Tinkerboard 2 build. This is really interesting because it uses the current Mainline kernel (5.19) instead of the ancient 4.xx builds that seem to be the only thing available in downloads.

for example here's the kernel config:

https://github.com/armbian/build/blob/master/patch/kernel/archive/rockchip64-5.19/add-board-tinker-board-2.patch

and the u-boot config:

https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-rockchip64/add-board-tinker-board-2.patch

 

This boots somewhat successfully however I think it needs a bit more work to be usable.

When it boots you'll see a bunch of CQE errors like:
 

running CQE recovery I/O error, dev mmcblk1

and

mmc1: cqhci: spurious TCN for tag 5

which result in the filesystem going into read-only mode, and the system being pretty unusable.

I found this somewhat recent post about rk3399's: https://patchwork.kernel.org/project/linux-arm-kernel/patch/20190301164349.60589-3-christoph.muellner@theobroma-systems.com/

and tried adding the

disable-cqe-dcmd

into the proper location, but it did not work.

 

So I was wondering about:

 

Is the Tinkerboard 2 supposed to have CQE dcmd support? I couldn't tell from the hardware specs if this was the case. If so, how should I fix this issue?

This has not been updated in a little while, and I was unsure about the modifications this made to drivers/power/regulator/fan53555.c and drivers/power/pmic/fan53555.c in order to use it as a regulator for the gpu and cpu.. It seems like a lot of other rk3399 use

 compatible = "silergy,syr827";

is this a better option?

 

 

 

 

[DaveWK 0]

I think I have narrowed the problem down to the emmc configuration.. For armbian I see:
 

&sdhci {
	bus-width = <8>;
	mmc-hs400-1_8v;
	supports-emmc;
	mmc-hs400-enhanced-strobe;
	non-removable;
	keep-power-in-suspend;
	status = "okay";
};

&sdmmc {
	clock-frequency = <150000000>;
	clock-freq-min-max = <100000 150000000>;
	supports-sd;
	bus-width = <4>;
	cap-mmc-highspeed;
	cap-sd-highspeed;
	disable-wp;
	num-slots = <1>;
	//sd-uhs-sdr104;
	vmmc-supply = <&vcc3v3_s3>;
	vqmmc-supply = <&vccio_sd>;
	pinctrl-names = "default";
	pinctrl-0 = <&sdmmc_clk &sdmmc_cmd &sdmmc_cd &sdmmc_bus4>;
	status = "okay";
};

Is the use of mmc-hs400-1_8v here correct, as well as hs400-enhanced-strobe? I see in some cases this has been disabled due to the frequency being too low for the driver, so the hs200 is used instead.

In the case of helios, another rk3399 board, hs400 was re-enabled: https://github.com/armbian/build/pull/2677/files#diff-1ffa592865c07dc11cdd53c328d714c1f7160c3170279467f8138f11d6166d02

Should this be using hs200 of hs400, and at what clock speed?

 

[Suleyman Poyraz 0]

Is there any changes???

[DaveWK 0]

Unfortunately I am running into the same thing as this guy:

https://forum.armbian.com/topic/17448-is-asus-tinker-board-2-supported-by-armbian/#comment-122107

I did figure out that when I use fedora's u-boot for roc-cc-rk3399 that they include in the RPM's that it doesn't have the problem with writing to the MMC, but unfortunately the USB and ethernet doesn't come up (can only use the serial console). Sad because it is really quick to boot and even loads the driver correctly for Graphics on fedora.

Not sure who's putting out these old debian 4.19 releases, but I wished they'd work on making a dts compatible with the latest u-boot so I can use whatever distro I want instead of forcing some ancient debian fork on folks who mistakenly bought this thinking it would work with mainline u-boot.