-
Notifications
You must be signed in to change notification settings - Fork 101
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
properly unlock flash on re-entry of wolfBoot_swap_and_final_erase #526
Conversation
and move it out of the lock logic of update and delta update
1dfa519
to
bbdf14e
Compare
add hal_flash_unlock after setting the key since setting the key locks flash
added hal and ext flash locks to the simulator, fixed test failures caused by flash being accessed while locked. @danielinux any idea why the unit test is failing? is it because I added the locks to hal/sim.c and it's not aware of them? |
The hal_flash_lock/unlock functions are mocked and checked, it seems that the unit test is dectecting a |
I figured out the issue, it was only unlocking flash when encryption was on, I think it was a copy and paste issue. should be good to go now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Good idea adding checks for unlock/lock in the simulator as well.
Just a doubt about DISABLE_BACKUP
calling wolfBoot_swap_and_final_erase()
and move it out of the lock logic of update and delta update