Solved

Using MX created an app utilizing Secure Manager 1.2 on STM32H573, after running 'provisioning.py --sfi-gen', the generated sfi image does not include the non-secure app image; after 'provisioning.py --sfi-flash', the product-state is set to TZ-CLOSED, and the non-secure app image can be loaded using 'project.py download', and the product-state can be changed to Closed manually using CubeProgrammer.  I'd like to simply it to a single step by calling 'provisioning.py --sfi-gen --sfi-flash -a', which will not only provision the secure manager, but also program the non-secure image and set the product-state to Closed, is it possible?

Hi,I am working with some custom boards for H7 and U5-series.The board schematics for STM32H735IG-DK and STM32U5A9-DISC shows both boards are using the same OCTO SPI but only the H7-board is using series resistors of 33 ohms for the all the data lines. In order to minimize reflections and match the transmission’s 50 ohms impedance, I have understood it as series resistor values should be chosen as: R_value = 50 ohm -  MCU_impedance. In such case one would assume the H7-series has an output impedance of about 20 ohms and the U5-series about 0 ohms.Is this a correct assumption / best practice?Are series resistors needed/reccomended on a U5-design?Is output impedance documented somewhere? (could not find it in ref. manuals for memory bus)Thanks for any hints

Hello everyone,I am trying to migrate a project for the STM32MP151C from dunfell to kirkstone.The versions of the main components I am using are the following:ComponentVersiontf-a-stm32mpv2.6-stm32mp-r2.2optee-os-stm32mpv3.16.0-stm32mp-r2.2u-boot-stm32mpv2021.10-stm32mp-r2.2linux-stm32mpv5.15.145-stm32mp-r2.2 The project intends to have a custom u-boot environment. For this a patch is applied to modify CONFIG_EXTRA_ENV_SETTINGS in stm32mp15_common.h, like this:#define FOO_USBFLASH_BOOTFS "foo_usbflash_bootfs=" \ "load usb 0:1 ${loadaddr} foo-image-bootfs-foo-core-stm32mp151c-foo.ext4;" \ "mmc write ${loadaddr} 2400 20000;" \ "mmc write ${loadaddr} 22400 20000;\0" #define CONFIG_EXTRA_ENV_SETTINGS \ STM32MP_MEM_LAYOUT \ STM32MP_BOOTCMD \ STM32MP_PARTS_DEFAULT \ BOOTENV \ FOO_USBFLASH_BOOTFS \ STM32MP_EXTRA \ STM32MP_BOARD_EXTRA_ENVThis approach worked perfectly fine in the old version of the project, but now when the system boots into u-boot I see that the cus

Dear forum,I try to understand the bin shape of the VL53L8CX / CH sensor calibration buffer while evaluating different sensor cover and their influence on ranging. Using the example8 file from the ULD driver the shape looks more or less always the same (as eg. shown by @John E KVAM ) for most cover glasses I used. Nevertheless doing the math with a bin size of 3.75 cm the light path must be in range of ~40 cm, which seems to me highly unlikely with a 1 mm cover glass placed in 0.5 mm distance. Moreover I realized that the calibration buffer yields 144 bins whereas I read somewhere here that there are only 128 bins for ranging.Perhaps someone can elaborate on that a little bit.Thanks!

We are developing a Bluetooth application using the STM32WB55RG. According to the documentation, I found that using the Router and service approach can achieve a one-to-many connection. I want to know if, once a peripheral establishes a connection with the router, it can still connect to other phones. Can the router simultaneously connect to two phones, as shown in the diagram below? Additionally, I found an open-source project on GitHub that has a server-multiple client connection feature, but I am not sure how it is implemented. Could you provide any documentation on server-multiple client connections?stm32-hotspot/STM32WB-BLE-sensors-multiple-links: This example implements a multilink communication between a STM32WB5MM-DK board and up to 8 smartphones through Bluetooth® LE

Hello, I am following a few examples for bare metal firmware (without HAL or LL) to enable USART. I am using a NUCLEO-H745ZI-Q starting with an empty project. From the users manual I am gathering that the STLink MCU on the board provides a 25MHz (X1) clock (STLK_MCO) to (PH0-MCU/PH1-MCU) into the H745xx dual core MCU. I am focused on working only with the CM4 at the moment and ignoring the CM7. I have been pretty puzzled on setting the BRR register with the correct USARTDIV value which is making doubt my understanding of which clock is being supplied to the MCU by default? I am also assuming since there is a physical clock (default clock via hardware supplied) that I do not need to configure a clock? I was able to blink an LED via GPIO/PIN clock enables etc... without configuring like a SysTick or something like that. The board also has the 32.768KHz (X3) directly populated to the H745xx pins but I have ignored it for now. If I use the following code with PeriphClk=25000000 and Ba

Hi everyone,I'm trying to integrate st_yolo_lc_v1_192 pretrained model to my project on STM32H750 MCU.I'm new to the framework and AI tech.I see the output shape is 12x12x30 which I know the 12x12 means there are 12x12 grids. What I don't know is the '30', does that mean 5 * [x, y, w, h, confidence, class] ? and do I need to apply an activation function to these values? Thanks! 

hi i am having a problem with my stm32cubeide, specifically i cant connect to the stm32f407vgt6 microcontroller on my custom board, but when loading or erasing with cubeprog everything goes smoothly.i have tried cleaning my board, updating stlink to v2j45f7, reinstalling stm32cube1.15 since i previously updated to 1.16. still nothing works.can anyone help me?  edit : this my log debug 

Hi,I survey an MCU that IO can be operated in 1.08V to 3.6V.The STM32H563xx could reach my request.But the DS shows the only 10 IOs can be operated in 1.08V to 3.6V.Does STM32H563xx have any setting to extend low power IOs?Or other MCU part number can support more low power IOs(1.08V to 3.6V) ? 

 Hardware SetupBoard: NUCLEO-L412KBPeripherals:SD Card (SPI1)Temperature Sensor (I2C1)Original Pin Configuration (SPI Not Working properly)SD Card (SPI1):CS: PA5MISO: PA6MOSI: PA7CK: PA1 Temperature Sensor (I2C1):SDA: PB7SCL: PB6Issue DescriptionWhen using both SPI1 and I2C1 peripherals simultaneously with the above pin configuration, the SPI communication fails to work properly. Interestingly, when commenting out the I2C initialization, the SPI communication functions correctly.Working SolutionI resolved the issue by remapping the pins as follows:  Modified Pins:SPI1_MOSI: Changed to PB5I2C1_SDA: Changed to PA10I2C1_SCL: Changed to PA9After this remapping, both peripherals work correctly together.SuggestionThis pin conflict might be worth documenting in the board's errata, as the original configuration leads to unexpected behavior when using these common peripherals together.Has anyone else encountered similar issues with this board when using SPI1 and I2C1 simultaneous

Hello,Firstly I'd like to say I have googled for examples and worked independently by reading ST docs and looked at the suggested topics before posting. I did begin to hijack another thread but I'll start one instead.What a long and painful tradition printing with ST dev boards is!My latest attempt is to follow this SWV tutorial for another board.Apologies if it's something ridiculous, I'm new!Having just tested the code before posting tonight, even with non blink related code commented out it has stopped blinking but still some help please :Dhttps://www.youtube.com/watch?v=sPzQ5CniWtwHere is the code I am running.  #include "main.h" /* Private includes ----------------------------------------------------------*/ /* USER CODE BEGIN Includes */ #include "stdio.h" //The printf function is here /* USER CODE END Includes */ /* Private typedef -----------------------------------------------------------*/ /* USER CODE BEGIN PTD */ /* USER CODE END PTD */ /* Private

Dear ST Hello,what is the best way to use CubeMX without any deleting functions in CubeIDE?For code added to the main file, it's clear to use /**User */ comment guidelines but, for functions, should i create another file or module for my functions?Thank you in advance,S.Tairk,

Hi there,I have a STM32F746G Discovery board on which I have developed an application. The application was running fine, there was some strange behaviour, probably some minor bugs, but it looked good. When I bought a new identical board and flashed the application, the display literally showed some random noise, like this:I flashed the examples from TouchGFX to see if it made a difference, but I got the same result. My old board is DK32F746G$U2, which works fine, but the new one is DK32F746G$CU4, which renders everything wrong. I found a STM post on this link: STM32F746G_Discovery touch screen buttons stop wor... - STMicroelectronics Community, that says there may be different display built-in:1. CU1 uses - HT043C2. CU2 uses - GJX043A6 -40D YI have no clue what the display is used for CU4 as I could not find any information about it. How do I solve this? Thanks for the help!!!

We are developing a wireless charger with additional wireless-to-USB gateway functionality. We have a design where we use the STWB2-HP as a wireless power transmitter - works fine most of the time. In parallel, we implemented an ESP32-S3 with BT and WiFi. We use a USB2 compatible USB-C connector.USB power is used for the whole system.CC lines are connected to the STWBC2-HP.Data lines are connected to the ESP32. On Windows and Linux machines, the data connection works as expected. The STWBC Studio interface reports USB-BC and USB-PD power modes at 5V, depending on the connected host devices. With a PD wall adapter, all power modes (PD: 5V, 9V, 20V) are available and charging works. However, when we connect our hardware to a MacOS machine (Macbook Pro M1 2021 or Mac mini), the device is visible for about 1 second and then disappears. The power to the USB port stays on and charging works as expected. Only the data lines are disabled on the USB host (manually resetting the ESP has no effec

Where can I find the source code for the firmware on the STEVAL-WLC38RX and STEVAL-WBC86TX boards?  I'd like to start there and make some modifications.Thanks.

I have the following function to write data to the FM24CL64 memory: void FM24CLXX_WriteData(uint16_t memAddr, uint8_t *data, uint16_t size) { uint8_t memAddrData[2] = { (uint8_t)(memAddr >> 8), (uint8_t)(memAddr & 0xFF) }; HAL_StatusTypeDef status = HAL_I2C_Mem_Write(&hi2c1, FM24CLXX_I2C_ADDR, memAddrData[0], I2C_MEMADD_SIZE_8BIT, data, size, 100); if (status != HAL_OK) { Error_Handler(); } }  Symptoms:The write operation fails, but the HAL_StatusTypeDef status returns a code that doesn't indicate exactly where the issue is.I have verified that the I2C address FM24CLXX_I2C_ADDR = 0xA0 is correct.The Error_Handler() function is being triggered, but I don't know exactly why.Possible Causes:There could be an issue with how the I2C command is sent.Maybe the address or size format isn't compatible with the memory or STM32 I2C configuration.Request:Anyone with experience in using STM32 with I2C and FM24CLXX memory, could you please help me identify what cou

I just unpacked NUCLEO64 C031C6 board and .. no code is working. Debugging I found all the code was stuck at SystemClock_Config / HAL_RCC_OscConfig.I checked and by default in the ioc file the HSE and LSE are set to "Crystal/Ceramic". For now I found a workaround - in the clock configuration I chose using the internal HSI, but I'd expect the boards to be working out of box with external clock source what is even declared on the board description (24 MHz or 48 MHz HSE)Later I found in the user manual (6.7 OSC clock sources):"HSE, which is the 8 MHz oscillator for the STM32 microcontroller. This clock is not implemented on the STM32 Nucleo-64 board" I have as well nucleo32-l432kc where the HSE seems to be present and working.I'd like to just confirm - is the HSE crystal really not there? Or did I miss something?Thank you for any insight

Hi,at the moment on the STM32U5G9 we have the SWD pins (SWDIO and SWCLK) set to DEBUG, but we would like to also use them as GPIO after programming. How do we switch them to GPIO at runtime? Thank you 

Hi ,I am not sure but my development board STM32H750B-DK may have some issues and I need some help to find what it may be .  As per the readme.txt (there is very less literature that I could find on this board) , I could dump the ext_mem boot bin into the Internal flash and I did not face any issue there. I am now trying to flash the IO toggle image onto the QSPI flash present on the development board and I always face the same error. I feel that there maybe a hardware issue on the board but I could be wrong. Your help is highly appreciated. I have attached the error image.  

Hello,I am using the BLE_p2pServer_ota example from the STM32Cube_FW_WBA_V1.4.1 firmware package.For testing purposes I would like to set different channels/frequencies for TX/RX (2402, 2440, 2480 ... MHz). Where can I find the corresponding functions for setting them?  

Hello,I have successfully implemented a Touchgfx based UI app using cubeMX and freertos on the STM32U599 chip. This is a basic application with multiple screens, a number of components all in ARGB2222. I am now in the process of porting my app from FreeRTOS to the zephyr platform. I am able to initialize touchgfx and start the process.Using gdb I verified the touch gfx process going through my first screen setup and invalidate it. But at some point in touchgfx::Application::draw(touchgfx::Rect&), a hard fault is produced.I have two theories on how this could be happening:1- Linker issues. At first zephyr was trying to allocate my UI elements where it saw fit. So I looked at the '.list' generated by cubeIDE to understand where my sections should be placed. Doing so I was able to put together the following linker sections and passed it to zephyr using cmake:SECTION_PROLOGUE(TouchGFX_Framebuffer, (NOLOAD),) { . = ALIGN(4); __TouchGFX_Framebuffer_start = .; KEEP(*("TouchGFX_Framebuf

Hello,I'm busy working on my first touchGFX project and I am using flex buttons instead of toggle buttons. I set the trigger to toggle and change the color of the button which works really well. The issue I am facing is that if I set a button to the off state when its default state in on and change screens the buttons will all reset to on when returning to the screen.I notice the same thing happens even with toggle buttons. Is there any way to save the state of the button when leaving the screen so that when I return it will still be in the correct state?Thanks in advance.

How would I be able to create a binary for this project or run it through CubeIDE? For some context I have taken this project from the FP-AI-VISION1_V3.1.0 pack, made some modifications, and would like to flash my H747i board with it. I can build the CM4 and CM7 files but when it comes to running the entire project or creating a binary for it I am at a loss. Thank you!

I am currently working with the VL6180X proximity sensor and would like to inquire about its long-term performance characteristics:      1. What is the expected Light/Luminous Depreciation time frame for the VL6180X's VCSEL source? Could you                provide any data regarding its lumen maintenance curve or L70/L50 specifications?     2.How does Light/Luminous Depreciation affect the sensor's performance over time?        Specifically:                 1. Does it primarily manifest as a reduction in return signal rate?                 2. Are there any observable changes in measurement accuracy?                 3. What are the typical indicators that Light/Luminous Depreciation has occurred?      3. Are there any recommended compensation strategi

I’m using a VL53L5CXV0DH/1 sensor in my current setup (see pictures). The goal is to detect a ball rolling between the sensor and the background. The red box is about 12cm apart.The settings is 4x4 for speed, i also noticed that 60 is not the highest scan frequency in code : status = vl53l5cx_set_ranging_frequency_hz(&dev,60);if i set 120 this works too, while scanning seems to be lot faster and just as accurate, why is 60 defined as maximum in the datasheet?However (even at 60), I often see target_status = 255 for 3-4 pads, without the ball passing and wonder why this happens. When this occurs, the distance information is apparently correct but the datasheets states that the distance readings become unreliable, and I want to ensure I get the most accurate and dependable measurements.When the ball passes i see 255 in even more status records.What could be causing this issue?Additionally, I’d appreciate any advice on settings or adjustments to improve detection, especially