About LCove.1

LCove.1 · 2021-04-23

Hi, I have an STM32F373. If I have the VREFSD+ tied to 3.3V and have it set to Forced Externally using VREF pin in the SDADC1 of the .ioc file, then the MCU will flash properly.However, if I disconnect VREFSD+ from the 3.3V, and set it to "Forced In...

LCove.1 · 2021-04-29

This is what I mean://hsdadc1.Init.ReferenceVoltage = SDADC_VREF_VREFINT1; //this is generated by .ioc (does not work) but it gets set to 256 in the debugger. hsdadc1.Init.ReferenceVoltage = 1; // this works

LCove.1 · 2021-04-29

So I found while debugging that it is setting hsdadc->Init.ReferenceVoltage to 256 when Vref is set to Forced Internally to 1.22V instead of 1.If it to Forced Internally to 1.8V, then it sets that Init.Referencevoltage to 512 instead of 2 (binary 10)...

LCove.1 · 2021-04-28

It is getting stuck insidestm32f3xx_hal_sdadc.cat this 2nd line here: SDADC1->CR1 &= ~(SDADC_CR1_REFV); SDADC1->CR1 |= hsdadc->Init.ReferenceVoltage;

LCove.1 · 2021-04-28

Now it is getting past Systemclock_Config() but it is now getting hung up inside MX_SDADC1_Init();

LCove.1 · 2021-04-28

Turns out I had to download STMCubeProgrammer, erase the chip, then it will let me re-flash the chip and debug. It is getting hung up on the SystemClock_Config();. Still troubleshooting why.

User statistics

User Activity

STM32F373 SDADC1 - VREFSD+ pin - STLink error when set to forced to internal 1.22V

Re: STM32F373 SDADC1 - VREFSD+ pin - STLink error when set to forced to internal 1.22V

Re: STM32F373 SDADC1 - VREFSD+ pin - STLink error when set to forced to internal 1.22V

Re: STM32F373 SDADC1 - VREFSD+ pin - STLink error when set to forced to internal 1.22V

Re: STM32F373 SDADC1 - VREFSD+ pin - STLink error when set to forced to internal 1.22V

Re: STM32F373 SDADC1 - VREFSD+ pin - STLink error when set to forced to internal 1.22V