Solved

I am verifying USB implementation using Nucleo-H7S3L8.When I executed CDC_Standalone in STM32CubeH7RS using the Debug button and ran the Appli code, the function “HAL_PWREx_EnableUSBVoltageDetector()” in ‘MX_USBPD_Init()’ did not return HAL_OK and an error occurred.Within this function, the “USB regulator ready flag (PWR_CSR2_USB33RDY)” is not set, causing a timeout and resulting in a HAL_ERROR.However, when I stop debugging, disconnect the USB cable, and reconnect it, the COM port appears in the Windows Device Manager.I have not made any changes to the contents of CDC_Standalone.The jumper on JP3 on the board has been changed from STLINK to UCPD.What should I do to properly debug USB on this board? 

I'm getting bad overshoot and undershoot spikes on an SD card interface. The spikes are so bad that 1/300 large (2MB) file writes fails, and it's damaging the SD cards so that a card that has been subjected to these spikes will continue to fail after it is moved to a good board. I can knock down the spikes by adding a 33-51 ohm series resistors to the data, clk and cmd lines. With 51 ohms I have done over 50,000 large file writes without errors as long as I use a virgin SD card that hasn't been subjected to the spikes.The boards have traces equalized for length, and one version uses 8 mil wide traces, the other uses 12 mils. Both have overshoots. One of my boards has long 4.5" traces to the card. But I'm also seeing spikes on a shorter version with only 3.2" traces to the card. There are lots of example SDIO schematics online but only 1/10 show series resistors. Application note AN5200 on SDMMC does not mention resistors.When I watch the data lines on a scope, an initial burst of

Hi, I am testing the SATEL VL53L7CX board, but the SDA on this board is stuck at zero. I have checked that there are no short cuts and that the pull up is there. Any ideas how to solve this?

Hi, I'm trying to compile an STM32U599VJTX build containing the X-CUBE-NFC6 software pack to talk to an ST25R3916B on our prototype board but cannot get it to compile.  I get the following errors related to "rfal" files:     I believe the platform settings are ok: Any help on the errors would be greatly appreciated.   STM32CubeIDE version 1.18.1 STM32CubeMX version 6.14.1 STM32Cube MCU Package for STM32U5 Series 1.7.0 X-CUBE-NFC6 version 3.1.0  

I found a problem while using the VL53L4CD. My usual practice is to initialize the VL53L4CD after the terminal is turned on. During subsequent use, I only use Start and Stop to control whether to start ranging.Now it is found that when I stop, the terminal enters a low-power state. When this state persists for a period of time, when operating VL53L4CD again and sending the start instruction, no interrupt signal can be received. Moreover, after I send VL53L4CD_ClearInterrupt, the interrupt signal remains at a low level all the time.When I start, I first call VL53L4CD_ClearInterrupt, and then call VL53L4CD_StartRanging. At this time, there is no occlusion before VL53L4CD, and the register value printed out is after the VL53L4CD_StartRanging interface is called.Tof reg [0], value [1]Tof reg [1], value [29]Tof reg [2], value [2]Tof reg [3], value [10]Tof reg [4], value [0]Tof reg [5], value [2f]Tof reg [6], value [bc]Tof reg [7], value [cc]Tof reg [8], value [9]Tof reg [9], value [80]Tof r

I'm seeing "noise" in some objects drawn on the screen.  See pic... the yellow circle ("shape") should be solid yellow, but instead includes red-orange horizontal lines.  If the circles are rearranged the yellow circle can look correct, but the blue circle may have the lines instead - only lighter blue, not red-orange.  Also, the button can include some horizontal lines when showing the "pressed" version.  These lines can flicker a bit too.. possibly turning on and off very quickly.   What is causing this and what can be done to fix it?  There was some improvement when setting the Alpha to 255 (from 127) but problem still exists.Screen is running at RGB565 - don't have enough RAM to run at RGB888.  STM32H7a3.  No RTOS.  Interface is LTDC with DMA2D enabled (but I did try disabling DMA2D).  Single layer... what else do you need to know??  Thanks!!

I am looking for a memory map for the stm32wl5moc.  I thought I found one before but cannot find it again.  It is not in the datasheet.  Any suggestions?  Thank you.

Hello, I am trying to write some non-blocking motor driver code for a STM32F401Re board. Currently, I am setting the timers to PWM mode and adjusting the ARR to change the PWM frequency using an IRQ handler. This approach is working for TIM3 output, but TIM2 seems to stop outputting after one iteration of the while loop. I've been through the registers and it looks like the CC1IF isn't always being set for TIM2 and I'm not sure why. By adjusting the ARR, shouldn't both timers roll-over after hitting their new max value? I've attached the main file and the A4988 driver file I'm writing. For the A4988 file, the methods in question are A4988_run() and A4988_IRQ_Handler().   Thanks!    

I have a STM32H73G-DK developement kit and I want to interface a custom 7" touchscreen/display with it using TouchGFX to create a basic menu structure.  I was able to get the display to show static images by following the guide in these youtube videos (from STMicro):https://youtu.be/yiHjOH7zJP0https://youtu.be/XnSg3UJfSFcFollowing these videos I was able to get a static image to display perfectly however I also need to get the touchscreen functionality to work as well.  The development kit comes with a smaller display that uses the FT5336 touchscreen controller but my display uses the GT911.  One of the steps in the first video is the comment out the touch screen "sampleTouch" code in STM32TouchController.cpp and type in "return true;" as the only code to execute there.  This effectively disables the touchscreen functionality, and if you don't do it the whole project will fail and you get gibberish on the screen.  Since my screen uses the GT911 I searched for d

Hi,I'm working on a USB Mass Storage Class (MSC) application using the STM32U5 series. I have a working firmware that correctly enumerates as a USB MSC device on STM32U5G9J-DK2 - Windows detects it and loads the built-in USBSTOR.SYS driver as expected. The configurations I've used are similar to the DFU example provided for the same board on STMCube IDE.However, when I flash the code with similar configurations to the STM32U5G9J-DK1, it fails to enumerate properly. In Windows Device Manager, I get: Windows has stopped this device because it has reported problems. (Code 43) The USB device returned an invalid USB device descriptor.How can I fix this?

Hello ST team and community,Why doesn’t ST provide the necessary internal pin length information for DDR layout in an official and accessible way — such as in the datasheet, an application note, or any other verified documentation?Currently, the only resource available is an Excel table listing signal names, not pin names, and as far as I can tell, it’s based on an Altium reference design. While it's theoretically possible to map signal names to actual pins, there is no reliable way to verify this mapping — especially since the Excel file isn't an official part of the datasheet or app notes.This makes accurate DDR layout challenging, especially for length matching, where precise internal pin delay data is critical.I kindly ask ST to provide official documentation that includes internal pin lengths clearly referenced by actual pin names, not just signal names.This would make DDR layout far more reliable and would prevent design issues caused by guesswork or reverse-engineering unofficia

Hello,we previously used the STM32U5G9J-DK2 discovery kit with FreeRTOS and TouchGFX (with hardware-accelerated Vector Font Rendering, etc) successfully.Now we are trying to bring up a custom STM32U5G7VJ based board. We first created the ioc File with CubeMX, configured all the pins and later on enabled FreeRTOS and TouchGFX middlewares. As far as possible, the settings from the discovery board were replicated (except we now use RGB888 instead of RGB565 and a few different LTDC and OCTOSPI settings)After opening the project template in the TouchGFX editor, a hello world screen was added.However, when building in STM32CubeIDE, the following error occurs in TouchGFX/target/generated/HardwareMJPEGDecoder.cpp: fatal error: jpeg_utils.h: No such file or directoryWhen I compared the HardwareMJPEGDecoder.cpp file between the discovery kit project and our own, I noticed it's different: The one from the discovery kit is around 5 KB larger and it has no #include <jpeg_util

Hello everyone,I'm facing a HardFault issue when jumping from a bootloader to an application on the STM32L476RG.The fault occurs right at the beginning of the application, specifically at the instruction bl __libc_init_array inside the Reset_Handler (from startup_stm32l476xx.s).Memory layout:Bootloader: starts at 0x08000000, size: 12 kBApplication: starts at 0x08004000, max size: 150 kB (currently using ~95%)RAM usage: around 30%Bootloader jump sequence:typedef void (*p_function)(void);static void app_start(boot_t *self) {HAL_DeInit();self->boot.address = *(volatile uint32_t *)(self->address.app + 4);self->boot.jump_to_app = (p_function) self->boot.address;__set_MSP(*(volatile uint32_t *) self->address.app);SCB->VTOR = self->address.app;self->boot.jump_to_app();}Here, self->address.app = 0x08004000.The bootloader reads the application’s initial stack pointer and reset vector from 0x08004000 and 0x08004004, respectively, and then jumps to the reset handler of

Hi, I have two PCs (Windows 11) with STM32CubeIDE 1.18.1.Although both copies of STM32CubeIDE should be the same, the Project context menu looks different (see attached screenshot). Actually one copy is missing menu items like "Convert to C".Reinstalling didn't help.Any idea how to get the full version of the context menu? 

Hi all,currently iam using the stm32h757 controller.i want to use the FMC on both cores, in SRAM mode with this config: hsram1.Instance = FMC_NORSRAM_DEVICE; hsram1.Extended = FMC_NORSRAM_EXTENDED_DEVICE; /* hsram1.Init */ hsram1.Init.NSBank = FMC_NORSRAM_BANK1; hsram1.Init.DataAddressMux = FMC_DATA_ADDRESS_MUX_DISABLE; hsram1.Init.MemoryType = FMC_MEMORY_TYPE_SRAM; hsram1.Init.MemoryDataWidth = FMC_NORSRAM_MEM_BUS_WIDTH_16; hsram1.Init.BurstAccessMode = FMC_BURST_ACCESS_MODE_DISABLE; hsram1.Init.WaitSignalPolarity = FMC_WAIT_SIGNAL_POLARITY_LOW; hsram1.Init.WaitSignalActive = FMC_WAIT_TIMING_BEFORE_WS; hsram1.Init.WriteOperation = FMC_WRITE_OPERATION_ENABLE; hsram1.Init.WaitSignal = FMC_WAIT_SIGNAL_DISABLE; hsram1.Init.ExtendedMode = FMC_EXTENDED_MODE_DISABLE; hsram1.Init.AsynchronousWait = FMC_ASYNCHRONOUS_WAIT_DISABLE; hsram1.Init.WriteBurst = FMC_WRITE_BURST_DISABLE; hsram1.Init.ContinuousClock = FMC_CONTINUOUS_CLOCK_SYNC_ONLY; hsram1.Init.WriteFifo = FMC_WRITE_FIFO

Board: stm32h753zi nucleoFirmware & CubeMX: latest versionI have configured the adc to continous conversion and DMA output. The initialization fails in main.c in HAL_ADC_INIT. I stepped through the HAL lib and saw that LL_ADC_IsInternalRegulatorEnabled returns the HAL_ERROR.The docstring of this function says /* Verification that ADC voltage regulator is correctly enabled, whether */ /* or not ADC is coming from state reset (if any potential problem of */ /* clocking, voltage regulator would not be enabled). */ if (LL_ADC_IsInternalRegulatorEnabled(hadc->Instance) == 0UL)I do not find any documents online which describe how the clock frequency of the adc should be set up. Could you please give me a hint.

I am looking into making an Avatar widget (image inside a non rectangular container).I looked at some of the the lcd.blitcopy, canvas, circles and painters and getting a bit confused where you could apply a mask to an image to only render a section of it.I am sure this would be a great addition to the shared widget.Right now, I am looking into circles and their painters to figure out the paint() and drawn() operations.

We are using the LIS2DW12 accelerometer in our custom product. We understand that this sensor can detect movement or positioning along the X, Y, and Z axis. However, in our application, we need to detect when the device changes its orientation in terms of degrees—for example, when it flips or tilts significantly from one position to another.Can the LIS2DW12 generate an interrupt based on such orientation changes (e.g., using 6D orientation detection)? We are looking for a way to trigger events when the device is rotated beyond a certain angle.Thank you

I have a brand new Nucleo G474RE board. I see that the default HSE is X3 at 24MHz. The solder bridges and capacitors are OK as per the board documentation, and checked to be physically on the board.But I cannot get HSE to oscilate. The (autogenerated) clock config code times out hereHAL_StatusTypeDef HAL_RCC_OscConfig(RCC_OscInitTypeDef *RCC_OscInitStruct) [...] /* Set the new HSE configuration ---------------------------------------*/ __HAL_RCC_HSE_CONFIG(RCC_OscInitStruct->HSEState); /* Check the HSE State */ if (RCC_OscInitStruct->HSEState != RCC_HSE_OFF) { /* Get Start Tick*/ tickstart = HAL_GetTick(); /* Wait till HSE is ready */ while (READ_BIT(RCC->CR, RCC_CR_HSERDY) == 0U) { if ((HAL_GetTick() - tickstart) > HSE_TIMEOUT_VALUE) { return HAL_TIMEOUT; <--- I end up HERE } } }I also probed pin 5 PF0 and pin 6 PF1 with an osciloscope with a 10X probe and they have no signal (both at 0VDC).My MX configuration regarding the clocks is as follows: 

Hi, I was trying to test the feature of "Level 2 flash lock" on my custom board. I'm having an unexpected behaviour.My total application consists of a bootloader responsable to load an application via CAN BUS through a custom communication protocol.Now, If I load my application program via CAN (via bootloader), the MCU can not set itself to level2 but remains set to level 1. If I transfer the same application with JTAG, the MCU can set itself to level 2 protection and any attempt to connect to it is correctly disabled. (in level 1 I can still connect by erasing the whole chip content). To give further informations, here is the code responsable to set level 2 protection implemented:FM_ClearFlags(); FM_Unlock(); flashSts = FM_CheckProtectionStatus(); if(flashSts == FM_FLASH_NOT_PROTECTED) // check current protection status { FM_SetOBConfig(); flashSts = FM_CheckProtectionStatus(); } FM_Lock(); void FM_ClearFlags(void) { FLASH->SR |= 0xE0; // clear the errors RDERR P

Hello,I read the UID from STM32L031K6P6 and each device returns the same result: 0x14473332, 0x38363437, 0x0.I read the value from the address given in RM0377 (0x1FF8 0050).Is the address given in RM0377 correct?I am attaching screen shots from CubeProgrammer.

Hi,I'm trying to use the NPU of the STM32N6 to run a onnx model in attachment.The issue I try to fix is that stedgeai is not using the NPU for all operations. Some of them are run in SW instead of HW, like Conv and Gemm and I don't understand what is preventing the acceleration.Here is the stedgeai output:/home/doc/STM32Cube/Repository/Packs/STMicroelectronics/X-CUBE-AI/10.1.0/Utilities/linux/stedgeai generate --target stm32n6 --name network - m denoiser_LSTM_Valetini_nobatchsize_preprocess_simplified_q.onnx --st-neural-art "n6-noextmem@/home/doc/STM32Cube/Repository/Packs/STMicroelectronics/X-CUBE-AI/10.0.0/scripts/N6_scripts/user_neuralar t.json" --verbosity 1 ST Edge AI Core v2.1.0-20194 329b0e98d WARNING: Unsupported keys in the current profile n6-noextmem are ignored: memory_desc > memory_desc is not a valid key anymore, use machine_desc instead >>>> EXECUTING NEURAL ART COMPILER /home/doc/STM32Cube/Repository/Packs/STMicroelectronics/X-CUBE-AI/10.1.0/Utilitie

The X-CUBE-NFC3 zip I downloaded (v2.1.0) does not contain the CR95HF driver (Drivers/CR95HF folder missing). The package claims to support CR95HF for STM32, but only ST25R95 files are present.Impact:Cannot detect ST25TA tags using X-NUCLEO-NFC03A1 (CR95HF mode).cannot read or write data on tagRequest:Where can I find the official CR95HF driver for X-CUBE-NFC3?Is this a known packaging issue?Alternate solution to read ST25TA with STM32F401RE?Steps Tried:Re-downloaded X-CUBE-NFC3 multiple times.Hardware:NUCLEO-F401REX-NUCLEO-NFC03A1 (mounted directly on the board)

Hi, I'm putting down a LIS2DH12 accelerometer on a new PCB. The datasheet calls for an aluminum capacitor on VDD, but the eval board (STEVAL-MKI151V1) shows a small capacitor that looks like a ceramic. I don't know for sure because I can't find the BOM for the eval board. I really don't have clearance for an electrolytic capacitor. How critical is it?

Hi everyone!Does anyone have the link to the schematic of stm32h750b-dk. I'm new to this world but I found the schematic for other boards. By schematic I mean the correspondence between the name of the pins as marked on the board and the "internal" name that is used to access that pin in the CubeMX. For example, for stm32f7 I can see that D0 correspondes to PC7, D7 to PI3, etc.Thanks in advance for your help.Best,TJota