STM32CubeL4 v1.17.1 OSPI Delay Block Bypass Problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2022-03-09 11:18 PM
The latest versions of the STM32CubeL4 drivers (1.17.1) and CubeMX (6.5.0) introduce two bugs related to the OSPI and Delay Block Bypass.
- In stm32l4xx_hal_ospi.c line 383, the MODIFY_REG macro no long clears the DLYBYP bit. It also fails to set it according to the CubeMX configuration. I don't understand why these were removed.
- The CubeMX setting is using inverse logic. The setting is labeled Delay Block Bypass. Thus, Enable should indicate the bypass is enabled (HAL_OSPI_DELAY_BLOCK_BYPASSED), whereas Disable should mean disabling the bypass (HAL_OSPI_DELAY_BLOCK_USED). However, CubeMX reverses these values.
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2022-03-22 9:22 AM
Hello @ebray,
For the first point regarding the stm32l4xx_hal_ospi.c, I confirm the issue, an internal ticket is submitted, it will be corrected with the future release.
PS: Internal ticket 121187. This is an internal tracking number and is not accessible or usable by customers.
For the second point concerning the STM32CubeMX, I will let @Sara BEN HADJ YAHYA check it.
Thank you.
Chahinez.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2022-03-22 9:22 AM
Hello @ebray,
For the first point regarding the stm32l4xx_hal_ospi.c, I confirm the issue, an internal ticket is submitted, it will be corrected with the future release.
PS: Internal ticket 121187. This is an internal tracking number and is not accessible or usable by customers.
For the second point concerning the STM32CubeMX, I will let @Sara BEN HADJ YAHYA check it.
Thank you.
Chahinez.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2022-03-23 1:02 AM
Hello @ebray ,
Thanks for your feedback,
Issue confirmed from my side and I reported it to the dev team to be fixed. I will keep you posted with the updates.
Internal ticket number: 124989 (This is an internal tracking number and is not accessible or usable by customers).
Thanks @ChahinezC for flagging this to us.
Sara.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2022-06-29 3:00 AM
Hello @ebray ,
This issue is fixed in STM32CubeMX latest release.
V6.6.0 is now available under this Link.
Thanks for your contribution.
Sara.
