CSC Armbian for RK3318/RK3328 TV box boards

[gurzixo]

Hello again Jock an all the other members of this topic !

After a long time without fiddling with those lovely boxes, I need now a low-cost Linux box (typically 4gb/64gb) for setting up a simple local web server with node/express/nginx.

Would someone be kind enough to provide a working AliExpress link of such a box where at least Eth and maybe WiFi are working out of the box?

Thanks a lot,

Michel 

[jock]

@gurzixo much better to steer to an officially supported SBC from armbian, if you need something reliable: https://www.armbian.com/download/?device_support=Platinum support&arch=aarch64

[gurzixo]

@jockThanks Jock, I know that and I agree with you. I could also take an Rpi4 with an SSD, but it is also for the fun of tinkering and checking if I still have "green fingers"

The app is not critical as it's for displaying the welcome book and appliance manuals in some holiday rentals on the guests's phone from a QR code.

[incbot]

Good day JOCK. Thank you so much for linking to the latest armbian releases. I installed 25.5.0-trunk.444 and brought it to 25.8.0-trunk.26 by several updates. The system is loaded and steadily updated. Managed to configure ethernet and wifi with static addresses. The network works well. The question is that I can't figure out how to start bluetooth. At first, the system worked without overlays and tried to load BCM43342 when I connected overlay 6330 using armbian-config, nothing changed. I don't have too much experience in unix. What am I doing wrong? PS I attach a photo of the board and  armmonitor -u)

[Андрей Димов]

Incbot, hi I have this problem too. Use rk3318-config command to set device tree overlay (on the second step push space then enter) and then don't touch device tree overlay in armbian-config. After reboot use command hciconfig -a, if it have some message on screen - Bluetooth working

Edited May 19 by Андрей Димов

[incbot]

I turned off overlay rockchip-RK3318-box-wlan-ap6330 in armbian-config (not a single overlay was selected here anymore) and selected the rk3318-box-led-conf1 option through rk3318-config (in this case, overlays rk3318-box-led-conf1 and rk3318-box-wlan-ap6334 are connected to boot). A certain Bluetooth block appeared in the text of the armbianmonitor -u output (see new output here), but apparently the driver is still not the same and hciconfig -a does not work (there is no command in the system). Any more ideas?

Edited May 20 by incbot

[Андрей Димов]

Incbot, after set device tree option in the rk3318-config, try enter reboot command (don't reset power, need reboot only), then try hciconfig -a

[incbot]

All the data above was collected after installing the necessary overlay in rk3318-config and then rebooting...

[Андрей Димов]

This method works for me, but I don't  change Bluetooth driver's. You can also try command:

 

apt reinstall bluez

 

apt --fix-broken install

[incbot]

I tried to do the following: 

 

01) replace the driver (do symb link): 

        ln -s /usr/lib/firmware/brcm/BCM43342.hcd /usr/lib/firmware/brcm/BCM.hcd. 

02) Judging by armbianmonitor -u, the chip was recognized. 

03) Installed the necessary packet: 

        sudo apt install bluetooth -y 

04) Tested that the service Bluetooth is running: 

       sudo service bluetooth status. 

05) Got "Running" 

06) Only after these actions hciconfig -a gave a meaningful conclusion... 

07) Next, after all this, I tried to control bluetooth via : 

      sudo bluetoothctl

08) On the show command inside, I finally saw my device wiyh MAC and that it was active. 

09) Put it into detected mode: 

      discoverable on 

10) Saw the alias rk3318-box on my phone when searching for Bluetooth devices around. 

11) Despite the fact that an invitation with the same PIN code for connecting appeared both on the tvbox and on the phone, for some reason it is not possible to connect them. At the same time, for the tvbox mode Pairable: yes

 

!!! THE REASON IS NOT CLEAR TO ME, but it is definitely associated with tvbox, because as soon as I confirm the connection (press "Y") on it, the connection is cut off... Phone confirmation does not interrupt the connection at first. WTF? I reinvent the wheel again?????

 

PS After pair coomand on tvbox i see it:

 

[agent] Confirm passkey 815681 (yes/no): y
Failed to pair: org.bluez.Error.AuthenticationFailed

Edited May 20 by incbot

[incbot]

I am need to sleep more)) I stubbornly answered "y" instead of "yes" when pairing with the phone in bluetoothctl )))) It turned out to connect on "yes".

 

😀😀😀 Say me please an exists easier way to solve  the my problem with Bluetooth?

Edited May 20 by incbot

[Андрей Димов]

I can suggest only hard way - clear installation armbian then HA, without manipulation with driver and use rk3318-config to set device tree option

[paradigman]

I would like to use my device as a VPN client, i.e. connect to a remote OpenVPN server. How can I enable the Tun/Tap module on my board?

 

[gurzixo]

Hello again,

I am struggling to install armbian on my H96Max (blue PCB RK3318_V1.4, 4G/64G).

The Armbian_22.11.0-trunk_Rk3318-box_bullseye_edge_5.19.15_minimal.img image works OK (at least for the display).

All the new images fail to initialise the display (a 4K HDMI monitor), either using *_minimal.img or *_gnome_desktop.img

I managed to install the latest (Armbian_community_25.8.0-trunk.8_Rk3318-box_noble_current_6.12.28_gnome_desktop.img) image using the serial console. Kernel is 6.12.28

I can now connect using ssh on ethernet (the WIFI does not work yet...)

 

I get in syslog and dmesg a LOT of the following errors:

[ 2683.281403] ------------[ cut here ]------------
[ 2683.281441] [CRTC:38:crtc-0] vblank wait timed out
[ 2683.281570] WARNING: CPU: 1 PID: 50 at drivers/gpu/drm/drm_atomic_helper.c:1682 drm_atomic_helper_wait_for_vblanks.part.0+0x238/0x25c
[ 2683.281629] Modules linked in: cfg80211 rfcomm algif_hash algif_skcipher af_alg bnep sunrpc snd_soc_hdmi_codec hci_uart btqca hantro_vpu btrtl btintel crct10dif_ce rockchip_vdec(C) v4l2_jpeg v4l2_vp9 btbcm rockchip_rga v4l2_h264 bluetooth videobuf2_dma_contig snd_soc_spdif_tx gpio_ir_recv videobuf2_dma_sg rc_core v4l2_mem2mem rfkill videobuf2_memops videobuf2_v4l2 dw_hdmi_i2s_audio videodev dw_hdmi_cec lima snd_soc_simple_card videobuf2_common snd_soc_rockchip_spdif snd_soc_rockchip_i2s snd_soc_rk3328 snd_soc_simple_card_utils gpu_sched drm_shmem_helper mc snd_soc_core rk_crypto snd_compress rng_core snd_pcm_dmaengine snd_pcm snd_timer snd soundcore cpufreq_dt joydev zram zsmalloc binfmt_misc sch_fq_codel dm_mod autofs4 dwmac_rk stmmac_platform stmmac pcs_xpcs nvmem_rockchip_efuse rockchipdrm dw_hdmi_qp gpio_syscon dw_hdmi cec dw_mipi_dsi analogix_dp drm_display_helper adc_keys
[ 2683.282340] CPU: 1 UID: 0 PID: 50 Comm: kworker/u16:2 Tainted: G    B   WC         6.12.28-current-rockchip64 #1
[ 2683.282375] Tainted: [B]=BAD_PAGE, [W]=WARN, [C]=CRAP
[ 2683.282389] Hardware name: Rockchip RK3318 BOX (DT)
[ 2683.282409] Workqueue: events_unbound commit_work
[ 2683.282446] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2683.282471] pc : drm_atomic_helper_wait_for_vblanks.part.0+0x238/0x25c
[ 2683.282499] lr : drm_atomic_helper_wait_for_vblanks.part.0+0x238/0x25c
[ 2683.282531] sp : ffff8000809dbcb0
[ 2683.282542] x29: ffff8000809dbce0 x28: 00000000000007d5 x27: 0000000000000000
[ 2683.282580] x26: 0000000000000001 x25: 0000000000000000 x24: ffff6d33cdf68000
[ 2683.282616] x23: 0000000000000001 x22: 0000000000000000 x21: ffff6d33cc6f6280
[ 2683.282654] x20: ffff6d33cdf70080 x19: 0000000000000000 x18: ffffffffffffffff
[ 2683.282691] x17: 000000040044ffff x16: 00500072b5503510 x15: ffff8000809db860
[ 2683.282727] x14: 00000000ffffffea x13: ffff8000809db9f8 x12: ffffd4f64aa4ac10
[ 2683.282768] x11: 0000000000032030 x10: 0000000000031fe0 x9 : 0000000000024330
[ 2683.282805] x8 : c0000000fffff822 x7 : ffffd4f64a99aa18 x6 : 0000000000084bb0
[ 2683.282842] x5 : ffff6d34be7424c8 x4 : 0000000000000000 x3 : 0000000000000027
[ 2683.282878] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff6d33c4c4c600
[ 2683.282918] Call trace:
[ 2683.282932]  drm_atomic_helper_wait_for_vblanks.part.0+0x238/0x25c
[ 2683.282962]  drm_atomic_helper_commit_tail_rpm+0x84/0xa0
[ 2683.282992]  commit_tail+0xa4/0x18c
[ 2683.283019]  commit_work+0x14/0x20
[ 2683.283043]  process_one_work+0x16c/0x3e4
[ 2683.283073]  worker_thread+0x2d0/0x3d8
[ 2683.283097]  kthread+0x10c/0x110
[ 2683.283123]  ret_from_fork+0x10/0x20
[ 2683.283151] ---[ end trace 0000000000000000 ]---

 

This seems to come from the accelerated graphic driver. The corresponding function can be seen there: drm_atomic_helper.c

This function waits for receiving a vertical blanking pulse that never comes, so the warning at line 1679 is triggered.

 

I don't intend to do hard-core graphics so I don't care about graphic performance. In fact this lovely box will be used for hosting a headless server.

Is there a way to use a legacy or un-accelerated graphic driver?

If not, how could I remove entirely the graphic subsystem and use only character mode?

 

Thanks!

Michel

 

EDIT: In fact the first warning occurs when switching to the colour frame buffer device:

...

rk_gmac-dwmac ff550000.ethernet: Enable RX Mitigation via HW Watchdog Timer
May 29 19:00:08 h96max kernel: rk_gmac-dwmac ff550000.ethernet: device MAC address de:10:75:60:c0:cb
May 29 19:00:08 h96max kernel: Console: switching to colour frame buffer device 160x45
May 29 19:00:08 h96max kernel: ------------[ cut here ]------------
May 29 19:00:08 h96max kernel: [CRTC:38:crtc-0] vblank wait timed out
May 29 19:00:08 h96max kernel: WARNING: CPU: 0 PID: 74 at drivers/gpu/drm/drm_atomic_helper.c:1682 drm_atomic_helper_wait_for_vblanks.part.0+0x238/0x25c
May 29 19:00:08 h96max kernel: Modules linked in: dwmac_rk stmmac_platform stmmac pcs_xpcs nvmem_rockchip_efuse gpio_syscon rockchipdrm dw_hdmi_qp dw_hdmi cec dw_mipi_dsi analogix_dp drm_display_helper adc_keys
May 29 19:00:08 h96max kernel: CPU: 0 UID: 0 PID: 74 Comm: kworker/u16:5 Tainted: G    B              6.12.28-current-rockchip64 #1
May 29 19:00:08 h96max kernel: Tainted: [B]=BAD_PAGE

...

 

So I suspect that not switching to a FB could solve my problem

Edited May 29 by gurzixo
Added the timing of first warning

[Artem Kochegizov]

Hello! I try to flash my H96Max on RK3318 but i cannot load armbian. After success flash armbian to emmc i remove sd and nothing, nothing load and nothing in uart port, only red led light and thats all.

 

Здравствуйте! Я пытаюсь прошить свой H96Max на RK3318, но не могу загрузить armbian. После успешной прошивки armbian на emmc я извлекаю SD-карту, и ничего, ничего не загружается и ничего не отображается в последовательном порту, только красный светодиод и всё.

 

when i'm load from sd multitool i get  this log from uart

 

i'm try to find u-boot on my h96max emmc and nothing, first 100bytes empty. Where i can get u-boot?

LoadLog.txt

Edited yesterday at 11:44 AM by Artem Kochegizov

[Offeacy61]

02.05.2021 в 21:31, Generic_user сказал:

I bought an x88 (rk3318 4g ram 64 gb rom version) and was happy with the specs.

After trying it with the SD card everything was working so I tried to burn it into the internal flash.

During the installation process(first using rk-config, then directly with dd) the whole process gets stuck during the copy of the /usr directory.

After multiple attempts the box seems to be bricked, and I can't even boot with an SD card with a saved tested armbian image.

 

the bricking could be the result of multiple issues:

-power supply apparently outputting 13V, hence making the box "blink" instead of booting

-deleting binaries on the internal flash

 

Anyway, my tv box isn't working at the moment and I am trying my best to try different images and dtbs.

If I can't get support from the seller I might look at the serial output and investigate more


Remote Control and Management: As for managing and controlling devices remotely, have you considered using a remote control app for easy device management? Apps like the Universal Remote App For iPhone by Eltima could make it more convenient to control and manage your devices, whether you're troubleshooting or doing everyday tasks. It’s a great tool for people managing devices across different locations, especially when you need remote control of something like your x88 box.

It sounds like you're in a tough spot with your x88 box, but there are definitely a few things you can try to unbrick it.
 

Check Power Supply: As you mentioned, the power supply might be outputting 13V, which is not ideal. It's crucial to have a stable 5V supply for the device to boot properly. If you can, try using a different power adapter (5V, 2A) and see if that helps stabilize the boot process.

 

Use a Correct Recovery Image: Make sure you're using the correct image for the box. It seems like you were trying to burn the image directly, but if the process was interrupted, it could leave your internal storage in an inconsistent state. Try downloading the official firmware for your box model from the manufacturer's site (if available) or from trusted forums where users with similar devices share their files.

 

Try the USB Burning Tool: Some boxes like this one can be recovered using a tool like the USB Burning Tool (if it's based on Rockchip). You can try flashing the firmware through USB using the tool while the box is in recovery mode. Here’s a general approach:

 

• Download and install the USB Burning Tool.
•  
• Put your box into MaskROM Mode (this usually involves shorting specific pins or pressing a button while plugging the box into your computer via USB).
•  
• Connect your device to the PC and use the USB Burning Tool to flash the firmware.

 

Serial Console Output: If you're comfortable with it, connecting a serial console to the box can give you a lot of insight into where things are failing. This could help identify whether it's a hardware or software issue. The serial output could give you error messages that could point to a specific issue (e.g., faulty bootloader or file system corruption).

 

SD Card Recovery: If you can't get it to boot from the internal flash, continue using the SD card with a stable Armbian image. If the internal storage is corrupt, you might still be able to boot and recover your box through the SD card by reinstalling the firmware on the internal storage via the system running off the SD card.

 

If you haven't already, you could also try reaching out to the manufacturer or seller for support, as they might be able to help you with the recovery process. But if that’s not an option, digging into the serial console is definitely your best bet.

 

Good luck! Hopefully, you'll be able to get your device back up and running soon.