Success , Armbian from station m2 on rk3566 android boxes !11

[Trigu75]

And your screenshot shows you are doing it wrong...

The right way is to decompile the dtb to dts , understand how it is configured , find the right pin configurations in it , and edit and compile back from dts to dtc

[ASDosjani]

I didn't want to decompile it, only interested whats the difference between them. Anyway, when I decompile with dtc it shows a lot of errors but the dts file generates.

[shaggy013]

it shows just a few errors dont overdue

and without decompiling ?

what are the io-domains setting ?

just to name one

and proberly the 4 or 8 gb comes from uboot , you can find some info with google

you can find the easy find the dts wich is used as base

[ASDosjani]

Can I ask if the old firmware is freezing sometimes for you too?

[shaggy013]

i don't even have that box

but your again asking things wich have no use !

and your both just lazy , there is 1 dts file with box in the name and your too lazy to adjust that a little .

disable some usb ports add the lcd , disable some more , check io-domain . and your done

and proberly you can leave the dummy-amlogic out of the dts .

all questions with even try to make a own dts is just useless

[ASDosjani]

Sorry for the misunderstanding, I wanted to ask Trigu75 about the firmware.

Where can I find that dts what you are talking about and how to can I adjust it? With a simple nano? I saw these setting in the kernel settings while building armbian, but I don't know what io-domain means. Now I'm using termux and I can run server from there, but it's not optimal. Sorry for the stupid questions.

[shaggy013]

realy !!

What model name is in the dtb you got ?!

you dont see that in kernel setting !

just type " decompile dtb " in google
decompile the dtb
read the model name from dts file it creates
build with armbian a legacy build of a rk3566/68 board doesnt matter wich one just with a 4.19 kernel
copy the dtb file wih the name you found in your decompiled dts to another place
decompile the dtb wich you copied from armbian and compare it with the dts you compiled from the dtb of your box

and instead of saying i dont know what io-domains means GOOGLE it " io-domain rockchip"

your dtb says

io-domains {
compatible = "rockchip,rk3568-pmu-io-voltage-domain";
status = "okay";
pmuio1-supply = <0x29>;
pmuio2-supply = <0x29>;
vccio1-supply = <0x29>;
vccio3-supply = <0x29>;
vccio4-supply = <0x2a>;
vccio5-supply = <0x29>;
vccio6-supply = <0x2a>;
vccio7-supply = <0x29>;
phandle = <0x124>;
};

the armbiam dtb gonna say

io-domains {
compatible = "rockchip,rk3568-pmu-io-voltage-domain";
status = "okay";
pmuio2-supply = <0x29>;
vccio1-supply = <0x29>;
vccio3-supply = <0x29>;
vccio4-supply = <0x29>;
vccio5-supply = <0x29>;
vccio6-supply = <0x29>;
vccio7-supply = <0x29>;
phandle = <0x135>;
};

and the original dts of the armbian dtb says

/* Need to be modified according to the actual hardware */
&pmu_io_domains {
status = "okay";
pmuio2-supply = <&vcc_3v3>;
vccio1-supply = <&vcc_3v3>;
vccio3-supply = <&vcc_3v3>;
vccio4-supply = <&vcc_3v3>;
vccio5-supply = <&vcc_3v3>;
vccio6-supply = <&vcc_3v3>;
vccio7-supply = <&vcc_3v3>;
};

and proberly it should be

/* Need to be modified according to the actual hardware */
&pmu_io_domains {
status = "okay";
pmuio2-supply = <&vcc_3v3>;
vccio1-supply = <&vcc_3v3>;
vccio3-supply = <&vcc_3v3>;
vccio4-supply = <&vcc_1v8>;
vccio5-supply = <&vcc_3v3>;
vccio6-supply = <&vcc_1v8>;
vccio7-supply = <&vcc_3v3>;
};

and so you go on till you get it working or destroy your board.

[ASDosjani]

Thanks for the detailed answer, i will try, but my problem is not that I can't boot into armbian, but java always crashing. What do you mean by "original dts of the armbian dtb"? I found the rk3566-box-demo-v10.dtb and decompiled it and it's only shows the hex values not the vcc_3v3.

[shaggy013]

Thanks for the detailed answer, i will try, but my problem is not that I can't boot into armbian, but java always crashing. What do you mean by "original dts of the armbian dtb"? I found the rk3566-box-demo-v10.dtb and decompiled it and it's only shows the hex values not the vcc_3v3.

yeah and still dont see the diference in hex between 1v8 and 3v3 ?!

and armbian is dead

here a firefly ubuntu

i dont have the device

drr1056 with your dtb

https://drive.google.com/file/d/1k0S...ew?usp=sharing

ddr1560 with your dtb

https://drive.google.com/file/d/1Wbw...ew?usp=sharing

and stop complaining about your bad mc

[ASDosjani]

Wow, thanks for your work, but both image stuck at the "Rockchip KERNEL" image. Tomorrow I will check serial debug if needed.

[shaggy013]

Wow, thanks for your work, but both image stuck at the "Rockchip KERNEL" image. Tomorrow I will check serial debug if needed.

yeah i know what was wrong dts was litle to high

here another attempt i think it boots

your dtb doesnt work with a .219 so i took a raxda .193 and now it even boots on my device with your dtb

https://drive.google.com/file/d/1Znat1E1worbIWbt4z_aTszBsZgLfAWKn/view?usp=sharing

yah it is not linux but know i know what was wrong

only have to figure out to make avb image works to get the google things working

[ASDosjani]

Same thing happened as before.

[shaggy013]

Same thing happened as before.

fo you have a bootlog or dmesg ?

i surprised it wont boot

you can pm

[ASDosjani]

Do you know which baud rate is used in this image, because I don't get any usable log with 1500000 or 115200 baud rate. The 1500000 is working with the default Android and armbian.

[shaggy013]

it is just 1500000 like normal rockchip

strange should just boot or give a log

you can try reflash it , no uboot ouptput can also means the sd isnt flashed right and otherwise it should boot from emmc
the boot order is spi sd emmc from bootrom

you dont have the power connected

and the uboot boot between device is not been a problem that i know to get at least some output on a serial console