helix

Driver for integrated Wi-Fi card already compiled to Linux kernel. So, you should put to the brcm folder: * exactly one *.bin file, which is firmware for your Wi-Fi card. Kernel may look for this file during boot at several different filenames depending on hardware. * exactly one *.txt file, which is nvram parameters specific to your Wi-Fi card. Kernel also may try to reach this file at different filenames, but will use just one. clm_blob not always necessary, you may try to connect without it. Use nmtui command. *.hcd files - firmware for bluetooth module, if you do not need bluetooth you may safely ignore this files and then bluetooth will not appear in system. If your Tv-BOX was able to connect to Wi-Fi with the Android image installed, probably is will connect to same Wi-Fi with Armbian too, if the correct files are present in the brcm folder. In my case (AP6212 wifi module), I found correct files inside backup image I made with Multitool before flashing the Armbian image: original file was: fw_bcm43436b0.bin renamed: brcmfmac43430b0-sdio.bin original file was: nvram_ap6212.txt renamed: brcmfmac43430b0-sdio.txt You will need to somehow mount a backup copy of the original disk image, then open it as normal disk on regular pc and search for the necessary files.

Can you show output of this command? It will help to understand which file is required by the wifi driver. dmesg | grep brcm You can check which files driver looks for: #become root sudo su #create empty folder for wifi drivers cd /lib/firmware mv brcm brcm_back mkdir brcm reboot # after reboot messages from kernel will show missing files and errors dmesg | grep brcm #try to add missing files with correct filenames one by one and reboot again #first you will need correct firmware file *.bin #then nvram file *.txt #then possible one more, but it depends Consider using ssh. All configuration will be much more convenient just because you be able to copy paste commands from regular pc rather then logging in to the graphical environment and typing again. As i know, ssh enabled by default in armbian, so you will need just install client on you pc.

Check github releases page: https://github.com/armbian/community/releases/

finally bluetooth is working with such config: &uart0 { status = "okay"; uart-has-rtscts; bluetooth { pinctrl-names = "default"; compatible = "brcm,bcm43438-bt"; max-speed = <4000000>; clocks = <&rk805 0x01>; clock-names = "extclk"; shutdown-gpios = <&gpio1 RK_PC5 GPIO_ACTIVE_HIGH>; host-wakeup-gpios = <&gpio1 RK_PD2 GPIO_ACTIVE_HIGH>; }; }; firmware from android partition: sha256sum BCM4343B0.hcd 2252534aa755ab2857eb9765c55eb1d917e77992b5ee2ff701955cdcda9a8c9a BCM4343B0.hcd

Hello, In led-conf3 overlay sdio card on mmc1 is disabled as I can see, so wifi does not work with this overlay. I'm trying to add lines about rk805 to the initial working config rk3318-box and compile it, but it breaks sdio somehow: [ 1.141446] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 1.141560] mmc1: error -110 whilst initialising SDIO card [ 1.141743] dwmmc_rockchip ff510000.mmc: card claims to support voltages below defined range [ 1.145758] mmc1: error -110 whilst initialising MMC card [ 1.171182] mmc_host mmc1: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0) [ 1.345809] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 1.345933] mmc1: error -110 whilst initialising SDIO card [ 1.346116] dwmmc_rockchip ff510000.mmc: card claims to support voltages below defined range [ 1.350139] mmc1: error -110 whilst initialising MMC card [ 1.376838] mmc_host mmc1: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0) [ 1.618019] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 1.618141] mmc1: error -110 whilst initialising SDIO card [ 1.618299] dwmmc_rockchip ff510000.mmc: card claims to support voltages below defined range [ 1.622240] mmc1: error -110 whilst initialising MMC card [ 1.648896] mmc_host mmc1: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0) [ 2.096685] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 2.096818] mmc1: error -110 whilst initialising SDIO card [ 2.097000] dwmmc_rockchip ff510000.mmc: card claims to support voltages below defined range [ 2.100963] mmc1: error -110 whilst initialising MMC card [ 2.114878] mmc1: Failed to initialize a non-removable card Same result with rk3328-evb.dts from mainlain kernel 6.6.30, which have rk805 support by default. Ok, may be &sdio { vmmc-supply = <&vcc_io>; } is missing, so i add this line also, but card still does not initialising: [ 1.144440] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 1.144552] mmc1: error -110 whilst initialising SDIO card [ 1.167189] mmc_host mmc1: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0) [ 1.341046] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 1.341166] mmc1: error -110 whilst initialising SDIO card [ 1.367235] mmc_host mmc1: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0) [ 1.599001] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 1.599115] mmc1: error -110 whilst initialising SDIO card [ 1.625242] mmc_host mmc1: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0) [ 2.077057] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 2.077170] mmc1: error -110 whilst initialising SDIO card [ 2.077353] dwmmc_rockchip ff510000.mmc: card claims to support voltages below defined range [ 2.081314] mmc1: error -110 whilst initialising MMC card [ 2.095266] mmc1: Failed to initialize a non-removable card finally i managed to initialize sdio with enabled rk805: &sdio { post-power-on-delay-ms = <0x100>; }

🤯 Is there a tool to convert hex pointers (phandle) to human readable names when doing dtc -I dtb -O dts? For example, in original dtb file I have: io-domains { compatible = "rockchip,rk3328-io-voltage-domain"; status = "okay"; vccio1-supply = <0x29>; vccio2-supply = <0x2a>; vccio3-supply = <0x29>; vccio4-supply = <0x2b>; vccio5-supply = <0x29>; vccio6-supply = <0x29>; pmuio-supply = <0x29>; phandle = <0xa3>; }; where <0x29> is: RK805_DCDC4 {}

Hello, i'am struggling to add bluetooth support. Perhaps this will need to be described in the device tree? Enabling rk805-1 (with conf3 overlay) has a positive effect, but this overlay unfortunately also disables wifi on sdio. It appears my board is similar to rk3328-evb, which is correctly described in the mineline kernel in compact way. Can you give me some advice on how to create the correct device tree for my board?

This explains why firmware names does not match: https://patchwork.kernel.org/project/linux-wireless/patch/20210804231308.576071-1-mike.rudenko@gmail.com/#24397725 This will make wlan0 available and the adapter will be able to see networks: ln -s fw_bcm43436b0.bin brcmfmac43430b0-sdio.bin ln -s nvram_ap6212.txt brcmfmac43430b0-sdio.txt but there is still an error in the log: [43290.813906] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430b0-sdio.rockchip,rk3318-box.bin failed with error -2 [43290.817278] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430b0-sdio.clm_blob failed with error -2 [43290.967040] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [43290.967061] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) [43290.967934] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/2 wl0: Jul 20 2018 13:31:01 version 9.88.4.16 (d853e07@shgit) (r) FWID 01-f5575e5 es7.c5.n4.a3

Hello, I'am recently install Armbian_community 24.5.0-trunk.563 Bookworm with Linux 6.6.30-current-rockchip64 on RKM v3 tv-stick and it works good, excepting wireless: root@rk3318-box:~# dmesg | grep brcmfmac [ 10.596796] brcmfmac: F1 signature read @0x18000000=0x1532a9a6 [ 10.609573] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430b0-sdio for chip BCM43430/2 [ 10.610733] usbcore: registered new interface driver brcmfmac [ 10.611292] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430b0-sdio.rockchip,rk3318-box.bin failed with error -2 [ 10.611486] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430b0-sdio.bin failed with error -2 [ 11.619242] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 RKM v3 is tv-stick with rk3328 cpu 2g ram 16g emmc (https://www.rikomagic.com/en/showgoods/90.html) Inside the stick has rk805-1 power chip and klmag1jetd emmc chip. Not sure about memory because it under the same heat sink with cpu. Stock image, extracted from eMMC with help of multitool looks like this: /dev/loop0p1 16384 24575 8192 4M /dev/loop0p2 24576 32767 8192 4M /dev/loop0p3 32768 40959 8192 4M /dev/loop0p4 40960 43007 2048 1M /dev/loop0p5 43008 75775 32768 16M /dev/loop0p6 75776 141311 65536 32M /dev/loop0p7 141312 149503 8192 4M /dev/loop0p8 149504 157695 8192 4M /dev/loop0p9 157696 190463 32768 16M /dev/loop0p10 190464 192511 2048 1M /dev/loop0p11 192512 258047 65536 32M /dev/loop0p12 258048 389119 131072 64M /dev/loop0p13 389120 421887 32768 16M /dev/loop0p14 421888 946175 524288 256M /dev/loop0p15 946176 9334783 8388608 4G /dev/loop0p16 9334784 9367551 32768 16M /dev/loop0p17 9367552 13561855 4194304 2G /dev/loop0p18 13561856 13692927 131072 64M /dev/loop0p19 13692928 13693951 1024 512K /dev/loop0p20 13693952 13698047 4096 2M /dev/loop0p21 13698048 30535646 16837599 8G some partitions have dtbs: rkm_android7_dtbs/ ├── p1 │ ├── 00_kernel │ ├── 01_dtbdump_rockchip,rk3328-evb.dtb │ ├── 02_dtbdump_rockchip,rk3328-evb.dtb │ ├── 03_dtbdump_rockchip,rk3328-evb.dtb │ ├── 04_dtbdump_rockchip,rk3328-evb.dtb │ └── offset ├── p11 │ ├── 00_kernel │ ├── 01_dtbdump_rockchip,rk3328-evb-avb.dtb │ └── offset ├── p12 │ ├── 00_kernel │ ├── 01_dtbdump_rockchip,rk3328-evb-avb.dtb │ ├── 02_dtbdump_Rockchip_RK3128h_liantong_board.dtb │ └── offset └── p8 ├── 00_kernel ├── 01_dtbdump_Rockchip_RK3128h_liantong_board.dtb └── offset p1 01..04 files contain the same and look like for bootloader (very brief) p11 and p12 partition contain bigger one - 01_dtbdump_rockchip,rk3328-evb-avb.dtb (same content in both p11 and p12 partitions as i see). it contains such nodes: wireless-bluetooth { compatible = "bluetooth-platdata"; clocks = <0x9a 0x01>; clock-names = "ext_clock"; uart_rts_gpios = <0x76 0x0a 0x01>; pinctrl-names = "default\0rts_gpio"; pinctrl-0 = <0x9b>; pinctrl-1 = <0x9c>; BT,power_gpio = <0x76 0x15 0x00>; BT,wake_host_irq = <0x76 0x1a 0x00>; status = "okay"; }; wireless-wlan { compatible = "wlan-platdata"; rockchip,grf = <0x1c>; wifi_chip_type = "ap6354"; sdio_vref = <0x708>; WIFI,host_wake_irq = <0x76 0x13 0x00>; status = "okay"; }; inside the stick there is a chip with metal cap marked AP6212 but in the last_kmsg from stock firmware there is such a line: <6>[ 2.304427] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = ap6354 partition 17 have firmwares: ls rkm_v3_p17/etc/firmware/ 4343A0.hcd fw_bcm4334b1_ag_apsta.bin fw_RK903_p2p.bin rtl8723b_fw awnb108.hcd fw_bcm4334b1_ag.bin monet.bin rtl8723bs_config bcm20710a1_24M.hcd fw_bcm4334b1_ag_p2p.bin nh660.hcd rtl8723bs_fw bcm20710a1_26M.hcd fw_bcm4339a0_ag_apsta.bin nvram_4330_oob.txt rtl8723bs_VQ0_config bcm20710a1.hcd fw_bcm4339a0_ag.bin nvram_4330.txt rtl8723bs_VQ0_fw BCM20710A1.hcd fw_bcm4339a0_ag_p2p.bin nvram_AP6181.txt rtl8723bu_config bcm2076b1.hcd fw_bcm43436b0_apsta.bin nvram_AP6210_24M.txt rtl8723d_config bcm40183b2.hcd fw_bcm43436b0.bin nvram_AP6210.txt rtl8723d_fw bcm43241b4.hcd fw_bcm43436b0_p2p.bin nvram_ap6212a.txt rtl8723ds_config bcm4329.hcd fw_bcm43438a0_apsta.bin nvram_ap6212.txt rtl8723ds_fw BCM4330B1.hcd fw_bcm43438a0.bin nvram_ap6233f.txt rtl8761a_config bcm43341b0.hcd fw_bcm43438a0_p2p.bin nvram_AP6234.txt rtl8761a_fw bcm4339a0.hcd fw_bcm43438a1_apsta.bin nvram_ap6236.txt rtl8761at8192er_fw bcm43438a0.hcd fw_bcm43438a1.bin nvram_ap6255.txt rtl8761at_config bcm43438a1.hcd fw_bcm43438a1_p2p.bin nvram_ap62x2.txt rtl8761at_fw BCM4343A0.hcd fw_bcm43455c0_ag_apsta.bin nvram_AP6330.txt rtl8761au8192ee_fw BCM4343A1.hcd fw_bcm43455c0_ag.bin nvram_AP6335.txt rtl8761au8812ae_fw BCM4343B0.hcd fw_bcm43455c0_ag_p2p.bin nvram_ap6354.txt rtl8761au_fw BCM4345C0.hcd fw_bcm4354a1_ag_apsta.bin nvram_ap6356s.txt rtl8761aw8192eu_config bcm4354a1.hcd fw_bcm4354a1_ag.bin nvram_ap6356.txt rtl8761aw8192eu_fw BCM4354A2.hcd fw_bcm4354a1_ag_p2p.bin nvram_ap6398s.txt rtl8821a_config BCM4356A2.hcd fw_bcm4356a2_ag_apsta.bin nvram_AP6441.txt rtl8821a_fw BCM4359C0.hcd fw_bcm4356a2_ag.bin nvram_ap6452.txt rtl8821as_config fw_awnb108_ap.bin fw_bcm4356a2_ag_p2p.bin nvram_AP6476.txt rtl8821as_fw fw_awnb108.bin fw_bcm4359c0_ag_apsta.bin nvram_AP6493.txt rtl8821c_config fw_bcm40181a2_apsta.bin fw_bcm4359c0_ag.bin nvram_awnb108.txt rtl8821c_fw fw_bcm40181a2.bin fw_bcm4359c0_ag_p2p.bin nvram_B23.txt rtl8821cs_config fw_bcm40183b2_ag_apsta.bin fw_info.txt nvram_GB86302I.txt rtl8821cs_fw fw_bcm40183b2_ag.bin fw_RK901a0_apsta.bin nvram_RK901.txt rtl8822b_config fw_bcm40183b2_ag_p2p.bin fw_RK901a0.bin nvram_RK903_26M.cal rtl8822b_fw fw_bcm40183b2_apsta.bin fw_RK901a2_apsta.bin nvram_RK903.cal rtl8822bs_config fw_bcm40183b2.bin fw_RK901a2.bin nvram_RK903.txt rtl8822bs_fw fw_bcm40183b2_p2p.bin fw_RK901a2_p2p.bin nvram_WL211.txt ssv6051-sw.bin fw_bcm43241b4_ag_apsta.bin fw_RK901.bin otp.bin.z77 ssv6051-wifi.cfg fw_bcm43241b4_ag.bin fw_RK903_ag_apsta.bin rk903_26M.hcd TV_Firmware.mk fw_bcm43241b4_ag_p2p.bin fw_RK903_ag.bin rk903.hcd wifi_efuse_8189e.map fw_bcm4330_apsta.bin fw_RK903_ag_p2p.bin RT2870APCard.dat wifi_efuse_8723bs-vq0.map fw_bcm4330.bin fw_RK903b2_apsta.bin RT2870AP.dat wifi_efuse_8723cs.map fw_bcm43341b0_ag_apsta.bin fw_RK903b2.bin RT2870STACard.dat wifi_efuse_8723ds.map fw_bcm43341b0_ag.bin fw_RK903b2_p2p.bin RT2870STA.dat fw_bcm43341b0_ag_p2p.bin fw_RK903.bin rtl8723b_config I have not yet understood how the kernel determines device to contact at which address and what firmware to load into it and i'm asking for advice on what I should learn to make it work. 01_dtbdump_rockchip,rk3328-evb-avb.dts