Solved

Dear all!this is the first time i design PCB for STM32H755, as my understand for direct SMPS that i design like attach file, really i don't know is it correct, so can you help take look and let me know if any mistake.

Hi :I want to switch my project from HAL to LL because of flash size.But SPI doesn't work after switching.When I using HAL, the code below in main function works fine, uart will print OK.When I switch to LL, it will print NG.After switching to LL, I already add LL_SPI_Enable(SPI1); to MX_SPI1_Init function.Cubemx project and all code is as attachment. uint8_t data = 0x80; CS_GPIO_Port->BSRR = (uint32_t)CS_Pin << 16u; #ifdef USE_HAL_DRIVER HAL_SPI_Transmit(&hspi1, &data, 1, 100); HAL_SPI_Receive(&hspi1, &data, 1, 100); #else while (!LL_SPI_IsActiveFlag_TXE(SPI1)); LL_SPI_TransmitData8(SPI1, data); while (!LL_SPI_IsActiveFlag_TXE(SPI1)); LL_SPI_TransmitData8(SPI1, 0xff); while (!LL_SPI_IsActiveFlag_RXNE(SPI1)); data = LL_SPI_ReceiveData8(SPI1); #endif CS_GPIO_Port->BSRR = CS_Pin; if(data == 0x05) { while (!LL_USART_IsActiveFlag_TXE(USART2)); LL_USART_TransmitData8(USART2, 'O'); while (!LL_USART_IsActiveFlag_TXE(USART2)); LL_USART

Hi, I am using an STM32U5A9ZJT with LTDC L8 buffer and cannot select GPU2D, is support for L8 being added soon?Being able to use L8 and vector fonts would be ideal for storage savings. I also noticed that the "hardware" option for vector rendering is available on the STM32U5A9, isn't this a feature of the NeoChromVG of the STM32U5G9? Can I use L8 images in touchgfx when using an RGB565 buffer? I tried this and it works in the emulator but crashes on device. 

I am following the "How to deploy SSP using a step-by-step approach". I am working on "3.1.2.2. Secret file content for STM32MP2 series". The target MPU is STM32MP257F. I have some questions as below:1. How do I know whether to choose "Format 1" or "Format 2"?2. I selected the binary file as FIP-EDMK, which is 256-bit but the KeySize shows 128-bit and it won't let me select 256-bit again. Is this acceptable?   

Me 2, having the same issue as STM32C011 QFPN20 not able to be programmed using stlink-v2   moved from this post.

Hello, I'm trying to use the HAL function to calculate a file MD5 on my STM32H750 MCU. I successully managed to calculate the MD5 of little files using HAL_HASH_MD5_Start. Now I want to calculate the MD5 of a large file, so I'm not able to store all the file content in RAM. How to use the HAL functions to calculate the MD5 in chunk? Thank you in advance,Matteo

Hi, I have a problem with pinging PCs with my adapter USB-Ethernet with an STM32F207. I'm currently working with CDC-ECM for Ethernet-Over-USB. First case: I have 2 VMs with Linux on them. The USB is connected to the first VM (VM1) and the Ethernet is connected to the second (VM2). I can ping VM1 with VM2 but I can't ping VM2 with VM1.Second case: I have one VM with Linux and a Windows machine. The USB is connected to the VM and the ethernet is connected to the Windows machine. When I ping the VM with Windows or Windows with the VM I have only loss packets... Does someone have any idea why ?Thanks,

Hello ST Community, I’m a student with a strong interest in embedded systems, particularly with STM32 microcontrollers. I aspire to become a driver developer for STM32 platforms and would like to learn how to write peripheral drivers from scratch by deeply understanding STM32 datasheets, reference manuals, and hardware architecture. I’m looking for recommendations on: Training institutes (preferably in India) that provide in-depth, hands-on training on low-level driver development for STM32 (not just application-level programming). Online platforms or courses (paid or free) that focus on writing bare-metal STM32 drivers using CMSIS or directly accessing registers. Any structured learning paths, books, or resources you personally found valuable on this journey. If anyone has gone through this learning process or knows mentors or institutions offering such training, your guidance would be highly appreciated. Thank you in advance for your support.

I am having issues with the STM32G0 ADC measurements. I am trying to measure 2 voltages:1. 3.3V2. 12VAfter the voltage divider, the 3.3_adc and 12v adc pins are connected to the MCU pins directly:3.3_adc - PA3 (ADC1_IN3)12v adc - PA7 (ADC1_IN7)My STM32CubeMX configuration for the ADC is as following:VREFBUF Mode is configured as External voltage reference:Because we have 2.5V connected to the VREF+ pin of the MCU and we want to use it as the ADC Reference Voltage, see the schematic below:I have measured the voltages with the Multimeter on VREF+, +3.3V and +12V, and all of them are correct and as expected. I have also measured the voltages using multimeter after the Voltage divider and I measure as following:3.3_adc - 0.275V (if I apply voltage divider, I get 3.3V precisely)12v adc - 0.508 (if I apply voltage divider, I get about 11.6V. This is expected voltage on this pin as it has some diode connected on this line hence its not actually +12V)My code is as following:/* USER CODE BEGIN

Hi, I'm working on a project in MC Workbench 6.3.2 and trying to configure a motor with a maximum speed of 150 RPM. When I set the "Max. Application Speed" parameter to 150 RPM (as shown in the first picture), I encounter an error related to the "Speed Sensing Configuration". I've attempted various parameter combinations for the Hall Sensor settings (as shown in the second picture), but haven't resolved the issue. Could you please advise on how to fix this problem? Thank you for your help.

hi all,I'm Trying to send a string from STM32F401RE MCU to EPS32 Via UART i have programmed both STM as well as ESP32 and i successfully verified that data is available on UART pin of STM  Data on UART Pins of STMBut I'm not able to receive data on ESP32, i double checked the UART Hardware connection is correctand i configured STM UART in TX_ONLY mode , did not configure any hardware flow pins ,baudrate is 9600,1 stop bit and not using parity  ESP32 UART RX I'm receiving some Garbage value on Arduinocan anyone please help me with the UART message not Receiving in ESP32

Been working on the Nucleo H5 dev board for about a month.  Everything with the built-in ST-Link/V3 was fine until randomly yesterday, the board would no longer get out of reset when the ST-Link is powered.   Board powers up and boots if getting power from the USB-OTG port AND the ST-Link is unplugged.  Tried with STProgrammer and GDB in VSCode debugger, neither can connect to the target chip.  To be clear, the STLink enumerates and works OK, but the MCU is held in reset state.   Board is held in reset state when ST-Link gets power/host connection.  Attempting to flash the board always gives "Reason: Target held under reset.".   All solder jumpers and physical jumpers are in the default positions   Fixes I've tried: Any set of settings via the STProgrammer, including Soft Reset, the "under reset" connection type, etc.  Any time STLink is powered from host, the board is held reset and will not connect still. Updating the STLink/V3 drivers/fi

I've been playing around with an STM32F7508-DK, and I was successfully programming hex files with CubeProgrammer and running the application. I eventually tried doing a "Full chip erase", and now when I program the hex files that were working previously, the application does not seem to boot. There are no error messages from CubeProgrammer, just the application hanging at the "white screen".How can I recover the dev kit?

Hi. Last week I received my first STM32U5A5 board and tried to implement USBX HID standalone mode, following this tutorial. Guess what? I managed to make it work and It just works very well! I should call  USBX_Device_Process(NULL); in the main loop so the STM32U5A5 serves as USB HID device. My question is that, is it appropriate to call USBX_Device_Process function in the main loop, while the USB polling rate is 1000 Hz (depending on settings)? When debugging, that function is called multiple times per milliseconds and I'm worrying about some malfunctioning due to the excess of USBX_Device_Process calling.  Or is it totally fine repeating  the USBX_Device_Process function without carefully configured timers or fitting the timing into the polling rate? Thanks in advance!

Hello STIm trying to generate a HSO compatible FOC board using the STM32G747CEUx but I am not able to select the HSO option for Speed sensing.I've seen the requirement of using atleast two different ADCs for the current sensor and voltage measurementTherefor I have assigned ADC1 and ADC2 for current measurementAnd ADC3, 4 and 5 for voltage measurementBut I am not getting a solution for this.Here is my json design fileThank you"mcu": "STM32G474CEUx", "clockFrequency": 170, "motorDrives": [ { "name": "M1", "minRatedVoltage": 16.9, "maxRatedVoltage": 60, "maxRatedCurrent": 80, "maxRatedPower": 2000, "features": [ { "type": "CurrentSensing", "name": "CurrentSensing", "hwVariants": [ { "signals": { "CURRENT_AMPL_U": [ { "name": "PA0", "help": {}, "cost": 0 } ], "CURRENT_AMPL_V": [ { "name": "PA1", "help": {}, "cost": 0 } ], "CURRENT_AMPL_W": [ { "name": "PA2", "help": {}, "cost": 0 } ] }, "type": "ThreeShunt_AmplifiedCurrents", "cost": 0, "amplifyingN

Hello,I am working on the STM32H745ZITx platform and using both CM7 and CM4 cores with FreeRTOS. I am trying to run a TCP server on the CM7 core using LwIP.However, when I call the accept() function, the system seems to hang. Specifically, after accept() is called, none of the tasks on the CM7 core continue to run — it appears as if the RTOS scheduler has crashed or is blocked.I have reviewed the example from this repository:STM32H745_Nucleo_M7_ETH and followed the STM32H745_Nucleo_M7_ETH project structure closely.Do you have any suggestions or guidance on what else I should check? Could this be related to interrupt priority, improper memory configuration, or something else I may have overlooked?I would appreciate any help or insights you can provide.Best regards,Kemal UZGOREN

I am using the latest (pre-release, version 3.something) official extension, on Linux.Creating a new empty project went fairly smoothly (see my other form post about missing CMSIS headers), but when I tried to build the project, cmake couldn't find the toolchain.It turns out that cmake was trying to run "arm-none-eabi-gcc" and so on, assuming that they would be in the current PATH!  In fact, these executables are bundled with the extension and (on my Linux system) are located in~/.local/share/stm32cube/bundles/gnu-tools-for-stm32/13.3.1+st.8/binNo one (at least on Linux---not sure what Windows users do these days) is going to want to modify their system path to add a weird bin directory just for a single application.  The right way to tell cmake where to find the tools is to either modify *its* environment or give it full paths to each tool.  But the extension did not do this when it was installed---I think that is a bug because it is easy to automate.Complicating matter

I'm investigating 2.5Gb Ethernet PHYs for our STM32MP257D board.  Most, if not all, require SGMII which is not explicitly supported in the ST MPU documentation.Anyone been down this road?Anyone know of a compatible 2.5Gb PHY that can use the STM32MP2xx RGMII?Thx

Configure STM32G0 to sample 11 channels; When voltage is injected into only one channel each time, the sampling values of all channels are correct. When voltage is injected into 11 channels simultaneously, the sampling values of all channels are incorrect and random values are displayed. Could someone help me explain the reason for this problem and how I should configure it? Thank you.

There are three types of sensor in vl53l8 family, VL53L8CA, VL53L8CH and VL53L8CX. It seems like sensor in X-NCULEO-53L8A1 is VL53L8CA, but the relevant documents and resources are very few. so what should i read as a reference? what is the diffrence among the three sensors?

The following line of code is generated by CubeMX v6.14.0.202502271554 for a STM32G070RBTx using FW Package v1.6.2:LL_ADC_SetCommonPathInternalCh(__LL_ADC_COMMON_INSTANCE(ADC1), LL_ADC_AWD_CH_VREFINT_REG|LL_ADC_AWD_CH_TEMPSENSOR_REG);The constants used are for the Analog Watchdog in ADC_CFGR1 and have no relation to the internal path configuration in ADC_CCR.  This can configure the wrong internal paths and change the ADC clock prescaler.As stated in the function description, the constants should be one of the following: * @PAram PathInternal This parameter can be a combination of the following values: * @arg @ref LL_ADC_PATH_INTERNAL_NONE * @arg @ref LL_ADC_PATH_INTERNAL_VREFINT * @arg @ref LL_ADC_PATH_INTERNAL_TEMPSENSOR * @arg @ref LL_ADC_PATH_INTERNAL_VBAT Regards,

 Hello,I am currently using the STM32L496 microcontroller in a product design. In this design, I use PC1 as an output to control the EN (enable) pin of a TPS78228 LDO. I'm encountering an issue where the LDO exhibits unexpected behavior when EN is driven low by the STM32. Setup Details:There is a 470 kΩ pull-down resistor between PC1 and the EN pin.A 4.7 µF capacitor is connected to VOUT, as recommended.When I manually pull EN directly to GND (bypassing PC1, when STM32 is powered-off), the LDO shuts down correctly, with VOUT dropping to 0 V.However, when STM drives PC1 low, the EN pin voltage appears close to 0 V, but VOUT remains at 1.8 V.Vin is within the recommended range and remains the same in both cases. I’ve attached two scope captures showing two different behaviors. In both:Blue = VEN (EN pin voltage)Orange = VOUT (LDO output)In Figure 1 STM32 is not in use and I manually drive the enable pin to the GND and to VCC interchangeably. As expected, VOUT drops to

Hello,I am beginning development with MCUs, am new to this.  At the moment, I am at the design stage.I have identified a device which seems most suitable for my application, STM32G0B1CET in this case.I am trying to understand the I/O constraints.  I would like to be able to, once in a while, use the bootloader to update firmware in-system.On this particular device, If I understand correctly, the bootloader is designed to use any of a long list of peripherals (two USART, two I2C, two SPI, USB, and FDCAN) - and it accordingly configures the device for this purpose.This appears to very seriously constrain how the pins may be connected on my board (to avoid unwanted interaction or conflict during the boot phase).So it seems that, even if "naively" the device has enough I/O for my application, many of them can't be used just because of how the bootloader (even temporarily) configures them.What am I missing?Thank you.

Hello ST Team and Community,I’m working with the X-NUCLEO-IHM07M1 board for 6-step sensorless BLDC control, and I need some clarification regarding the purpose and correct use of the GPIO_BEMF pin.In this ST Community answer, it is mentioned:"The GPIO_BEMF pin is provided to manage the BEMF sampling during the PWM ON state for 6-Step control only."I understand that this refers to enabling the BEMF voltage divider (e.g., 10k/2.2k) to bring phase voltage into the ADC range during PWM ON time. However, on the X-NUCLEO-IHM07M1, it seems that even during the PWM OFF time, if GPIO_BEMF is not pulled LOW, the voltage divider is disconnected (floating bottom resistor), and the BEMFx signal becomes unreliable or unusable for ADC reading.So my question is:Do we also need to pull GPIO_BEMF LOW when sampling BEMF during the PWM OFF-state (e.g., mid-off-time) in order to enable the voltage divider and get a proper ADC reading?If not, how is the ADC expected to receive a reliable voltage at BEMFx wi

Platform: linuxSteps to reproduce:+ Create a new STM32 Project- Select Board->H753ZI - STM32Cube FW_H7: V1.12.1- copy only the necessary library files and finish+ Select board options all+ Software Packs | Select Components | X-CUBE-AZRTOS-H7 3.4.0 | RTOS | ThreadX | Core (6.4.0): Enable+System core | SYS  | Timebaser soruce: TIM6- Middleware and Software Packs | X-CUBE-AZRTOS-H7 | RTOS ThreadX: Enable- Middleware and Software Packs | X-CUBE-AZRTOS-H7 | RTOS ThreadX: Enable | Core Init: check| Application Thread:TrueSave ioc, generate code and build22:36:05 **** Build of configuration Debug for project h7_tx_3.4.0_iter02 **** make -j4 all arm-none-eabi-gcc -mcpu=cortex-m7 -g3 -DDEBUG -DTX_INCLUDE_USER_DEFINE_FILE -c -x assembler-with-cpp -MMD -MP -MF"Middlewares/ST/threadx/ports/cortex_m7/gnu/src/tx_thread_context_restore.d" -MT"Middlewares/ST/threadx/ports/cortex_m7/gnu/src/tx_thread_context_restore.o" --specs=nano.specs -mfpu=fpv5-d16 -mfloat-abi=hard -mthumb -o "Middle