If you search Alexpress for keywords
H96Max v11 TV Box
you will find lot of sellers. You may find a better deal than what I found.
Some sellers list lower price, but in fine print mention shipping US$ 5~10. Some others have little higher price, but free shipment, which makes total cheaper, like the one I purchased CA$40 (= US$30), after $3.50 discount over list price, and free shipping, and this one has 4GB RAM, 32GB emmc flash.
Went to following post in Armbian CSC forum, and followed instructions:
https://forum.armbian.com/topic/26978-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=143890
(1) Downloaded file nvram_2734c.txt from above noted post
NOTE: Had to log-in to Armbian CSC forum to download above noted file.
(2) Issued following command to preserve original wifi config file by adding .ORIG at it’s name’s end
sudo mv /usr/lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt /usr/lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt.ORIG
(3) Created new blank wifi config file by command below:
sudo nano /usr/lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt
(4) Pasted into the new blank file, the text copied from file nvram_2734c.txt (see step 1 above). Saved and closed file.
(5) Rebooted
(6) Ran Command sudo nmtui (or sudo armbian-config) and configured & activated on-board WiFi
Armbian_23.02.2_Rk3318-box_bullseye_current_5.15.93.img.xz
Armbian_23.02.2_Rk3318-box_jammy_current_5.15.93_xfce_desktop.img.xz
Step-1:
Downloaded tool “multitool”
https://users.armbian.com/jock/rk3318/multitool.img.xz
Step-2
Burned “multitool” image to 16GB microSD card
Step-3
Clicked microSD card’s drive letter to open it. In opened drive, opened folder named “images”. Copied downloaded image “Armbian_23.02.2_Rk3318-box_jammy_current_5.15.93_xfce_desktop.img.xz” to the images folder of microSD card. Ejected card from Laptop/Desktop.
Step-4:
Powered off H96Max TV Box. Slipped microSD card into its card slot. Connected Monitor to HDMI port of TV Box, and Keyboard to USB port of TV Box.
Powered up TV Box, clicked OK to disclaimer, then using keyboard arrow keys, moved selection to “Burn image”, selected the emmc and image, press Enter Key and waited till installation finished.
Step-5:
Using arrows keys, moved selection to shutdown and pressed Enter Key.
Step-6:
After shutdown, pulled power plug out of wall socket. Removed microSD card from TV Box, and after removing microSD card, inserted power plug into wall socket. The TV Box booted and started initial setup dialogues for Armbian (root password setup, username and password setup, locale and language setup etc).
Step-7:
After initial setup, gave reboot command, and TV Box booted with Armbian XCFE Desktop GUI.
Very interesting approach.
- dump1090-fa ver 8.2
- piaware ver 8.2
- piaware-web ver 8.2
- dump978-fa ver 8.2
I’ve installed a t620 at a remote site and had a bit of an issue.
By ‘remote’, I mean difficult to access and no 240V. (just PV and battery). The T620 runs on 19VDC, so I use a 24V → 19V DC-DC brick for the supply.
HP used the same power connector for many different products with widely varying power requirements. This is the ‘why’ the plug has three contacts (Pos, Neg, Sig). Dell do a similar thing and the ‘Sig’ has I2C comms, but the HP only includes a high value resistor to indicate the power rating of the brick (if it’s out of spec, the PC doesn’t try to start).
I had a hunt around and found I could buy a 2.1mm barrel to HP plug adapter, so I ordered two from different suppliers).
What arrived looked perfect. A good snug fit and a multimeter told be the Sig resistor was in range - except it didn’t work.
Everything measured ok and poking a meter into the t620 showed it was getting power, but …
Turned out the the Sig pin on the adapter (centre pin) was a couple of mm too short and didn’t make contact inside the t620’s socket.
Take 2, order a fly-lead with the correct plug. This was just a cable with bare wires on one end and the HP plug on the other. It had no Sig resistor, but all three wires were present, so adding a resistor wasn’t a big deal.
Just thought I’d toss this in for anyone wanting to run a Thinclient on low voltage.
I only have the original powersupplies with the T620’s
I have currently 4 of them in use, 2x Win10 as a printserver and a fileserver and 2x Debian (1x Debian 11 with Flightaware and 1 with Debian 12 Bookworm for testing purposes).
So far no issues with the powersupplies and the pins. But I understand you had to improvise.
After upgrading the OS to jammy_current_6.1.30_xfce_desktop, what extra steps are needed to enable the WIFI? Are the steps detailed stating how file nvram_2734c.txt has to be edited, etc, still needed with the newer version of Armbian?
I have not upgraded to the newer version “jammy_current_6.1.30_xfce_desktop”, so cannot tell.
Is WiFi not working on the upgraded OS as well?
If so please ask in the Armbian CSC forum:
https://forum.armbian.com/topic/26978-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=143890
Meanwhile, I see that prices for Raspberry Pi’s are coming down. I saw an RPi-4B 4 GB on Amazon for $80. Still not what it should be, but getting closer. Also there’s starting to be more availability on https://rpilocator.com.
I just purchased an RPi 4 4gb for $85 w/free standard shipping from China. Order shipped June 7 and is arriving June 14. I ordered thru Amazon.com and had several vendors from which to select.
I have now upgraded OS to:
Armbian_23.5.1_Rk3318-box_jammy_current_6.1.30_xfce_desktop.img.xz
Downloaded from:
https://imola.armbian.com/dl/rk3318-box/archive/
YES, to enableg the on-board WiFi with this latest OS version also, I had to do exactly the same workaround (nvram_2734c.txt) as described in my post linked below:
https://discussions.flightaware.com/t/fyi-alternatives-to-raspberry-pi-for-this-hobby/82096/187
nvram_2734c.txt# original nvram found in Android sources for HS2734C SP
#
#
manfid=0x2d0
prodid=0x05c1
vendid=0x14e4
devid=0x4380
boardtype=0x05de
boardrev=0x1200
boardnum=22
macaddr=00:90:4c:c5:12:38
sromrev=3# brcm4334 nvram for AP6334/HK6334/SP6334
boardflags=0x10081a01
xtalfreq=37400
nocrc=1
ag0=252
aa2g=1
ccode=ALL
regrev=1
pa0itssit=0x20
#PA parameters for 2.4GHz_QM_4p2_120517
pa0b0=0x2AFD
pa0b1=0xFB41
pa0b2=0x6C
tssifloor2g=12
extpagain2g=2
extpagain5g=2
cckPwrOffset=12
# rssi params for 2.4GHz
rssismf2g=0x2
rssismc2g=0xC
rssisav2g=0x1
# rssi params for 5GHz
rssismf5g=0x8
rssismc5g=0x8
rssisav5g=0x1
#PA parameters for lower band_QM_4p2_120214
pa1lob0=0x1672
pa1lob1=0xFD53
pa1lob2=0xFF69
tssifloor5gl=18
#PA parameters for midband
pa1b0=0x1712
pa1b1=0xFD5D
pa1b2=0xFF82
tssifloor5gm=18
#PA parameters for high band
pa1hib0=0x1696
pa1hib1=0xFD64
pa1hib2=0xFF7A
tssifloor5gh=18
PwrOffset40mhz5g=-10
rxpo5g=0
maxp2ga0=78
ofdm2gpo=0x44444444
mcs2gpo0=0xaaaa
mcs2gpo1=0xaaaa
cckdigfilttype=24
ofdmdigfilttype2g=9
ofdmdigfilttype5g=3
ofdm40digfilttype=8
maxp5gla0=64
ofdm5glpo=0x33333333
mcs5glpo0=0x5555
mcs5glpo1=0x5555
mcs5glpo2=0x7777
mcs5glpo3=0x7777
maxp5ga0=66
ofdm5gpo=0x33333333
mcs5gpo0=0x5555
mcs5gpo1=0x5555
mcs5gpo2=0x7777
mcs5gpo3=0x7777
maxp5gha0=65
ofdm5ghpo=0x33333333
mcs5ghpo0=0x5555
mcs5ghpo1=0x5555
mcs5ghpo2=0x7777
mcs5ghpo3=0x7777
#il0macaddr=00:90:4c:c5:12:38
wl0id=0x431b
pagc2g=0x10
#For HS2734C Module
swctrlmap_2g=0x0c0c0c0c,0x12120202,0x02020202,0x11202,0x1ff
swctrlmap_5g=0x40404040,0xa0a0a0a0,0x80808080,0x11202,0x2f8
elna_off_gain_idx_2g=30
triso2g=6
triso5g=3
muxenab=0x10
#sd_gpout=0
#sd_oobonly=1
dacrate2xen=1
txalpfbyp=1
# In RC58.29, adding to keep the txALPF powered up , even when the txALPF is bypassed.
txalpfpu=1
# 11b ACR Performance
aci_detect_en_2g=1
dacpu.fab.4=1
gain_settle_dly_2g=4
gain_settle_dly_5g=4
#For TSMC rx sensitivity in low rate
noise_cal_po_2g=-1
#For UMC rx sensitivity in low rate
noise_cal_po_2g.fab.4=6
noise_cal_po_40_2g=-1
noise_cal_high_gain_2g=73
noise_cal_nf_substract_val_2g=346
noise_cal_po_5g=-1
noise_cal_po_40_5g=-1
noise_cal_high_gain_5g=73
# Adding in RC58.29
noise_cal_nf_substract_val_5g=346
iqlocalidx5g=55
# In RC58.35/38. Added on For LOFT
dlocalidx5g=75
# In RC58.33, change EPA_or_PAD_lpbck5g=1 to lpbckmode5g=1
#EPA_or_PAD_lpbck5g=1
lpbckmode5g=1
txiqlopapu5g=0
iqcalidx5g=50
txiqlopapu2g=0
#In RC58.35, Change Value to 5
dlorange_lowlimit=5
loflag=1
# In RC58.29, for RSSI return with pkteng_stats
#rssicorrnorm=3
#rssicorratten=3
#rssicorrnorm5g=5,3,3
#rssicorratten5g=5,3,3
#for BT-coexistence
btc_params80=0
btc_params6=10
btc_params95=53
My wifi is working. I had to turn on the wifi radio. This page was very helpful:
So I have confirmed that my file /usr/lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt
is identical to the one you have shown. I rebooted (power cycled) my rk3318 box but I am not able to get WIFI interface to come on. Is there some further step needed to enable WIFI on my box?
I do see this in dmesg output:
[ 15.764408] brcmfmac: F1 signature read @0x18000000=0x16034334
[ 15.772263] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3
[ 15.794616] usbcore: registered new interface driver brcmfmac
[ 15.797774] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.rockchip,rk3318-box.bin failed with error -2
[ 15.811338] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.clm_blob failed with error -2
rk3318-box> nmcli
eth0: connected to Armbian ethernet
“eth0”
ethernet (rk_gmac-dwmac), 3E:60:58:2D:4A:43, hw, mtu 1500
ip4 default
inet4 192.168.1.49/24
route4 192.168.1.0/24 metric 100
route4 default via 192.168.1.1 metric 100
route4 169.254.0.0/16 metric 1000
inet6 fe80::e7c8:a970:6fb1:64e8/64
route6 fe80::/64 metric 1024
wlan0: unavailable
“Broadcom BCM4334”
wifi (brcmfmac), 90:18:7C:74:03:B1, sw disabled, hw, mtu 1500
lo: unmanaged
“lo”
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
DNS configuration:
servers: 192.168.1.1
domains: home
interface: eth0
Use “nmcli device show” to get complete information about known devices and
“nmcli connection show” to get an overview on active connection profiles.
Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
rk3318-box> nmcli device show
GENERAL.DEVICE: eth0
GENERAL.TYPE: ethernet
GENERAL.HWADDR: 3E:60:58:2D:4A:43
GENERAL.MTU: 1500
GENERAL.STATE: 100 (connected)
GENERAL.CONNECTION: Armbian ethernet
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/1
WIRED-PROPERTIES.CARRIER: on
IP4.ADDRESS[1]: 192.168.1.49/24
IP4.GATEWAY: 192.168.1.1
IP4.ROUTE[1]: dst = 192.168.1.0/24, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]: dst = 0.0.0.0/0, nh = 192.168.1.1, mt = 100
IP4.ROUTE[3]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
IP4.DNS[1]: 192.168.1.1
IP4.DOMAIN[1]: home
IP6.ADDRESS[1]: fe80::e7c8:a970:6fb1:64e8/64
IP6.GATEWAY: –
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 1024
GENERAL.DEVICE: wlan0
GENERAL.TYPE: wifi
GENERAL.HWADDR: 90:18:7C:74:03:B1
GENERAL.MTU: 1500
GENERAL.STATE: 20 (unavailable)
GENERAL.CONNECTION: –
GENERAL.CON-PATH: –
IP4.GATEWAY: –
IP6.GATEWAY: –
GENERAL.DEVICE: lo
GENERAL.TYPE: loopback
GENERAL.HWADDR: 00:00:00:00:00:00
GENERAL.MTU: 65536
GENERAL.STATE: 10 (unmanaged)
GENERAL.CONNECTION: –
GENERAL.CON-PATH: –
IP4.ADDRESS[1]: 127.0.0.1/8
IP4.GATEWAY: –
IP6.ADDRESS[1]: ::1/128
IP6.GATEWAY: –
IP6.ROUTE[1]: dst = ::1/128, nh = ::, mt = 256
Do NOT use nmcli.
Use nmtui
sudo nmtui
The original file installed by default with the OS image is NOT identical to the file nvram_2734c.txt .
It is also NOT identical to the content of nvram_2734c.txt which I have posted.
If you do not replace contents of default file by the contents of nvram_2734c.txt, WiFi will appear to work, but will FAIL to connect
What I meant to say is that after I had followed your steps and downloaded the nvram_2734c.txt file and installed it I still didn’t have working WIFI as I had not
And I could not figure out using “nmtui” how to do these 2 steps. But once I did steps 1) and 2) using “nmcli” per the link I had shared my WIFI is working fine. So I was just saying I rechecked ‘md5sum’ values and confirmed that I had installed the new file.
I am new to ADS-B tracking world though a life long aviation enthusiast since my youth. I am having lots of fun tracking planes in my area, seeing who is going where. (Of course I could do so before on flightaware website but somehow more exciting to listen to planes w/ my own receiver.)
Thanks for all the detailed instructions.
Wondering if anyone is using a Thin Client for both FA and LiveATC?
It could be done, as long as you are referring to the liveatc website ?
If you mean real live atc on an sdr dongle it would require a second dongle.
It would need a graphical user interface I guess, operating Debian or Dietpi. I have my TC’s (HP T620 2 dual and 2 quadcore running in command line interface mode for FA but that could also be done in a GUI setting. Never ventured there 
I have tried both GUI and CLI (headless) versions of Debian 11 OS.
I found that in CLI version, my ThinClient HP520 performs somewhat faster and the CPU temperature is also somewhat lower.
Same is the result when I tried headless CLi and GUI versions of Armbian OS on Android TV Box H96Max Rockchip3318
I’ve tried the GUI versions as well but never with FA and Liveatc in conjunction to each other. Dual core TC’s will benefit the most from the CLI, for quadcore CPU TC’s this “shouldn’t” be a problem.
Since I never done that combo I assume it will work but have not tried it.
Max Temp I’ve seen on a quadcore was 59 degrees Celsius