-
Notifications
You must be signed in to change notification settings - Fork 630
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
Problem with embassy_stm32::ospi::Ospi::new_*
#2926
Comments
I checked https://github.com/embassy-rs/stm32-data-generated/tree/main and found all pins seemingly correctly assigned, for instance: |
I brefly check the I see some differences:
This can be the cause for not implemented error, but I'm not knowledgeable about embassy build process and embedded programming to answer this with certainty. |
Thanks for the hints, I'll follow them. But actually, this looks like something that @Dirbaio has to look at, doesn't it? |
I think it would be best if he takes a look at this, as he is more experienced in this field :) |
So, it seems to be about the OCTOSPI manager that sits between the physical pins i.e.:
and the internal OCTOSPI1 virtual port. From the reference manual, p. 964: |
Here I accidently found a micropython guy addressing the same issue, seemingly: |
I have problems creating a new OSPI driver for a quadspi external chip. I get
the trait 'embassy_stm32::ospi::*<embassy_stm32::peripherals::OCTOSPI1>' is not implemented for '*'
for all 6 Pins. Am I doing something wrong here or is it a bug?I try it with the current git version of embassy.
If I look at https://github.com/embassy-rs/embassy/blob/main/examples/stm32f7/src/bin/qspi.rs, I think I have cooked it down and abstracted from the mcu- and flash-specific parts.
Also, I see the function
embassy/embassy-stm32/src/qspi/mod.rs
Line 88 in 4b4777e
equivalent to
embassy/embassy-stm32/src/ospi/mod.rs
Line 259 in 4b4777e
so I assume, I can use the qspi example as a pattern for ospi too?
That's the minimal code which I'd expect to build:
The text was updated successfully, but these errors were encountered: