search

STMicroelectronics / STM32CubeF7

STM32Cube MCU Full Package for the STM32F7 series - (HAL + LL Drivers, CMSIS Core, CMSIS Device, MW libraries plus a set of Projects running on all boards provided by ST (Nucleo, Evaluation and Discovery Kits))
Other
322 stars 191 forks source link

QSPI times out on 32F769IDISCOVERY #52

Closed Jookia closed 2 years ago

Jookia commented 2 years ago

Caution The Issues are strictly limited for the reporting of problem encountered with the software provided in this project. For any other problem related to the STM32 product, the performance, the hardware characteristics and boards, the tools the environment in general, please post a topic in the ST Community/STM32 MCUs forum.

Describe the set-up

I'm using the 32F769IDISCOVERY board and upstream Mbed OS.

Describe the bug

The HAL_QSPI_Transmit sometimes times out instead of returning data.

How To Reproduce

I've listed details on how to reproduce this at https://github.com/ARMmbed/mbed-os/issues/15108 , the place I reported this issue to in the first place. In summary, it's just using the QSPIFBlockDevice on Mbed OS and running it until it fails.

Additional context

This bug is strikingly similar to https://github.com/STMicroelectronics/STM32CubeF7/issues/6 . So much so that the fix works too.

Screenshots If applicable, add screenshots to help explain your problem.

N/A

RKOUSTM commented 2 years ago

Hi @Jookia,

Thank you for your report. This point will be forwarded to our development teams for analysis. We will be back to you as soon as we get feedback.

Thank you again for your report.

With regards, Rihab

RKOUSTM commented 2 years ago

Duplicate of #6.

RKOUSTM commented 2 years ago

Hi @Jookia,

Thank you for your report. This duplicated issue will remain closed. The reported issue #6 will be kept open to track the point.

With regards,

jeromecoutant commented 2 years ago

Thank you for your report. This duplicated issue will remain closed. The reported issue #6 will be kept open to track the point.

6 is closed with STM32CubeF7 v1.16.0

whereas #52 has been opened with STM32CubeF7 v1.16.1

I think you should re-open this one...

Jookia commented 1 year ago

I've opened another bug report at #82 since this is still active sadly.