Solved

I have attached a picture of the compiled code.

Status from reads: WUTE is enabled, WUT shows what I set, RTC is enabled, and the WUTF flag is correctly being set every so often (and manually being cleared during GPIO interrupts I'm troubleshooting with).What's not happening: The EXTI interrupt is not being fired; the device is not waking up from sleep. It can be woken up from an EXTI fired from GPIO. This is hopefully enough to narrow it down: The RTC wakeup timer itself is working, but it's not triggering the interrupt. What needs to be accomplished to fix this? It should trigger the interrupt once WUTF gets set.WUT setup steps:Enable the RTC and setup/enable LSEDisable write protectionclear WUTEwait until WUWTF is setset timeout in WUT and WCKSELSet WUTEEnable write protectionInterrupt setup steps. Note that this works for GPIO interrupts:Unmask imr1's mr20 field (20 should be RTC wakeup)Enable rtsr's tr20, and disable ftsr's tr20 (Set rising trigger)unmask the NVIC RTC wakeup IRQ channelSetup an EXTI interrupt handler functionTh

Here is a noodlescratcher for you all.Take a nucleo-334R8 board. Start a new project with CubeMx. Set it up to be HSE bypass, into the PLL with x9. Just to make it a bit more fun, set the bypassed clocksource to be 7 mhz. Add the MCO and divide it down so you can inspect it with whatever tool you have. Make sure that clock security is NOT enabled. Now start and run your code.Strangly, the board will work fine even after SystemClock_Config(). When you inspect the MCO at PA8, you will find ~72 mhz there.Surly it must be the HSI that has "contaminated" the pll... right?Is there any way to circument this? I tried to stop the HSI with LL_RCC_HSI_Disable(); and the MCO still kept throwing out a 72 mhz clock.RegardsMartin

Hi, All. In the wiki, the process to program the PKH into the OTP is done with stm32key tool in u-boot. Also, PKH file must be available in a filesystem partition. All these tasks need to be done manually...Is it possible to do this same process from sysfs? My idea is to be able to automate this task in a script.

Hi,all!In the wiki about secure boot, only FSBL and SSBL files are signed and authenticated.It would be very interesting and useful if you could also sign and authenticate the kernel and increase security.Is this possible?

I wrote I2S Loop back test program. I2S2 as Master Transfer mode and I2S3 as Slave Receive mode. (Proto for ADC in and DAC out.)It works OK when 16bit in 16bit frame. However, in 24 bit in 32bit frame, DMA pointer etc. are corrupted.With step-by-step trace, I found crushing point in stmf4xx_hal_i2s.c.Is this BUG or my program is wrong???Many thanks in advance, K.A.Gist of the program is below and screen shot of IDE is attached.int main(void) { .... HAL_I2S_Receive_DMA(&hi2s3, (uint16_t *) ADC_Data, (uint16_t) (BUF_LEN*2) * 4) ; // (16bit*2)*stereo*double buffer   while (1) { while ((&hi2s2)->State != HAL_I2S_STATE_READY) ; if (HAL_I2S_Transmit_DMA(&hi2s2, (uint16_t*) Out_buf, (uint16_t) (BUF_LEN*2) * 2) != HAL_OK) { Error_Handler(); } } }   /********** call back **********/   void HAL_I2S_RxHalfCpltCallback(I2S_HandleTypeDef * hi2s3) { ADC1_ptr = BUF_LEN*2 ; }   void HAL_I2S_RxCpltCallback(I2S_HandleTypeDef * hi2s3) { ADC1_ptr = 0 ;

Hello all,I want to disable the timer interrupt in the IRQ Handler and then enable again in the main loop. However the interrupt is triggered nearly immediately after I re-enable the interrupt (setting the UIE bit). I attached my code below. If I disable and enable the counter instead of just the interrupt then the code runs correctly. Why is that? I have tried to set the TIM_CR1_URS but no avail.void MX_TIM2_Init(void) { TIM_ClockConfigTypeDef sClockSourceConfig = {0}; TIM_MasterConfigTypeDef sMasterConfig = {0};   htim2.Instance = TIM2; htim2.Init.Prescaler = 0; htim2.Init.CounterMode = TIM_COUNTERMODE_UP; htim2.Init.Period = 3333; htim2.Init.ClockDivision = TIM_CLOCKDIVISION_DIV1; htim2.Init.AutoReloadPreload = TIM_AUTORELOAD_PRELOAD_DISABLE; if (HAL_TIM_Base_Init(&htim2) != HAL_OK) { Error_Handler(); } sClockSourceConfig.ClockSource = TIM_CLOCKSOURCE_INTERNAL; if (HAL_TIM_ConfigClockSource(&htim2, &sClockSourceConfig) != HAL_OK) { Error_Handler();

As mentioned above I can't connect as the watchdog is continuously going off. I used the STM32CubeMx to enable the IWDG and it created the s/w load which enables the IWDG but doesn't refresh it. I know how to fix it in the s/w but my debugger under TrueStudio won't connect to load the new image. My board is continuously resetting.Have I bricked my board or is there some s/w tool I can use to erase the board? Remember I am running on linux.Thanks in Advance for any help.Cheers!!

Hi,Can ST-Link be used to program both M0 and M4 cores? Also if the controller in STLink is replaced with STM32WB55RG can the driver for STLink be customized or does it require a new driver development? Is the driver open source? If yes, on what format will it be?

Hi, I am using an STM32L4 Discovery kit and using VS Code on Windows 10 for development and using CMake to build the application. I have all the setup done using CMake. I now need to include the different mems middleware for calibration and need to know where I can find the source (not just the libraries) to include them if it is open source. Thanks.

Pin MODE for peripherals are set incorrectly with RSVD instead of correct alternate function definition (AF13).When building uboot it failed because pin Mode "RSVD" is incorrectly defined.e.g code from device tree   m4_dcmi_pins_mx: m4_dcmi_mx-0 {        pins {            pinmux = <STM32_PINMUX('A', 6, RSVD)>, /* DCMI_PIXCLK */                    <STM32_PINMUX('E', 0, RSVD)>, /* DCMI_D2 */                    <STM32_PINMUX('E', 1, RSVD)>, /* DCMI_D3 */                    <STM32_PINMUX('F', 11, RSVD)>, /* DCMI_D12 */      &nbsp

I've been trying to use the TIM2_CH1 function for PA15 but without success on a Nucleo-L073RZ. This function works OK on pins PA0 and PA5. Also PA15 works if set in GPIO output mode.Errata document does not state anything about this pin.Could you confirm?

Hello. I'm using VL53L1X sensor with Ultra Lite Driver (ULD). VL53L1X_GetRangeStatus function returns all the time status 13. This value comes from the array "status_rtn".Where can I find info about the meaning of these values?What does status=13 mean?Regards

Hi,I am trying to use motor profiler 5.4.4 with B-G431B-ESC1. Every time, Electric model reaches 30 percent quickly and then gradually reaches 38 percent to get the 'too much time' warning after which process fails.I tried different BLDC motors (12 pair-400KV, 7 pair-1900kv)and also tried different supply voltage(12V, 16V, 25V). However result is same. I can also see few other posts which mentions about similar issue, however, they have not been answered. Any help to resolve this is much appreciated.

I am trying to find maximum data rate supported by SPC582B60X, no data is given in datasheet is there any relation by which i can calculate data rate? and what will be the CAN controller clock speed?please suggest

Hi,Using STM32G474RE board (Nucleo-64). I have tried a lot of different things to configure VREFBUF and none of them have any effect.I'm outputting two voltages on DAC1 at 75% scale and 25% scale and they are always relative to approx 3.25V (which is what I see on the VDDA pin). I wanted to see if I could observe e.g. DAC using VREF of 2.048v (or any of the configurable voltages).I've tried setting the VRS, HIZ and ENVR bits directly and I've also tried the LL_VREFBUF_* calls. I have the SYS/VREFBUF Mode set to "Internal voltage reference" in the Device Configuration Tool. None has any effect. I am using the STM32CubeIDE.In fact I would really like to configure this pin as external reference for my application but I can't achieve that either.Any clues? Thanks.

Hi,I recently booted the IDE but forgot to set my mobile phone as a hot spot. Now IDE looks for Information Center on HDD.

..

If I perform like a stupid User (write Tag and before the message is published i remove it from the Tag), I am able to get an error message from the NFC-Tag. It's something like "Tag I/O-Error" or "Tag I/O-Error, Tag is not ndef". So if this happens many times in a row, i am not able to write,read,format or clear the Tag via NFC again. Not with my Phone-App or with "NFC-Tools". I am only able to reset it via I2C on the Microcontroller. If I want to get Information from the Chip, it says "Capacity 0/0Bytes" so it's not accepting any order. My Question now is, why does this happen and is there a way to Reset the tag via NFC? Did anybody else have this problem before?

Hello,I am designing an e-meter based on the STPM32. I will be measuring current through a shunt resistor. According to the evaluation board gerbers, the shunt should be on the low side and connected to the Neutral line. Is that correct? Should the PCB ground be connected to the Neutral as well?Is it possible to connect it to the high side?Thanks.

I want to exchange large data buffers with the coprocessorI have tried following wiki page.​https://wiki.st.com/stm32mpu-ecosystem-v1/wiki/How_to_exchange_large_data_buffers_with_the_coprocessor_-_principle#User_space_interface​I tried to bitbake, but I have an error.​= Steps =​$ cd [my Distribution Package Directory Path]/layers/meta-st/$ git clone https://github.com/STMicroelectronics/meta-st-stm32mpu-app-logicanalyser.git -b dunfell​$ DISTRO=openstlinux-weston MACHINE=stm32mp1-demo-logicanalyser source [my Distribution Package Directory Path]/layers/meta-st/scripts/envsetup.sh$ bitbake st-image-weston​= Error =ERROR: Layer stm-st-stm32mp-app-logicanalyzer is not compatible with the core layer which only supports these series​​Are there missing something in my steps?​Best Regards.H Masuda

I am developing on the STM32H7B3i-DK board using Keil MDK + STMCubeMx for creating the project.For some bizarre reason that I can't explain, I can no longer do debugging on my dev board after been blocked for a few days by an issues that I had with "option bytes". Now the option bytes issue was resolved I tried to continue with my debugging only to discover that I can not longer do debugging on the board which was kind of working.Every time I run the debugger it seems to crash in the following function. The value passed in the SupplySource parameter is PWD_LDO_SUPPLY.HAL_StatusTypeDef HAL_PWREx_ConfigSupply (uint32_t SupplySource) { ,,, /* Set the power supply configuration */ MODIFY_REG (PWR->CR3, PWR_SUPPLY_CONFIG_MASK, SupplySource); ,,, }Once the code tries to execute the line MODIFY_REG(PWR->CR3, PWR_SUPPLY_CONFIG_MASK, SupplySource) it crashes with the following dialog box messageAt which point I can no longer continue with the debug session other than to power cycle th

I see that H723 and variants are coming.Any plan for Nucleo or discovery kit for these?

Hello community,after unsoldering the solderbridges of the STM8S-Disco-Board, I try to connect the SWIM to a STM8AF Chip. I read in the manueal, that this is not possible (only for STM8S-Family). But after trying it, I could flas Code on the µC and Debug it with the STVD. For example, a counter in my programm ist counting up :)But if I want to switch Timer1-Output-Pin from LOW to HIGH, nothing happens.Is ist possible,, that I can program the µC and it is running without errors, but the mapping of the GPIOs are not correctly done? Is there a influence of the SWIM-adapter even if I had chosen the STM8AF-Chip in STVD?Thank you all, Steffen

does it matter in mono operation whether I connect pin L/R to GND or to 3v3? Or does the pin always have to be open or to GND in mono mode?Of course, my output signal has to be evaluated differently, but nothing can be damaged from an electrical point of view?Thanks