Solved

I am using the STM32U575 on a custom board and see that AN2606 indicates PG10 becomes a SPI MISO output in bootloader mode. I would like to connect this same SPI port to another device with the STM32 in master mode for the user application. In order to avoid contention on this signal, I am hoping that in bootloader mode the SPI MISO output is tri-stated if the associated NSS is negated (high). I have seen a couple of posts that touch on this question but I have not been able to confirm the behavior. For example: https://community.st.com/t5/stm32-mcus-products/spi-pin-states-during-bootloader-detection-phase/m-p/696205 Another post for a different part mentions that the SPI port can be setup to support multiple slaves by tri-stating MISO when not selected, but I don't know if this is the default behavior in bootloader mode for this device. Thank you for any feedback.   -Jason

As the title says, the STM32G47 PA9 pin appears to be set high in boot mode opposed to pulled high though a resistor which is states in AN2606. This is becoming a problem because it introduces negative behaviors in our design when we try to reprogram. Is this a known behavior documented elsewhere?I have gotten pretty frustrated when migrating from the STMF3 family to the STMG4 since there are many more pins being pulled or set in one direction or another during boot mode. Is there any way to disable some of these hardware defined communications protocols during the boot loader mode initiated by the BOOT0 pin?

I have installed MCSDK 6.4.1I can run the workbench (MotorControl Workbench_6.4.1) without any problem.But i cannot run the Motor pilot application.At first there was an error stating "The code execution cannot proceed because MSVCP140.dll was not found Reinstalling the program may fix this problem"I then installed "Microsoft Visual c++ 2015-2022 Redistributable (x64) 14.44.35211This error is not present anymore but nothing is starting when clicking on the motor pilot icon, no new window appears. I tried reinstalling the mcsdk without any change observed.I can see the following in the MotorPilot.log :2025-08-27 17:30:11.844 INFO-:MotorPilot is running in C:/Program Files (x86)/STMicroelectronics/MC_SDK_6.4.1/Utilities/PC_Software/STMotorPilot 2025-08-27 17:30:11.844 INFO-:Application is starting : MotorPilot version:6.4.1 2025-08-27 17:30:11.844 INFO-:ini file path=C:/Users/vboxuser/AppData/Roaming/ST Microelectronics/ST Motor Pilot.ini 2025-08-27 17:30:11.850 INFO-:Polling time out is

Hello everyone,How to calibrate the hse clock, I use NUCLEO-WL33CC2 boards.Best regards

Hoping someone could help.  I did a full erase on the stm32h747i_disco from the stm32cube programmer.  I attempted (several times) to upload the STM32Cube_Demo-STM32H747I-DISCO-V1.0.0_FULL.hex and got the following error:14:09:58 : Opening and parsing file: STM32Cube_Demo-STM32H747I-DISCO-V1.0.0_FULL.hex14:09:58 : Memory Programming ...14:09:58 : File : STM32Cube_Demo-STM32H747I-DISCO-V1.0.0_FULL.hex14:10:00 : Size : 58.38 MB14:10:00 : Address : 0x0800000014:10:00 : Download in Progress:14:10:04 : Error: failed to download Sector[0]14:10:04 : Error: failed to download the File14:10:05 : Memory [0x08000000 : 0x08200000] - Checksum : 0x139CE03CDoes anyone have a suggestion?

 Hello,On the STM32N6, I am using DCMIPP_PIXEL_PACKER_FORMAT_YUV422_1.I am seeing the correct coloring when using CMW_MIRRORFLIP_NONE and the incorrect coloring when setting CMW_MIRRORFLIP_FLIP. Any help getting the correct DCMIPP_ColorConversionConfTypeDef color_conf for the CMW_MIRRORFLIP_FLIP ? ... if (HAL_DCMIPP_PIPE_EnableRedBlueSwap(&hcamera_dcmipp, DCMIPP_PIPE1) != HAL_OK) { Error_Handler(); } #define N10(val) (((val) ^ 0x7FF) + 1) DCMIPP_ColorConversionConfTypeDef color_conf = { .ClampOutputSamples = ENABLE, .OutputSamplesType = DCMIPP_CLAMP_YUV, .RR = N10(26), .RG = N10(87), .RB = 112, .RA = 128, .GR = 47, .GG = 157, .GB = 16, .GA = 16, .BR = 112, .BG = N10(102), .BB = N10(10), .BA = 128, }; if (HAL_DCMIPP_PIPE_SetYUVConversionConfig(&hcamera_dcmipp, DCMIPP_PIPE1, &color_conf) != HAL_OK) { Error_Handler(); } if (HAL_DCMIPP_PIPE_EnableYUVConversion(&hcamera_dcmipp, DCMIPP_PIPE1) != HAL_OK) { Error_H

I have been asked to implement functionality for a Feig NFC-reader ( ID CPR30-USB) into an existing C# desktop-application.However, I only find some SDK-like thing for Java (the "ST25PC-NFC"). But I would need something for C, or C++, or C# or VisualBasic. Or anything that would be .NET-compatible.A similar question has been asked here: Solved: ST25 SDK for .NET - STMicroelectronics Community It is marked as "solved", but for the life of me I cannot understand how this is solved, since the "accepted solution" from "customer support" only points to the same Java code.

The codebase is generated by CubeMX and now I'm facing issues during debug.debug method is SWD using ST-LINK V2.In debug mode, after resume fron HAL_Init(); , the code will crashed into system memory zone and have no debug information.Break at address "0x1fff12ca" with no debug information available, or outside of program code.the location of the address varies around 0x1fffxxxx sometimes.to be exact, the crash will happen when:Initialize the IWDGUsing Flash R/W OperationStart Timer (But not Init)In STM32G031, 0x1fff12ca is located at system memory area where it houses the factory bootloader.What confuses me is, I have another code project that has basically the same start up code at main() but it works just fine (in another STM32G031, and hardware connection is the same regarding BOOT0 pin). Tried Clean project and rebuild, restart IDE and change optimization, changing minimum heap and stack, absolutely no help whatsoever. I have not try to load

Is there any mapping document like this one on the H7S3L8 as there is for the H743ZI-B01?I only find this document:https://www.st.com/content/ccc/resource/technical/document/user_manual/group0/26/49/90/2e/33/0d/4a/da/DM00244518/files/DM00244518.pdf/jcr:content/translations/en.DM00244518.pdf   Thanks for your help!

Hi,   I have been working with a STM32U575 MCU and something strange has happened that I spent a lot of time trying to find the root cause for it and I am not able to understand what is wrong. I work with I2C slave interrupts and have FreeRTOS running. I realized FreeRTOS gets stuck in checking priorities when a FromISR function is called from the I2C handler. Long story short, checking all the configs many times, I checked what are the priority of the IRQs?     HAL_NVIC_SetPriority(I2C1_EV_IRQn, NVIC_IRQ_PRIOR_I2C_SLAVE_EV, NVIC_IRQ_SUB_PRIOR_I2C_SLAVE_EV); HAL_NVIC_SetPriority(I2C1_ER_IRQn, NVIC_IRQ_PRIOR_I2C_SLAVE_ER, NVIC_IRQ_SUB_PRIOR_I2C_SLAVE_ER); HAL_NVIC_EnableIRQ(I2C1_EV_IRQn); HAL_NVIC_EnableIRQ(I2C1_ER_IRQn); PRINT("I2C1_EV raw priority: %lu\n", NVIC_GetPriority(I2C1_EV_IRQn)); PRINT("I2C1_ER raw priority: %lu\n", NVIC_GetPriority(I2C1_ER_IRQn)); PRINT("__NVIC_PRIO_BITS = %d\n", __NVIC_PRIO_BITS); PRINT("configPRIO_BITS = %d", configPRIO_BITS);   having

I have the STLink V3MINIE. When connected to the PC the red power LED is on. But I can't program any device because there is not target voltage. ST Prog (v2.17) shows Target voltage 0.00 VHow can I fix this? Is there a jumper or solder connection missing on the stlink? Or is the board damaged?Thanks for help! 

Hi, I'm seeking some advice on using a STM32U5A5 in USB device only via a USBC connection.Any previous USB "device only" designs I've worked on only required connections to D+, D- and ground to communicate. These designs have been USB2x.The U5A5 has lots of cool features regarding the USB module etc but we have assigned other features to the pins that are associated with the more the more advanced features like CCx and VBUS SENSE etc. As we plan to use the part in device only mode am I correct in assuming that reallocating the unused pins OK to do and that D+, D- and GND are the only connections required?We are using the USBC port for a communications link to a PC using CDC, and developing with the associated NUCLEO-U5A5ZJ-Q board. However our product schematic will look like the one in the attached schematic snippet.Thanks in advanceCaleb

Hi everyone,I’m currently working on a project involving predictive maintenance and anomaly detection using the STWINBX1 (STEVAL-STWINBX1) board. I’ve successfully configured the board and flashed it using STM32CubeIDE, ensuring everything is set up as expected. I’ve also downloaded the NanoEdge Datalogger and flashed it using STM32 ST-Link Utility, but despite everything being correctly configured, NanoEdge AI Studio is not receiving any data from the board.Here’s what I’ve checked so far:The board is properly connected to my PC.I’ve verified the COM port number, and I'm sure it's correct.The NanoEdge Datalogger has been flashed successfully.The board’s sensors are properly connected and powered.Despite these steps, the data is not being received in NanoEdge AI Studio. I’ve also ensured that no other processes are using the COM port, and I’ve checked that all configurations are aligned with the expected setup.Can anyone suggest what could be causing this issue or guide me on where I m

Hello,We are working with an STM32F429ZIT6TR to design an 800x480 LCD Display Controller Board,I configured the FMC with the 8080 interface to receive data from Main Board (another provider), and also enabled SDRAM through the FMC. The LTDC is used to drive the LCD.The plan is to transfer data to our Display Controller board via the 8080 interface and then use the LTDC for display refresh. The data lines are shared between the 8080 interface and the SDRAM, but they have different chip select signals.we built a first prototype, but when we tried to write data into the SDRAM, we observed sporadic/incorrect values.My questions are:Could sharing the data lines between the 8080 interface and SDRAM cause signal integrity or bus contention issues, even though the chip selects are different?Do you have any recommendations for PCB layout in this case?

Hi, I'm running a (custom) board that makes use of an STM32H723VET and a LAN8742. A project is set up in CubeMX that makes use of lwIP together with this LAN-chip (there is an issue in CubeMX which deselects the LAN8742 on loading the CubeMX file, but this is something I have already catched). lwIP is configured to make use of a static IP. Now when I run my code in CubeIDE, I can see the interface is set up properly and it detects a 100 MBit duplex connection. Unfortunately that's all what works. In call of netif_set_link_up(), an ARP-request is tried to be transmitted. Some layers deeper, within the HAL-functions, this ARP-request can not be sent. Function HAL_ETH_Transmit() ends up in an timeout while waiting for these ARP-data being transmitted. That lets me assume, something wents wrong with the hardware initialisation. However, functions HAL_ETH_Init() and LAN8742_Init() go through without any error and function LAN8742_GetLinkState() returns a proper link state&nbs

Hello,I'm evaluating ST25DV for an application and am trying to characterize max available VEH voltage. I'm using STEVAL-SMARTAG1 board, and monitoring VEH output while enabling "Energy Harvesting" feature on the "NFC Tap" app.  I can't seem to get above 3.4V on the VEH pin.I've used both the embedded antenna, and as well as an external antenna (at which point I cut the embedded antenna traces). With the external antenna I made sure it is tuned to 13.56MHz while connected to ST25DV front end. I can confirm that the induced voltage is 9V (which seems to be due a clamping because when I disconnect the ST25DV I can get induced voltages well over 20V).I'm trying to understand what is limiting VEH to 3.4V when I can clearly get quite a bit of voltage from the coil.  The 3.4V limit seems to be also due to a clamp, because irrespective of the antenna position the voltage won't go above that, period. Once I move the antenna sufficiently far away, at some distance the VEH starts to qu

https://controllerstech.com/stm32-usb-host-msc/I downloaded the app from this site, and the project from 2020 works. However, even though I followed the same tutorial, my code doesn't work in the 2025 version.

Split from https://community.st.com/t5/stm32-mcus-touchgfx-and-gui/how-to-work-with-buttons-without-touch-panel/td-p/165514Hi,I’m working with TouchGFX on an H743, following the example from the Nucleo board, and I have the state of a physical key (e.g., a GPIO button) available when MB1642ButtonController::sample is called. What is the simplest way to interact with TouchGFX based on this key state?Specifically, I want to know:Do I have to handle everything through code by manually triggering events for widgets (like buttons)?Is there any way to map a key press (e.g., key "1") to a TouchGFX button press, similar to how the touch interface works, directly from the GUI?Thanks in advance for any help or suggestions!

Hey folks, I’m new to PCB design and I ran into something odd. I had a small board made for a project, but during testing some of the traces get warm and one even browned slightly. I thought I sized them correctly in KiCad, but maybe I messed up.Do PCBs have some kind of standard design rules for current handling? And how do you know what thickness or width to use for power vs signal traces? I keep hearing terms like silkscreen, ground plane, etc., but it’s still confusing to me. Any tips? @Member

I have tried to route the LSI clock to PA2 pin in my Nucleo Board G474RE without success. SB13 & SB17 are open (it means ST Link is not connected to PA2 pin). Configuration was carried out with STMCube32 Mx but I don´t obtain the CLK in PA2. I have checked also the LSCOSEL and LSCOEN bits and are correct configured.My dudes are: 1) Muss RTC be activated to obtain the desired behaviour? My suposition is NO, because when I route the LSI to MCO pin (PA8) it works fine.2) did I forget to modify something else in Nucleo Board G474RE?Thanks in advance!   

Board:STM32U5A9xxI set the Number of PDO to define = 5 in the cubeide.But after generate code, the code in usbpd_pdo_defs.h, macro:PORT0_NB_SINKPDO is still 1U.I also checked the file usbpd_pdo_defs_u5.ftl in cubeide's location, the macro PORT0_NB_SINKPDO is a value param from cubeide indeed, but it seems not effective. Is a bug?/* Define ------------------------------------------------------------------*/ #define PORT0_NB_SOURCEPDO 0U /* Number of Source PDOs (applicable for port 0) */ #define PORT0_NB_SINKPDO 1U /* Number of Sink PDOs (applicable for port 0) */ #define PORT1_NB_SOURCEPDO 0U /* Number of Source PDOs (applicable for port 1) */ #define PORT1_NB_SINKPDO 0U /* Number of Sink PDOs (applicable for port 1) */ 

We plan to implement a VL53L1X driver based on this API for our Open Source Real-Time OS (community project) and would have to publish the API source code (content of directory STSW-IMG009_v3.5.4/API only) either as part of the GitHub repository of the OS or as a separate GitHub repository to use it as a package.I had to accept the PLLA (SLA0081) to get the VL53L1X ULD API (STSW-IMG009) which restricts the use and the distribution of the code a lot. On the other hand this PLLA (SLA0081) also says that some portions of the licensed materials might contain Open Source Software subject to Open Source Terms.The files in the API itself tell * This software is licensed under terms that can be found in the LICENSE file * in the root directory of this software component. * If no LICENSE file comes with this software, it is provided AS-IS.And the `License.txt` in directory `STSW-IMG009_v3.5.4/API` saysThis software component is provided to you as part of a software package and appli

Hello Engs, How do you calculate the mission profile for the LDO40LPU33RY LDO regulator in an automotive application? Best regards

Split from this thread. thanks to @Ozone @Karl Yamashita, this afternoon I have tried to extend can2.0 to canfd with my project of stm32g474vet6.  I found some strange things, I think there may be a bug of stm32g474vet6 fdcan module. I modifed the FDCAN_TxHeader to FD_Frame and datelength to 64byte. for  FDCAN_RxHeader, almost nothing to modify. then i used an app on PC to send a 64bytes CAN message,  then my code received the 64bytes message and copied to rxbuffer, the rxbuffer had 64bytes data, but FDCAN_RxHeader.datalength is 15. it is not 64.  i think this is a bug of stm32g474vet6, it received 64bytes data but FDCAN_RxHeader.datalength is 15. I have no can tool now (with used by other people), when i have the can tool, i will take screenshot to show the strange thing. hello @mƎALLEm @Saket_Om did you meet FDCAN received 64bytes but  FDCAN_RxHeader.datalength is 15? is there some configuration I miss?   Thanks a

Hello,What options need to be enabled or disabled to work in card reading or card emulation (tag) modes?I am using X-NUCLEO-NFC08A1 and X-CUBE-NFC6. Currently the cards are read, but not emulated (I need to send a link to the smartphone).