CSC Armbian for RK3318/RK3328 TV box boards

[haven]

My emmc was blown out with a power blackout during a flash process active. Very unlucky event.

 

[Riyadh Zaman]

Hello, I have the same tv box. i failed to boot from sd card. will you give a full process detail (This is the only method that worked for me: I re-recorded the U-boot using Windows 10 and RKDevTool GUI.

I download  U-boot from here:
https://github.com/hexdump0815/u-boot-misc/blob/master/misc.rk3328-no-sd-boot/rockchip-u-boot/u-boot-image-for-emmc-h96max-rk3328.img.gz
 Then I recorded to the SD card using the Multitool from straight from this thread. (u-boot-image-for-emmc-h96max-rk3328.img.gz) I download this file and failed to rerecord with RKDeveTool.  Also, any expert can be help. Thx.

Special request to JOCK.

u-boot-image-for-emmc-h96max-rk3328.img.gz

Edited December 4, 2024 by Riyadh Zaman

[Riyadh Zaman]

@jock 

Hello sir, Plz Help me. I have the same box RK3328 @user account. Give me a clear instruction as an armbian boss. I want to run server with the box. My main problem is cannot boot the box (multitool/direct armbian). but i have success to upgrade the android os 7.1 to 9. I used RkDevTool. Plz help. Thx.

 

https://forum.armbian.com/applications/core/interface/file/attachment.php?id=13598&key=67e51f8dea0e932984b14b784e000706

Edited December 9, 2024 by Riyadh Zaman

[jock]

@Riyadh Zaman instructions are in the first page of this thread

[Fcn3]

Hi @jock previously I flash my h96max box and install armbian server on it following your instructions on the first page. Now I want to try the desktop flavor. Should I follow the same instructions?

 

Thanks

[jock]

1 hour ago, Fcn3 said:

Hi @jock previously I flash my h96max box and install armbian server on it following your instructions on the first page. Now I want to try the desktop flavor. Should I follow the same instructions?

Hello, exactly the same instruction, yes

[Fcn3]

Installed the bookworm w/ xfce successfully. Configure the WiFi following the instructions provided. When I open chromium and want to play some YouTube videos, it is extremely slow and laggy. I'm curious if I'm missing some codec to install, or this is what we should expect from these cheap boxes.

 

The box has a 2GB of memory, if that helps

[jock]

@Fcn3 this what you can expect from such hardware. There is a chromium fork around with patches to allow v4l2request accelerated video decoding, but has never been tested on rk3318 and probably you have to built it yourself.

[Riyadh Zaman]

@jock Hello Sir, I have followed everything your instruction from first page. But i failed to boot my box from sd card. I have the same box. 

But no success to me. Need help and detail instruction for the box. Thanks.

[jock]

@Riyadh Zaman  from the first page:

 

[Riyadh Zaman]

Hello,

@jock I am on virtual machine linux. I am new on linux. I stuck at this point. what will be the next command. I have mini loader All.bin and image file. thx

 

After several try, it showing the error message.

Edited Monday at 07:43 PM by Riyadh Zaman
Correction

[ToShuk]

One question about my bricked MX10 4\64 GB, is it possible to update by maskrom image of armbian ?

 

i suspect that my mmc is dead, I got Download IDB Failed, one more question, is it possible to boot Armbian from SD CARD if mmc is dead? 

 

Edited Tuesday at 11:53 AM by ToShuk

[jock]

@ToShuk it depends upon a tree of factors.

 

mmc is totally invisible to the SoC

• The the SoC will automatically look for the sdcard - just plug armbian in the sdcard and it will work
• the above won't work if the sdcard slot is attached to the sdmmc_ext controller of the SoC; this depends on how the manufactured designed the board and, if this is your case, your only solution is to replace the onboard eMMC

 

mmc is stuck in read-only mode

• the SoC will indeed execute the bootloader, if any was present in the eMMC when it went read-only
• If the existing bootloader is the stock one, then you're stuck with the possibilities of the stock bootloader (eg: see the rockchip boot process wiki page): multitool will boot, but not plain armbian images; tinkering with armbian images bootloader will let them boot though. You can either short permanently the eMMC clock pin to ground, so the eMMC is clock gated and actually excluded from the system, or phisically remove the eMMC chip, so you can reconduct to the "totally invisible" case above
• if the existing bootloader is the one provided with armbian, the you're lucky and it should be possibile to boot from sdcard and USB

 

[ToShuk]

22 hours ago, jock said:

If the existing bootloader is the stock one

it looks like the bootloader is in stock because the multitool is loaded successfully, but I cant burn Armbian to emmc, it is stuck. How can I run Armbian from sdcard ? 

[jock]

53 minutes ago, ToShuk said:

it looks like the bootloader is in stock because the multitool is loaded successfully, but I cant burn Armbian to emmc, it is stuck. How can I run Armbian from sdcard ? 

As said, you can either remove the eMMC or short the clock pin to ground.

Otherwise learn how the rockchip vendor boot happens and use the multitool binaries to hack the armbian boot

[MattWestB]

@ToShuk Look in the log if the eMMC is in read only mode or if other error code.

I was having one RK2328 in read only mode but was unbricking it with RK factory tool but it was not easy.

And i have 2 RK3318 boxes with bad eMMC so using SC-Card then cant recover the chip (looks like ODRID have getting there external eMMC unbricked with the same chip but was doing it in very early kernel boot with script).

[ToShuk]

4 hours ago, jock said:

or short the clock pin to ground.

one second, if i short the clock ping of eMMC, what are the next steps ? how to boot Armbian from sd card? just flash img to sd card, put it to box and it will boot from sd card ?

[jock]

2 minutes ago, ToShuk said:

one second, if i short the clock ping of eMMC, what are the next steps ? how to boot Armbian from sd card? just flash img to sd card, put it to box and it will boot from sd card ?

exactly; shorting the clock pin will make the eMMC disappear from the system, hence the SoC will boot from sdcard

[ToShuk]

10 minutes ago, jock said:

exactly; shorting the clock pin will make the eMMC disappear from the system, hence the SoC will boot from sdcard

wow, good news! just a small clarification, Do you mean pins that turn on maskrom mode? in my side on the other side of the board under emmc.


Also another question, what about speed? i guess eMMC is better than sdcard?

[jock]

40 minutes ago, ToShuk said:

wow, good news! just a small clarification, Do you mean pins that turn on maskrom mode? in my side on the other side of the board under emmc.

Yes, the same.

Technically the SoC enters in maskrom mode when all the boot devices fails. Gating the eMMC will make the SoC boot from sdcard, if there's no sdcard, the SoC will attempt other boot options programmed in its ROM. Finally, if nothing is available, will sit and wait in maskrom mode.

 

 

 

 

[ToShuk]

19 hours ago, jock said:

Yes, the same.

Technically the SoC enters in maskrom mode when all the boot devices fails. Gating the eMMC will make the SoC boot from sdcard, if there's no sdcard, the SoC will attempt other boot options programmed in its ROM. Finally, if nothing is available, will sit and wait in maskrom mode.

 

 

Thank you! it's really work! wow, my eMMC is dead, os sees the real size of eMMC, but R\W operations are not available.

One more question, I have MX10 with an sv6051p wifi chip, but the os is not see any wifi devices, is it possible to turn on sv6051p chip?

[jock]

2 hours ago, ToShuk said:

One more question, I have MX10 with an sv6051p wifi chip, but the os is not see any wifi devices, is it possible to turn on sv6051p chip?

There is a driver for ssv6051p in the armbian images, but if the kernel does not see the chip it is probably turned off.

You need to set the right led-conf using rk322x-config script that enables the GPIO to turn on the wifi chip. MX10 is the tv box commercial name, but it tells nothing about the board which is inside: you have to look for the signatures on the board itself and see if you have a match with the led-conf proposed by rk322x-config

[A t]

On 4/16/2021 at 1:30 PM, jock said:

Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt.

i followed the instructions and now im stuck in this step .

The Hdmi didnt turn on its black screen and the led still blinking. what should i do  next? should i wait more ?

[jock]

17 hours ago, A t said:

The Hdmi didnt turn on its black screen and the led still blinking. what should i do  next? should i wait more ?

Find a possible IP address for the box and try to access via SSH, or use the UART serial to debug the issue

[A t]

ok i managed to access via SSH and did the configuration then did sudo apt update and upgrade and in the end got :

The system will suspend now!

client_loop: send disconnect: Connection reset
Progress: [ 99%]

tried to connect again but :

ssh: connect to host 192.168.1.xxx port 22 : Connection timed out

Now i try to power on the tv box with the controller and it does not turn on. Any solutions ?No image on hdmi

The LED is stable red

Thanks in advance!!

 

Edited 10 hours ago by A t

[jock]

@A t sorry but I have no idea, no logs, no board info and photos couldn't help understand what the problem may be

[A t]

sorry my bad!! my device is H96 max v11 RK3318 . The only time i was able to get access to the system was via ssh but now the device keep getting in suspension

HDMI has no image and cant connect again via ssh because the box is offline  (i'm noob sorry )

 

Broadcast message from gdm

@rk3318

-box on tty1 (Fri 2025-01-10 16:18:06 UTC): │ │ │ The system will suspend now! │ │ <Select> <Exit> │ │ │ Broadcast message from gdm

@rk3318

-box on tty1 (Fri 2025-01-10 16:18:06 UTC):──────────────────────────┘
The system will suspend now!
client_loop: send disconnect: Connection reset