-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
suit: Do not erase on IPUC write setup #21056
suit: Do not erase on IPUC write setup #21056
Conversation
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: b2a897a5f969444968bd4d89a5b2cb45327a35f9 more detailssdk-nrf:
Github labels
List of changed files detected by CI (1)
Outputs:ToolchainVersion: 4ffa2202d5 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
5cd42f1
to
d0c0028
Compare
d0c0028
to
b2a897a
Compare
Erasing of the IPUC took about 500ms of time, which led to many issues. The erasing was removed, instead different security measures were introduced, erasing parts when the seek offset is greater than the write peek offset. Signed-off-by: Artur Hadasz <artur.hadasz@nordicsemi.no>
b2a897a
to
f377b05
Compare
|
Erasing of the IPUC took about 500ms of time, which led to many issues.
The erasing was removed, instead different security measures were introduced, erasing parts when the
seek offset is greater than the write peek offset.