Solved

The call toHAL_NVIC_EnableIRQ(EXTI3_IRQn); is not generated with the checkbox enabled in the GPIO/NVIC panel in gpio.cHowever:the call for HAL_NVIC_SetPriority() is generated correctly.MCU: STM32L496ZGTxSTM32CubeIDE: Version: 1.17.0pads: PD3, PD4 set up as EXTI, NVIC enabled for both.generated code: (section of gpio.c): /* EXTI interrupt init*/ HAL_NVIC_SetPriority(EXTI3_IRQn, 0, 0); HAL_NVIC_SetPriority(EXTI4_IRQn, 0, 0); HAL_NVIC_EnableIRQ(EXTI4_IRQn);HAL_NVIC_EnableIRQ(EXTI3_IRQn);is missing. 

@ ST engineers: This is a feature request for the firmware of the STLINK-V3MINIE and related debuggers/programmers: pipelined data transfers over the existing USB High-Speed link.In my pursuit to greatly improve the STLINK-V3MINIE's performance for large continuous reads from MCU memory, I discovered there is huge room for improvement: SWD's full potential (~2038 KB/s = 24M [cycles/s] * 4 [bytes/transfer] / (46 [cycles/transfer])) is not yet used at all. (Note that USB shouldn't be the bottleneck, judging from the maximum clock speed the STLINK-V3MINIE's STM32F723's USB IP can support.) I only achieve ~549 KB/s when using an STM32H7S3 MCU with ST's programming SW (v2.20.0) using STLINK-V3MINIE (FW V3J17M10):STM32_Programmer_CLI --connect port=SWD freq=24000 ap=1 mode=HOTPLUG -halt --read 0x24000000 0x60000 /tmp/dmp.binA simplified sequence diagram of the communication used here is shown:Read memory region; current situationI measured the SWD clock line with an oscilloscope to verify 24

Hi, I have a custom board with a STM32WB55RG and I’m trying to upgrade the Wireless stack (and the FUS firmware). When I perform a Read FUS Infos in STM32CubeProgrammer, it returns v0.0.0 value for the FUS Version (I know that it should be v1.2.0 as it used to be v1.2.0). If I read the memory at address 0x20030000 I have the following value:  where DeviceInfoTable seems valid,  the Wireless stack version is1.15.0 build 3 and FUS version is 1.2.0 SFSA value is 0xce (address: 0x080ce000) Any ideas why I see this value (v0.0.0) when I read the FUS infos? Moreover, when I try to update the wireless stack (or the FUS firmware), everything looks to go well but when I read back the FUS infos they are still the old values. 

@Lina_DABASINSKAITE The forum seems to no longer explicitly identify which users are ST Staff.I think it should.

Hello ST team,I am using a P-NUCLEO-LRWAN3 starter kit with the NUCLEO-F746ZG gateway board.I accidentally overwrote the original gateway firmware on the F746ZG. I have already recovered the board so that it can be connected and programmed again with STM32CubeProgrammer, but I no longer have the original gateway firmware binary.I tried flashing another gateway binary:st-nucleo-lora-gw-at-fw-v2.1.7-eu868-TTN.binThe firmware runs, but it is clearly not the correct one for my hardware. After flashing it, the serial output shows EU868 / TTN settings and reports:router.eu.thethings.networkuplink/downlink port 1700channels around 867–868 MHzERROR: Radio A frequency and type are not matchedERROR: Radio B frequency and type are not matchedBefore I overwrote the original firmware, the gateway output was different. The original serial output showed:VERSION: 2.1.7, Nov 6 2018LORAWAN SERVER: ap1.loriot.iouplink/downlink port 1780channels from 471500000 to 472900000So I believe the original firmwar

Hello,I’m facing a strnge issue in the code generated by CubeMX for the STM32L496ZG.The project was imported in CubeIDE and compiled fine.but, as soon as HASH is activated the project no longer compiles and throws several hundreds of errors.CubeMX version is 6.17.0CubeIDE version is 2.1.1Looking at the errors, it appears that the HASH symbol is not defined, resulting in the associated code being grayed out.Regards

Dear all,I'm looking for the driver for the VD55G0 camera sensor compatible with the STM32N657 MCU. According to the camera sensor's driver product page (STSW-IMG505) a driver should be available for the N6 (the N6 is mentioned several times as being supported) but I can only find drivers for Raspberry Pi and V4L2. Could you please let me know where I can obtain the driver?Thank you very much for your support!Michael

I have multiple STLinks on multiple Nucleo boards.  I can debug only if I connect one at a time, but it is tedious to connect and reconnect to switch boards. When I plug in multiple devices I see them listed (bottom left) but I can’t work out how to select a specific STLink to use.  If I try to debug it fails with a “bound doStepConnectToTarget Failed: could not connect: Operation timed out.” and suggests I open launch.json.Disconnecting the cables is additionally tedious because I’m using the VCP on each, and disconnecting breaks the connection to the terminals, which then all need to be reconnected.I know that with the stand-alone STM32CubeIDE it possible to have separate configurations for each STLink (defined by Serial ID) and then I select the one to use as needed, without having to disconnect any hardware (and the VCPs for the devices I’m not debugging stay connected).Is there a way to specify the STLink serial ID to use in the launch.json file?  In VSCode I notice there is a but

I have 2 problem in my touchgfx project.I use STM32G4 series. I have an external loader with a starting address of 0xA0000000. I can perform read and write operations with this loader using CubeProgrammer. However, when I define the external loader via CubeIDE, it programs the address 0x080000000. Then I get Hard Fault.   Here is my flash.ld The external loader starts working when I start it with the external loader address 0x00000000, but I want to start with 0xA0000000. How can i fix it ?Also my second problem is texts. My text datas are sending to external flash, but it is not appear. Then I changed font section to internal flash in flash.ld, my text was appear. Here is my changed sections side.  The textures are changing because something else is changing. Why isn't the screen showing the text I added with the external loader?

Hello! I currently have several questions regarding STM8500 + STLD1 DC carrier communication. Please reply!   1: I send differential signals via STLD1, which are capacitively coupled at high voltage between DC48V and DC48V_GND, then received at the receiving end. Shouldn't be any issues, right? The theoretical transmission distance can reach 3km, right? Is there a more complete reference schematic design available? The schematic provided in the official manual is incomplete.   2: The STM32F401 communicates with the ST8500 via UART. Can I use the ST8500 simply by calling AT commands or API interfaces? Or do I need to program the ST8500 itself or download firmware to use it?   *This post has been translated from Chinese to comply with the ST Community guidelines.

Is there any way to correctly specify the baud rate for different UARTs in STM32CubeMX?I am currently using: STM32CubeMX V6.17.0 with STM32Cube_FW_H5_V1.6.0I wanted to set the baud rate to 9600 for LPUART1, UART4, and USART2.However, this isn't working; all three UARTs are outputting the same incorrect baud rate based on the calculated divider.Instead of 9600 baud, transmission occurs at 3075 baud (a factor of 3.12195121951219512195:1 too slow).The external 25 MHz HSE oscillator is used as the clock source (original from the Nucleo Board).PLL2Q is used as the clock source for each of the UARTs.I have already tried the following:Updating STM32CubeMX, Updating STM32Cube_FW_H5, Changing the UART clock from 250 MHz to 25 MHz and 5 MHz, Changing the baud rate from 9600 to 19200.When I initialize the UARTs at 19200, they all transmit at 6150 baud.The project was previously built using MX V6.16 and STM32Cube_FW_H5_V1.5.0/V1.5.1, but the problem persisted.Does anyone know how to correctly set

Hello everyone,I am currently working with an STM32G4 series MCU using multiple FDCAN peripherals and would like to hear about other developers' experiences regarding CAN communication reliability and synchronization.In projects where both FDCAN1 and FDCAN2 are active, have you encountered any challenges related to:Clock configuration and synchronization Bit timing calculations Bus load handling Message filtering across multiple instances Error recovery and bus-off situationsI'm particularly interested in best practices for configuring multiple FDCAN instances to ensure stable communication in automotive and industrial applications.Any recommendations, examples, or lessons learned from real-world deployments would be greatly appreciated.Thank you in advance for sharing your experience

hi team,I'm facing issue in enabling usart6 of the expansion connector of stm32mp257f-ev1, All i did was to enable the &usart6 via DT overlay, even tried disabling dmas, but no luck.I have attached the kernel log and also attached the RIFSC debug log FYRHoping for a quick reply, thanks in advance./dts-v1/; /plugin/; / { compatible = "st,stm32mp257f-ev1"; fragment@0 { target = <&usart6>; __overlay__ { status = "okay"; }; }; };$ stty -F /dev/ttySTM1 115200 E/TC:0 stm32_serc_handle_ilac:133 SERC exceptions [63:32]: 0x10 E/TC:0 stm32_serc_handle_ilac:139 SERC exception ID: 36 [ 39.106314] SError Interrupt on CPU0, code 0x00000000bf000002 -- SError [ 39.106336] CPU: 0 PID: 1618 Comm: stty Tainted: G O 6.6.78 #1 [ 39.106344] Hardware name: STMicroelectronics STM32MP257F-EV1 Evaluation Board (DT) [ 39.106348] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 39.106357] pc : stm32_usart_rx_dma_start_or_resume+0x80/0x234 [ 39.106375] lr : stm32_usart

There doesn't seem to be any (easy) way to get a full list of all the different "Sensor Box" variants?In particular, is there one which has at least IP65 protection?

Hello, I am trying to make the lpuart1+dma_linked_list transferring data in stop1 mode.My setup is like this:    SPI1 + GPDMA: // SPI clocked from HSI    Start transfer    Enter STOP    SCK continues toggling    DMA continues    Transfer completes    DMA irq wakes from stopLPUART1 + GPDMA: // LPUART clocked from LSE    Start transfer    Enter STOP    TX line freezes    DMA stops progressing    Exit STOP    TX resumes Both peripherals are using dma in linked list mode in a similar manner.My understanding is that since both peripherals are “autonomous” they should work in a similar way. I have no problem with the SPI1 working during stop1 mode but the LPUART seems to behave differently.This is my LPUART1 init code: void bsp_lpuart_init(void){    bsp_lpuart1_reset_hard();        LL_LPUART_SetPrescaler(LPUART1, LL_LPUART_PRESCALER_DIV1);    // Disable before configuration    LL_LPUART_Disable(LPUART1);    while (LL_LPUART_IsEnabled(LPUART1));    LPUART1->BRR = 3495; //419430    LL_LPUAR

I ported PPSSPP 1.20.3 to run on the STM32MP257D platform.With the GLES backend, everything looks fine and normal games run without issues. But when I try heavier 3D games like Tekken 6, it gets extremely choppy – single-core CPU usage stays around 95%.Then I tried switching to Vulkan. At first, the emulator crashed on startup. I debugged it by adding some print statements and found that a function call was returning an incorrect value – which shouldn't happen according to the Vulkan spec. Because of that, another function (vkCreateSwapchainKHR) ended up failing. 1) PPSSPP Crash Log:Spoiler (Highlight to read)08:00:074 Vulkan/VulkanContext.cpp:1416 I[G3D]: surfCapabilities_.current: 960x544 min: 1x1 max: -1x-1 computed: -1x-1 08:00:079 Vulkan/VulkanContext.cpp:1579 E[G3D]: vkCreateSwapchainKHR failed! VK_ERROR_DEVICE_LOST08:00:074 Vulkan/VulkanContext.cpp:1416 I[G3D]: surfCapabilities_.current: 960x544 min: 1x1 max: -1x-1 computed: -1x-1 08:00:079 Vulkan/VulkanConte

While researching the GNSS module for my project, I got somewhat confused about the power connection of the LIV4F module due to inconsistent information in the manuals. The general recommendation is to run at 1.8V for optimal power consumption, but my interface is running at 3.3V. In the evaluation board manual (UM3212), there's a 3.3V VCC_IO on pin 7 for communication and 1.8V VCC pin 8 for powering the module which would easily allow this set up. In the hardware manual (UM3004) for the module however, pin 7 is marked as reserved - which means there's no separate VCC_IO and I would need to level shift all the communication channels when running at 1.8V. I was hoping you could clarify whether pin 7 is available as VCC_IO or not?

I’m using the pre-release STM32Cube for Visual Studio Code (v3.5.1).After importing a project that was originally generated by STM32CubeMX with the “cmake” toolchain selected, the .vscode folder is created but contains neither tasks.json nor launch.json.When I try to add tasks.json manually, the command palette no longer offers the usual templates such as “STM32: CubeProg: Flash project (SWD)”.Could you confirm whether this is a regression in 3.5.1?If an immediate fix isn’t possible, would you mind sharing the correct tasks.json and launch.json snippets so I can paste them in by hand? Test conducted on July 28, 2025, testing platform Ubuntu 22.04+vscode(v1.102.2)+pre-release STM32Cube for Visual Studio Code (v3.5.1), test target STM32G474RET6.

Hi,I am using an STM32G0B1VET6. All power rails in my design, including VDDIO2/VDDUSB, are supplied from 3.0 V (2.95 min).I would like to use the USB interface and the built-in USB DFU bootloader for firmware updates.AN2606 states that VDDUSB must be connected to 3.3 V. However, AN4879 appears to specify a USB supply operating range down to 2.7 V, with 3.0 V as the minimum recommended operating voltage in some cases. Based on that, I would expect USB to operate correctly with VDDUSB supplied from 3.0 V.Could you please confirm whether USB DFU is supported on the STM32G0B1 when VDDUSB/VDDIO2 is powered from 3.0 V rather than 3.3 V?The board will be powered from its own 3.0 V supply. For the USB programming connection, I am planning to bring out only three wires:USB D+ USB D− GNDThe USB 5 V VBUS line will not be used to power the board.Are these three connections sufficient for entering the system bootloader and performing a firmware update through USB DFU, or is the USB VBUS line or a s

..

I posted on 3rd June and have received emails today saying i have replies. However the topic has now vanished! It is no longer on my topic list or reply list. When i click the link it goes to the main page!!Whats going on!? Hello RAdam.1, Your topic recently received a reply.Topic:  STM32WB05 reboots when starting to advertiseDate: 2026-06-03 10:49 AMDid it solve your problem?Click here to view the reply and mark one as an Accepted Solution.This helps others find helpful answers in the community too!Thanks for being a STMicroelectronics Community member.Your STMicroelectronics Community TeamSTMicroelectronics Community sent this message to richardadamsla@gmail.com.Don't want to receive emails from us? Just click here.

Neither in the front page listing, nor in the individual forums. New threads used to be highlighted in bold on the old forum.

Hello,I'm working with the STM32MP135F-DK kit and I'm trying to understand the correct way to configure interrupt lines (IRQs) for external devices,  specifically for the STPMIC1 in OP-TEE.I have been reading the official documentation and I'm a bit confused about whether it is mandatory to use the dedicated PWR Wake-up pins (WKUP1–WKUP6) for interrupt lines, or if any GPIO can be used.--- What I observed in the reference DTS files: Looking at the OP-TEE device tree (core/arch/arm/dts/stm32mp135f-dk.dts, tag 4.0.0-stm32mp), I can see that all IRQ consumers use EXTI lines above 55: - STPMIC1 interrupts-extended = <&exti 55 IRQ_TYPE_EDGE_FALLING> (WKUP1 / PF8) --- My questionsIs it mandatory to use one of the 6 dedicated WKUP pins (EXTI 55–60) for any device IRQ managed by OP-TEE? 

Using a custom board with the stm32l412 chip, after entering stop 2 mode, it measures 380uA instead of about 0.72uA without RTC as stated in datasheet.I know using custom board would get the current consumption to get a bit higher but this is almost ridiculous difference, so I expect that something is off, but not sure where to check.Thanks in advance.