Solved

Hi Is TouchGFX supported on MP1 or MP2 boards ?I found this article : https://wiki.st.com/stm32mpu/wiki/How_to_install_X-TouchGFX_MPU_AddonBut it looks like its only 1 board

My device uses an STM32H743VITx MCU.I need to use ADC3 at the beginning of my program to verify that three voltages are indeed at the correct values. Then I want to disable it completely before initializing ADC1 and ADC2 to avoid pin conflicts.Does the function HAL_ADC_DeInit(&hadc3) allow me to do this?

Everytime CubeMx downloads files but in the end shows the below error every time. Please tell me how do i resolve.

RM0486 describes CSI_PFCR bit 16 (DLD) as follows: Bit 16 DLD: Data lane direction of lane 00: Rx1: TxPer this description, configuring the CSI-2 host to receive from a camera sensor (i.e. lane 0 in RX mode) should require DLD = 0.However, in the shipped HAL, HAL_DCMIPP_CSI_SetConfig() explicitly sets DLD = 1 (via CSI_PFCR_DLD) when configuring the PHY for CSI-2 RX capture from a camera sensor:WRITE_REG(csi_instance->PFCR, (0x28U << CSI_PFCR_CCFR_Pos) |(SNPS_Freqs[pCSI_Config->PHYBitrate].hsfreqrange << CSI_PFCR_HSFR_Pos) | CSI_PFCR_DLD);The HAL source even contains a comment acknowledging the discrepancy:/* set basedir_0 to RX DLD 0 RX, 1 TX. Synopsys 1 RX 0 TX + freq range */This strongly suggests that the underlying Synopsys D-PHY basedir signal has the opposite polarity (1 = Rx, 0 = Tx) from what's documented for the DLD bit in RM0486, and that the HAL was written/validated against the actual behavior rather than the RM's bit description.Is this a mistake of myse

OpenSTLinux: Starter Package, plain image (FlashLayout_sdcard_stm32mp257f-dk-optee.tsv), version 5.0.17-openstlinux-6.6-yocto-scarthgap-mpu-v26.06.10M33 firmware: Zephyr RTOS (4.4.99), board target stm32mp257f_dk/stm32mp257fxx/m33, loaded and started from Linux via remoteproc.Goal: Drive a SPI device (Qorvo DW3000) from the Cortex-M33 over SPI6, which is exposed on the CN5 header (GPIO10/SPI6_MOSI = PC7, GPIO9/SPI6_MISO = PC4, GPIO11/SPI6_SCK = PF7).When the M33 firmware performs a SPI transfer, the GPIO chip-select line toggles correctly (verified on a logic analyzer), but SCK never produces any clock pulses & the line stays flat. Consequently no data is exchanged (MOSI/MISO flat). The transfer call itself returns; it just produces no clock.What I have already checked:-RIFSC firewall: SPI6 shows as NSEC, NPRIV, CID filtering disabled (from the RIFSC debug dump) — i.e. not blocked/assigned exclusively to the A35.-Clocks: clk_summary shows both ck_icn_p_spi6 (~200 MHz) and ck_ker_sp

Hi everyone,I am working on a project using BNO085 IMU sensor and STM32H7A3ZIT6Q. I have a single sensor working but stuck at 44Hz. The same sensor with SparkFun library on ESP32 achieves 1.2ms read time. I need help understanding why and how to match ESP32 performance on STM32.Hardware:NUCLEO-H7A3ZI-Q (STM32H7A3ZIT6Q, Cortex-M7 @ 280MHz)Adafruit BNO085 breakout boardI2C on PB8 (SCL), PB9 (SDA), PC0 (INT pin)P0 and P1 tied to GND (I2C mode, address 0x4A)Software:STM32CubeIDE with HALOfficial CEVA SH2 library from github.com/ceva-dsp/sh2REPORT_INTERVAL_US = 2500 (targeting 400Hz)SH2_ROTATION_VECTOR (9-axis full quaternion)STM32 performance achieved so far:I2C 400kHz polling: 28Hz, read_ms = 32msI2C 1MHz Fast Mode Plus: 44Hz, read_ms = 19msINT pin wait inside sh2_hal_read(): still 44Hz, read_ms = 19msESP32 performance with same sensor and SparkFun SH2 library:read time: 1.2msData rate: close to 400HzThis is a huge difference. 19ms on STM32 vs 1.2ms on ESP32 with the same SH2 library unde

I'm working on a dual-core project (Cortex-M7 + M4) for the NUCLEO-H755ZI-Q board in CubeMX/CubeIDE.I created the project using Board Selector (searched "NUCLEO-H755ZI-Q", selected the board, accepted the default LED/Button/Virtual Com Port options popup). Despite this, USART3's Mode dropdown is stuck on "Disable" and greyed out/unselectable in the peripheral configuration panel.Pins PD8/PD9 initially showed as "under BSP control". I right-clicked on PD8/PD9 in the pinout view and manually assigned them as USART3_TX and USART3_RX. The pins now show these labels correctly on the diagram — but the USART3 Mode dropdown is still stuck on "Disable" and I still cannot select Asynchronous mode, set baud rate, or configure anything.I also tried:Toggling the M7 core-assignment checkbox off/on for USART3 Creating a brand new project from scratch via Board Selector (same issue every time)   What to do ? 

I have noticed several recommendations on internet, that recommend providing a low high frequency impedance driving the ADC input for the MCU. For instance, you could add an RC-filter with the capacitance directly between the input pin and analog ground. This is one of the recommendations: https://community.st.com/stm32-mcus-products-25/many-people-have-complained-about-noise-on-adc-inputs-maybe-to-do-with-impedance-has-this-be-rectified-on-any-version-or-family-of-the-stm32-42573?tid=42573&fid=25  Well, I am not sure of such a recommendation anymore… Perhaps I should just state that I am a novice regarding the use of STM32 processors, but I am old regarding general electronics design and electrical noise. I have just tried this circuit with a Nucleo STM32G474RE board with 100 nF decoupling capacitor and a series resistor that I vary on the input pin:  The preconditions are that I make an AD-conversion every second and with a 170 MHz sysclock and a 42.5 MHz ADC clock. The sample ti

I’d like to create a mac address using the STM32U5’s 96-bit UID. since first byte I’ll use as constant, i need 40 bits to create a unique mac for my devices.i wonder what’s the best way to create a mac with the least change of collision.if i use 32 bit wafer coordinates, and 8 bit wafer number for example, how likely am i to get a collision, opposed to other methods?thank you

Hi all,I have a custom board with an integrated STLINK-V3MODS, connected to an STM32H755ZIT6 MCU. T_NRST is not connected between the STLINK-V3MODS and my MCU.My MCU is already powered on and running code normally. When I then connect the STLINK-V3MODS to my PC (via USB), it automatically resets my target MCU.Since T_NRST isn't wired at all, I don't understand how the V3MODS is able to reset my target.I'm already using the VCP (T_VCP_TX/T_VCP_RX) for logging. The issue is: when I plug in the STLINK-V3MODS to view the logs, it resets my MCU — but I don't want that. I want the MCU to keep running as-is, and just be able to plug in and observe the logs live without interrupting it.How can I prevent this reset-on-connect behavior while still being able to use the VCP for logging?Thanks!

How to flash M4 Core in STM32MP157F-DK2 using STM32Cube Programmer..? I have the Hex file but whenever I open Cube Programmer ST-LINK is not Detecting instead its Deteccting as USB, and in Device manager USB is recognized as STM32 Bootloader

Dear STMicroelectronics Support Team,we are preparing a reliability prediction report for an electronic assembly intended for customer qualification.The calculation is based on a parts count approach using IEC TR 63162:2025 as source of reference failure rates and IEC 61709:2017 for conversion to operating conditions.For the component STM32U545RET6Q, currently classified as a CMOS microcontroller according to IEC TR 63162, we kindly ask whether ST can provide manufacturer-specific reliability data, in particular:FIT rate or failure rate for STM32U545RET6Q, or for the STM32U5 family; reference conditions of the FIT value, including temperature, voltage, operating profile and confidence level; method or standard used for the reliability evaluation, for example IEC 61709, JEDEC, internal field data, HTOL, qualification data or other; reliability / qualification report that can support the use of the data in a customer-facing reliability prediction report; any applicable limitation regardi

Cross-posting from CC1125 Sleep current rises to ~2mA on the TI forum.I have a custom board with STM32F030 controlling a TI CC1125 sub-GHz radio transceiver via SPI plus a few GPIOs.Everything is fine for normal operation (TX, RX, etc), but the system has a "Shutdown" mode where the CC1125 is put into its low-power SLEEP state, and the STM32 is in STANDBY.In SLEEP the CC1125 should take under 1uA but, after sending the SLEEP command, I see the current rise over ~4s and eventually settle at ~2mA.I have managed to reproduce this using a Nucleo-F030R8 (ST-Link removed) and a TI dev board:The blue line is the total system current (STM32 + cc1125); red line is just the CC1125.Zooming-in on the Shutdown part: There seems to be something charging-up and then (partially?) switching-on?With the CC1125 disconnected, the Nucleo alone takes a steady ~3.1uA with the STM32 in STANDBY.So it looks like the issue is with the CC1125 somewhere; just posting here in case anyone has any suggestions.&n

STM32N657 / STEdgeAI 4.0.1 - Non-deterministic inference results with a minimal STAI wrapperHello,I am currently evaluating STEdgeAI 4.0.1 on an STM32N657 before integrating AI support into my RTOS (uKOS-X).My objective is not to use the generated CubeMX application. Instead, I want to build a small self-contained library that encapsulates all ST Edge AI resources and exposes only a minimal API to the application.The wrapper API is intentionally very small:gan_npu_status_t npu_init(void);gan_npu_status_t npu_putInput(const void *input);gan_npu_status_t npu_inference(void);gan_npu_status_t npu_getOutput(void *output);The application never accesses any STAI object directly.This is only a first validation step, therefore I intentionally use synchronous execution (STAI_MODE_SYNC) and polling only. Interrupt-driven execution will be implemented later.Configuration STM32N657 STEdgeAI 4.0.1 Neural-ART generated network Single network instance ST-generated sources left completely uncha

Setup Board: X-NUCLEO-NFC09A1 (ST25R100), brand new, unmodified, no jumpers/solder bridges changed Host: STM32, custom C++17 driver (register-level, not RFAL) SPI: confirmed working — bring-up sequence completes, all register reads/writes verified against DS14139 Rev 4 SymptomThe autonomous wake-up measurement cycle (triggered internally by the WUT every wut period) never emits any RF onto RFO1/RFO2, confirmed directly on an oscilloscope. However, the CALIBRATE_WU_MEASUREMENT direct command (0x74), issued manually once during bring-up, reliably emits a real RF burst every time (5 sub-pulses of ~26 µs each, ~130 µs total).This has been reproduced consistently across many test runs, with the following independently confirmed facts: wu_en is set and read back correctly (OPERATION = 0x01). The WU timer itself is confirmed running: with wuti (WU_CONTROL_1 bit 3) set, I_wut fires reliably in IRQ_STATUS_3 on schedule, tested at both wut = 77.3 ms and wut = 9.7 ms. IRQ_MASK_3 correctly

The CubeMx project does not generate the Usart Init in main .c file. I can add manually but just verifying if any problem with my CubeMx software. Request to please verify. I mean it is not called from the main.c file.

Hi everyone,I need some help please on a choppy DSI signal.Long story short, I have decided to clone an STM32U5G9 disco board and build my own DSI driver using the same mcu in a smaller package running at 3v3 VDD. All seems to be fine, all voltages levels are correct on the screen after removing R8 and bridging R9 (backlight also works) and the VLXSMPS output is the same as on the disco (1.2V). I have signal on all DSI lines as well, as expected.But...Below I am showing you the DSI_D0N signal from the original disco board, followed by my custom one. The capture was with an oscilloscope on the direct pin output of the two mcu-s, so the screen was not connected in either scenario. It is clear to me that the low state of the signal is too noisy on my custom board and thus, not too surprisingly, I have no output on the screen. Can anyone give me a hint please over what I did wrong in my design?About the custom board, it is 2-layers, the DSI lines are all matched and no vias were used. The

I purchased new board NUCLEO-H723ZG, installed STM32CubeIDE, STM32CubeMX, Programmer. Now I just want to build and run on my board any STM32CubeIDE example project without dancing around.But it seems like it is impossible to import ready to run project and run it. I waisted several hours with no luck.Can anyone point me out to any place online where I can just download the project, open it in IDE and run without modifications on my hardware board?

RAK3172 + ChirpStack FUOTA: Class-C session confirmed active, but zero radio IRQ activity (no RxDone / RxTimeout / RxError) — multicast fragments never received on one of two identical devicesSummaryI have two identical devices (same firmware, same hardware BOM) running FUOTA over LoRaWAN using a RAK3172 module (STM32WLE5-based, AT-command slave) driven by an STM32H7 host MCU. One device completes FUOTA perfectly every time. The second device — same code, same ChirpStack FUOTA deployment, same gateway — gets all the way to a confirmed Class-C switch and then receives nothing. No fragments, no radio errors, nothing.I’ve isolated this down to the radio IRQ level and would like input from anyone who has hit something similar with RAK3172 / STM32WL Class-C behavior.SetupEnd device MCU: STM32H7 (host), communicating with RAK3172 over UART using AT commands LoRa modem: RAK3172 (STM32WLE5 based), running STM32CubeWL / LoRaMac-node stack LNS: ChirpStack v4.17.0 (self-hosted) FUOTA: ChirpStack

Hello SirI’d like to know your goods label rules.it’s only have Assemble country information, no Wafer production country information? here’s my stock label information. and now i have a new batch need impoted and the documents was wrote COO is Morocco.the Customs asked us provide the Country of Origin Certificate.could you please support ?   

Under this configuration, the prompt indicates that the attribute "liveWatch" is not allowed. { "type": "jlinkgdbtarget", "request": "launch", "name": "STM32Cube: Launch JLink GDB Server", "origin": "snippet", "cwd": "${workspaceFolder}", "preBuild": "${command:st-stm32-ide-debug-launch.build}", "runEntry": "main", "imagesAndSymbols": [ { "imageFileName": "${command:st-stm32-ide-debug-launch.get-projects-binary-from-context1}" } ], "liveWatch": { "enabled": true, "samplesPerSecond": "4" } },This is the analysis conducted by GPT.STM32CubeIDE for Visual Studio Code 3.10.0JLinkDebugTargetAdapter correctly creates the Live Watch client.However, the Live Watch client immediately issues-var-createwhile the target is running.SEGGER J-Link GDB Server returnsCannot execu

I have a STM32C031C6 and I’m trying to set the clock to be 48MHz It works when I have the for loops in there, but its not supposed to have them and I want to get it working properly without needing them.If I comment out 1 of the for loops, then after that it gives me this error I’m not sure what I am doing wrong, I think I’m not waiting properly for something, but I don’t know what that is.Error in executing 'cont' command ...Target is not responding, retrying...Target is not responding, retrying...Shutting down...Target is not responding, retrying… This is the code.#include "stm32c031xx.h"void speed_up_to_48mhz(void){ // 1. ENABLE HSI and wait for the HSI to become Ready RCC->CR |= (1U << 8); while (!(RCC->CR & (1U << 10))); for(volatile int i =0; i<1000000; i++){} //bit 8 is prefetch //bit 9 is instruction cache //1 wait state FLASH->ACR = (1U << 9) | (1U << 0); FLASH->ACR &=~ (1U

We are using a mix of stm32 - G473, H503, H523, H563, H573.For each of these, we have a bootloader that locks the chip security (to Closed for full regression with password on the H5s).If we inadvertently put the wrong bootloader on a board, some combinations will brick the board - specifically, loading 523 or 563 bootloaders onto 503 or 573 boards goes to the closed state without a useful password in place.I would like to programmatically check that each bootloader is running on its expected target before setting security. I see the IDCODE register contains 0x484 for STM32H562/563/573, or 0x478 for STM32H523/533. Unfortunately this distinguishes the 523/563 which is not such a problem for us, but not the 563/573 which is our problem.Ideally, I would like a (different) function for each of our micros that will run correctly on the expected micro but return an error (or possibly hard fault) on anything else.Thanks

I am unable to start a project from STM32CubeMX running on Linux Mint. I have no proxy setup on my network and verified the same with Connection Parameters > Check Connection. I also tried the steps with another ISP, however the issue persists. What is the fix for this? 

Configuration:I2C address: 0x6A Bus speed: 100kHz (standard mode) ODR: 1920Hz for both XL and GY (ISM330BX_XL_ODR_AT_1920Hz, ISM330BX_GY_ODR_AT_1920Hz) Full scale: ±125dps gyro, ±4G accel Reading a 14-byte burst starting at register 0x20 (TEMP + GYRO + ACCEL) once every 10ms, from our control loop. The application currently checks the IMU every 10ms.My intention is:Every 10ms, determine whether a fresh IMU sample is available. If fresh data is available, start one interrupt-driven burst read (gyro + accel). When the transfer completes, update the application variables once. Ignore intermediate samples produced by the IMU between 10ms periods.Polling-based implementationInitially, we have implemented the IMU driver using a polling-based I²C implementation (partially based on an open-source GitHub driver). During long-duration testing, the application hung/resetting inside the blocking I²C loops. Code for this method is attached in attachment 1.Interrupt-based implementationTo overcome t