Fix erase sector failure on S25FL127S #101
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I found that all erase command except chip erase failed on my MKR1000 and Cypress S25FL127S (128Mbits). TestFlash.ino did not show any errors but flash.eraseSector(), eraseBlock32K() and eraseBlock64K() did not take effect.
I used my logic analyzer and noticed that the library send out some garbage on SPI bus after erase command and 3 address bytes. I added missing break statements in SPIFlash::_beginSPI() because that lacks some essential break statement in switch/case. (commit 1: 1de2c10)
Then I found that the library did not wait until the busy bit in SR1 was cleared. Timeout argument of _notBusy() must be in micro-second. 500L means 500 micro seconds which is too short to wait for completion of erase command. I've add " * 1000" to the arguments. (commit 2: 9633c2f)
And I modified TestFlash.ino to check error of erase commands execution. (commit 3: a179306)
I've tested these changes on my MKR1000 and S25FL127S and they looks working correctly. (S25FL127S does not have Erase Block 32 command however.)