收起左侧

rock5t,安装飞牛os1.1.31到tf卡和nvme硬盘都不能启动,屏幕无显示,原1.1.19版没问题

16
回复
301
查看
[ 复制链接 ]

1

主题

6

回帖

0

牛值

江湖小虾

2026-4-29 08:38:00 显示全部楼层 阅读模式
如题,rock5t新买的,12G内存,安装飞牛os1.1.31到tf卡和nvme硬盘都不能启动,屏幕无显示,原1.1.19版没问题
收藏
送赞
分享

0

主题

37

回帖

0

牛值

飞牛官方人员

2026-4-29 10:26:06 显示全部楼层
你好 请问你是刷的哪个文件?通过什么方式刷入的。我们这边尝试刷了5t和三合一固件均能启动
已经改成nvme启动,之前1.1.19版本用rufers和DD写入nvme硬盘都可以启动,最新的5t和三合一版都不能启动,包括TF卡和nvme,12G内存版本  详情 回复
2026-4-29 20:27
你好,可以接入香橙派5 plus吗?和最近官方兼容的瑞莎 Radxa ROCK 5B Plus类似的一块板子  详情 回复
2026-4-29 10:45

0

主题

6

回帖

0

牛值

江湖小虾

2026-4-29 10:45:00 显示全部楼层
fn_tom 发表于 2026-4-29 10:26
你好 请问你是刷的哪个文件?通过什么方式刷入的。我们这边尝试刷了5t和三合一固件均能启动 ...

你好,可以接入香橙派5 plus吗?和最近官方兼容的瑞莎 Radxa ROCK 5B Plus类似的一块板子

7

主题

9

回帖

0

牛值

江湖小虾

2026-4-29 10:58:10 显示全部楼层
要接串口看看,什么信息哦都没有,别人帮不了你

1

主题

3

回帖

0

牛值

江湖小虾

2026-4-29 11:40:09 显示全部楼层
是否下载错了版本,飞牛arm下载页面有两个5t

1

主题

6

回帖

0

牛值

江湖小虾

2026-4-29 20:27:35 楼主 显示全部楼层
fn_tom 发表于 2026-4-29 10:26
你好 请问你是刷的哪个文件?通过什么方式刷入的。我们这边尝试刷了5t和三合一固件均能启动 ...

已经改成nvme启动,之前1.1.19版本用rufers和DD写入nvme硬盘都可以启动,最新的5t和三合一版都不能启动,包括TF卡和nvme,12G内存版本

1

主题

6

回帖

0

牛值

江湖小虾

2026-4-29 20:57:29 楼主 显示全部楼层

DDR b8ce94f14b cym 25/09/26-15:48.05,fwver: v1.20
ch0 ttot6
ch1 ttot6
ch2 ttot6
ch3 ttot6
ch0 ttot7
LPDDR5, 2400MHz
channel[0] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=3072MB
ch1 ttot7
channel[1] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=3072MB
ch2 ttot7
channel[2] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=3072MB
ch3 ttot7
channel[3] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=3072MB
Manufacturer ID:0x13
DQS rds:h1,l0
CH0 RX Vref:23.8%, TX Vref:22.0%,23.0%
DQ rds:h2 l1 h7 l0 h1 l0 h1 h2, h1 l1 h1 h1 l1 l3 l1 l0

DQS rds:l0,h2
CH1 RX Vref:23.4%, TX Vref:22.0%,23.0%
DQ rds:h4 l0 h1 l0 h4 h7 l0 l0, l3 h2 h1 l0 l2 h2 h3 l0

DQS rds:h1,h1
CH2 RX Vref:27.1%, TX Vref:21.0%,21.0%
DQ rds:l0 h6 h1 h1 h1 l0 l1 l3, h7 h4 h5 l2 l2 h1 l0 l0

DQS rds:l0,l0
CH3 RX Vref:27.1%, TX Vref:21.0%,24.0%
DQ rds:l0 l0 l1 h1 h3 l0 h2 l0, l0 h4 l0 l0 h5 h1 h1 h1

stride=0x2, ddr_config=0x6
hash ch_mask0-1 0x20 0x40, bank_mask0-3 0x0 0x2400 0x44800 0x89000, rank_mask0 0x2000
change to F1: 534MHz
ch0 ttot6
ch1 ttot6
ch2 ttot6
ch3 ttot6
change to F2: 1320MHz
ch0 ttot8
ch1 ttot8
ch2 ttot8
ch3 ttot8
change to F3: 1968MHz
ch0 ttot6
ch1 ttot6
ch2 ttot6
ch3 ttot6
change to F0: 2400MHz
ch0 ttot7
ch1 ttot7
ch2 ttot7
ch3 ttot7
out
U-Boot SPL board init
U-Boot SPL rk2410-2017.09-62-6c807ac-g063ee5b #runner (Jan 13 2026 - 06:15:10)
sfc cmd=03H(6BH-x4)
Trying to boot from MMC2
MMC: no card present
mmc_init: -123, time 0
spl: mmc init failed with error: -123
Trying to boot from MTD2
part_get_info_efi: *** ERROR: Invalid GPT ***
part_get_info_efi: *** ERROR: Invalid Backup GPT ***
part_get_info_efi: *** ERROR: Invalid GPT ***
part_get_info_efi: *** ERROR: Invalid Backup GPT ***
part_get_info_efi: *** ERROR: Invalid GPT ***
part_get_info_efi: *** ERROR: Invalid Backup GPT ***
Trying fit image at 0x4000 sector

Verified-boot: 0

Checking atf-1 0x00040000 ... sha256(af59234162...) + OK

Checking uboot 0x00200000 ... sha256(ea289f79d8...) + OK

Checking fdt 0x00326c90 ... sha256(4bd41718f7...) + OK

Checking atf-2 0xff100000 ... sha256(488c757001...) + OK

Checking atf-3 0x000f0000 ... sha256(b621eea76c...) + OK

Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000)
Total: 497.520/882.609 ms

INFO: Preloader serial: 2
NOTICE: BL31: v2.3():v2.3-942-g98eaeb2f3:derrick.huang, fwver: v1.53
NOTICE: BL31: Built : 12:10:56, Aug 25 2025
INFO: spec: 0x1
INFO: code: 0x88
INFO: customer demand: 0x0
INFO: ext 32k is not valid
INFO: ddr: stride-en 4CH
INFO: GICv3 without legacy support detected.
INFO: ARM GICv3 driver initialized in EL3
INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0
INFO: l3 cache partition cfg-0
INFO: system boots from cpu-hwid-0
INFO: bypass memory repair
INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
INFO: dfs DDR fsp_params[0].freq_mhz= 2400MHz
INFO: dfs DDR fsp_params[1].freq_mhz= 534MHz
INFO: dfs DDR fsp_params[2].freq_mhz= 1320MHz
INFO: dfs DDR fsp_params[3].freq_mhz= 1968MHz
INFO: BL31: Initialising Exception Handling Framework
INFO: BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR: Error initializing runtime service opteed_fast
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
usb dr_mode not found

U-Boot rk2410-2017.09-62-6c807ac-g063ee5b #runner (Jan 13 2026 - 06:15:08 +0000)

Model: Radxa ROCK 5T
MPIDR: 0x0
PreSerial: 2, raw, 0xfeb50000
DRAM: 12 GiB
Sysmem: init
Relocation Offset: eda38000
Relocation fdt: eb9f7960 - eb9fecd0
CR: M/C/I
usb dr_mode not found
Using default environment

DM: v2
RESC: No bootdev
Failed to load DTB, ret=-2
No valid DTB, ret=-22
Failed to get kernel dtb, ret=-22
Checking variant: rockchip,rk3588, hw_id 0x3ff not in range [0x12c, 0x17c], bom_id 0xf not in range [0x0, 0xffffffff]
Found matching variant rockchip,rk3588 for hw_id 0x3ff and bom_id 0xf setting fdtfile to rockchip/rk3588-rock-5t.dtb
Model: Radxa ROCK 5T
[Vendor ERROR]:Invalid boot device type(0)

Error: Can't overwrite "ethaddr"

Error inserting "ethaddr" variable, errno=1

Error: Can't overwrite "eth1addr"

Error inserting "eth1addr" variable, errno=1

[Vendor ERROR]:Invalid boot device type(0)
rockchip_set_ethaddr: vendor_storage_write failed -19
[Vendor ERROR]:Invalid boot device type(0)
mmc@fe2c0000: 1, mmc@fe2e0000: 0
Card did not respond to voltage select!
mmc_init: -95, time 13
JEDEC id bytes: 0b, 40, 18
SF: Detected sfc_nor with page size 256 Bytes, erase size 4 KiB, total 16 MiB
Bootdev(atags): mtd 2
starting USB...
Bus usb@fc800000: USB EHCI 1.00
Bus usb@fc840000: USB OHCI 1.0
Bus usb@fc880000: USB EHCI 1.00
Bus usb@fc8c0000: USB OHCI 1.0
Bus usb@fcd00000: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fc800000 for devices... 2 USB Device(s) found
scanning bus usb@fc840000 for devices... 1 USB Device(s) found
scanning bus usb@fc880000 for devices... 1 USB Device(s) found
scanning bus usb@fc8c0000 for devices... 1 USB Device(s) found
scanning bus usb@fcd00000 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
No usb mass storage found
No bootdev
dev_desc is NULL!
boot mode: None
No bootdev
CLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kernel 0N/A)
b0pll 24000 KHz
b1pll 24000 KHz
lpll 24000 KHz
v0pll 24000 KHz
aupll 24000 KHz
cpll 1500000 KHz
gpll 1188000 KHz
npll 24000 KHz
ppll 1100000 KHz
aclk_center_root 702000 KHz
pclk_center_root 100000 KHz
hclk_center_root 396000 KHz
aclk_center_low_root 500000 KHz
aclk_top_root 750000 KHz
pclk_top_root 100000 KHz
aclk_low_top_root 396000 KHz

Unknown partition table type 0

PartType:
No bootdev
Net: No ethernet found.
Hit Ctrl+C key in 0 seconds to stop autoboot...

Device 0: unknown device
MMC: no card present
mmc_init: -123, time 0
pcie@fe150000: PCIe Linking... LTSSM is 0x0
pcie@fe150000: PCIe Linking... LTSSM is 0x6
pcie@fe150000: PCIe Linking... LTSSM is 0x1
pcie@fe150000: PCIe Linking... LTSSM is 0x210023
pcie@fe150000: PCIe Link up, LTSSM is 0x230011
pcie@fe150000: PCIE-0: Link up (Gen3-x2, Bus0)
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x1
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x1
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x1
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe Linking... LTSSM is 0x0
pcie@fe160000: PCIe-2 Link Fail
the always on regulator (vcc3v3-pcie30) should never be disabled!

Device 0: Vendor: 0x144d Rev: 6L6QCXZ7 Prod: S372NB0K808751
Type: Hard Disk
Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
Could not find misc partition
ANDROID: reboot reason: "(none)"
Not AVB images, AVB skip
android_image_load_by_partname: Can't find part: boot
Android image load failed
Android boot failed, error -1.
Scanning nvme 0:1...
Found U-Boot script /boot.scr
4796 bytes read in 1 ms (4.6 MiB/s)

Executing script at 00500000

Boot script loaded from nvme 0:1
127 bytes read in 1 ms (124 KiB/s)
32926208 bytes read in 1749 ms (18 MiB/s)
128945 bytes read in 48 ms (2.6 MiB/s)
Fdt Ramdisk skip relocation
No misc partition

Flattened Device Tree blob at 0x08300000

Booting using the fdt blob at 0x08300000
the always on regulator (vcc5v0-host-regulator) should never be disabled!
rockchip_usb2phy_power_off: Failed to set VBus supply
PHY: Failed to power off host-port: -13.
the always on regulator (vcc5v0-host-regulator) should never be disabled!
rockchip_usb2phy_power_off: Failed to set VBus supply
PHY: Failed to power off host-port: -13.
reserving fdt memory region: addr=8300000 size=85000
Using Device Tree in place at 0000000008300000, end 0000000008387fff
can't found rockchip,drm-logo, use rockchip,fb-logo
WARNING: could not set reg FDT_ERR_BADOFFSET.
failed to reserve fb-loader-logo memory

reserved-memory:

shmem@10f000: addr=10f000 size=100
Adding bank: 0x00200000 - 0xf0000000 (size: 0xefe00000)
Adding bank: 0x100000000 - 0x300000000 (size: 0x200000000)
Adding bank: 0x4f0000000 - 0x500000000 (size: 0x10000000)
Total: 10482.195/10495.95 ms

Starting kernel ...

1

主题

6

回帖

0

牛值

江湖小虾

2026-4-29 21:15:47 楼主 显示全部楼层

到启动内核就卡住了,hdmi屏幕是一直没有输出的

你好。需要把 spi nor 里面的 uboot 擦除掉。可参考瑞莎官网的教程  详情 回复
7 天前

0

主题

37

回帖

0

牛值

飞牛官方人员

文5234 发表于 2026-4-29 21:15
到启动内核就卡住了,hdmi屏幕是一直没有输出的

你好。需要写入我们提供的uboot到spi nor可参考瑞莎官网的教程
请问提供的UBOOT在哪下载,还是重新刷写下瑞莎的UBOOT?  详情 回复
7 天前

1

主题

6

回帖

0

牛值

江湖小虾

7 天前 楼主 显示全部楼层
fn_tom 发表于 2026-4-30 10:03
你好。需要写入我们提供的uboot到spi nor可参考瑞莎官网的教程

请问提供的UBOOT在哪下载,还是重新刷写下瑞莎的UBOOT?

0

主题

37

回帖

0

牛值

飞牛官方人员

刷这个

本帖子中包含更多资源

您需要 登录 才可以下载或查看,没有账号?立即注册

x
同样的板子,然后刷了这个spi,只能TF卡启动,nvme启动不了。  详情 回复
4 天前
把这个u-boot刷入spi后,TF卡安装的1.1.31版可以启动了,但是不能从nvme启动了,这个要怎么设置,还是要个同版本专用的从nvme启动的u-boot?希望能提供个,谢谢  详情 回复
7 天前
有个疑问,这种uboot是必须要刷的吗?之前没有刷的时候也能启动,但是ota后就失联了,跟楼主一样的卡到start kernel了。如果是必须的话,建议公司下载列表地方可以放下相关的wiki文档还有uboot的下载地址。  详情 回复
7 天前

0

主题

8

回帖

0

牛值

江湖小虾


有个疑问,这种uboot是必须要刷的吗?之前没有刷的时候也能启动,但是ota后就失联了,跟楼主一样的卡到start kernel了。如果是必须的话,建议公司下载列表地方可以放下相关的wiki文档还有uboot的下载地址。

1

主题

6

回帖

0

牛值

江湖小虾

7 天前 楼主 显示全部楼层

把这个u-boot刷入spi后,TF卡安装的1.1.31版可以启动了,但是不能从nvme启动了,这个要怎么设置,还是要个同版本专用的从nvme启动的u-boot?希望能提供个,谢谢
兄弟,搞定后**一下啊。我的OTA后也失联了。既然刷spi也没用,我就先不折腾了。  详情 回复
7 天前

0

主题

8

回帖

0

牛值

江湖小虾

文5234 发表于 2026-4-30 22:09
把这个u-boot刷入spi后,TF卡安装的1.1.31版可以启动了,但是不能从nvme启动了,这个要怎么设置,还是要 ...

兄弟,搞定后**一下啊。我的OTA后也失联了。既然刷spi也没用,我就先不折腾了。

0

主题

8

回帖

0

牛值

江湖小虾


同样的板子,然后刷了这个spi,只能TF卡启动,nvme启动不了。
我用TF试过,飞牛相册好像还不支持NPU,immich可以  详情 回复
4 天前

1

主题

6

回帖

0

牛值

江湖小虾

4 天前 楼主 显示全部楼层
Blur 发表于 2026-5-3 22:54
同样的板子,然后刷了这个spi,只能TF卡启动,nvme启动不了。

我用TF试过,飞牛相册好像还不支持NPU,immich可以
应该需要先下载那个 AI 3588的库才行吧  详情 回复
3 天前

0

主题

8

回帖

0

牛值

江湖小虾

文5234 发表于 2026-5-3 23:34
我用TF试过,飞牛相册好像还不支持NPU,immich可以

应该需要先下载那个 AI 3588的库才行吧
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则