Solved

Hello,I was trying to implement extended calibration for ADC1 on my STM32U575 according to RM0456 Rev 5.  I have a revision ID 0x3001 chip which should support extended calibration.  The chip would hang very badly (can no longer connect with debug probe!) after step 6 ("Set the LATCH_COEF bit").  I took a look at the HAL code in stm32u5xx_hal_adc_ex.c  and it is doing a few things differently:Using DMB instructions between setting CALINDEX and CALFACT and between setting CALFACT and setting LATCH_COEF.Preserving the low-order 8 bits of CALFACT when writing 0x03021100 to the register.When I changed my code to do those two things the ADC now completes calibration properly and doesn't hang my debug connection.It would be helpful if the RM could be updated accordingly!Thanks,TG

Dear ST Support Team,I am working with the STEVAL-ESC001V1 evaluation board and a drone motor listed at the following link:https://www.dys.hk/product/D2826.html RPS for power supply given directly to ESC power pins of 12V and 2A current.My objective is to run this motor using ST MC Workbench software version 6.4.1. I would like to confirm whether any additional hardware, such as an STM32 development board, is required in order to operate the motor with this setup.During system configuration in MC Workbench, I created a new project and selected STEVAL-ESC001V1 for the inverter section and Bull Running BR2804-1700KV for the motor section. However, when I later attempted to edit the project, the motor selection options displayed only two types of PMSM motors. Could you please clarify whether MC Workbench supports only PMSM motors? The motor I am using is a BLDC motor, as specified above.Additionally, I would like to inquire whether an example project for STEVAL-ESC001V1 is available

Hello,I'm using MEMS Studio to log data from a multi-sensor glasses platform for biomarker extraction research. My sensor configuration includes:ST1VAFE6AX (Accelerometer @ 240 Hz, Gyroscope @ 240 Hz, vAFE enabled)LIS2MDL (Magnetometer)LPS22DF (Pressure)STTS22H (Temperature)The CSV export includes a new_data column containing hex values (e.g., 0x08, 0x10, 0x18, 0x20, 0x400). I understand this is a bitmask indicating which sensor(s) have new data in each row, but I cannot find official documentation for the bit assignments.Through empirical analysis (checking which sensor columns actually change when each bit is set), I determined:Bit Mask Sensor CorrelationBit 30x08Accelerometer96.6%Bit 40x10Gyroscope96.6%Bit 50x20Magnetometer99.9%Bit 60x40Pressure—Bit 100x400vAFE—Questions:Is there official documentation for the new_data bitmask format in MEMS Studio CSV exports?Are these bit assignments consistent across different sensor configurations, or are they dynamically assigned based on which

Hello! I have a struggle to boot the isolation LRUN project from STM32Cube_FW_N6_V1.3.0/Projects/STM32N6570-DK/Templates/Template_Isolation_LRUN. 1. First i've performed the mass erase to remove the demo on the discovery board. 2. I've build and add the header to the binary with the Signing Tool for all three projects. Example below for FSBL. STM32_SigningTool_CLI -bin Template_Isolation_LRUN_FSBL.bin -nk -of 0x80000000 -t fsbl -o Template_Isolation_LRUN_FSBL-trusted.bin -hv 2.3 -dump Template_Isolation_LRUN_FSBL-trusted.bin3. I've Flashed the external memory in DEV mode with all three images:FSBL flashed to 0x7000 0000 SecApp flashed to 0x7010 0000NonSecApp flashed to 0x7018 00004. I've switched the board to Boot from ext. memory mode and pressed restart. The board doesn't boot. 5. I've loaded the FSBL project in DEV mode with debugger to internal RAM( 0x3418 0400 ) and it runs nicely. ---------------------------------------------

I am using a STM32G4 MCU and STM32CubeIDE. I want to synchronise two timers (TIM3 and TIM15) that are generating PWM signals so that they both start at the same time. TIM3 is set to 250 kHz and the PWM is modulated via DMA on channel 1.  The modulated signal is a 10 kHz sine wave.TIM15 is set to 10 kHz and the PWM is a simple 50% duty cycle.I need the timers to start together to ensure that the PW Modulated 10 kHz sine wave (TIM3) is synchronised to the 10 kHz PWM (TIM15).I thought it would be straight forward enough. I have configured TIM15 as master.  In CubeMX I have set Master/Slave Mode (MSM bit) to "Enable (Trigger delayed for master/slaves simultaneous start)" and Trigger Event Selection to "Enable (CNT_EN)".I have configured TIM3 as a slave.  In CubeMX I have set Slave Mode to "Trigger Mode" and Trigger Source to "ITR6" (per the reference manual).To the CubeIDE generated code I have added: /* USER CODE BEGIN 2 */ HAL_TIM_PWM_Start_DMA(&htim3,

Hello,starting from the example application of the OEMiRot boot project, I noticed that the NS application size is limited to 640kB in the flash_layout.h  (#define FLASH_NS_PARTITION_SIZE (0xA0000) /* 640 KB for NS partition */)Since there is 1MB avalaible in the slot, I would like to increase this size from 640kB to 896kB. A first naive change is just to change the define from 0xA0000 to 0xE0000 which leads to the state that the bootloader doesn't find a bootable image anymore.How do I set a larger non-secure application size to have a benefit of the 1MB flash slot? Best regards,Stefan

I am asking this question because I am a relatively new engineer working with STM32 and Cube IDE. When choosing the MCU to create a new project for my new board containing the STM32F401CCU6, I see that it is not listed and only STM32F401CEU6 appears. Can I create the project based on this model number and will everything work the same? I wanted to try it myself, but today has been a tough day, so I would appreciate your help with an answer tomorrow when I get to the office to save time.Thank you in advance.  

Hello, I have a question about the temperature calibration for the VL53L0X Time-of-Flight sensor.The UM2039 manual states the following:> [Temperature calibration] has only to be done before offset and cross-talk calibrations, after Reference SPADs  management and before the first ranging is performed.During assembly of our product, those calibration steps (SPADs, Temperature, Offset, XTalk) are performed in order.To account for possible temperature changes when the device is in use, we call both  `VL53L0X_PerformRefSPADManagement` and `VL53L0X_PerformRefCalibration` on device boot to ensure the sensor is ready for use for the current temperature.My question is if this would affect the offset and xtalk calibrations, since the docs state that temperature calibration must be perfomed before those. Or is that sequence merely to ensure the offset and xtalk calibrations are done with the correct temperature calibration.Thank you for your time.

Hello everyone, First of all I am kinda new in ARM (I never use), I am working on the STM32H745I-DISCO board (using the CM7 core) and I am facing a persistent issue with UART . No matter what I try, the RX Interrupt never triggers, and the code never enters the HAL_UART_RxCpltCallback. My Setup: Board: STM32H745I-DISCO IDE: STM32CubeIDE (Latest Version) Scenario: UART Loopback Test (Connecting TX to RX physically). Peripheral: USART6 (TX: PC6 / RX: PC7) on the Arduino Headers (D1/D0). Settings: 115200 baud, 8N1, Asynchronous. The Problem: -HAL_UART_Transmit works fine (signals observed). HAL_UART_Receive_IT returns HAL_OK. However, the HAL_UART_RxCpltCallback is never executed.  When checking SFRs in Debug mode: RXNE flag stays at 0. What I have verified so far (Step-by-Step): NVIC Settings: USART6 global interrupt is Enabled in CubeMX. Vector Table: USART6_IRQHandler exists in stm32h7xx_it.c and calls HAL_UART_IRQHandler. Initialization Order: I ensured that MX_USART6_

Dear ST, I am using Nano Edge AI Studio for Embedded ML teaching at university. Recently, I faced the problem of installing licenses on class computers reporting that “License has reached its activation limits”.I understand that Nano Edge Ai Studio is free but I cannot activate multiple computers in the classroom with my personal free license. Could you please explain how to solve the issue (activate 10 computers in the classroom).Regards,Žilvinas Nakutis

Dear STMicroelectronics Team,I am writing to strongly condemn the way power consumption values are presented in the STM32WB55 datasheet.When I choose a wireless SoC, I do so because of its wireless capabilities. If I only needed a microcontroller, I would simply buy an MCU from your STM32 families. The reason I selected WB55 was specifically for its BLE functionality. Therefore, the datasheet must provide power consumption values with BLE active, not just MCU Stop mode currents with BLE disabled.Presenting only the MCU’s low‑power figures while omitting the real BLE consumption is misleading and deceptive. It creates false expectations for developers and leads to serious disappointment in real‑world applications. This practice can only be described as fraudulent.I strongly denounce this approach. Wireless SoCs must be documented transparently, with accurate BLE advertising and connection current profiles. Competing vendors such as Nordic and Telink provide this clarity, and ST should d

NUCLEO WB55For an unknown reason I2C1 has just stopped working. The BLE & UART are working but the boards (I've tested on 2 identical boards) are no longer talking to the sensors via I2C.When I scope them up the traces for SCL & SDA are both flat lines (yes I checked the scope is working properly).Frustratingly, this all worked before xmas.Anyone any clue what could cause this?

In the UM2407 Rev 5 (Nucleo-H753ZI user manual) on page 29/54, section 7.6.6 there is a warning:USB Micro-AB connector (CN13) cannot power the Nucleo144 board. To avoid damaging the STM32H7, it is mandatory to power the Nucleo-144 before connecting a USB cable on CN13. Otherwise, there is a risk of current injection on STM32H7 I/Os. However, in an informal empirical test it seems that nothing got damaged when I connected CN13 to a PC/Laptop without powering the Nucleo. So, how big is this "Risk" really and what are potential consequences? And is this risk related to the Nucleo only, or would the same risk apply when integrating a STMH753ZI directly on a PCB. Can anybody provide more detailed information?Note: I do NOT want to power the Nucleo from CN13 but just leave the USB cable connected. Thank you and best regardsDiego 

Split from old thread Debug: "No source available for main()"This is not the same question.Little late to the party but I have the same issue kinda. I switched to other branch in our project and I had the very same result. Then I took all suggested steps and I get when I tried to debug:No source available for "__floatdisf() at 0x800216e" Besides after switching to that branch program compiles just fine but doesn't work. All of this is of some settings that remained in project and weren't covered in git commit, but it's hard to commit every single file in CubeIDE enviroment. All important files were covered like all code files and ioc etc. i always switch when Cube is not running because it also creates issues. Any ideas?

So far, in all my projects, the MCU has been powered via USB attached to computer. I would like to make a project in which the MCU is powered by a portable power supply. However, I don't know which equipment I need to use for this purpose. I have a power supply module from ELEGOO kit (ELEGOO Upgraded Electronics Fun Kit w/Power Supply Module, Jumper Wire, Precision Potentiometer, 830 tie-Points Breadboard for Arduino, STM32 : Amazon.com.au: Computers), which can output 5/3.3V electricity. Can I connect a powerbank to the supply module, and use the supply module to power the board, or should I look for other options? The board I use is stm32f407g-disc1, and the datasheet (DS8626_STM32F40xxx.book) says that the voltage should be in 1.8-3.6V range and the power of electrical current should be less than 240 mA (p79).

In iDE version 1.19, there was an STM32 Project creation feature, but it disappeared when I updated to 2.0.

Hello,we are seeing a systematic offset when using the internal temperature sensor of the STM32G031G8U6.Over the years we have tested ~50 SoCs (different production batches), and all devices show a very consistent temperature reading that is about 2–3 °C too high at room temperature compared to an external reference, higher temperatures weren't tested.Because of this, we are considering programming a temperature offset during flashing. Before doing so, we would like to better understand whether a single-point offset calibration is sufficient, or if the internal slope accuracy is not reliable enough, requiring a full two-point calibration.Example:If the MCU reports 24 °C but the real temperature is 21 °C, can we simply apply a +3 °C offset globally?Or is the internal temperature slope not guaranteed well enough, meaning that a two-point calibration is required?More specifically, regarding the factory calibration values on STM32G0:TS_CAL1:ADC raw value measured at 30 °CTolerance: ±5

 Hello ST Community,I am working with the STM32N6570-DK and the USBX Ux_Device_Video example fromSTM32Cube_FW_N6_V1.3.0\Projects\STM32N6570-DK\Applications\USBX\Ux_Device_Video.I followed the README instructions exactly:Built FSBL and Ux_Device_Video projects successfully in STM32CubeIDEGenerated FSBL.bin and Ux_Device_Video.binSigned both binaries using STM32_SigningTool_CLIProgrammed:FSBL-trusted.bin at 0x70000000 (external flash)Ux_Device_Video-trusted.bin at 0x70100000 (external flash)Set BOOT0 and BOOT1 to boot from external flash and reset the boardHowever, the application does not run as expected. When the board is connected to a Windows PC, the Windows Camera application fails with the error:   Can't start your camera0xA00F4241 <CameraSwitchFailed> (0xC00DABE7)From my understanding, the Ux_Device_Video example should enumerate as a USB UVC camera and stream video to the Windows Camera app. Since the camera app fails, it seems the firmware may not be executi

Hi everyone,I’m experiencing unexpected behavior while testing 9-bit SPI on an STM32, observed with a logic analyzer. The issue only occurs when the MOSI line is physically connected to the slave.Observations::keycap_1: MOSI not connectedCS and SCLK are correctMOSI stays highSPI decoder shows 0x1FF Expected behavior for a floating MOSI line:keycap_2: MOSI connected to the slaveMOSI data becomes correctBut a very brief rising edge (glitch) appears on CS during data transmissionCS immediately returns active → causes unintended slave deselectionResult: data loss during the SPI frameAdditional info:STM32 model: stm32u5g9j-dk2SPI mode: 9-bit, masterSCLK frequency: 10 MHzIs this a known issue with 9-bit SPI on STM32?Should I add a pull-up/pull-down on CS or MOSI?Any other suggestions to avoid this glitch?Attached are screenshots showing the behavior.Thanks in advance for your help!MOSI connectedMOSI not connected

Hi Team, Urgent help required!! Today I have update my CubeIDE to the latest version, before the update i have had several projects saved, but none of it is launching in CubeIDE, when i click on the .IOC file from CubeIDE it opens on CubeMX and when i clock on generate code it says "The Code is successfully generated under :C:/Users/S****** H******/STM32CubeIDE/workspace_1.16.0/Door Module Testing" and as soon as i click on Open Project it goes to CubeIDE and shows main.c file. When I try to open the .IOC in CubeIDE it redirects to CubeMX again, a never ending loop has formed. Attaching screenshots for your review. Someone from ST Electronics please look into my issue and give me a quick fix or a workaround. Regards, Prateek

Im trying to run SYSCLK from LSI on a STM32C011. But it appears as if the MCU is not running. I cant see anything in the datasheet that says the clock cant be used and it can be routed fine in the clock configurator. Am I missing something in the datasheet or does the HAL not support it?

Hello fellow readers,##Disclaimer##I am using a Nucleo Board, the Nucleo H7S3L8, and HAL_ERROR ist laughing me since 2 days in my face# I think you, dear reader, have heard about the SWR-Bit, which vanishes out as soon the software has restarted succesfully, everything seems perfect and you have finally the feeling you found the solution to world piece.But I am currently at the brink of insanity, because this little ******* ***** ** **** wont clear itself after I forced the reset. What do I mean specifically?HAL_StatusTypeDef HAL_ETH_Init(ETH_HandleTypeDef *heth) { uint32_t tickstart; if (heth == NULL) { return HAL_ERROR; } if (heth->gState == HAL_ETH_STATE_RESET) { heth->gState = HAL_ETH_STATE_BUSY; #if (USE_HAL_ETH_REGISTER_CALLBACKS == 1) ETH_InitCallbacksToDefault(heth); if (heth->MspInitCallback == NULL) { heth->MspInitCallback = HAL_ETH_MspInit; } /* Init the low level hardware */ heth->MspInitCallback(heth); #else /* Init the low lev

Hi,I can't find a way to select in MEMS Studio which MLC filters are passed FIFO and how to enalbe MLC result in FIFO.Configuration created by MEMS studio enabled MLC_FILTER_FEATURE_FIFO_EN in EMB_FUNC_FIFO_EN so I see selected MLC features in FIFO but nothing more - no filters, no results.I manually enabled MLC_FIFO_EN but MLC results didn't appear in FIFO.I tried to enable filters manually in mlc.json by adding "fifo": "true" to filters in json file, but it didn't help.  I've attached MLC files. Best regardsTomasz 

Hi I am using Nucleo H753zi board, can I use X-CUBE-MEMSMIC1 expansion for sound source localization.

Hello ST Community, I am seeking assistance with a project generation issue using STM32 Motor Control SDK (v6.x) and the EVLSPIN32G0A1 evaluation board. The Problem: Even though I explicitly select the EVLSPIN32G0A1 board (which features the STSPIN32G0A1 / STM32G071 core) in the Motor Control Workbench, the generated .ioc file and STM32CubeIDE project target the STM32G031C8Tx instead. Consequences: Debugger Error: When attempting to flash the code, the ST-LINK GDB server returns: "Target no device found" or a Device ID mismatch because it is looking for a G031 but finding a G071 core. Configuration Mismatches: The clock tree and memory boundaries in the .ioc are being set for the G031 (64KB Flash) instead of the STSPIN32G0 (128KB Flash). What I have tried: Creating a new project in MC Workbench and selecting the board from the "Boards" tab. Configuring