Fix pre-SDK Cache_Read_Enable for PUYA flash #8658
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.
This resolves the exception 0 issue with PUYA flash during the pre-SDK context. This Issue showed when using flash/ICACHE for
umm_init
and/or usingHWDT
Stack Dump .The
SPI_CS_SETUP
parameter has been observed set in RTOS SDK and NONOS SDK as part of flash init/configuration. It may be necessary for some flash chips to perform correctly. Turning on and leaving it on should be okay.phy_get_bb_evm
is the key function, called fromfix_cache_bug
in the NONOS SDK. This addition resolves the exception 0 issue with PUYA Flash when earlyCache_Read_Enable
is used.Changed
umm_init
back to default in IRAM. DefineUMM_INIT_USE_ICACHE
to moveumm_init
to flash and free up IRAM. For the non-debug build, it frees 136 bytes of IRAM while increasing IROM by 224 bytes.Resolves #8657 (comment) (has PUYA flash)
Unable to recreate the problem with the PUYA P25Q80H flash chip on ESP-01S.
Updated to summarize current PR.