| commit | 14f4606dcb0533ab64562406edd157008108e0db | |
| author | Tobias Ringström <tobias@ringis.se> | |
| Fri, 30 Apr 2010 12:04:14 +0000 (30 14:04 +0200) | ||
| committer | Øyvind Harboe <oyvind.harboe@zylin.com> | |
| Mon, 3 May 2010 09:55:08 +0000 (3 11:55 +0200) | ||
| tree | 20e9140745daa41a978c4f48009aafe599f86545 | treesnapshot (tar.gz zip) |
| parent | da9f72ca0a3305cf6f961834dc441496a36c85de | commitdiff |
STM32 flash erase timeout fix
The current timeout for STM32 flash block erase and flash mass erase is
10 (ms), which is too tight, and fails around 50% of the time for me.
The data sheet for STM32F107VC specifies a maximum erase time of 40 ms
(for both operations).
I'd also consider it a bug that the code does not detect a timeout, but
just assumes that the operation has completed. The attached patch does
not address this bug.
The attached patch increases the timeouts from 10 to 100 ms. Please apply.
/Tobias
The current timeout for STM32 flash block erase and flash mass erase is
10 (ms), which is too tight, and fails around 50% of the time for me.
The data sheet for STM32F107VC specifies a maximum erase time of 40 ms
(for both operations).
I'd also consider it a bug that the code does not detect a timeout, but
just assumes that the operation has completed. The attached patch does
not address this bug.
The attached patch increases the timeouts from 10 to 100 ms. Please apply.
/Tobias
| src/flash/nor/stm32x.c | diffblobblamehistory |