CM211-1 使用6.1内核，DTB使用m302a成功写入EMMC，网络正常

Question

CM211-1 使用6.1内核，DTB使用m302a成功写入EMMC，网络正常

Ivanriver opened this issue a year ago · comments

Ivanriver commented a year ago

Standard chat template, no routine, no chat.
标准聊天模板，无套路不聊天。

Device Information | 设备信息

SOC: S905L3
Model CM211-1 2+8 无蓝牙无WIFI版本，主板标识：MC016

**Armbian Version | Armbian_23.05.0

Kernel Version: [6.1.25]
Release: Armbian_23.05.0_amlogic_s905l3_jammy_6.1.25_server_2023.04.22

Describe the bug | 问题描述

5.15版本内核版本不做修改可以正常写入EMMC并启动，但是U盘/emmc启动均无网络。
6.1版本内核使用默认dtb可以启动，写入emmc提示成功，但是系统无法启动。
uEnv.txt中dtb改为meson-gxl-s905l3b-m302a.dtb，armbian写入emmc成功启动，网口正常。
写入时选项选择0，
DTB名字填写meson-gxl-s905l3b-m302a.dtb，
UBOOT_OVERLOAD填写：u-boot-p212.bin
MAINLINE_UBOOT和BOOTLOADER_IMG 留空，直接回车安装，磁盘格式选择EXT4

121   s905l3     UNT400G1                       meson-gxl-s905l2-x7-5g.dtb      
122   s905l2     E900v21E                       meson-gxl-s905l2-x7-5g.dtb      
123   s905l3b    IP103H                         meson-gxl-s905l3b-m302a.dtb     
0     Other      Customize                      Enter-custom-dtb-name           

[ OPTIONS ] Please Input ID: 0
Please Input SoC Name(such as s9xxx): s905l3
Please Input DTB Name(such as meson-xxx.dtb): meson-gxl-s905l3b-m302a.dtb
Please Input UBOOT_OVERLOAD Name(such as u-boot-xxx.bin): u-boot-p212.bin
Please Input MAINLINE_UBOOT Name(such as xxx-u-boot.bin.sd.bin):
Please Input BOOTLOADER_IMG Name(such as xxx-bootloader.img):

硬件图片

ophub · Answer 1 · Sun Apr 23 2023 15:50:26 GMT+0800 (China Standard Time)

你下载s905l3b的固件，选择112或者123安装，结果和你上面的相同
你试试s906l3b的6.1内核的固件，选择123安装： https://github.com/ophub/amlogic-s9xxx-armbian/releases/download/Armbian_jammy_04.22.0609/Armbian_23.05.0_amlogic_s905l3b_jammy_6.1.25_server_2023.04.22.img.gz

Ivanriver · Answer 2 · Sun Apr 23 2023 16:25:53 GMT+0800 (China Standard Time)

你下载s905l3b的固件，选择112或者123安装，结果和你上面的相同你试试s906l3b的6.1内核的固件，选择123安装： https://github.com/ophub/amlogic-s9xxx-armbian/releases/download/Armbian_jammy_04.22.0609/Armbian_23.05.0_amlogic_s905l3b_jammy_6.1.25_server_2023.04.22.img.gz

使用s905l3b固件无法启动，TTL卡在这里

rebootmode=cold_boot
Starting the controller
 ()
start amlogic old u-boot
 ()
[BL31]: tee size: 0
[BL31]: tee size: 0

ophub · Answer 3 · Sun Apr 23 2023 17:15:34 GMT+0800 (China Standard Time)

十分感谢你的分享，根据你的测试结果，添加了 s905l3-cm211 的独立选项，序号 124： 15613ef

你下载测试下
https://github.com/ophub/amlogic-s9xxx-armbian/releases/tag/Armbian_jammy_04.23.0515

Ivanriver · Answer 4 · Sun Apr 23 2023 18:14:09 GMT+0800 (China Standard Time)

十分感谢你的分享，根据你的测试结果，添加了 s905l3-cm211 的独立选项，序号 124： 15613ef

你下载测试下 https://github.com/ophub/amlogic-s9xxx-armbian/releases/tag/Armbian_jammy_04.23.0515

非常感谢你的适配！
序号124测试结果：
5.15版本启动网口不可用。
6.1.25内核版本可以直接写入，启动正常，网络正常。但是在断电后有很小几率无法启动，TTL日志如下。
之前在使用其他dtb文件写入EMMC后无法启动也是报这个错误。不过目前日常使用应该问题不大。

U-Boot 2021.04-00056-g13ac02db31-dirty (Apr 28 2021 - 22:52:02 +0800) p212

Model: Amlogic Meson GXL (S905X) P212 Development Board
SoC:   Amlogic Meson Unknown (Unknown) Revision 2a:e (c5:2)
DRAM:  2 GiB
MMC:   mmc@70000: 0, mmc@72000: 1, mmc@74000: 2
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
[BL31]: tee size: 0
[BL31]: tee size: 0
Net:   eth0: ethernet@c9410000
Hit any key to stop autoboot:  0
starting USB...
Bus usb@c9000000: dwc3_meson_gxl_get_phys: usb2 ports: 2
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus usb@c9000000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc2(part 0) is current device
Scanning mmc 2:1...
Found U-Boot script /boot.scr
1025 bytes read in 1 ms (1001 KiB/s)
## Executing script at 08000000
Start AMLOGIC mainline U-boot
## Error: "bootfromsd" not defined
373 bytes read in 3 ms (121.1 KiB/s)
## Error: "mac" not defined
## Error: "eth_mac" not defined
ethaddr=fa:3b:e6:fa:f4:b9
33321472 bytes read in 737 ms (43.1 MiB/s)
Error reading cluster
** Unable to read file /uInitrd **
Failed to load '/uInitrd'
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
SCRIPT FAILED: continuing...
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Card did not respond to voltage select! : -110
Scanning disk mmc@70000.blk...
Disk mmc@70000.blk not ready
Card did not respond to voltage select! : -110
Scanning disk mmc@72000.blk...
Disk mmc@72000.blk not ready
Scanning disk mmc@74000.blk...
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
** Can't read partition table on 2:0 **
Found 1 disks
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
Card did not respond to voltage select! : -110
Speed: 100, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 252
*** Unhandled DHCP Option in OFFER/ACK: 252
DHCP client bound to address 192.168.11.17 (6 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-fa-3b-e6-fa-f4-b9
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A80B11
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A80B1
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A80B
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A80
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A8
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-meson-p212
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-meson
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
Speed: 100, full duplex
*** ERROR: `serverip' not set
Config file not found
Speed: 100, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 252
*** Unhandled DHCP Option in OFFER/ACK: 252
DHCP client bound to address 192.168.11.17 (6 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
Speed: 100, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 252
*** Unhandled DHCP Option in OFFER/ACK: 252
DHCP client bound to address 192.168.11.17 (6 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET

ophub · Answer 5 · Sun Apr 23 2023 20:06:53 GMT+0800 (China Standard Time)

你这样测试下，USB启动后先不要写入emmc，先把extlinux.conf启用了，重启下看看能正常启动，再armbian-install写入

# 1. 第一次u盘启动后，先启用extlinux
cd /boot/extlinux
mv -f extlinux.conf.bak extlinux.conf
sync
reboot

# 2. 重启后，如果网卡正常工作，再写入
armbian-install

Ivanriver · Answer 6 · Sun Apr 23 2023 21:17:18 GMT+0800 (China Standard Time)

你这样测试下，USB启动后先不要写入emmc，先把extlinux.conf启用了，重启下看看能正常启动，再armbian-install写入
# 1. 第一次u盘启动后，先启用extlinux
cd /boot/extlinux
mv -f extlinux.conf.bak extlinux.conf
sync
reboot

# 2. 重启后，如果网卡正常工作，再写入
armbian-install

启用extlinux后可以启动，网口正常，依然有一定概率无法启动

U-Boot 2021.04-00056-g13ac02db31-dirty (Apr 28 2021 - 22:52:02 +0800) p212

Model: Amlogic Meson GXL (S905X) P212 Development Board
SoC:   Amlogic Meson Unknown (Unknown) Revision 2a:e (c5:2)
DRAM:  2 GiB
MMC:   mmc@70000: 0, mmc@72000: 1, mmc@74000: 2
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
[BL31]: tee size: 0
[BL31]: tee size: 0
Net:   eth0: ethernet@c9410000
Hit any key to stop autoboot:  0
starting USB...
Bus usb@c9000000: dwc3_meson_gxl_get_phys: usb2 ports: 2
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus usb@c9000000 for devices... 1 USB Device(s) found
      scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc2(part 0) is current device
Scanning mmc 2:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
400 bytes read in 1 ms (390.6 KiB/s)
1:      Armbian
Retrieving file: /uInitrd
17992815 bytes read in 399 ms (43 MiB/s)
Retrieving file: /zImage
Error reading cluster
** Unable to read file /zImage **
Failed to load '/zImage'
Skipping Armbian for failure retrieving kernel
SCRIPT FAILED: continuing...
** No partition table - mmc 2 **
** No partition table - mmc 2 **
** No partition table - mmc 2 **
** No partition table - mmc 2 **
** No partition table - mmc 2 **
** No partition table - mmc 2 **
** No partition table - mmc 2 **
** No partition table - mmc 2 **
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Card did not respond to voltage select! : -110
Scanning disk mmc@70000.blk...
Disk mmc@70000.blk not ready
Card did not respond to voltage select! : -110
Scanning disk mmc@72000.blk...
Disk mmc@72000.blk not ready
Scanning disk mmc@74000.blk...
** fs_devread read error - block
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Found 1 disks
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
** No partition table - mmc 2 **
Speed: 100, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 252
*** Unhandled DHCP Option in OFFER/ACK: 252
DHCP client bound to address 192.168.11.17 (6 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
missing environment variable: pxeuuid
Retrieving file: /extlinux/pxelinux.cfg/01-fa-3b-e6-fa-f4-b9
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: /extlinux/pxelinux.cfg/C0A80B11
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: /extlinux/pxelinux.cfg/C0A80B1
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: /extlinux/pxelinux.cfg/C0A80B
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: /extlinux/pxelinux.cfg/C0A80
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: /extlinux/pxelinux.cfg/C0A8
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: /extlinux/pxelinux.cfg/C0A
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: /extlinux/pxelinux.cfg/C0
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: /extlinux/pxelinux.cfg/C
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: /extlinux/pxelinux.cfg/default-arm-meson-p212
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: /extlinux/pxelinux.cfg/default-arm-meson
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: /extlinux/pxelinux.cfg/default-arm
Speed: 100, full duplex
*** ERROR: `serverip' not set
Retrieving file: /extlinux/pxelinux.cfg/default
Speed: 100, full duplex
*** ERROR: `serverip' not set
Config file not found
Speed: 100, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 252
*** Unhandled DHCP Option in OFFER/ACK: 252
DHCP client bound to address 192.168.11.17 (6 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
Speed: 100, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 252
*** Unhandled DHCP Option in OFFER/ACK: 252
DHCP client bound to address 192.168.11.17 (6 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
=> Error reading cluster
Unknown command 'Error' - try 'help'
=>

ophub · Answer 7 · Sun Apr 23 2023 21:33:38 GMT+0800 (China Standard Time)

你5.15不能启动是缺少u-boot引导，6.1和5.15只有这个u-boot的差别。

在你启用/extlinux/extlinux.conf后错误日志和之前有区别。

# 之前的错误日志
** Unable to read file /uInitrd **
Failed to load '/uInitrd'

# 后来的错误日志
Retrieving file: /zImage
Error reading cluster
** Unable to read file /zImage **
Failed to load '/zImage'

难道是写入了不安全的emmc分区？你看看文档，还原成安卓系统，确认下正确的分区。看12.10
https://github.com/ophub/amlogic-s9xxx-armbian/blob/main/build-armbian/documents/README.cn.md

Ivanriver · Answer 8 · Sun Apr 23 2023 23:05:12 GMT+0800 (China Standard Time)

你5.15不能启动是缺少u-boot引导，6.1和5.15只有这个u-boot的差别。

在你启用/extlinux/extlinux.conf后错误日志和之前有区别。
# 之前的错误日志
** Unable to read file /uInitrd **
Failed to load '/uInitrd'

# 后来的错误日志
Retrieving file: /zImage
Error reading cluster
** Unable to read file /zImage **
Failed to load '/zImage'
难道是写入了不安全的emmc分区？你看看文档，还原成安卓系统，确认下正确的分区。看12.10 https://github.com/ophub/amlogic-s9xxx-armbian/blob/main/build-armbian/documents/README.cn.md

这个是安卓系统的分区结构
https://7ji.github.io/ampart-web-reporter/?dsnapshot=logo::33554432:1%20recovery::33554432:1%20rsv::8388608:1%20tee::8388608:1%20crypt::33554432:1%20misc::33554432:1%20instaboot::536870912:1%20boot::33554432:1%20system::1073741824:1%20cache::536870912:2%20params::67108864:2%20ctc::314572800:2%20bootfiles::536870912:2%20data::-1:4&esnapshot=bootloader:0:4194304:0%20reserved:37748736:67108864:0%20cache:113246208:536870912:2%20env:658505728:8388608:0%20logo:675282944:33554432:1%20recovery:717225984:33554432:1%20rsv:759169024:8388608:1%20tee:775946240:8388608:1%20crypt:792723456:33554432:1%20misc:834666496:33554432:1%20instaboot:876609536:536870912:1%20boot:1421869056:33554432:1%20system:1463812096:1073741824:1%20params:2545942528:67108864:2%20bootfiles:2621440000:536870912:2%20swdb:3166699520:16777216:2%20data:3191865344:4282384384:4

根据文档描述，BLANK1大小设定100M，BOOT设定为8+512+8，共528M，BOOT后不可使用分区大小为1M，应该是设定为以下内容

# Set partition size (Unit: MiB)
elif [[ "${AMLOGIC_SOC}" == "s905l3" ]]; then
    BLANK1="100"
    BOOT="528"
    BLANK2="1"

但是armbian-install使用上述参数安装后依旧有一定几率无法启动。后来将boot分区设定为520M，尝试多次均能正常启动。根据文档描述应该是有1M的不可用空间，目前不确定后期使用是否会有影响。

# Set partition size (Unit: MiB)
elif [[ "${AMLOGIC_SOC}" == "s905l3" ]]; then
    BLANK1="100"
    BOOT="520"
    BLANK2="1"

找了下CM211-1的相关资料，发现有多个代工版本，目前没有其他设备测试。参考Issues里的同型号产品，感觉不具有通用性，此贴可以作为后续刷机参考。非常感谢您的帮助！

gametta · Answer 9 · Mon Apr 24 2023 07:18:49 GMT+0800 (China Standard Time)

随机不启动的原因貌似以前有人说过，要用btrfs格式，ext4有这个问题，你可以实验一下。

Ivanriver · Answer 10 · Mon Apr 24 2023 08:33:18 GMT+0800 (China Standard Time)

随机不启动的原因貌似以前有人说过，要用btrfs格式，ext4有这个问题，你可以实验一下。

测试了btrfs格式，第二次重启就出现无法启动了

ophub · Answer 11 · Mon Apr 24 2023 08:41:13 GMT+0800 (China Standard Time)

放弃间隙8M，少用点，多跳点。
用下面的设置试试。先还原安卓系统，再写入才有效。

# Set partition size (Unit: MiB)
elif [[ "${AMLOGIC_SOC}" == "s905l3" ]]; then
    BLANK1="108"
    BOOT="512"
    BLANK2="64"

ophub · Answer 12 · Mon Apr 24 2023 08:45:57 GMT+0800 (China Standard Time)

把你刷机用的安卓系统分享一个下载链接，我转存一份。这是带root的吧？安卓版本是9.0？

Ivanriver · Answer 13 · Mon Apr 24 2023 09:27:29 GMT+0800 (China Standard Time)

Set partition size (Unit: MiB)

elif [[ "${AMLOGIC_SOC}" == "s905l3" ]]; then
BLANK1="108"
BOOT="512"
BLANK2="64"

昨天设定的BLANK2="1"，执行apt upgrade之后无法启动。
今天修改了分区参数，跳过了那1M的不可用空间，目前使用的分区如下，暂时没有发现异常。

# Set partition size (Unit: MiB)
elif [[ "${AMLOGIC_SOC}" == "s905l3" ]]; then
    BLANK1="100"
    BOOT="520"
    BLANK2="10"

Ivanriver · Answer 14 · Mon Apr 24 2023 09:32:20 GMT+0800 (China Standard Time)

把你刷机用的安卓系统分享一个下载链接，我转存一份。这是带root的吧？安卓版本是9.0？

这个安卓系统是4.4版本的，不带root。找到的安卓9的固件开机都不能进入桌面，TTL无法中断。
链接: https://pan.baidu.com/s/1ocsaFuv2ql1V5018Gx4ruA?pwd=6yua
提取码: 6yua

ophub · Answer 15 · Mon Apr 24 2023 09:46:20 GMT+0800 (China Standard Time)

不带root，能开启adb，支持usb启动？

安卓估计我转存到这里了： https://github.com/ophub/kernel/releases/tag/tools

Ivanriver · Answer 16 · Mon Apr 24 2023 10:51:28 GMT+0800 (China Standard Time)

不带root，能开启adb，支持usb启动？

安卓估计我转存到这里了： https://github.com/ophub/kernel/releases/tag/tools

由于刷机需要拆机，我就直接通过TTL调整了，TTL使用reboot update命令重启会从U盘启动。

shitlime · Answer 17 · Mon Jul 24 2023 13:33:07 GMT+0800 (China Standard Time)

按照这个issue操作，写入emmc后，拔掉U盘重启：

GXLX2:BL1:3cfee7:42a5ae;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;
TE: 81558

BL2 Built : 13:36:55, Jun 22 2020.
gxl g85d6ad1 - longyong.chen@droid02-sz

Board ID = 4, adc=302
set vcck to 1070 mv
set vddee to 1070 mv
CARD_3 high, old board
CPU clk: 1200MHz

DDR3 chl: Rank0+1 @ 792MHz - FAIL
DDR3 chl: Rank0 @ 792MHz
bist_test rank: 0 29 08 4a 37 14 5a 21 00 42 3e 1c 61 23 03 44 38 15 5b 28 05 4b 38 14 5c 618   - PASS

Rank0: 2048MB(auto)-2T-11
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x013c0000, size: 0x00007600
Load bl301 from eMMC, src: 0x00018200, des: 0x01380000, size: 0x00002400
Load bl31 from eMMC, src: 0x0001c200, des: 0x10100000, size: 0x00019600
Load bl33 from eMMC, src: 0x00038200, des: 0x01000000, size: 0x0007b000
NOTICE:  BL3-1: v1.0(debug):361f8a7
NOTICE:  BL3-1: Built : 16:43:26, Dec 19 2018
NOTICE:  BL31: GXL normal boot!
NOTICE:  BL31: BL33 decompress pass
[Image: gxl_v1.1.3103-9234004 2018-12-27 10:43:23 yao.zhang@droid07]
efuse init ops = c5
efuse init hdcp = c, cf9=7
x2_hp_e = 0
bl30: check_permit, count is 1
bl30: check_permit: ok!
chipid: 0 0 3 c c 0 70 b3 98 a0 0 c5 not ES chip
[0.645310 Inits done]
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 (Mar 29 2021 - 17:09:00)

DRAM:  2 GiB
Relocation Offset is: 76e8c000
this uboot is for hw_1_8, set GPIODV_24gpio: pin GPIODV_24 (gpio 43) value is 1
gpio: pin GPIOZ_14 (gpio 73) value is 1
register usb cfg[0][1] = 0000000077f5bc10
[CANVAS]canvas init
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: clk_level = 7
vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
vpp: vpp_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 = 0x0000000073e7cc00
aml_priv->desc_buf = 0x0000000073e7ef20
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 5f4c4d41
      Amlogic multi-dtb tool
      Multi dtb detected
      unified board, board id = 4
      Multi dtb tool version: v2 .
      Support 6 dtbs.
        aml_dt soc: gxlx2 platform: p291 variant: 2g
        dtb 0 soc: gxl   plat: p211   vari: 1g
        dtb 1 soc: gxl   plat: p211   vari: 2g
        dtb 2 soc: gxlx   plat: p261   vari: 1g
        dtb 3 soc: gxlx   plat: p261   vari: 2g
        dtb 4 soc: gxlx2   plat: p291   vari: 1g
        dtb 5 soc: gxlx2   plat: p291   vari: 2g
      Find match dtb: 5
start dts,buffer=0000000073e81750,dt_addr=0000000073eb1750
      Amlogic multi-dtb tool
      Multi dtb detected
      unified board, board id = 4
      Multi dtb tool version: v2 .
      Support 6 dtbs.
        aml_dt soc: gxlx2 platform: p291 variant: 2g
        dtb 0 soc: gxl   plat: p211   vari: 1g
        dtb 1 soc: gxl   plat: p211   vari: 2g
        dtb 2 soc: gxlx   plat: p261   vari: 1g
        dtb 3 soc: gxlx   plat: p261   vari: 2g
        dtb 4 soc: gxlx2   plat: p291   vari: 1g
        dtb 5 soc: gxlx2   plat: p291   vari: 2g
      Find match dtb: 5
parts: 1
00:      data   ffffffffffffffff 4
init_part() 278: PART_TYPE_DOS
eMMC/TSD partition table have been checked OK!
check pattern success
mmc env offset: 0x7400000
In:    serial
Out:   serial
Err:   serial
board id is : 4
hpd_state=0
cvbs performance type = 7, table = 1
[store]To run cmd[emmc dtb_read 0x1000000 0x40000]
_verify_dtb_checksum()-924: calc 5e24f54e, store 5e24f54e
_verify_dtb_checksum()-924: calc 5e24f54e, store 5e24f54e
dtb_read()-1046: total valid 2
dtb_read()-1113: do nothing
      Amlogic multi-dtb tool
      Multi dtb detected
      unified board, board id = 4
      Multi dtb tool version: v2 .
      Support 6 dtbs.
        aml_dt soc: gxlx2 platform: p291 variant: 2g
        dtb 0 soc: gxl   plat: p211   vari: 1g
        dtb 1 soc: gxl   plat: p211   vari: 2g
        dtb 2 soc: gxlx   plat: p261   vari: 1g
        dtb 3 soc: gxlx   plat: p261   vari: 2g
        dtb 4 soc: gxlx2   plat: p291   vari: 1g
        dtb 5 soc: gxlx2   plat: p291   vari: 2g
      Find match dtb: 5
wipe_data=successful
wipe_cache=successful
_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

cmd store failed
Err imgread(L333):Fail to read 0x2000B from part[logo] at offset 0
There is no valid bmp file at the given address
[OSD]load fb addr from dts
[OSD]fb_addr for logo: 0x3dc00000
[OSD]load fb addr from dts
[OSD]fb_addr for logo: 0x3dc00000
[CANVAS]addr=0x3dc00000 width=3840, height=2160
There is no valid bmp file at the given address
upgrade_step=0
amlkey_init() enter!
[EFUSE_MSG]keynum is 4
[BL31]: tee size: 0
[KM]Error:f[keymanage_dts_get_key_device]L85:ch_code key name is not exist
[KM]Error:f[_get_km_ops_by_name]L231:key ch_code not know device 4
[KM]Error:f[key_manage_query_exist]L546:There isn't dts cfg for key[ch_code]
[KM]Error:f[key_manage_query_size]L503:Fail in query key exist
rebootmode=cold_boot
Enter USB burn
Try connect time out 701, 700, 771
key1 = 7d82dd22
key2 = 7e81dd22
key3 = 728ddd22
time_out = 7a120
ir init
irkey - irkey key_value1 key_value2 key_value3 time_value

Usage:
irkey
Hit any 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

cmd store failed
Err imgread(L132):Fail to read 0x100000B from part[boot] at offset 0
Enter USB burn
Try connect time out 1001, 1000, 2097
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

cmd store failed
Err imgread(L132):Fail to read 0x100000B from part[recovery] at offset 0
gxl_p211_v1#

设备：CM211-1
主板：MC022
镜像：release： Armbian_23.08.0_amlogic_s905l3-cm211_jammy_6.1.39_server_2023.07.20.img.gz

aolin2000 · Answer 18 · Wed Jul 26 2023 15:49:15 GMT+0800 (China Standard Time)

可以驱动CM211-1的WIFI了吗？(uew5621ds)

Jake10102016 · Answer 19 · Sun Jul 30 2023 08:28:28 GMT+0800 (China Standard Time)

设备：CM211-1，北京移动，闪存颗粒是NAND，U盘可以正常启动，写入成功，从闪存启动无法启动

lisir-77 · Answer 20 · Mon Aug 07 2023 15:53:47 GMT+0800 (China Standard Time)

就是可以发个视频给我借鉴一下吗谢谢各位

lanlandezei · Answer 21 · Mon Aug 14 2023 20:18:17 GMT+0800 (China Standard Time)

我这款盒子是不是刷不了armbian，线刷安卓没问题，下了各种版本armbian固件s905l s905l3 s905l3b。开心盒子助手adb reboot update 调试U盘启动都启动不了。我的机器dtb是p291，USB写入固件后看都没有p291 这个型号的dtb文件。

Gx · Answer 22 · Sat Sep 16 2023 17:44:08 GMT+0800 (China Standard Time)

121 s905l3 CM211-1 meson-gxl-s905l3b-m302a.dtb
122 s905l3b E900V22D,TY1608 meson-gxl-s905l2-x7-5g.dtb
123 s905l3b E900V21E,E900V22E,MGV2000 meson-gxl-s905l3b-e900v22e.dtb
124 s905l3b M302A,M304A,CM211-1,CM311-1 meson-gxl-s905l3b-m302a.dtb
125 s905l3b IP103H,TY1608,BV310,B860AV-2.1M meson-gxl-s905l3b-m302a.dtb
126 s905lb BesTV-R3300L,SumaVision-Q7,MG101 meson-gxl-s905x-p212.dtb
127 s905lb Q96-mini meson-gxl-s905x-p212.dtb
128 s905mb S65 meson-gxl-s905x-p212.dtb
0 Other Customize Enter-custom-dtb-name

[ OPTIONS ] Please Input ID: 124
[ INFO ] Input Box ID: [ 124 ]
[ INFO ] Model Name: [ M302A,M304A,CM211-1,CM311-1 ]
[ INFO ] FDTFILE: [ meson-gxl-s905l3b-m302a.dtb ]
[ INFO ] MAINLINE_UBOOT: [ ]
[ INFO ] BOOTLOADER_IMG: [ ]
[ INFO ] UBOOT_OVERLOAD: [ u-boot-s905x-s912.bin ]
[ INFO ] NEED_OVERLOAD: [ yes ]
[ STEPS ] Which type of filesystem do you want for your root?

ID TYPE

1 ext4
2 btrfs

[ OPTIONS ] Please Input ID (1/2): 1
[ INFO ] Input Type ID: [ 1 ]
[ INFO ] Type of filesystem: [ ext4 ]
[ STEPS ] Partitioning eMMC...
[ INFO ] Start backing up the default bootloader.
dd: error reading '/dev/mmcblk2': Input/output error
0+0 records in
0+0 records out
0 bytes copied, 1.12973 s, 0.0 kB/s
[ ERROR ] Using dd to backup [ /usr/lib/u-boot/mybox-bootloader.img ] failed.
root@armbian:~#

Gx · Answer 23 · Sun Sep 17 2023 14:58:17 GMT+0800 (China Standard Time)

121 s905l3 CM211-1 介子-gxl-s905l3b-m302a.dtb 122 s905l3b E900V22D，TY1608 介子-gxl-s905l2-x7-5g.dtb 123 s905l3b E900V21E，E900V22E，MGV2000 介子-gxl-s905l3b-e900v22e.dtb 124 s905l3b M302A，M304A，CM211-1，CM311-1 介子-gxl-s905l3b-m302a.dtb 125 s905l3b IP103H，TY1608，BV310，B860AV-2.1M 介子-gxl-s905l3b-m302a.dtb 126 s905lb 百视通-R3300L，苏玛视讯-Q7，MG101 介子-gxl-s905x-p212.dtb

127 s905lb Q96-迷你介子-gxl-s905x-p212.dtb 128 s905mb S65 介子-gxl-s905x-p212.dtb 0 其他自定义输入自定义 dtb

名称

[ 选项 ]请输入 ID： 124 [ 信息 ] 输入框 ID： [ 124 ] [ 信息 ] 型号： [ M302A，M304A，CM211-1，CM311-1 ] [ 信息 ] FDTFILE： [ 介子-gxl-s905l3b-m302a.dtb ] [ 信息 ] MAINLINE_UBOOT： [ ] [ 信息 ] BOOTLOADER_IMG： [ ] [ 信息 ] UBOOT_OVERLOAD： [ u-boot-s905x-s912.bin ] [ 信息 ] NEED_OVERLOAD： [ 是 ]

[ 步骤 ]

您的根需要哪种类型的文件系统？

身份证类型

1 ext4

2 btrfs
[ 选项 ]请输入 ID （1/2）： 1 [ 信息 ] 输入类型 ID： [ 1 ] [ 信息 ] 文件系统类型： [ ext4 ] [ 步骤 ] 正在分区 eMMC... [ 信息 ] 开始备份默认引导加载程序。 dd：读取错误 '/dev/mmcblk2'：输入/输出错误 0+0 记录 0+0 记录输出 0 字节复制， 1.12973 s， 0.0 kB/s [ 错误 ] 使用 dd 备份 [ /usr/lib/u-boot/mybox-bootloader.img ] 失败。 root@armbian：~#

拆机查看，闪存是NAND，是不是就没法写入了？必须emmc的芯片才行？

ophub · Answer 24 · Sun Sep 17 2023 15:04:01 GMT+0800 (China Standard Time)

不支持nand

Gx · Answer 25 · Sun Sep 17 2023 15:07:46 GMT+0800 (China Standard Time)

不支持nand

拆机看了好几个，山东魔百盒cm211-1，闪存都是nand，山东UNT402A也是nand，哭死。。。。

bo · Answer 26 · Wed Oct 18 2023 22:42:06 GMT+0800 (China Standard Time)

按照这个issue操作，写入emmc后，拔掉U盘重启：

GXLX2:BL1:3cfee7:42a5ae;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;
TE: 81558

BL2 Built : 13:36:55, Jun 22 2020.
gxl g85d6ad1 - longyong.chen@droid02-sz

Board ID = 4, adc=302
set vcck to 1070 mv
set vddee to 1070 mv
CARD_3 high, old board
CPU clk: 1200MHz

DDR3 chl: Rank0+1 @ 792MHz - FAIL
DDR3 chl: Rank0 @ 792MHz
bist_test rank: 0 29 08 4a 37 14 5a 21 00 42 3e 1c 61 23 03 44 38 15 5b 28 05 4b 38 14 5c 618   - PASS

Rank0: 2048MB(auto)-2T-11
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x013c0000, size: 0x00007600
Load bl301 from eMMC, src: 0x00018200, des: 0x01380000, size: 0x00002400
Load bl31 from eMMC, src: 0x0001c200, des: 0x10100000, size: 0x00019600
Load bl33 from eMMC, src: 0x00038200, des: 0x01000000, size: 0x0007b000
NOTICE:  BL3-1: v1.0(debug):361f8a7
NOTICE:  BL3-1: Built : 16:43:26, Dec 19 2018
NOTICE:  BL31: GXL normal boot!
NOTICE:  BL31: BL33 decompress pass
[Image: gxl_v1.1.3103-9234004 2018-12-27 10:43:23 yao.zhang@droid07]
efuse init ops = c5
efuse init hdcp = c, cf9=7
x2_hp_e = 0
bl30: check_permit, count is 1
bl30: check_permit: ok!
chipid: 0 0 3 c c 0 70 b3 98 a0 0 c5 not ES chip
[0.645310 Inits done]
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 (Mar 29 2021 - 17:09:00)

DRAM:  2 GiB
Relocation Offset is: 76e8c000
this uboot is for hw_1_8, set GPIODV_24gpio: pin GPIODV_24 (gpio 43) value is 1
gpio: pin GPIOZ_14 (gpio 73) value is 1
register usb cfg[0][1] = 0000000077f5bc10
[CANVAS]canvas init
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: clk_level = 7
vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
vpp: vpp_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 = 0x0000000073e7cc00
aml_priv->desc_buf = 0x0000000073e7ef20
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 5f4c4d41
      Amlogic multi-dtb tool
      Multi dtb detected
      unified board, board id = 4
      Multi dtb tool version: v2 .
      Support 6 dtbs.
        aml_dt soc: gxlx2 platform: p291 variant: 2g
        dtb 0 soc: gxl   plat: p211   vari: 1g
        dtb 1 soc: gxl   plat: p211   vari: 2g
        dtb 2 soc: gxlx   plat: p261   vari: 1g
        dtb 3 soc: gxlx   plat: p261   vari: 2g
        dtb 4 soc: gxlx2   plat: p291   vari: 1g
        dtb 5 soc: gxlx2   plat: p291   vari: 2g
      Find match dtb: 5
start dts,buffer=0000000073e81750,dt_addr=0000000073eb1750
      Amlogic multi-dtb tool
      Multi dtb detected
      unified board, board id = 4
      Multi dtb tool version: v2 .
      Support 6 dtbs.
        aml_dt soc: gxlx2 platform: p291 variant: 2g
        dtb 0 soc: gxl   plat: p211   vari: 1g
        dtb 1 soc: gxl   plat: p211   vari: 2g
        dtb 2 soc: gxlx   plat: p261   vari: 1g
        dtb 3 soc: gxlx   plat: p261   vari: 2g
        dtb 4 soc: gxlx2   plat: p291   vari: 1g
        dtb 5 soc: gxlx2   plat: p291   vari: 2g
      Find match dtb: 5
parts: 1
00:      data   ffffffffffffffff 4
init_part() 278: PART_TYPE_DOS
eMMC/TSD partition table have been checked OK!
check pattern success
mmc env offset: 0x7400000
In:    serial
Out:   serial
Err:   serial
board id is : 4
hpd_state=0
cvbs performance type = 7, table = 1
[store]To run cmd[emmc dtb_read 0x1000000 0x40000]
_verify_dtb_checksum()-924: calc 5e24f54e, store 5e24f54e
_verify_dtb_checksum()-924: calc 5e24f54e, store 5e24f54e
dtb_read()-1046: total valid 2
dtb_read()-1113: do nothing
      Amlogic multi-dtb tool
      Multi dtb detected
      unified board, board id = 4
      Multi dtb tool version: v2 .
      Support 6 dtbs.
        aml_dt soc: gxlx2 platform: p291 variant: 2g
        dtb 0 soc: gxl   plat: p211   vari: 1g
        dtb 1 soc: gxl   plat: p211   vari: 2g
        dtb 2 soc: gxlx   plat: p261   vari: 1g
        dtb 3 soc: gxlx   plat: p261   vari: 2g
        dtb 4 soc: gxlx2   plat: p291   vari: 1g
        dtb 5 soc: gxlx2   plat: p291   vari: 2g
      Find match dtb: 5
wipe_data=successful
wipe_cache=successful
_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

cmd store failed
Err imgread(L333):Fail to read 0x2000B from part[logo] at offset 0
There is no valid bmp file at the given address
[OSD]load fb addr from dts
[OSD]fb_addr for logo: 0x3dc00000
[OSD]load fb addr from dts
[OSD]fb_addr for logo: 0x3dc00000
[CANVAS]addr=0x3dc00000 width=3840, height=2160
There is no valid bmp file at the given address
upgrade_step=0
amlkey_init() enter!
[EFUSE_MSG]keynum is 4
[BL31]: tee size: 0
[KM]Error:f[keymanage_dts_get_key_device]L85:ch_code key name is not exist
[KM]Error:f[_get_km_ops_by_name]L231:key ch_code not know device 4
[KM]Error:f[key_manage_query_exist]L546:There isn't dts cfg for key[ch_code]
[KM]Error:f[key_manage_query_size]L503:Fail in query key exist
rebootmode=cold_boot
Enter USB burn
Try connect time out 701, 700, 771
key1 = 7d82dd22
key2 = 7e81dd22
key3 = 728ddd22
time_out = 7a120
ir init
irkey - irkey key_value1 key_value2 key_value3 time_value

Usage:
irkey
Hit any 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

cmd store failed
Err imgread(L132):Fail to read 0x100000B from part[boot] at offset 0
Enter USB burn
Try connect time out 1001, 1000, 2097
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

cmd store failed
Err imgread(L132):Fail to read 0x100000B from part[recovery] at offset 0
gxl_p211_v1#

设备：CM211-1 主板：MC022 镜像：release： Armbian_23.08.0_amlogic_s905l3-cm211_jammy_6.1.39_server_2023.07.20.img.gz

一模一样的主板MC022 搞定了吗？

wi86live · Answer 27 · Sun Oct 29 2023 03:43:40 GMT+0800 (China Standard Time)

不支持nand

拆机看了好几个，山东魔百盒cm211-1，闪存都是nand，山东UNT402A也是nand，哭死。。。。

看NAND 如果是BGA169封装的话在手机上拆个16gb的EMMC换上去就行了

wi86live · Answer 28 · Tue Dec 12 2023 01:41:40 GMT+0800 (China Standard Time)

你是什么盒子?自身存储440GB? 2GB的内存?S905L3b 我推荐试试 Armbian_23.11.0_amlogic_s905l3b_lunar_5.15.137_server_2023.11.02.img.gz<https://github.com/wi86live/amlogic-s9xxx-armbian/releases/download/Armbian_lunar_save_2023.11/Armbian_23.11.0_amlogic_s905l3b_lunar_5.15.137_server_2023.11.02.img.gz>,我的盒子刷的盒子是天邑TY1608,测试后这个最稳定 ,新内核可能是CPU 带不动

…

________________________________ 发件人: chinamememe ***@***.***> 发送时间: 2023年12月6日 11:44 收件人: ophub/amlogic-s9xxx-armbian ***@***.***> 抄送: wi86live ***@***.***>; Comment ***@***.***> 主题: Re: [ophub/amlogic-s9xxx-armbian] CM211-1 使用6.1内核，DTB使用m302a成功写入EMMC，网络正常 (Issue #1318) 1701862940648.jpg (view on web)<https://github.com/ophub/amlogic-s9xxx-armbian/assets/10960816/d0374062-cd3d-4cb2-87b5-359426ce5090> 一直重复 ― Reply to this email directly, view it on GitHub<#1318 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AP4YQV75VDXQVSXUL3ZP2O3YIBLBPAVCNFSM6AAAAAAXILKOJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBSG4YDSOJUGM>. You are receiving this because you commented.Message ID: ***@***.***>

skygunner · Answer 29 · Fri Feb 23 2024 20:52:59 GMT+0800 (China Standard Time)

设备：CM211-1，北京移动，闪存颗粒是NAND，U盘可以正常启动，写入成功，从闪存启动无法启动

北京移动MC022主板上的BWCMMQ511G08G存储芯片是狭义的NAND，支持emmc协议。经过armbian-install可以成功安装并启动。
5.15

[ OPTIONS ] Please Input ID: 121
[ INFO ] Input Box ID: [ 121 ]
[ INFO ] Model Name: [ CM211-1,M411A ]
[ INFO ] FDTFILE: [ meson-gxl-s905l3b-m302a.dtb ]
[ INFO ] MAINLINE_UBOOT: [  ]
[ INFO ] BOOTLOADER_IMG:  [  ]
[ INFO ] UBOOT_OVERLOAD: [ u-boot-p212.bin ]
[ INFO ] NEED_OVERLOAD: [ no ]

gaonan1212 · Answer 30 · Sun Apr 21 2024 11:13:51 GMT+0800 (China Standard Time)

Armbian_24.5.0_amlogic_s905l3-cm211_jammy_6.1.87_server_2024.04.20.img
cm211-1，u盘启动盒子绿灯，屏幕无输出没进安卓，网口一直检测不到，不知道该咋操作了
之前u盘启动只成功过openwrt系统，想搞armbian写入emmc，我的存储芯片是BWCMMQ511G08G，带wifi

ophub · Answer 31 · Sun Apr 21 2024 11:41:27 GMT+0800 (China Standard Time)

先刷下对应的安卓系统。

gaonan1212 · Answer 32 · Sun Apr 21 2024 19:03:03 GMT+0800 (China Standard Time)

Armbian_24.5.0_amlogic_s905l3-cm211_jammy_6.1.87_server_2024.04.20.img cm211-1，u盘启动盒子绿灯，屏幕无输出没进安卓，网口一直检测不到，不知道该咋操作了之前u盘启动只成功过openwrt系统，想搞armbian写入emmc，我的存储芯片是BWCMMQ511G08G，带wifi

我搞定了，cm211-1s zg，广东移动
我先刷的安卓9线刷包：S905L3 安卓9.0当贝语音版（通刷mgv3001 211-1 CM311-1)设置无密码带原生设置20220711.img
拆机短接在背面4r12，检测到设备后就不用再短接了，中途有失败可以马上调整擦除选项继续刷

刷完进安卓9开wifi，用开心电视助手连adb
armbian使用：Armbian_24.5.0_amlogic_s905l3-cm211_bookworm_6.6.28_server_2024.04.20.img
写入u盘，用开心电视助手从u盘启动，然后顺利ssh，顺利armbian-install

sr9158 · Answer 33 · Sat May 11 2024 14:27:30 GMT+0800 (China Standard Time)

Armbian_24.5.0_amlogic_s905l3-cm211_jammy_6.1.87_server_2024.04.20.img cm211-1，u盘启动盒子绿灯，屏幕无输出没进安卓，网口一直检测不到，不知道该咋操作了之前u盘启动只成功过openwrt系统，想搞armbian写入emmc，我的存储芯片是BWCMMQ511G08G，带wifi

我搞定了，cm211-1s zg，广东移动我先刷的安卓9线刷包：S905L3 安卓9.0当贝语音版（通刷mgv3001 211-1 CM311-1)设置无密码带原生设置20220711.img 拆机短接在背面4r12，检测到设备后就不用再短接了，中途有失败可以马上调整擦除选项继续刷刷完进安卓9开wifi，用开心电视助手连adb armbian使用：Armbian_24.5.0_amlogic_s905l3-cm211_bookworm_6.6.28_server_2024.04.20.img 写入u盘，用开心电视助手从u盘启动，然后顺利ssh，顺利armbian-install

请问armbian下WIFI能用吗？

gametta · Answer 34 · Tue May 14 2024 07:49:49 GMT+0800 (China Standard Time)

您好：首先905系列的可以用刷机神奇，PDD上有几块钱，不用拆机，另外如果盒子自带wifi就可以使用，如果不带可以外插一个随身WIFI，驱动一般都可以。在 2024-05-11 14:27:53，"sr9158" ***@***.***> 写道： Armbian_24.5.0_amlogic_s905l3-cm211_jammy_6.1.87_server_2024.04.20.img cm211-1，u盘启动盒子绿灯，屏幕无输出没进安卓，网口一直检测不到，不知道该咋操作了之前u盘启动只成功过openwrt系统，想搞armbian写入emmc，我的存储芯片是BWCMMQ511G08G，带wifi 我搞定了，cm211-1s zg，广东移动我先刷的安卓9线刷包：S905L3 安卓9.0当贝语音版（通刷mgv3001 211-1 CM311-1)设置无密码带原生设置20220711.img 拆机短接在背面4r12，检测到设备后就不用再短接了，中途有失败可以马上调整擦除选项继续刷刷完进安卓9开wifi，用开心电视助手连adb armbian使用：Armbian_24.5.0_amlogic_s905l3-cm211_bookworm_6.6.28_server_2024.04.20.img 写入u盘，用开心电视助手从u盘启动，然后顺利ssh，顺利armbian-install 请问armbian下WIFI能用吗？ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

CM211-1 使用6.1内核，DTB使用m302a成功写入EMMC，网络正常

Set partition size (Unit: MiB)

ID TYPE

1 ext4 2 btrfs

身份证类型

1 ext4

1 ext4
2 btrfs