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,I encountered a strange problem while using stm32cubeMX in a new project.Everytime i saved the code files and then regenerated the code using stm32cubeMX,the user code will gone.A example,"#include "led.h" " have been insert in the user code zone,then i saved the project,and regenerated code using stm32cubeMX.then "#include "led.h" " is missing..."Keep User Code When re-generating" already been checked as shown in the figure。stm32cubeMX version 6.16.1.any advise will be appreciated,thx.
I have been using PE micro Multilink FX for several years, but its Linux support is terrible. Is there a ST (or another) alternative with this functionality compatible with stm32CubeIDE? I just need to supply power (up to 100 mA at 3.3V) to my board for debugging. I don't need high tracing performance or anything like that. Thanks in advance,Gaston
In STM32CubeCLT (including latest 1.20.0 version), there is CMake but no make.To build projects from CubeMx gererated make projects, I have to install STM32CubeIDE and add below into PATH. C:\ST\STM32CubeIDE_2.0.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.make.win32_2.2.0.202409170845\tools\bin Manually install standard GnuWin32 Make is not enough because it miss some additional tools such as rm.exe, mkdir.exe ...
Hi,I am trying to enable secure boot in STM32mp157f-ev1 board. I am using the Developer Package source code provided by ST. I am using this command to generate the tf-a.stm32:make E=0 -f ../Makefile.sdk.stm32mp1 TF_A_DEVICETREE=stm32mp157f-ev1 TF_A_CONFIG="optee-sdcard optee-programmer-usb" TRUSTED_BOARD_BOOT=1 GENERATE_COT=1 ROT_KEY=<path>/privatekey.pem ROT_KEY_PWD=<password> KEY_ALG=ecdsa MBEDTLS_DIR=<path>/mbedtls-3.4.1 DYN_DISABLE_AUTH=0 DEPLOYDIR=$FIP_DEPLOYDIR_ROOT/arm-trusted-firmware stm32But I am getting an error:LD SOURCES-stm32mp-openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11/stm32mp-openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11/sources/ostl-linux/tf-a-stm32mp-v2.10.13-stm32mp-r2-r0/tf-a-stm32mp-v2.10.13-stm32mp-r2/../build/optee-sdcard-stm32mp157f-ev1/bl2/bl2.elfarm-ostl-linux-gnueabi-ld.bfd: SOURCES-stm32mp-openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11/stm32mp-openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11/sources/ostl-linux/tf-a-stm32mp-v2.10.13-stm32mp-r
Hi Team,Issue summary: when button is clicked then other button callback function getting trigger on TouchGFX simulation and same on hardware.Hardware details: STM32F429 Disc1 boardTouchGFX version: 4.24.0UI snip: When I click within area marked in square sky color box which is button area then kitchen callback function is triggered which is fine; but which also covers the 30% around area of Lobby. So when I click on Lobby button which is part of Kitchen button(around 30%) then kitchen callback function is triggered. So question is how to resolve this isseu.TouchGFX UI screenThanks MR
Hello,I'm facing some trouble with interfacing these two boards.Right now, I had only configured cube to load the datalogger example.It's running fine without the 6283A1 but when I plug it on the IKS4A1, the code crash.While debugging, I found that when the 6283A1 is not installed, the "configuration" variable is correctly filled with correct function pointer :But when the 6283A1 is inserted, not all the variable is filled and the code is trying to execute a function that's not registered in the variable : MotionFuncDrv[1][1]->GetAxesI think it's a bug in the IKS library, the color sensor may have been interpreted as the LSM6 ?Althought, the I2C bus is working fine. Without the color sensor :Searching for I2C devices on the bus...Device found: 0x32Device found: 0x3CDevice found: 0x70Device found: 0x88Device found: 0xBADevice found: 0xD4Device found: 0xD6Total found devices: 7 With the color sensor :Searching for I2C devices on the bus...Device found: 0x32Device
Hello everyone, I recently bought the NUCLEO-N657X0-Q and I am trying to debug it using the ST-LINK_gdbserver.Also this is my first development board and I don't know where to look. The data sheet and reference manual give me nothing in this regard and I am helpless. Here is the command line output:$ /opt/ST/STM32CubeCLT_1.20.0/STLink-gdb-server/bin/ST-LINK_gdbserver --swd \ -cp /opt/ST/STM32CubeCLT_1.20.0/STM32CubeProgrammer/bin -v -l 31 --frequency 8000 -k STMicroelectronics ST-LINK GDB server. Version 7.12.0 Copyright (c) 2025, STMicroelectronics. All rights reserved. Starting server with the following options: Persistent Mode : Disabled Logging Level : 31 Listen Port Number : 61234 Status Refresh Delay : 15s Verbose Mode : Enabled SWD Debug : Enabled InitWhile : Enabled COM frequency = 8000 kHz Target connection mode: Under reset Target not halted after reset. Force halt Failed to halt target Target not halted Error in initializing ST-LINK device. Rea
Hi, I am trying to merge the left and right wrist tilt configuration examples so that I have left wrist tilt on the FSM1 routing to INT1 and right tilt on the FSM2 routing to INT2 on LSM6DSV16X. I am sharing the merged config and the reference configurations being used(link). I have been trying to find an example for multi FSMs in MEMS studio but can't find any. Issue is thig config works fine for right wrist but not for left wrist. Any help in this regard would be appreciated. thanks
Hello, rm0456 in chapter 33.4.8. talks about "Software procedure to calibrate the ADC" and "Extended calibration mode" on some products. It is not clear, if "Software procedure to calibrate the ADC" is enough for products with "Extended calibration mode" or if extended procedure should be done always when available?Please clarify! Thanks
Hello Team,I am currently working on QuadSPI with MDMA, but I am unable to locate the driver code for this functionality.Could you please provide the required driver code?For reference, I am working on the STM32MP133F series.Regards,Sreedhar Kaduru
I have just installed STM32 cubeMX v6.16.1 on my Windows 10 machine have the following issue:In the Pinout&Configuration step we can hover mouse over items in the left tree view and eventually we can click on links to Related Documents. However those documents open in Acrobat Reader on my machine, even tough I have configured PDF-XChange Editor as default PDF viewer (Windows Settings, Apps, by ending, .PDF -> PDF XChange Editor).When I double-click PDF files in Windows Explorer they properly open in PDF Xchange, not Acrobat Reader. Having PDFs open in Acrobat is really annoying due to the constant popups and waste of screen space with useless tabs.
Title: VL53L8CX pulls SCK line low on ESP32 – PCB or power-up issue?Hello everyone,I’m currently developing a prototype using a VL53L8CX sensor together with an ESP32 controller. On our PCB, the sensor seems to permanently pull the SCK line low. This is already the second revision of the PCB, so with fairly high confidence I can rule out a basic PCB layout or routing issue. Here are my questions: Can you spot any possible mistakes in the schematic?Do you know under which conditions the VL53L8CX might actively pull SCK low? (To me it looks like an internal IC problem)Could this be related to the power-up or reset sequence of the sensor?Do you have any general debugging tips for this kind of issue?The SCK line is connected through a TXS0108 level shifter. With a different I²C device, the TXS0108 works perfectly fine, so I’m not sure if it’s involved here — but could the TXS0108 still cause problems in this setup?On the software side, I already tried:Running an I²C scanner
Are the design files of this board available from ST website? I'd need to know where can I get 3.3V and tie it to pin1 (Target VCC) off CN14. Then I'll be able to power the target MCU through this connector. Please check next post for further information:https://community.st.com/t5/stm32-mcus-boards-and-hardware/arm-debug-probe-with-power-to-target-capability/m-p/878207#M29644thanks in advance,Gaston
Hello,Is there a list of supported/recommended displays that are compatible with the DSI connector CN4 on STM32MP157D-DK1 please?Kind regards,Al
HiI am using Vl53L1X to measure dark surface upto 1000 cm far.. I am using a split cover glass(specifications attached). The benefits of using the split cover is that it prevents crosstalk. But even after attaching the cover, the distance measured by the sensor decreases when the object moves away from the sensor. Do I still need crosstalk calibration with cover glass or the cover is not ok.I have configured my sensor as follows:status = VL53L1X_SetDistanceMode(dev, 2); /* 1=short, 2=long */ status = VL53L1X_SetTimingBudgetInMs(dev, 100000); /* in ms possible values [20, 50, 100, 200, 500] */ status = VL53L1X_SetSignalThreshold(dev, 1024);//500); VL53L1X_SetROI(dev, 16, 16); // Full FoV (start here)
For the analysis and working of the gate driver L6491, we need the simulation model of the gate driver L6491 of LTspice or Pspice. Please provide the simulation model as soon as possible. It would be very helpful to us.Thank you!
I'm developing the STM32H735ZG using IAR EW.I wanted to design sectors 4-7 of the STM32H735ZG's flash memory as a readable/writable data storage area, so I created it by referring to the reference manual, but I can't read or write data properly. I modified the .icf file as attached, defining sectors 4-7 (0x08080000-0x080fffff) as the data storage area(named MEMORY block)./*###ICF### Section handled by ICF editor, don't touch! ****/ /*-Editor annotation file-*/ /* IcfEditorFile="$TOOLKIT_DIR$\config\ide\IcfEditor\cortex_v1_0.xml" */ /*-Specials-*/ define symbol __ICFEDIT_intvec_start__ = 0x08000000; /*-Memory Regions-*/ define symbol __ICFEDIT_region_ROM_start__ = 0x08000000; define symbol __ICFEDIT_region_ROM_end__ = 0x0807FFFF; define symbol __ICFEDIT_region_RAM_start__ = 0x24000000; define symbol __ICFEDIT_region_RAM_end__ = 0x2404FFFF; define symbol __ICFEDIT_region_ITCMRAM_start__ = 0x00000000; define symbol __ICFEDIT_region_ITCMRAM_end__ = 0x0000FFFF; define symbol __ICFEDIT
Hi there, I am using the Motor Control Workbench tool (6.4.1) and having issues after flashing using the Motor Pilot tool (6.4.1). My current setup is the Nucleo-F401RE + Nucleo-IHM16M1 + GBM2804H-100T motor.The project creation and code generation works fine, and the code builds and I am able to flash the code onto the STM32F401RE. I am designing for 3xPWM input and 3 Current Sensing resistors. All other settings are default. Then, using the Motor Pilot tool I am encountering the "Driver Protection" error right after connection. After investigating the generated code with a debugger, I found the issue to be with these two lines in the MX_NVIC_Init() function. I have not made any changes to the generated code. I am using the STM32CubeIDE. HAL_NVIC_SetPriority(TIM1_BRK_TIM9_IRQn, 4, 1)HAL_NVIC_EnableIRQ(TIM1_BRK_TIM9_IRQn); At the second line the code fails silently and gets stuck in a infinite loop (not sure exactly where). Even after this failure,the motor pilot ap
I am porting Linux to a board that uses the STM32MP255F.I used the BSP from the STM32MP257F-DK board.For now, I was able to get the LCD panel to display, but the weston-graphical-session did not start.When I added the following line to /etc/default/weston, the weston-graphical-session started:OPTARGS=--use-pixmanThe demo menu appears, and I can launch the demos.However, the GPU demos do not run.As I understand it, the OPTARGS=--use-pixman setting is meant for when there is no GPU.Since the GPU demos also do not run, it seems that the GPU is not operating.Under what conditions does the GPU fail to operate?For reference, the Device Tree gpu section is configured as follows:&gpu {contiguous-area = <&gpu_reserved>;status = "okay";};Another thing I am concerned about is that the initialization around usb3dr does not match the custom board, so I have disabled it.&m33_rproc {mboxes = <&ipcc1 0x100>, <&ipcc1 0x101>, <&ipcc1 2>;mbox-names = "vq0",
Good day everyone!We are working with a custom PCB based on the STM32H750 Discovery board. We are trying to replace the existing MT25QL512ABB8ESF dual-bank setup with a dual S25FL512S setup (both driven with the same chip select).I've got a board with the replacement S25FL512S ICs soldered on and am following the ST MOOC on QSPI flash loaders, but I'm running into issues in passing the recommended testing script; it fails at the memcmp function. As per the ST course, I created an empty project, set up the ioc file, and copy-pasted the user code section to the appropriate commented regions in the generated qspi c and h files from the repo, and I used the provided code from stm32-external-loader/QSPI_Drivers/MT25QL512/quadspi.h at contrib · STMicroelectronics/stm32-external-loader · GitHub .I've reduced the SECTORS_COUNT to 3 for quicker debugging, commented out the MPU_Config function for now, and am watching the contents of a smaller buffer after calling the CS
I am configuring the RTC and using the user button on NUCLEO-H563ZI, but it is not working as expected. When I check the configuration in .ioc, I see that yellow signal in the RTC section. I have checked it and do not understand what is happening.Could someone guide me about that warning and how it affects the operation of the RTC?Thank you in advance.
Hello guys,I have a stm32G474RET board. I am using tim1 in PWM input mode and i want to update on the fly the hrtimA period and compare values using DMA. This is the code i have written: // Addresses for HRTIM registers (Timer A) destPER = (uint16_t*)&HRTIM1->sTimerxRegs[HRTIM_TIMERINDEX_TIMER_A].PERxR; destCMP = (uint16_t*)&HRTIM1->sTimerxRegs[HRTIM_TIMERINDEX_TIMER_A].CMP1xR; // Start DMA transfers in circular mode HAL_TIM_IC_Start_DMA(&htim1, TIM_CHANNEL_1, destPER, 1); HAL_TIM_IC_Start_DMA(&htim1, TIM_CHANNEL_2, destCMP, 1); HAL_HRTIM_WaveformOutputStart(&hhrtim1, HRTIM_OUTPUT_TA1); HAL_HRTIM_WaveformCounterStart(&hhrtim1, HRTIM_TIMERID_TIMER_A); HAL_TIM_IC_Start(&htim1, TIM_CHANNEL_1); HAL_TIM_IC_Start(&htim1, TIM_CHANNEL_2); My problem is that the period of the hrtim is changing dynamically based on the input PWM signal, but the CMP1 doesn't. The only thing I could find is that when i tried to configure the channel 2 of tim
Hi ST Community,I'm facing an issue with FatFs on SDMMC where f_open() or even f_mount() returns FR_DISK_ERR, even though the SD card is initializing correctly at the HAL level.Here's a summary of the problem and what I’ve verified so far.HAL_SD_Init() completes successfullyCard information is read correctly:CIDCSDRCACapacity (LogBlockNbr, LogBlockSize)SDMMC interface appears operationalRaw HAL read/write tests (CID/CSD) work fineI would be grateful if ST experts or anyone familiar with SDMMC + FatFs integration please help me to resolve this issue :
I am developing a product using the NUCLEO-N657X0-Q dev board and have generated the configuration setup from CubeMX and developed the code in the CubeIDE. When I need to layout my own circuit board I will want to use the STM32N657A0 variant which has 169 pins and I was wondering if I am able to use CubeMX to change the existing configuration done for the Nucleo board to the STM32N657A0 169 pin device without destroying the code I have already developed? I have written the code using resources and pin outs available on the STM32N657A0 device but the actual pins are different on the two devices so need to know if I can make the transition using CubeMX or whether it will have to be done manually?
Setup Details:Board: STM32H750B-DK Discovery KitSTM32CubeIDE: Version 2.0.0 (Build 26820_20251114_1348 UTC)STM32Cube FW_H7: v1.12.1STM32CubeMX: v6.16.0TouchGFX Designer: v4.26.0 (MVP pattern)External Memory: 1GB QSPI Flash (MT25TL01G) + 8MB SDRAMProject Configuration:Created TouchGFX project in Designer, saved and generated codeOpened .ioc file in STM32CubeMX v6.16.0Configured:QSPI in memory-mapped mode with 30-bit addressing (1GB flash)SDRAM via FMCMPU configured with QSPI region execution enabled (0x90000000, 256MB)Vector table relocated to 0x90000000Linker script modified for external flash executionThe Problem:Debugger fails with protocol error when attempting to debug:Error in final launch sequence: Failed to execute MI command: monitor reset halt Protocol error with Rcmd Failed to execute MI command: monitor mww 0xE000ED08 0x90000000 Protocol error with Rcmd Failed to execute MI command: monitor reg pc 0x90000004 Protocol error with RcmdWhat Works::white_heavy_check_mark: Code pr
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.