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

[timschuerewegen]

Device: NEXBOX A95X (S905)

Image: Armbian_20.05.0-trunk_Arm-64_buster_current_5.5.1_20200227.img.xz

 

When I execute install-aml.sh and reboot, the device is bricked and booting from microSD card no longer works

 

I had to restore the original Android firmware with Amlogic's USB Burning Tool.

 

Any suggestions?

 

[noname]

16 hours ago, balbes150 said:

Test version of the image (20200314) for installation in eMMC on s905 chips with a 5.6 core . Please note that this is only a test version, which has a number of disadvantages. The amount of RAM available after installation will be 1 GB (including for systems launched from external media). After installation, you need to manually expand the ROOT_EMMC partition, after installation it will be approximately 8GB. There may be other bugs. I checked the installation mode on the Vega S95 Telos S905. My system starts normally from eMMC. To install it you need to run the script from the root user (install-aml-s905-emmc.sh).

I installed with "install-aml-s905-emmc.sh" and now get looping black screen. (Tronsmart Vega S95 Pro)

 

Spoiler

root@arm-64:~# ./install-aml-s905-emmc.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.0446988 s, 93.8 MB/s
Start install u-boot to eMMC
16384+0 records in
16384+0 records out
8388608 bytes (8.4 MB, 8.0 MiB) copied, 1.75093 s, 4.8 MB/s
Done
Start copy system for eMMC.
Formatting BOOT partition...mkfs.fat 4.1 (2017-01-24)
done.
Cppying BOOT...cp: error writing '/ddbr/install/zImage': No space left on device
done.
Edit init config...done.
Formatting ROOT partition...
e2fsck 1.44.1 (24-Mar-2018)
ROOT_EMMC: clean, 11/472352 files, 54326/1885864 blocks
done.
Copying ROOTFS.
Copy BIN
Create DEV
Copy ETC
Copy HOME
Copy LIB
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
*******************************************
root@arm-64:~#

 

Spoiler

 

GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
no sdio debug board detected
TE: 112909

BL2 Built : 12:06:06, Jun 13 2016.
gxb g176ecdb - laiyin.mo@droid12-sz

set vcck to 1100 mv
set vddee to 1000 mv
Board ID = 1
CPU clk: 1536MHz
DDR chl: Rank0+1 same @ 792MHz
DDR0: 1024MB(auto)-2T-11
DataBus test pass!
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c000, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010000, des: 0x01000000, size: 0x0000d460
Sending bl30......................................................OK.
Run bl30...
Load bl31 from eMMC, src: 0x00020000, des: 0x101[0000, size: 0x00013140
Image: gxb_v1.1.3134-b387442 2016-06-16 14:48:44 yun.cai@droid06]
OPS=0x12
7f a4 49 46 bd 50 bd 3f c3 35 ae 1f [0Load bl33 from eMMC, src: 0x00034000, des: 0x01000000, size: 0x0006af00
.199671 Inits done]
secure task start!
high task start!
low task start!
NOTICE:  BL3-1: v1.0(debug):c813a61
NOTICE:  BL3-1: Built : 14:47:05, Jun 16 2016
INFO:    BL3-1: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9

U-Boot 2015.01-00018-g6c5824b-dirty (Oct 12 2017 - 18:36:33)

DRAM:  1 GiB
Relocation Offset is: 36f3b000
register usb cfg[1][0] = 0000000037f96ac0
rYVkѕɁusb cfg[0][1] = 0000000037f96ae0
register usb cfg[2][0] = 0000000037f96b00
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: clk_level = 7
vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
MMC:   SDIO Port C: 0, SDIO Port B: 1
emmc/sd response timeout, cmd8, status=0x3ff2800
emmc/sd response timeout, cmd55, status=0x3ff2800
[mmc_startup] mmc refix success
[mmc_init] mmc init success
In:    serial
Out:   serial
Err:   serial
reboot_mode=cold_boot
hpd_state=0
cvbs performance type = 4, table = 0
Net:   Meson_Ethernet
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[CANVAS]addr=0x3d800000 width=5760, height=2160

Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
There is no valid bmp file at the given address
Hit Enter or space or Ctrl+C key to stop autoboot -- :  0
Device: SDIO Port C
Manufacturer ID: 15
OEM: 100
Name: 8WMB3
Tran Speed: 52000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 7.3 GiB
mmc clock: 40000000
Bus Width: 8-bit DDR
reading s905_autoscript
1654 bytes read in 4 ms (403.3 KiB/s)
## Executing script at 01020000
start amlogic old u-boot
## Error: "bootfromsd" not defined
reading boot_android
** Unable to read file boot_android **
** Bad device usb 0 **
reading u-boot.ext
** Unable to read file u-boot.ext **
** Bad device usb 0 **
reading uEnv.txt
359 bytes read in 3 ms (116.2 KiB/s)
## Error: "mac" not defined
## Error: "eth_mac" not defined
reading /zImage
4796416 bytes read in 79 ms (57.9 MiB/s)
reading /uInitrd
11068440 bytes read in 176 ms (60 MiB/s)
reading /dtb/amlogic/meson-gxbb-vega-s95-pro.dtb
25664 bytes read in 8 ms (3.1 MiB/s)
## Error: "aadmac" not defined
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    11068376 Bytes = 10.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
load dtb from 0x1000000 ......
## Flattened Device Tree blob at 01000000
   Booting using the fdt blob at 0x1000000
   Loading Ramdisk to 3349a000, end 33f283d8 ... OK
   Loading Device Tree to 000000001fff6000, end 000000001ffff43f ... OK

Starting kernel ...

uboot time: 1521864 us
"Synchronous Abort" handler, esr 0x02000000
ELR:     2600000
LR:      37f41690
x0 : 000000001fff6000 x1 : 0000000000000000
x2 : 0000000000000000 x3 : 0000000000000000
x4 : 0000000001080000 x5 : 00000000cc0d678a
x6 : 0000000000000000 x7 : 0000000000000000
x8 : 000000001fff62b8 x9 : 0000000000000002
x10: 000000000a200023 x11: 0000000000000002
x12: 0000000000000002 x13: 0000000033f2ae3e
x14: 0000000033f28b90 x15: 0000000037f3c0d0
x16: 0000000037f3c2b4 x17: 0000000000000000
x18: 0000000033f2ae28 x19: 0000000000000400
x20: 0000000000000400 x21: 0000000037fa66b8
x22: 0000000000000003 x23: 0000000033f45a78
x24: 0000000037f9b4b8 x25: 0000000000000000
x26: 0000000000000700 x27: 0000000037f41648
x28: 0000000000000000 x29: 0000000033f29b70

Resetting CPU ...

 

 

[balbes150]

2 hours ago, noname said:

Cppying BOOT...cp: error writing '/ddbr/install/zImage': No space left on device

Check which partitions were created on eMMC and what state they are in.

[balbes150]

An additional bug was detected when installing on S905 in eMMC. Starting Armbian from the SD card will stop working correctly. To work around it , you either need to start the system from USB, or rename the s905_autoscript file on eMMC (for the time of starting from the SD card).

[noname]

45 minutes ago, balbes150 said:

Check which partitions were created on eMMC and what state they are in.

I can't booting from USB or SD. I can't pause with uart.

How ckecking state partitions?

[balbes150]

20 minutes ago, noname said:

I can't booting from USB or SD. I can't pause with uart.

How ckecking state partitions?

I have u-boot normally stops on the "space" key (pressed the key , hold it, turn on the power, u-boot stopped and allows you to execute any commands in the UART console)

 

[noname]

1 hour ago, balbes150 said:

I have u-boot normally stops on the "space" key (pressed the key , hold it, turn on the power, u-boot stopped and allows you to execute any commands in the UART console)

 

I use putty, and now "space" don't working. With normal booting "space" worked.

 

2 hours ago, balbes150 said:

rename the s905_autoscript file on eMMC

What should be the new file name? I flashed to origin and run "install-aml-s905-emmc.sh" again. Before this i launched ddbr.

Spoiler

root@arm-64:/root# ./install-aml-s905-emmc.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.0594106 s, 70.6 MB/s
Start install u-boot to eMMC
16384+0 records in
16384+0 records out
8388608 bytes (8.4 MB, 8.0 MiB) copied, 1.60175 s, 5.2 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 Sun Mar 15 06:14:26 2020
e2fsck 1.44.1 (24-Mar-2018)
ROOT_EMMC: clean, 11/472352 files, 54326/1885864 blocks
done.
Copying ROOTFS.
Copy BIN
Create DEV
Copy ETC
Copy HOME
Copy LIB
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
*******************************************
root@arm-64:/root#

 

[balbes150]

16 minutes ago, noname said:

What should be the new file name? I flashed to origin and run "install-aml-s905-emmc.sh" again. Before this i launched ddbr.

To run with eMMC, the name must be s905_autoscript. If you need to run Armbian from an SD card, you start the system from eMMC and rename /boot/s905_autoscript on eMMC to any name. After starting from the SD card, do not forget to return the name on eMMC to s905_autoscript, otherwise there will be no system startup from eMMC.

[noname]

@balbes150 After the last attempt, everything worked out. Thanks. The system is now loaded from eMMC.

Maybe a stupid question, but why did the MAC change? Now this BADGER METER INC.

 

There is no place at all on the boot partition.

Spoiler

root@arm-64:~# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  linux-image-current-arm-64
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
17 not fully installed or removed.
Need to get 0 B/28.5 MB of archives.
After this operation, 1,024 B disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 32154 files and directories currently installed.)
Preparing to unpack .../linux-image-current-arm-64_20.05.0_arm64.deb ...
Unpacking linux-image-current-arm-64 (20.05.0) over (20.05.0) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-current-arm-64_20.05.0_arm64.deb (--unpack):
 cannot copy extracted data for './boot/System.map-5.6.0-rc4-arm-64' to '/boot/System.map-5.6.0-rc4-arm-64.dpkg-new': failed to write (No space left on device)
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
mv: cannot stat '/boot/vmlinuz-5.6.0-rc4-arm-64': No such file or directory
Errors were encountered while processing:
 /var/cache/apt/archives/linux-image-current-arm-64_20.05.0_arm64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@arm-64:~#

 

[balbes150]

39 minutes ago, noname said:

There is no place at all on the boot partition.

show

fdisk -l

[balbes150]

41 minutes ago, noname said:

Maybe a stupid question, but why did the MAC change? Now this BADGER METER INC.

console UART command

 

setenv mac yor_MAC

saveenv

[noname]

Spoiler

root@arm-64:~# fdisk -l /dev/mmcblk1
Disk /dev/mmcblk1: 7.3 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8509a0e7

Device         Boot  Start      End  Sectors  Size Id Type
/dev/mmcblk1p1       16384   147455   131072   64M 83 Linux
/dev/mmcblk1p2      147456 15234373 15086918  7.2G 83 Linux
root@arm-64:~#

 

Spoiler

root@arm-64:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            265M     0  265M   0% /dev
tmpfs            80M  6.8M   74M   9% /run
/dev/mmcblk1p2  7.1G  1.3G  5.8G  18% /
tmpfs           400M     0  400M   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           400M     0  400M   0% /sys/fs/cgroup
tmpfs           400M  8.0K  400M   1% /tmp
/dev/mmcblk1p1   64M   60M  4.9M  93% /boot
/dev/zram0       49M  2.6M   43M   6% /var/log
tmpfs            80M     0   80M   0% /run/user/1000
root@arm-64:~#

 

[balbes150]

50 minutes ago, noname said:

There is no place at all on the boot partition.

Launch from an external media GPARTED and resize it to fit your needs.

[balbes150]

File with the new u-boot for s905-eMMC, the size of the first partition increased to 500MB.

 

https://yadi.sk/d/NGrJwf3SXi1boA

[noname]

27 minutes ago, balbes150 said:

File with the new u-boot for s905-eMMC, the size of the first partition increased to 500MB.

 

https://yadi.sk/d/NGrJwf3SXi1boA

How to use it? After write to image Armbian_20.05.0_Arm-64_bionic_current_5.6.0-rc4_20200314 no booting from USB.

[balbes150]

12 minutes ago, noname said:

How to use it? After write to image Armbian_20.05.0_Arm-64_bionic_current_5.6.0-rc4_20200314 no booting from USB.

This file should be written to eMMC with the dd command .

Or replace this file with the one located in the /root/boot/u-boot-s905 directory and perform a new installation.

[noname]

1 minute ago, balbes150 said:

This file should be written to eMMC with the dd command .

And this will not affect the data that may be in the place that will now be occupied by the new uboot?

[balbes150]

16 minutes ago, noname said:

And this will not affect the data that may be in the place that will now be occupied by the new uboot?

u-boot has a fixed size, and the current MBR partition table will be replaced with it ( with the loss of all data).

[hexdump]

@balbes150 - how exactly is this working technically? isn't in theory the mbr part occupied by the bootloader as well on s905?

 

a lot of thanks in advance and best wishes - hexdump

[noname]

1 hour ago, balbes150 said:

Or replace this file with the one located in the /root/boot/u-boot-s905 directory and perform a new installation.

Everything worked out. Many thanks.

The system boots with eMMC.

/dev/mmcblk1p1  575M   94M  481M  17% /boot

 

[balbes150]

14 hours ago, hexdump said:

how exactly is this working technically? isn't in theory the mbr part occupied by the bootloader as well on s905?

Yes, the MBR, when placing a u-boot on eMMC, is in the u-boot zone , but there are ways around this.

[Zahari Zahariev]

got wifi working on magicsee n5 plus (Amlogic s905x3).

 

The wifi is  Realtek RTL8822BS. There no driver in kernel source.

 

procedure to build driver or use attached binary (for kernel: 5.6.0-rc4-arm-64 )

 

mkdir -p /opt/amlogic
cd /opt/amlogic
git clone https://github.com/150balbes/Amlogic_s905-kernel.git
git clone https://github.com/ChalesYu/rtl8822bs-aml.git

cd /lib/modules/5.6.0-rc4-arm-64/
ln -s /opt/amlogic/Amlogic_s905-kernel build
ln -s /opt/amlogic/Amlogic_s905-kernel source
 
cd /opt/amlogic/Amlogic_s905-kernel.git
zcat /proc/config.gz > .config
make prepare

    - edit file: /opt/amlogic/Amlogic_s905-kernel/include/generated/utsrelease.h (must be version of your current working kernel: uname -r)
            #define UTS_RELEASE "5.6.0-rc4-arm-64"
            
cd /opt/amlogic/rtl8822bs-aml
    - replace files for kernel version 5.6.x (attached in post).
        os_dep/linux/ioctl_cfg80211.c
        os_dep/linux/rtw_proc.c
        
make -j2
sudo make install
sudo modprobe 88x2bs
 

regards,

Zahari

 

ioctl_cfg80211.c rtw_proc.c 88x2bs.zip

[stut]

On 3/15/2020 at 3:31 PM, balbes150 said:

This file should be written to eMMC with the dd command .

Or replace this file with the one located in the /root/boot/u-boot-s905 directory and perform a new installation.

 

I replaced the u-boot file and ran the install script, installation went fine but it got stuck in a bootloop and it looks like its using the old u-boot install.

 

Spoiler

U-Boot 2015.01 (Dec 27 2018 - 15:58:07)

DRAM:  2 GiB
Relocation Offset is: 76eb2000
register usb cfg[0][1] = 0000000077f59d00
[CANVAS]canvas init
boot_device_flag : 1
Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc.
init bus_cycle=6, bus_timing=7, system=5.0ns
reset failed
get_chip_type and ret:fffffffe
get_chip_type and ret:fffffffe
chip detect failed and ret:fffffffe
nandphy_init failed and ret=0xfffffff1
MMC:   aml_priv->desc_buf = 0x0000000073eb26b0
aml_priv->desc_buf = 0x0000000073eb49d0
SDIO Port B: 0, SDIO Port C: 1
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
init_part() 278: PART_TYPE_DOS
[mmc_init] mmc init success
dtb magic 536f976b
      Amlogic multi-dtb tool
      Cannot find legal dtb!
start dts,buffer=0000000073eb7200,dt_addr=0000000073eb7200
check_valid_dts: FDT_ERR_BADMAGIC
get_partition_from_dts: -9
get_ptbl_from_dtb()-259: get partition table from dts faild
mmc_device_init()-1081: get partition table from dtb failed
get_ptbl_rsv()-483: magic faild MPT,    
mmc_device_init()-1108: dtb&rsv are not exist, no LPT source
_find_partition_by_name()-188: do not find match in table env
get partition info failed !!
Using default environment

In:    serial
Out:   serial
Err:   serial
reboot_mode=cold_boot
[store]To run cmd[emmc dtb_read 0x1000000 0x40000]
_verify_dtb_checksum()-917: calc 39da9716, store dd847a7a
dtb_read()-1034: cpy 1 is not valid
_verify_dtb_checksum()-917: calc 20c637da, store ce178d1f
dtb_read()-1034: cpy 0 is not valid
dtb_read()-1039: total valid 0
      Amlogic multi-dtb tool
      Cannot find legal dtb!
[store]Err:do_store_dtb_ops,L330:Fail in fdt check header
board_late_init(): [store dtb read $dtb_mem_addr] fail
load dtb to 1000000
[store]To run cmd[emmc dtb_read 1000000 0x40000]
_verify_dtb_checksum()-917: calc 39da9716, store dd847a7a
dtb_read()-1034: cpy 1 is not valid
_verify_dtb_checksum()-917: calc 20c637da, store ce178d1f
dtb_read()-1034: cpy 0 is not valid
dtb_read()-1039: total valid 0
      Amlogic multi-dtb tool
      Cannot find legal dtb!
[store]Err:do_store_dtb_ops,L330:Fail in fdt check header
board_late_init(): store dtb read 1000000 fail
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: clk_level = 7
vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
vpu: vpu_clk_gate_init_off
vpp: vpp_init
hpd_state=0
cvbs performance type = 6, table = 0
Net:   dwmac.c9410000[KM]Error:f[keymanage_dts_parse]L287:not a fdt at 0x0000000001000000

Start read misc partition datas!
_find_partition_by_name()-188: do not find match in table misc
Cannot find dev.
amlmmc cmd <NULL> failed 

store - STORE sub-system

Usage:
store store init flag
store read name addr off|partition size
    read 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store write name addr off|partition size
    write 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store rom_write add off size.
        write uboot to the boot device
store erase boot/data: 
        erase the area which is uboot or data 
store erase partition <partition_name>: 
        erase the area which partition in u-boot 
store erase dtb 
store erase key 
store disprotect key 
store rom_protect on/off 
store scrub off|partition size
        scrub the area from offset and size 
store dtb iread/read/write addr <size>
        read/write dtb, size is optional 
store key read/write addr <size>
        read/write key, size is optional 
store mbr addr
   update mbr/partition table by dtb

[burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store  read misc 0x73ea1470  0x0  0x440]
failed to store read misc.
info->attemp_times = 0
info->active_slot = 0
info->slot_info[0].bootable = 0
info->slot_info[0].online = 0
info->slot_info[1].bootable = 0
info->slot_info[1].online = 0
info->attemp_times = 0
boot-info is invalid. Resetting.
save boot-info 
info->attemp_times = 0
info->active_slot = 0
info->slot_info[0].bootable = 1
info->slot_info[0].online = 1
info->slot_info[1].bootable = 0
info->slot_info[1].online = 0
info->attemp_times = 0
_find_partition_by_name()-188: do not find match in table misc
Cannot find dev.
amlmmc cmd <NULL> failed 

store - STORE sub-system

Usage:
store store init flag
store read name addr off|partition size
    read 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store write name addr off|partition size
    write 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store rom_write add off size.
        write uboot to the boot device
store erase boot/data: 
        erase the area which is uboot or data 
store erase partition <partition_name>: 
        erase the area which partition in u-boot 
store erase dtb 
store erase key 
store disprotect key 
store rom_protect on/off 
store scrub off|partition size
        scrub the area from offset and size 
store dtb iread/read/write addr <size>
        read/write dtb, size is optional 
store key read/write addr <size>
        read/write key, size is optional 
store mbr addr
   update mbr/partition table by dtb

[burnup]Err:store_write_ops,L110:cmd [store  write misc 0x73ea1470  0x0  0x440] failed attemp_times = 0 
active slot = 0 
wipe_data=successful
wipe_cache=successful
upgrade_step=0
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[CANVAS]addr=0x3d800000 width=5760, height=2160
_find_partition_by_name()-188: do not find match in table logo
Cannot find dev.
amlmmc cmd <NULL> failed 

store - STORE sub-system

Usage:
store store init flag
store read name addr off|partition size
    read 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store write name addr off|partition size
    write 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store rom_write add off size.
        write uboot to the boot device
store erase boot/data: 
        erase the area which is uboot or data 
store erase partition <partition_name>: 
        erase the area which partition in u-boot 
store erase dtb 
store erase key 
store disprotect key 
store rom_protect on/off 
store scrub off|partition size
        scrub the area from offset and size 
store dtb iread/read/write addr <size>
        read/write dtb, size is optional 
store key read/write addr <size>
        read/write key, size is optional 
store mbr addr
   update mbr/partition table by dtb

[burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store  read logo 0x1080000  0x0  0x2000]
Err imgread(L446):Fail to read 0x2000B from part[logo] at offset 0
There is no valid bmp file at the given address
[KM]Error:f[keymanage_dts_parse]L287:not a fdt at 0x0000000001000000
gpio: pin GPIOAO_2 (gpio 102) value is 1
InUsbBurn
noSof
Hit Enter or space or Ctrl+C key to stop autoboot -- :  0 
_find_partition_by_name()-188: do not find match in table boot
Cannot find dev.
amlmmc cmd <NULL> failed 

store - STORE sub-system

Usage:
store store init flag
store read name addr off|partition size
    read 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store write name addr off|partition size
    write 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store rom_write add off size.
        write uboot to the boot device
store erase boot/data: 
        erase the area which is uboot or data 
store erase partition <partition_name>: 
        erase the area which partition in u-boot 
store erase dtb 
store erase key 
store disprotect key 
store rom_protect on/off 
store scrub off|partition size
        scrub the area from offset and size 
store dtb iread/read/write addr <size>
        read/write dtb, size is optional 
store key read/write addr <size>
        read/write key, size is optional 
store mbr addr
   update mbr/partition table by dtb

[burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store  read boot 0x1080000  0x0  0x100000]
Err imgread(L245):Fail to read 0x100000B from part[boot] at offset 0
InUsbBurn
noSof
card out
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
emmc/sd response timeout, cmd1, status=0x1ff2800
[MSG]mmcinfo failed!
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
emmc/sd response timeout, cmd1, status=0x1ff2800
(Re)start USB...
USB0:   USB3.0 XHCI init start
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
_find_partition_by_name()-188: do not find match in table recovery
Cannot find dev.
amlmmc cmd <NULL> failed 

store - STORE sub-system

Usage:
store store init flag
store read name addr off|partition size
    read 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store write name addr off|partition size
    write 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store rom_write add off size.
        write uboot to the boot device
store erase boot/data: 
        erase the area which is uboot or data 
store erase partition <partition_name>: 
        erase the area which partition in u-boot 
store erase dtb 
store erase key 
store disprotect key 
store rom_protect on/off 
store scrub off|partition size
        scrub the area from offset and size 
store dtb iread/read/write addr <size>
        read/write dtb, size is optional 
store key read/write addr <size>
        read/write key, size is optional 
store mbr addr
   update mbr/partition table by dtb

[burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store  read recovery 0x1080000  0x0  0x100000]
Err imgread(L245):Fail to read 0x100000B from part[recovery] at offset 0

 

Here's printenv, usb start, fatls and usb info from u-boot. I can't get it to boot from sd or usb anymore. Is it possible to sort this out without restoring the Android rom?

 

Spoiler

A95X#printenv
EnableSelinux=permissive
active_slot=_a
baudrate=115200
bcb_cmd=get_valid_slot;
boot_part=boot
bootargs=rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 androidboot.selinux=permissive logo=osd1,loaded,0x3d800000,576cvbs maxcpus=4 vout=576cvbs,enable hdmimode=1080p60hz cvbsmode=576cvbs hdmitx= cvbsdrv=0 androidboot.firstboot=0 jtag=apao androidboot.hardware=amlogic androidboot.slot_suffix=_a
bootcmd=run storeboot
bootdelay=1
cmdline_keys=if keyman init 0x1234; then if keyman read usid ${loadaddr} str; then setenv bootargs ${bootargs} androidboot.serialno=${usid};setenv serial ${usid};fi;if keyman read mac ${loadaddr} str; then setenv bootargs ${bootargs} mac=${mac} androidboot.mac=${mac};fi;if keyman read deviceid ${loadaddr} str; then setenv bootargs ${bootargs} androidboot.deviceid=${deviceid};fi;fi;
cvbs_drv=0
cvbsmode=576cvbs
display_bpp=24
display_color_bg=0
display_color_fg=0xffff
display_color_index=24
display_height=576
display_layer=osd1
display_width=720
dtb_mem_addr=0x1000000
ethact=dwmac.c9410000
ethaddr=aa:44:e4:d9:03:20
factory_reset_poweroff_protect=echo wipe_data=${wipe_data}; echo wipe_cache=${wipe_cache};if test ${wipe_data} = failed; then run init_display; run storeargs;if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi; if test ${wipe_cache} = failed; then run init_display; run storeargs;if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi; 
fb_addr=0x3d800000
fb_height=1080
fb_width=1920
fdt_high=0x20000000
firstboot=0
gatewayip=10.18.9.1
hdmimode=1080p60hz
hostname=arm_gxbb
init_display=osd open;osd clear;imgread pic logo bootup $loadaddr;bmp display $bootup_offset;bmp scale
initargs=rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 
ipaddr=10.18.9.97
jtag=apao
loadaddr=1080000
maxcpus=4
netmask=255.255.255.0
outputmode=576cvbs
preboot=run bcb_cmd; run factory_reset_poweroff_protect;run upgrade_check;run init_display;run storeargs;run upgrade_key;run switch_bootmode;
reboot_mode=normal
recovery_from_flash=setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if itest ${upgrade_step} == 3; then if ext4load mmc 1:2 ${dtb_mem_addr} /recovery/dtb.img; then echo cache dtb.img loaded; fi;if ext4load mmc 1:2 ${loadaddr} /recovery/recovery.img; then echo cache recovery.img loaded; wipeisb; bootm ${loadaddr}; fi;else fi;if imgread kernel ${recovery_part} ${loadaddr} ${recovery_offset}; then wipeisb; bootm ${loadaddr}; fi;
recovery_from_sdcard=setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if fatload mmc 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload mmc 0 ${loadaddr} recovery.img; then if fatload mmc 0 ${dtb_mem_addr} dtb.img; then echo sd dtb.img loaded; fi;wipeisb; bootm ${loadaddr};fi;
recovery_from_udisk=setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if fatload usb 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload usb 0 ${loadaddr} recovery.img; then if fatload usb 0 ${dtb_mem_addr} dtb.img; then echo udisk dtb.img loaded; fi;wipeisb; bootm ${loadaddr};fi;
recovery_offset=0
recovery_part=recovery
sdc_burning=sdc_burn ${sdcburncfg}
sdcburncfg=aml_sdc_burn.ini
serverip=10.18.9.113
stderr=serial
stdin=serial
stdout=serial
storeargs=setenv bootargs ${initargs} androidboot.selinux=${EnableSelinux} logo=${display_layer},loaded,${fb_addr},${outputmode} maxcpus=${maxcpus} vout=${outputmode},enable hdmimode=${hdmimode} cvbsmode=${cvbsmode} hdmitx=${cecconfig} cvbsdrv=${cvbs_drv} androidboot.firstboot=${firstboot} jtag=${jtag}; setenv bootargs ${bootargs} androidboot.hardware=amlogic;run cmdline_keys;setenv bootargs ${bootargs} androidboot.slot_suffix=${active_slot};
storeboot=if imgread kernel ${boot_part} ${loadaddr}; then bootm ${loadaddr}; fi;run update;
switch_bootmode=get_rebootmode;if test ${reboot_mode} = factory_reset; then run recovery_from_flash;else if test ${reboot_mode} = update; then run update;else if test ${reboot_mode} = cold_boot; then run try_auto_burn; else if test ${reboot_mode} = fastboot; then fastboot;fi;fi;fi;fi;
try_auto_burn=update 700 750;
update=run usb_burning; run sdc_burning; if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;
upgrade_check=echo upgrade_step=${upgrade_step}; if itest ${upgrade_step} == 3; then run init_display; run storeargs; run update;else fi;
upgrade_key=if gpio input GPIOAO_2; then echo detect upgrade key; sleep 3;if gpio input GPIOAO_2; then run update; fi;fi;
upgrade_step=0
usb_burning=update 1000
wipe_cache=successful
wipe_data=successful

Environment size: 5182/65532 bytes

 

A95X#usb start
(Re)start USB...
USB0:   USB3.0 XHCI init start
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... init_part() 278: PART_TYPE_DOS
1 Storage Device(s) found

 

A95X#usb info
1: Hub,  USB Revision 3.0
 - u-boot XHCI Host Controller 
 - Class: Hub
 - PacketSize: 9  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Mass Storage,  USB Revision 2.0
 - Generic USB Storage 000000000272
 - Class: (from Interface) Mass Storage
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x05e3  Product 0x0736 Version 2.114
   Configuration: 1
   - Interfaces: 1 Bus Powered 98mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 2
     - Class Mass Storage, Transp. SCSI, Bulk only
     - Endpoint 1 In Bulk MaxPacket 512
     - Endpoint 2 Out Bulk MaxPacket 512

 

A95X#fatls usb 0:1
            dtb/
     1282   uenv.txt 
  5780109   system.map-5.6.0-rc4-arm-64 
      709   aml_autoscript 
      637   aml_autoscript.cmd 
        0   aml_autoscript.zip 
     1536   armbian_first_run.txt.template 
     4882   boot-desktop.png 
      764   boot-emmc.cmd 
      764   boot-emmc.cmd.aw 
      571   boot-emmc.ini 
      836   boot-emmc.scr 
      836   boot-emmc.scr.aw 
    38518   boot.bmp 
      918   boot.cmd 
      918   boot.cmd.aw 
      589   boot.ini 
      990   boot.scr 
      990   boot.scr.aw 
   209589   config-5.6.0-rc4-arm-64 
      831   emmc_autoscript 
      759   emmc_autoscript.cmd 
 13838196   initrd.img-5.6.0-rc4-arm-64 
     1615   s905_autoscript 
     1543   s905_autoscript.cmd 
   709768   u-boot.sd 
   709768   u-boot.usb 
     4096   ._uenv.txt 
 13838260   uinitrd 
            .temporaryitems/
 27795968   vmlinuz-5.6.0-rc4-arm-64 
 27795968   zimage 

30 file(s), 2 dir(s)

 

Ended up restoring Android and used the normal 202003011 build, installing to internal went fine and booting from it too! 

[balbes150]

58 minutes ago, stut said:

Here's printenv, usb start, fatls and usb info from u-boot. I can't get it to boot from sd or usb anymore. Is it possible to sort this out without restoring the Android rom?

you can try activating the multi-upload manually. Execute these commands.

 

usb start

fatload usb 0 1020000 aml_autoscript

autoscr 1020000

[medmouncef]

On 3/17/2020 at 6:10 PM, Zahari Zahariev said:

got wifi working on magicsee n5 plus (Amlogic s905x3).

 

The wifi is  Realtek RTL8822BS. There no driver in kernel source.

 

procedure to build driver or use attached binary (for kernel: 5.6.0-rc4-arm-64 )

 

mkdir -p /opt/amlogic
cd /opt/amlogic
git clone https://github.com/150balbes/Amlogic_s905-kernel.git
git clone https://github.com/ChalesYu/rtl8822bs-aml.git

cd /lib/modules/5.6.0-rc4-arm-64/
ln -s /opt/amlogic/Amlogic_s905-kernel build
ln -s /opt/amlogic/Amlogic_s905-kernel source
 
cd /opt/amlogic/Amlogic_s905-kernel.git
zcat /proc/config.gz > .config
make prepare

    - edit file: /opt/amlogic/Amlogic_s905-kernel/include/generated/utsrelease.h (must be version of your current working kernel: uname -r)
            #define UTS_RELEASE "5.6.0-rc4-arm-64"
            
cd /opt/amlogic/rtl8822bs-aml
    - replace files for kernel version 5.6.x (attached in post).
        os_dep/linux/ioctl_cfg80211.c
        os_dep/linux/rtw_proc.c
        
make -j2
sudo make install
sudo modprobe 88x2bs
 

regards,

Zahari

 

ioctl_cfg80211.c 237.19 kB · 2 downloads rtw_proc.c 95.86 kB · 2 downloads 88x2bs.zip 1.22 MB · 3 downloads

Hello. I try to apply this method to H96 Max X3 (amlogicS905X3) but I stumble on 2 points: 

         * utsrelease.h = #define UTS_RELEASE "5.6.0-rc4+"

         * make -j2 >> File path error message

Please see the attached screenshots

[nasty007]

Hello, is there way to install or replace XFACE with MATE desktop?

Im using GT-Mini2 S905x3 device

[stut]

22 hours ago, nasty007 said:

Hello, is there way to install or replace XFACE with MATE desktop?

Im using GT-Mini2 S905x3 device

 

I don't know if you should be flashing tv boxes when you don't know Debian/Ubuntu package manager basics like apt search and apt install. Something like apt install mate-desktop-environment should install MATE like you want.

[balbes150]

The version of the image 20200323.

Resolved then issue of pulseadio conflict with the G12 audio device . Now you don 't need to delete PULSEAUDIO. To enable audio on g12, you only need to run the script (g12_sound.sh) or for GX\GXM models, run the script (gx_sound.sh).

[Beppe]

Hi All,

I've tried to install the latest unified images on my tv Box (MX10 4/64GB) which is a Rockchip 3328, following the instructions, but i couldn't manage to.
I installed it several times without any issue before images got unified, but since then i am having issues installing it.
Here's what i'm doing.

1 - Downloading Armbian_20.05.0_Arm-64_buster_current_5.6.0-rc4_desktop_20200323.img.xz
2 - Unpacking the zip
3 - Flashing the Image on the SD card (Using etcher, or similar tools)
4 - Edit the uEnv.txt file as per instructions (you can find my file in attach)

Next step of the instruction is to add the correct u-boot to the SD card, but i don't understand what actually this means.
I'm missing the actual instructions to add this u-boot file.
Here's what i've tried so far:
- Downloading the u-boot file from https://yadi.sk/d/lTbXkrmZN5Hf6g (but which one do i have to download? as of now i tried u-boot-rk3328-mvr9.img)
- Write it on the SD card using dd (i'm on Linux)
- Re-update the uEnv.txt file with correct info as it appears to be overwrited (see attached)

Now, i plugin the SD card into my Tv Box and power it on, but i only get a black screen (I don't know if it actually booted or not).
I just can't get it to work.
Can you please help me out? What am i missing? Are the above steps correct or not?

Regards & thanks,
Beppe

uEnv.txt

[balbes150]

27 minutes ago, Beppe said:

I've tried to install the latest unified images on my tv Box (MX10 4/64GB) which is a Rockchip 3328, following the instructions, but i couldn't manage to.

What system (firmware) is installed in eMMC ?