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 yesterday at 07:54 PM 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 5 hours ago 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 1 hour ago 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 1 hour ago 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