Toybrick

系统启动卡在uboot

alan1996

中级会员

积分
270
发表于 2022-3-14 09:49:56    查看: 3995|回复: 4 | [复制链接]    打印 | 显示全部楼层
新买的TB RK3568开发板,第一次启动正常进预烧录得debian10系统,然后按照wiki教程烧录RK官方的Android固件,烧录工具提示烧录成功,但是系统卡在了uboot,之后再尝试烧录debian系统,还是同样的情况,uboot串口调试信息如下,请帮忙分析一下,谢谢
U-Boot SPL board init
U-Boot SPL 2017.09-ga1f6fc00a0-210413 #ldq (Apr 13 2021 - 11:35:00)
unknown raw ID phN
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2
MMC error: The cmd index is 1, ret is -110
Card did not respond to voltage select!
mmc_init: -95, time 10
spl: mmc init failed with error: -95
Trying to boot from MMC1
SPL: A/B-slot: _a, successful: 0, tries-remain: 7
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256+ OK
## Checking uboot 0x00a00000 ... sha256+ OK
## Checking fdt 0x00b294f8 ... sha256+ OK
## Checking atf-2 0x00068000 ... sha256+ OK
## Checking atf-3 0xfdcd0000 ... sha256+ OK
## Checking atf-4 0xfdcc9000 ... sha256+ OK
## Checking atf-5 0x00066000 ... sha256+ OK
## Checking optee 0x08400000 ... sha256+ OK
Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000)
Total: 220.895 ms

INFO:    Preloader serial: 2
NOTICE:  BL31: v2.3():v2.3-181-gc9a647cae:cl
NOTICE:  BL31: Built : 10:55:41, Oct 18 2021
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    pmu v1 is valid
INFO:    dfs DDR fsp_param[0].freq_mhz= 1560MHz
INFO:    dfs DDR fsp_param[1].freq_mhz= 324MHz
INFO:    dfs DDR fsp_param[2].freq_mhz= 528MHz
INFO:    dfs DDR fsp_param[3].freq_mhz= 780MHz
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    BL31: Initializing runtime services
INFO:    BL31: Initializing BL32
I/TC:
I/TC: OP-TEE version: 3.13.0-515-g7b4275734 #hisping.lin (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05)) #1 Wed Aug  4 07:11:39 UTC 2021 aarch64
I/TC: Primary CPU initializing
I/TC: Primary CPU switching to normal world boot
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0xa00000
INFO:    SPSR = 0x3c9

Model: Rockchip RK3568 Evaluation Board
PreSerial: 2, raw, 0xfe660000
DRAM:  4 GiB
Sysmem: init
Relocation Offset: ed34f000
Relocation fdt: eb9f91d0 - eb9fecd8
CR: M/C/I
Using default environment

dwmmc@fe2b0000: 1, dwmmc@fe2c0000: 2, sdhci@fe310000: 0
Bootdev(atags): mmc 0
MMC0: HS200, 200Mhz
PartType: EFI
boot mode: recovery (misc)
FIT: No fdt blob
boot mode: recovery (misc)
Android 11.0, Build 2021.6, v2
Found DTB in recovery part
DTB: rk-kernel.dtb
HASH(c): OK
ANDROID: fdt overlay OK
I2c0 speed: 100000Hz
vsel-gpios- not found! Error: -2
vdd_cpu init 900000 uV
priv->not_save_power_en is 0x1,RK817_POWER_EN_SAVE0 0x0
PMIC:  RK8090 (on=0x40, off=0x00)
vdd_logic init 900000 uV
vdd_gpu init 900000 uV
vdd_npu init 900000 uV
io-domain: OK
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
fs_set_blk_dev mmc 0:3 fail
boot_linux_read_logo_file logo.bmp fail, len: 1
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
fs_set_blk_dev mmc 0:3 fail
boot_linux_read_logo_file logo.bmp fail, len: 1
Rockchip UBOOT DRM driver version: v1.0.1
VOP have 2 active VP
vp0 have layer nr:3[1 3 5 ], primary plane: 5
vp1 have layer nr:3[0 2 4 ], primary plane: 4
vp2 have layer nr:0[], primary plane: 0
Using display timing dts
dsi@fe060000:  detailed mode clock 132000 kHz, flags[8000000a]
    H: 1080 1095 1097 1127
    V: 1920 1935 1937 1952
bus_format: 100e
VOP update mode to: 1080x1920p0, type: MIPI0 for VP1
VOP VP1 enable Smart0[654x270->654x270@213x825] fmt[2] addr[0xedf04000]
final DSI-Link bandwidth: 880 Mbps x 4
PHY is not locked
u-boot lcd cmd write.generic write fifo is full
failed to write cmd0: -110
failed to send on cmds: -110
disp info 0, type:11, id:0
hdmi@fe0a0000 disconnected
CLK: (sync kernel. arm: enter 816000 KHz, init 816000 KHz, kernel 0N/A)
  apll 1416000 KHz
  dpll 780000 KHz
  gpll 1188000 KHz
  cpll 1000000 KHz
  npll 1200000 KHz
  vpll 660000 KHz
  hpll 24000 KHz
  ppll 200000 KHz
  armclk 1416000 KHz
  aclk_bus 150000 KHz
  pclk_bus 100000 KHz
  aclk_top_high 500000 KHz
  aclk_top_low 400000 KHz
  hclk_top 150000 KHz
  pclk_top 100000 KHz
  aclk_perimid 300000 KHz
  hclk_perimid 150000 KHz
  pclk_pmu 100000 KHz
Net:   eth1: ethernet@fe010000, eth0: ethernet@fe2a0000
Hit key to stop autoboot('CTRL+C'):  0
## Booting FIT Image FIT: No fit blob
FIT: No FIT image
ANDROID: reboot reason: "recovery"
optee api revision: 2.0
TEEC: Reset area[0] info...
TEEC: Reset area[1] info...
Vboot=0, AVB images, AVB verify
TEEC: ree_fs_new_open : no such file. /dirf.db
TEEC: unavailable fd: 0!
TEEC: unavailable fd: 0!
TEEC: unavailable fd: 0!
lib/avb/libavb_user/avb_ops_user.c: trusty_read_lock_state failed
Error determining whether device is unlocked.
read_is_device_unlocked() ops returned that device is UNLOCKED
avb_footer.c:41: ERROR: Footer magic is incorrect.
avb_vbmeta_image.c:65: ERROR: Magic is incorrect.
avb_slot_verify.c:773: ERROR: recovery: Error verifying vbmeta image: invalid vbmeta header
Verify recovery with vbmeta.
avb_slot_verify.c:762: ERROR: vbmeta: Error verifying vbmeta image: OK_NOT_SIGNED
TEEC: ree_fs_new_open : no such file. /dirf.db
TEEC: unavailable fd: 0!
TEEC: unavailable fd: 0!
TEEC: unavailable fd: 0!
lib/avb/libavb_user/avb_ops_user.c: trusty_read_rollback_index failedavb_slot_verify.c:883: ERROR: vbmeta: Error getting rollback index for location.
AVB verify failed
Android boot failed, error -1.
MMC error: The cmd index is 1, ret is -110
Card did not respond to voltage select!
mmc_init: -95, time 9
switch to partitions #0, OK
mmc0(part 0) is current device
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
MMC error: The cmd index is 1, ret is -110
Card did not respond to voltage select!
mmc_init: -95, time 9
** Bad device mmc 1 **
MMC error: The cmd index is 1, ret is -110
Card did not respond to voltage select!
mmc_init: -95, time 9
** Bad device mmc 1 **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
starting USB...
Bus dwc3@fcc00000: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus dwc3@fd000000: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus usb@fd800000: USB EHCI 1.00
Bus usb@fd840000: USB OHCI 1.0
Bus usb@fd880000: USB EHCI 1.00
Bus usb@fd8c0000: USB OHCI 1.0
scanning bus dwc3@fcc00000 for devices... 1 USB Device(s) found
scanning bus dwc3@fd000000 for devices... 1 USB Device(s) found
scanning bus usb@fd800000 for devices... 1 USB Device(s) found
scanning bus usb@fd840000 for devices... 1 USB Device(s) found
scanning bus usb@fd880000 for devices... 1 USB Device(s) found
scanning bus usb@fd8c0000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
ethernet@fe010000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
phy_startup() failed: -110FAILED: -110ethernet@fe2a0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
phy_startup() failed: -110FAILED: -110missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-ce-5a-63-6d-3a-d4
ethernet@fe010000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
phy_startup() failed: -110FAILED: -110ethernet@fe2a0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
phy_startup() failed: -110FAILED: -110missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
ethernet@fe010000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
phy_startup() failed: -110FAILED: -110ethernet@fe2a0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
phy_startup() failed: -110FAILED: -110missing environment variable: bootfile


回复

使用道具 举报

395876134

版主

积分
1043
发表于 2022-3-16 17:53:10 | 显示全部楼层
请问android固件用哪个?
回复

使用道具 举报

395876134

版主

积分
1043
发表于 2022-3-16 17:55:32 | 显示全部楼层
回复

使用道具 举报

alan1996

中级会员

积分
270
 楼主| 发表于 2022-3-24 14:29:10 | 显示全部楼层
395876134 发表于 2022-3-16 17:55
https://eyun.baidu.com/s/3pM3uxF9#sharelink/path=%2F请用上头的固件

寄给厂商修了,使板子本身的问题,现在可以正常启动了
回复

使用道具 举报

wangyb@zhejiang

注册会员

积分
76
发表于 2022-11-29 14:20:38 | 显示全部楼层
alan1996 发表于 2022-3-24 14:29
寄给厂商修了,使板子本身的问题,现在可以正常启动了

我跟你遇到的是相同的问题,寄给厂家给你反馈的是什么问题?
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

产品中心 购买渠道 开源社区 Wiki教程 资料下载 关于Toybrick


快速回复 返回顶部 返回列表