Solved

I am using TouchGFX 4.24.0(The newest version). It does not seem to generate the newest version of code for STM IDE to use. I think this causing problems when I need to make changes between the script and the gui. Is there a way to change what version of code is generated?  I have no examples to show, other than it prompts me to "Migrate" to a newer version when I go to the IDE. When I start to make changes to the original gui it obliterates my code, Wigits go missing, screen flickers. I am using the board STM32H735G-DK.

Hi,On an Stm32f4 based board, we have the external crystal (8MHZ) mounted. The Firmware however uses HSI clock. Does the HSI drift have an impact on CAN communication with another device over a long period of time(say weeks)? Is it recommended to use HSE instead? Thank you in advance for your inputs.

Hi is the stack stm32wb5x_BLE_Stack_full_fw.bin and the one which we generating through cubemx(BLE Wireless stack Full) are same?

Hello!I'm using a 320x240 TFT display with ST7789V driver and SPI interface by X-CUBE-DISPLAY. Pixel transfer works correctly when I use the BSP_LCD_WriteData function. I can also display images and animation using the TouchGFX framework.However, when I use the BSP_LCD_WriteDataDMA function to perform the same process but with DMA, I encounter an anomalous behavior that I cannot explain.The code transfers the data successfully and the display show the image during the first execution. Then, on the second execution, the display suddenly turns off, blacking out all pixels, as soon as the BSP_LCD_SetDisplayWindow function is called. Despite this, neither the driver nor the DMA reports any errors. uint32_t Display_TransferData(uint8_t useDMA, uint8_t * data, uint32_t size) { uint8_t * ptr = data; uint32_t i = 0; while(i < size) { uint32_t n_byte = 65534; if(size < i+n_byte) n_byte = size - i; uint32_t ret; if(useDMA) { ret = BSP_LCD_WriteDataDMA(0, ptr

Hi,   i go to start SDMMC1 in STM32H753z, is any sample code? can please provide.   in SDMMC i need to use FATFS APIs or SDMMC APIs ? i am confusing please help me.   when i debug the below code i am can n't access it stop at f_mount() starting only. please provide how to use SDMMC.Thank You  

Hi, I am experiencing a problem on the STM32F411RET6 and STM32F411RCT6 MCUs. When programming these devices I am getting a repeated "Target is not responding, retrying..." message until the debugging session shuts down and exits. I have managed to narrow it down to the something related to the Main PLL. The MCU works if the 16MHz HSI RC clock or the 8 MHz HSE clock is selected as the System Clock Mux source, but fails with the "Target is not responding, retrying..." message if the PLLCLK is selected irrespective of whether the HSI or HSE is selected as the PLL Source.In a desperate effort I've also replaced the STM32F411 with a STM32L433RCT6 which pins are almost an exact match to that of the STM32F411. Using this MCU the PLL works as expected and I can use either the HSI or HSE as the PLL Source.I've attached the non-working STM32CubeIDE STM32F411 project which toggles pin PC8. Any assistance will be greatly appreciated. ThanksRenier

Hello everyone,I have recently been trying to get the CAN1 bus working on the STM32F427. So far, however, it has not worked in either loopback or normal mode. For the normal mode I had a CANCaseXL Analyzer available. The problem, however, is that not even the loopback works. I have attached the main.c file and the ioc project file.When I call HAL_CAN_AddTxMessage(), I get HAL_OK back, so that seems to work. However, I have set a breakpoint in the CAN interrupt handler (HAL_CAN_IRQHandler() in file stm32f4xx_hal_can.c) and there I see that the TERR0 bit gets set. Accordingly, the transmission process has failed. I have already tried many other possibilities, which unfortunately did not work either.Maybe someone has an idea. Many thanks in advance!Louis

Hi guys,I've trying to use the S2-LP DK v1.3.5 with the STM32L053R8 and STEVAL-FKI868V2.However, I can not open "COMx (ST DK)". The S2-LP DK shows  "Wrong firmware detected".I've flashed and uploaded the "S2LP_CLI_NUCLEO_L0.bin" but still shows same "wrong firmware detected" message.I've also downloaded the same firmware by using the IAR EW, but still have same message by S2-LP DK.Would please resolve this issue.I wonder the my board or the ST-Link driver for the windows 11 have some issues.Regards,- ChutaTheCat2024 

Hello! I'm new to STM32 hardware, and I'm having some difficulties getting it running on my Black Pill board with an STM32F411CEU6. It has both Read and Write Protection enabled, and I am trying to disable them using STM32CubeProgrammer through an STLINK V2. However, upon trying change option bytes, it gives me a weird error.For attempting to change read protection from value 0xFF to 0xAA it gives me this:16:24:25:038 : Error: Expected value for Option Byte "RDP": 0xAA, found: 0xFF 16:24:25:044 : Error: Option Byte Programming failed Or modified by application after OB_LAUNCH And similar story for trying to change the write protection values from true to false for all flash sectors: 16:26:41:386 : Error: Expected value for Option Byte "WRP0": 0x0, found: 0x1 16:26:41:391 : Error: Expected value for Option Byte "WRP1": 0x0, found: 0x1 16:26:41:395 : Error: Expected value for Option Byte "WRP2": 0x0, found: 0x1 16:26:41:399 : Error: Expected value for Option Byte "WRP3": 0x0, fou

Hello my friends,I am trying to setup an I2C slave that is being addressed with a read-request and then answers a fixed number of bytes. I was trying to find out what the XferOptions do, but after I could not find out I went through the HAL-driver code myself and found no location where they are actually being used. The basic procedure is, that interrupts are being generated by the hardware, set some flags, and in the TX-Slave part of the code, nowhere the XferOptions are used (am I right?). So I dont know what to do with them, just write anything in? Is this a "Bug" in that sense that the lib asks you for a parameter that is never being used? void HAL_I2C_AddrCallback(I2C_HandleTypeDef *hi2c, uint8_t TransferDirection, uint16_t AddrMatchCode){ if (TransferDirection == I2C_DIRECTION_TRANSMIT) // if the master wants to transmit the data { //HAL_I2C_Slave_Seq_Receive_IT(hi2c, &dummy_in, 1, I2C_FIRST_FRAME); RINGBUFFER_reset(); } else{ RINGBUFFER_dequeue(&data);

I am controlling a VN9D5D20FN high side driver with the SPI2 interface on an STM32F373.  I can communicate with the high side driver, and sometimes briefly get an output to turn on using SPI control.  However, frequently the high side driver sets the SPI Error bit in the global status byte, mask 0x20.I cannot determine why the high side driver is reporting a SPI error, and the datasheet is not clear on what causes that bit to be set (or at least I haven't been able to find it).  The datasheet is here: https://www.st.com/resource/en/datasheet/vn9d5d20fn.pdfOn page 23, it states:"The SPIE is a logical OR combination of errors related to a wrong SPI communication (SCKcount and SDI stuck at errors).The SPIE bit is automatically set when SDI is stuck at High or Low.The SPIE is automatically cleared by a valid SPI communication."So, it appears SPIE gets set if SDI is stuck High or Low, or there are not enough SCK counts when receiving (24 bits per SPI transaction).  From

Hello, I am trying to read battery voltage within a task called by sequencer on STM32WB55CEU.I am following this post: https://community.st.com/t5/stm32-mcus/how-to-use-the-stm32-adc-s-internal-reference-voltage/ta-p/621425I verified that I can measure both VREFint and Channel 10 separately in Single Mode, however combining 2 measurements in Scan mode does not work. I am not sure whats causing this, considering I am doing everything as recommended in the provided post. It may not be related to BLE. I must be missing something obvious.In the following code, the call to  /* * Rank 2: measurement channel */ stat = HAL_ADC_PollForConversion(&hadc1, 0xffff); uint32_t measurement_raw = HAL_ADC_GetValue(&hadc1); takes about 10 seconds and measurement_raw becomes same value as vrefint_raw. The Vrefint conversion seems ok.This is the whole code: void ADC_BattMonitor_Init(void) { HAL_ADCEx_Calibration_Start(&hadc1, ADC_SINGLE_ENDED); __NOP(); }

Hi,I have a custom master PCB connected to a few slave custom PCBs via serial. In some systems they are connected via I2C and in other systems they are connected via RS232.They all run STM32 micros.I am looking for two out-of-the-box protocols with source code available, one for the I2C and one for the RS232. They need to be very simple because only very little and simple data is exchanged (enable motor, change state machine state, turn LED on/off, etc) and none of it is time critical either.Which protocol would you suggest and where can I find the source code?Is there any such or similar solution provided by ST?Thank you :) 

     Hallo everyone,Since some time I struggle to get DMA access working on a STM32H723. I was pointed out this MCU is a complicated beast, but I would at least expect sensible, coherent documentation for it.When I look at page 683, I see:on next page: and on page 691:At the bottom of page 672 I read:These pieces of information confuse me: the register name in the headers are different from the ones in the Register Map, and it looks to me there is no register for 'DMAMUX2CRxC'.Further, when I run the debugger on an application that intends to use DMA on SPI3_Tx, I failed to read the registers mentioned above in the column "Live Expressions", because I didn't know the correct names. Although the column 'SFRs' show:combinations like: DMAMUX1_C2CR, DMAMUX_C2CR, DMAMUX1.DMAMUX_C2CR, etc. did not result in showing values. I find it quite an omission in the documentation that an user gets bits and pieces information andmust guess how to put it together to one coheren

Hi,Hope you are doing good.I am trying to transmit "AT" command using USART communication to SIM800A(SIM.COM). I am facing errors, should I write a separate GSM module. Thank you. 

Heyho,so I was just checking the MCO1 output of my STM32H733ZGT6 and found some super jittery 64 MHz with full swing between 0V and 3.3V.Then checked my code and found that I had not set the RCC->CFGR and not even initialized the GPIO.When I actually set it up it does what it should, but why is there such an output signal without the GPIO having been configured?This could be some serious EMI source or cause some other trouble if the GPIO is not yet configured, but connected elsewhere (I only have a serial R and a testpoint on my PCB).

I am using the VL53L4CD sensor board very similar to https://www.sparkfun.com/products/18993 with my application. I am using the modified version of https://github.com/stm32duino/VL53L4CD driver on the Raspberry Pico board. I am using the both the xshut and INTR pins. I am able to read the sensor ID and load the default configuration without any issues. However, the call to  VL53L4CD_CheckForDataReady times out in the SensorInit function. Also, in the function  VL53L4CD_SetRangeTiming, reading the osc frequency return 0, instead of non-zero. I have also compared the driver files with the https://github.com/STMicroelectronics/x-cube-tof1/blob/main/Drivers/BSP/Components/vl53l4cd/ . They seem to be identical except the platform functions. Please let me know what could be causing these issues?    

Hello,I recently bought a NUCLEO-F412ZG and shortly downloaded STM32CubeIDE.However, I only tried to debug and launch the generated program, without changing anything, and came across this error message :Checked the path, all is good. I can't seem to compile any project.Here are the logs from st-link_gdbserver_log.txt :[0.000] initConfigParams(): Configuration flags start[0.000] initConfigParams(): external-init false[0.000] initConfigParams(): pend-halt-timeout (null)[0.000] initConfigParams(): halt false[0.000] initConfigParams(): config-file ""[0.000] initConfigParams(): persistent false[0.000] initConfigParams(): +log-file "C:\Users\xxx\Documents\STM32\First\Debug\st-link_gdbserver_log.txt"[0.000] initConfigParams(): +log-level 31[0.009] initConfigParams(): +port-number 61234[0.009] initConfigParams(): +verbose true[0.009] initConfigParams(): refresh-delay 15[0.009] initConfigParams(): +verify true[0.009] initConfigParams(): +swd true[0.009] initConfigParams(): swo-port 61234[0.009

Hello,According to the manual , "This attribute, attached to a variable with static storage, means that the variable must be emitted even if it appears that the variable is not referenced."In the following code, unreferenced_variable is always discarded:static uint8_t unreferenced_variable __attribute__((used));There's no warning from the compiler.Is 'used' supported in principle please?Is there a problem with the syntax? 

HelloI am looking for an example to get the ADC regular sequence transferred by DMA to memory going.I use TIM15 to trigger the ADC regular sequence, which has four measurements, every 5 milliseconds. When I activate the EOS IRQ and toggle a GPIO I see that the four conversions are done. So that works fine.However, if I start the GPDMA to transfer the ADC data to an array it copies the same value to all four array elements. I added another GPIO toggle to the GPDMA transfer complete ISR and see on the scope that the ISR is happening after the third conversion. Also strangely enough, the DMA half transfer complete ISR starts after the first conversionOn the ADC I enabled DMA (CFGR.DMAEN = 1) and set it to circular mode (CFGR.DMACFG = 1)My GPDMA configuration is src/dest data width: HalfWord (CTR1.SDW_LOG2 = 1 / CTR1.DDW_LOG2 = 1)src/dest burst length: 1 (CTR1.DBL_1 = 0, CTR1.SBL_1 = 0)src increment: disable (CTR1.DINC = 0)dest increment: enable (CTR1.SINC = 1)BlockHwRequest: SingleBu

Hello everyone. I am currently working on a bootloader with a STM32H743VGT6.I need to write data on both banks which aren't continuous as you can see below:  It was recommended in this topic to use HEX format, but I need to stick to bin files. So my question is:Can I set all the data in the bin file from 0x0808 0000 to 0x080F FFFF to the value 0xFF?Or do I need to find an other solution? Like using two bin files (which I'd like to avoid). Thank you in advance for your help.Best regards,Sulian

Hey guys.I need to enable/disable the line 14 of the EXTI interrupts multiple times, using HALDo i just use the HAL_NVIC_DisableIRQ  HAL_NVIC_EnableIRQ  ( and HAL_NVIC_SetPriority whenever i re-enable the line?), providing the correct handle to the api each time?

Hello Community,I'm working on a project and could use your help. I'm trying to make a sine wave with a changing frequency from 600 Hz to 5 kHz using STM32 microcontroller(STM32L073RZT) with 32 MHz as sysclk. This are my configurations. Where this r2r pins are DAC bits.  I am not able to generate sine wave more than 280 Hz but i want to generate till 2 KHz. Please suggest if I'm doing something wrong or if anyone has a good idea on how to overcome this issue. Code: /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2024 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file * in the root directory of this software component. * If no LICENSE file comes with this sof

Hi,I have a project on Nucleo board with STM32U575ZIT6Q. I'm using STM32CubeIDE.My ADC worked fine until i did this:After migration HAL_ADC_Start function returns error.When I generate code I use this setting:What is wierd, is that if I unselect this box, and generate code then ADC starts to work again!Since I need to have those files separate I have to use previous Cube version.Is there something I need to do or this is a SW bug?Thanks.

I have a timer (TIM10) with a period of 500 us, running without interrupt or any other function.Then I have a rising+falling signal interrupt on PB0 (EXTI0) driven with a 31.25 kHz square wave.In EXTI0 I read the CNT value into a variable New, evaluate the difference with the previous CNT value Old (obviously considering the case when Old value is greater than New value) and copy the New into Old for the next EXTI0 interrupt.What I see is that many times the difference between New and Old, which should be about 16 us, is even 40, 80, 100 us or more!I've checked with a signal output on a pin and a scope that I have EXTI0 interrupts correctly every 16 us, without any interrupt loose or other strange behaviours.Seem's like sometimes (many times...) the CNT value read is not the current one but some strange old value.What could be the problem?Thanks