Product forums

Hi I am using NUCLEO-N657X0-Q board, for the STM32N657 part, with the release STEdgeAI 2.0.We are using STM32Cube ecosystem (IDE, CubeMX, Programmer) for the development. I have been using NPU Validation example without any issues. The example there for the DK board, "\Projects\STM32N6570-DK\Applications\SNS\", which does not run for NUCLEO after a bit of changes for Nucleo. Gets stuck after the SystemIsolation_Config() in AppliNonSecure, with a Hard Fault. SECURE_RegisterCallback(IAC_ERROR_CB_ID, (void *)SecureError_Callback); (which is IACCVIOL = 1) ==> Though I have MPU is already enabled in the FSBL.    Same time, after a bit of struggle with the CubeMX, Generated the code for Nucleo with X-Cube-AI 10.0 package. But this ended up with 1000's of errors in the build.   Another way, by trying from working SNS Application sample (of course with FSBL) from Nucleo Templates and then adding the AI related Middleware, Apps to NS App side, it goes as far as /* End

Hello,I tried to understand what does A35-TD does better than M33-TD flavor and vice versa. But I don't find enough information. The information that confuses me is it says A35-TD Flavor has Hard real time on Arm Cortex-M33. What does it mean operation wise- what capabilities does it have extra compared to M33-TD Flavor? Could someone please help me understand this?  Thanking.with regardsAmit

Hi team,  We have our own customized USBPD board (STM32L562CET6) which support both SPR(100W) and EPR(140W). SPR is working great, now we want to work on 140W using EPR mode. So that initially we have tried to enter EPR mode by following method #define USBPD_EPRMDO_ACTION_ENTER (uint32_t)(0x01 << 24)#define USBPD_EPRMDO_DATA_ENTER (uint32_t)(0x8C << 16)eprmdo[0] = 1; //Header - no.of data objectseprmdo[1] = USBPD_EPRMDO_ACTION_ENTER | USBPD_EPRMDO_DATA_ENTER;//EPRMDOstatus = USBPD_PE_Request_DataMessage(0, USBPD_DATAMSG_EPR_MODE, eprmdo); But it returns "USBPD_FAIL". Please clarify me that "Is it possible to enter EPR mode by using above mentioned method? If yes, please correct me why i am getting USBPD_FAIL status." 

[PN]: STSPIN32G4[VERSION]: v6.4.1[TOOL]: MC Workbench / Motor Pilot[DETAILS]:I am working with a custom PCB design which was largely follows the EVSPIN32G4 schematic. I defined a custom board in MC Workbench and generated firmware, and can upload the firmware to the STSPIN without issue. Motor Pilot detects the board, and I can command START/STOP and read values/status.When I press START for either Torque or Speed control, the board enters some ALIGNMENT stage (only the first time) followed by RUN. No behavior is observed with the motor. No faults are ever reported by Motor Pilot. I can STOP and START motor control again and still see no change in behavior.With a scope, after START I see a single pulse on the U phase's gate for around 22 microseconds, then it falls to 0V and remains there. I did briefly run the firmware under GDB, and I see that MOE is set during RUN.Using a 48V frameless motor, running from a Li-Ion pack (bus voltage currently 56V), SIR680LDP-T1-RE3 FETs. VCC mea

I have an application that uses the OCTOSPI1 interface to read from and write to an external NOR flash memory into an SRAM1 buffer. The read and write operations are performed in the NS section of the application. If I perform a transfer without using DMA, it works. However, if I try to use GPDMA1, I get a buffer with all data set to 0, with no error.Additional information: the application works very well with GPDMA1 if I disable the MCU’s TrustZone mode.I conclude that GPDMA is not fully initialized to work with TrustZone enabled, but I can’t figure out what’s missing despite my searches on this forum.Any help would be greatly appreciated.

I created a motion_fx for stm32h562 from CubeMx. The auto generated motion_fx.h file does call (line 135)size_t MotionFX_GetStateSize(void);​But the code does miss the include #include <stddef.h>Which results in the following error:unknown type name 'size_t' motion_fx.h ./Middlewares/ST/STM32_MotionFX_Library/Inc line 135 C/C++ Problem 

I'm confused by ST's seeming definition of what they think a QUAD word is....according to most of the planet a WORD is 16-bits, so a QUAD word is 64-Bits.  However according to ST a quad word is 128 bits on the STM32U535.I enclose a section of my code - essentially I want to write 11520 values which are U32's and then read them again when I power it back up, bit its getting confused because I can't get my head around whether there's 64, or 128 bits in a QUAD WORD! xnLookup[][][] is the Parameter I want to write, and the read back which is a U32This is the WRITE: i=0;//Channel 0..3 j=0;//Temperature 0..180 (-50 to +130DegC) k=0;//Term X0, X1, X2, X3 etc n=1;//Counter for every 4th flash word MemCount=0;//Total memory locations //was 11520 for -50 to +130DegC. change to for(m=0;m<11520;m++)//Total number of parameters to write - //12160 { //Copy the polynomial term into the flash array flashdata32[n-1].l=xnlookup[k][i][j].l;//Put the polynomial term onto the fla

I am using an STM32 Nucleo-F767ZI with RMII Ethernet + LAN8742A PHY and an example project based on lwIP/TCP-IP. I noticed a strange behavior: if I comment out MX_USB_OTG_FS_PCD_Init(), Ethernet communication stops working. If I keep it enabled, Ethernet works correctly. The peripheral initialization order is: MX_GPIO_Init(); MX_USART3_UART_Init(); MX_LWIP_Init(); MX_TIM3_Init(); MX_SPI4_Init(); MX_CAN1_Init(); MX_UART5_Init(); MX_USB_OTG_FS_PCD_Init(); Additional observations: SystemClock_Config() does not change Replacing MX_USB_OTG_FS_PCD_Init() with HAL_Delay() does not fix it So it does not look like a timing issue It seems that HAL_PCD_Init() / HAL_PCD_MspInit() for USB is enabling or configuring something indirectly that Ethernet depends on My question is: What could USB FS initialization be configuring that would make Ethernet work, even though they should be unrelated? I am thinking about possibilities such as: GPIO clocks being enabled indirectly MSP/NVIC config

Hi,In STM32CubeIDE/MX versions 1.19 and 6.15, I configured HRTIM, and it worked fine without any errors in CubeMX. I have updated STM32CubeIDE/MX to versions 2.1.1 and 6.16.1, and I have noticed the error messages shown in the pictures below.The dead time is not used, but when set Output 2 state MX displays the message "Set Sources: nothing to set as Dead Time is enabled, Output2 signal is defined based on Output1 Configuration Set Sources". The project operates like before the update, but it is not possible to add new Set Sources (I can only change the number of Set Sources to zero). How to understand this behaviour?Krzysztof  

Is there a detailed user manual available for the NUCLEO-U3C5ZI-Q?The product page links to a generic getting started document and a generic document on Nucleo 144 boards, but I can't see anything that lists the I/O or that documents the links.

Hello,i tried to generate for STM32f429i disco a project with graphic = touchgfx.1) i generate cubemx (for STM32f429i disco) project for SW4STM32 toolchain2) i generate a simple touchgfx project for SW4STM32 toolchainBut compilation under eclipse gives the following errors :HALSDL2.hpp:22:10: fatal error: SDL2/SDL_video.h: No such file or directoryHALSDL2.hpp:22:10: fatal error:SDL2/SDL_render.h: No such file or directorymain.cpp:30:10: fatal error: shellapi.h: No such file or directoryI can i solve these compilation errors ?thanksbest regards

I am planning to do an aging test which need capture the voltage of a net, but i found STM32U585OIY6QTR report a value about 40 while the actual voltage of ADC channel is close to VREF.Then i write a simple ADC demo to verify ADC configuration, and run my code on B-U585I-IOT02A board(based on STM32U585AII6Q), it report a correct value, but the same code report a wrong value on my board.I use ADC1  CHANNEL2(GPIOC GPIO_PIN_1) on both board.The only difference between B-U585I-IOT02A and my hardware is the different VREF i think(B-U585I-IOT02A use 3.3V, but my board use 2.5V).Is there any difference on ADC usage between STM32U585AII6Q and STM32U585OIY6QTR?You can find my ioc file and code in attachment, can anyone help me check my configuration? 

I am performing FTM Demo (Firmware Update) on ST25PC-NFC using ST's STEVAL Reader Board. I have disabled the Fast commands from settings, so FTM is using writeMsg command. Below, I have added a snippet of one of the packets being sent. 2026-03-24 10:04:20.785 writeMsg >> 22AA02329411AE665102E0FF08180C180C180C7FF87FF00000000000000000000000000000000003EC0FFC1C1C180C300C30003000300030003000180C1C1C0FF803F0000000000000000000000000000000007FC07FF018381818180C180C180C180C180C180C181818387FF07FE0000000000000000000000000000000007FF87FF818181818199819801F801F8019801998181818187FF87FF8000000000000000000000000000000003FFC3FFC0C0C0C0C0CCC0CC00FC00FC00CC00CC00C000C003FC03FC00000000000000000000000000000000003EC0FFC1C1C180C300C3000300030FE30FE300C380C1C1C0FFC03F0000000000000000000000000000000007E7E7E7E18181818182026-03-24 10:04:20.893 writeMsg << 0000 The packet aligns well with the Write Message request format from the datasheet except for the MsgLength and Message Data part.&n

Greetings - I would like to request consideration for a Latched INT option similar to that of the STHS34PF80 sensor (Register: CTRL3 22h). I typically utilize the VL53 with Min/Max threshold values and would like the option to have the INT signal latched when the object is within threshold values.Thank you for the consideration,Terry

I am working on a project that uses the ST67W611 for cloud connectivity, but I am experiencing some issues when trying to connect to AWS IoT Core.Note: The NCP is already flashed with the T01 binary.The AWS endpoint is correct — for the sake of this question, let’s assume it is:xxxxxx-something.amazonaws.com.What WorksBroker: test.mosquitto.orgI am able to publish data to the broker and receive data from it when using test.mosquitto.org.However, I am now trying to get it working so that our custom device can connect to AWS IoT Core.MQTT Configuration(This is my current MQTT configuration.) #define MQTT_BROKER "xxxxxxxxxxxxxxxxxxus-west-1.amazonaws.com" #define MQTT_PORT 8883 #define MQTT_CLIENT_ID "Thing01" #define MQTT_USE_TLS 4 #define MQTT_KEEPALIVE_S 60 static const char s_aws_ca_cert[] = "-----BEGIN CERTIFICATE-----\r\n" "Conten........\r\n" "Conten........\r\n" ..... "-----END CERTIFICATE-----\r\n" static const char s_aws_client_cert[] = "-----BEGIN CERTIFICATE---

Hello,My STM32H573I-DK board is bricked after a failed provisioning attempt.What happened:Accidentally changed PRODUCT_STATE from Open (0xED) to 0x17 (Provisioning) via programmerThen an AI coding assistant (Copilot) attempted some configuration via DFU mode and enabled TrustZoneI no longer have access to the PC where this was doneCurrent symptoms:SWD: "Unable to get core ID", "Cannot connect to access port 1"DA discovery (debugauth=2): "The target is unable to boot on RSS_DA or is in OPEN mode"DA regression (debugauth=1) with default STM32CubeFW_H5 keys: "Unable to detect DBGMCU Mailbox" or "unable to boot on RSS_DA"DFU (USB0): "Target device not found" (with boot jumper set to SYS/MEM)UART bootloader: timeoutWhat I tried:SWD with HOTPLUG, UR, HWrst, ap=0, freq=100DA regression with default key_3_leaf.pem and cert_leaf_chain.b64regression.bat from ROT_Provisioning\DADFU via User USB (CN17) with JP4 on USB-PD positionUART via ST-Link VCPSetup:Board: STM32H573I-DKSTM32CubeProgrammer: v2

Hi AllMaximum input voltage for this series of MCU per Table II of the datasheet is specified to be 4.0 VDC for all pins other than five-volt tolerant. Table 12 specifies the maximum injected current for all pins other than five-volt tolerant to be +/- 5 mA.Given the above specifications would it be permissible to exceed the maximum input voltage if the injected current is limited to lets say 0.1 mA by a resistor in series with the non five-volt tolerant I/O pin? If not what would be the reason?Regardsik

I am trying to develop a small scale lorawan app on a nucleo-wl55jc using the application example in stm32cube_fw_wl_v1.5.0 and have spent several hours trying to trace my error/bug in the software. All join attempts fail because the deveui as it appears in the se-identity.h file is ignored and the mcu derived value applied. Tracing this value to the lora_app.c file shows the se-identity.h file is correctly read and the macro expansion appears to give the correct value in the set user credentials section (lines 617-620) but the join is attempted using what I believe to be the mcu derived value. The same credentials work as expected when used under stm32cude_fw_wl_1.4.0 At the outset, I must confess it's 25 years since I did any serious programming so I may of missed something obvious but I would be grateful for any pointers as to why it's failing!  

Hello! I have been using the STM32H723ZG Nucleo board and am now trying to ping the STM32 device from a PC through an Ethernet connection, but the ping is not working. For ex: ping 192.168.10.XX (STM32 Static IP) No response is received. My board setup and module details are given below.Board / Setup MCU: STM32H723ZG (Nucleo) Interface: Ethernet (RMII) PHY: (e.g., LAN8742 – please confirm) Stack: lwIP (CubeMX generated) RTOS: FreeRTOS Connection: Ethernet cable through splitter (PC ↔ STM32) PC IP: 192.168.10.XX (static) STM32 IP: 192.168.10.XX (static) STM cube IDE version: 1.18.1 Observed Behavior (STM32 side logs): STM32 successfully receives ARP requests from PC.           Who has 192.168.10.50? Tell 192.168.10.100 (Captured by wireshark).      2. lwIP processes the request and generates an ARP reply.      3. ARP reply frame content (from debug log):           192.168.10.XX is at 00:80:XX:X

  I have already set the MTU to 3000 on the PC side. On the STM32H743 side, I have set the RXBUFFLEN, MTU, PBUF_POOL_SIZE, and other related memory configurations to 3000. I have configured and enabled Jumbo Frame and disable Jabber disable and Watchdog disable with ETH->MACCR |= (ETH_MACCR_JE | ETH_MACCR_WD | ETH_MACCR_JD | ETH_MACCR_GPSLCE);However, when I ping the STM32 from the PC with 1472 bytes, it is successful, but pings larger than 1472 bytes fail. Why is this happening? What have I not configured correctly?  

Hi,I am doing the evaluation of ST33KTPM2X-i2c on my Linux v6.1.70 embedded system.According to the 'Enabling TPM support in the Linux kernel from the version 6.1' from an5714-integrating-the-stsafetpm-trusted-platform-modules-with-linux-stmicroelectronics.pdf, :From the version 6.1, the TPM support can be enabled with a short method, which is available in the [TCG-TPM-I2C-DRV] github in Section 1: Open-source software resources.I understand the driver is available within the Linux v6.1 already. What I need to to is to enable the tpm_tis_i2c.c and add device node into my DTB. Done!But when I looked into the source code of Linux v6.1 (mainline or https://github.com/raspberrypi/linux/blob/rpi-6.1.y/drivers/char/tpm/tpm_tis_i2c.c#L385), the driver is not presented there - where I expect something like: .compatible = "st,st33ktpm-i2c". Could you help me?

Hello,After spending several days investigating this topic and reviewing all the documentation I could find, I am still completely stuck on how to proceed with implementing STiROT + OEMuROT on my STM32H7S3.An important point is that I am trying to add this security architecture to a project that is already at a fairly advanced stage of development. The project was originally built on top of the XIP template provided by ST:https://github.com/STMicroelectronics/STM32CubeH7RS/tree/main/Projects/NUCLEO-H7S3L8/Templates/Template_XIP The difficulty comes from the fact that, in the XIP context, the project only includes these layers:AppliBootExtMemLoaderAs a first step, I imported ROT_Provisioning into the project in a separate folder. However, I still do not see how I should properly integrate or adapt the following components into my current project structure:OEMiROT_AppliOEMiROT_BootSTiROT_AppliSTiROT_BootShould I try to merge the `*_Appli` projects into my existing Appli context, and

  Hello, I am working on STM32 NUCLEO-G431RB using STM32CubeIDE and FreeRTOS (CMSIS-RTOS v2). I am trying to implement the following requirement: Requirement ADC1 → 1 Channel using Interrupt ADC2 → 7 Channels using DMA Both should run simultaneously with FreeRTOS ADC Configuration ADC1 (Interrupt) Single channel (PA0) Using HAL_ADC_Start_IT() Used for detecting external voltage Expected Behavior: When I connect external power supply to PA0 PA0 should show voltage value Remaining 7 channels should show 0 Example:     PA0 = 2.5V (Interrupt)PA1 = 0PA6 = 0PA7 = 0PC0 = 0PC1 = 0PC2 = 0PC3 = 0       ADC2 (DMA) 7 Channels: PA1 PA6 PA7 PC0 PC1 PC2 PC3 Configuration: Scan conversion enabled Continuous conversion enabled DMA circular mode Using HAL_ADC_Start_DMA() Expected Behavior: If I connect external voltage to PA1     PA0 = 0PA1 = 2.5V (DMA)PA6 = 0PA7 = 0PC0 = 0PC1 = 0PC2 = 0PC3 = 0   &nb

Hi ST Team,I'm creating project in the motor control workbench,I had selected hardwars are1. STM32G4EVAL1 Board2. Motor Drive3. Motor once i selected in the tool as shown in below.in this connector are not available to connect to the main board to motor drive.need to import the .Json file but in portal there is .Json file.This connector (X-NUCLEO-IHM09M2) is needed to use .Could you please help me on this connector how to download from st website. 

When connecting to our stm32n6 using a stm32 Programmer we get an unstable connection. Connecting with a low clock rate (5khz instead of 8000khz) improved the Issue but there still isn't a reliable way to connect to the board. Some retries are needed to get a connection. Also after some time the connection doesnt work entierly and the MCU needs to be powercycled.