Skip to content

Conversation

@bjoernQ
Copy link
Contributor

@bjoernQ bjoernQ commented May 17, 2023

This moves functions dealing with PSRAM into RAM

@MabezDev
Copy link
Member

Is there a reason why this is needed?

@bjoernQ
Copy link
Contributor Author

bjoernQ commented May 17, 2023

It fixes one of the problems Juraj M. ran into with the spooky-maze example.
I think what happened there was that while we reconfigure SPI1 and SPI0 the code we called was not in the current cache-page but reading from flash wasn't possible in that moment (because we are reconfiguring the SPIs). I haven't checked my theory but it explains why the example works while in Juraj's code it crashed. At least moving one of the functions to RAM fixed that and just to be on the safe side I decided to put everything up the call-tree to RAM. Then there wasn't much left so I also moved the remaining functions to RAM

Copy link
Member

@MabezDev MabezDev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, that makes sense! LGTM!

@bjoernQ bjoernQ merged commit 3be64df into esp-rs:main May 17, 2023
@bjoernQ bjoernQ deleted the esp32s3-move-psram-functions-to-ram branch May 17, 2023 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants