Solved

Hello everyone,I have a project with an STM32U575VGT6. This was created with STM32CubeMX version 6.8.1. Now the project should be made compatible with the latest IDE version (V1.17.0) as part of a larger conversion action and for this purpose a migrate of the ioc was carried out (STM32CubeMX version 6.13.0).In the original project, VREFBUF was set to ‘Internal voltage reference’ mode with ‘SCALE0’.After the upgrade, this selection is no longer available and VREFBUF is set to ‘Disabled’ by default.I have also noticed that since the upgrade there is the option ‘isolation Vdda’ under ‘PWR’, which cannot be deactivated.Ultimately, this means that 0V is applied to the Vref pin and the ADC and DAC do not function correctly.What has been changed here and what do I have to set so that my application works again?Many thanks for your helpRobertold Version:new Version: 

When attempting to configure USB_OTG_HS and corresponding USB_DEVICE_M4/M7 middleware on STM32H747XI (on either M7 or M4 cores), the "STM32_USB_Device_Library" directory gets included on both cores, causing the core that isn't using the USB peripheral to fail build. Here are the errors that occur:/.../H7/Middlewares/ST/STM32_USB_Device_Library/Core/Src/usbd_core.c:20:10: fatal error: usbd_core.h: No such file or directory20 | #include "usbd_core.h"| ^~~~~~~~~~~~~compilation terminated./.../H7/Middlewares/ST/STM32_USB_Device_Library/Core/Src/usbd_ctlreq.c:20:10: fatal error: usbd_ctlreq.h: No such file or directory20 | #include "usbd_ctlreq.h"| ^~~~~~~~~~~~~~~compilation terminated./.../H7/Middlewares/ST/STM32_USB_Device_Library/Core/Src/usbd_ioreq.c:20:10: fatal error: usbd_ioreq.h: No such file or directory20 | #include "usbd_ioreq.h"| ^~~~~~~~~~~~~~compilation terminated./.../H7/Middlewares/ST/STM32_USB_Device_Library/Class/CDC/Src/usbd_cdc.c:59:10: fatal error: usbd_cdc.h: No such f

I have ordered STM32N6570-DK board in order to start working on STM32N6 MCU.But I was confused how to set it up. And STM does not tell you. Here, what I have figured out:1. Orientation of PFC cable for camera:Place the contacts of the FPC cable towards the PCB (you should see still the blue plastic cover and the text on cable in normal orientation of setup).The camera module and its connector is very delicate: make sure not to lose the black bridge used in order to tighten the cable: I lost my one immediately somewhere under my desk.2. You need an USB-C power supply!Nobody tells you, but what I found:The board - WITHOUT the camera activated - draws already 470..480mA of current (e.g., via USB-A from USB hub to USB-C on DK board).If you activate now the "AI" feature on the demo, where the camera is activated and "should" show you the live video on LCD screen: all remains dark, both LEDs are red and even NRST button does not work (does not bring back the board to live).You need: a real U

(I deleted the content by accident) I'm working on a project that uses Smart Presence Detection to control a LED strip using the X-NUCLEO-53L8A1 board. I started a blank project in STM32CubeIDE and included the X-CUBE-TOF1 bundle. I have added several other features to control the LEDs (SPI, DMA, timers, etc). I am able to get ranging data from the ToF sensor.I would like to add the Smart Presence Detection from STSW-IMG048 but I'm having a great deal of difficulty integrating the SPD code with the existing code that talks to the VL53L8. It seems that the SPD code makes extensive use of function calls to control the sensor using the VL53LMZ_ULD_API but these calls do not work in the context of my existing project - perhaps it some incompatibility in the GPIO or I2C setup but I cannot be sure. I would prefer to be able to use calls to the sensor-control functions in the X-CUBE-TOF1 package to satisfy the requirements of the SPD but it does not look possible - the TOF1 functions do

I have basic application of tcp_server. void tcp_echoserver_init( uint16_t port) { tcp_echoserver_pcb = tcp_new(); if ( tcp_echoserver_pcb != NULL) { err_t err;   /* bind echo_pcb to port (ECHO protocol) */ err = tcp_bind( tcp_echoserver_pcb, IP_ADDR_ANY, port);   if (err == ERR_OK) { /* start tcp listening for echo_pcb */ tcp_echoserver_pcb = tcp_listen( tcp_echoserver_pcb );   /* initialize LwIP tcp_accept callback function */ tcp_accept( tcp_echoserver_pcb , tcp_echoserver_accept); } else { /* deallocate the pcb */ memp_free(MEMP_TCP_PCB, tcp_echoserver_pcb ); } } }   static err_t tcp_echoserver_accept(void *arg, struct tcp_pcb *newpcb, err_t err) { err_t ret_err; struct echoserver *es;   LWIP_UNUSED_ARG(arg); LWIP_UNUSED_ARG(err);   /* set priority for the newly accepted tcp connection newpcb */ tcp_setprio(newpcb, TCP_PRIO_MIN);   /* allocate structure es to maintain tcp connection informations */ es = (struct ec

Hi everyone,I'm working with the B-G431B-ESC1 board and need help setting up overcurrent protection. I want to ensure safe operation and prevent damage to the hardware.Could anyone guide me on the best way to configure the current sensing and protection in MC Workbench?Any insights, step-by-step instructions, or shared experiences would be greatly appreciated!Thanks in advance! :rocket: 

Hello, I have an existing STM32_WPAN configuration with 3 BLE services and I want to completely remove Service 2. Is there any way to do that?  I've already reduced the number of services to 2, but it ends up removing Service 3 which I want to keep. Is it possible to swap Service 2 and 3 and then reduce to 2 services. thank you in advance  

If I have 2 external devices, one mapped on GPIOC0 and another on GPIOG0 of the micro, so they generate the same EXTI0 interrupt, how is it possible to distinguish which of them is calling the interrupt? I mean, is it possible to read effectively the GPIO state (C0 or G0)? or doing this can cause any trouble?

 Hi @Igor Cesko I am experiencing connection issues with STM Cube programmer when connecting ST LINK debugger.The controller part number i am using is STM32G491MCT.Getting "Error Target device held under rest", I can connect only if I change the ST link configuration to Hotplug mode.Even after connecting sometimes it shows "there is no active configuration".I am unable to program the controller.Kindly help me to get resolve with the issue as early as possible.       

1. Developing tools directories as this:D:\ProgramData\STMicroelectronics\STM32Cube\STM32CubeMXD:\ProgramData\STMicroelectronics\STM32Cube\STM32CubeProgrammerD:\ProgramData\STMicroelectronics\TouchGFX\4.24.2\2. ST link drivers are installed well.(because code can be compiled and downloaded via usb ST-link)3. Hardware is STM32U5A9J-DK.4. TouchGFX Designer demo is TouchGFX Demo6. Run simulator is OK. My question is:   I want to run this demo on STM32U5A9J-DK, but the run button can not work and display 'Cannot Run Target'.   which procedure is wrong? Or is there any guidance to solve this problem? 

Dear Gfx TeamWhen launching project.touchgfx, often the splash screen dissapears but IDE apears only after ~10 seconds. During tose 10 seconds, it is not clear what is goung on. Neither splash screen nor the IDE is visible.Please make splash screen go away only after IDE is available i.e. splash screen is shown over IDE for second or two.Thanks

Do we need to use stm32 ODE hardware every time fro programming the ISPU?. If no, how can i flash the program in to ISPU?. Since ISPU have 40 kB RAM do we need to write program every time in to RAM while booting ?https://www.st.com/content/st_com/en/campaigns/ispu-ai-in-sensors.html

Requirments-LCM->1024x600 TFT With CTP and Or 1028x 800 LVDS TFT With CTPColor Depth-> 24bppFPS-> ~30MCU-> _________?RAM-> __________?QSPI-> __________?I have Selected the following Hardware But need expert opinion on this subjectMy Selection-MCU->STM32H750 BGASDRAM-> 16 BIT (IS42S32400F-6BL)QSPI->MT25QL512The above parts are used in STM32H750B-DK

Dear Experts,I need your help to configure the clock using CMSIS. I am using Nucleo 64 board of STM32F411RE. Steps I have followed:-1. Enable PWR CLK.2. SET VOS value to 3.3. Enable Prefetch, Instruction cache, Data cache.4. Set Flash Latency 3WS.5. SET HSE Bypass.6. Enable HSE CLK.7. Wait for HSE RDY Flag.8. Set PLL Prescaler values.9. Enable PLL.10. Wait for PLL RDY Flag.11. Select System CLK as PLL.12. Check status of System CLK Source. (SWS bits)13. Set APB1 Prescaler to div 2.14. Disable HSI CLK. /** ****************************************************************************** * @file : main.c * @author : Auto-generated by STM32CubeIDE * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2024 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file * in the root directo

I am using an stm32c011 MCU and want to put my device into standby mode and then periodically wake it up (every 30s or so).I have seen guides which use the RTC to do that, but cube mx doesn't show me a WakeUp option on my RTCAm I missing something or how am I supposed to continue from here?

Issue DescriptionI am experiencing a debugging issue with a project generated using TouchGFX Designer 4.24.2 for STM32H7B3I-DK, running on STM32CubeIDE 1.17.0. When I attempt to start debugging, I get the following error:   Failed to execute MI command: load C:\TouchGFXProjects\Test01\STM32CubeIDE\Debug\STM32CubeIDE.elf Error message from debugger back end: Load failed   Tests PerformedProject generated with TouchGFX 4.24: If I generate the project from TouchGFX and try to debug, I get the error mentioned above.The firmware loads correctly when flashed (.hex) manually via STM32CubeProgrammer, but the graphics appear corrupted.Empty STM32CubeIDE Project (No TouchGFX): If I create a new empty project for the STM32H7B3I-DK in STM32CubeIDE 1.17.0, the debugger works without any issues.Flashing and debugging function properly.ObservationsThe issue seems specific to projects generated using TouchGFX 4.24.2There might be a problem with memory configuration, linke

Hello, does anyone know how these two components (STM32H753XIH6 and STM32L4S7AII6) verify that the data in both internal and external memories(Ram, Rom, Nor and Nand) are not corrupted?Thanks for your help?

I am trying to use the built-in bootloader to flash a new firmware onto my MCU (STM32H723). Unfortunately, I cannot get any reaction from the MCU when trying to connect to it, and I am struggling to diagnose which step is going wrong.Short version of my steps:I pull BOOT0 high & NRST low (before this point, the MCU is running the normal firmware code)I release NRST, the MCU starts up again (attaching the ST-Link debugger, I confirmed that the code being execute is around 0x1FF00000, i.e. the MCU is somewhere in the bootloader code)I try to connect to the MCU using the STM32CubeProgrammer, set to UART (MCU pins PA9/PA10), baud 9600 (tried everything up to 115200), even parity, 8 data bits, 1 stop bit, flow control off. Whatever settings I try, I always get: Port configuration: parity = even, baudrate = 9600, data-bit = 8, stop-bit = 1.0, flow-control = off Timeout error occured while waiting for acknowledgement. Error: Activating device: KO. Please, verify the boot mode configu

 int loopTime = 0, maxLoopTime = 0;/* Private function prototypes -----------------------------------------------*/void SystemClock_Config(void); int main(void){   /* MCU Configuration--------------------------------------------------------*/   /* Reset of all peripherals, Initializes the Flash interface and the Systick. */  HAL_Init();   /* Configure the system clock */  SystemClock_Config();   /* Initialize all configured peripherals */  MX_GPIO_Init();  MX_DMA_Init();  MX_ADC1_Init();  MX_ADC2_Init();   MX_COMP1_Init();  MX_COMP2_Init();  MX_COMP4_Init();  MX_DAC3_Init();  MX_OPAMP1_Init();  MX_OPAMP2_Init();  MX_OPAMP3_Init();  MX_TIM1_Init();  MX_IWDG_Init();  MX_I2C3_Init();  /* USER CODE BEGIN 2 */  SystemManager_Start();  /* USER CODE END 2 */   /* Infinite loop */  /* USER CODE BEGIN WHILE */  while (1) 

openstLinux version: 1. en.SOURCES-stm32mp1-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.062. en.SDK-x86_64-stm32mp1-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06command: $ cd tf-a-stm32mp-v2.10.5-stm32mp-r1 $ export FIP_DEPLOYDIR_ROOT=$PWD/../../FIP_artifacts $ make -f $PWD/../Makefile.sdk TF_A_DEVICETREE=stm32mp157d-openedv DEPLOYDIR=$FIP_DEPLOYDIR_ROOT/arm-trusted-firmware stm32 -j2 $ cd optee-os-stm32mp-4.0.0-stm32mp-r1 $ export FIP_DEPLOYDIR_ROOT=$PWD/../../FIP_artifacts $ make -f $PWD/../Makefile.sdk CFG_EMBED_DTB_SOURCE_FILE=stm32mp157d-openedv DEPLOYDIR=$FIP_DEPLOYDIR_ROOT/optee optee -j2 $ cd u-boot-stm32mp-v2023.10-stm32mp-r1 $ make -f $PWD/../Makefile.sdk ARCH=arm CROSS_COMPILE=arm-ostl-linux-gnueabi- DEVICE_TREE=stm32mp157d-openedv all -j2  tvs: #Opt Id Name Type IP Offset Binary - 0x01 fsbl-boot Binary none 0x00000000 arm-trusted-firmware/tf-a-stm32mp157d-openedv-optee-programmer-usb.stm32 - 0x03 fip-boot FIP none 0x00000000 fip/fip-

I am working on a low power mode in a freeRTOS ble application. On a user request the device is to go into low power mode Stop2. In order to achieve the lowest power consumption ~2µA (stm32wb55) the ble activity has to be deactivated and the cpu1 & cpu2 has to go into lp-mode. In order to deactivate the ble antenna hci_reset is used. The low power mode implemented with hci_reset() works when tested on a Nucleo-STM32wb55 board based on the BLE_HeartRateFreeRTOS example. When I set it up on another project the hci_reset deletes all threads BLE threads (expected), but also deletes the working thread which means it doesn't excecute the the rest of the LP sequence. Here is the setup so far:  void LowPowerThread(void *argument) { HAL_EnableDBGStopMode(); for (;;) { osDelay(5000); HAL_GPIO_WritePin(GPIOD, GPIO_PIN_12, GPIO_PIN_RESET); /* Turn off DEBUG LED */ hci_reset(); /* resets the Link Layer on an LE Controller (ble_hci_le.h) */ LL_C2_PWR_S

I Enabled LWIP DEBUG options in CUBEMXin lwipopt.h  /* USER CODE BEGIN 1 */ #define LWIP_DEBUG 1 /* USER CODE END 1 */ in main.c  int __io_putchar(int ch) { ITM_SendChar(ch); return ch; }  But I am not getting anything in SWVITM Data Console

I am a novice, would like to ask if anyone will write a set of library files only for a single model of microcontroller because of the bloated official library files, is this common? For example, I was looking at the stm32h7 series recently, and the idea came to me because the layers of hal library nesting were very annoying.

Moved from MPUs forum.Hi, I looking to use the Nucleo WB55RG board to prototype some BLE firmware.I was looking through the examples in Cube MX but that particular board wasn't listed but there were a few similar choices, (see below). I was thinking the NUCLEO-WBAA55CG or the P-NUCLEO-WB55-NUCLEO?

I've already become familiar with the NUCLEO-C071 by creating some additional hardware (display, encoder, etc.). Now, I want to design a board using the smaller 32-pin version. However, in this smaller version, I find some differences that I don't know how to address (I have read the datasheet thoroughly multiple times but cannot find any answers):1) In the 64-pin version, pin 6 is the VBAT to connect a battery or a supercapacitor to maintain the RTC operation in case of power loss. Where has it gone in the 32-pin version?2) In the 64-pin version, both the quartz for the CPU and for the RTC can be mounted. Can you confirm that in the 32-pin version, the CPU only works without quartz? Even for managing USB?Thank you to anyone who can help me.Luca.