Upgrade Exception of RK3566/RK3568

zyk

If the board RK3566/RK3568 have both Nor Flash and EMMC storage media, and we upgrading firmware miss some steps, it may cause some exceptions such as  system failed to start normally

The following summarizes some exceptions and handling methods for reference:

Download Firmware Fail


R:  Without switching storage media to EMMC, the firmware is directly upgraded. At this time, the firmware is burned into Nor Flash. The capacity of Nor Flash cannot load a complete firmware with a size of 1GB +, so it will fail. In case of upgrading failure, it is recommended to click EraseFlash to erase to prevent entering Nor Flash after restart


S: Refer to steps of wiki https://wiki.t-firefly.com/en/Co ... are_with_flash.html

List Storage Fail

R: Without downloading MiniLoaderAll.bin , and directly click to read the storage list. A typical step is missing,

S:
1. downloading MiniLoaderAll.bin, we could get it in this link https://www.t-firefly.com/share/ ... 2084e383074ada.html

2. Follow the steps to download MiniLoaderAll.bin to the boot column of the tool, and then click to read the storage list




Click Download Exception




R:
1. There is a problem of MiniLoaderAll.bin that we got
2. Downloaded MiniLoaderAll.bin repeatedly

S: Download MiniLoaderAll.bin again.  After the boot column is downloaded successfully, there is no need to click download repeatedly

System Failed to Start Normally

1. Bootdev(atags): mtd 2
   
2. GUID Partition Table Header signature is wrong: 0xA9425BF5A94153F3 != 0x5452415020494645
   
3. *** ERROR: Can't write GPT header ***
   
4. Backup GPT repair fail!
   
5. PartType: EFI
   
6. boot mode: recovery (misc)
   
7. FIT: No fdt blob
   
8. boot mode: None
   
9. Android 11.0, Build 2021.4, v2
   
10. Found DTB in boot part
    
11. Failed to read resource hdr
    
12. Failed to create resource list
    
13. Failed to load DTB
    
14. Failed to get kernel dtb, ret=-19
    
15. io-domain: OK
    
16. Model: Rockchip RK3568 Evaluation Board
    
17. rockchip_set_ethaddr: vendor_storage_write failed -5
    
18. rockchip_set_serialno: could not find efuse/otp device
    
19. no recovery key node
    
20. CLK: (sync kernel. arm: enter 816000 KHz, init 816000 KHz, kernel 0N/A)
    
21.   apll 816000 KHz
    
22.   dpll 780000 KHz
    
23.   gpll 1188000 KHz
    
24.   cpll 1000000 KHz
    
25.   npll 24000 KHz
    
26.   vpll 24000 KHz
    
27.   hpll 24000 KHz
    
28.   ppll 100000 KHz
    
29.   armclk 816000 KHz
    
30.   aclk_bus 150000 KHz
    
31.   pclk_bus 50000 KHz
    
32.   aclk_top_high 300000 KHz
    
33.   aclk_top_low 200000 KHz
    
34.   hclk_top 150000 KHz
    
35.   pclk_top 50000 KHz
    
36.   aclk_perimid 300000 KHz
    
37.   hclk_perimid 150000 KHz
    
38.   pclk_pmu 50000 KHz
    
39. Net:   No ethernet found.
    
40. Hit key to stop autoboot('CTRL+C'):  0
    
41. ## Booting FIT Image FIT: No fit blob
    
42. FIT: No FIT image
    
43. ANDROID: reboot reason: "(none)"
    
44. optee api revision: 2.0
    
45. TEEC: blk_dread fail
    
46. TEEC: OpteeClientRkFsInit fail!
    
47. Can't read vboot flag
    
48. Android boot failed, error -1.
    
49. no mmc device at slot 1
    
50. no mmc device at slot 0
    
51. starting USB...
    
52. Bus dwc3@fcc00000: usb maximum-speed not found
    
53. Register 2000140 NbrPorts 2
    
54. Starting the controller
    
55. USB XHCI 1.10
    
56. Bus dwc3@fd000000: usb maximum-speed not found
    
57. Register 2000140 NbrPorts 2
    
58. Starting the controller
    
59. USB XHCI 1.10
    
60. scanning bus dwc3@fcc00000 for devices... 1 USB Device(s) found
    
61. scanning bus dwc3@fd000000 for devices... cannot reset port 1!?
    
62. 1 USB Device(s) found
    
63.        scanning usb for storage devices... 0 Storage Device(s) found
    
64. 
    
65. Device 0: unknown device
    
66. No ethernet found.
    
67. missing environment variable: pxeuuid
    
68. missing environment variable: bootfile
    
69. Retrieving file: pxelinux.cfg/00000000
    
70. No ethernet found.
    
71. missing environment variable: bootfile
    
72. Retrieving file: pxelinux.cfg/0000000
    
73. No ethernet found.
    
74. missing environment variable: bootfile
    
75. Retrieving file: pxelinux.cfg/000000
    
76. No ethernet found.
    
77. missing environment variable: bootfile
    
78. Retrieving file: pxelinux.cfg/00000
    
79. No ethernet found.
    
80. missing environment variable: bootfile
    
81. Retrieving file: pxelinux.cfg/0000
    
82. No ethernet found.
    
83. missing environment variable: bootfile
    
84. Retrieving file: pxelinux.cfg/000
    
85. No ethernet found.
    
86. missing environment variable: bootfile
    
87. Retrieving file: pxelinux.cfg/00
    
88. No ethernet found.
    
89. missing environment variable: bootfile
    
90. Retrieving file: pxelinux.cfg/0
    
91. No ethernet found.
    
92. missing environment variable: bootfile
    
93. Retrieving file: pxelinux.cfg/default-arm-rockchip
    
94. No ethernet found.
    
95. missing environment variable: bootfile
    
96. Retrieving file: pxelinux.cfg/default-arm
    
97. No ethernet found.
    
98. missing environment variable: bootfile
    
99. Retrieving file: pxelinux.cfg/default
    
100. No ethernet found.
     
101. Config file not found
     
102. No ethernet found.
     
103. No ethernet found.
     
104. =>

Copy the code

R: System boot from Nor Flash, check the log "Bootdev(atags): mtd 2".

S:
1. erase Nor flash directly in this uboot mode

1. => mtd erase nor0
   
2. Erasing 0x00000000 ... 0x01ffffff (8192 eraseblock(s))
   
3. => reboot

Copy the code

2. Enter maskrom mode and erase Nor flash by AndroidTool(RKdevTool), refer to https://wiki.t-firefly.com/en/Co ... are_with_flash.html


There are two situations when we entering maskrom mode, one EMMC is empty, another one EMMC has burned into a firmware

If EMMC is empty, we could refer to chapter 《MaskRom Mode》 to short Nor FLash circuit to enter maskrom

AIO-3568J: https://wiki.t-firefly.com/en/Core-3568J/04-maskrom_mode.html
ROC-RK3568-PC: https://wiki.t-firefly.com/en/ROC-RK3568-PC/04-maskrom_mode.html
ROC-RK3566-PC: https://wiki.t-firefly.com/en/ROC-RK3566-PC/04-maskrom_mode.html

If EMMC has burned into a firmware, the system will boot from EMMC to normal mode after short circuit Nor Flash. Each time we want to boot from EMMC to normal mode, we must short Nor Flash, it's cumbersome and  inconformity. So we need to go back maskrom mode to erase Nor Flash, there are two ways for us to enter maskrom:   
①Short circuit Nor Flash and EMMC at the same time

②When shorting circuit of Nor Flash, press ctrl+c to enter uboot command line mode during EMMC startup. and then enter command rbrom to go back maskrom mode

1. U-Boot 2017.09 (Jul 07 2021 - 10:03:57 +0800)
   
2. ...
   
3. dwmmc@fe2b0000: 1, dwmmc@fe2c0000: 2, sdhci@fe310000: 0
   
4. Bootdev(atags): mmc 0
   
5. MMC0: HS200, 200Mhz
   
6. ...
   
7.   pclk_pmu 100000 KHz
   
8. Net:   eth1: ethernet@fe010000, eth0: ethernet@fe2a0000
   
9. Hit key to stop autoboot('CTRL+C'):  0
   
10. => <INTERRUPT>
    
11. => <INTERRUPT>
    
12. => rbrom

Copy the code

"Bootdev(atags): mmc 0" means system boot from EMMC


Trapped in "Starting kernel"

1. Starting kernel ...
   
2. 
   
3. =>

Copy the code

R: It may be caused by improper configuration of the serial port debug module or software used. The system may have been up. At this time, we can connect the screen like HDMI to see whether there is a display or whether ADB can be used normally


S: Try to use official serial port module https://www.firefly.store/goods.php?id=32

robinwayne

Great article! I really appreciate your efforts to create quality and meaningful work. Thank you for your inspiration! Play game planet clicker free.

selapinajrferwa

Playing games is more than bitlife entertainment; it’s a tool for developing problem-solving skills and strategic thinking. Many games challenge players to make quick decisions and adapt to changing scenarios, which are valuable life skills.