search

ophub / amlogic-s9xxx-armbian

Support for Armbian in Amlogic, Rockchip and Allwinner boxes. Support a311d, s922x, s905x3, s905x2, s912, s905d, s905x, s905w, s905, s905l, rk3588, rk3568, rk3399, rk3328, h6, etc.
GNU General Public License v2.0
5.69k stars 1.82k forks source link

E900V22C的uboot和dtb #83

Closed Calmact closed 2 years ago

Calmact commented 2 years ago

E900V22C是新出的移动运营商盒子，CPU为S905L 3A-B (1.8G 四核 A53 和 G31的GPU)、2G DDR4 内存、8G eMMC5.2，100M 网卡，UWE5621DS无线芯片支持802.11a/b/g/n/ac双频无线网，海鲜市场70左右，目前使用Armbian_22.02.0_Aml_s905x2_focal_5.15.16_2022.01.22.1134.img.gz 修改boot分区下

1. 用uboot-u200.bin重命名覆盖为u-boot.ext和u-boot-x96max.bin
2. uEnv文件内修改为FDT=/dtb/amlogic/meson-g12a-u200.dtb

还是有问题，能否到E900V22C的QQ群：320724049指导下工作？

Calmact commented 2 years ago

启动日志：


U-Boot 2021.04-00056-g13ac02db31-dirty (Apr 28 2021 - 22:44:20 +0800) u200

Model: Amlogic Meson G12A U200 Development Board
SoC:   Amlogic Meson G12A (Unknown) Revision 28:b (70:2)
DRAM:  2 GiB
MMC:   sd@ffe05000: 0, mmc@ffe07000: 1
Loading Environment from nowhere... OK
In:    serial@3000
Out:   serial@3000
Err:   serial@3000
Net:   eth0: ethernet@ff3f0000
Hit any key to stop autoboot:  0
starting USB...
Bus usb@ff500000: Register 3000140 NbrPorts 3
Starting the controller
USB XHCI 1.10
scanning bus usb@ff500000 for devices... cannot reset port 2!?
cannot reset port 4!?
3 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
1123 bytes read in 1 ms (1.1 MiB/s)
## Executing script at 08000000
Start AMLOGIC mainline U-boot
## Error: "bootfromsd" not defined
unable to select a mode : -110
SCRIPT FAILED: continuing...
unable to select a mode : -110
unable to select a mode : -110
unable to select a mode : -110
unable to select a mode : -110
unable to select a mode : -110
unable to select a mode : -110
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk sd@ffe05000.blk...
unable to select a mode : -110
Scanning disk mmc@ffe07000.blk...
 ** fs_devread read error - block
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Found 4 disks
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
unable to select a mode : -110
unable to select a mode : -110
MMC Device 2 not found
no mmc device at slot 2
Speed: 100, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 43
*** Unhandled DHCP Option in OFFER/ACK: 43
DHCP client bound to address 192.168.30.103 (7 ms)
*** Warning: no boot file name; using 'C0A81E67.img'
Using ethernet@ff3f0000 device
TFTP from server 192.168.30.1; our IP address is 192.168.30.103
Filename 'C0A81E67.img'.
Load address: 0x44000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-36-3e-5e-ea-04-7b
Speed: 100, full duplex
Using ethernet@ff3f0000 device
TFTP from server 192.168.30.1; our IP address is 192.168.30.103
Filename 'pxelinux.cfg/01-36-3e-5e-ea-04-7b'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A81E67
Speed: 100, full duplex
Using ethernet@ff3f0000 device

Filename 'pxelinux.cfg/default'.
Load address: 0x1080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Config file not found
Speed: 100, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 43
*** Unhandled DHCP Option in OFFER/ACK: 43
DHCP client bound to address 192.168.30.103 (17 ms)
Using ethernet@ff3f0000 device
TFTP from server 192.168.30.1; our IP address is 192.168.30.103
Filename 'boot.scr.uimg'.
Load address: 0x8000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Speed: 100, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 43
*** Unhandled DHCP Option in OFFER/ACK: 43
DHCP client bound to address 192.168.30.103 (7 ms)
Using ethernet@ff3f0000 device
TFTP from server 192.168.30.1; our IP address is 192.168.30.103
Filename 'boot.scr.uimg'.
Load address: 0x8080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
=>
ophub commented 2 years ago

下载s905x的固件，什么也别修改，写入TF/USB使用，不支持写入EMMC

Calmact commented 2 years ago

不修改无法进uboot，这个CPU应该是s905x2?

ophub commented 2 years ago

用5.4内核可以试一试，删除u-boot.ext，不用这个

s905x的固件在s905X/L/W通用。你试5.4内核的固件，不用u-boot，只需要测试哪个dtb适合你的盒子

魔百盒s905L用 meson-gxl-s905x-p212.dtb meson-g12a-u200.dtb meson-g12a-sei510.dtb

Calmact commented 2 years ago

x2已经测试不修改uboot使用meson-g12a-u200.dtb能够进系统，但是没网有线网络，s905L 3A-B和s905L 还是不一样，e900v22c的s905L 3A-B在coreELEC和emuelec里面使用g12a_s905x2_2g.dtb的设备树有线网络没问题，只是没识别无线蓝牙芯片UWE5621DS和红外遥控。 请问： 1、elec系统里的g12a_s905x2_2g.dtb能否直接/修改后在s905L 3A-B上使用？ 2、e900v22c（或者其他机型）在armbian适用的dtb文件，如何编译生成？ 3、uboot如何影响，如果s905L 3A-B是s905x2的马甲芯片，应该如何修改才能完美适配？ 4、无线蓝牙芯片UWE5621D的驱动适配仅需修改dtb么，还是只要找到驱动编译就行了，驱动仓库https://github.com/Stane1983/uwe5621-aml

ophub commented 2 years ago

都是在内核里修改/编译。 https://github.com/unifreq/linux-5.10.y/tree/main/arch/arm64/boot/dts/amlogic

Calmact commented 2 years ago

最近新上市的一批移动盒子S905L 3A-B、S905L 3A主控的，比如E900V22C/D，性能强悍，是原来S905X2的马甲，性能大概是X3的4/5，能够从u盘启动armbian，ee，ce这些系统，使用u200的dtb。e900v22c的Q群：320724049，诚邀@ophub大神来指导工作。

xcray commented 2 years ago

我前段时间弄了个江苏的M401A，试来试去，必须用u200的dtb才能启动；写入emmc的话，只有e900v22c的uboot + u200的dtb才行，并且不能写入bootloader。