-
Notifications
You must be signed in to change notification settings - Fork 726
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add octospim support for octospi #3102
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Haobo Gu <[email protected]>
Signed-off-by: Haobo Gu <[email protected]>
Signed-off-by: Haobo Gu <[email protected]>
Signed-off-by: Haobo Gu <[email protected]>
Signed-off-by: Haobo Gu <[email protected]>
Signed-off-by: Haobo Gu <[email protected]>
Signed-off-by: Haobo Gu <[email protected]>
Signed-off-by: Haobo Gu <[email protected]>
Signed-off-by: Haobo Gu <[email protected]>
I've tested this PR on stm32h7b0 + w25q64 qspi flash, worked well. But there are still limitations of current implementation:
|
Did more testing on a rm67162 qspi screen, worked too. Demo project: https://github.com/HaoboGu/eg-demo |
Hi @HaoboGu, I managed to use your branch on an stm32h735g-dk to communicate with PSRAM through the hyperbus. However, I had to use OCTOSPI2 because of how the dev kit is wired up so I think it's worth trying to figure out how to support OCTOSPI2 as well. Are you still working on this branch? |
@ninjasource Yeah, OCTOSPI2 is not support now. I had some problems when implementing it for both OCTOSPI1 and OCTOSPI2. For a temporary solution, you can change here and here to make it work for OCTOSPI2 |
Signed-off-by: Haobo Gu <[email protected]>
I've pushed a commit making it possible to support both OCTOSPI1 and OCTOSPI2. But
This problem is still there. @Dirbaio Do you have any suggestions on solving it? |
This PR adds initial support for OCTOSPIM peripheral of octospi. Current implementation just adds OCTOSPIM to octospi, and enables corresponding pins of OCTOSPIM.
Closes #3097