2024-10-30 01:08 AM - last edited on 2024-10-30 11:25 AM by Tesla DeLorean
HELP ME,PLEASE!!!
In addition to the failure of the microcontroller, are there any other unreasonable configurations that may cause data transmission to fail?
2024-10-30 10:48 AM - edited 2024-10-30 10:49 AM
Hello @maya123,
Try the read-to-use OSPI example available on the STM32CubeL4 MCU package within 32L4R9IDISCOVERY:
So, compare the provided code there with your code to figure out what is missed there.
Have a look at these resources that may help you with tips and the link to the videos:
2024-10-30 11:07 AM
More probable that you don't initialize the interface properly or construct a command structure for the peripheral.
You present NO code.
2024-10-30 11:28 AM
Initialize and interact with it like it's a MEMORY DEVICE
Don't assume you can blindly Transmit to it.
The Peripheral might have more capabilities, but the HAL is going to want more normative behaviour.
Look at code examples which illustrate normal command, address, data phase interactions.
The peripheral manages the NCS if you've initializes the thing properly, and interact with in normally.
See QSPI/OSPI examples within the CubeL4 libraries and BSP code
2024-10-30 05:57 PM
Sorry my mistake.
I forgot to post the code.
Since other interfaces on the board (USART, I2C, etc.) are occupied,
at this stage I can only judge the status of the team through the flashing of the LED light.
Here is a screenshot of my code:
There is an initialization part in the code,
and the light does not flash after powering on.
I think it means it is in the OSPI_STATE_READY state.
Regarding the instruction structure, I will try again.
Thanks!