cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Observer
Observer
866 Views
Registered: ‎02-14-2018

Zynq Ultrascale+ Fallback Multiboot

Jump to solution

We are trying to implement fallback multiboot to avoid bricking of system during failed field updates. We are finding that the boot header needs to be corrupted to trigger the fallback multiboot from a golden image.  This is not very useful.  What happens when the FSBL is corrupted or the boot image is corrupted?  How do we implement full fall back multiboot like we had in earlier FPGA families?  We are booting from a Quad-SPI (QSPI32) flash memory using a XCZU6CG MPSoC device.

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Moderator
Moderator
825 Views
Registered: ‎03-19-2014

UG1137 describes the behavior in Fallback.  The header is validated in a non-secure boot.   For a pull partition check, add authentication.  In that boot case the partition is authenticated, if it fails, the boot will fallback to the next image.

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

View solution in original post

0 Kudos
1 Reply
Highlighted
Moderator
Moderator
826 Views
Registered: ‎03-19-2014

UG1137 describes the behavior in Fallback.  The header is validated in a non-secure boot.   For a pull partition check, add authentication.  In that boot case the partition is authenticated, if it fails, the boot will fallback to the next image.

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

View solution in original post

0 Kudos