STM32 MCUs

We need further clarification regarding the difference between the above ICs.We recently purchased the mentioned STM32 MCU, but received two different variants. In one IC, the ST logo on the right side has the marking “e3” with “L” outside the circle. In the other IC, the ST logo on the right side has the marking “e4” with “L” outside the circle.Kindly clarify the difference between the “e3” and “e4” markings and confirm whether both ICs are equivalent in specification and performance.

I am developing a device that implements the USB device class.According to application note AN4879 "Introduction to USB Hardware and PCB Design Considerations Using STM32 Microcontrollers" it is written as follows:Based on the USB specification, a USB device must use VBUS sensing detection. When the device detects the host presence, it connects its pull-up resistor to either a D+ or D- data signal. This allows the host to detect the device presence on the bus. There are two cases: • The USB device is bus-powered. VBUS sensing is not mandatory (USB is always connected when the device is powered)• The device is self-powered. VBUS sensing is mandatory. Pin PA9, a five volt-tolerant pin, which includes an additional function natively dedicated to VBUS sensing. I have an option when the device is self-powered. Therefore, VBUS sensing is mandatory.It is also written

Hello everyone. I have recently made my own STM32 board based on the STM32F405. After soldering all the components and testing all pads and connections, finding them to be wired correctly and checking that the 3.3V is being supplied to all the correct pins, I tried to upload some code but to my shock the STM32F405 isn't establishing a connection via the ST-Link V2 nor the USB cable. After trying multiple fixes, I suspect the issue might be the STM32F405 chip that I got off AliExpress itself.  So before I took any further steps to replace it, I decided to post my schematics on here for review in case the problem was in my PCB design. If you have any remarks on what might have caused this problem, please share them. NOTE: The -B label is referring to ground, and P is the VCC. schematics:

I have been working with the single core LoRaWAN_End_Node example application on a B-WL5M-SUBG1 board with good success.  With STM32CubeMx v6.16.0, WL Firmware 1.4.0, I see a current draw of under 2uA between transmissions.Last week I upgraded STM32CubeMx to v6.17.0 which in turn upgraded the WL Firmware to 1.5.0, changed the end node example to use the LBM library rather than the LmHandler for managing the radio, and changed the example application name to LoRaWAN_End_Node_LBM.  The application functionality is good but the power consumption jumped to around 80uA between transmissions.In both cases I configured pullups in the USART2 pins (PA2, PA3).I can alternate between these two versions of the application on the same board and the results are very consistent.Has anyone else seen this and does anyone have any suggestions?

  Hello, I am currently developing a project that requires an ultra-low-power BLE-based indoor localization tag. The device should periodically wake up and advertise, remaining in standby mode (targeting approximately 500 nA to 1 µA) for about 90% of the time. I am using NUCLEO-STM32WBA65RI. For an initial test, I plan to configure the system to stay in standby for around 5 minutes, then wake up and advertise for 30 seconds. I have already studied the documentation regarding STM32 low-power modes and reviewed examples such as the Heart Rate application, where BLE is used together with low-power modes. However, I still have some doubts. From my understanding, these examples are designed for continuous radio operation and rely on SRAM1/SRAM2/RADIO retention, which increases power consumption. It also appears that some internal mechanism - possibly the UTIL_TIMER based on RTC or the 2.4 GHz radio

Hello, I can't cope with interrupt transactions. (I need it later for composite device).For tests I generated HID device example. When device is connected to host it appears correctly in the system.For interrupt endpoint configured 0x81.I need to answer for interrupt transactions, but which callback is responsible for this?I start debugging from very deep. Breakpoints were set in HAL_PCD_IRQHandler(). As I understand in this functions all usb transactions starts, but I see only interrupts from ZERO endpoint. Dumping by WireShark I see host sends requests to my device x.xx.1 and responses.Why I don't see interrupts for 0x81 (also I check 0x01) in HAL_PCD_IRQHandler()?What I do wrong?

I got another strange issue with a STM32F3, as usual related to DMA.The problem relates to an "old" DAC / DMA example I tried to port to a different MCU.The original is called "DMA_RAM_DAC", and is part of the V1.1.0 firmware package for the F303 discovery board.(.../STM32F3-Discovery_FW_V1.1.0/Project/Peripheral_Examples/DMA_RAM_DAC)Building and running it on this target, it works fine.However, my actual target hardware is the F3 Nucleo32. This board has a STM32F303K8T, instead of the 'huge'  STM32F303VCT on the F3-Discovery.The relevant difference here is, the mentioned example uses DMA2 channel3, which does not exist on smaller devices like the STM32F303K8. According to the reference manual, the relevant DMA request can be mapped to DMA1, by setting corresponding bits in SYSCFG (RM0316 Rev.10, page 267, 269).To do this DMA request mapping, bit 13 in SYSCFG->CFGR1 needs to be set.And here is were the problem starts.N

Hello. Could someone please recommend a good power board that can power and control two gimbal 3-phase BLDC 12V motors with encoders AS5048A https://www.sparkfun.com/gimbal-motor-with-encoder-12v-587rpm.html ? I use the STM32 NUCLEO-64 F401RE microcontroller board. Thank you.

I'm using the LCD of the STM32U073K8, but the program failed to initialize the LCD. After checking, I found that the STM32U073K8 doesn't have the VLCD pin. Is the STM32U073K8 not compatible with the LCD peripheral? Or are there other settings?

Hello ST Community,I am working on a USB Video Class (UVC) application using STM32H7S3L8 (NUCLEO-H7S3L8) in USB HS device mode.Requirement:Streaming 640×480  30fps (YUY2, uncompressed), requiring ~18.4 MB/s bandwidth.With the STM32 HAL, I can only achieve:~8.2 MB/s (1024 bytes × 1 transaction per microframe)This limits performance to ~13 fps at 640×480.USB 2.0 specification allows up to 3 transactions per microframe for high-speed isochronous endpoints.However in STM32 HAL:ep->maxpacket = ep_mps & 0x7FFU masks transaction bitsNo MC (multi-count) handli

 Hello,I am currently working with the NUCLEO-STM32WBA65RI. My main goal is to place the board in Standby mode and periodically wake it up to perform BLE advertising (as a Peripheral), while still allowing it to handle a possible connection request from another device.So far, I have followed the "Standby with RTC" example to implement low-power operation. I would now like to integrate the BLE stack to enable advertising during the wake-up periods. The intended behavior is for the device to sleep for 1 minute, wake up via the RTC, perform advertising for a short duration, and then return to Standby mode.From the documentation, I understand that the radio and Link Layer must be in deep sleep for Standby mode to be properly achieved. Could you provide some guidance on the correct way to ensure this state? Additionally, what happens if the radio is not in deep sleep when attempting to enter Standby mode?Best regards,

Hi I configured the DFSDM1 on the STM32H753VIT6 for a MEMS Mic.I got the problem that the DMA Callback on (Half)/Full buffer never gets called. I used AN5027 as guideline and the DFSDM Audio ExampleD-Cache disabled and set the Audio Sampling Frequency low (4kHz) to debug over UART. Main (snippets):DFSDM_Filter_HandleTypeDef hdfsdm1_filter0; DFSDM_Channel_HandleTypeDef hdfsdm1_channel4; DMA_HandleTypeDef hdma_dfsdm1_flt0; . . . . int32_t LeftRecBuff[1024]; void HAL_DFSDM_FilterRegConvHalfCpltCallback(DFSDM_Filter_HandleTypeDef *hdfsdm_filter) { /*Never Reached*/ } int main(void) { HAL_Init(); SystemClock_Config(); /* Initialize all configured peripherals */ MX_GPIO_Init(); MX_DMA_I

Hello,   I designed a custom control board based on STM32G431CBT6 and before manufacturing the PCB I would like to make sure there are no fundamental hardware mistakes.   My main concern is not firmware but hardware connections.   I would appreciate if you can review especially:   SWD programming interface connections Power supply and decoupling capacitors BOOT0 and NRST configuration VDDA and VREF+ connections CAN transceiver interface (TJA1051/3 with VIO = 3.3V) Anything that may prevent programming or startup     The goal is to verify that the MCU can be programmed and start reliably after assembly.  

I am currently working on the STM32N6570-DK board and need support for MIPI camera interfacing using CSI (not USB).RequirementInterface a MIPI camera using CSIRead camera dataEncode the dataSend it to a PC via Ethernet using UDP streamingSupport NeededHow to configure and enable CSI (MIPI camera interface)Any reference examples/projects for camera bring-upGuidance on reading camera data from CSIAny examples for encoding + Ethernet (UDP) streamingKindly provide any documentation or example projects that can help achieve this.

Post edited by ST community moderator. In next time please use </> to share a code. HI, I have Implemented ADC1 - DMA with one channel and ADC2 - DMA with 7 channels and im transmitting data through UART IT. I want to know if this code works usually. void HAL_ADC_ConvCpltCallback(ADC_HandleTypeDef* hadc) { if (hadc->Instance == ADC1) Print_ADC_Values_IT(); if (hadc->Instance == hadc2.Instance) Print_ADC_Values_IT(); } hadc2 is workin only when i disable HAL_ADC_Start_DMA(&hadc1, (uint32_t*)&adc1_value, 1); Here's the overview of my code: MX_GPIO_Init(); MX_DMA_Init(); MX_ADC1_Init(); MX_ADC2_Init(); MX_USART1_UART_Init(); /* USER CODE BEGIN 2 */ // HAL_ADCEx_Calibration_Start(&hadc1, ADC_SINGLE_ENDED); HAL_ADCEx_Calibration_Start(&hadc2, ADC_SINGLE_ENDED); // Start ADC1 (1 channel) // HAL_ADC_Start_DMA(&hadc1, (uint32_t*

Hello, I am using an STM32H755 Nucleo board in a system where the board is plugged into a custom PCB via headers. The system has been working for about two weeks without any issues. Occasionally I remove the Nucleo board to update the firmware and then plug it back into the PCB. Today the system stopped responding to UART commands. When I connected the board to my PC, STM32CubeIDE reported: "No ST-LINK detected! Please connect ST-LINK and restart the debug session." I also tried STM32 ST-LINK Utility and got: "Can not connect to target! Please select 'Connect Under Reset' mode..." However, STLinkUpgrade is able to detect the ST-LINK and perform a firmware upgrade. Another important observation: The ST-LINK MCU on the board (STM32F7) is getting very hot. Additional diagnostics: - The board was completely removed from the external PCB. - Even when powered independently, the ST-LINK MCU still

Hi,I am using STM32H755 where M7 and M4 runs bare-metal firmware using OpenAMP (RPMsg).Sampling rate is set to 250 SPS. The data is sent from M4 to M7 using OPENAMP_send() function.Observation: Data loss of approximately 10% is observed during transmission from M4 to M7. The loss does not follow a fixed pattern.Questions:- Is this an expected behavior with RPPMsg/OpenAMP at this rate?- How can I ensure reliable transfer without data loss? Thanks & Regards,Bhagyashree Ghosh Roy

I am currently working with MC Workbench and the ST Motor Pilot tool for motor control development. While setting up and attempting to establish a connection using the latest version of ST Motor Pilot, I am encountering a connection issue that appears to be caused by a bug in the current release.As suggested in the community forums, I also tried using an older version of ST Motor Pilot. However, this introduces dependency conflicts, as other required components and tools in the workflow depend on the latest versions and are not fully compatible with the older Motor Pilot version.Board- STEVAL-ESC001V1  

Hello, I am currently working with the NUCLEO-WB05KN1 development board (STM32WB05KN MCU) and I would like to implement FOTA (Firmware Over-The-Air) / OTA update over Bluetooth. However, I could not find any clear reference documentation, application note, or example project related to: Bootloader implementation for OTA Memory partitioning (dual bank / slot usage) BLE-based firmware update flow Any official FOTA example for STM32WB05 series I checked the datasheet and reference manual, but there is no clear explanation of: Whether a built-in/system bootloader supports OTA via BLE How to structure the flash (bootloader + application separation)

Hi All,I've this requirement, can someone suggest how do I proceed.I'm using stm32u535 and over usart it's connected to Silicon labs chip. Silicon labs chip has Wi-Fi and I want to update firmware of STM32U535. This silicon labs chip is connected to cloud over Wi-Fi. 

Hi everyone,I'm using an STM32H723 for a project with Hall sensor encoders on two BLDC motors.**Hardware:**- Left motor: PE7, PE8, PE9 (U,V,W)- Right motor: PD3, PD4, PD2 (U,V,W)**Problem:**Right motor encoder works perfectly. Left motor has issues:1. Tick count is much lower than right motor (82 vs 236 ticks for same movement)**Debug Output:*ENC:0,1|DIR:STOP,CW ← Left STOP, Right movingENC:6,11|DIR:CW,CW ← Both OK brieflyENC:8,21|DIR:STOP,CW ← Left STOP againENC:82,236|DIR:CW,CW ← Huge tick difference**What I've Tried:**- Added debouncing- Removed direction reset on invalid transitions- Verified signals on oscilloscope (clean)- External pull-ups (4.7kΩ)**Key Difference:**- Right motor: Dedicated EXTI2, EXTI3, EXTI4 handlers → WORKS- Left motor: Shared EXTI9_5_IRQHandler for all 3 pins → PROBLEMS**Questions:**1. Can shared EXTI9_5_IRQHandler cause miss

We are currently working with a custom PCB using an STM32N6 chip and an MX25UM512G flash chip. The flash is connected identically to the Nucleo development board.When powering up the board in Dev Boot mode, it is not possible to read the flash chip using CubeProgrammer. The MCU crashes, which we assume based on the reduced power consumption observed afterward.If we first load a firmware image into SRAM using CubeIDE (which successfully connects to and reads the flash memory), then reading and writing the flash via CubeProgrammer works as expected.However, after a power cycle without reloading the firmware into SRAM, the flash becomes inaccessible again.Additionally, after flashing the firmware using this workaround (i.e., initializing the flash via our own firmware and then booting in Flash mode), the software is not executed from flash and the system does not boot.Our assumption is that the flash is not correctly initialized by the boot ROM. Any h

Hello community,  I am working with different ibis model of STM32H7, however, this is the only one that's giving me an error in my Altium Designer – could you have a look at it? The file is stm32h723_730_733_lqfp144.ibs Kind regards,Javier.

I am developing a project using the STM32U5G9J. In particular I based our board on the STM32U5G9J-DK2 board. My project includes over the air update for which I am using the external flash that comes on the DK2 board for temporary firmware swapping storage. The external loader MX66LM1G45G_STM32U5G9J-DK2.stldr looks like is not accessing beyond 64MBytes, giving the impression of mirroring the first 64MBytes. I need to be able to have the external loader handle fully the 128 MBytes, as well as my application being able to access the 128 MBytes by code. I am using the STM32CubeIDE 1.19.0. which the IOC file configuration for HSPI is in OCTO SPI mode with the capacity to read 128MBytes. I am using the external loader to manually write certain pieces for debugging purposes. I cannot verify if my code works until the external loader is being able to access the full 128MBytes. Please help me providing the right external loader, as well as the certainty that the IOC file can have the

Title edited to clarify that this refers to a NUCLEO-WBA65RI board.Hello, I am currently using STM32WBA65RI with Standby mode. According to datasheet, this mode should be able to reach 120nA current consumption with the 16 GPIO wake-up pins (RTC disabled). However running the Standby example and shutting down the RTC I am still getting 3uA of current consumption. What can I do to decrease the current consumption up to the nanoA?Best regards.