Add support for eaidk-610 #991

13584452567 · 2023-02-01T11:49:54Z

添加对于eaidk-610的支持
PS：这块板子的AP6255模块内置的蓝牙在5.15.x内核下会出现蓝牙固件加载失败的问题，这个问题经过测试在6.1.x上内核已被解决。

添加对于eaidk-610的支持

ophub · 2023-02-01T12:13:40Z

多谢分享
这个设备是emmc还是tf卡？

安装使用方法8里面介绍一下这个设备的使用方法

https://github.com/ophub/amlogic-s9xxx-armbian/blob/main/build-armbian/documents/README.cn.md

13584452567 · 2023-02-01T12:20:33Z

好的，随后添加

ophub · 2023-02-01T12:24:15Z

48052d4

刚才忘了rebuild里添加选项了，我补充上了。

ophub · 2023-02-01T12:57:27Z

https://github.com/ophub/amlogic-s9xxx-armbian/releases/tag/Armbian_jammy_02.01.0756

你下载文件名称里带eaidk-610标签的，测试下是否使用正常。

13584452567 · 2023-02-01T14:21:50Z

可以，功能都可用。十分感谢

ophub · 2023-02-01T14:35:24Z

好的👌感谢分享支持。

13584452567 · 2023-02-02T01:52:01Z

大佬有没有armbian移植相关的群？我想进去学习学习。

ophub · 2023-02-02T02:21:15Z

我也没找到armbian的群，我在f大的openwrt群里学习。

去年我在f大的群里看到一个很形象的比喻，有个网友把他比做盒子圈的袁隆平，因为他把openwrt和armbian进行了杂交融合创新，使用了armbian的启动机制，融合openwrt的主体功能，打开了在盒子里使用openwrt的大门。

一年前他同时发布openwrt和armbian，持续发布到第56版，后来他改用内核制作openwrt后停止了继续发布armbian。当时我刚开始使用armbian，觉得没了挺可惜的，就一边向他请教，一边网上搜索教程，一知半解地创建了这个armbian仓库。

在这个armbian的重构中，我延续了f大之前的使用标准和习惯，在内核、u-boot等方面和openwrt通用，所以理论上支持openwrt使用的盒子都可以使用对应的armbian，反之也一样。

他创建了很多仓库，包括u-boot的制作、内核源码、打包制作等，里面有相关的教程。

f大的仓库和他在恩山的帖子中都有他的群链接
https://github.com/unifreq/openwrt_packit
https://www.right.com.cn/forum/thread-4076037-1-1.html

13584452567 · 2023-02-02T02:42:39Z

感谢大佬答疑解惑！

ihexon · 2023-02-03T20:17:39Z

刚好学校电子实验室里有这个板子，我稍微试了一下 Armbian_23.02.0_rockchip_eaidk-610_jammy_6.1.9_server_2023.02.02.img 这个镜像，写入 emmc 似乎并不能启动，串口提示：## Error: "distro_bootcmd" not defined

附上 uboot 日志：

U-Boot TPL 2023.01-00934-gf147aa80f5 (Jan 30 2023 - 21:49:58)
Channel 0: LPDDR3, 800MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR3, 800MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2023.01-00934-gf147aa80f5 (Jan 30 2023 - 21:49:58 +0800)
Trying to boot from MMC2


U-Boot 2023.01-00934-gf147aa80f5 (Jan 30 2023 - 21:49:58 +0800)

SoC: Rockchip rk3399
Reset cause: POR
Model: OPEN AI LAB EAIDK-610
DRAM:  3.9 GiB
PMIC:  RK808
Core:  279 devices, 23 uclasses, devicetree: separate
MMC:   mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
Model: OPEN AI LAB EAIDK-610
Net:
Error: ethernet@fe300000 address not set.
No ethernet found.

Hit any key to stop autoboot:  0
## Error: "distro_bootcmd" not defined

操作步骤：

$ sudo ./rkdeveloptool db ~/rk3399_loader_v1.27.126.bin
$ sudo ./rkdeveloptool wl 0x0 ~/Armbian_23.02.0_rockchip_eaidk-610_jammy_6.1.9_server_2023.02.02.img

rk3399_loader_v1.27.126.bin 来源 amlogic-s9xxx-armbian/build-armbian/u-boot/rockchip/eaidk-610/rk3399_loader_v1.27.126.bin

这个镜像是写入 SDCARD 里启动的？

13584452567 · 2023-02-04T00:18:49Z

刚好学校电子实验室里有这个板子，我稍微试了一下 Armbian_23.02.0_rockchip_eaidk-610_jammy_6.1.9_server_2023.02.02.img 这个镜像，写入 emmc 似乎并不能启动，串口提示：## Error: "distro_bootcmd" not defined

附上 uboot 日志：

U-Boot TPL 2023.01-00934-gf147aa80f5 (Jan 30 2023 - 21:49:58)
Channel 0: LPDDR3, 800MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR3, 800MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2023.01-00934-gf147aa80f5 (Jan 30 2023 - 21:49:58 +0800)
Trying to boot from MMC2


U-Boot 2023.01-00934-gf147aa80f5 (Jan 30 2023 - 21:49:58 +0800)

SoC: Rockchip rk3399
Reset cause: POR
Model: OPEN AI LAB EAIDK-610
DRAM:  3.9 GiB
PMIC:  RK808
Core:  279 devices, 23 uclasses, devicetree: separate
MMC:   mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
Model: OPEN AI LAB EAIDK-610
Net:
Error: ethernet@fe300000 address not set.
No ethernet found.

Hit any key to stop autoboot:  0
## Error: "distro_bootcmd" not defined

操作步骤：

$ sudo ./rkdeveloptool db ~/rk3399_loader_v1.27.126.bin
$ sudo ./rkdeveloptool wl 0x0 ~/Armbian_23.02.0_rockchip_eaidk-610_jammy_6.1.9_server_2023.02.02.img

rk3399_loader_v1.27.126.bin 来源 amlogic-s9xxx-armbian/build-armbian/u-boot/rockchip/eaidk-610/rk3399_loader_v1.27.126.bin

这个镜像是写入 SDCARD 里启动的？

这个镜像直接烧录到TF卡上就可以使用，但是板子上的uboot不能使用rk维护的，必须使用主线uboot。也可刷入到emmc进行启动，我所使用的工具是AndroidTool_Release_v2.64，windows下的具体配置为
0xCCCCCCCC Boot ./rk3399_loader_v1.27.126.bin
0x00000000 system ./image/Armbian_23.02.0_rockchip_eaidk-610_jammy_6.1.9_server_2023.02.02.img

具体的操作过程我过段时间解决了这块板子的spi和网卡负载异常问题之后再写。

也有其他人遇到了同样的问题，已经定位问题。将提交一个更改来兼容新版的EAIDK-610布局

Add support for eaidk-610

13584452567 · 2023-03-01T13:24:20Z

对了，EAIDK-610的启动时间略长。看日志每次都在等待两个进程超时。一个是raise network interface，另一个是trying to start ttyAML0,。可否关闭呢？尤其是后面那个ttyaml0

ophub · 2023-03-01T13:32:24Z

amlogic-s9xxx-armbian/build-armbian/armbian-files/common-files/usr/sbin/armbian-fix

Line 83 in c4e02b9

    
           [[ "${platform_name}" == "rockchip" ]] && sudo systemctl disable serial-getty@ttyFIQ0 2>/dev/null && echo "29. Disable ttyFIQ0 (ttyS2)"

之前r66s这么禁止的

13584452567 · 2023-03-01T13:33:37Z

这个armbian-fix在什么时候运行的？只能系统启动之后运行一次来修复吗？

ophub · 2023-03-01T13:35:22Z

amlogic-s9xxx-armbian/rebuild

Lines 851 to 853 in c4e02b9

    
           # Add tasks that need to be executed on initial startup 
        
           armbian_firstrun="usr/lib/armbian/armbian-firstrun" 
        
           sed -i '/armbian-release/i\[ -f "/usr/sbin/armbian-fix" ] && . /usr/sbin/armbian-fix' ${armbian_firstrun}

只初始化时运行一次

ophub · 2023-03-01T13:35:58Z

你试试刚才 https://github.com/ophub/amlogic-s9xxx-armbian/releases/tag/Armbian_bullseye_03.01.0815
能不能启动了

13584452567 · 2023-03-01T13:35:59Z

好的

13584452567 · 2023-03-01T13:36:14Z

你试试刚才 https://github.com/ophub/amlogic-s9xxx-armbian/releases/tag/Armbian_bullseye_03.01.0815 能不能启动了

还是不行，而且抓不到日志。

ophub · 2023-03-01T13:37:07Z

trying to start ttyAML0

systemctl stop getty@ttyAML0
systemctl disable getty@ttyAML0
systemctl status getty@ttyAML0

你用这个禁止试试

ophub · 2023-03-01T13:48:25Z

之前测试的有日志？卡哪了？
还是这几次测试都一样没有日志？

13584452567 · 2023-03-01T13:51:37Z

之前测试的有日志？卡哪了？还是这几次测试都一样没有日志？

之前是有uboot输出，然后卡在trying to boot mmc0...,这几次测试直接无了。
那个能用的armbian包貌似没有区分出bootfs和rootfs
我试一试用官方的orange pi 3的包，按道理那个应该也是H6通用的。

ophub · 2023-03-01T14:00:17Z

没有区分出bootfs和rootfs使用的是GPT分区表

因为跳过的区域小了所以破坏了无法挂载。
https://wiki.freebsd.org/arm/Allwinner/booting
使用GPT要跳过128k以上

ophub · 2023-03-01T14:12:38Z

https://linux-sunxi.org/Bootable_SD_card#SD_Card_Layout

缺这个文件？

13584452567 · 2023-03-01T14:21:24Z

这个我在安卓里看到过，在全志平台里，script.bin用于指定SOC控制器和GPIO相关的配置。script.bin是由script.fex用工具转换得来.

13584452567 · 2023-03-15T08:11:14Z

什么是I2C接口的oled屏幕呢？我没记错的话这块板子的视频输出接口应该只有HDMI,MIPI Panel，eDP这三个接口。

板子的gpio引脚全部使能，如果你是要使用gpio以I2C协议链接屏幕的话，你需要修改dts内的gpio定义，自行编译dtb然后替换boot/dtb目录下的dtb。如果嫌麻烦，可以尝试使用eaidk-610的官方fedora 28 固件，很遗憾，我这里没有官方固件，没办法提供给你。

这块板子除了spi和type-c（上游驱动貌似有问题，始终无法注册tcpm），其余功能应该已经全部启用。

我手边并没有gpio接口的屏幕，无法给你提供详细的操作流程。

phcl1998 · 2023-03-15T08:24:30Z

什么是I2C接口的oled屏幕呢？我没记错的话这块板子的视频输出接口应该只有HDMI,MIPI Panel，eDP这三个接口。

板子的gpio引脚全部使能，如果你是要使用gpio以I2C协议链接屏幕的话，你需要修改dts内的gpio定义，自行编译dtb然后替换boot/dtb目录下的dtb。如果嫌麻烦，可以尝试使用eaidk-610的官方fedora 28 固件，很遗憾，我这里没有官方固件，没办法提供给你。

这块板子除了spi和type-c（上游驱动貌似有问题，始终无法注册tcpm），其余功能应该已经全部启用。

我手边并没有gpio接口的屏幕，无法给你提供详细的操作流程。

好的，感谢！我说的不对，是通信方为i2c的oled屏幕，控制芯片是ssd1306，不过还是感谢大佬回复我这个小白

Add support for eaidk-610

phcl1998 · 2023-03-21T10:26:31Z

大佬我现在知道为啥板子上的i2c用不了了，在dtb文件里没有开启i2c，我根据用户手册发现GPIO2_A7/I2C7_SDA、GPIO2_B0/I2C7_SCL在rk3399-eaidk-610.dts文件里对应的是i2c7 = "/i2c@ff160000";

i2c@ff160000 {
		compatible = "rockchip,rk3399-i2c";
		reg = <0x00 0xff160000 0x00 0x1000>;
		assigned-clocks = <0x08 0x46>;
		assigned-clock-rates = <0xbebc200>;
		clocks = <0x08 0x46 0x08 0x15a>;
		clock-names = "i2c\0pclk";
		interrupts = <0x00 0x24 0x04 0x00>;
		pinctrl-names = "default";
		pinctrl-0 = <0x3e>;
		#address-cells = <0x01>;
		#size-cells = <0x00>;
		status = "okay";
		phandle = <0xec>;
	};

把status = "disabled"，改为status = "okay";然后重新编译为dtb，替换原有的dtb重启之后就可以识别了

yifengyou · 2023-03-21T14:33:16Z

请问 eaidk-610的官方fedora 28 固件 dts在哪里能获取到，亦或是只能从dtb转换？

13584452567 · 2023-03-22T00:46:23Z

大佬我现在知道为啥板子上的i2c用不了了，在dtb文件里没有开启i2c，我根据用户手册发现GPIO2_A7/I2C7_SDA、GPIO2_B0/I2C7_SCL在rk3399-eaidk-610.dts文件里对应的是i2c7 = "/i2c@ff160000";
i2c@ff160000 {
		compatible = "rockchip,rk3399-i2c";
		reg = <0x00 0xff160000 0x00 0x1000>;
		assigned-clocks = <0x08 0x46>;
		assigned-clock-rates = <0xbebc200>;
		clocks = <0x08 0x46 0x08 0x15a>;
		clock-names = "i2c\0pclk";
		interrupts = <0x00 0x24 0x04 0x00>;
		pinctrl-names = "default";
		pinctrl-0 = <0x3e>;
		#address-cells = <0x01>;
		#size-cells = <0x00>;
		status = "okay";
		phandle = <0xec>;
	};
把status = "disabled"，改为status = "okay";然后重新编译为dtb，替换原有的dtb重启之后就可以识别了

感谢你的测试反馈！我稍后将推送补丁默认启用i2c7

13584452567 · 2023-03-22T00:48:50Z

请问 eaidk-610的官方fedora 28 固件 dts在哪里能获取到，亦或是只能从dtb转换？

我这里并没有fedora固件，没有办法帮到你。非常抱歉

不过generic的linux固件一般是获取uboot传入的设备树，像armbian这种使用自己的dtb的应该比较少？

或许你可以尝试拆解编译好的uboot.bin，用hexeditor把dtb提取出来？

yifengyou · 2023-03-23T23:01:51Z

最近发现这个问题，插上电源启动正常，但是按reset重启，就会卡在这里，这会是什么原因呢？

13584452567 · 2023-03-23T23:32:46Z

最近发现这个问题，插上电源启动正常，但是按reset重启，就会卡在这里，这会是什么原因呢？

看起来你的uboot还是官方的远古版本，想要引导主线内核需要主线的uboot。

按道理强刷应该会刷新uboot到主线的，你可能需要再尝试一次。

Add support for eaidk-610

dos7lo · 2023-04-07T09:31:07Z

大佬，这块板子自带的mipi 5.5存触控屏没有显示输出这个需要怎么调整啊？
https://github.com/yifengyou/eaidk-610/blob/master/docs/eaidk-610%E5%BC%80%E5%8F%91%E6%9D%BF%E4%BB%8B%E7%BB%8D/LCD.md

phcl1998 · 2023-04-23T11:25:29Z

分享一下官方提供的系统以及ubuntu、安卓系统：
https://pan.baidu.com/s/1qZ-ONFsT9yiqdlNjLbLsWQ?pwd=63aa
提取码:63aa

gfarry · 2023-05-08T15:50:20Z

你好！r99 rk3399 怎么入手？想装armbian

phcl1998 · 2023-05-09T00:52:14Z

你好！r99 rk3399 怎么入手？想装armbian

闲鱼入手

yifengyou · 2023-05-12T14:22:43Z

大佬，这块板子自带的mipi 5.5存触控屏没有显示输出这个需要怎么调整啊？ https://github.com/yifengyou/eaidk-610/blob/master/docs/eaidk-610%E5%BC%80%E5%8F%91%E6%9D%BF%E4%BB%8B%E7%BB%8D/LCD.md

巧了，我正在适配，希望早日成功~

Lasius-alienus · 2023-07-09T01:46:21Z

这块屏我也在研究，使用orangepi 4 lts ubuntu jammy 5.18.5系统官方说明文档描述了一种使用overlay点亮mipi屏幕的方法，但由于参数不同无法显示画面，只能点亮背光。eaidk官方提供的fedora 28我只获取了fdt，这块板子的资料里面有相关的内核源码，里面有dts文件，上述的这些文件我都提取出来了，部分反编译了dts，做了一些移植mipi部分dts的尝试，这些文件全部放在 https://github.com/Lasius-alienus/eaidk-610-device-tree ，需要的话自行研究。

ophub · 2023-07-09T01:49:53Z

感谢分享

Lasius-alienus · 2023-07-17T00:12:26Z

这块屏幕的驱动不是在dts中描述的，研究香橙派的屏幕驱动方法给了我一定的启发。一般的全部在dts中描述屏幕所有信息的方式并不可行，dts中只需要空节点。armbian(5.15.y)官方和orangepi提供的源码都在Kernel/drivers/gpu/drm/panel提供了sitronix-st7703这个对应的驱动，以模块安装到内核里然后在overlay里面仿照orangepi官方给的dtbo写一个适配这个屏幕的dtbo应该就可以了。顺便一提，对于GENERIC(ELF)镜像而言，eaidk官方提供的镜像中dtb都存储在kernel.img里面，这个好像没法拆。

Add support for eaidk-610

yifengyou · 2023-08-26T23:33:44Z

这块屏幕的驱动不是在dts中描述的，研究香橙派的屏幕驱动方法给了我一定的启发。一般的全部在dts中描述屏幕所有信息的方式并不可行，dts中只需要空节点。armbian(5.15.y)官方和orangepi提供的源码都在Kernel/drivers/gpu/drm/panel提供了sitronix-st7703这个对应的驱动，以模块安装到内核里然后在overlay里面仿照orangepi官方给的dtbo写一个适配这个屏幕的dtbo应该就可以了。顺便一提，对于GENERIC(ELF)镜像而言，eaidk官方提供的镜像中dtb都存储在kernel.img里面，这个好像没法拆。

# ll resource.img 
-rw-r--r-- 1 root root 1.1M  8月 26 20:59 resource.img
# ls out-resource.img/
  logo.bmp  logo_kernel.bmp  rk-kernel.dtb

eaidk官方fedora镜像，uboot初始化阶段会去加载resource.img 中的rk-kernel.dtb，然后操作其他。

Lasius-alienus · 2023-09-01T12:11:25Z

这块屏幕的驱动不是在dts中描述的，研究香橙派的屏幕驱动方法给了我一定的启发。一般的全部在dts中描述屏幕所有信息的方式并不可行，dts中只需要空节点。armbian(5.15.y)官方和orangepi提供的源码都在Kernel/drivers/gpu/drm/panel提供了sitronix-st7703这个对应的驱动，以模块安装到内核里然后在overlay里面仿照orangepi官方给的dtbo写一个适配这个屏幕的dtbo应该就可以了。顺便一提，对于GENERIC(ELF)镜像而言，eaidk官方提供的镜像中dtb都存储在kernel.img里面，这个好像没法拆。
# ll resource.img 
-rw-r--r-- 1 root root 1.1M  8月 26 20:59 resource.img
# ls out-resource.img/
  logo.bmp  logo_kernel.bmp  rk-kernel.dtb
eaidk官方fedora镜像，uboot初始化阶段会去加载resource.img 中的rk-kernel.dtb，然后操作其他。

您好，我之前尝试提取dtb的操作失败了，请问您有提取的dtb吗。此外，您现在成功驱动了mipi屏幕吗？

我之所以认为不在dtb当中定义是因为：

opi的屏幕驱动方式是在dtb中保留空节点，通过编译的模块驱动屏幕。
我尝试移植的dts当中mipi的flag部分无法编译成功，无论是armbian（5.15.y）源码还是opi提供的源码都是如此。

Add support for eaidk-610

tomorrowrain · 2025-10-08T08:27:41Z

咨询下大佬，tf卡写入系统镜像Armbian_25.11.0_rockchip_eaidk-610_trixie_6.1.154_server_2025.10.01.img，上电后，micro usb的串口，还能直接使用吗？

13584452567 · 2025-10-08T11:58:42Z

咨询下大佬，tf卡写入系统镜像Armbian_25.11.0_rockchip_eaidk-610_trixie_6.1.154_server_2025.10.01.img，上电后，micro usb的串口，还能直接使用吗？

理论上应该没问题，Win直接连接MicroUSB接口之后会显示串口设备连接，直接用putty就可以看日志了。

至少在我适配的时候是这样。这东西就是板载了一个UART串口转换器，如果不能用的话可能要在上位机上安装驱动，跟板子上的驱动关系不是很大。

tomorrowrain · 2025-10-09T14:07:54Z

大佬，试了用rufus和balenadEtcher将镜像烧入tf卡,启动的日志打印如下，尝试问过元宝和千问，但基础太差，未找到有用信息，请求大佬帮忙解答下，元宝提到的关键信息是缺少trust.img 以及尝试通过usb进行刷机。
启动日志如下：
DDR Version 1.12 20180518
In
Channel 0: LPDDR3, 800MHz
CS = 0
MR0=0x58
MR1=0x58
MR2=0x58
MR3=0x58
MR4=0x3
MR5=0x1
MR6=0x6
MR7=0x0
MR8=0x1F
MR9=0x1F
MR10=0x1F
MR11=0x1F
MR12=0x1F
MR13=0x1F
MR14=0x1F
MR15=0x1F
MR16=0x1F
CS = 1
MR0=0x58
MR1=0x58
MR2=0x58
MR3=0x58
MR4=0x3
MR5=0x1
MR6=0x6
MR7=0x0
MR8=0x1F
MR9=0x1F
MR10=0x1F
MR11=0x1F
MR12=0x1F
MR13=0x1F
MR14=0x1F
MR15=0x1F
MR16=0x1F
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=2048MB
Channel 1: LPDDR3, 800MHz
CS = 0
MR0=0x58
MR1=0x58
MR2=0x58
MR3=0x58
MR4=0x3
MR5=0x1
MR6=0x6
MR7=0x0
MR8=0x1F
MR9=0x1F
MR10=0x1F
MR11=0x1F
MR12=0x1F
MR13=0x1F
MR14=0x1F
MR15=0x1F
MR16=0x1F
CS = 1
MR0=0x58
MR1=0x58
MR2=0x58
MR3=0x58
MR4=0x3
MR5=0x1
MR6=0x6
MR7=0x0
MR8=0x1F
MR9=0x1F
MR10=0x1F
MR11=0x1F
MR12=0x1F
MR13=0x1F
MR14=0x1F
MR15=0x1F
MR16=0x1F
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=2048MB
256B stride
ch 0 ddrconfig = 0x101, ddrsize = 0x2020
ch 1 ddrconfig = 0x101, ddrsize = 0x2020
pmugrf_os_reg[2] = 0x3AA0DAA0, stride = 0xD
OUT
Boot1: 2018-04-08, version: 1.12
CPUId = 0x0
ChipType = 0x10, 218
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14910MB
FwPartOffset=2000 , 100000
mmc0:cmd5,32
SdmmcInit=0 0
BootCapSize=0
UserCapSize=119850MB
FwPartOffset=2000 , 0
StorageInit ok = 141072
LoadTrustBL
Addr:0x4000 No find trust.img!
LoadTrustBL error:-3
LoadTrustBL
No find bl30.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xa4554
RunBL31 0x10000
NOTICE: BL31: v1.3(debug):65aa5ce
NOTICE: BL31: Built : 10:47:37, Jun 19 2018
NOTICE: BL31: Rockchip release version: v1.1
INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 0
INFO: plat_rockchip_pmu_init(1151): pd status 3e
INFO: BL31: Initializing runtime services
INFO: BL31: Initializing BL32
INF [0x0] TEE-CORE:init_primary_helper:337: Initializing (1.1.0-170-gc4654a6 #16 Wed May 30 08:54:30 UTC 2018 aarch64)

INF [0x0] TEE-CORE:init_primary_helper:338: Release version: 1.2

INF [0x0] TEE-CORE:init_teecore:83: teecore inits done
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9

U-Boot 2014.10-RK3399-06 (May 13 2021 - 12:00:48)

CPU: rk3399
cpu version = 0
CPU's clock information:
aplll = 816000000HZ
apllb = 24000000HZ
gpll = 800000000HZ
aclk_periph_h = 133333333HZ, hclk_periph_h = 66666666HZ, pclk_periph_h = 33333333HZ
aclk_periph_l0 = 100000000HZ, hclk_periph_l0 = 100000000HZ, pclk_periph_l0 = 50000000HZ
hclk_periph_l1 = 100000000HZ, pclk_periph_l1 = 50000000HZ
cpll = 800000000HZ
dpll = 800000000HZ
vpll = 24000000HZ
npll = 24000000HZ
ppll = 676000000HZ
Board: Rockchip platform Board
Uboot as second level loader
DRAM: Found dram banks: 1
Adding bank:0000000000200000(00000000ffe00000)
Reserve memory for trust os.
dram reserve bank: base = 0x08400000, size = 0x01e00000
128 MiB
SdmmcInit = 0 0
SDCard Update.
storage init OK!
Using default environment

GetParam
W: Invalid Parameter's tag (0x00000000)!
Invalid parameter
No pmic detect.
CPU's clock information:
aplll = 816000000HZ
apllb = 24000000HZ
gpll = 800000000HZ
aclk_periph_h = 133333333HZ, hclk_periph_h = 66666666HZ, pclk_periph_h = 33333333HZ
aclk_periph_l0 = 100000000HZ, hclk_periph_l0 = 100000000HZ, pclk_periph_l0 = 50000000HZ
hclk_periph_l1 = 100000000HZ, pclk_periph_l1 = 50000000HZ
cpll = 800000000HZ
dpll = 800000000HZ
vpll = 24000000HZ
npll = 24000000HZ
ppll = 676000000HZ
misc partition not found!
SecureBootEn = 0, SecureBootLock = 0

#Boot ver: 0000-00-00#0.00
empty serial no.
normal boot.
no fuel gauge found
no fuel gauge found
read logo on state from dts [0]
no fuel gauge found
'recovery' does not seem to be a partition nor an address
Unable to boot:recovery
try to start backup
'backup' does not seem to be a partition nor an address
Unable to boot:backup
try to start rockusb

13584452567 · 2025-10-09T14:14:18Z

大佬，试了用rufus和balenadEtcher将镜像烧入tf卡,启动的日志打印如下，尝试问过元宝和千问，但基础太差，未找到有用信息，请求大佬帮忙解答下，元宝提到的关键信息是缺少trust.img 以及尝试通过usb进行刷机。启动日志如下： DDR Version 1.12 20180518 In Channel 0: LPDDR3, 800MHz CS = 0 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x3 MR5=0x1 MR6=0x6 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F CS = 1 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x3 MR5=0x1 MR6=0x6 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=2048MB Channel 1: LPDDR3, 800MHz CS = 0 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x3 MR5=0x1 MR6=0x6 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F CS = 1 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x3 MR5=0x1 MR6=0x6 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=2048MB 256B stride ch 0 ddrconfig = 0x101, ddrsize = 0x2020 ch 1 ddrconfig = 0x101, ddrsize = 0x2020 pmugrf_os_reg[2] = 0x3AA0DAA0, stride = 0xD OUT Boot1: 2018-04-08, version: 1.12 CPUId = 0x0 ChipType = 0x10, 218 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd5,32 SdmmcInit=0 0 BootCapSize=0 UserCapSize=119850MB FwPartOffset=2000 , 0 StorageInit ok = 141072 LoadTrustBL Addr:0x4000 No find trust.img! LoadTrustBL error:-3 LoadTrustBL No find bl30.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xa4554 RunBL31 0x10000 NOTICE: BL31: v1.3(debug):65aa5ce NOTICE: BL31: Built : 10:47:37, Jun 19 2018 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1151): pd status 3e INFO: BL31: Initializing runtime services INFO: BL31: Initializing BL32 INF [0x0] TEE-CORE:init_primary_helper:337: Initializing (1.1.0-170-gc4654a6 #16 Wed May 30 08:54:30 UTC 2018 aarch64)

INF [0x0] TEE-CORE:init_primary_helper:338: Release version: 1.2

INF [0x0] TEE-CORE:init_teecore:83: teecore inits done INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9

U-Boot 2014.10-RK3399-06 (May 13 2021 - 12:00:48)

CPU: rk3399 cpu version = 0 CPU's clock information: aplll = 816000000HZ apllb = 24000000HZ gpll = 800000000HZ aclk_periph_h = 133333333HZ, hclk_periph_h = 66666666HZ, pclk_periph_h = 33333333HZ aclk_periph_l0 = 100000000HZ, hclk_periph_l0 = 100000000HZ, pclk_periph_l0 = 50000000HZ hclk_periph_l1 = 100000000HZ, pclk_periph_l1 = 50000000HZ cpll = 800000000HZ dpll = 800000000HZ vpll = 24000000HZ npll = 24000000HZ ppll = 676000000HZ Board: Rockchip platform Board Uboot as second level loader DRAM: Found dram banks: 1 Adding bank:0000000000200000(00000000ffe00000) Reserve memory for trust os. dram reserve bank: base = 0x08400000, size = 0x01e00000 128 MiB SdmmcInit = 0 0 SDCard Update. storage init OK! Using default environment

GetParam W: Invalid Parameter's tag (0x00000000)! Invalid parameter No pmic detect. CPU's clock information: aplll = 816000000HZ apllb = 24000000HZ gpll = 800000000HZ aclk_periph_h = 133333333HZ, hclk_periph_h = 66666666HZ, pclk_periph_h = 33333333HZ aclk_periph_l0 = 100000000HZ, hclk_periph_l0 = 100000000HZ, pclk_periph_l0 = 50000000HZ hclk_periph_l1 = 100000000HZ, pclk_periph_l1 = 50000000HZ cpll = 800000000HZ dpll = 800000000HZ vpll = 24000000HZ npll = 24000000HZ ppll = 676000000HZ misc partition not found! SecureBootEn = 0, SecureBootLock = 0

#Boot ver: 0000-00-00#0.00 empty serial no. normal boot. no fuel gauge found no fuel gauge found read logo on state from dts [0] no fuel gauge found 'recovery' does not seem to be a partition nor an address Unable to boot:recovery try to start backup 'backup' does not seem to be a partition nor an address Unable to boot:backup try to start rockusb

根据日志来看，你启动的还是板子上的系统，你可能需要手动破坏一下板子的uboot信息才能引导入TF卡。

注意！破坏前确保板载系统内没有重要数据，提前做好备份，不然寄了只能把片吹下来用烧录器读了。

如何破坏参考这里：#1634

当然，你也可以按照上文教程直接将系统烧录进板载存储

tomorrowrain · 2025-10-13T12:29:37Z

感谢大佬，通过线刷的方式已经刷入了Armbian_25.11.0_rockchip_eaidk-610_jammy_6.1.154_server_2025.10.01.img，我目前发现连接网线启动的时候会报下面的错误，eth0无法连接网络，而WiFi能正常连接，尝试按12.7.2 使用NetworkManager 给eth0绑定静态IP、禁用ipv6、路由器管理页面中能够看到已经为板子分配了IP，但是板子无法访问外网，也ping不到网关，可能是哪里的问题？
[ OK ] Started systemd-hostnamed.service - Hostname Service.
[ 9.273774] rk_gmac-dwmac fe300000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0
Starting NetworkManager-di…nager Script Dispatcher Service...
[ OK ] Started NetworkManager-dis…Manager Script Dispatcher Service.
[ 9.369378] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=POLL)
[ 10.885552] rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found
[ 10.886252] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW
[ 10.887265] rk_gmac-dwmac fe300000.ethernet eth0: configuring for phy/rgmii link mode
[ 13.984539] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 13.984641] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 17.630967] platform rt5651-sound: deferred probe pending
[FAILED] Failed to start NetworkMan…[0m - Network Manager Wait Online.
See 'systemctl status NetworkManager-wait-online.service' for details.
[ OK ] Reached target network-online.target - Network is Online.
Starting rc-local.service - /etc/rc.local Compatibility...
Starting rpc-statd-notify.…- Notify NFS peers of a restart...
[ OK ] Started rpc-statd-notify.s…m - Notify NFS peers of a restart.
Stopping ssh.service - OpenBSD Secure Shell server...
[ OK ] Stopped ssh.service - OpenBSD Secure Shell server.
Starting ssh.service - OpenBSD Secure Shell server...
[ OK ] Started ssh.service - OpenBSD Secure Shell server.
[ 74.338534] rc.local[1438]: Restarting ssh (via systemctl): ssh.service.
[ 74.397185] rc.local[1451]: irq name:eth0, irq:69, affinity: 8
[ 74.397546] rc.local[1451]: irq name:xhci-hcd:usb5, irq:76, affinity: 4
[ 74.397899] rc.local[1451]: irq name:xhci-hcd:usb7, irq:77, affinity: 4
[ 74.398178] rc.local[1451]: Set the rps cpu mask of eth0 to 0x33
[ OK ] Started rc-local.service - /etc/rc.local Compatibility.
Starting plymouth-quit-wai… until boot process finishes up...
Starting plymouth-quit.ser… Terminate Plymouth Boot Screen...

Add support for eaidk-610

Add support for eaidk-610

a988adb

添加对于eaidk-610的支持

ophub merged commit 467c61f into ophub:main Feb 1, 2023

ophub mentioned this pull request Feb 1, 2023

如何为仓库添加支持？ #990

Closed

ophub added a commit that referenced this pull request Feb 23, 2023

Merge pull request #991 from 13584452567/main

037e452

Add support for eaidk-610

ophub added a commit that referenced this pull request Mar 1, 2023

Merge pull request #991 from 13584452567/main

e6052e6

Add support for eaidk-610

ophub added a commit that referenced this pull request Mar 21, 2023

Merge pull request #991 from 13584452567/main

5662757

Add support for eaidk-610

ophub added a commit that referenced this pull request Mar 31, 2023

Merge pull request #991 from 13584452567/main

554ec50

Add support for eaidk-610

ophub added a commit that referenced this pull request Jul 27, 2023

Merge pull request #991 from 13584452567/main

0b7552f

Add support for eaidk-610

ophub added a commit that referenced this pull request Aug 20, 2023

Merge pull request #991 from 13584452567/main

a097d0e

Add support for eaidk-610

ophub added a commit that referenced this pull request Dec 6, 2023

Merge pull request #991 from 13584452567/main

c5f723f

Add support for eaidk-610

ophub added a commit that referenced this pull request Apr 25, 2024

Merge pull request #991 from 13584452567/main

4882718

Add support for eaidk-610

ophub added a commit that referenced this pull request Nov 2, 2025

Merge pull request #991 from 13584452567/main

00a9998

Add support for eaidk-610

Add support for eaidk-610 #991

Add support for eaidk-610 #991

Uh oh!

Conversation

13584452567 commented Feb 1, 2023

Uh oh!

ophub commented Feb 1, 2023

Uh oh!

13584452567 commented Feb 1, 2023

Uh oh!

ophub commented Feb 1, 2023

Uh oh!

ophub commented Feb 1, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

13584452567 commented Feb 1, 2023

Uh oh!

ophub commented Feb 1, 2023

Uh oh!

13584452567 commented Feb 2, 2023

Uh oh!

ophub commented Feb 2, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

13584452567 commented Feb 2, 2023

Uh oh!

ihexon commented Feb 3, 2023

Uh oh!

13584452567 commented Feb 4, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

13584452567 commented Mar 1, 2023

Uh oh!

ophub commented Mar 1, 2023

Uh oh!

13584452567 commented Mar 1, 2023

Uh oh!

ophub commented Mar 1, 2023

Uh oh!

ophub commented Mar 1, 2023

Uh oh!

13584452567 commented Mar 1, 2023

Uh oh!

13584452567 commented Mar 1, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ophub commented Mar 1, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ophub commented Mar 1, 2023

Uh oh!

13584452567 commented Mar 1, 2023

Uh oh!

ophub commented Mar 1, 2023

Uh oh!

ophub commented Mar 1, 2023

Uh oh!

13584452567 commented Mar 1, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

13584452567 commented Mar 15, 2023

Uh oh!

phcl1998 commented Mar 15, 2023

Uh oh!

phcl1998 commented Mar 21, 2023 • edited by ophub Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

yifengyou commented Mar 21, 2023

Uh oh!

13584452567 commented Mar 22, 2023

Uh oh!

13584452567 commented Mar 22, 2023

Uh oh!

yifengyou commented Mar 23, 2023

Uh oh!

13584452567 commented Mar 23, 2023

Uh oh!

dos7lo commented Apr 7, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ophub commented Feb 1, 2023 •

edited

Loading

ophub commented Feb 2, 2023 •

edited

Loading

13584452567 commented Feb 4, 2023 •

edited

Loading

13584452567 commented Mar 1, 2023 •

edited

Loading

ophub commented Mar 1, 2023 •

edited

Loading

13584452567 commented Mar 1, 2023 •

edited

Loading

phcl1998 commented Mar 21, 2023 •

edited by ophub

Loading

dos7lo commented Apr 7, 2023 •

edited

Loading

Lasius-alienus commented Jul 9, 2023 •

edited by ophub

Loading

Lasius-alienus commented Jul 17, 2023 •

edited

Loading