Toybrick

标题: 烧写新固件debian,一直停留在loader模式,无法启... [打印本页]

作者: cr7jj    时间: 2020-2-25 09:59
标题: 烧写新固件debian,一直停留在loader模式,无法启...
烧写新固件debian(12.05)成功了,一直停留在loader模式,无法启动,请问如何解决。


作者: cr7jj    时间: 2020-2-25 10:01
烧写新固件debian(12.05)成功了,一直停留在loader模式,无法启动,请问如何解决。


作者: jefferyzhang    时间: 2020-2-25 10:18
1. 板子是哪块?
2. 烧完手动给板子重新上电后能开机么?
作者: cr7jj    时间: 2020-2-25 11:07
jefferyzhang 发表于 2020-2-25 10:18
1. 板子是哪块?
2. 烧完手动给板子重新上电后能开机么?

我用的是rk3399pro,烧录fedora可以,但是烧写新固件debian(12.05)成功了,一直停留在loader模式,无法启动,重新上电也是不能开机
作者: jefferyzhang    时间: 2020-2-25 11:10
3399pro evb么?
不是toybrick的板子是无法用toybrick的固件的。
作者: cr7jj    时间: 2020-2-25 11:10
jefferyzhang 发表于 2020-2-25 10:18
1. 板子是哪块?
2. 烧完手动给板子重新上电后能开机么?
  1. 这是开机log

  2. Connecting to COM3...
  3. Connected.

  4. |DDR Version 1.24 20191016
  5. In
  6. soft reset
  7. SRX
  8. Channel 0: LPDDR3, 800MHz
  9. CS = 0
  10. MR0=0x58
  11. MR1=0x58
  12. MR2=0x58
  13. MR3=0x58
  14. MR4=0x3
  15. MR5=0x1
  16. MR6=0x5
  17. MR7=0x0
  18. MR8=0x1F
  19. MR9=0x1F
  20. MR10=0x1F
  21. MR11=0x1F
  22. MR12=0x1F
  23. MR13=0x1F
  24. MR14=0x1F
  25. MR15=0x1F
  26. MR16=0x1F
  27. Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB
  28. Channel 1: LPDDR3, 800MHz
  29. CS = 0
  30. MR0=0x58
  31. MR1=0x58
  32. MR2=0x58
  33. MR3=0x58
  34. MR4=0x2
  35. MR5=0x1
  36. MR6=0x5
  37. MR7=0x0
  38. MR8=0x1F
  39. MR9=0x1F
  40. MR10=0x1F
  41. MR11=0x1F
  42. MR12=0x1F
  43. MR13=0x1F
  44. MR14=0x1F
  45. MR15=0x1F
  46. MR16=0x1F
  47. Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB
  48. 256B stride
  49. ch 0 ddrconfig = 0x101, ddrsize = 0x20
  50. ch 1 ddrconfig = 0x101, ddrsize = 0x20
  51. pmugrf_os_reg[2] = 0x3280D280, stride = 0x9
  52. OUT
  53. Boot1: 2019-03-14, version: 1.19
  54. CPUId = 0x0
  55. ChipType = 0x10, 309
  56. SdmmcInit=2 0
  57. BootCapSize=100000
  58. UserCapSize=15028MB
  59. FwPartOffset=2000 , 100000
  60. mmc0:cmd8,20
  61. mmc0:cmd5,20
  62. mmc0:cmd55,20
  63. mmc0:cmd1,20
  64. mmc0:cmd8,20
  65. mmc0:cmd5,20
  66. mmc0:cmd55,20
  67. mmc0:cmd1,20
  68. mmc0:cmd8,20
  69. mmc0:cmd5,20
  70. mmc0:cmd55,20
  71. mmc0:cmd1,20
  72. SdmmcInit=0 1
  73. StorageInit ok = 78524
  74. SecureMode = 0
  75. SecureInit read PBA: 0x4
  76. SecureInit read PBA: 0x404
  77. SecureInit read PBA: 0x804
  78. SecureInit read PBA: 0xc04
  79. SecureInit read PBA: 0x1004
  80. SecureInit read PBA: 0x1404
  81. SecureInit read PBA: 0x1804
  82. SecureInit read PBA: 0x1c04
  83. SecureInit ret = 0, SecureMode = 0
  84. atags_set_bootdev: ret:(0)
  85. GPT part:  0, name:            uboot, start:0x2000, size:0x2000
  86. GPT part:  1, name:            trust, start:0x4000, size:0x2000
  87. GPT part:  2, name:       boot_linux, start:0x6000, size:0x30000
  88. GPT part:  3, name:           rootfs, start:0x36000, size:0x1d23fdf
  89. find part:uboot OK. first_lba:0x2000.
  90. find part:trust OK. first_lba:0x4000.
  91. LoadTrust Addr:0x4000
  92. No find bl30.bin
  93. Load uboot, ReadLba = 2000
  94. Load OK, addr=0x200000, size=0xf4324
  95. RunBL31 0x40000
  96. NOTICE:  BL31: v1.3(debug):42583b6
  97. NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
  98. NOTICE:  BL31: Rockchip release version: v1.1
  99. INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
  100. INFO:    Using opteed sec cpu_context!
  101. INFO:    boot cpu mask: 0
  102. INFO:    plat_rockchip_pmu_init(1190): pd status 3e
  103. INFO:    BL31: Initializing runtime services
  104. INFO:    BL31: Initializing BL32
  105. INF [0x0] TEE-CORE:init_primary_helper:337: Initializing (1.1.0-230-g6c76e8a9 #191 Mon Nov 18 07:00:24 UTC 2019 aarch64)

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

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


  111. U-Boot 2017.09-00949-g4fe38bf57c (Nov 28 2019 - 17:42:13 +0800)

  112. Model: Rockchip RK3399 Evaluation Board
  113. PreSerial: 2
  114. DRAM:  2 GiB
  115. Sysmem: init
  116. Relocation Offset is: 7dbd0000
  117. Using default environment

  118. dwmmc@fe320000: 1, sdhci@fe330000: 0
  119. Bootdev(atags): mmc 0
  120. MMC0: HS400, 150Mhz
  121. PartType: EFI
  122. rockchip_get_boot_mode: Could not found misc partition
  123. boot mode: normal
  124. init_resource_list: failed to get boot part, ret=-1
  125. init_resource_list: failed to get resource part, ret=-1
  126. Read kernel dtb failed, ret=-19
  127. Model: Rockchip RK3399 Evaluation Board
  128. rockchip_set_serialno: could not find efuse device
  129. toybrick_SnMacAc_check read sn id fail
  130. toybrick_SnMacAc_check read mac id fail
  131. toybrick_SnMacAc_check read ac id fail
  132. toybrick_SnMacAc_check read sn_mac_ac fail
  133. toybrick_SnMacAc_check goto loader
  134. RKUSB: LUN 0, dev 0, hwpart 0, sector 0x0, count 0x1d5a000
复制代码

作者: jefferyzhang    时间: 2020-2-25 11:12
非Toybrick板子我们无法帮你解决。
请联系提供方处理
作者: cr7jj    时间: 2020-2-25 11:12
jefferyzhang 发表于 2020-2-25 11:10
3399pro evb么?
不是toybrick的板子是无法用toybrick的固件的。

是用你们的toybrickrk3399pro开发板
作者: cr7jj    时间: 2020-2-25 11:18
jefferyzhang 发表于 2020-2-25 11:12
非Toybrick板子我们无法帮你解决。
请联系提供方处理

就是用你们官方的toybrick rk3399Pro 开发板,烧录fedora可以正常启动,但是烧录你们提供最新的Debian固件不能正常启动
作者: addy    时间: 2020-2-25 11:24
请把开发板的产品名称,产品型号和SN发给我们确认下(位于包装盒背面的标签上)
作者: cr7jj    时间: 2020-2-25 11:28
addy 发表于 2020-2-25 11:24
请把开发板的产品名称,产品型号和SN发给我们确认下(位于包装盒背面的标签上) ...

名称:TB-RK3399proD   型号:T331020116D  SN:TD033101190501038
作者: addy    时间: 2020-2-25 11:41
请问,你是否有对EMMC做个全盘格式化或清存储的操作?
如果没有,请按主控芯片旁边的maskrom按键,让系统进maskrommos在烧写固件试试?
作者: cr7jj    时间: 2020-2-25 11:49
addy 发表于 2020-2-25 11:41
请问,你是否有对EMMC做个全盘格式化或清存储的操作?
如果没有,请按主控芯片旁边的maskrom按键,让系统进 ...

我试过在maskrom模式下烧写固件成功,烧录完就变成loader模式,还是不能正常启动
作者: addy    时间: 2020-2-25 14:23
如果每次启动都出现以下几行LOGO,那就是emmc的vendor分区被你误删了,需要返厂维修:
137.toybrick_SnMacAc_check read sn id fail
138.toybrick_SnMacAc_check read mac id fail
139.toybrick_SnMacAc_check read ac id fail
140.toybrick_SnMacAc_check read sn_mac_ac fail

141.toybrick_SnMacAc_check goto loader

作者: cr7jj    时间: 2020-2-25 15:32
本帖最后由 cr7jj 于 2020-2-25 15:34 编辑
addy 发表于 2020-2-25 14:23
如果每次启动都出现以下几行LOGO,那就是emmc的vendor分区被你误删了,需要返厂维修:
137.toybrick_SnMacA ...

我下载fedora启动都没有出现以下几行LOGO,可以正常使用,只有Debian出现这个问题,而且我只烧录linux单系统
作者: lll138139    时间: 2020-3-24 16:10
cr7jj 发表于 2020-2-25 15:32
我下载fedora启动都没有出现以下几行LOGO,可以正常使用,只有Debian出现这个问题,而且我只烧录linux单系 ...

老哥,请问解决了么?我这里也遇到了这个问题
作者: zzmher    时间: 2020-4-3 00:00
我也是这个情况,烧写完了,还是loader状态,启动不了,前面烧写双系统是可以正常启动的
作者: wangqihong    时间: 2020-4-15 15:15
我也是请问怎么解决的啊
作者: vincent911001    时间: 2020-4-15 17:21
本帖最后由 vincent911001 于 2020-4-16 17:51 编辑

Hi,

I am having exactly the same problem too.(Fedora is also working nicely on my board)
[attach]967[/attach]


  1. DDR Version 1.24 20191016
  2. In
  3. Channel 0: LPDDR3, 800MHz
  4. CS = 0
  5. MR0=0x58
  6. MR1=0x58
  7. MR2=0x58
  8. MR3=0x58
  9. MR4=0x2
  10. MR5=0x1
  11. MR6=0x5
  12. MR7=0x0
  13. MR8=0x1F
  14. MR9=0x1F
  15. MR10=0x1F
  16. MR11=0x1F
  17. MR12=0x1F
  18. MR13=0x1F
  19. MR14=0x1F
  20. MR15=0x1F
  21. MR16=0x1F
  22. Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB
  23. Channel 1: LPDDR3, 800MHz
  24. CS = 0
  25. MR0=0x58
  26. MR1=0x58
  27. MR2=0x58
  28. MR3=0x58
  29. MR4=0x3
  30. MR5=0x1
  31. MR6=0x5
  32. MR7=0x0
  33. MR8=0x1F
  34. MR9=0x1F
  35. MR10=0x1F
  36. MR11=0x1F
  37. MR12=0x1F
  38. MR13=0x1F
  39. MR14=0x1F
  40. MR15=0x1F
  41. MR16=0x1F
  42. Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB
  43. 256B stride
  44. ch 0 ddrconfig = 0x101, ddrsize = 0x20
  45. ch 1 ddrconfig = 0x101, ddrsize = 0x20
  46. pmugrf_os_reg[2] = 0x3280D280, stride = 0x9
  47. OUT
  48. Boot1: 2019-03-14, version: 1.19
  49. CPUId = 0x0
  50. ChipType = 0x10, 246
  51. SdmmcInit=2 0
  52. BootCapSize=100000
  53. UserCapSize=15028MB
  54. FwPartOffset=2000 , 100000
  55. mmc0:cmd8,20
  56. mmc0:cmd5,20
  57. mmc0:cmd55,20
  58. mmc0:cmd1,20
  59. mmc0:cmd8,20
  60. mmc0:cmd5,20
  61. mmc0:cmd55,20
  62. mmc0:cmd1,20
  63. mmc0:cmd8,20
  64. mmc0:cmd5,20
  65. mmc0:cmd55,20
  66. mmc0:cmd1,20
  67. SdmmcInit=0 1
  68. StorageInit ok = 77645
  69. SecureMode = 0
  70. SecureInit read PBA: 0x4
  71. SecureInit read PBA: 0x404
  72. SecureInit read PBA: 0x804
  73. SecureInit read PBA: 0xc04
  74. SecureInit read PBA: 0x1004
  75. SecureInit read PBA: 0x1404
  76. SecureInit read PBA: 0x1804
  77. SecureInit read PBA: 0x1c04
  78. SecureInit ret = 0, SecureMode = 0
  79. atags_set_bootdev: ret:(0)
  80. GPT part:  0, name:            uboot, start:0x2000, size:0x2000
  81. GPT part:  1, name:            trust, start:0x4000, size:0x2000
  82. GPT part:  2, name:       boot_linux, start:0x6000, size:0x30000
  83. GPT part:  3, name:           rootfs, start:0x36000, size:0x1d23fdf
  84. find part:uboot OK. first_lba:0x2000.
  85. find part:trust OK. first_lba:0x4000.
  86. LoadTrust Addr:0x4000
  87. No find bl30.bin
  88. Load uboot, ReadLba = 2000
  89. Load OK, addr=0x200000, size=0xf4324
  90. RunBL31 0x40000
  91. NOTICE:  BL31: v1.3(debug):42583b6
  92. NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
  93. NOTICE:  BL31: Rockchip release version: v1.1
  94. INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
  95. INFO:    Using opteed sec cpu_context!
  96. INFO:    boot cpu mask: 0
  97. INFO:    plat_rockchip_pmu_init(1190): pd status 3e
  98. INFO:    BL31: Initializing runtime services
  99. INFO:    BL31: Initializing BL32
  100. INF [0x0] TEE-CORE:init_primary_helper:337: Initializing (1.1.0-230-g6c76e8a9 #191 Mon Nov 18 07:00:24 UTC 2019 aarch64)

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

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


  106. U-Boot 2017.09-00949-g4fe38bf57c (Nov 28 2019 - 17:42:13 +0800)

  107. Model: Rockchip RK3399 Evaluation Board
  108. PreSerial: 2
  109. DRAM:  2 GiB
  110. Sysmem: init
  111. Relocation Offset is: 7dbd0000
  112. Using default environment

  113. dwmmc@fe320000: 1, sdhci@fe330000: 0
  114. Bootdev(atags): mmc 0
  115. MMC0: HS400, 150Mhz
  116. PartType: EFI
  117. rockchip_get_boot_mode: Could not found misc partition
  118. boot mode: None
  119. init_resource_list: failed to get boot part, ret=-1
  120. init_resource_list: failed to get resource part, ret=-1
  121. Read kernel dtb failed, ret=-19
  122. Model: Rockchip RK3399 Evaluation Board
  123. rockchip_set_serialno: could not find efuse device
  124. toybrick_SnMacAc_check read sn id fail
  125. toybrick_SnMacAc_check read ac id fail
  126. toybrick_SnMacAc_check read sn_mac_ac fail
  127. toybrick_SnMacAc_check goto loader
  128. RKUSB: LUN 0, dev 0, hwpart 0, sector 0x0, count 0x1d5a000
  129. -
复制代码


Please advise.


Thanks


作者: cr7jj    时间: 2020-4-30 08:53
用fedora的uboot.img就可以启动
作者: penguin    时间: 2020-6-16 14:19
我也遇到了这个问题。

作者: Ptolemaeus    时间: 2021-3-11 15:21
启动文件坏了?
作者: wanqieddy    时间: 2022-1-18 14:23
我现成也遇到这个问题
作者: addy    时间: 2022-1-18 15:14
打印那几行LOG表示,这块板子没有烧写序列号。就算用fedora的uboot能起来,也可能有问题。
uboot读不到序列号的原因有几种:
1. 这块板子不是toybrick板子
2. 板子的emmc曾经被擦除过,vendor的内容也被清空。





欢迎光临 Toybrick (https://t.rock-chips.com/) Powered by Discuz! X3.3