Recently active topics

I am looking at the datasheet and reference manual for the STM32H750. I am trying to learn about the connections between buses and I saw on the reference manual that AHB2 in the D2 domain has no master bus port, however the datasheet shows an AHB/APB bridge between buses labeled AHB2 and APB2. later in section 2.1.3 of the reference manual, there is no mention of an AHB2 to APB2 connection. What does this mean for accessing peripherals on the AHP2 peripheral bus, is it intended for AHB1 as per the reference manual, or through AHB2 as per the datasheet, or is there another way I am not seeing?Reference manual Diagram showing no AHB2 → APB2 connectionDatasheet Block Diagram showing APB2 connection to AHB2 through AHB/APB bus bridge (blue box) 

We have begun work on a new project based on RFID technology, specifically utilizing the ST25R3915. For simulation purposes, we require an IBIS model for this chip; however, I have been unable to locate one on your website. Would it be possible for you to provide an IBIS model so that we may perform PCB simulations prior to manufacturing?Thank you in advance!Best regards!

Hello all,The problem that I’m facing is that two specific zones are showed in white color in my screen. These zones only appear in a circleProgress that is based in an image.I am using the TouchGFX version 4.26.1, and the MCU is a STM32U575CIUX.These problem only happens when I save data on the persistent memory of the MCU with this function (source code below):// Write into flash memorybool PERSIST_write(RegistroFlash *persist_memory_to_write){uint32_t address = USER_FLASH_START_ADDRESS;uint8_t *ptr = (uint8_t *)persist_memory_to_write;FLASH_EraseInitTypeDef erase;uint32_t pageError;HAL_StatusTypeDef program_ok_result = HAL_ERROR;bool function_ok_result = false;// Unlock the flash memory to write thereHAL_FLASH_Unlock();// Erase the corresponding flash page (in my case only the last page 255)// Although we do not use it completely a complete page must be deleted (2 KB)erase.TypeErase = FLASH_TYPEERASE_PAGES;erase.Page = (USER_FLASH_START_ADDRESS - FLASH_BASE) / FLASH_PAGE_SIZE;erase.

Hi everyone,I'm having a very annoying issue with an STM32U5G9ZJ and a Newhaven NHD-4.0-480480AF-MSXP-CTP display using an ST7701SN over 2-lane MIPI DSI.The basic communication works, but I cannot get any video onto the display.What worksThe panel responds correctly to LP short DSI commands:Reset works. ST7701 registers can be read. The initialisation sequence runs successfully. 0x29 Display ON works. 0x23 All Pixels On makes the display white.So the panel and the LP DSI communication are working.What doesn't workAs soon as I try to send RGB888 video over HS DSI, the display stays black.I've tested this both using the LTDC/framebuffer and the internal pattern generator. The latter was to rule out the framebuffer/LTDC completely.The pattern generator starts successfully and the DSI registers show the video engine and both data lanes entering an active HS state, but the panel still stays black.I'm using:2 DSI lanes RGB888 Burst video mode 480 × 480 480 packet size Continuous clock Automa

I am working on a project involving communication between an STM32H753 and an FPC2534. I have successfully connected the two components, and the system works as expected; however, it stops functioning when I enable the I-cache and D-cache on the STM32H753. Could you explain why this happens?

Hi!I’m using this commangst-launch-1.0 -v  filesrc location=bbb.mp4 !  qtdemux ! h264parse !  v4l2slh264dec !   waylandsink fullscreen=trueTo play video in 1080p without lagging. But this comes without sound.How can I play sound with gst-launch-1.0?I can only play sound with “aplay /path/to/file.wav”.

Hello,I would like to report an issue encountered with the "STM32CubeWiSE - Bluetooth LE Explorer" tool, version 1.1.0.I am using a custom board equipped with an STM32WBA65, running firmware in "TransparentMode."To connect my board to the PC, I am using an FTDI USB-to-serial adapter.The problem occurs when the tool opens the COM port: the first command, "HCI_READ_LOCAL_VERSION_INFORMATION," fails because 4 unexpected characters (0xFF, 0x01, 0x00, 0x00) are sent by the PC.Even the retry attempt, which occurs one second later, fails because the HCI protocol is no longer synchronized.Consequently, the tool fails to recognise the chip and is not usable.This issue does not occur with the Nucleo board's USB-to-serial adapter.STM32CubeMonitor-RF 2.19.0 works fine.As a workaround, I modified the firmware to ignore the 3 next characters when its get an invalid packet indicator with value 0xFF.BRAnthony S 

Hi everyone,We’re currently evaluating the LSM6DSV16X for a multimodal data acquisition application and are using its Machine Learning Core (MLC) to detect specific events and generate corresponding labels in a time-series data stream.To ensure accurate temporal alignment between different data sources, we’d like to understand the latency between the actual occurrence of a physical event and the availability of the corresponding MLC output.Has ST characterized this latency or published any relevant specifications, test results, or documentation? If not, is there a recommended test procedure or validation methodology for measuring it reliably?Any insights or suggestions from the ST team or community members with experience using the MLC would be greatly appreciated.Thanks in advance for your help!

Hi,I'm trying to program a blank STM32H573 through the embedded system bootloader over I2C4, but the bootloader does not respond.SetupBlank flash, product state Open, BOOT0 = 1 (measured at the MCU pin), board power-cycled Host: Aardvark I2C master at 100 kHz, address 0x65 (per AN2606) No debugger, USB or UART connectedResultLines idle high, but 0x65 is NACKed A full scan from 0x00 to 0x7F gets no ACKQuestionsAN2606 lists I2C4 on PD12/PD13. Does the bootloader use only those pins, or also other I2C4 pins such as PB8/PB9? Is BOOT0 = 1 enough on a blank device, or is STiROT involved in this boot path?Thanks.

Hi! When I run the command "vulkaninfo --summary". I get this critical error."libvulkan_VSI.so.1.3.3 contained a 1.1 or greater API version, but does not support vkEnumerateInstanceVersion, treating as a 1.0 ICD".What this means is that according to the data sheet of STM32MP2, the GPU supports Vulkan 1.3. but due to the lack of support for vkEnumerateInstanceVersion, the Vulkan support falls back to 1.0.Question: is this true that Vulkan falls back to 1.0 fue to this warning?Is there any newer version of libvulkan_VSI.so?Here is the complete output: """WARNING: [Loader Message] Code 0 : loader_scanned_icd_add: Driver /vendor/lib/libvulkan_VSI.so.1.3.3 supports Vulkan 1.3, but only supports loader interface version 2. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Manifest ICD for "/vendor/lib/libvulkan_VSI.so.1.3.3" contained a 1.1 or greater API version, but does not support vk

I have heard that ST have tried QtNanoBrowser on the MP257 and according to them the web browser is working well.My question is if there are any more additional information about the user experience of QtNanoBrowser on the MP257?For example a benchmark and which pages did run smoothly and which pages took long time to load.

 Hello STM32 Community,I am currently working on a custom PCB designed using the STM32H7A3ZIT6Q (Cortex-M7) microcontroller. I am trying to program the MCU using an ST-LINK/V2 debugger through a Tag-Connect adapter, but STM32CubeProgrammer is unable to detect the target MCU.Hardware configuration: MCU: STM32H7A3ZIT6Q (SMPS variant) Programmer: ST-LINK/V2 Adapter: TC2050-ARM20-10 REV2 Programming cable: TC2050 PCB programming connector: TC2050-IDC-ND footprint External power supply: 3.3 V DC Target voltage reported by ST-LINK: 3.22 V Debug interface: SWD STM32CubeProgrammer settings: Port: SWD Frequency: 100 kHz Mode: Under Reset Reset Mode: Hardware Reset Access Port: 0 Speed: Reliable ST-LINK Firmware: V2J47S7 Error messages:Error: Unable to get core IDError: No STM32 target found!Troubleshooting performed: The ST-LINK/V2 is successfully detected by STM32CubeProgrammer. The programmer reports a target reference voltage of approximately 3.22 V. The PCB is

Hello,I’m a master’s student soldering an STM32L031G6U6 (UFQFPN28) onto my own PCB using a hot air station, and I’d like to do it correctly. My first attempt (no solder paste, no extra flux, about 400 °C) left the chip unable to connect over SWD, so I suspect poor joints or heat damage.Could you please advise:1. Do the package pins carry enough solder on their own, or should I apply solder paste/flux on the PCB pads?2. What hot air temperature, airflow, and heating time do you recommend, and what is the maximum temperature/time the part tolerates?3. Is there a recommended reflow profile or preheating for this package (e.g. JEDEC J-STD-020), and any ESD or handling precautions?Thank you in advance for your help.

Hello ST Support,I am using the NUCLEO-H533RE board and would like to clarify whether the STM32H533 supports hardware-accelerated SHA-3, particularly SHA3-256.I noticed an inconsistency in the documentation:The product page and datasheet feature summary list “HASH (SHA-1, SHA-2, SHA-3)”. Section 3.30 — HASH hardware accelerator of datasheet DS14539 Rev 3 describes SHA-1/SHA-2 algorithms but does not mention SHA-3. I could not find a SHA-3 operating mode in RM0481, or a corresponding algorithm selector/API in the STM32CubeH5 HAL version installed in my project.Could you please confirm:Does the STM32H533RET6 physically support hardware-accelerated SHA3-256? If so, which registers, HAL APIs, and STM32CubeH5 version should be used? Is an example available?Thank you for your clarification. 

Hello everyone! 👋I am new to STM32 development and recently started learning how to program STM32 microcontrollers using STM32CubeIDE. I created a simple project, but I am having trouble connecting my development board to the debugger.I am not sure whether I missed a configuration step or if there is a problem with the USB connection or debug settings. Since I am still learning, I would appreciate some guidance on how to troubleshoot this issue. 😊❓ Error / IssueWhen I try to start a debugging session, STM32CubeIDE does not seem to detect my board correctly. Sometimes the debugging process fails to start, and I am unsure what to check next. ⚠️ 🙏 My Questions Is there any additional driver I need to install? How can I check whether the ST-LINK debugger is detected correctly? Are there any beginner-friendly steps to verify the board and debug configuration? I would really appreciate any advice. I am just getting started with STM32 and would love to learn how to solve this

Wiring from st link to the stm32g061Error message It does not connect to STM32CubeProgrammer with the stm32G061 it keeps saying Error: unable to get core IDError: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication. I have NRST pulled high with a 10k ohm resistor and then a tactile button which will make it go low when pressed.  The pinout for the STM32G061 is the same as the STM32G050 and when I have the same wiring as I did with the STM32G050 on this st link v2, but with the stm32G050 it connected correctly in STM32CubeProgrammer.  Why doesn’t it work with the STM32G061?

Our board contains a STM32H523 and a W25Q256JV connected to OctoSPI1 configured for Quad SPI mode. FileX/LevelX should handle the external memory.LevelX OSPI Component is configured for “Custom”. After generating the code with CubeMX (6.18.1), Filex/Target/lx_stm32_ospi_driver_glue.c contains several functions with wrong code, e.g: INT lx_stm32_ospi_get_status(UINT instance) {…/* Initialize the read status register command */s_command.OperationType = HAL_XSPI_OPTYPE_COMMON_CFG;s_command.IOSelect = HAL_XSPI_SELECT_IO_7_0;s_command.Instruction = LX_STM32_OSPI_OCTAL_READ_STATUS_REG_CMD;s_command.InstructionMode = HAL_XSPI_INSTRUCTION_8_LINES;s_command.InstructionWidth = HAL_XSPI_INSTRUCTION_16_BITS;s_command.Address = 0;s_command.AddressMode = HAL_XSPI_ADDRESS_8_LINES;s_command.AddressWidth = HAL_XSPI_ADDRESS_32_BITS;s_command.AlternateBytesMode = HAL_XSPI_ALT_BYTES_NONE;s_command.DataMode = HAL_XSPI_DATA_8_LINES;s_command.DataLength = 2;s_command.DummyCycles = LX_STM32_OSPI_DUMMY_CYCLES_

Hi listI am testing the STM32MP135d-odyssey for a project. It is small, still cheap, has support for POE and on board ethernet connectors and SD-card holder. The buildroot repositories are quite old so I wonder if the board is in actual use and can be recommended for new projects?The xogium repository seems very outdated but I have cherry picked a few patches from there to a fork of STMicroelectronics repository and it builds and boots with modern buildroot. I have only tested to boot from sd-card yet.Please test if interested. I have updated versions of buildroot-stm32mp135d-odyssey, u-boot and optee_os in my Github repository.https://github.com/GauiStori/buildroot-stm32mp135d-odysseyShall I make pull requests for u-boot and optee_os to STMicroelectronics or xogium? Or is there an updated version of xogium somewhere?Now I want to see if I can find a working Yocto recipe. RegardsGudjon 

Page 31 of AN5093, AN2687 is mentioned while discussing crystals. AN2687 is about a LCD software driver. I believe they meant to mention AN2867 which is also mentioned earlier in the document.   

Hello,I have a STM32U585. I’m trying to use SAI to transmit and receive I2S audio as a slave. The I2S master is an external codec that’s configured for stereo 16bit 16kHz audio. Mic/input from codec->MCU and speaker/output from MCU->codec. The first stereo sample received on the codec is routed to the left speaker and second to the right. This works as expected for the mic. For the speakers, sometimes even samples will play on the right side and odd on the left. I’ve loaded the DMA buffer with dummy values 0xAAAA and 0x0000 to demonstrate. MISO is the signal of interest here. I’d like 0xAAAA to be on Ch 1 consistently.Expected SamplesUnexpected SamplesThis occurred about 50% of the time. It’s observable for the entire runtime and doesn’t correlate with how long the software has been running. I suspected a sync issue SAI/DMA so I implemented a quick hack to poll the GPIO to start the DMA transfer after the falling edge of WS to help sync. This improves reliability from 50% to 90%.

Hello,I want to implement HOGP (BLE HID) on an STM32WBA23KE so that it can connect to Windows 11.I implemented it using the BLE_HID_Mouse sample for STM32WBA55G-DK1 as a reference, but Windows 11 does not recognize it as an HID device (it seems to be failing in some procedure after the Bluetooth connection). I checked the GATT service configuration by connecting with a smartphone app, and there seem to be no particular problems (although I cannot read the Report Map or HID Information due to BLUETOOTH_PRIVILEGED).With the STM32WBA55G-DK1, I have confirmed that it can connect to Windows 11 as an HID device and behaves like a mouse.I have attached the main source files and .ioc file of the STM32WBA23KE project.Are there any possible causes?Best regards, Gotoda 

Cubemx2 only allots enough buffer descriptor table space for 4 endpoints. When a 5th endpoint is added, the table will overlap with the data buffer. In the following generated code, address should be starting at 0x28 and not 0x20. HAL_PCD_PMAConfig(&hUSB_DRD_FS_PCD, 0x0, HAL_PCD_SNG_BUF, 0x20); HAL_PCD_PMAConfig(&hUSB_DRD_FS_PCD, 0x80, HAL_PCD_SNG_BUF, 0x60); HAL_PCD_PMAConfig(&hUSB_DRD_FS_PCD, 0x81, HAL_PCD_SNG_BUF, 0xA0); HAL_PCD_PMAConfig(&hUSB_DRD_FS_PCD, 0x82, HAL_PCD_SNG_BUF, 0xE0); HAL_PCD_PMAConfig(&hUSB_DRD_FS_PCD, 0x3, HAL_PCD_SNG_BUF, 0x120); HAL_PCD_PMAConfig(&hUSB_DRD_FS_PCD, 0x83, HAL_PCD_SNG_BUF, 0x160); HAL_PCD_PMAConfig(&hUSB_DRD_FS_PCD, 0x4, HAL_PCD_SNG_BUF, 0x1A0); 

We are using STM32G0B1CEU6N to implement two PD sink ports. USB is not used. We also need IOs with 1.8V and 3.3V levels. Device datasheet states in Table 81 that UCPD requires VDD to be 3.0-3.6V in sink applications. All UCPD CC pins are in VDDIO2 bank. Does UCPD require VDD to be 3.0V or is it really powered from VDDIO2? What voltage level is required on VDDIO2 to support UCPD CC pins?

Windows 11 version 22H2 (OS Build 22621.6060)Visual Studio Code v1.141.0STM32CubeIDE for Visual Studio Code V3.11.0STM32CubeMX v6.18.1STMCUFinder v6.0.0I have configured the executable path below via File > Preferences > Settings below: Already created settings.json below, {  "stm32cube-ide-core.configuration.productSTM32CubeMX.executablePath": "C:/STMicroelectronics/STM32CubeMX/STM32CubeMX.exe",  "stm32cube-ide-core.configuration.productFinder.executablePath": "C:/Program Files/STMicroelectronics/STMCUFinder/STMCUFinder.exe"}When click on “Launch STM32CubeMX”, nothing shown up.However, I can run the STM32CubeMX externally from Windows​​​ (not from VSCode).Later, I found the solution that CAN Launch STM32CubeMX, that is previously I have set the STM32CubeMX.exe to run as Administrator, so:- remove the administrator elevation from STM32CubeMX.exe- remove the settings.jsonThen clicking the “Launch STM32CubeMX”, the STM32CubeMX is running fine already the same time you are able to l

Hello,I am looking for a camera module for the NUCLEO-H7S3L8 board, using the STM32H7S3L8 MCU.My project requirements are: Field of view: at least 120° horizontal FOV Preferably RGB or YCbCr output I would prefer a module that is reasonably easy to connect, with a breakout board or pin header I would like to avoid MIPI CSI-2 cameras because the NUCLEO-H7S3L8 does not have a CSI-2 camera receiver or a 22-pin camera connector The STM32H7S3L8 datasheet, Section 3.26, states that its DCMIPP supports an 8- to 16-bit parallel camera interface, including RGB565, YCbCr 4:2:2 and compressed data such as JPEG. However, the NUCLEO-H7S3L8 board does not appear to have a dedicated camera FPC connector.I found an ST Community table listing OV2640, OV5640 and OV5642 as examples of sensors supported by STM32 DCMI. I am therefore considering an OV5640 module with a 120° lens, such as this module:https://www.eleparts.co.kr/goods/view?no=6210776&utm_ I also considered an Arducam Mega SPI camera