hello zhuyonghui,
sorry, that’s no such documentation to cover that.
this issue might happened if you power-off the system after power-on within 1-minutes.
here’s the reason…
you may also look into bootloader messages,
for example,
QSPI: erasing sectors from 176 – 176 <== SMD_a
QSPI: erasing sectors from 177 – 177 <== SMD_b
in the r32.4 CBoot flow, we always update primary SMD first (i.e. SMD_a), there will have a risk when power off in the SMDs updating.
please upgrade to the latest release, (i.e. JetPack-4.5.1)
with the change update, it’ll update the un-used SMD partition first (i.e. SMD_b), hence will be the fail-safe update.
thanks