Closed sgauche closed 1 year ago
ST Internal Reference: 156227
Hi @sgauche,
To ensure that the SPI does not initiate a new transfer you should call HAL_SPI_DeInit()
and HAL_SPI_Init()
before starting a new master receive. This is actually mentioned within the the stm32f4xx_hal_spi driver in the section "How to use this driver".
Would you please thus make sur that you are executing these instructions in your code.
With regards,
Hi @sgauche,
Please allow me to close this thread as no activity. You may reopen it at anytime if you have any details to share with us in order to help you to solve the issue. Thank you for your comprehension.
With regards,
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 your report to the ST Community in the STM32 MCUs dedicated page.
Describe the set-up
Describe the bug (skip if none)
When using SPI in half-duplex mode, the SPI is not disabled at the appropriate time during a read as described in RM0090 Section 28.3.8 so an extra transaction is started.
How to reproduce the bug (skip if none)
call HAL_SPI_Receive after a HAL_SPI_Transmit with hspi->Init.Direction == SPI_DIRECTION_1LINE
Additional context
Screenshots