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

[Ouistyty]

Hello.

 

I used your great work already on a tvbox of a friend and I decided to order one to play with.

I just received "Int boX Smart TV i7" whit a s912 and trying to do the same.
but it's blocking at the moment it update the password.
I've tried multiple amlogic image without any success.

/dtb/amlogic/meson-gxm-q200.dtb

/dtb/amlogic/meson-gxm-q201.dtb

...

I've also tried multiple SD card

I've tried USB stick too , but there I blocking with a pink background 

 

I also tried with an older build found without the autologon script and is was blocking at the same place, when it was time to update the root password, but whit this old version the error message appear : "authentication token manipulation error"

 

I was wondering if you could have any clue on the cause of this issue.

 

Thanks

 

/Ouistyty

[Ouistyty]

Please ignore my message,
Looking at multiple topic on this kind of issue, it seems related to SD.
I'll wait to get a new SD and retry before coming back again for help.
Regards

 

/Ouistyty

[Madasafish]

Has anyone tested on Tanix TX6s box? If not, do you believe the Tanix TX6 dtb files will work on Tanix TX6s?

[DevShanky]

1 hour ago, Madasafish said:

Has anyone tested on Tanix TX6s box? If not, do you believe the Tanix TX6 dtb files will work on Tanix TX6s?

 

I think Tanix TX6s has Allwinner H616 which is a different processor.  It will most likely not work. Tanix TX6 has H6.

 

You may also want to check this out

-R

 

[winit_a]

Tonix TX3 Mini   WIFI don't work

how to config

Armbian_20.07_Arm-64_focal_current_5.7.9.img.xz

 

 

 

info Tonix 3 mini

used firmware TX3Mini-20181210.img can boot armbian

if used TX3Mini-S905W-20191008.img firmware boot into android recovery only can't boot armbian

[Madasafish]

25 minutes ago, Rajesh said:

I think Tanix TX6s has Allwinner H616 which is a different processor.  It will most likely not work. Tanix TX6 has H6.

Thank-you Rajesh,

 

I am aware the Tanix TX6s (H616) is a different processor to the Tanix TX6 (H6) but they both use the same sun50i.  https://linux-sunxi.org/Allwinner_SoC_Family

or am I barking up the wrong tree here?

 

Madasafish.

[dbsharpe]

30 minutes ago, winit_a said:

Tonix TX3 Mini   WIFI don't work

how to config

Armbian_20.07_Arm-64_focal_current_5.7.9.img.xz

 

info Tonix 3 mini

used firmware TX3Mini-20181210.img can boot armbian

if used TX3Mini-S905W-20191008.img firmware boot into android recovery only can't boot armbian

 

I've had one of these boxes but didn't run Armbian on it. The one I had was p281 and the copy of Android dmesg I have seems to indicate a TLL901X chip. I sold it as wifi support seemed lacking on libreelec.
The Android system backup I have has many wifi chips to choose from in /system/lib/libhardware_legacy.so (according to /usr/bin/strings).
You could start by looking at this post if your lucky and it is actually a broadcom chip.

Also, you need to look in dmesg or /var/log/syslog for "firmware" regarding any load messages.

[DevShanky]

53 minutes ago, dbsharpe said:

 

I've had one of these boxes but didn't run Armbian on it. The one I had was p281 and the copy of Android dmesg I have seems to indicate a TLL901X chip. I sold it as wifi support seemed lacking on libreelec.
The Android system backup I have has many wifi chips to choose from in /system/lib/libhardware_legacy.so (according to /usr/bin/strings).
You could start by looking at this post if your lucky and it is actually a broadcom chip.

Also, you need to look in dmesg or /var/log/syslog for "firmware" regarding any load messages.

 

Tanix TX3 mini uses SSV6501 for wifi. The vendor I believe does not exist now and no one supports the driver for mainline kernel. It is too much work and very flaky and unstable I believe. Use external USB wifi and you should be good. Or use legacy kernel if it helps.

 

-R

 

[winit_a]

dmesg -w

Jul 28 02:36:10 localhost kernel: [    9.188333] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4
Jul 28 02:36:10 localhost kernel: [    9.188464] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
Jul 28 02:36:10 localhost kernel: [    9.192378] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4330/4 wl0: Oct 25 2011 19:34:12 version 5.90.125.104

 

try

mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.old
ln -s  /lib/firmware/brcm/nvram_ap6330.txt  /lib/firmware/brcm/brcmfmac4330-sdio.txt

 

it work  

thank you.

[usman]

I have installed Armbian_20.02.0-rc1.037_Aml-s9xxx_bionic_current_5.5.0-rc6_20200205.img on Minix Neo UI with SD card.

Can anyone please explain how to install to emmc. I see people referring to install_emmc.sh but I dont have anything by this name in the root folder.

[DevShanky]

17 hours ago, winit_a said:

dmesg -w

Jul 28 02:36:10 localhost kernel: [    9.188333] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4
Jul 28 02:36:10 localhost kernel: [    9.188464] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
Jul 28 02:36:10 localhost kernel: [    9.192378] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4330/4 wl0: Oct 25 2011 19:34:12 version 5.90.125.104

 

try

mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.old
ln -s  /lib/firmware/brcm/nvram_ap6330.txt  /lib/firmware/brcm/brcmfmac4330-sdio.txt

 

it work  

thank you.

 

Did you mean to say you got the onboard wifi working on the device?

 

-R

[winit_a]

18 hours ago, Rajesh said:

 

Did you mean to say you got the onboard wifi working on the device?

 

-R

Yes .

TX3 Mini onboard wifi (Cz1830) working

 

[DevShanky]

4 hours ago, winit_a said:

Yes .

TX3 Mini onboard wifi (Cz1830) working

 

 

You are lucky to have that working. I have a TX3 mini with ssv6501 and could never make it work.

 

I also have a QBox (S905X) having exact same situation as you see with BCM4330. The dmsg messages are exactly same.

 

I tried this but it does not work for me.

mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.old
ln -s  /lib/firmware/brcm/nvram_ap6330.txt  /lib/firmware/brcm/brcmfmac4330-sdio.txt

 

The config.txt has these content:

PM=0
nv_by_chip=1 \
43362 1 nvram_ap6210.txt
43430 0 nvram_ap6212.txt

 

So I tried linking nvram_ap6210.txt and nvram_ap6212.txt but it doesn't help.

 

Guess there is more to it than I can perceive.

 

-R

 

[dbsharpe]

1 hour ago, Rajesh said:

 

You are lucky to have that working. I have a TX3 mini with ssv6501 and could never make it work.

 

I also have a QBox (S905X) having exact same situation as you see with BCM4330. The dmsg messages are exactly same.

 

I tried this but it does not work for me.

mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.old
ln -s  /lib/firmware/brcm/nvram_ap6330.txt  /lib/firmware/brcm/brcmfmac4330-sdio.txt

 

The config.txt has these content:

PM=0
nv_by_chip=1 \
43362 1 nvram_ap6210.txt
43430 0 nvram_ap6212.txt

 

So I tried linking nvram_ap6210.txt and nvram_ap6212.txt but it doesn't help.

 

Guess there is more to it than I can perceive.

 

-R

 

On your qbox, which is probably p212, you might find this post of use:

I don't think /lib/firmware/brcm/config.txt is used in linux currently.

 

[DevShanky]

4 hours ago, dbsharpe said:

On your qbox, which is probably p212, you might find this post of use:

I don't think /lib/firmware/brcm/config.txt is used in linux currently.

 

Thank you. I will try this out. 

-R

[Gaurav]

HI Friends 

 

I am having problem loading through USB .  I have got  A95X Max Android TV box which has Cortex A53 .  I select "aml_autoscript.zip" from Update Utility . System reboots and then shows error

"unable to mount udisk: no file or directory

Failed to open /udisk/aml_autoscript.zip"

 

PLease if you somebody can guide me to fix this issue.  Linux on Android TV Box looks promising but its my first experience probably I am not doing something correctly. ANy help will be greatly apppreciated. 

 

Thanks

Gaurav 

[dbsharpe]

43 minutes ago, Gaurav said:

"unable to mount udisk: no file or directory

Failed to open /udisk/aml_autoscript.zip"

 

 

Personally, I encourage my tv box to boot into Armbian by issuing the command 'reboot update' in a shell terminal under android or power up with the toothpick method (poke the button inside the A/V port).
After that, make sure your flash sticks /uEnvv.txt is correct with a just the irelevant lines commented out apart from the ones used.
You may have to read page 1 of this thread again regarding u-boot after checking uEnv.txt about 10 times.

[Gaurav]

17 hours ago, dbsharpe said:

Personally, I encourage my tv box to boot into Armbian by issuing the command 'reboot update' in a shell terminal under android or power up with the toothpick method (poke the button inside the A/V port).
After that, make sure your flash sticks /uEnvv.txt is correct with a just the irelevant lines commented out apart from the ones used.
You may have to read page 1 of this thread again regarding u-boot after checking uEnv.txt about 10 times.

You are right I think I am not putting the u-boot correctly.  Can you please help me with the steps ..... do I have to write u-bootXXX.img on separate card and the linux image separate one ? I am using Etcher to write and it seems I can't write two img together on same card ..it overwrites the current image. 

[SteeMan]

1 hour ago, Gaurav said:

You are right I think I am not putting the u-boot correctly.  Can you please help me with the steps ..... do I have to write u-bootXXX.img on separate card and the linux image separate one ? I am using Etcher to write and it seems I can't write two img together on same card ..it overwrites the current image. 

If you have an A95X Max box as you say in a previous post, then you should have an Amlogic s905x2 cpu.   For that CPU per the instructions you should not be needing to do anything with uboot.  Just write the image to the sd card, edit the uEnv.txt file and boot from the sd card (toothpick method should work).  

[lesgar]

On 21/7/2020 at 10:42, balbes150 said:

ver 20200721-dev kernel 5.8-rc6

@balbes150 I try your image an not work ethernet and wifi. New sun50i-h6-tanix-tx6.dtb is smaller 19,2 KiB (19.705) than sun50i-h6-tanix-tx6.dtb on allwinner 20.07 image 20,1 KiB (20.588). In allwinner 20.07 work fine, but in 20200721-dev  not work. Can you explain me how to fix, tanks.

[Mickynuts]

Hi sorry for that question.
I am running the last image on mega with TX6-P (H6) with 16go Emmc.
i want to copy the sd card to emmc. I am using ddbr for backup. but the speed is 0.0 byte.
if i just want to install with the script "install-aw-sh" in the root directory. The result is the same. With Iostat or Nmon, the activity is zero.
after 2 hours the file created with install-aw.sh is of size 0 (no error) but i kill process.
Can someone help me ? have you encountered the same problem? I run with the 5.7.7-aw-h6-tv kernel
uname -r see: Linux aw-h6-tv 5.7.7-aw-h6-tv # 20.07 SMP PREEMPT Thu Jul 9 09:38:18 MSK 2020 aarch64 aarch64 aarch64 GNU / Linux
see picture and i have past the dmesg in dmesg.txt

other image work on emmc ? 

dmesg.txt

[Lucas]

Hello,

 

I am running last image on sunvell t95v pro (S912) with 16gb emmc and 2gb ram. I currently boot from USB flash drive but I want to install to emmc.

I used /root/install-aml.sh:

root@arm-64:~# ./install-aml.sh
Start script create MBR and filesystem
/dev/mmcblk1
Start backup u-boot default
4+0 records in
4+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.166257 s, 25.2 MB/s
Start create MBR and partittion
Start restore u-boot
442+0 records in
442+0 records out
442 bytes copied, 0.00383592 s, 115 kB/s
8191+0 records in
8191+0 records out
4193792 bytes (4.2 MB, 4.0 MiB) copied, 0.371816 s, 11.3 MB/s
Done
Start copy system for eMMC.
Formatting BOOT partition...mkfs.fat 4.1 (2017-01-24)
done.
Cppying BOOT...done.
Edit init config...done.
Formatting ROOT partition...
/dev/mmcblk1p2 contains a ext4 file system labelled 'ROOT_EMMC'
        last mounted on /ddbr/install on Mon Aug  3 16:35:58 2020
e2fsck 1.44.1 (24-Mar-2018)
ROOT_EMMC: clean, 11/881280 files, 81956/3520768 blocks
done.
Copying ROOTFS.
Copy BIN
Create DEV
Copy ETC
Copy HOME
Copy LIB
Copy LIB64
Create MEDIA
Create MNT
Copy OPT
Create PROC
Copy ROOT
Create RUN
Copy SBIN
Copy SELINUX
Copy SRV
Create SYS
Create TMP
Copy USR
Copy VAR
Copy fstab
*******************************************
Complete copy OS to eMMC
*******************************************

The script output looks good, but when I now boot without usb flash drive it stucks at the armlogic s912 boot logo. Booting from USB flash drive is still working.

Any idea what goes wrong?

[Falldaemon]

14 hours ago, Lucas said:

Merhaba,

 

16 gb emmc ve 2 gb ram ile sunvell t95v pro (S912) üzerinde son görüntüyü çalıştırıyorum. Şu anda USB flash sürücüden önyükleme yapıyorum ama emmc'ye kurmak istiyorum.

/Root/install-aml.sh kullandım:

Komut dosyası çıkışı iyi görünüyor, ancak şimdi usb flash sürücü olmadan önyükleme yaptığımda armlogic s912 önyükleme logosuna yapışıyor. USB flash sürücüden önyükleme hala çalışıyor.

Neyin yanlış gittiğine dair bir fikrin var mı?

Sudo mount /dev/mmcblk1p1 /mnt denermisin

[dbsharpe]

I don't have much experience of booting and running from internal flash but the usual forum response to such failure is that you have NAND and not EMMC in your tv box.
Assuming /dev/mmcblk1p1 and /dev/mmcblk1p2 file systems are good, you could work around by booting off sdcard but mount /dev/mmcblk1p2 as your root file system. Check internal flash /etc/fstab is OK and modify /uEnv.txt on the sdcard to point to flash /dev/mmcblk1p2 (APPEND=root=LABEL=ROOT_EMMC).

 

[DevShanky]

On 7/30/2020 at 8:43 PM, Rajesh said:

Thank you. I will try this out. 

-R

 

@dbsharpe  I loaded Android for the box (it is QBox S905X) and reviewed dmesg.  The wifi is working on the box.

 

It appears that the firmware file used is fw_bcm40183b2.bin and nvram_ap6330.txt. I am not able to locate fw_bcm40183b2.bin on the Armbian image. Incidentally bluetooth is working.

 

Where should I look for right firmware?

 

This is from armbianmonitor log:

 

[    9.537004] brcmfmac: F1 signature read @0x18000000=0x16044330
[    9.542185] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4
[    9.542369] usbcore: registered new interface driver brcmfmac
[    9.563478] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.amlogic,p212.txt failed with error -2
[    9.741509] random: crng init done
[    9.741518] random: 7 urandom warning(s) missed due to ratelimiting
[    9.808242] Bluetooth: hci0: BCM: chip id 62
[    9.808822] Bluetooth: hci0: BCM: features 0x0f
[    9.810584] Bluetooth: hci0: BCM4330B1
[    9.810601] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0000
[    9.887357] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4
[    9.887528] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[    9.891344] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4330/4 wl0: Oct 25 2011 19:34:12 version XXX.XXX.125.104
[   10.163224] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 184
[   10.163232] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 188
[   10.163236] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 192
[   10.163240] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 196
[   10.163244] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 200
[   10.163248] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 204
[   10.163252] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 208
[   10.163256] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 212
[   10.163260] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 216
[   10.615857] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0000
[   10.616562] Bluetooth: hci0: BCM: Using default device address (43:30:b1:00:00:00)

 

http://ix.io/2toh

 

-R

 

 

[DevShanky]

1 hour ago, Rajesh said:

 

@dbsharpe  I loaded Android for the box (it is QBox S905X) and reviewed dmesg.  The wifi is working on the box.

 

It appears that the firmware file used is fw_bcm40183b2.bin and nvram_ap6330.txt. I am not able to locate fw_bcm40183b2.bin on the Armbian image. Incidentally bluetooth is working.

 

Where should I look for right firmware?

 

This is from armbianmonitor log:

 

[    9.537004] brcmfmac: F1 signature read @0x18000000=0x16044330
[    9.542185] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4
[    9.542369] usbcore: registered new interface driver brcmfmac
[    9.563478] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.amlogic,p212.txt failed with error -2
[    9.741509] random: crng init done
[    9.741518] random: 7 urandom warning(s) missed due to ratelimiting
[    9.808242] Bluetooth: hci0: BCM: chip id 62
[    9.808822] Bluetooth: hci0: BCM: features 0x0f
[    9.810584] Bluetooth: hci0: BCM4330B1
[    9.810601] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0000
[    9.887357] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4
[    9.887528] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[    9.891344] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4330/4 wl0: Oct 25 2011 19:34:12 version XXX.XXX.125.104
[   10.163224] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 184
[   10.163232] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 188
[   10.163236] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 192
[   10.163240] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 196
[   10.163244] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 200
[   10.163248] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 204
[   10.163252] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 208
[   10.163256] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 212
[   10.163260] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 216
[   10.615857] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0000
[   10.616562] Bluetooth: hci0: BCM: Using default device address (43:30:b1:00:00:00)

 

http://ix.io/2toh

 

-R

 

 

 

 Please ignore above messages. I have finally got it working. The interface was listed but it was down. I did sudo ifconfig wlan0 up and it is working now. Thank you for all the suggestions and help!

 

-R

[gpread]

Hi,

 

I am trying to install Armbian_20.07_Arm-64_buster_current_5.7.9.img onto the emmc (internal storage) of my TVBOX.  Its a T95N S905X device with 1g RAM and 8g emmc. 

 

I followed the process at the start of this thread and I can get it running fine off of the micro sd card, using either/both of the meson-gxl-s905x-p212.dtb or meson-gxl-s905x-nexbox-a95x.dtb and I have successfully used the Amlogic USB burning tool to install and run stock firmware images for MXQPro, T95N, T95X and A95X-nexbox.

 

I have tried without success once running ambian from the external microsd to install it to the intermal emmc using the /root/install-aml.sh or /root/install-aml-S905.sh.  I have tried to debug why it does not work and it appears to come down to how the storage is seen by the kernel/OS.  fdisk -l shows the emmc in the form of /dev/mmcblkX with /dev/mmcblkXp1 and /dev/mmcblkXp1 but the devices tree has them as /dev/mmcblkXboot0 and /dev/mmcblkXboot1. The X varies according to which dtb I use, its either 0 or 1.

 

I tried renaming the /dev/xxxxxboot0 and 1 entries to match what fdisk and the script wants but it does not resolve the issue.

 

Any pointers or solutions will be gratefully received, thanks

[Vasy]

Hi all,

I am trying to deploy Armbian_20.07_Arm-64_focal_current_5.7.9_desktop on a Mini M8S (S905, 2GB RAM, 8 GB Flash, Realtek 8723BS wifi). Everything works fine except the RAM that always gets detected as 800 Mbytes no matter what.  From what I read here, this is an u-boot issue and tried different ones (the original one, the one from Armbian_5.44_S9xxx_Ubuntu_bionic_3.14.29_mate_20180729.img that seemed to detect all memory). Still no luck.  I have no UART interface Please tell me, is there an available uboot version for the latest armbian releases that can detect the memory fine? Many thanks.

[dbsharpe]

7 hours ago, gpread said:

Any pointers or solutions will be gratefully received, thanks

My suggestion for potential solution is my post.

[dbsharpe]

5 hours ago, Vasy said:

from Armbian_5.44_S9xxx_Ubuntu_bionic_3.14.29_mate_20180729.img that seemed to detect all memory). Still no luck.  I have no UART interface Please tell me, is there an available uboot version for the latest armbian releases that can detect the memory fine? Many thanks.

In the absence of a u-boot file, this is how I was able to work round it but you still need to boot from sdcard but run root from flash.
You will need to restore an operable android image with USB Burning Tool or restore full backup of internal flash.

On my p201 S905X device, I was able to format all (most) of the internal flash apart from the first 108Mb (arbitrary value)
which excludes the bootloader  (something like mke2fs -F  -t ext4 -m 0  -L ROOT_EMMC  -E offset=113246208  /dev/mmcblk1 [ -< device for internal flash]  )
                                                 
You can get your flash layout from dmesg after booting into android. You will also need to know how to unpack & pack  uInitrd. Your custom boot uInitrd will get overwritten if you install or upgrade certain debian packages.
I no longer have the RAM issue and was able to make some use of those fake microsd cards I've collected over
the years.