CSC Armbian for RK3318/RK3328 TV box boards

[Vidhome]

I tried, it didn't take off, only after these steps it works.

[Jean-Francois Lessard]

@jock and @MattWestB 

 

The module probe warning needs to be investigated further.

 

About the display service, it's simply a bash script. It relies on existing other kernel modules to manages the icons: ledtrig_timer and  ledtrig_netdev. ledtrig_timer is a basic timer trigger to make the colon blink every half second and is missing from @MattWestB stack trace. If the module is not loaded, the display service will fail on line "echo timer > /sys/class/leds/display::colon/trigger".  So make sure the module ledtrig_timer is available and loaded first. "make service-install" adds a modprobe soft dependency on ledtrig_timer and ledtrig_netdev and will load them automatically if present. So you just need to get sure the modules are built and available.

 

For testing the display LEDs and segments, the first thing to check is whether all LEDs and segments are turned on when probing the module (but before starting the display service). The driver purposely turns on everything on the controller can on probing. If the led doesn't turn on, it's a device tree / controller model / hardware problem. Then you can use "display-utils -c" and follow these instructions: Check your display configuration.

Edited October 16 by Jean-Francois Lessard

[Jean-Francois Lessard]

@MattWestB did you happen to configure a default led trigger in your display device tree? I think that was the issue.

 

I've updated the tm16xx GitHub repo with a couple of changes:

- fixed default trigger init value

- fixed /usr/sbin service path

- revised error management & verbosity of display service

- added prompts to display check

 

Please update to this latest version and confirm if it solves your issues (please tag me in your reply).

[MattWestB]

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.

[haven]

I have been running all ok with kernel 6.6.2-edge-rockchip64

A few days ago updated to 6.6.47-current-rockchip64, now HDMI audio is not working, video is ok, Everything else works like a charm.

Uboot has been also updated. 

I have all the output configuration well configured, but no output at all. Cards detected, output sink detected, default output points to the right ouput, not muted, volume 100%.

 

aplay -l 

card 0: HDMI [HDMI], device 0: ff000000.i2s-i2s-hifi i2s-hifi-0 [ff000000.i2s-i2s-hifi i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: ANALOG [ANALOG], device 0: ff010000.i2s-rk3328-hifi rk3328-hifi-0 [ff010000.i2s-rk3328-hifi rk3328-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: SPDIF [SPDIF], device 0: ff030000.spdif-dit-hifi dit-hifi-0 [ff030000.spdif-dit-hifi dit-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

 

In dmseg I see this error (maybe related):

[   69.740081] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22
[   69.769681] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_hw_params on i2s-hifi: -22

 

Any idea how to get HDMI audio working?

Edited October 20 by haven

[haven]

Update: 
the error I see in dmesg are irrilevant, I checked a good working system and they are still there without any issue.

Still no HDMI sound on kernel 6.6.47

[jock]

@haven could not check right now, but nothing should have changed from the audio side. Perhaps the order of the devices changed and what was once the default, now it is not anymore?

Recently I enjoyed some Quake running on an rk3318 box and analog audio was the default.

 

Those errors also are not relevant, the audio devices will still work with no issues.

[ExUser 44]

Hi everyone! I have 2 TV-boxes H96Max on RK3318 4/64 Gb. I would like to install Linux on them and get the most out of them. 
Ideally to use them as DAW and software synthesizer for Midi keyboard. But even using them as an office desktop would be cool too. 
I am new to the Armbian universe. Can you please tell me which image would be best for these tasks ? Maybe there are some installation and configuration guides. 
Having working wifi, bluetooth and clock is not necessary at all unlike sound. 
I apologize in advance if I have addressed to the wrong place

[MattWestB]

@ExUser 44 From the first post download and flash multitool on one SD-Card (USB is not supported by factory android bootloader) and put it in the box and power on.

Make one backup of the eMMCand then shutdown the box and copy the backup to one safe place.

Download one Armbian from links in the first post (stable Ubuntu or debian server or desktop).

Copy the tar file to the (multitool) sd-card image folder and puting it in the box and power it up.

The safest and brutal is erase eMMC and write the Arbian image to ti but can being one brick.

The more safe is only erase the eMMC then the SOC is not finding boot-loader on it its trying booting from sc-card .

If only erasing eMMC you can burning Armbian on one SD-Card and the system shall booting from it  and cant being bricked.

Then getting it working try writing the eMMC with multitol and hope its working well (then you also getting USB boot support).

[haven]

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 ..

[Truong Thinh Chau]

@jock Please help me!! I want to run armbian on my android box but multitool not work!!

My device is H30 Rk3318 4G/64GB. You can see here for full specs:
https://bringyourhope.en.made-in-china.com/product/vZjmPilhAJVo/China-Rk3318-Android-Smart-TV-Box-4GB-RAM-64GM-ROM.html

 

My stock rom link here: https://mega.nz/file/f7oxwRyL#MlehtAsq-XvCw7yYrdBqJuxQMtASRqEjbnDvtOHqbgU

 

 

dmesg.multitool.log

Edited November 3 by Truong Thinh Chau

[jock]

@Truong Thinh Chau hello, happy to lend a hand, but you should be more specific on what is your problem... dmesg looks ok to me; your board is a new entry too, and it looks to me it has an unknown (to me) PMIC that could be a source of issues.

I will try to have a look into the dtb from your firmware (thanks for that), but lately I've been quite busy and can't promise anything

[Truong Thinh Chau]

@jock Thank your support!
My device got black screen when i tried to boot with multitool. So i cant install armbian for my device. I uploaded my device dtb that extract from boot.img, you can check it

rk3328-evb.7z

Edited November 3 by Truong Thinh Chau

[jock]

@Truong Thinh Chau perfect, thanks fot the device tree, I had the chance to give a quick look into and I can't see anything very different about your board, so it should work out of the box. As long as dmesg looks ok to me, it could be an issue with HDMI. Did you try to access the box via SSH? Here are the instructions: https://forum.armbian.com/topic/34923-csc-armbian-for-rk322x-tv-box-boards/page/45/#comment-135407

 

In case HDMI is not accessible or is not working, the multitool can be operated via regular SSH access, just give a dozen seconds or more to boot. The board led should be blinking when ready and the device should be pingable.

[Truong Thinh Chau]

Thanks @jock!!
Yeah!! SSH worked fine with me and Armbian worked! I have one more question.

How to fix hdmi to display??

Edited November 3 by Truong Thinh Chau

[jock]

@Truong Thinh Chau I see that you are using an armbian image from a third-party source (ophub), I'm sorry but you have to ask them about issues; I'm not aware of their customizations and modifications. If you want help from this forum, please use an image from an official source.

[Truong Thinh Chau]

@jock I so sorry abort that. I installed Armbian from OFFICIAL source!! Please help me fix hdmi and why does my device ram memory have 2GB? 

 

Edited November 4 by Truong Thinh Chau

[jock]

@Truong Thinh Chau Your board has 2GB of RAM because the tv box has fake specs. My tv box also claims 4gb of RAM, but has 2.

 

About the HDMI issue, in 6.6 kernel there were some important patches to improve HDMI compatibility, but general HDMI raccomendations apply, so try another cable or try another monitor/TV.

There could be something related to the the device tree (a GPIO, mostly), but I had no time to check in detail, sorry.

 

What you can also do is try to use get-edid/parse-edid (google for tutorials) to try and read the EDID from the connected monitor to see if it gets detected

[Truong Thinh Chau]

@jock I checked my box with parse-edid. You can check my picture, monitor deteched

 

[jock]

@Truong Thinh Chau hmmm, preferred mode is 10 which has no modeline but just hsync and vsync indications. i'm no expert in such material, but it doesn't look right to me and your monitor may be not exactly right telling the modeline to the kernel.

 

You may try to append extraargs=video=HDMI-A-1:1920x1080@60 in /boot/armbianEnv.txt to see if the console shows up. If it works, notice that this only forces the console framebuffer to handle such resolution and if you start a desktop environment it will go black again because you have to force the resolution the way the desktop environment wants (for example, xfce requires you to edit an XML configuration file if I recall correctly).

 

Some reference for the kernel command line flag: https://docs.kernel.org/fb/modedb.html

Examples: https://forum.armbian.com/topic/3749-how-to-change-resolution-hdmi-display-armbian527/?do=findComment&comment=66311 (here there is also an attempt to load a custom EDID, which I don't remember if it is enabled or not in the rockchip64 kernel)

 

[Enzo Turini]

Hello everyone, my beginner’s question on this topic is: I installed ‘armbian.com/jock/rk3318/Armbian_22.05.0-trunk_Rk3318-box_bullseye_current_5.15.35_minimal’ on my X88 Pro10 on a microSD, and everything works perfectly. If I were to transfer it to eMMc, would I be able to reinstall it again? Considering that my X88 Pro10 also runs Apache, MariaDB, PHP, Blynk, and DNS.

Another question: I also installed the version armbian.com/jock/rk3318/Armbian_23.08.0-trunk_Rk3318-box_bookworm_edge_6.3.13_minimal, but I couldn’t get the WiFi (BCM43342) to work. If anyone can answer these questions, I would appreciate it.

[haven]

Still working on HDMI audio problem, with updates.

( v24.8.4 for RK3318 Box running Armbian Linux 6.6.47-current-rockchip64)

Gdm3 + Xfce Desktop

 

If I boot with HDMI cable disconnected and connect the cable after BOOT completed  -> HDMI sound ok

If I boot with HDMI cable connected -> no HDMI sound

 

 I cannot find any error, all seems ok.

 

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDMI], device 0: ff000000.i2s-i2s-hifi i2s-hifi-0 [ff000000.i2s-i2s-hifi i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

 

parse-edid < /sys/class/drm/card0-HDMI-A-1/edid
Checksum Correct

Section "Monitor"
        Identifier "Panasonic-TV"
        ModelName "Panasonic-TV"
        VendorName "MEI"
        # Monitor Manufactured week 1 of 2020
        # EDID version 1.3
        # Digital Display
        DisplaySize 700 390
        Gamma 2.20
        Option "DPMS" "false"
        Horizsync 15-80
        VertRefresh 49-76
        # Maximum pixel clock is 150MHz
        #Not giving standard mode: 1280x1024, 60Hz

        #Extension block found. Parsing...
        Modeline        "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
        Modeline        "Mode 0" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
        Modeline        "Mode 1" 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync
        Modeline        "Mode 3" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
        Modeline        "Mode 4" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
        Modeline        "Mode 5" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
        Modeline        "Mode 6" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
        Modeline        "Mode 7" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace
        Modeline        "Mode 8" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
        Modeline        "Mode 9" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
        Modeline        "Mode 10" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
        Modeline        "Mode 11" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
        Modeline        "Mode 12" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
        Modeline        "Mode 13" 74.250 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
        Modeline        "Mode 14" 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
        Modeline        "Mode 15" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
        Modeline        "Mode 16" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
        Modeline        "Mode 17" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
        Modeline        "Mode 18" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
        Modeline        "Mode 19" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
        Modeline        "Mode 20" 27.00 720 732 796 864 576 581 586 625 -hsync -vsync
        Option "PreferredMode" "Mode 2"
EndSection

 

Tried to include in boot.cmd  extra option "hdmi.audio=1" with no results.

Tried to reload all alsa modules with sudo alsa force-reload ->  no results

 

Tried to disable and re-enable hdmi with:

xrandr --output HDMI-1 --off

xrandr --output HDMI-1 --auto

no result

Edited November 11 by haven

[jock]

@haven just had the chance to check with Debian Bookworm with no DE at all, bare terminal.

In my case, on my IIyama monitor, I have no issues at all with HDMI sound. It works on kernel 6.6.60 (latest 6.6 release so far), double checked on older 5.19 kernel and it works the same way.

 

Perhaps the issue is more software related with pulseaudio/xfce rather than related to bare hardware?

 

As a side note, I only have a very loud default volume, since there is no volume control and so I get 100% volume.

Turning down volume configuring alsa with "softvol" plugin (following this) fixes the loud volume and HDMI audio works fine in bare terminal for me.

[haven]

Update to hdmi no audio problem.

 

If I boot with HDMI cable disconnected and connect the cable after BOOT (15s after power-up)  -> HDMI sound ok

If I boot with HDMI cable connected -> no HDMI sound

 

tested  with kernel 6.6.60 current and 6.8.11 edge, same issue.

Pulseaudio not installed, only using alsa.

Analog audio working ok.

 

Monitor/tv edid detected correctly in all cases.
Studing some trick to delay HDMI detection after boot. or to re-trigger o re-load hdmi kernel module afterwards.

Still no results. 

Edited November 16 by haven

[Fcn3]

Hello folks, this is my first time posting in this forum. Thanks for all your contribution in making this amazing project!

 

I recently bought a H96Max v11 and I've attached a picture of the board.

 

 

Following the instructions, I'm able to get Armbian up and running. I then run the command sudo rk3318-config" and it asks me about the SoC type from one of the three options

1. RK3318 (max 1.1Ghz, slower but safer)

2. RK3318 (max 1.3Ghz)

3. RK3328 (max 1.3Ghz)

 

I hesitate between 1 and 2. I want 1.3Ghz if possible since it is about 20% faster than 1.1Ghz, but I also don't want to risk the board. How can I decide if my board is able to running at 1.3Ghz?

 

[haven]

 2. RK3318 (max 1.3Ghz) is safe enough (imho)