Product forums

Hi, I am currently working on a project that requires us to install a browser on our board. We are using an STM32mp25, which is using the Mickledore image. I am finding that the meta-browser layer is not compatible with Mickledore, and if I'm not mistaken meta-browser only runs on Scarthgap. What I've tried to do is switch my layers to the Scarthgap branch, and unfortunately what I find is that from my conf/local.conf is that the stm32mp25 is not a recognized maching (MACHINE = "stm32pm25"), meaning that the stm32mp25 is not supported on Scarthgap. Has anyone successfully installed a browser on the stm32mp25 (eval board)? Any help would be greatly appreciated! For reference I was following along with this demo https://www.digikey.com/en/maker/projects/intro-to-embedded-linux-part-2-yocto-project/2c08a1ad09d74f20b9844e566d332da4

Our Engineering team is currently having difficulties getting our onboard STM32F303RB MCU to enumerate as a USB DFU device when entering Bootloader mode. We require this functionality in order to be able to upgrade our firmware out in the field. We are able to have our application firmware enumerate a USB device but no luck with the bootloader. The STM32 communicates to an Embedded Linux Host via a USB Hub: Embedded Linux Host <-> USB Hub <-> STM32 We have a few questions regarding getting the bootloader to enumerate. On the internet there appears to be mixed messages as to whether the STM32F303RB MCU uses an internal pullup when in the Bootloader. Are you able to confirm whether it does enable an internal pullup for the bootloader? I have set BOOT0 HIGH but there is also mixed messages about BOOT1 being pulled to GND. To enter USB DFU mode does BOOT1 have to be pulled to GND or is it a don't care and can be left floating? Is there some kind of output/pin I am able to prob

STM8S003F3P6 in this there are two timer 1 with Four independent capture/compare channels (CAPCOM) configurable as input capture, output compare, PWM generation (edge and center aligned mode) and single pulse mode output and tim2 has 3 individually configurable capture/compare channels.can i use all seven as simultaneously for PWM?

STM32H7R7L8H6H XSPI2 is mounted with MX25UM25645GXDI00, and the frequency setting exceeds 133Mhz. The Boot program fails to run and gets stuck in the "XSPI_WaitFlagStateUntilTimeout" function.Please help me!XSPI2 ConfigurationClock Tree ConfigurationEXTMEM_MANAGER Config 1EXTMEM_MANAGER Config 2Stuck here

USB Issues with STM32F767-ZIT – Project StatusI’m an amateur working on building an electronic device. Currently, I’m in the planning and prototyping phase and creating my own PCB design. My current project is based on the STM32F767-ZIT, and I’m having trouble getting the USB (USB-B) connection to work.Hardware SetupPower: VBUS is powered through a ferrite from 5 V on the female USB-B jack.Data lines: D+ and D- are connected to PA11/PA12, each with 22 Ω resistors.GND: connected to the board.HSE: 8 MHzWires: relatively short, nothing unusual.Current BehaviorWhen connecting to a PC:Windows plays the device connect sound, and a device appears in Device Manager.The device shows as “Unknown USB Device (Device Descriptor Request Failed)”.Properties:Device type: USB ControllerManufacturer: Standard USB Host ControllerStatus: “This device has been stopped because it reported problems (Code 43)”USBView shows: FailedEnumeration: Unknown USB Device (Device Descriptor Request Failed)Oscilloscope O

I'm working on a custom STM32U5 board and I'm trying to harden the system.I followed the AN5347 (https://www.st.com/resource/en/application_note/an5347-arm-trustzone-features-for-stm32l5-and-stm32u5-series-stmicroelectronics.pdf) in particular I followed the chapter 10 with success as I was able to raise up to RDP=2 with OEM password and back to RDP=0.Then I tried for the second time using the STM32CubeProgrammer instead of the command line as described in the application note, but I got some issues at step 5: Set RDP level 2. The STM32CubeProgrammer did not end the process and got stuck writing RDP=0xCC in the option byte and after ten minutes I forced the termination of the GUI.After that I was not able to recover to RDP=0.Every time I try to send a command to the board I get some error.If I try to follow chapter 10.6 Unlock RDP level 2 with OEM2Key with the command line:STM32_Programmer_CLI.exe -c port=swd mode=UR -unlockrdp2 0xMYKEYLOW 0xMYKEYHIthe result i

I have been running into an issue with the cubeprogrammer very recently where I am unable to connect to my MCU anymore. I get the following log: using v2.2212:41:28 : STM32CubeProgrammer API v2.22.0 | Windows-64Bits12:43:17 : UR connection mode is defined with the HWrst reset mode12:43:17 : ST-LINK SN : 34FF6A0630514B384036244312:43:17 : ST-LINK FW : V2J47S712:43:17 : Board : --12:43:17 : Voltage : 3.56V12:43:17 : SWD freq : 4000 KHz12:43:17 : Connect mode: Normal12:43:17 : Reset mode : Hardware reset12:43:17 : Device ID : 0x45012:43:17 : Revision ID : Rev V12:43:17 : Error: Database: There's no active configuration for this device. All the 8 configurations are disabled!12:43:17 : Debug in Low Power mode is not supported for this device.12:43:18 : UPLOADING OPTION BYTES DATA ...12:43:18 : Bank : 0x0012:43:18 : Address : 0x5200201c12:43:18 : Size : 308 Bytes12:43:18 : Error: Uploading Option Bytes bank: 0 failed12:43:18 : Error: Initializing the Option Bytes failed12:43:18 : Error: Unab

Hello,I'm using the latest STM32CubeMX 6.16.1 (Linux version), and working on a project cloned from the one provided for STM32MP257F-DK.In the Project Manager -> Advanced Settings, there is the "Generated Function Calls" table.If I set checkboxes here, e.g. in the "Do Not Generate Function Calls" column, the generated code reflects the new settings. However, when I reload the project (via "close/open" or just restarting CubeMX), all checkboxes are in their default positions (disabled for all functions in "Do Not Generate Function Calls").The same thing is with the first "Generate Code" column, and re-ordering the calls doesn't save as well.Is there a workaround?A question to STMicro engineers: enabling OpenAMP middleware for STM32MP2 boards fails to build in CubeIDE. Looks like it is a known issue https://community.st.com/t5/stm32-mpus-software-development/stm32mp257f-dk-openamp-no-such-file-or-directory/td-p/786509, is there a plan to fix it in the next release of CubeMX?Thanks!Reg

Hi! I'm trying to muddle my way through a project in which I'd like to use an stm32u5 MCU. I would like to extend the RAM/FLASH of the MCU by using PSRAM and eMMC; it seems that higher densities of PSRAM require being run at 1.8V, so I am imagining powering at least the digital side of the MCU with a 1.8V rail. My application also involves motor control; I'll be using the STSPIN233, which can also be powered by a 1.8V rail. I would like to perform current sensing, and here's where my question comes in. I'd like to use a current sense amplifier, e.g. TI's INA181 (or similar). These devices need a 3.3V rail for power. I am curious whether it is better to:Power the analog domain of the stm32u5 at 3.3V. The current sense amplifiers + shunt resistors are scaled such that I produce a total rail-to-rail voltage near 3.3V, biased at 1.65V.Power the analog domain of the stm32u5 at 1.8V. The current sense amplifiers + shunt resistors are scaled such that I produce a total rail-to-rail

Im trying to get the reading from distance sensor SICK DT35 through STEVAL-IOM001V1 which uses the L6360 IC via STSW-IOLINKGUI to get the proper reading we need to upload the IODD file of the sensor which I'm not be able to do with the GUI. There's not sufficient information about the GUI which is the cause of the problem so provide the needed documentation otherwise provide us the way to get the value from the sensor. and specify that what is the STSW-IOLINKGUI for is it just to test the connection via running the LED BLINK code.Give me a detail documentation to understand all the functions of the GUI.

Hello Team,   One more query is there. We are not using USB. In STM32H7S7L8H6 pin D9-VDD50USB is there. So, can we connect it with 3.3V supply?   Thanks & Regards, Jignesh Karena

When creating a new project (for STM32H573) using CubeMX, it generates defaults keys under ROT_Provisioning\SM\Keys:06/19/2025 03:20 PM 232 ITS_key1.pem02/17/2026 09:34 PM 16 SFI_Encryption_Key.bin02/17/2026 09:34 PM 12 SFI_Encryption_Nonce.bin02/18/2026 12:06 PM 136 SFI_Global_License.bin06/19/2025 03:20 PM 246 SM_Authentication.pem06/19/2025 03:20 PM 182 SM_Authentication_pub.pem06/19/2025 03:20 PM 246 SM_Encryption.pem06/19/2025 03:20 PM 182 SM_Encryption_pub.pemUsing TPC, those keys (including the SFI_global_license) can be regenerated, but when provisioning, got the following error:2026-02-18 12:19:23,911 - DEBUG - Processing license...2026-02-18 12:19:24,072 - DEBUG - Error: Execution of RSS CMD failed, returned value = 0xF6F6F6F62026-02-18 12:19:24,072 - DEBUG - Error: Failed to Process License!2026-02-18 12:19:24,073 - DEBUG - Error: .....ROT_Provisioning\SM\Binary\SecureManagerPackage.sfi SFI file Install Operation Failure! Please, try again.2026-02-18 12:19:24,073 - DEBU

    Reference Board: Nucleo-H753ZI (MB1364, ST-LINK V3, rev B) Summary We have an external UART sensor (WitMotion HWT9053 IMU) connected to the Arduino D0/D1 header pins on a Nucleo-H753ZI. The sensor is confirmed working on Arduino. We have verified all USART register configurations are correct at the hardware level. A full GPIO scan of every MCU pin (PA0–PG15) shows zero toggling signal from the sensor. We suspect a board-level routing issue (solder bridges) but need ST guidance. Approach History Phase 1: Custom STM32H7 Firmware We wrote custom firmware using STM32H7 HAL to communicate with the sensor at 57600 baud via USART1 on PB6(TX)/PB7(RX). Console output via USART3 PD8/PD9 (ST-Link VCP) works correctly. Phase 2: Porting Vendor F1 Reference Code to H7 We also ported the sensor vendor's official STM32F1 sample code to STM32H7 HAL. This scans all standard baud rates (4800–921600) and attempts to detect the sensor. Same result — zero bytes received. Phase 3:

We found that a specific card type (Mifare Desfire EV1) became unusable with the RFAL after a format. But I was able to "resurrect" it by using a Phone or a reader with a different IC.Since debugging showed that the gIsoDep.state was always getting stuck in ISODEP_S_DSL, I saw that the default retires for deselect are zero. And as the Standard states "When the PCD fails to receive an S(DESELECT) response the PCD may retry the deactivation sequence.", I increased them by manipulating RFAL_ISODEP_MAX_DSL_RETRYS inside the lirbraries headers.As a result the card also worked again on my ST25R3961b based device. But I would very much like to not change the library code and instead use officially provided interfaces. That interface seems to be rfalIsoDepInitializeWithParams(). But it is explicitly called inside rfal_nfc.c with the default parameters, just before starting the RATs. So where do I intervene to get my own settings in? Is that even possible?

Please note that maintenance on the user authentication service is scheduled for 26 February. During this period, some disruptions may occur. The impact is limited to versions earlier than STM32CubeMX V6.16 and STM32CubeIDE V2.0.0. The service returns to normal soon after maintenance is complete. What to do if you encounter a problem If you experience issues during the maintenance window, please use st.com or try again after one hour. If the problem persists after that time, contact us through the Community for further assistance.   Update 27 February 2026: The maintenance was successfully completed as scheduled on 26 February. If you encounter any issues, please do not hesitate to contact us.    

Please note that maintenance on the user authentication service is scheduled for 26 February. During this period, some disruptions may occur. The impact is limited to versions earlier than STM32CubeMX V6.16 and STM32CubeIDE V2.0.0. The service returns to normal soon after maintenance is complete. What to do if you encounter a problem If you experience issues during the maintenance window, please use st.com or try again after one hour. If the problem persists after that time, contact us through the Community for further assistance.   Update 27 February 2026: The maintenance was successfully completed as scheduled on 26 February. If you encounter any issues, please do not hesitate to contact us.

I realized that in my discovery board with STM32F411VE the accelerometer/magntometer is lsm303agr and not lsms303DLHC. I would have an updated schematic.

STM32CubeMX v6.14.1 (Firmware Package is STM32Cube FW_G0 V1.6.2) has removed the option for peripheral I2C2 to select SMBus-two-wire-interface.This prevents me from migrating my project as only SMBus-Alert-mode is available but can't be used as the alert pin is already allocated for GPIO. So the CubeMX migration changes I2C2 to I2C mode.The original project is from STM32CubeMX v6.10.0 and the Firmware Package is STM32Cube FW_G0 V1.6.2I tried creating a project from scratch and the SMBus-two-wire-interface option just isn't available.   

Hi, I am working with the STM32MP25 and trying to use the I2C peripheral from the Cortex-M33 coprocessor.The STM32MP25 includes an Arm Cortex-A35 core running Linux and a Cortex-M33 core for real-time applications. I am able to successfully load and run a basic firmware on the Cortex-M33 using remoteproc. However, when I enable and initialize the I2C peripheral in the M33 firmware, the system hangs and eventually restarts. After investigating, I learned that the RIFSC configuration must be updated to grant the Cortex-M33 access to the I2C peripheral. I applied a patch to modify the RIFSC settings accordingly, but the issue persists and the peripheral is still not accessible from the M33.I would like to know:Are there any additional steps required (beyond RIFSC configuration) to allow Cortex-M33 access to I2C?Is there official documentation or reference material explaining how to properly assign peripherals to the coprocessor using RIFSC?Are there any examples or recommended workflows f

Dear,  Can you confirm that OCTOSPI P2 is available only on WLCSP208 and TFBGA216 packages of this series?  I wanted to use both OCTOSPI interfaces in LQFP144, but noticed that there is missing only OCTOSPIM_P2_IO3 line in it, so my conclusion is that LQFP144 supports only one OCTOSPI. Is that right?  Thank you. 

Hi,I am implementing DCMIPP configuration in that I am enabling the CSI but when I trying to enable the pin I cannot enable the the camera pins those pins are showing red. And I am unable locate .ioc file  for DCMIPP interface is there any .ioc file configuration please provide that.

Question for STM.Could you please advise what to do to make the environment generate audio files?Could anyone of you show me how to generate these files?They are generated for all classes except audio.I guess there should be these too.Alternatively, please show me how to create an AUDIO Device using the STM32H5 processor.Please for the msc class even adds  storage_configuration_number = USBD_Get_Configuration_Number(CLASS_TYPE_MSC, 0); storage_interface_number = USBD_Get_Interface_Number(CLASS_TYPE_MSC, 0); if( ux_device_stack_class_register( _ux_system_slave_class_storage_name, ux_device_class_storage_entry, storage_configuration_number, storage_interface_number, &storage_parameter) != UX_SUCCESS) { return UX_ERROR; }Edited to apply source code formatting - please see How to insert source code for future reference.

I am experimenting with STs Fast Transfer Mode using FEIG MR102 Reader. I tried the FTM Demo on the ST25PC NFC. For that I connected the STEVAL-25R3916B reader and used ST25DVC Discovery board for ST25DV tag.  Please note that I am using the source code of ST25PC NFC to run the FTM Demo so that I can capture the console. I used the "Send a 100k-byte random buffer" option from FTM Demo and looks like it works fine. You can see one instance from console of the FTM in action: 2026-02-27 11:42:53.286 fastWriteMsg >> 22CA02329411AE665102E0FF08E2961EF89ABC5F493D2D14CB68C4A312312D34C056B52A067D78D7575F4B3280F5D3283699CF4A7ED9069AFB137F8DA1185045C625008F995DDA0057A51E329F00A3DA1044D27B0B9A81E4DC28D1C27683AB2430F758859F3E1BE7D6F16815749EC5C094D1A8414AD0561E5CD6CD552AA78EDAED96CE741C4142C7B8275E7D4A9BE10622D4B373B288E2707358C1DC3819A3C8C7672019D9152C1C79F7CBBA98A2D8EFE000730D45E6AA723BFA3A7DCDF38D0D8E7D556A031631D9D589BA4613EE0196C8437CA6596BCA725255EFBD8781D1

Hi,When is VD66GY expected to be back in stock?

The STM32Cube CMake Support extension blocks the VSCode UI when multi-root VSCode workspace are opened. Specifically, if a multi-root workspace is opened, the STM32Cube CMake Support extension continuously shows the Select hardware window. Even if the user closes the window by pressing Esc, it immediately reappears, preventing the user from doing anything, since that window has the highest priority.This happens because the extension detects the CMakeLists.txt file in the sub-workspace another_generic_cmake_project (see attached project) and, for some reason, attempts to configure the sub-workspace as an STM32Cube project, even though it is not an STM32 project but a generic CMake project.Currently, as a workaround, I have to add the setting: "settings": { "stm32cube-ide-build-cmake.ignoreCubeProjectDiscovery": true, }to the multi_root_project.code-workspace file, which prevents the STM32Cube CMake Support extension from attempting to detect the main workspace and any