12.07.2015 Views

PXA3xx Boot ROM Reference Manual - Marvell

PXA3xx Boot ROM Reference Manual - Marvell

PXA3xx Boot ROM Reference Manual - Marvell

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

multiple versions of the Device Keying Binary, one for use in manufacturing and one for use indevelopment. The development Device Keying Binary could be used to aid in debugging theplatform.<strong>Marvell</strong> provides the <strong>Marvell</strong> ® Wireless Trusted Platform Tool Package as an example for OEMs.This package contains all of the host tools and middleware required for both trusted and traditionalboot. Contact your local <strong>Marvell</strong> field applications engineer for more information.The Device Keying Binary is responsible for completing the following on trusted boot platforms:• Provide an interface through the UART or USB port to print messages, when run-time progressand error reporting are needed, and download binary images.• Set up the DDR memory and all necessary flashes to store the downloaded images. At aminimum, this includes the OEM boot module.• If the flash signature in the trusted image module indicates a setup for NAND, create the initialbad block table.• Integrity check the images against the trusted image module.• Find a good entropy source to generate/collect a five-word random number generator (RNG)seed and program it into flash where the <strong>Marvell</strong> ® WTM save state is newly created, accordingto the trusted image module.• Program the encrypted hash value of the OEM platform verification key into the flash one-timeprogrammable Register 0 (64-bits) and the remaining 96 bits into the lower half of Register 1(for platforms using XIP-based flashes only).• Program the hash value of the JTAG re-enabling key, also referred to as the corrupted OEMboot module reverification key, into the upper half of Register 1 (32 bits) and the remaining 128bits into Register 2 and lock Registers 0, 1, and 2 respectively (for platforms using XIP-basedflashes only).• Program the OEM wrapped verification keys (24 bits for A0, 48 bits for stepping B0 andforwards) into the <strong>Marvell</strong> ® WTM fuses using the OEM_Platform_Bind_PI via an ippCP call.• Program the platform configuration fuses in the <strong>Marvell</strong> ® Wireless Trusted Module.12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758Copyright © 2010 <strong>Marvell</strong> PUBLIC REKEASE Doc. No. MV-S301208-00 Rev. -Page 31

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!