Показаны различия между двумя версиями страницы.
Следующая версия | Предыдущая версия | ||
wiki:cmp:proc:rockchip:rv1103_rv1106:uboot:start [2024/04/10 23:25] – создано Roman Abakumov | wiki:cmp:proc:rockchip:rv1103_rv1106:uboot:start [2024/04/10 23:32] (текущий) – Roman Abakumov | ||
---|---|---|---|
Строка 2: | Строка 2: | ||
* https:// | * https:// | ||
* https:// | * https:// | ||
- | + | ===== 1. Chapter-1 Basic Introduction ===== | |
- | ===== 1.5 Boot-order | + | ==== 1.5 Boot-order ==== |
The RK platform currently has two startup methods depending on whether the front-end Loader code is open source: | The RK platform currently has two startup methods depending on whether the front-end Loader code is open source: | ||
Строка 16: | Строка 16: | ||
be replaced with each other | be replaced with each other | ||
- | ===== 1.9 TPL/ | + | ==== 1.9 TPL/ |
U-Boot can use the same set of code to obtain Loaders with three different functions by using different compilation conditions: TPL/ | U-Boot can use the same set of code to obtain Loaders with three different functions by using different compilation conditions: TPL/ | ||
Строка 50: | Строка 50: | ||
</ | </ | ||
- | ===== 1.12 U-Boot DTS ===== | + | ==== 1.12 U-Boot DTS ==== |
U-Boot has its own DTS file, and the corresponding DTB file will be automatically generated during compilation and added to the end of u-boot.bin. File directory: | U-Boot has its own DTS file, and the corresponding DTB file will be automatically generated during compilation and added to the end of u-boot.bin. File directory: | ||
< | < | ||
Строка 57: | Строка 57: | ||
The specific DTS file used by each platform is specified through '' | The specific DTS file used by each platform is specified through '' | ||
- | + | ===== 2. Chapter-2 RK Architecture ===== | |
- | ===== 2.8 Aliases | + | ==== 2.8 Aliases ==== |
Some special aliases in U-Boot are different from the definitions in kernel DTS. | Some special aliases in U-Boot are different from the definitions in kernel DTS. | ||
Строка 68: | Строка 68: | ||
</ | </ | ||
- | ===== 2.20 vendor storage | + | ==== 2.20 vendor storage ==== |
U-Boot of the RK platform provides a Vendor storage area for users to save SN, MAC and other information. The storage offset is as follows (see details vendor.c) | U-Boot of the RK platform provides a Vendor storage area for users to save SN, MAC and other information. The storage offset is as follows (see details vendor.c) | ||
Строка 93: | Строка 93: | ||
Command effect: diff the configuration differences between the current .config and rv1126_defconfig into the rv1126-emmc-tb.config file. | Command effect: diff the configuration differences between the current .config and rv1126_defconfig into the rv1126-emmc-tb.config file. | ||
- | ===== 4.7 DTBO/ | + | ===== 4. Chapter-4 System module ===== |
+ | ==== 4.7 DTBO/DTO ==== | ||
In order to facilitate users’ understanding of the contents of this chapter, please read the appendix chapter first to clarify the professional terms: DTB, DTBO, DTC, DTO, DTS, FDT | In order to facilitate users’ understanding of the contents of this chapter, please read the appendix chapter first to clarify the professional terms: DTB, DTBO, DTC, DTO, DTS, FDT | ||
Строка 106: | Строка 107: | ||
For more information on this chapter, please refer to: https:// | For more information on this chapter, please refer to: https:// | ||
- | ===== 4.11 HW-ID DTB ===== | + | ==== 4.11 HW-ID DTB ==== |
U-Boot of the RK platform supports detecting the GPIO or ADC status on the hardware and dynamically loading different Kernel DTBs, which is temporarily called HW-ID DTB (Hardware id DTB) | U-Boot of the RK platform supports detecting the GPIO or ADC status on the hardware and dynamically loading different Kernel DTBs, which is temporarily called HW-ID DTB (Hardware id DTB) | ||
function. | function. | ||
- | ==== 4.11.1 Design principles | + | === 4.11.1 Design principles === |
Usually hardware design will frequently update versions and some components, such as screens, wifi modules, etc. If each hardware version corresponds to a set of software, maintenance will be | Usually hardware design will frequently update versions and some components, such as screens, wifi modules, etc. If each hardware version corresponds to a set of software, maintenance will be | ||
more troublesome. Therefore, the HW_ID function is needed to implement a set of software that can adapt to different versions of hardware. | more troublesome. Therefore, the HW_ID function is needed to implement a set of software that can adapt to different versions of hardware. | ||
Строка 120: | Строка 121: | ||
the current hardware version from resource.img. to kernel | the current hardware version from resource.img. to kernel | ||
- | ==== 4.11.2 Hardware Reference | + | === 4.11.2 Hardware Reference === |
Currently, it supports ADC and GPIO methods to determine the hardware version. | Currently, it supports ADC and GPIO methods to determine the hardware version. | ||
Строка 137: | Строка 138: | ||
There is currently no hardware reference design for GPIO, and users can customize it themselves. | There is currently no hardware reference design for GPIO, and users can customize it themselves. | ||
- | ===== 8.3 io command | + | ===== 8. Chapter-8 Debugging methods ===== |
+ | ==== 8.3 io command ==== | ||
Function: Read and write memory. | Function: Read and write memory. | ||
Строка 160: | Строка 162: | ||
</ | </ | ||
- | ===== 8.10 dm tree ===== | + | ==== 8.10 dm tree ==== |
Function: View the binding and probe status between all device-drivers. | Function: View the binding and probe status between all device-drivers. | ||
Строка 221: | Строка 223: | ||
=== 11.1.1 Configuration === | === 11.1.1 Configuration === | ||
+ | ===== 12. Chapter-12 FIT ===== | ||
==== 12.3 Platform configuration ==== | ==== 12.3 Platform configuration ==== | ||
=== 12.3.3 Image file === | === 12.3.3 Image file === |