Join discussions in the Product Forums. Ask questions, learn from your peers, and share insights on ST solutions to accelerate your design journey.
Most recent activity
Hi Team,Is there any framework or lib support available from ST for automation testing of TouchGFX based UI either on simulator or on actual device?If anyone has any idea or workaround, then please share!Thanks
Using STM32CubeIDE on macos (with STM32H7431VITx, FWIW), the Debug Console has a pretty poor interface, where there's no readline support and even basic things like "arrow up" to recall the latest command doesn't work, rather it moves the cursor up in the text. Gdb's output is black, the text I type is green and when executing a command, it gets echoed in red to the console. A while back I ran the same version on macos and Linux; on Linux on it was providing a full terminal with readline support, as you'd expect, but on macos it was like this and it hasn't improved in the intervening years. Is there some setting that I can enabled to make it a proper terminal with readline support and all on macos?Version: 2.0.0Build: 26820_20251114_1348 (UTC)sample screenshot below:
Left commented out SFU_NO_SWAP and defined ENABLE_IMAGE_STATE_HANDLING in app_sfu.h, but when trying to build SECoreBin and SBSFU errors appear:/Middlewares/ST/STM32_Secure_Engine/Core/se_fwimg.h:47:61: error: unknown type name 'SE_FwStateTypeDef'Is there something I am missing? I selected AES-GCM crypto schemeI have followed https://www.st.com/resource/en/application_note/an5056-integration-guide-for-the-xcubesbsfu-stm32cube-expansion-package-stmicroelectronics.pdf (Chapter 8.5)
Hi all! I'm trying to implement a wear leveling in user memory accessed from I2C for a counter on bit level. My question is: Are ST25DV eeprom byte cells similar to classic ones where each write cycle starts with a clear (which sets the byte to 0xFF) and after it writes 0 bits where needed? Or is there somewhere an inversion taking place? Could someone help me, by pointing out some directions in datasheets for me in this matter? I found another post where memory default state is quoted from the datasheet which specifies that factory default is 0x00, but this doesn't imply that it's default state isn't 0xFF. Thanks in advance, notram
I have been using RFAL succesfully with STM32L4. For a more price sensitive project I need to port the code to STMG070 and I cannot get RFID readings to work. Measuring ampltiude gives same result on both codes:st25r3911MeasureAmplitude(&c); printf("Amplitude %d\n\r", c); The following have been verified:* Same RFID PCB is used for both processors (RFID PCB and processor PCB are connected by pin connector)* Same RFID card is used* Init of RFAL gives ID 13 on both codes* GPIO interrups are generated* Same LDO on both PCB* Voltage to ST25R3911B is stable* Both processors runs at same frequency 16 MHz On STM32L4 the state change (during a succesful RFID read) of rfalNfcWorker goes like:RFAL_NFC_STATE_IDLERFAL_NFC_STATE_POLL_TECHDETECT x 19RFAL_NFC_STATE_POLL_COLAVOIDANCE x 29RFAL_NFC_STATE_POLL_ACTIVATION x 2But when running on STM32G070 RFAL_NFC_STATE_IDLERFAL_NFC_STATE_POLL_TECHDETECTRFAL_NFC_STATE_LISTEN_TECHDETECT until timeout Anyone have
Hi, I try to get the USB-Host running with USBX. Hardware is a custom board with TCPP02 and STM32U575. Init process is running, but I never get an interrupt (ux_host_event_callback) when plugging in a USB stick. Any idea? ioc file and schematic are attached. Best regards, Achim
I am using STM32CubeIDE version 1.19.0.ProblemI get the error:“Authentication Error Manager – Connection lost”What I triedChecked internet connection (working fine)Used mobile hotspotChecked connection in Firmware Updater (shows OK)System detailsOS: Windows 11 Pro Laptop: Lenovo ThinkPad T14Board: STM32F407VGT6 / STM32F407 Discovery boardAdditional infoThe issue occurs even though the firmware updater shows a valid connection. Both Wi-Fi and mobile hotspot give the same error.QuestionWhat could be causing this authentication/network issue in STM32CubeIDE, and how can I fix it?
For users having / wanting / needing their own VSCode C++ setup it would be very beneficial to have the STM32 debugging VSCode extensions not rely on the rest of the STM32 Cube extensions.Neither do I want nor do I need all of the bundle management, CMake replacement, code analysis and what not stuff the VSCode extensions are doing.Currently, st-cube-ide-stlink-gdbserver, st-cube-ide-debug-generic-gdbserver, st-cube-ide-debug-core (whatever I would really need) pull in the Core and, especially annoying and not really understandable for me, the CMake Support extension.I'd appreciate to have a debugging support extension that works well with any build + edit setup, just like cortex-debug.
The MCU I use is H533, but I guess the SPI peripheral in other MCUs would be similar.I'm looking for the recommended way to regularly transmit over SPI "small" data frames (in the sense that one frame fits into the FIFO) that can vary in size. For example, in response to different events I would be updating values of different DACs or shift registers and they all have their own data frame format and size, usually between 16 and 32 bits.SPI peripheral has TSIZE and DSIZE settings seemingly exactly for that, but they require disabling the SPI peripheral to be changed (for TSIZE it's documented, for DSIZE, it seems not), and it adds latency to transfers.So far it seems the optimal approach in my case is to as follows. Please bear with me for a moment and let me know if I'm missing something.1. Keep DSIZE at 8 bits.2. Keep the SPI enabled and set CSTART once at the beginning.LL_SPI_Enable(SPIx); LL_SPI_StartMasterTransfer(SPIx);3. When transferring, manually fill the FIFO with the data fra
Hello all,I’m working with an STM32 microcontroller (specifically the STM32H743), and I have a question regarding the use of an external TCXO as the HSE clock source.As per the datasheet, when using an external clock source (such as a TCXO), the HSE must be configured in bypass mode, and the input clock is expected to meet the digital I/O thresholds (e.g., 0.7 × VDD for logic high). However, many high-quality TCXOs have typical output swings of only 0.8–1 Vp-p (clipped sine wave), which do not meet CMOS thresholds when VDD is 3.3 V.Therefore, directly driving OSC_IN with such a TCXO in bypass mode is not viable per the datasheet.That said, I made an observation I’d like to confirm with you:While using a crystal in crystal resonator mode (not bypass), I probed the OSC_IN pin using a low-capacitance active probe and measured a signal of approximately 1 Vp-p. Since this amplitude is generated internally by the oscillator circuit when using a crystal, it seems the STM32’s HSE input is desi
The STM32L476 does not have an nBOOT0 option bit in its option bytes. Is there a way to boot from the main flash memory without using the BOOT0 pin?
I'm developing using the STM32WBA65I-DK1. I'd like to know how to implement interrupt handling for button presses. It appears that stm32wba65i_discovery.h does not contain any APIs related to button presses (which is perhaps to be expected since the DK does not have push buttons). The sample code I'm using is BLE_HeartRate_Thread. If you have any source code that might be helpful, please let me know.
Hello everyone,I'm working with the STM32L562E-DK board and the STM32Cube_FW_L5_V1.5.0 firmware. I want to integrate my own code (which reads a sensor MPU6050 via I2C) into the STM32CubeL5 TFM (Trusted Firmware-M) application, running it in the Non Secure environment. The base project I'm using is TFM_Appli, which comes in the package, and I've added my source code to the NonSecure section.I created a separate project in STM32CubeMX using the board's I2C1, which utilizes pins PB6 (SCL) and PB7 (SDA). I then generated the code and copied the I2C communication initialization code into the "main.c" file of my "TFM_Appli_NonSecure" project. Specifically:/* This is before "int main (void)"-----------------------*/ I2C_HandleTypeDef hi2c1;/*------------- I'm calling these function from "int main(void)" ------------*/ static void MX_GPIO_Init(void) { /* USER CODE BEGIN MX_GPIO_Init_1 */ /* USER CODE END MX_GPIO_Init_1 */ /* GPIO Ports Clock Enable */ __HAL_RCC_GPIOB_CLK_ENABLE(); __H
Hi everyone,I'm facing a really frustrating issue where my STM32CubeIDE can no longer detect my ST-LINK, and I've narrowed the problem down specifically to stlinkserver.exe failing to launch. This problem appeared completely randomly on my PC.Here are the symptoms and what I have already ruled out:The Problem: When I try to manually execute stlinkserver.exe via PowerShell to see what's wrong, it exits instantly without printing any output, errors, or logs. Even forcing the help menu or debug mode does absolutely nothing:PowerShell PS C:\Program Files (x86)\STMicroelectronics\stlink_server> .\stlinkserver.exe PS C:\Program Files (x86)\STMicroelectronics\stlink_server> .\stlinkserver.exe -d 5 PS C:\Program Files (x86)\STMicroelectronics\stlink_server> .\stlinkserver.exe -h Running Get-Process stlinkserver confirms the process is not running in the background at all. It just dies immediately upon execution.What DOES work (Hardware & Drivers are fine):STM32CubeProgrammer
Hello everyone i am currently working on a project with a NUCLEO-C092RC Board. With this Board i want to send OBD-II Frames to my car and receive reponses with data. I also use a LCD Display via SPI. But now i have a problem. i connected CANH/L with the Board. I also connected 12V and GND from the OBD-II-Port to a buck converter, which steps the voltage down to 7 V for VIN on the Board, which should be within spec. Then i tried to send a frame, but i did not get a response, when the Board was only powered by 12V via buck converter. After that i think i broke my MCU, because then i connected my PC with the Board and switched the power source back from VIN to ST-Link with a jumper. I was able to debug my programm. but when i also disconnected CANL and CANH from the Board or switching the jumper from VIN to ST-Link (i am nor sure anymore), the red LED from STMPS2141STR came on. It only turns off, if i disconnect VDD from 3V3 Volt with pulling JP5. I also measured from what i think
Hello. I've a problem regarding LSE On stm32l562xx mcu. Sometimes it boots, sometimes it doesn't "90 % of time it generates timeout Error" . and it takes too much time to boot up to 4 seconds. I've tried all your sdk initializations, also tried setting lse drive to all 4 modes but nothing changes. Same behaviour and same time. Below is my initialization code and attached how we connect LSE on our board. Regards RCC_OscInitTypeDef RCC_OscInitStruct = {0}; RCC_ClkInitTypeDef RCC_ClkInitStruct = {0}; /** Configure the main internal regulator output voltage */ if (HAL_PWREx_ControlVoltageScaling(PWR_REGULATOR_VOLTAGE_SCALE0) != HAL_OK) { /*Error*/ } /** Configure LSE Drive Capability */ HAL_PWR_EnableBkUpAccess(); __HAL_RCC_LSEDRIVE_CONFIG(RCC_LSEDRIVE_HIGH); /** Initializes the RCC Oscillators according to the specified parameters * in the RCC_OscInitTypeDef structure. */ RCC_OscIn
Hello,My goal is to wakeup the end node to send a single frame then go to shutdown mode, but I'm having some hard time putting the device in shutdown modeI am calling HAL_PWREx_EnterSHUTDOWNMode(); in LoRaWAN_Process() function, after checking on a successful TxDone state.
This thread is split from this old discussion @FBL RCC_USBPHY1REFCLKSOURCE_OTGPHY1 and RCC_USBOTGHS1CLKSOURCE_HSE_DIV2 are missing in generated code I created a simple FSBL application that is jump to the AppliThe Appli is using the same approach (SW solution) like it was implemented inside "Ux_Device_CDC_ACM" example, (it was migrated in to the Appli)Currently, during debug, I am observing the same issue like it was described before (stuck in USB_CoreReset() during checking the "USBx->GRSTCTL & USB_OTG_GRSTCTL_CSRST" )The solution, that you provided, it looks like it does not working anymore by using the latest Cube_FW and generated compilation errors (no defines for the RCC_USBPHY1REFCLKSOURCE_OTGPHY1 and RCC_USBOTGHS1CLKSOURCE_HSE_DIV2).Could you please provide a solution (it would be better to see an example) how to solve this issue base on the latest MXCube and STM32CubeIDE versions. Currently it is : STM32CubeIDE_2.1.1 STM32Cube_FW_N6_V1.3.
Hello, I would like to learn if there is an easy way in STM32CubeMX2 to start a new project with an existing ioc2 file. It seems that the only way I can do this is make a copy of the ioc2 file, do a text find and replace for the name of the project and reopen the project in MX2. In essence, I like to start a project from a working ioc2 configuration and modify it to work on a fork of the project. I don't want to recreate a complex configuration from scratch because I found the hard way that it is easy to make mistakes or to omit something. Thank you, -Gil Please check the follow-up discussion here: Issue with Save As feature in STM32CubeMX2
I want to change /opt/st/stm32cubeide_2.0.0/plugins/com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.linux64_2.2.300.202508131133/tools/bin/STM32_Programmer_CLIto/opt/st/stm32cubeide_1.4.0/plugins/com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.linux64_1.4.0.202007081208/tools/bin/STM32_Programmer_CLIbecause my computer OS is too old to run the latest version. How can I do that with Version: 2.0.0?
Hi - when I attempt to download the driver for this device the download never completes; I get a file "Unconfirmednnnn.crdownload" in my download folder. I'm using Edge browser on a Windows 11 Home 64 bit operating system. Using Norton, can't see anything there that would prevent the download. Have successfully downloaded from other sites many times with no issues.Anyone with any insights?Thanks.
I'm designing a USB-C charging circuit for a battery-powered device using the STUSB4531 for PD negotiation alongside a BQ25792 buck-boost battery charger. The BQ25792 handles the full VBUS power path internally (inrush limiting, reverse current protection, OVP, and dead battery support), so I'm trying to understand whether the external P-FET that STUSB4531 normally drives is still required. Specifically: 1. Can the GATE pin be left NC or tied off without affecting CC detection and PD negotiation? Or does the IC require a valid FET load on GATE to operate correctly?2. If the GATE pin must drive something, would it be acceptable to connect GATE to the BQ25792's CE (charge enable) pin instead of a FET gate — effectively using it as a charger enable signal rather than a loadswitch?3. Dead battery / no battery scenario: I need the system to power up from VBUS even when the battery is absent or fully depleted. The BQ25792 already supports dead battery mode on its own. If the external FE
Hello, I want to use an I2C port of a STM32F411 MCU (MCU_A) in target mode to receive data from another MCU (MCU_B), MCU_B code already existing and verified with other receivers.I configured the project with STM32CubeMX, with interrupts enabled to handle communication in interrupt mode.I used MX standard settings to generate CubeIDE project with HAL code.With some effort for setting up the initialization and other code for MCU_A in CubeIDE, communication looks ok from sending MCU_B perspective.Additional check of SDA and SCL signals with DSO looks ok to. But the problem was: No data was transfered to the receive data buffer in MCU_A. After several hours of debugging, I found a suspicious code section in the HAL code (stm32f4xx_hal_i2c.c).In the HAL function static void I2C_Slave_ADDR(I2C_HandleTypeDef *hi2c, uint32_t IT2Flags)which is called in HAL_I2C_EV_IRQHandler ()when adress matches, the direction flag received from MCU_B
Hello Community,I'm trying to interface STM32 P-NUCLEO-WB55 with ADS1293 via SPI communication protocol, But there is a issue I'm unable to read data, to verify the SPI I tried to print "Reg10 = %d\r\n" but it is returning zero as value. I'm attaching the connections diagram and ioc diagram and code file, Can anyone please help me with where I'm getting wrong..Thank you
Hello,I made a small USB Power Delivery trace/monitor tool using the STM32G071B-DISCO.STM32CubeMonitor-UCPD v1.4 does not correctly decode some PDO types defined in USB-PD 3.0 and later (e.g., AVS), which makes analysis difficult.So I put together a tool that can decode and visualize these PDOs more clearly.Project repository:https://github.com/aso/UCPD-MonitorExample output is shown below:[Screenshot:Apple40WSPRAVS.png] If you have a chance to try it, I’d be interested in any feedback or suggestions.
ST Community highlights – April to June 2026
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.