Fix failing flash operations with gcc -O3 #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…h operations fail because CPUSS_SYSARG is read aout too closely after CPUSS_SYSREQ has been set. Using two NOP()s instead of one after setting CPUSS_SYSREQ is sufficient to overcome this. Tested and verified on RDK4 demo-board.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
By creating this pull request you agree to the terms in CONTRIBUTING.md.
https://github.com/Infineon/.github/blob/master/CONTRIBUTING.md
--- DO NOT DELETE ANYTHING ABOVE THIS LINE ---
CONTRIBUTING.md also tells you what to expect in the PR process.
Description
When compiling for PSoC4 with GCC and compile flag -O3, flash operations fail because
CPUSS_SYSARGis read out too closely afterCPUSS_SYSREQhas been set. Using two__NOP()s instead of one after settingCPUSS_SYSREQis sufficient to overcome this.Related Issue
None
Context
The problem was observed on proprietary hardware with a PSoC4 S Max and on a Rutronics RDK4 evaluation board.
The value of
CPUSS_SYSARGinProcessStatusCode()was neitherSROMCODE_SUCCESSnorSROMCODE_ERROR_FLAGand thusProcessStatusCode()returnedCY_FLASH_DRV_OPERATION_STARTED, even thoughCY_FLASH_NON_BLOCKING_SUPPORTEDwas not set.Adding the extra
__NOP()s apparently gives the processor enough time to update theCPUSS_SYSARGregister.