Page MenuHomePhabricator

Boot up fails if there is unexpected data in flash on Musca-A2
Closed, ResolvedPublic


Boot up failed on Musca-A2 with PS and ITS using real flash if the flash is not erased properly. The boot is successful and the tests pass if all the associated flash areas are erased (SST/ITS/NV-counter flash areas) areas. The following command was used to erase the flash areas :

srec_cat bl2/ext/mcuboot/mcuboot.bin -Binary -offset 0x200000 tfm_sign.bin -Binary -offset 0x220000 -fill 0xFF 0x420000 0x425000 -o tfm.hex -Intel

The current theory is that FS data associated with a previous version of SST might have been present in the flash, and caused incompatibilities with the current version. But possibly the SST module needs to be hardened against such issues and needs further investigation.

Event Timeline

We would need to support versioning of SST FS data and also have mechanisms to detect if the flash is clean or in consistent state.

jf549 claimed this task.Jul 3 2020, 11:08 AM
jf549 triaged this task as Normal priority.
jf549 edited projects, added Restricted Project; removed Trusted Firmware M.
jf549 added a subscriber: TTornblom.

Great find!

This fixes my issues with the Musca-A target.

soby-mathew closed this task as Resolved.Oct 21 2020, 12:47 PM

Cleaning the flash properly seems to solve the issue. Closing this bug as resolved. The SST hardening will taken up as a backlog item.