ewww

the topic H96MAX have an description how to create a MMC flashing image
"legacy u-boot"
 
 
ask on wrt forum and bring that to our topic
 
 
can you edit the legacy uboot to the same config as the mainline for LAN?
 
 
Found some Github posts
Github is blocked on my work so i get it from google cache.... 

 
 
This problem also happends on N2
you will find a armbian solution....
 
@ewww

@maka please share the DTS and DTB files here to other users work around next steps
 
did the wifi works?

But eth0 is working, isn't it?

it is working with async timmings. it's an know issue
 
To armbian, we use legacy uboot kernel.
in your case, the RTL8211F dont accept to start with legacy uboot and switch to mainline armbian
 

the fix, their is a mismatch in
" mainline " vs  " downstream uboot "
that causes its clock "fix up" based on the kernels DTB
set the wrong clocks for (at least) GPLL and CPLL.
Fixing this the RGMII interface now works as intended.

You will need to create a mainline Uboot or fix the RGMII
 

IO voltages to the trash can, RTL will provide ....
rk3566-box-demo_rboxr2_8.dtb

Another idea
 
Change gmac1 to gmac0 in pinctrl-0
rk3566-box-demo_rboxr2_7.dtb

i made a change from "host" to "otg" in the first usb node, maybe fails because of that. Anyway, ethernet should be ok and have no more ideas. Can you check if rtl8211f is in the box?

I have realized that was using an rboxr2 dts that is diferent from yours because I had a previous file and was opening the wrong one. Because of this there is a voltage error that have mended.  The usb nodes are different as well but havent changed anything because is causing fatal error. You can play with usb nodes if you want to.
 
I think this file should work with the right voltage but the "final" word is just a hope.
 
PD 4f-2d is the right timing.
rk3566-box-demo_rboxr2_final.dtb

Be carefull, This value coud be a phandle.
the phandle is an redirect pointer.
 
 
# when you sent 
redirect = <0x4f>;
# the device redirect it to something like 
usb2phy2@483e8000 { compatible = "ti,am437x-usb2"; reg = <0x483e8000 0x8000>; ctrl-module = <0x4c>; clocks = <0x1a 0x4d>; clock-names = "wkupclk", "refclk"; #phy-cells = <0x0>; linux,phandle = <0x4f>; phandle = <0x4f>; };  

All is correct,but you must not comment all you trials, just make efforts to solve.

@ewww Seems that you want to take the nightmare of playing with dts files. So this is your first exercise.
 
rk3566-box-demo_rboxr2_5.dtb reports that your ethernet is based in RTL8211F but doesnt work. Because we can guess that kernel identification is good, maybe the timing is wrong in 4.19 dts file.  Apply the corect timing ( TX delay RX delay) to the board.

Another phy error. Lets try twice.
rk3566-box-demo_rboxr2_6.dtb rk3566-box-demo_rboxr2_5.dtb

This could be the good one. I forgot the usb phys !
😹
rk3566-box-demo_rboxr2_4.dtb

Keep dumping here, just mark down with references and purposes for every change

Sent from my 22021211RC using Tapatalk

@ewww You're using Linux version 6.1.34-media
please compile an armbian kernel 6.2++++ 
 rk3566-box-demo.dts came with edge kernel 6.2

detected but crashed
 
one by one
 
rk3566-box-demo_rboxr2_3.dtb

Just to try
rk3566-box-demo_rboxr2_2.dtb

@maka @ewww good job
Now you just need to enable the right USB setup.
Don't forgot to share


Sent from my 22021211RC using Tapatalk

@ewww You are closer than I expected...
you just need to compare the power pins and other things.
as @maka  said this device is fully compatible with rk3566-box-demo.dtb 
adaptation is minimal.
you can wait for another user of this device, but without much effort you should get.
 
try disabling all usb ports on rk3566-box-demo.dts to see the boot happen
if the boot happens, enable only the ones you believe work
 
 

@maka thanks. I have just tested 2 dtb. HDMI is working, but no usb
 
After that, it dropped to shell because it can't find root fs (I put OS on usb, tested 2 port)
 

Sorry
 
I have made a mistake better use this.
rk3566-box-demo_rboxr2.dtb

Here you have a dtb file that could work. Has the voltages suitable for your box. even the ethernet doesnt work properly without them. Maybe usbs dont work well because I dont manage them well enough.
 
Good luck
rk3566-box-demo_rboxr2.dtb

be carefull, My device is based on FAN53555, tcs4525, RK809-5
your device is based on rk3566-box-demo.dts
misconfiguration for power devices can make things go hot.
make things based on your DTS from android11 and rk3566-box-demo
this is the true, no way to scape, the work is slow like an ant.
use the translation mode i suggest, anything you do outside of that will make things stop working.
Author: Piotr Oniszczuk piotr.oniszczuk@gmail.com
Based on Quartz64 DT by: Peter Geis pgwipeout@gmail.com
with sort of code from @thc013
 
 
split your dts to work in pages.
if you start today, 30 days, 30 pages....
do it on track and slowly, it will work

@ewww

This is everything you need to create a bootable v0.7Armbian mmc image: DUMP
 
Please cofirm that this image works on your device....
On RK3566_DC_R2_HK5235F_11_20210705.1409.img
How i did it?
imgRePackerRK.exe /cid /2nd /debug /log update.img  
and after that

 
dtc -I dtb -O dts -o android11.dts dtb  
 
android11.dts

Lets Start with an example:

Leds:

On Android 11 DTS we have:
 
 
and on Linux Rockchip:
 
 
So we can do an Linux compatible with HK1 RBOX R2:
 
 
and let's pray that the linux gods give you strength to run this translation on all devices...........
it will take some time but, as I said when I opened this topic, you have to be very patient
 
You will need to include this devices on RK3566-box-demo
Enable devices that you have
disable devices that you dont
changing ports to devices that uses different address....

Use this calculator to compare ports from original android HEX and set it up decimal number for linux...
 
 
rk3566-box-demo.dts