Solved

Hello everyone,    Recently I tried to use VL53L3CX to accomplish a distance calculating project. When referencing the document of VL53L3CX I found a little strange about the distance parameter.        For example, the note of ranging capabilities table in the datasheet DS13204, shows that "The ranging distances reported are the ones reported by the driver by the parameter called RangeMilliMeter". While in the application note AN5561, it shows that "The ranging distances in the table below are those reported by the driver by the parameter called RangeMeanMilliMeter."        What I confused is: inside the API(VL53L3CX_BareDriver_1.2.10), I could not find the driver parameter named "RangeMeanMilliMeter".While "RangeMilliMeter" could be found in the structure VL53L3_RangingMeasurementData_t. So if there has any difference between these two parameters? If yes, how to use the parameter RangeMilliMeter and what's its definition

Hi ST TeamI have a question about the TDA7266D13TR product.Checking the TDA7266D13TR datasheet gives the specifications for the TDA7266D and lists the operating temperature as 0°C to 70°C.The temperature specification I need is -20~85°C or higher.Please let me know if there are other options based on temperature.

I want to collect data wirelessly using the SensorTilebox.PRO and an STEVAL-MKI240KA (LSM6DSV32X) connected via the DIL24 socket. When I flash the DATALOG2_Release binary, I can see the onboard sensors using the ST BLE Sensor app, but not the external IMU. When I flash the MEMS Studio datalog extended firmware, I can log data from the external IMU but the device must be connected to a computer using a USB cable. Are there any pre-existing solutions allowing for datalogging (either through BLE connection or automatically on startup) with data from the external IMU, or does this functionality require directly modifying and flashing custom firmware?

Currently, I am working on an STM32L432 microcontroller, emitting a 20 kHz sine wave. The code is relatively simple, although I am getting a slightly different frequency. I have been looking for solutions and found an embedded software package called RC-CALIB as a relatively cheap solution to this.However, I cannot load the package on my CUBE IDE, even though the software was downloaded directly from the STM website. The latest version is from 2015.Thanks for your time.

Hi, can anybody tell me what type of diode I see here?Marking (see photo) is:ST      6LEZ 904 Board are used for recuperator motor control. Thanks

Hello,I have a couple of diodes that needs replacing, but I can't decode the markings. Is there a reference manual or an easy way to find the right diode?The markings are:ST-logoT01C029Can anyone help?Thanks! Elco 

Hi everyone can anyone help me initialize LTDC driver and LCD screen. I'm using the STM32F7508-DK board and I don't know what I need to configure in STM32CubeMX?

Hello, We have purchased the following boards recommended by STM in order to work on UCPD Source and Sink applications: 1. Two NUCLEO-G071RB boards 2. One X-NUCLEO-SRC1M1 3. One X-NUCLEO-SNK1M1 We downloaded the repository of board and imported the following default examples from its pack: X-CUBE-TCPP (4.1.0) : 1. SRC1M1_Source 2. SNK1M1_Sink But while logging the traces, we observe that Explicit Contract is not negotiated. I am sharing the traces from STM UCPD Monitor tool Ver 1.3.0 and also the test set-up. Please suggest what else needs to be done in order to get the set-up working as desired. With regard, Sudarshan Chaudhary

 /* ============= Copyright (c) 2023, STMicroelectronics All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the copyright holders nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. *THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.

Hallo, I am saving the log files of the chart in the CUBEMonitor software. I read certain values from the MCU through Cube Monitor and save them as .CSV. However I've noticed that the first file I save after opening the software does start from 0 seconds. In case I stop the data acquisition and clear the chart and start it again. A new log file is created with advanced time i.e. although the chart does show the time scale to be from 0 seconds. This problem doesn't occur if I restart the software, but it is tedious everytime to restart the software. Is there a way I can reset the time for every acquisition made? Thanks

Dears.I am following the guide for the matter part of the stm32 wiki. I am requesting help because an error occurred in the 1.2.2.4 Matter code generation chapter.https://wiki.st.com/stm32mcu/wiki/Connectivity:Matter_develop_and_prototype#Matter_code_generationI was able to successfully convert the .zap file to create a .matter file, but I failed to create the two files that contain the callback definitions.The error message is as follows, and I ran it on Windows.I look forward to your kind help. 

After testing trying to write a byte to Flash I seemed to have bricked board.  I thought board just went out, so I bought another one, programmed it and now that board is broken too.  I commented code out, tried 3rd board and it works fine.Here is the code I tried  uint32_t Flash_Address = 0x80FFF00; HAL_FLASH_Unlock(); FLASH_Erase_Sector(11, FLASH_VOLTAGE_RANGE_2); // Use appropriate sector number and voltage range HAL_FLASH_Program(FLASH_TYPEPROGRAM_BYTE, Flash_Address, 0xAA); HAL_FLASH_Lock();  The error I get now is:Target not halted after reset. Force haltFailed to halt targetTarget not halted Error in initializing ST-LINK device.Reason: Target not halted. Error in final launch sequence: Failed to execute MI command:target remote localhost:61234 Error message from debugger back end:localhost:61234: Connection timed out.Failed to execute MI command:target remote localhost:61234 Error message from debugger back end:localhost:61

Hello,First I want to clarify that STM32CubeProgrammer is a very cool and useful software.The purpose of my question is that in my company we need to integrate a "Firmware Flasher" into one of our Software products since we are not going to indicate our customers to download, install, and use STM32CubeProgrammer to update their device's firmware.I was wondering if there is a sample project or code that uses libusb (preferably in C or C++), that I can use as a reference to develop a firmware flasher. I say ideally in C and C++ but if it is not in any of these languages that is ok. I can just translate it from whatever to C++ using ChatGPT.Thanks!

I have two projects one was created some time ago with STM32CubeMX V6.10.1 and it shows me having 'blue' Enable CSS button for the LS mux the other is created with STM32CubeMX V6.12.1 (using the same exact part) YET it is greyed out.  How do I change this or what am I missing that keeps me from selecting the LSE on this project?  (See clock config pictures below and notice how the one allows me to select many of the fields and the other does not)  

Hello!I am running the UART_Printf example on my Nucleo and the output to USART3 (default) works fine, but when I change the output to USART2 or USART6, it doesn't send data.

We have new boards with STM32L433RCT6 as MCU and only 30% of boards can program with STM32CubeProgrammer. Other boards just cannot connect to ST-LINK. I have tried these:1. Use "under reset" mode, not working2. Use JTAG signals. The good board can be connected and the bad one still cannot.3. Use UART bootloader with BOOT0 pull up. The good board can be connected and the bad one still cannot. I have checked every pin of STM32L433RCT6, and found there is a 2Hz square wave on PB8, I disconnected external connection to PB8, and the square wave still there. If I press reset button, it will go to low. Is this normal?Can anyone help me? I really appreciate any help. Thank you!  

Hello,SDRAMs are available in different speed option -5, -6 or -7. IMHO this specifies the max. SDRAM clock at CAS=3, but SDRAM can configured via CAS parameter to be used at a lower clock frequency.Alliance Memory -7 for example can be configured CAS=3, 2 and 1, ISSI only with CAS=3 and2.The lower the CAS value the lower the max. clock frequency, here for the -7 chip at CL3=133, CL2=100 and CL3=50MHz and the higher the access time.According to the H7 datasheet, the max. FMC Clock is 100MHz. Regarding Alliance Memory, I would expect to configure CL=2 for 10ns clock.The STM32H753_EVAL2 is equipped with ISSI speed option -6 and is configured CAS=2. IMHO it should be no problem to run a SRAM at a lower clock but regarding SDRAM I am unsure because of the reduced access time of 5.4ns compared to the 6ns at speed option -6 with CAS=2. So I wonder if -7/CAS=2 would be also a valid option for running the FMC at 100MHz.Regarding the ISSI read timing herethe shorter the access time th

Hi,I got an issue where I can no longer activate SWV Viewer option inside debug configuration for my NUCLEO-U083RC board. The SWV checkbox is greyed out. Whether I create a new project or load an existing one, the SWV option is greyed out and can no longer be selected. Anyone got an idea what is going on?Also I had some issues with ITM_SendChar as it would not compile. Debug Trace Asynchronous Sw is active. On Nucleo board I assume SWO is connected. Cube IDE 1.17.0.STM32U0 V1.2 package. 

Hey there!Can we allocate the USB classes dynamically?Like, first we Initialize the USB Device stack,  just register the CDC class and add its interface and start the USB Device Core (which pulls up the D+ line)This we need to do (atleast registering one class) for Host (PC) to recognize our device as USB Composite device with some functionality (Com port)Then, when USB is inserted, I'll add a 5s delay and then register another class., let's say USB MSC and register its storage. Will it work? If yes, can anyone say the flow of coding?I'm using classic stm32 usb library for STM32U0 series MCUCurrently I'm doing like this:-> In main.cbool isUsbInterrupt = false;int main(void){/* USER CODE BEGIN 1 *//* USER CODE END 1 *//* MCU Configuration--------------------------------------------------------*//* Reset of all peripherals, Initializes the Flash interface and the Systick. */HAL_Init();/* USER CODE BEGIN Init *//* USER CODE END Init *//* Configure the system clock */SystemClock_Co

Anybody has a contact with STM s site in Catane ( Sicilia)?Thank you in avance !

I have a working project that simply writes to a a file on an SD card (Using STM32H7B3I-DK, Not Using RTOS).When I add it to a touchgfx project, f_mount() and f_open() return NO_FILE_SYSTEM. This happens even after f_mkfs() returns FR_OK. I have the following parameters:Freertos - task : stack 512 (words)  Priority : osPriorityRealtimeProject manage - linker settings Minimum Heap Size : 0x1000Project manage - linker settings Maximum Heap Size  : 0x1000FATFS - SDMMC instance : SDMMC1 Use DMA template - EnabledSDMMC1 - Use clock divide factor : 2There is no DMA Settings tab in SDMMC1, is this an issue?EDIT: I have tried it with just RTOS and FATFS and It works... The issue occurs when touchgfx is in the project

Yesterday I updated CubeIDE to 1.17.0. Everything seems to work except code generation.When I open my projectname.ioc file, it asks me to migrate or continue. Since I was updating anyway, I chose "migrate". When I then made changes and saved, a dialog popped up for half a second and closed and no code was changed. When reverted my .ioc file (in git) and tried again choosing "continue" this time, something was downloaded and unzipped in the background and then code generation worked like it used to.

I am using the above subject Nucleo.  I create a project and let STM32CubeIDE V 1.16.1 create a default project.  I make NO changes to this.  I close the .ioc and open main and add the following code (seen by Red Bars).  I build and load to target.  I place a breakpoint on the HAL_FLASHEx_ERASE function and when I go to step over this function I get a hard fault interrupt.  I step into code and the following line MODIFY_REG(FLASH->CR, FLASH_CR_PNB, ((Page << FLASH_CR_PNB_Pos) | FLASH_CR_PER | FLASH_CR_STRT));creates the hard fault.  Can someone please tell me what I am doing wrong here?....The target address has been verified to be readable via STM32CubeProgrammer so I know that it is not out of memory space. 

Hello everyoneI use an ESP32 to start a firmware update. The bootloader has been started, the esp32 writes block by block. In the end, I use the Go Commad from Bootloader Command Sets to jump into the application. My sequence.1. set BOOT0 Pin back to low2. esp32 sends 0x21 and 0xDE3. receive 0x794. then esp32  sends 0x8000000 + 08(Checksum)5. bootloader acknowledges it with 0x79but the new firmware won't start. Is there a suggestion why this is the case ? When I press the reset button the firmware will be started, but I don't want any hardware solution

I'm trying to setup a pin configuration so that I can start making a PCB. I want to use two NAND flash ICs connected to the STM32F415ZGTx using the FSMC, setup in a way that there is a redundant backup of data and logs in the event of a failure. When I go to configure both, it seems that they both are using the same NWAIT pin so I am not sure whether I should continue to use this same pin for both chips or if I should switch to using INT2 and INT3.  I also have PSRAM in the configuration which also seem to be using the NWAIT pin (PD6).Sorry in advance if this is a dumb question :) - first time using STM32CUBEMX/IDE so I am pretty new to configuring pinouts.  Mostly just used prebuilt boards but I wanted to learn how to work with the platform.