Bianbu-LXQt-K3-v4.0 无法使用 Titan 工具写入

使用 “TITANTOOLS FOR LINUX X64 (64-BIT) (APPIMAGE)” 2.2.2-RC 在 Linux下尝试刷写 Bianbu-LXQt-K3-v4.0 (UEFI) 镜像,板卡已在 DFU 模式下且被正确识别,但刷机工具解压镜像后,尝试写入时报如下错误:

请问镜像是否存在问题?

  1. 请将下载的镜像的md5码值发出来一下
  2. 您是在linux实体机还是虚拟机上运行titan工具?
  3. 确保解压目录有足够的空间,以应用不会弹出磁盘空间不足警告为准,如果忽视警告强行解压,会导致解压不完全,烧录报错。可以在设置界面修改解压目录
  4. 请提供烧录报错时完整的串口日志和工具报错截图

您好,我目前在k3开发板尝试烧录uefi镜像,然后titan软件显示成功烧录,但是重新开机f2无法进入界面,软件烧录输出链接
[info] —》Start flashing the device

[info] 执行 fastboot getvar version-brom

[info] 1.0

[info] 执行 fastboot stage factory/FSBL.bin

[info] run fastboot continue

[info] 执行 fastboot getvar version

[info] 0.4

[info] 执行 fastboot oem speed:super-speed

[info] 执行 fastboot stage u-boot.itb

[info] run fastboot continue

[info] 执行 fastboot getvar mtd-size

[info] 8M

[info] 执行 fastboot getvar blk-size

[info] universal

[info] match partition table: [‘partition_{size0}.json’, ‘partition_{size1}.json’]

[info] Start matching partition table: partition_8M.json

[info] Start matching partition table: partition_4M.json

[info] Partition table matching successful: partition_4M.json

[info] Match the original partition table: partition_universal.json

[info] partition match result: partition_4M.json

[info] partition match result: partition_universal.json

[info] fastboot flash mtd partition_4M.json

[info] parse gpt/mtd table okay

[info] fastboot flash bootinfo bootinfo_spinor.bin

[info] fastboot flash fsbl FSBL.bin

[info] fastboot flash env env.bin

[info] fastboot flash esos esos.itb

[info] fastboot flash opensbi fw_dynamic.itb

[info] fastboot flash uboot edk2.itb

[info] fastboot flash gpt partition_universal.json

[info] parse gpt/mtd table okay

[info] fastboot flash env env.bin

[info] fastboot flash bootinfo bootinfo_block.bin

[info] fastboot flash fsbl FSBL.bin

[info] fastboot flash esos esos.itb

[info] fastboot flash opensbi fw_dynamic.itb

[info] fastboot flash uboot edk2.itb

[info] fastboot flash ESP esp.vfat

[info] fastboot flash bootfs bootfs.ext4

[info] fastboot flash rootfs rootfs.ext4

[info] —》Successful flashing!

  1. 你使用的是K3哪种板型?如果是COM260的话,v4.0.0 UEFI固件还有些兼容性问题
  2. 系统可以正常开机进系统吗?
  3. 连接屏幕的方式是dp直连还是转了HUB?

k3-pico-itx开发板,不是com,开机无法进系统,显示屏不亮,但是烧录回u-boot可以正常进界面,链接方式是官方文档里建议的拓展坞,dp转hdmi

sys: 0x10000200
try sd…
bm:3
ERROR: CMD8
ERROR: sd f! l:90
bm:4
nor m:0xef d:0x6017
j…

U-Boot SPL 2022.10 (Apr 30 2026 - 11:07:27 +0800)
DDR Part Number: MT62F4G32D8DV, Size: 16384MB, Data Rate: 6400MT/s
DDR quick boot consume 9ms
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03041001 I0
PROGRESS CODE: V03051005 I0
PROGRESS CODE: V02010000 I0
PROGRESS CODE: V02011000 I0
PROGRESS CODE: V02011001 I0
PROGRESS CODE: V02010004 I0

PROGRESS CODE: V01040001 I0
PROGRESS CODE: V02010000 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02070000 I0
PROGRESS CODE: V02070003 I0
PROGRESS CODE: V02070004 I0
PROGRESS CODE: V02020000 I0
PROGRESS CODE: V02020004 I0
PROGRESS CODE: V02020003 I0
PROGRESS CODE: V02020000 I0
PROGRESS CODE: V02020004 I0
PROGRESS CODE: V02020003 I0
PROGRESS CODE: V02020006 I0
PROGRESS CODE: V02020000 I0
PROGRESS CODE: V02020004 I0
PROGRESS CODE: V02020003 I0
PROGRESS CODE: V02020006 I0
PROGRESS CODE: V02020006 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03040002 I0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V02010000 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02070000 I0
PROGRESS CODE: V02070003 I0
PROGRESS CODE: V02020000 I0
PROGRESS CODE: V02020000 I0
PROGRESS CODE: V02020000 I0
PROGRESS CODE: V02020000 I0
PROGRESS CODE: V02020000 I0
PROGRESS CODE: V02020000 I0
PROGRESS CODE: V03051007 I0
PROGRESS CODE: V03051001 I0
ERROR: C40000002:V03051002 I0 6D33944A-EC75-4855-A54D-809C75241F6C 23FFF870
PROGRESS CODE: V03051001 I0
PROGRESS CODE: V03058000 I0
PROGRESS CODE: V03058001 I0
error: font: glyphs too large to fit on screen.
error: file `/grub/riscv64-efi/bli.mod’ not found.串口结果

请提供下显示器的型号。

试下重新刷固件、换一台显示器或者不接hub让dp直连试下

用uboot固件进入系统后,执行apt install spacemit-ec-firmware安装软件包,然后执行下ectool version看下ec固件版本号是多少?