2023-11-20 02:22 AM
I notice the delay block doesn't seem to be configurable for the OSPI peripheral in QSPI mode. Does any one know if it is still possible to use the delay block with a QSPI clock? I've tried coding the delay block a few different ways but it doesn't seem to work.
2023-11-20 03:04 AM
Which U5 device? What device in QSPI mode?
I've interfaced Winbond W25Q devices to several models of U5 boards without needing this.
U545 don't have OSPIM or secondary interface.
2023-11-20 03:18 AM
Hello @EvoFrank and welcome to the Community :),
For STM32U5 devices, the delay block is an independent peripheral that can be configured for the Octo-SPI interface.
I suggest you to check the DLYBYP bit of the OCTOSPI_DCR1 register.
-->I've tried coding the delay block a few different ways but it doesn't seem to work.
Could you please give more details about how you coded the delay block?
Are you using STM32CubeMx to generate code?
Thank you.
Kaouthar
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2024-04-03 05:56 AM
Hi All, Sorry for the delay in responding.
To clarify I'm using a U585.
--> Are you using STM32CubeMx to generate code?
I do not have the option of enabling the delay block in CubeMX if I configure the OSPI peripheral to work in QSPI mode. This makes me think that perhaps one cannot use the delay block in QSPI mode, see screenshot below:
I can manually modify the generated code for the OSPI peripheral from:
hospi1.Init.DelayBlockBypass = HAL_OSPI_DELAY_BLOCK_BYPASSED;
to
hospi1.Init.DelayBlockBypass = HAL_OSPI_DELAY_BLOCK_USED;
However, it seems that modifying OspiDLYBCfg.Units and OspiDLYBCfg.Phase doesn't seem to make any difference to whether data is Tx/Rx'd correctly at a given clock frequency.
2024-10-07 07:26 AM
Hi @EvoFrank ,
>I do not have the option of enabling the delay block in CubeMX if I configure the OSPI peripheral to work in QSPI mode.
I apologize for any inconvenience. Now, the Delay block configuration issue using STM32CubeMx toolchain is fixed in STM32CubeMX V6.12.0.
I think DLYB_OSPI_PSRAM_ExhaustiveTuning is interesting example.
Thank you.
Kaouthar
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.