Skip to content

SE_PATCH_Data() API may fail with error code 3 #6

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.

Sign up for GitHub

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

Jump to bottom
Closed
firmwareguru opened this issue Dec 7, 2022 · 2 comments
Closed

SE_PATCH_Data() API may fail with error code 3 #6

firmwareguru opened this issue Dec 7, 2022 · 2 comments

Comments

@firmwareguru
Copy link
Contributor

firmwareguru commented Dec 7, 2022 •
edited
Loading

Noted in v1.3.0, but exists in all prior versions.

Error code 3 - Invalid image - firmware image header checksum failed or not present

User application must explicitly enable the hardware CRC unit's power before engaging with the SE_PATCH_Data() API. Suggested to use __HAL_RCC_CRC_CLK_ENABLE().

This step will not be required in v1.4.0 as the power will be turned on at time of SE_PATCH_Init().
@firmwareguru firmwareguru changed the title SE_PATCH_Data() API will fail with error code 3 SE_PATCH_Data() API may fail with error code 3 Dec 7, 2022
@firmwareguru
Copy link
Contributor Author

This issue has been noted in the v1.3.0 release errata @ https://github.com/firmwaremodules/stm32-secure-patching-bootloader/releases/tag/v1.3.0

@firmwareguru
Copy link
Contributor Author

Fixed in v1.4.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@firmwareguru