[Armbian for Amlogic S805 and S802/S812]

On 1/26/2021 at 12:45 PM, menelike said:

@SteeMan

 

Thanks for your response. I am not sure what you mean with "clean copy", but  Kernel 3.x runs perfectly fine on the device. I just wanted to upgrade debian from stretch to bullseye because of missing/outdated debian packages.

But I think that you're correct, there is no upgrade path. 😪

 

Luckily I had a H96 Pro H3 with a S905x which I managed to run the bullseye on.

 

Hi. Have you been able to get the wifi to work with 2.4 and 5 GHz on your H96 Pro in Bullseye?

[Single Armbian image for RK + AML + AW (aarch64 ARMv8)]

I posted the file with translation problems, so here is the correct translation:

The problem is almost completely solved. I analyzed and searched the forum for some posts from dbshape, balbes150 and gilberto (are you also a Brazilian?)
The steps were as follows:

 

1- I mounted the Android image and in the /etc folder I copied the /wifi and /bluetooth folders;

 

2- I checked in the kernel output that Armbian was looking for the files brcm/brcmfmac4334-sdio and brcm/BCM4334B0.hcd.

 

3- Inside the /wifi folder there is the file fw_bcm4334b1_ag.bin. I copied it to the /lib/firmware/brcm/folder, renaming it brcmfmac4334-sdio.bin. This file is also present in the Armbian itself in /lib/firmware/rkwifi/, but I preferred to use the original Android.
sudo cp -av fw_bcm4334b1_ag.bin /lib/firmware/brcm/brcmfmac4334-sdio.bin
'fw_bcm4334b1_ag.bin' -> '/lib/firmware/brcm/brcmfmac4334-sdio.bin'

 

4- Inside the /bluetooth folder there is the file bcm4334.hcd. I copied it to the /lib/firmware/brcm/ folder, renaming it BCM4334B0.hcd.
sudo cp -av bcm4334.hcd /lib/firmware/brcm/BCM4334B0.hcd
'bcm4334.hcd' -> '/lib/firmware/brcm/BCM4334B0.hcd'

 

5- Then I rebooted. After the reboot, bluetooth working but wifi not.
In the kernel output:
brcmfmac mmc2: 0001: 1: Direct firmware load for brcm/brcmfmac4334-sdio.amlogic,p212.txt failed with error -2
brcmfmac mmc2: 0001: 1: Direct firmware load for brcm/brcmfmac4334-sdio.txt failed with error -2

 

6- Inside the Android /wifi folder is the nvram.txt file. I copied this file to /lib/firmware/brcm/ renaming it to brcmfmac4334-sdio.amlogic,p212.txt.
sudo cp -av nvram.txt /lib/firmware/brcm/brcmfmac4334-sdio.amlogic,p212.txt
'nvram.txt' -> '/lib/firmware/brcm/brcmfmac4334-sdio.amlogic,p212.txt'

 

7- Then I restarted again. After reboot, wifi working but only 2.4 Ghz. 5 Ghz not yet.
In the kernel output it has:
brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available

I looked over this file, but for the 4334 driver it doesn't exist.

 

There are other files in the /wifi folder, but I still don't know how important they are. I leave the link for her below and I wait if anyone has a suggestion to give from now on:
https://bit.ly/3hgFrfx

 

--------------------------------------------------

I read some posts from @usual user and @dbsharpe and researched other things, so here are the results:

 

@gilberto, I created my own Android builds, for my board using linux-amlogic-toolkit-master. It has a Windows version, but it had a bug when I tried to use it. With this tool, I mount the Android image and edit it easily.

 

To edit the .dtb files I installed dtc with the command:
sudo apt install device-tree-compiler

 

To convert .dtb to .dts:
dtc -I dtb -O dts -f meson-gxl-s905x-p212.dtb -o meson-gxl-s905x-p212.dts

 

But I was confused because I only found this reference to wifi in the Armbian dts file:

wifi32k {
        compatible = "pwm-clock";
        #clock-cells = <0x0>;
        clock-frequency = <0x8000>;
        pwms = <0x38 0x0 0x7736 0x0>;
        phandle = <0x13>;

 

On Android I managed to extract the .dtb files from the system image. I used the linux-amlogic-toolkit-master tool to extract the _aml_dtb.PARTITION file. I renamed the file to dtb.img and used the tool https://github.com/PabloCastellano/extract-dtb to extract the .dtb files. I extracted two files: 01_dtbdump_Amlogic.dtb and 02_dtbdump_Amlogic.dtb. Then I converted the two files to dts using dtc. Now I have two .dts that are huge. The first file is for the version with 1 GB of RAM and the second is for the version of 2 GB, mine. I also extracted the file directly from Android running, using the command dd if = /dev/dtb > /storage/downloads/droid.dtb and after converting to dts I realized that the files are identical. When I have time I will analyze that file because has more than 2000 lines of code. I tried to use the dtb file extracted directly from Android on Armbian, but of course, it didn't work.

 

I leave attached the two dts files, from Android and Armbian:

02_dtbdump_Amlogic-dts.txt

meson-gxl-s905x-p212-dts.txt

 

Thanks to @balbes150: Armbian's usability is better than Android for my uses. I will install Home Assistant in my box and use it as a server or use it in my classes. Thankful.

[Single Armbian image for RK + AML + AW (aarch64 ARMv8)]

20 hours ago, gilberto said:

the solution is further down this forum, I am Gilberto and staff helped me solve this problem .....

The problem is almost completely solved. I analyzed and searched the forum for some posts from dbshape, balbes150 and gilberto (are you also a Brazilian?)
The steps were as follows:

1- I mounted the Android image and in the /etc folder I copied the /wifi and /bluetooth folders;

 

2- I checked in the kernel output that Armbian was looking for the files brcm/brcmfmac4334-sdio and brcm/BCM4334B0.hcd.

 

3- Inside the /wifi folder there is the file fw_bcm4334b1_ag.bin. I copied it to the /lib/firmware/brcm/folder, renaming it brcmfmac4334-sdio.bin. This file is also present in the Armbian itself in /lib/firmware/rkwifi/, but I preferred to use the original Android.
sudo cp -av fw_bcm4334b1_ag.bin /lib/firmware/brcm/brcmfmac4334-sdio.bin
'fw_bcm4334b1_ag.bin' -> '/lib/firmware/brcm/brcmfmac4334-sdio.bin'

 

4- Inside the /bluetooth folder there is the file bcm4334.hcd. I copied it to the /lib/firmware/brcm/ folder, renaming it BCM4334B0.hcd.
sudo cp -av bcm4334.hcd /lib/firmware/brcm/BCM4334B0.hcd
'bcm4334.hcd' -> '/lib/firmware/brcm/BCM4334B0.hcd'

 

5- Então fiz o reboot. Após o reboot, bluetooth funcionando mas wifi não. Na saída do kernel:
brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.amlogic,p212.txt failed with error -2
brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.txt failed with error -2

 

6- Dentro da pasta /wifi do Android está o arquivo nvram.txt. Copiei este arquivo para /lib/firmware/brcm/ renomeando como brcmfmac4334-sdio.amlogic,p212.txt.
sudo cp -av nvram.txt /lib/firmware/brcm/brcmfmac4334-sdio.amlogic,p212.txt
'nvram.txt' -> '/lib/firmware/brcm/brcmfmac4334-sdio.amlogic,p212.txt'

 

5- Then I rebooted. After the reboot, bluetooth working but wifi not.
In the kernel output:
brcmfmac mmc2: 0001: 1: Direct firmware load for brcm/brcmfmac4334-sdio.amlogic,p212.txt failed with error -2
brcmfmac mmc2: 0001: 1: Direct firmware load for brcm/brcmfmac4334-sdio.txt failed with error -2

 

6- Inside the Android /wifi folder is the nvram.txt file. I copied this file to /lib/firmware/brcm/ renaming it to brcmfmac4334-sdio.amlogic,p212.txt.
sudo cp -av nvram.txt /lib/firmware/brcm/brcmfmac4334-sdio.amlogic,p212.txt
'nvram.txt' -> '/lib/firmware/brcm/brcmfmac4334-sdio.amlogic,p212.txt'

 

7- Então reiniciei mais uma vez. Após o reboot, wifi funcionando mas somente 2.4 Ghz. 5 Ghz ainda não. Na saída do kernel tem:
brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
I looked over this file, but for the 4334 driver it doesn't exist.

 

There are other files in the /wifi folder, but I still don't know how important they are. I leave the link for her below and I wait if anyone has a suggestion to give from now on:
https://bit.ly/3hgFrfx

[Single Armbian image for RK + AML + AW (aarch64 ARMv8)]

Well, using Armbian_20.02.0-rc1.037_Aml-s9xxx_bionic_current_5.5.0-rc6_desktop_20200205, on my H96 Pro H3, the wifi is not working. I took the output of dmesg on Android, it has this:

[  113.499310] dhd_os_open_image: /etc/wifi/40183/config.txt (102 bytes) open success
...
[  113.574510] Final fw_path=/etc/wifi/40183/fw_bcm4334b1_ag.bin
[  113.580529] Final nv_path=/etc/wifi/40183/nvram.txt
[  113.585309] Final clm_path=/etc/wifi/40183/clm_bcmdhd.blob
[  113.592102] Final conf_path=/etc/wifi/40183/config.txt
...
[  113.607107] dhd_os_open_image: /etc/wifi/40183/fw_bcm4334b1_ag.bin (451566 bytes) open success
[  113.739233] dhd_os_open_image: /etc/wifi/40183/nvram.txt (2019 bytes) open success
[  113.814711] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.

In Armbian dmesg, the important part of the output is this:

[    8.902412] brcmfmac: F1 signature read @0x18000000=0x16034334
[    8.908532] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3
[    8.909037] usbcore: registered new interface driver brcmfmac
[    8.916140] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.bin failed with error -2
[    9.027835] Bluetooth: hci0: BCM: chip id 68
[    9.028441] Bluetooth: hci0: BCM: features 0x0f
[    9.030268] Bluetooth: hci0: BCM4334B0
[    9.030287] Bluetooth: hci0: BCM4334B0 (002.001.013) build 0000
[    9.030417] bluetooth hci0: Direct firmware load for brcm/BCM4334B0.hcd failed with error -2
[    9.030429] Bluetooth: hci0: BCM: Patch brcm/BCM4334B0.hcd not found

 

Someone knows what is error -2? Does anyone know how to solve?

Here are the complete dmesg outputs:
https://bit.ly/3hgFrfx

[Single Armbian image for RK + AML + AW (aarch64 ARMv8)]

6 hours ago, jeanrhum said:

The procedure has changed and the first post of this topic has been updated.

Yes, thanks, I was blind for that. Now, Armbian is running, but my Wi-Fi chip is marked as HS2734A and not working. I have a H96 Pro H3. There's a way to compile driver for that?

[Single Armbian image for RK + AML + AW (aarch64 ARMv8)]

Hi. After a while without using Raspbian on my H96 Pro H3 (S905x), I am wanting to install Raspbian to also install Home Assistant. But when trying to boot I am not getting it. Is the process still as in the videos, copying a .dtb file and renaming it to dtb.img? Or has the procedure changed? I tested it by renaming all meson-gxl-s905x * but it didn't work.