search

STMicroelectronics / STM32CubeWB

Full Firmware Package for the STM32WB series: HAL+LL drivers, CMSIS, BSP, MW, plus a set of Projects (examples and demos) running on all boards provided by ST (Nucleo, Evaluation and Discovery Kits).
https://www.st.com/en/embedded-software/stm32cubewb.html
Other
227 stars 138 forks source link

P-NUCLEO-WB55.Nucleo\Examples\ADC\ADC_SingleConversion_TriggerTimer_DMA is fake #11

Closed fs34a closed 3 years ago

fs34a commented 4 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

Describe the bug Like the title, this example is fake. It is supposed to use TIM2 triggering ADC conversion via DMA, but the truth is this is a ADC software trigger ADC DMA continuous conversion. They are very much the different. If you remove TIM2 totally, ADC DMA is still running. So this example is totally fake. Yet this example is very important as many users need A timer to trigger ADC in certain period. Please correct this example. Thanks.

How To Reproduce

  1. Indicate the global behavior of your application project.

  2. The modules that you suspect to be the cause of the problem (Driver, BSP, MW ...).

  3. The use case that generates the problem.

  4. How we can reproduce the problem.

Additional context If you have a first analysis or patch correction, thank you to share your proposal.

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

ASELSTM commented 4 years ago

Hi @LockeKK,

In order to allow a better understanding of the problem, could you please give us more details about the issue and how to reproduce it, so that our development teams can give you an answer.

With regards,

fs34a commented 4 years ago

This example intents to use HW timer TIM2 triggers ADC in DMA mode. But in fact, the ADC is triggered by Software rather then TIM2's TRGO update event. You can find this in the ADC configures. You can totally remove TIM2, ADC is still working. Just run this project you will find how to reproduce it.

ASELSTM commented 4 years ago

Hi @LockeKK,

Thank you for your contribution.

The issue has been confirmed and an bug tracker has been opened internally. A fix will be implemented and made available in the frame of a future release. Thank you once more.

With regards,

ASELSTM commented 4 years ago

ST Internal Reference: 93065

fs34a commented 4 years ago

Good, thanks for your support. I will close this ticket.

ASELSTM commented 4 years ago

Reopened till the fix is released on GitHub.

ASELSTM commented 3 years ago

Hi @LockeKK,

I hope you are fine. The issue you reported has been fixed in the frame of version v1.10.0 of the STM32CubeWB published recently on GitHub.

Thank you again for having reported.

With regards,

fs34a commented 3 years ago

Hi @LockeKK,

I hope you are fine. The issue you reported has been fixed in the frame of version v1.10.0 of the STM32CubeWB published recently on GitHub.

Thank you again for having reported.

With regards,

Thanks for your support.