diff options
author | Rob Austein <sra@hactrn.net> | 2016-11-02 19:02:58 -0400 |
---|---|---|
committer | Rob Austein <sra@hactrn.net> | 2016-11-02 19:02:58 -0400 |
commit | 66348b6986cf38d9d0fe707eca7bbfd7be3def18 (patch) | |
tree | f527150782aa8d8bb6b07d9fa0343664f59d5354 /Drivers/STM32F4xx_HAL_Driver/Src/stm32f4xx_hal_i2c.c | |
parent | 42d98519724319a3fad92fc40cca5aefa30276d7 (diff) |
Wait for WIP to clear before returning from erase operations too.
Wrong-block-type race condition errors went away after adding the WIP
check after flash write operations, then came back once (isolated
incident) while running a series of tests which had written enough
flash blocks that ks_flash may have finally had to erase something
rather than just zeroing.
Code inspection confirmed that the erase code was not waiting for WIP
to clear before exiting. Difficult to prove that this was the cause
of an unreproducible failure, but seems like a likely candidate given
previous behavior and change should be harmless, so adding it.
Timeout for this flag check is 2000 ms, which is what other
erase-related WIP flag checks were already using.
Diffstat (limited to 'Drivers/STM32F4xx_HAL_Driver/Src/stm32f4xx_hal_i2c.c')
0 files changed, 0 insertions, 0 deletions