Replies: 2 comments 1 reply
-
|
Are you referring to Caliptra 1.x or 2.0? In 1.x, the boot media is totally up to the SoC; it is given to Caliptra via a mailbox command. So it is not required to boot from SPI. In 2.x passive mode, the same is true. In 2.x subsystem mode, the boot flow follows the OCP recovery spec, for which there are bindings to multiple transports IIUC. So the integrator can choose to boot over SPI or I3c or some other transport depending on what boot source they include. @mhatrevi or @bharatpillilli to link to more details about how subsystem boot works. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, The physical path on which the FW can be fetched/streamed can be anything chosen by SoC. The requirement is to be able to write/stream the payload (after stripping off the physical channel metadata) into the same streaming boot/recovery interface registers. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently Caliptra supports loading the SoC firmware from the SPI flash and compare the SHA(image) to the SoC manifest.
Is it possible to dynamic download the firmware from the host (not from the SPI flash) and directly authenticate the signature?
The motivation behind this query is the hyperscalers requirement is to reduce the amount of flash updates by providing the second stage firmware (signed) dynamically from the host.
Beta Was this translation helpful? Give feedback.
All reactions