March 14Mar 14 Hello everyone, I have two identical-looking "arm-64" Amlogic TV boxes (S805X-based, meson-gxl-s805x-p241.dtb), both running the same Armbian image (kernel 5.9.0-arm-64 from balbes150 build). Both boxes have BCM43430 WiFi+BT combo (AP6212 module) on SDIO (mmc1). Problem: - STB 1: WiFi works perfectly (BCM43430/1 stepping) - STB 2: WiFi fails to initialize (BCM43430/2 stepping) — always ends with "HT Avail timeout (1000000): clkctl 0x50" Key dmesg from STB 1 (working): [ 7.719726] brcmfmac: F1 signature read @0x18000000=0x1541a9a6 [ 7.736079] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 7.976301] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2021 01:12:21 version 7.45.98.118 (7d96287 CY) FWID 01-32059766 → wlan0 appears and connects normally Key dmesg from STB 2 (not working): [ 7.564287] brcmfmac: F1 signature read @0x18000000=0x1542a9a6 [ 7.568240] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/2 [ 8.644057] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 [ 9.652082] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 → No wlan0 interface created What I already tried on STB 2: 1. Copied entire /lib/firmware/brcm folder from STB 1 → same timeout 2. Symlinked brcmfmac43430a0-sdio.bin / .txt → same timeout 3. Symlinked Raspberry Pi 3 variant (brcmfmac43430-sdio.raspberrypi,3-model-b.txt) → same 4. Created symlink for board-specific file: ln -sf brcmfmac43430-sdio.txt brcmfmac43430-sdio.amlogic,p241.txt → still fails 5. Added various NVRAM tweaks (boardflags3=0x48200100, LPO=1, sd_drivestrength=6, etc.) → no change 6. Tried sdio_overclock=0 (and 25000000) → module says "unknown parameter 'sdio_overclock' ignored" (not supported in this kernel 5.9 build) Current /lib/firmware/brcm contents (relevant files): - brcmfmac43430-sdio.bin - brcmfmac43430-sdio.txt - brcmfmac43430a0-sdio.bin - brcmfmac43430a0-sdio.txt - brcmfmac43430-sdio.raspberrypi,3-model-b.txt - brcmfmac43430-sdio.amlogic,p241.txt (now exists) modinfo brcmfmac shows no sdio_overclock or drive_strength parameter available. Questions: - Has anyone seen BCM43430/2 stepping specifically fail like this while /1 works on the same image? - Is there a known good NVRAM .txt for BCM43430/2 on Amlogic boxes? - Any other module parameters or DTB tweaks that could slow down SDIO clock or force LPO mode? - Or is this most likely a hardware difference (LPO crystal issue on the module/board)? Any help or pointers greatly appreciated — really want to avoid buying USB dongles if possible. Thanks! ls /lib/firmware/brcm bcm4329.hcd BCM4330B1.hcd bcm4330.hcd BCM43342.hcd BCM4334B0.hcd BCM43430A1.hcd BCM43430B0.hcd bcm43438-sdio.hcd BCM4343A0.hcd BCM4345C0_003.001.025.0162.0000_Generic_UART_37_4MHz_wlbga_ref_iLNA_iTR_eLG.hcd BCM4345C0.amlogic,sm1.hcd BCM4345C0.firefly,rk3566-roc-pc.hcd BCM4345C0.radxa,zero2.hcd BCM4345C0.raspberrypi,4-compute-module.hcd BCM4345C5.hcd BCM4356A2.hcd BCM4359C0.hcd BCM4362A2.hcd BCM4362A2-khadas-vim4.hcd brcmfmac4329-sdio.bin brcmfmac4329-sdio.txt brcmfmac4330-sdio.amlogic,q200-n1.txt brcmfmac4330-sdio.bin brcmfmac4330-sdio.rockchip,rk3318-box.txt brcmfmac4330-sdio.txt brcmfmac43342-sdio.bin brcmfmac43342-sdio.txt brcmfmac4334-sdio.bin brcmfmac4334-sdio.rockchip,rk3318-box.txt brcmfmac43362-sdio.bin brcmfmac43362-sdio.txt brcmfmac4339-sdio.1CK.txt brcmfmac4339-sdio.bin brcmfmac4339-sdio.txt brcmfmac4339-sdio.ZP.txt brcmfmac43430a0-sdio.bin brcmfmac43430a0-sdio.txt brcmfmac43430b0-sdio.bin brcmfmac43430b0-sdio.rockchip,fine3399.bin brcmfmac43430b0-sdio.txt brcmfmac43430-sdio.bin brcmfmac43430-sdio.clm_blob brcmfmac43430-sdio.raspberrypi,3-model-b.bin brcmfmac43430-sdio.raspberrypi,3-model-b.txt brcmfmac43430-sdio.raspberrypi,model-zero-2-w.bin brcmfmac43430-sdio.raspberrypi,model-zero-2-w.txt brcmfmac43430-sdio.txt brcmfmac43436s-sdio.bin brcmfmac43436s-sdio.raspberrypi,model-zero-2-w.bin brcmfmac43436s-sdio.raspberrypi,model-zero-2-w.txt brcmfmac43455-sdio.amlogic,sm1.bin brcmfmac43455-sdio.amlogic,sm1.txt brcmfmac43455-sdio.bin brcmfmac43455-sdio.clm_blob brcmfmac43455-sdio.firefly,rk3566-roc-pc.bin brcmfmac43455-sdio.firefly,rk3566-roc-pc.txt brcmfmac43455-sdio.radxa,zero2.bin brcmfmac43455-sdio.radxa,zero2.txt brcmfmac43455-sdio.raspberrypi,3-model-b-plus.bin brcmfmac43455-sdio.raspberrypi,4-compute-module.bin brcmfmac43455-sdio.raspberrypi,4-compute-module.txt brcmfmac43455-sdio.raspberrypi,4-model-b.bin brcmfmac43455-sdio.raspberrypi,4-model-b.txt brcmfmac43455-sdio.raspberrypi,5-model-b.bin brcmfmac43455-sdio.raspberrypi,5-model-b.clm_blob brcmfmac43455-sdio.raspberrypi,5-model-b.txt brcmfmac43455-sdio.txt brcmfmac43456-sdio.bin brcmfmac43456-sdio.clm_blob brcmfmac43456-sdio.radxa,rockpi4b.bin brcmfmac43456-sdio.radxa,rockpi4b.txt brcmfmac43456-sdio.radxa,zero2.bin brcmfmac43456-sdio.radxa,zero2.txt brcmfmac43456-sdio.radxa,zero.bin brcmfmac43456-sdio.radxa,zero.txt brcmfmac43456-sdio.raspberrypi,400.bin brcmfmac43456-sdio.raspberrypi,400.txt brcmfmac43456-sdio.txt brcmfmac4356-sdio.bin brcmfmac4356-sdio.clm_blob brcmfmac4356-sdio-nanopi-m4v2.bin brcmfmac4356-sdio-nanopi-m4v2.txt brcmfmac4356-sdio.txt brcmfmac4359-sdio.bin brcmfmac4359-sdio.txt brcmfmac43752-pcie.bin brcmfmac43752-pcie.clm_blob brcmfmac43752-pcie.txt brcmfmac43752-sdio.9tripod,x3568-v4.bin brcmfmac43752-sdio.9tripod,x3568-v4.txt brcmfmac43752-sdio.bin brcmfmac43752-sdio.clm_blob brcmfmac43752-sdio.firefly,rk3568-roc-pc.bin brcmfmac43752-sdio.firefly,rk3568-roc-pc.txt brcmfmac43752-sdio.txt brcmfmac-ap6330-sdio.bin brcmfmac-ap6330-sdio.txt clm_bcm43752a2_ag.blob config_bcm43456c5_ag.txt config_bcm43752a2_ag.txt config.txt fw_bcm43456c5_ag_apsta.bin fw_bcm43456c5_ag.bin fw_bcm43752a2_ag_apsta.bin fw_bcm43752a2_ag.bin fw_bcm43752a2_ag_p2p.bin nvram_ap6256.txt nvram_ap6275s.txt SYN43711A0.hcd
March 14Mar 14 You aren't using Armbian. The balbes150 builds were a fork of Armbian and know one here would know what sources they were built with. So this question is really off topic for Armbian.
March 14Mar 14 23 minutes ago, Bug Hunter said: Hello everyone, I have two identical-looking "arm-64" Amlogic TV boxes (S805X-based, meson-gxl-s805x-p241.dtb), In the world of TV boxes "identical looking" means nothing, as manufacturers build each batch with the lowest cost components available at the time. There are many cases where identical looking boxes even contain different cpus ( ie amlogic vs rockchip). My recommendation would be first to verify the markings on the boards (there is usually some sort of board identifying text on the board)to really see if they are the same under the hood.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.