Solved

Running ST Cube IDE 1.19 on Windows 11, co-pilot autocompletions seem to be causing an issue. I see the suggestion, then a dialog pops up saying the following:An internal error occurred during: "Generating completion...".Invalid thread accessI look at the error log as I see the following:Failed to parse wmic outputException Stack Trace:org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Premature end of file.at java.xml/com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:262)at java.xml/com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:342)at com.st.stm32cube.ide.mpu.remote.serial.internal.SerialPortProviderWindows.run(SerialPortProviderWindows.java:127)at java.base/java.util.TimerThread.mainLoop(Timer.java:566)at java.base/java.util.TimerThread.run(Timer.java:516)

I have STM32N6570-DK board and need to use very small sized camera ~1x1mm 30 fps with USB UVC interface for object detection applications. As the camera does not have dcmi/csi-2 interface, I am exploring how to use USB HS Host driver and UVC class driver. Questions: 1. Is it possible to get real-time inference on UVC video stream(20-30fps) as in an example ST      provides? I have tried the example and inferencing speed is very fast. 2. Are there any example codes I can refer to for USB host and vuc class driver?  3. or should I try find the video bridging hardware converter(UVC to DCMI parallel/MIPI CSI-2)? 4. Even if I can find CSI-2 converter, firmware development will still be very challenging for CSI interface. Is it worth trying out? DCMI parallel will be much easier to implement in coding. However, small camera does not come with parallel interface. Are my assumptions correct? Any help/guidance/clarification would be greatly appreciated! Thank you

Does ST offer an implementation of hardware acceleration of mbedtls-2021?I found this:STM32CubeL5\Projects\STM32L562E-DK\Applications\TFM\TFM_Appli\Secure\Src\ecdsa_alt.cSTM32CubeL5\Projects\STM32L562E-DK\Applications\TFM\TFM_Appli\Secure\Src\ecdsa_curves_alt.cfrom https://github.com/STMicroelectronics/STM32CubeL5.gitThis is excactly what I want (a bridge between mbedtls and the PKA_HAL driver), but it's for a 2019 version of mbedtls, and the mbedtls folks since broke the interface, so it doesn't compile. (and it doesn't look like an quick/easy fix)Is there a newer version somewhere?/Troels

Hi everyone,I'm working with a custom board based on the STM32WB55, and I'm facing a very strange issue with the Bluetooth Low Energy advertising. BLE advertising works perfectly when the board is running under debugger (SWD debug mode), wireless stack is correctly updated and option Bytes remain as programmed even after power cycling. CPU2 starts, and aci_gap_set_discoverables() returns BLE_STATUS_SUCCESS.The problem is, when I remove the debugger and simply power-cycle the board (i.e. unplug power supply usb cable and replug it), BLE advertising does NOT start.Do you have any idea of how to fix this problem?Thank you

Hi I have used STMCubeIDE 1.11.0 (Cube 1.6.1) to generate the code for USB CDC interface for STM32G0B1.The code is as CubeMX would generate. I have not modified the code at all.When I plug the device into a PC I get "USB device not recognized" I have increased the heap and stack to be 0x1000. without any luck. What can I try to try to figure out what the issue is.Thanks,

I have two boards, both with the G473.I am using the ROM bootloader on SPI1. On one board, the bootloader works.  On the other, it only responds with 0xA5 during the initialization sequence.The MCU can program and run if I load it through the SWD port.I have checked the SPI signals, both digital and analog, they look great.  The MCU pins are firmly soldered to the board.  The other board works.  My code works.  If you can actually get the bootloader to synchronize, it works.I have gone through every forum post I can find, and it is sounding like there is a possible consensus that the ST bootloader is bugged and will sometimes initialize the wrong interface.  Is that... really true?  It selects the wrong interface and all of these people are having problems with it?  Can any one from ST talk about this?  This sounds like a really serious problem if true!  What else could it be?AN2606 says the G473 will init the pins on the USART and

Hello.I've tried to implement the TCP client using freeRTOS, socekt API and LwIP middleware on STM32H723ZG.However, I cannot figure out why the connect() function in socket api doesn't work and stuck.Is there a example for nucleo-H723ZG with LwIP and TCP client?Sincerely. 

Dear Community,I am using a Nucleo-H723ZG for my uni project and im running into issues with the PA11 & PA12 Pins.I want to use them for FDCAN1 and I have verified that my code works. No matter in what way i try to use these two pins the dont output.if I switch to FDCAN2 with the same code and simply switch all instances of &hfdcan1 to &hfdcan2 i can read the signals with an scope and a can2usb adapter and get the right values. I also tried to select just the mcu instead of the board because i read that sometimes USB_OTG messes with things but no luck.Lastly i tried with another brand new Nucleo-H723ZG but also here no output on PA11 & PA12 whatsoever.Not even in GPIO-Mode. Do I have to turn something specific of?I attached the full project. Kind regards

I know that USB3DR cannot be used with PCI Express if USB3DR is configured as SuperSpeed.But can USB3DR be used with PCI Express if USB3DR is configured as 2.0 e.g Hi-Speed?

Hi,I'm using an STM32H723 and store my configuration data in flash. Here The procedure is: erase the flash once, then write to the erased flash. On read check the flash for a magic word to find where data have been written. Next write happens the same way, it uses the magic word to find an unused part of the flash to write to (in order to save erase cycles). So data are written several times until a new erase is necessary.Now sometimes I end up in the HardFault handler because of an illegal read:void *Flash_Storage_Read(const size_t length) { uint32_t base_addr = FLASH_STORAGE_START_ADDR; uint32_t final_addr = base_addr + length; uint32_t *finalData=(uint32_t*)final_addr; const uint8_t *flashID=(uint8_t*)final_addr; while ((final_addr<FLASH_STORAGE_END_ADDR) && (*finalData!=0xFFFFFFFF)) -------> this read access causes the HardFault_Handler() to be called { base_addr+=length; final_addr+=length; finalData=(uint32_t*)final_addr; } return (void*)base_addr; }&n

Hi,I am developing a telemetry project using the P-L496G-CELL02 Discovery Kit. My goal is to use the X-CUBE-CELLULAR expansion package to handle the cellular modem connectivity and MQTT implementation.However, I am facing difficulties installing this package properly in STM32CubeIDE.The Issue: I went to Help > Manage Embedded Software Packages > STMicroelectronics tab and clicked "Refresh", but the X-CUBE-CELLULAR package does not appear in the list to be installed.What I have done so far:I searched the Package Manager extensively, but it is missing.I have downloaded the .zip file of the package (v6.0.0) directly from the ST website.I tried to use the "Install from Local" option in the Package Manager with this zip file, but it failed (likely because it is not formatted as a pack).Since the automatic installation is not available, what is the correct step-by-step procedure to manually install or integrate the X-CUBE-CELLULAR package into my STM32CubeIDE workspace?I want to ensure

While testing the X-CUBE-EEPROM library in STM32CubeIDE (v1.18.1), I observed the FLASH->CR register in the SFRs window. I noticed that the display for BKER (bank erase select bit) is missing in the FLASH_CR register. Please try to correct this in the next STM32CubeIDE release.

IntroSTM32CubeMX supports CMake since 6.11.0 as a tool chain option. Sometimes you want to customize your project, but you don't want generated files to be overwritten. I will reply to this post how to do these things and this will be the accepted answer. It's like a knowledge base article. Please expand it with more ideas and I will add it to that answer.Generated filesSTM32CubeMX generates:./CMakeLists.txt:This file can be customizedcmake/stm32cubemx/CMakeLists.txt: file with all cube generated source files and defines. It's an interface library. This file can not be modified as it will be overwritten when regenerating with STM32CubeMXcmake/touchgfx/CMakeLists.txt: if you have touchgfx in your project this will be added too. It's an interface library. This file can not be modified as it will be overwritten when regenerating with TouchGFX Designerpotentially more subfolders with CMakeLists.txt filesgcc-arm-none-eabi.cmake: toolchain file for gcc. Used if you use gc

STM32CubeProgrammer 2.18.0 and 2.19.0STLINK-V3SET FW V3J16M7B5S1.STM32H563RIT6 rev X. Bootloader version 0xE4.1. Connect under reset.2. Configure MCU with EDATA1_EN=1 EDATA1_STRT=0x73. Erase sectors 120–127 and fill them with byte 0xEC.4. Create a file file.bin file with 10 bytes of some data.5. STM32_Programmer_CLI.exe --connect port=SWD mode=UR speed=fast ap=1 -d file.bin 0x09001800I expect sector 121 to be erased and the first 10 bytes of it programmed with contents of file.bin.Actually, sectors 121–127 are erased and the first 10 bytes of sector 121 are programmed with contents of file.bin. I.e. it seems erase is done for the reminder of the bank instead of calculating the number of affected sectors from file length.But if you set EDATA1_EN=0 and download file.bin to 0x08002000 it works. The system only misbehaves when the flash is configured as high-cycle count flash.The problem can also be reproduced by using a .hex-file targeting these addresses. Would it pos

Hello, I am currently having problems initializing the I2C interfaces on the M33 core of the STM32MP257F-DK Board. The interfaces in question are I2C2 and I2C8, the ones exposed on the 40 pin connector. I have code that toggles LEDs and it works fine when the I2C initialization is commented out but when its not it pauses. I found a community post that seemed like it might have the answer, here is the link for that post: https://community.st.com/t5/escalated-topic/stm32mp257f-persistent-issue-with-i2c8/td-p/854389. But when I click the link I get taken to a page that says the following: Access DeniedYou do not have sufficient privileges for this resource or its parent to perform this action. Click your browser's Back button to continue. Return to my original page

Starting from V2.13 the STM32CubeProgrammer_CLI adds strange empty lines into the .hex file when adding CRCs using the --safelib command.Example:...:20F9C000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF47:20F9E000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF010002010100000032B840D616:00FA000006:00FA000006:00FA000006...:00FA000006:00FA000006:020000044807AB:20FA0000D8E292E5D9D0BDBC4BA59A0800855CA4FBEF5C19E0AC58BC12F208DD16414D16DA:20FA20007C32E22F87D80DB1ACEF0F2AC0E8EA3883BA937EC9278191C221243352C16A6BDA...Each empty line has the address of the first free place into the original .hex (seme address where CRCs will be added) but no data and the number of lines seems to be equal to the number of CRC lines added.This is annoying because later I use srec_cat tool and I get lots of warnings about these empty lines! Any suggestione?Thanks!

I'm trying to flash an an NUCLEO-N657X0-Q board with the STM32N6 using STM32CubeProgrammer v2.20.0. I have two NUCLEO-N657X0-Q boards here: One of them flashes just fine, the other one refuses to work. Both boards are in development mode (BOOT jumpers set accordingly as described here https://github.com/STMicroelectronics/STM32N6-GettingStarted-ImageClassification?tab=readme-ov-file#boot-modes). In STM32CubeProgrammer, I have selected the appropriate External loader to be able to write to the external flash memory.As a simple experiment, I am trying to erase a sector of the external flash memory. I am using the exact same STM32CubeProgrammer settings for both boards. Erasing the flash works just fine on one of the boards, but on the other board, I get the following error:Did I accidentally enable some kind of flash memory protection? How do I disable it? Or is my board broken? The board still boots the old code in the flash memory when in flash boot mode, so I don't thin

Update: I found out that HAL_PWR_EnableWakeUpLine() must be enabled to wake up the system.The system now wakes up correctly from Stop3 mode. With the SMPS enabled and all pins configured as analog, the current draw is approximately 5 µA, which matches the values given in the datasheet./**********************************************************************************************************************************/ Hello everyone,I am working with NUCLEO-U385RG-Q board and using the RTC wake-up timer as the wake source for low-power modes. I noticed consistent differences between STOP2 and STOP3:IssueThe RTC wake-up interrupt works reliably in STOP2.The exact same configuration does not wake the system from STOP3.ConfigurationLSE is running (32.768 kHz crystal).RTC is clocked from LSE.RTC wake-up timer is configured via HAL_RTCEx_SetWakeUpTimer_IT().No other wake sources are enabled.QuestionsAre there additional registers or power settings required for STOP3 to allow RTC wake-up e

Hello.I have developed a firmware for Riverdi_121STM32H7.The firmware has Italian and English texts,but we planned to develop a version for Chinese customers, Myanmar, and other non european customers. My doubt is:  Unicode::atoi and Unicode::sprintf("%d" produce number in other language, don't ? Thakyou for the answers ... 

Heyho,after some *** CAN beginner mistakes on my side, I got the FDCAN BRS 8 Mbit working.Or so I thought. It's only working between my custom boards, as I found out after connecting a Kvaser Leaf v3.With the Kvaser (directly connected to the board's D-sub, termination on, signals on the scope look good (enough)) and BRS on, it only works with max 2 Mbit, and only if the Kvaser's bit timing is set below 70% sampling point.So far I played with changes to TDC, sampling point, SJW, and all bit timings (checked the Kvaser timing website).Any ideas welcome!

Currently, STM32Cube for Visual Studio Code introduces a new bundled package manager which replaces STM32CubeCLT.However, when developing STM32 projects with other IDEs (e.g. CLion), STM32CubeCLT is still required to provide the build environment.This leads to several problems when using multiple IDEs (VS Code + CLion):Separate installations of toolchains (STM32Cube for VS Code and STM32CubeCLT) consume extra disk space.STM32CubeCLT cannot be updated incrementally; users must download the whole package.STM32Cube for VS Code currently cannot manage STM32CubeCLT packages, leading to duplicated toolchain management.By default, tools are installed on C:\ drive, which is inconvenient for users with limited system disk space.Feature request:Allow STM32Cube for VS Code’s package manager to use and manage STM32CubeCLT packages.Benefits:Reduce disk usage by avoiding duplicated toolchains.Simplify updates and package management.Improve developer experience when using multiple IDEs (VS Code + CLi

Post edited by ST moderator to be inline with the community rules for the code sharing. In next time please use </> button to paste your code. Please read this post: How to insert source code. Hello everyone, I have designed a custom PCB using the STM32L031K6 microcontroller. The board includes an external 32.768 kHz crystal oscillator (LSE - Low Speed External). The Problem: I am flashing code to the board using an ST-Link. When running a simple LED blinking application (which uses HAL_Delay), the LED either blinks only once or gets stuck indefinitely within the HAL_Delay function. This strongly suggests an issue with the microcontroller's clock configuration or the LSE activation. Hardware and Code Details: MCU: STM32L031K6 External Oscillator: 32.768 kHz (LSE) Development Environment: STM32CubeIDE Library Used: STM32Cube HAL Problematic Function: HAL_Delay() (This function relies on a properly running clock source, usually SysTick). I will attach the following: S

Hello community,I am running in an issue with the VREFINT calibration value of the ADC.For calculation I use the __LL_ADC_CALC_VREFANALOG_VOLTAGE function from the stm32u0xx_ll_adc.h file and I'm getting wrong values.The Chip is powered with 3.3V and so I expect a reading of approx. 3300 from this function, but what I'm getting is a value of around 2993.The measured voltage at the VDDA/VREF+ pin (48-pin package) is 3.296V, the reading of the VREFINT Channel is approx. 1660.If I change the supply voltage to 3V, I get around 1820 from the VREFINT Channel.The readout of the VREFINT address (0x1FFF6EA4) is 1654 (0x0676) so point 2.1.2 of the errata sheet is not applicable.If I change the value VREFINT_CAL_VREF in stm32u0xx_ll_adc.h from 3000UL to 3300UL the return values are plausible.For me it looks like the calibration was done using 3.3V instead of 3.0V as stated in the datasheet.The marking of the controller reads likeSTM32U073CCT6CQ27C 9R ACHN 435 1M (or LM)Can anyone confirm or is th

I try to understand in details the way the Hash peripheral works on the STM32L552. I need to make the HASH SHA-256 with 224 blocks of 512 bits. The Hash works perfectly until the block 223. Then I enter 16 values in the FIFO (in my code below I have a loop for 15 because I entered previously another value). Then I launch the final digest. I expect the automatic digest of block 224 and the automatic padding in a block 225 to the final hash value. But I always have the wrong value in the final step. Any idea about what I'm missing? 

I would like to read some data from the EEPROM on initialization to use in the TouchGFX application.I currently have an API that can request read/write operations from TouchGFX to the backend.At the moment, I've implemented it in the Model.hpp void bind(ModelListener* listener) { modelListener = listener; if (!storageInitialized) { initializeFromStorage(); storageInitialized = true; } }withvoid Model::initializeFromStorage() { #ifndef SIMULATOR StorageResponse_t wr = Storage_Request(STORAGE_CMD_READ, EEPROM_ADDR_STRUCT_2, &struct2, sizeof(struct2)); wr = Storage_Request(STORAGE_CMD_READ, EEPROM_ADDR_STRUCT_1, &struct1, sizeof(struct1)); #endif }but I'm not sure if it's the correct location.I just want to send the read EEPROM command on the first load of TouchGFX and never again