OctoSPI delay block code unnecessarily generated

[tzijnge]

Hi Everyone,

I noticed that CubeMX (version 6.14.0) generates a call to HAL_OSPI_DLYB_SetConfig in octospi.c even though I have configured the OctoSPI to bypass the delay block.

1. Is it safe to just remove any Delay Block related code?
2. Is this a bug in CubeMX? It increases the code size, so I would like it to be removed if it's not necessary

My target is a Nucleo-U5A5.

 

Thanks!

Timon Zijnge

 

[KDJEM.1]

Hello @tzijnge,

 

Thank you for bringing this issue to our attention.

I reported it internally.

• Bypassed if DLYBYP = 1 (no phase shift effect on DQS signal strobe). You can remove the delay Block related code.
• Used if DLYBYP = 0 to phase-shift DQS if unit delays are enabled and configured.

Internal ticket number: 205608 (This is an internal tracking number and is not accessible or usable by customers).

 

Thank you.

Kaouthar

[KDJEM.1]

Hello @tzijnge ;

 

The STM32CubeMX issue is resolved in STM32CubeMX version 6.15.0. 

 

Thank you.

Kaouthar