SoC Manifest SVN

[rstrongMCT]

In https://github.com/chipsalliance/caliptra-sw/blob/main/auth-manifest/README.md, the SoC Manifest describes a 4 byte Manifest Version.

https://github.com/chipsalliance/Caliptra/blob/main/doc/Caliptra.md (Table 21: Caliptra Fuse Map) describes 2 eFuse fields:

SOC MANIFEST SVN | 128 | ROM FMC RUNTIME | In-field programmable | One-hot encoded value for the SOC authorization manifest minimum supported SVN.

SOC MANIFEST MAX SVN | 8 | ROM FMC RUNTIME | In-field programmable | Maximum value for the SOC authorization manifest SVN.

How does Caliptra use these values during AUTHORIZE_AND_STASH?

Similar question for the FW Manifest

Table 18: Firmware manifest header shows a 4 Byte SVN (SVN | 4 | Security Version Number for the firmware, checked against the SVN fuses.)

Yet, Table 21: Caliptra Fuse Map describes: RUNTIME SVN | 128 | ROM FMC RUNTIME | In-field programmable | Firmware security version number.

Is it intended to have a mismatch between manifest header and eFuse values?

Is MCU RT also described by a SoC Manifest? If yes, is MCU's RT SoC Manifest independent of non-MCU SoC FW's SoC Manifest?