Secure Boot Overview

Microchip Principal Engineer Gerry Vahe introduces the Secure Boot process and discusses its value and function. Learn about some of Microchip's Secure Boot enabled ICs and how they can benefit many kinds of designs.

For more information:

[wwolfram]

@9:10 Some steps here might be helpful to understand - For example: the Public Key is applied to the HASH to create a signature, and this signature is compared to the signature created by the Private Key of the HSM (I assumed a trusted device)? That does not seem correct. Rather, it seems that the signature created by the HSM (using its private key) needs to be 'decrypted' by the public key then compared to the HASH calculated from the desired FW to be run. If these are equal, then we know the FW has integrity and can be trusted.

[imtiyajshaikh]

Very helpful. Simple and lucid explaination

[wfliu]

Very clear description for Secure BOOOT with HSM, Thanks MacroChip :)

[mallninja]

@1:30 "Secureboot ensures that only trusted and authentic firmware runs on the embedded system" - trusted by whom? By what definition of "authentic"?

[DrInfiniteExplorer]

Does Microchip have a statement or philosophy or similar about secureboot and the right to repair (for example)?
It's not uncommon for IoT connected devices to only operate if they are allowed to phone home to a cloud operated server, and all instructions/reports to/from the device needs to go through said server.
And it's not uncommon for such companies to go out of business and/or pull their services, which leaves customers with essentially bricked expensive devices.
Has Microchip thought about these scenarios? Are there any guidelines one can follow to deal with this sort of things, either from the perspective of a service provider, or from the perspective of a consumer?
Are the two concerns mutually exclusive by nature?