PXA3xx Boot ROM Reference Manual - Marvell

More documents

Recommendations

Info

PXA3xx Processors and Tavor ProcessorBoot ROM Reference Manual7.1 Trusted Image Module FormatFor the trusted image module format for the boot operation, all values are 32-bit unsigned integers.VERSION INFORMATION:unsigned int Version;unsigned int Identifier;unsigned int Trusted;unsigned int IssueDate;unsigned int OEMUniqueID;FLASH INFORMATION:unsigned int WTMFlashSign;unsigned int WTMEntryAddr;unsigned int WTMEntryAddrBack;unsigned int Reserved[2];unsigned int BootFlashSign;TIM SIZING INFORMATION:unsigned int NumImages;unsigned int NumKeys;unsigned int SizeOfReserved;IMAGE INFORMATION ARRAY IMAGE[NumImages];unsigned int ImageID;unsigned int NextImage;unsigned int FlashEntryAddr;unsigned int LoadAddr;unsigned int ImageSize;unsigned int ImageSizeToHash;unsigned int HashAlgorithmID;unsigned int Hash[8];KEY INFORMATION ARRAY KEY[NumKeys];unsigned int KeyID;unsigned int HashAlgorithmID;unsigned int ModulusSize;unsigned int PublicKeySize;unsigned int RSAPublicExponent[64];unsigned int RSAModulus[64];unsigned int KeyHash[8];unsigned int Reserved[SizeOfReserved];PLATFORM DIGITAL SIGNATURE INFORMATION:unsigned int DSAlgorithmID;unsigned int HashAlgorithmID;unsigned int ModulusSize;unsigned int Hash[8];unsigned int RSAPublicExponent[64];unsigned int RSAModulus[64];unsigned int RSADigS[64];7.1.1 Version InformationThe Version Information field provides information about the trusted image module and platform.• Version – Current version of the trusted image module.• Identifier – TIMH identifier used to locate the trusted image module.• Trusted – Identifier to distinguish between trusted and non-trusted platforms.12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758Doc. No. MV-S301208-00 Rev. - PUBLIC RELEASE Copyright © 2010 MarvellPage 72
• IssueDate – Date this module was created.• OEMUniqueID – OEM-specific identifier.7.1.2 Flash InformationTable 39:The Flash Information substructure identifies boot flash properties and the location of the WirelessTrusted Module (Marvell WTM) save state, as follows.• WTMFlashSign – Signature that provides the Marvell WTM save state location. The upperthree bytes contain an ASCII-encoded hexadecimal value of XIP for XIP or NAN for NAND,Samsung OneNAND, and SanDisk ® (formerly MSystems) flash. The lower byte is theplatform fuse encoding that determines the flash device being used.• WTMEntryAddr – Address offset from the base of the flash device to the location of the primaryMarvell WTM save state block.• WTMEntryAddrBack – Address offset from the base of the flash device to the location of thebackup Marvell WTM save state block.• Reserved[2] – Reserved for future use.• BootFlashSign – Signature that determines from which flash the platform boots. The upperthree bytes contains an ASCII-encoded hexadecimal value of XIP for XIP or NAN for NAND,OneNAND, and SanDisk flash. The lower byte contains the platform fuse encoding thatdetermines the flash device being used. The BootFlashSign values are noted in Table 39.BootFlashSign DefinitionsBootFlashSign value Platform Boot Device Encoded HEX Value0x4E41_4E06 x8 NAND device on DF_nCS0 NAN’060x4E41_4E04 x16 NAND device on DF_nCS0 NAN’040x4E41_4E01x16 SanDisk mDOC on SMEMC NAN’01nCS20x4E41_4E02x16 OneNAND on SMEMC on NAN’02nCS20x5849_5005 x16 XIP NOR XIPB Flash on nCS2 XIP’050x5849_5007 x16 XIP NOR XIPA Flash on nCS2 XIP’07NOTE: XIPB and XIPA support different command sets. Refer to Table 14 for further information. Other NORflash memories may be used.7.1.3 TIM Sizing Information• NumImages – Number of “IMAGE INFORMATION” substructures in the trusted image module.• NumKeys – Number of “KEY INFORMATION” substructures in the trusted image module.• SizeOfReserved – Size of the reserved area; values can range from 0 to 4 KB – (size of othertrusted image module information).7.1.4 Image Information ArrayThe Image Information Array is a substructure that contains information about each image loadedinto the boot flash. The number of substructures is determined by the NumImages field above.• ImageID – A unique identifier for the image. The "OBMI" identifier must be present in thearray for the Boot ROM to correctly boot the platform. Other identifiers can be determined bythe OEM, but are limited to 32 bits in size.• NextImageID – Next image that should be loaded from flash memory.12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758Copyright © 2010 Marvell PUBLIC RELEASE Doc. No. MV-S301208-00 Rev. -Page 73
Page 1 and 2:
CoverMarvell® PXA3xx Processors an
Page 3 and 4:
Table of Contents1 Boot ROM Functio
Page 5 and 6:
6.3.5 USB Vendor Request Package ..
Page 7 and 8:
Figure 1:PXA3xx Top Level Boot ROM
Page 9 and 10:
Table 42: Host Commands ...........
Page 11 and 12:
1 Boot ROM Functional Overview1.1 G
Page 13 and 14:
Figure 1:PXA3xx Top Level Boot ROM
Page 15 and 16:
Boot ROM Differences2 Boot ROM Diff
Page 17 and 18:
Boot ROM DifferencesTIM/NTIM/OBM Su
Page 19 and 20:
Boot ROM DifferencesPXA31x and Tavo
Page 21 and 22: Boot ROM DifferencesPXA31x and Tavo
Page 23 and 24: 3 Software RequirementsThis chapter
Page 25 and 26: Typedef struct S_Reloc{USHORT Heade
Page 27 and 28: 4 Methods for Platform Provisioning
Page 29 and 30: 4. If the same OEM boot module is u
Page 31 and 32: multiple versions of the Device Key
Page 34 and 35: PXA3xx Processor and Tavor Processo
Page 74 and 75: PXA3xx Processors and Tavor Process
Page 112: Marvell Semiconductor, Inc.700 Firs
show all

PXA3xx Boot ROM Reference Manual - Marvell

Create successful ePaper yourself

Delete template?

Save as template?