Hi, expert:
I have studied Jetson boot flow. The boot procedure is mb1 → mb2 → uefi → linux. We want to burn uefi_t26x_general.bin to our own spi flash outside SOM.
I saw some mb2 dtsi files in Linux_for_Tegra/bootloader folder. Can we config mb2 to burn uefi to other spi flash outside SOM?
Hi ycl,
Are you using the devkit or custom board for Thor?
What’s the Jetpack version in use?
There’s a QSPI inside the SoM. Do you mean that you have added another QSPI on your custom carrier board?
Could you elaborate on your use case?
Yes, we have added another QSPI flash on our carrier board.
Our use case is that thor can be brought up from both spi flash inside SOM and spi flash on our carrier board.
Can guide us how to do or how to configure MB2 ?
Thanks.
Sorry that we have not verified for this use case.
How do you connect the secondary QSPI flash on custom carrier baord? Which SPI interface are you using?
There are multiple partitions inside the QSPI for the booting. Maybe you can try to clone them from the original QPSI.
Hi, KevinFFF:
We are about to connect CVM SPI1, SPI2, SPI3 to external spi flash. If we cloned flash from original QSPI flash, how can BPMP BootRom choose from which flash to load MB1, MB2, and uefi?
What’s more, how to add SPI1, SPI2, SPI3 drivers in uefi? Is there some example code?
And during flashing, how to choose the spi port to flash spi-firmware? For example, use spi0, spi1, or spi2 to flash spi-firmware.
We don’t and never verified for the similar use case which uses 2 QSPI on Jetson.
I don’t think BootROM could recognize them and the overall boot flow will be changed significantly.
May I know why you need to add the second QSPI in your case?
We have A/B slot for bootloader which is designed for fail-safe mechanism.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.