Skip to content

Commit f6f7a5c

Browse files
committed
provisioning: Add troubleshooting to README
It is a common source of failure that the provisioning data is overwritten when programming a new flash image. In a new troubleshooting section in the README, add a recommendation to upgrade the DAPLink version to a version that supports partial image updates.
1 parent 5f02ead commit f6f7a5c

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

provisioning/README.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,3 +69,13 @@ To generate a key, specify the lifetime with `psa_set_key_lifetime()` and
6969
This example generates certificate signing requests (CSRs) which can be used
7070
for TLS client authentication. The CSR is printed over the serial port, for
7171
use with your certificate authority (CA).
72+
73+
74+
### Troubleshooting
75+
76+
If your provisioning data isn't persisting, there is a chance it is being
77+
overwritten by the flash programmer. If using DAPLink, ensure you are using a
78+
DAPLink interface version of 0246 or newer. Older versions of DAPLink do not
79+
support partial flash programming, and always overwrite any data stored in
80+
internal flash. In our case, this would be the provisioning data we want to
81+
keep!

0 commit comments

Comments
 (0)