Jump to content

Recommended Posts

Posted (edited)

Firstly, I would like to say I know next to nothing about what I am doing at all. I'm trying to learn though!

 

With the current shortage of decent SBCs at a reasonable price I thought being able to run Armbian on the above device would make it a very good deal.

 

I am only interested in using the device as a server so I currently have no information on running it as a desktop though I can burn an image and post the results if anyone is interested.

 

From reading the forums it seems many devices will try and boot from external storage of some sort before booting from emmc. This turned out not to be the case for this device.

 

I blundered about for a while just writing random stuff to sd cards and trying to boot, nothing worked.

 

I eventually connected a serial adapter to this board, there are holes on the board quite clearly marked, V,R,T and G. The baud rate is 1500000

 

Once I had done this, I realised how much earlier I should have done it, I now had a little light on what was going on.

 

It appeared from using printenv that the boot targets are set on this device to go for emmc first. There is no saveenv so this left me wondering how I was going to ever get it to boot without needing the serial adapter.

 

There appeared to be no option to boot from SD. What I did notice was that one of the boot targets was usb0 and so I wrote the Armbian_22.02.0-trunk_Station-m2_bullseye_legacy_4.19.219.img to a USB stick.

 

I replaced the rk3566-firefly-roc-pc.dtb with the one attached which I extracted from the Android firmware.

 

I then tried to boot from this by breaking into the boot sequence using ctrl-c and then used "run bootcmd_usb0".

 

I saw that it was trying to boot but then was unable to find the root filesystem. I now thought that USB wasn't compiled in/loaded at this stage and this led me to believe that I may be able to get this working by now adding an SD card with the same image on it.

 

This worked! I ended up with a login prompt and networking was working and I could SSH in.

 

So how now do I get it to boot from my combo?

 

I started by using fdisk and deleted all partitions on the emmc, this trashed everything and after restoring the android image back to the emmc using the rockchip recovery tool and a bit more reading, I could see that u-boot was on the second emmc partition.

 

There were actually 15 partitions on the emmc.

 

I now deleted all but the first two and issued the reboot command.

 

I still have no explanation for what happened next.

 

For some reason, the usb storage seemed no longer to be recognised but yet the first stage of the boot seemed to be happening but then it was crashing. I knew what the problem was from my earlier experimentation. When I wrote the SD card, I hadn't replaced the DTB as I believed I only needed the SD for the root filesystem. I quickly added the DTB so the SD and rebooted.

 

This was now successful. I was now booting from the SD card, something I hadn't seemed to be able to do from the u-boot command line, that will just be some error of mine.

 

I quickly added a partition to the emmc and copied the root filesystem there. I then updated the sd card extlinux to point to that emmc partition for the root filesystem and thats just about currently where I am at.

 

|_   _/ _ \| ___|  |  _ \| |_   _ ___
  | || (_) |___ \  | |_) | | | | / __|
  | | \__, |___) | |  __/| | |_| \__ \
  |_|   /_/|____/  |_|   |_|\__,_|___/

Welcome to Armbian 22.05.3 Bullseye with Linux 4.19.219-station-p2

System load:   2%               Up time:       7:36
Memory usage:  13% of 7.50G     IP:            192.168.50.29
CPU temp:      43°C             Usage of /:    6% of 58G

Last login: Sun Aug  7 23:34:24 2022 from 192.168.50.121

 

cat /proc/cpuinfo
processor       : 0
BogoMIPS        : 48.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x2
CPU part        : 0xd05
CPU revision    : 0

processor       : 1
BogoMIPS        : 48.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x2
CPU part        : 0xd05
CPU revision    : 0

processor       : 2
BogoMIPS        : 48.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x2
CPU part        : 0xd05
CPU revision    : 0

processor       : 3
BogoMIPS        : 48.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x2
CPU part        : 0xd05
CPU revision    : 0

Hardware        : Rockchip RK3566 BOX DEMO V10 ANDROID Board
Serial          : 399eb13dd69295ae

 

free
               total        used        free      shared  buff/cache   available
Mem:         7862464     1014552     6063900       61308      784012     6705776
Swap:              0           0           0

 

I really wish I could get the saveenv to work but I guess this means rebuilding u-boot and flashing that, then I could boot from emmc, I can already do that from the u-boot cli but I'm quite some reading and experimentation away from that.

 

I conclude from this though that there will never be a way to get to this stage without hooking up to a serial adapter first as I can see no way to delete those emmc partitions without that and so it will always try and boot the android first.

 

Maybe a custom firmware that only contains the u-boot? That too is much reading away.

 

I hope this all helps someone in some way, I wouldn't be where I am with this now without the help of this forum.

 

The box, by the way is this one: https://www.amazon.co.uk/gp/product/B098DY737L

 

The replacement dtb is attached.

 

I also managed to get Proxmox running on it

 

 

 

 

 

t95plus.dtb

proxmox-t95.jpg

Edited by DigitalDaz
Posted

It seems to me that you have not  flashed Linux uboot to emmc so booting from there is not working. Booting from sd card is not a bad solution though. 

Posted

Hi @DigitalDaz

 

Looks great so far, just a few questions.

Does it support 1gbe ? and is the 8gb accessible?

Great effort awesome to see, i sent you a dm in regards to what you've got done here. 

Posted

Yes, its gigabit and yes, the 8GB is there too

 

And coming very soon is a guide on how to get this all working without opening the box. It very easy once you know how.

 

If you haven't got a USB A male to USB A male, get one.

Posted

I already have one sat here, 4GB variant but haven't had any chance to delve into it yet.

Im going to order a 8gb one now and i've got a few  a to a cables from reflashing amlogic boxes.

Sounds very promising

Posted

I'm really struggling with the emmc boot at the moment, trying everything.

 

My knowledge just isn't up to it. I'm doing a shed load of reading.

 

What is very easy is to boot from and sdcard then have the root filesystem on emmc so basically its just loading the first part of the boot from sdcard then continues to boot from the emmc.

 

Performance should be as good as having it installed on emmc.

 

Posted

I can already boot from emmc by the way by using a serial cable and issuing a couple of commands in the u-boot

 

There is a saveenv missing that would normally allow you to save the env variables to flash, then it would be easy.

 

So yes, I can boot from flash but I don't currently have a way to save it.

 

That's now :)

 

I'm sure its just a matter of time

Posted

the H96 Max RK3566 8GB (the very first at 8GB) doesn't even have a SD slot, u-boot nor any uEnv.txt it's a DSU https://developer.android.com/topic/dsu
dynamic software update that can be bypassed but it's totally alien to the solutions we (I) have thus far. I got them rooted though but replacing the OS is gonna be a tough candy 

I too made a station image but M-2 (rk3566) not P-2 (rk3568) with the build script, fingers crossed. The RK tools doesn't differenciate 3568 of 3566 in the config files.

 

 

Posted

For the reference, here is the device tree source of t95plus.dtb

  Reveal hidden contents

 

 

Posted

Broke my u-boot partition. i guess i bricked my device now. :(

 

My goal is to boot an os with efi partition, the existing u-boot partition has no bootefi command. To do this, i decided to try building my own u-boot img.

I found out that rockchip does not suport rk3566 , only rk3568. Thats why i followed a guide for rk356x chips.

I booted armbian on the target device and build it natively using this guide: https://forum.pine64.org/showthread.php?tid=14507

the patch file is gone (404). I had to clone the repo and use

 

git log --full-history -1 -- [file path] to the commit of the file and finally find it.

 

I used the patch and fixed one broken entry, so i could start compiling.

 

At the end i got a u-boot.img which i finally copied using dd to partiton2 (u-boot) of the emmc. This overwrites the current working u-boot.

 

On my attached UART i get the following output.

▒zDDR Version V1.09 20210630
ln
ddrconfig:7
LPDDR4X, 324MHz
BW=32 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=8192MB
tdqss: cs0 dqs0: 48ps, dqs1: -72ps, dqs2: -72ps, dqs3: -144ps,
tdqss: cs1 dqs0: 48ps, dqs1: -72ps, dqs2: -72ps, dqs3: -120ps,

change to: 324MHz
PHY drv:clk:36,ca:36,DQ:29,odt:60
vrefinner:16%, vrefout:41%
dram drv:40,odt:0
clk skew:0x61

change to: 528MHz
PHY drv:clk:36,ca:36,DQ:29,odt:60
vrefinner:16%, vrefout:41%
dram drv:40,odt:0
clk skew:0x58

change to: 780MHz
PHY drv:clk:36,ca:36,DQ:29,odt:60
vrefinner:16%, vrefout:41%
dram drv:40,odt:0
clk skew:0x58

change to: 920MHz(final freq)
PHY drv:clk:36,ca:36,DQ:29,odt:60
vrefinner:16%, vrefout:22%
dram drv:40,odt:80
vref_ca:00000071
clk skew:0x3b
cs 0:
the read training result:
DQS0:0x46, DQS1:0x47, DQS2:0x4b, DQS3:0x43,
min  : 0xa  0xa  0xe  0xb  0x1  0x2  0x6  0x2 , 0x6  0x6  0x2  0x2  0xa  0xa  0xc  0x7 ,
       0xf  0xf  0xe  0xa  0x6  0x1  0x6  0x4 , 0xa  0x6  0x5  0x1  0xd  0xc  0x9  0xc ,
mid  :0x2d 0x2e 0x31 0x2f 0x24 0x26 0x2a 0x26 ,0x28 0x28 0x25 0x23 0x2d 0x2a 0x2f 0x29 ,
      0x33 0x32 0x30 0x2d 0x29 0x24 0x26 0x28 ,0x2c 0x29 0x28 0x23 0x2f 0x2e 0x2b 0x2f ,
max  :0x51 0x52 0x55 0x53 0x48 0x4b 0x4e 0x4a ,0x4b 0x4a 0x49 0x44 0x50 0x4b 0x52 0x4b ,
      0x58 0x56 0x52 0x50 0x4c 0x48 0x47 0x4c ,0x4e 0x4c 0x4b 0x46 0x52 0x50 0x4d 0x52 ,
range:0x47 0x48 0x47 0x48 0x47 0x49 0x48 0x48 ,0x45 0x44 0x47 0x42 0x46 0x41 0x46 0x44 ,
      0x49 0x47 0x44 0x46 0x46 0x47 0x41 0x48 ,0x44 0x46 0x46 0x45 0x45 0x44 0x44 0x46 ,
the write training result:
DQS0:0x40, DQS1:0x33, DQS2:0x33, DQS3:0x2b,
min  :0x5e 0x61 0x63 0x5f 0x56 0x58 0x5a 0x5c 0x5a ,0x4d 0x4d 0x49 0x48 0x50 0x4f 0x54 0x51 0x4d ,
      0x51 0x50 0x4e 0x4e 0x48 0x48 0x4a 0x4f 0x4d ,0x49 0x48 0x46 0x43 0x4d 0x4d 0x4d 0x4e 0x48 ,
mid  :0x7b 0x7d 0x7f 0x7c 0x73 0x75 0x77 0x77 0x76 ,0x6a 0x69 0x65 0x64 0x6d 0x6b 0x6d 0x6c 0x69 ,
      0x6e 0x6e 0x69 0x69 0x65 0x5d 0x5f 0x65 0x66 ,0x66 0x65 0x61 0x5e 0x69 0x6a 0x62 0x6b 0x60 ,
max  :0x98 0x9a 0x9b 0x99 0x91 0x92 0x94 0x93 0x93 ,0x87 0x85 0x82 0x81 0x8a 0x87 0x87 0x88 0x85 ,
      0x8c 0x8c 0x85 0x85 0x82 0x73 0x74 0x7b 0x80 ,0x84 0x82 0x7d 0x7a 0x86 0x88 0x78 0x89 0x78 ,
range:0x3a 0x39 0x38 0x3a 0x3b 0x3a 0x3a 0x37 0x39 ,0x3a 0x38 0x39 0x39 0x3a 0x38 0x33 0x37 0x38 ,
      0x3b 0x3c 0x37 0x37 0x3a 0x2b 0x2a 0x2c 0x33 ,0x3b 0x3a 0x37 0x37 0x39 0x3b 0x2b 0x3b 0x30 ,
cs 1:
the read training result:
DQS0:0x44, DQS1:0x47, DQS2:0x4c, DQS3:0x43,
min  : 0x9  0x9  0xc  0x9  0x1  0x2  0x5  0x1 , 0x5  0x5  0x3  0x1  0xb  0x8  0xd  0x6 ,
      0x11 0x10  0xe  0xb  0x6  0x2  0x7  0x5 , 0xa  0x7  0x6  0x2  0xe  0xd  0xa  0xd ,
mid  :0x2c 0x2c 0x2f 0x2c 0x23 0x25 0x27 0x24 ,0x28 0x28 0x26 0x23 0x2d 0x2a 0x30 0x29 ,
      0x34 0x34 0x30 0x2e 0x2a 0x25 0x28 0x29 ,0x2c 0x29 0x28 0x24 0x30 0x2e 0x2c 0x2f ,
max  :0x4f 0x4f 0x53 0x50 0x46 0x48 0x4a 0x47 ,0x4c 0x4b 0x4a 0x45 0x50 0x4d 0x53 0x4c ,
      0x58 0x58 0x52 0x51 0x4e 0x49 0x49 0x4e ,0x4e 0x4c 0x4b 0x46 0x52 0x50 0x4e 0x51 ,
range:0x46 0x46 0x47 0x47 0x45 0x46 0x45 0x46 ,0x47 0x46 0x47 0x44 0x45 0x45 0x46 0x46 ,
      0x47 0x48 0x44 0x46 0x48 0x47 0x42 0x49 ,0x44 0x45 0x45 0x44 0x44 0x43 0x44 0x44 ,
the write training result:
DQS0:0x40, DQS1:0x33, DQS2:0x33, DQS3:0x2b,
min  :0x5d 0x5f 0x62 0x60 0x56 0x58 0x5a 0x5c 0x5a ,0x4c 0x4c 0x49 0x48 0x4f 0x4f 0x53 0x51 0x4d ,
      0x52 0x52 0x4e 0x4e 0x48 0x48 0x4a 0x4f 0x4f ,0x4b 0x4a 0x49 0x46 0x4f 0x4e 0x4f 0x50 0x4b ,
mid  :0x7a 0x7c 0x7e 0x7d 0x73 0x75 0x77 0x77 0x76 ,0x69 0x69 0x65 0x65 0x6c 0x6b 0x6d 0x6c 0x69 ,
      0x6f 0x6e 0x69 0x6a 0x65 0x5d 0x5f 0x65 0x68 ,0x69 0x66 0x65 0x61 0x6c 0x6c 0x64 0x6d 0x62 ,
max  :0x98 0x9a 0x9b 0x9a 0x91 0x93 0x95 0x93 0x93 ,0x87 0x86 0x82 0x82 0x8a 0x87 0x87 0x88 0x85 ,
      0x8c 0x8b 0x84 0x87 0x82 0x73 0x74 0x7b 0x81 ,0x87 0x83 0x81 0x7d 0x89 0x8a 0x7a 0x8b 0x79 ,
range:0x3b 0x3b 0x39 0x3a 0x3b 0x3b 0x3b 0x37 0x39 ,0x3b 0x3a 0x39 0x3a 0x3b 0x38 0x34 0x37 0x38 ,
      0x3a 0x39 0x36 0x39 0x3a 0x2b 0x2a 0x2c 0x32 ,0x3c 0x39 0x38 0x37 0x3a 0x3c 0x2b 0x3b 0x2e ,
CA Training result:
cs:0 min  :0x47 0x49 0x41 0x40 0x41 0x3e 0x45 ,0x44 0x44 0x3d 0x3d 0x3f 0x3e 0x45 ,
cs:0 mid  :0x86 0x87 0x81 0x7e 0x80 0x7c 0x76 ,0x83 0x82 0x7d 0x7c 0x7e 0x7c 0x75 ,
cs:0 max  :0xc6 0xc6 0xc1 0xbd 0xbf 0xbb 0xa7 ,0xc3 0xc1 0xbd 0xbb 0xbd 0xba 0xa6 ,
cs:0 range:0x7f 0x7d 0x80 0x7d 0x7e 0x7d 0x62 ,0x7f 0x7d 0x80 0x7e 0x7e 0x7c 0x61 ,
cs:1 min  :0x45 0x4c 0x3e 0x41 0x3c 0x41 0x44 ,0x43 0x46 0x3b 0x40 0x3c 0x40 0x41 ,
cs:1 mid  :0x86 0x87 0x80 0x7e 0x7e 0x7d 0x77 ,0x84 0x82 0x7d 0x7c 0x7e 0x7c 0x74 ,
cs:1 max  :0xc8 0xc3 0xc2 0xbb 0xc1 0xb9 0xaa ,0xc6 0xbf 0xbf 0xb9 0xc0 0xb9 0xa8 ,
cs:1 range:0x83 0x77 0x84 0x7a 0x85 0x78 0x66 ,0x83 0x79 0x84 0x79 0x84 0x79 0x67 ,
out
U-Boot SPL board init
U-Boot SPL 2017.09-ga1f6fc00a0-210413 #ldq (Apr 13 2021 - 11:35:00)
unknown raw ID phN
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2
spl: partition error
Trying to boot from MMC1
No misc partition
## Verified-boot: 0
## Checking firmware@1 0x00a00000 ... OK
## Checking fdt@1 0x00b33108 ... OK


 

At this point, the system hangs, and its not possible to CTRL-C stop the boot process etc.

 

I tried flashing the Device with Android Tool or the RockChip Factory Tool, but it seems not to detect the usb device anymore. :(

 

Thats very bad because i thought if i mess up with u-boot i could still reflash it using this tool. Maybe i am just doing something wrong with the factory Tool but as far as i see, i guess it requires the pre-installed u-boot?

 

Any help would be appreciated. Thx!

 

 

 

 

 

 

 

 

Posted

My last hope is that it is possible to intercept 

 

unknown raw ID phN
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2

---- HERE ----

spl: partition error
Trying to boot from MMC1

---- OR HERE ----

No misc partition
## Verified-boot: 0
## Checking firmware@1 0x00a00000 ... OK
## Checking fdt@1 0x00b33108 ... OK

 

To get it working again. But this would require some magically prepared sd card i guess? Any help would be welcome.

Posted

@Hefti Did you figure out how to restore your board? I just clobbered mine too (with `rkdeveloptool wl 0x40 idloader.bin` gone wrong). I think I will need to short the eMMC 

Posted

has anyone gotten a newer version to run with wifi on the t95 plus? i have an 8gb model and got klipper to run just fine off the sd card but would like to update to get wifi working and install to emmc ive tried the steps over at t95plus.com but issue is when i get to Replace the UUID in the line beginning with APPEND with the UUID obtained from the step above, it should end up like this: i have issues with the UI

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines