MattWestB

@MattWestBThank you for your time.
I attachboard photos, it's a X88 Pro 10 android-box. I can read on the second photo, under the sticker, X88 PRO B RK3318 D4 V1 2 so I chose X88 PRO B config, but it won't work neither bluetooth or wifi (at least if I chose SP6330 in armbian-config I have an output to that grep). 
I look at the overlays and it should be loading the config (the last one is rk3318-box-wlan-ap66330, the one added by armbian-config).
I might be missing something, I feel quite clueless.


 
 
 
 


 
 

RK322Xs is 32 bit ARM CPUs and can only running 32 bit OS so not possible installing aarch64 OS on the hardware.
Also it have not enough RAM (normally 1 or 2 G) for running very large docker containers.

RK322Xs is 32 bit ARM CPUs and can only running 32 bit OS so not possible installing aarch64 OS on the hardware.
Also it have not enough RAM (normally 1 or 2 G) for running very large docker containers.

@jock @Asriel Nguyen finally I found the solution.
Rockchip has an official document say:
 
 
https://opensource.rock-chips.com/wiki_Rockusb#Maskrom_mode
 
So, the command of write u-boot-main.img is
 
rkdeveloptool wl 0x2000 u-boot-main.img  
After write u-boot, you able to boot MultiTool from OTG USB

@Asriel Nguyen The board looks very not RK3228 like but your lsusb is saying it one in maskrom mode so shall being one but no initial booltloader in the eMMC = shall booting Multitool / Armbian OK from SD-Card (but not direct from USB sticks).
Only PM is if the card reader is on the standard address or being on other then its not working.
 
Do you have some high res picture of top and bottom of the PCB then cant see the small components and printing ?

@wanton beis Your device is having eMMC and no nand flash.
If flashing factors Android on the bootloader in the eMMC can only booting eMMC or old bootloaders from the sd-card like Multitool.
If eMMC is empty the SOC is looking for one sc-card for bootloader and if you have written one new arbian image on it it shall finding it and booting OK and also can booting USB-flash from the sd-card (jump starting).
Then writing Android or one old Linux on the eMMC it can only booinng from eMMC system or sd-card all with old system so need updating the bootloadre in the eMMC or erasing the eMMC for  booting newer systems from  the sd-card and gettig jump loading of USB-flash.

ok i triggered maskrom with this
 
 
now i need to know how to boot from the sd directly or flash the nand with the backup... i dont understand rkdeveloptool...
 
done. i flashed idk, i think it was the u-boot and now i can boot multitool from sd. everything fine!
 
motherboard is `TXCZ_R98S_V30`

same happened to me, EMMC dead, no way to recover -> only boot from SDCARD

Still working on HDMI audio, with some updates.
Pulseaudio default sink set correctly.
 
Fisrt of all the issue appears only on my home TV. Tested with other TV sound seems ok. HDMI port works with other device (my notebook)
kernel 6.6.47-current    Armbian v24.8.4  -> no hdmi audio kernel 6.6.2-edge    Armbian v23.11.1 -> no hdmi audio kernel 6.8.11-edge    Armbian v24.8.4 -> no hdmi audio kernel 6.11.0-edge    Armbian v24.8.4 -> no hdmi audio kernel 6.1.63-current  Armbian v23.11.1 ->  hdmi audio OK still working on ..

Unbrick rk3229 TV-box X96q:
(processor marked as S905W, but actually is not, software detects it as rk3229)
 
For unbrick power off, short this two resistors (upper contacts) with screwdriver, power on, red led will be bright - remove screwdriver. Unbricked, you can load from SD-card now. 
 

Thanks for great work @Jean-Francois Lessard !!!
I think the trigger was not loaded OK with my manual install.
My 2 boxes is for the moment HA in production and the second one is updated Android V11 (from V10) then it was having problems running large IPTV (corrupting the files system) that looks working OK now.
Then i have getting all stable and also can getting HyperHDR also running (USB problems . . .  with V1.4 hardware but one other box looks doing better but not the USB3) i can doing one rockade and doing more testing.

@E O Bernardini From the first page opening post is https://users.armbian.com/jock/rk322x/armbian/stable/ you find the last Jocks builds.

@Parth
Even 3128 is working quite well with linux  just compile kernel with appropriate config and appropriate cpu platform

Regarding the garbage on uart, remember the uart speed is unusual  ( 1500000 NOT 115200 ) until it starts modified uboot that is 115200 so you have to take care of this note

I am the one in this project that discovered the uart pins on mostly of 322x boards and I can give for sure that if garbage comes out is:
wrong pin
wrong speed
lack of ground

On the software - firmware side   can give you answers  @jock  @RaptorSDS and all the friends athat daily work on those boards
 

About the service and driver issues, you could post in the post of the author about the kernel module:
 
I'm glad you tested also the indivual leds and they work; I will integrate those into the RK3318_V1.4  device tree overlay

@MattWestB led-conf7 does not exist on rk3318 build, it is just up to led-conf5 I introduced very recently; your board should fit into the base device tree.
 
Anyway, if you'd like to test the new tm16xx driver (which include support for fd6551 and several other led driver chips) you'd need to switch to the armbian beta repository, but beware of the dragons ahead! So take a full backup first!
You can switch to beta repository in armbian-config or by changing apt.armbian.com to beta.armbian.com in /etc/apt/sources.list.d/armbian.list
 
Then run apt update and upgrade at least the kernel, dtb and armbian-bsp-cli-rk3318 packages, then reboot, run rk3318-config and (for your specific case) you should be able to test the fd6551 driver with led-conf5 (YX_RK3318 board)
Now that you are confirming me that RK3318_V1.4 also have a display panel and the fd6551, I can update your board device tree too. Notice that it should be handy to know if leds and segmentes are displaying correctly. You can make reference to the original driver https://github.com/jefflessard/tm16xx-display on how to configure and tweak the driver for your specific board. Everything which is there applies as-is.
 
The same applies for other people with X88 and YX_RK3318 boards: there the led-conf that applies to their board should be already working out-of-the box!
 
 

@Netraam31 well, first of all it would be useful to share the board name you got and the led driver chip you have. perhaps I already got the dts and so you don't need to extract it.
To extract it, the procedure is totally manual, I use a hex editor for that, so if you have no clue on how to do it never mind.

Hello, I am working on an alternative fd6551 and clones led driver for our tv boxes front displays.
It is getting up in very good shape, but requires some tuning up; I would like to ask anyone who owns a box with a front led panel and is interested to report the board name, the display chip (common chips are fd6551, fd650, tm1650, etc...) and the original stock dts if possibile.
 
It would make things easier to support already existing boards.
 
Thank you!
 
edit: for source code and reference: https://github.com/paolosabatino/leds-fd6551
 

Unfortunately the 6.6.39 (Armbian 24.5.3 current) version seems to be the last version. After update I've the boot issue. I've rollbacked to 6.6.32 kernel version...
Who can we report it to?

 

This DTB enables all the ram speeds and the Mali 450 MP2 GPU is set so it can boost to 750 MHz well within safe operating voltages and the CPU is set to be able to scale to 1.5 GHz (also well-within safe operating voltages.

Tings Fixed :
Mali450-MP2 GPU Clock [added 600 / 700 / 750 MHZ OPP]
RK3318 CPU Clock [600 MHz to 1.5 GHz]
DDR RAM [All Enabled]

thanks to the support of Bing copilot in precise prompt
feel free to test now that i got everything nearly sorted out.
(WARNING!!! Large Heat Sink + 12V Fan Required)

The DTS File is also here if you want to tweak the settings you need.
place the File "rk3318.DTB" in /boot/dtb/rockchip/rk3318.dtb and reboot.
and point /boot/armbianEnv.txt so that rk3318-box.dtb is "rk3318.dtb"
rk3318.dtb rk3318.dts

Sure it wasn't too complicated really, I can give you the gist of it from memory.
 
1. Burn Armbian_22.05.0-trunk_Rk3318-box_jammy_current_5.15.35_xfce_desktop to usb drive, plug into usb otg port to boot.
2. Go through basic install routine as usual until you get to armbian desktop
3. You should see your emmc drive as a desktop icon
4. open terminal
5. mount your emmc and important dirs, I don't think I had to mount boot dir ymmv
example mount /dev/mmcblk2p1 /mnt
mount -t proc proc /mnt/proc
mount -t sysfs sys /mnt/sys
mount -o bind /dev /mnt/dev
mount -t devpts pts /mnt/dev/pts
chroot /mnt
6. Use armbian-config to install working kernel (6.6.32) as well as update bootloader.
7. Exit terminal and shut down system, once you no longer get a signal to display unplug usb drive and power cycle to verify bootup and you can freeze with armbian-config once booted up.
 

I was able to chroot into my existing installation after booting from the Armbian_22.05.0-trunk_Rk3318-box_jammy_current_5.15.35_xfce_desktop image from a usb stick, then i ran armbian-config to install the 6.6.32 kernel and freeze it without issue fwiw.

Bullseye 22.04 My image

H96 MAX V12 RK3318 4gb EMMC 64gb Tested ☑️
 
Armbian-unofficial_24.5.0-trunk_Rk3318-box_bullseye_current_6.6.23_minimal (SERVER)
 

That's right.
I use multitool only to erase internal flash and then use rkdeveloptool to flash loader and image as it is described in first page.
The device boots from sdcard in both cases, blank or flashed emmc but if there is a proper partition on internal flash Armbian works right, otherwise turns off(I heve tried to erase emmc and create partition with fdisk tool in Armbian, and OS works properly ). Armbian boots from internal flash too.
I think booting issue and turning off after minute are two different cases. Turning off probably is some kind of interaction between RAM and EMMC into EMCP chip itself(kingston 08emcp08-el3cv100).
This is dumped android firmware:
https://drive.google.com/file/d/1ZLl-KCvGS47SAO8tY1YDvCHDv6YWIWRP/view?usp=sharing

thats look like a power or thermal problem maybe , did you managed to try (sdcard or usb) with cpu-stability to overlays= line in /boot/armbianEnv.txt
or verbosity=7 and look in the Serial log maybe still always same step where it break
 
hope you have a serial adapter at the box

Hi All
 
 
 
Thanks for the help.
 
I am now searching for the clock, but mine scope is max 100 Mhz so maybe it do not see or just noise.
The pins you mention 6 and 7 just has voltage on it, no clock signal.
 
The idea of the use of the empty nand place I did also has idea of, because these boards are made for mucho 
chips so yes it can be there. Mine board has a eMc/ram indeed. I can reball a new one if fake or a bad one.
 
On the back of the board is no pads, there some below the rt3229 cpu.
 
Are there more pins to short on emmc on free space on board, can I go with other menas to get into the system,
ssh or so.