| ac44b9c7 | 25-Sep-2025 |
Sumit Garg <sumit.garg@oss.qualcomm.com> |
feat(kodiak): add support for RB3Gen2 platform
RB3Gen2 is an IoT platform based on Kodiak SoC. Details about this platform can be found here [1]. The boot flow with TF-A/OP-TEE is:
PBL (ROM) -> X
feat(kodiak): add support for RB3Gen2 platform
RB3Gen2 is an IoT platform based on Kodiak SoC. Details about this platform can be found here [1]. The boot flow with TF-A/OP-TEE is:
PBL (ROM) -> XBL -> BL2 -> BL31 -> BL33 -> Normal world OS | --> BL32
Steps to build TF-A for RB3Gen2:
$ make -j`nproc` PLAT=rb3gen2 SPD=opteed QTISECLIB_PATH=<qtiseclib-path> BL32=<path-to-optee-bin> BL33=<path-to-os-bootloader-bin> fip all
$ ./tools/qti/generate_fip_elf.sh build/rb3gen2/release/fip.bin 0x9fc00000
The resulting fip.elf should be flashed in uefi_a partition on UFS flash storage.
Note here that the bl2.elf generated requires to be signed as TZ image with QTI signing involved. There is an ongoing effort to enable OEM only signing for future boards support.
[1] https://www.qualcomm.com/developer/hardware/rb3-gen-2-development-kit
Change-Id: Ic19f28a5f559a0da28337f2d8da0d0e289a94514 Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
show more ...
|
| 6091f03d | 25-Sep-2025 |
Sumit Garg <sumit.garg@oss.qualcomm.com> |
refactor(qti): introduce SoC codename as Kodiak
Qualcomm has recently started using SoC codenames for upstream support with Linux kernel being the first adoptor. Using SoC codenames for upstream pro
refactor(qti): introduce SoC codename as Kodiak
Qualcomm has recently started using SoC codenames for upstream support with Linux kernel being the first adoptor. Using SoC codenames for upstream projects removes the need to follow different product names like for kodiak which is also known as sc7280, qcm6490 etc.
Let's follow this practice of using SoC codenames for TF-A project too beginning with Kodiak. While doing that let's refactor SoC and board specific files where the existing support for sc7280 has been renamed to sc7280_chrome to reflect it's usage.
Change-Id: I236fadf8ae9550f94deb05ebfed17e2ddbd69509 Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
show more ...
|
| c48d0aef | 25-Sep-2025 |
Sumit Garg <sumit.garg@oss.qualcomm.com> |
feat(qti): add TF-A BL2 common platform framework
Currently QTI pltforms only supports coreboot as the second stage bootloader. Lets enable support for TF-A BL2 as the common reference second stage
feat(qti): add TF-A BL2 common platform framework
Currently QTI pltforms only supports coreboot as the second stage bootloader. Lets enable support for TF-A BL2 as the common reference second stage bootloader which is able to support a variety of normal world OS bootloaders (BL33) like edk2, U-Boot, coreboot-depthcharge etc.
The common reference boot flow should look like following on QTI platforms:
PBL (ROM) -> XBL -> BL2 -> BL31 -> BL33 -> Normal world OS | --> BL32
As of now XBL is performing DRAM initialization and loads two set of images for BL2 and FIP into DRAM from flash after performing secure boot checks if enabled. Then BL2 does the FIP parsing from DRAM and loads payloads at appropriate addresses as per the FIP configuration.
Note here that BL2 image is loaded from TZ partition on UFS flash which by default requires QTI secure boot checks.
Change-Id: Ice73905bff39291fa417389cb84dabe455c3f0ba Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
show more ...
|
| 48897bad | 25-Sep-2025 |
Casey Connolly <casey.connolly@linaro.org> |
feat(qti): add BL32 support
Add support for loading a BL32 image like OP-TEE. In this case we stop routing secure EL3 interrupts to EL3 and instead allow S-EL1 to handle them.
Change-Id: I8ba25f83c
feat(qti): add BL32 support
Add support for loading a BL32 image like OP-TEE. In this case we stop routing secure EL3 interrupts to EL3 and instead allow S-EL1 to handle them.
Change-Id: I8ba25f83cfc8749974fb5760392a8c64b2cec18b Signed-off-by: Casey Connolly <casey.connolly@linaro.org> Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
show more ...
|
| 8eb87556 | 25-Sep-2025 |
Sumit Garg <sumit.garg@oss.qualcomm.com> |
refactor(qti): make UART config independent
Make UART configuration independent of coreboot since there are alternative bootloaders like TF-A BL2 which can be supported. Also, configure UART scope t
refactor(qti): make UART config independent
Make UART configuration independent of coreboot since there are alternative bootloaders like TF-A BL2 which can be supported. Also, configure UART scope to enable runtime logging as well.
Change-Id: I1956535c769c2c3141854d062dc02c289b86b48d Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
show more ...
|
| 327a32d9 | 25-Sep-2025 |
Sumit Garg <sumit.garg@oss.qualcomm.com> |
refactor(qti): make CNTFRQ config independent
Make system counter frequency configuration independent of prior stage boot-loader like coreboot to enable an alternative boot-loaders such as TF-A BL2.
refactor(qti): make CNTFRQ config independent
Make system counter frequency configuration independent of prior stage boot-loader like coreboot to enable an alternative boot-loaders such as TF-A BL2.
Change-Id: Id22803557466643f6455a243929626f71a4714fc Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
show more ...
|