Solved

Hello,I am evaluating cryptographic performance for a secure boot using a NUCLEO-H533RE board and the OEMiRoT example from STM32CubeH5.I compared two AES-128-CTR implementations:Software: mbedtls_aes_crypt_ctr(). Hardware-backed: bootutil_aes_ctr_encrypt() using SAES.The mean encryption times are:Input size Software SAES-backed implementation 32 bytes 10.55 µs 29.46 µs 256 bytes 76.70 µs 222.88 µs 1024 bytes 303.50 µs 886.02 µs  For an academic comparison, is it accurate to describe this result as “software AES-CTR versus SAES ECB with software CTR and driver protection overhead”? Thank you!

Hello,Any idea how to get the price history for the part “STM32L053C8T6” ? (specifically on Sept06 th)I have a quotation conflict with my supplierThanksMiki

Hello,I am working on a requirement involving XIP (Execute-In-Place) from external QSPI flash on the STM32U5G9 and am encountering an issue executing the application from external flash.I have developed a working external flash loader for my QSPI memory and successfully programmed a simple GPIO toggle application into external flash.In the bootloader, I initialize the QSPI interface, configure the flash in memory-mapped mode, and then jump to the application located at 0xA0000000.Using the debugger, I can confirm that execution reaches the application's Reset_Handler at 0xA00002B4. However, when executing the very first assembly instruction, the processor enters HardFault_Handler at 0xA0000458.The fault status registers indicate: CFSR = 0x00000001 (Instruction Access Violation) HFSR = 0x40000000 (Forced HardFault) MPU is disabled VTOR = 0xA0000000 I have also verified that the application vector table contains valid stack-pointer and reset-handler addresses, and that the external

I am reading through AN5464 and UM1052 looking through the PID tuning sections.https://www.st.com/resource/en/application_note/an5464-position-control-of-a-threephase-permanent-magnet-motor-using-xcubemcsdk-or-xcubemcsdkful-stmicroelectronics.pdfhttps://www.st.com/resource/en/user_manual/um1052-stm32f-pmsm-singledual-foc-sdk-v43-stmicroelectronics.pdfTypically one would tune the inner loop PI for Torque and Flux then go onto tune the outer loop position PID. The calculated position control PID parameters for the project by default are completely unstable. I am looking for any documentation around the recommended method of tuning the inner loops as in both the Flux and Torque PI parameters. Is there anything along these lines available?

Hi, does VL53L4ED support a programmable FoV? I am looking for a ToF sensor with extended temperature range, but require a narrower FoV and range up to ~2000mm.Thanks!-BH

Hi all, I have designed a target board that operates at 2.5 to 3V. Is the STLINK-V2 SWDIO and SWCLK 3V3?Will it damage my board?Is the STLINK VAPP pin an input or an output i.e. does it sense my target supply voltage and level-shift accordingly?If so, will it be fairly high impedance i.e. not draw too much current from my target?The wording in the STLINK doc is unclear: 

Hi HelloI would like to confirm whether the LDO regulator is available on the STM32H725REV6 with VFQFPN68 encapsulation. The documentation is ambiguous, as AN5419 says the following in item 2.1.6:The low drop out (LDO) voltage regulator is always enabled after Power-on reset. If it is disabled, it remainsdisabled even after any reset source except for a Power-on reset. For system supply configuration where thisregulator is not needed, it will be switched OFF by the user software after system start-up. On some packages,the LDO power supply is available on external VDDLDO pins. When it is not available on an external pin, VDDLDOis connected internally to VDD.Can you clarify?

I believe I’ve encountered an Issue with the current version of the STM32 HAL2 and wanted to raise an issue, but I’m not sure where best to raise the issue.The one of the new features in the new HAL2 hash is that HAL_HASH_Update can handle input sizes that don’t perfectly line up with the block size, using HASH_SaveRemainingBytes to save any excess bytes at the end of a call and then calling HASH_AppendLastIncompleteWord at the next call to write those excess bytes to peripheral along with using some bytes from the new buffer to bulk it up to 4. This means that I can write something like: (where the buffer is 163 bytes long)HAL_HASH_Update(&hhash, &u8InputBuffer[0], 10,0xFFFF);HAL_HASH_Update(&hhash, &u8InputBuffer[10], 10,0xFFFF);HAL_HASH_Update(&hhash, &u8InputBuffer[20], 1,0xFFFF);HAL_HASH_Update(&hhash, &u8InputBuffer[21], 62,0xFFFF);HAL_HASH_Update(&hhash, &u8InputBuffer[83], 7,0xFFFF);HAL_HASH_Update(&hhash, &u8InputBuffer[90], 73,0

Hello, community,I try to  develop power supply  based on VIPER35L, but  it  runs only in burst mode never reaching steady regulation. I have made almost a copy  of  STEVAL-ISA171V1, except of transformer, which was made by myself. According application note  AN4812.  What might be the culprit?  Are  transformer data  correct in it ?  I mean ratio  8:1:1. Isn’t  it too  small to power  self? Several oscilloscope  snapshots are taken.  Any advice appreciated. Bnx  

Error MessageDebugger Settingsi am trying to upload the firmware into the co-processor of the stm32mp157fdk-2 board and struggling with this error I shared the error details and my debug configurations In the drop down menu of the Serial Port nothing is over there but I can able to use putty and can able to view the booting messages, and I am not trying to upload the code while connected with the putty, I also tried the engineering mode tooAnd now I am on the windows, is this windows specific error or what? cause when I was trying to upload using the linux everything was running very fine. Now I create elf file everytime and scp into the board then manually start the co processor, I don’t want to do this again and again 

Hi,Can we use a ferrite bead with STM8S MCU for VCC pin along with the recommended decoupling capacitors at the VCC pin. Thanks in advance.

Heyho,preparing the BOM for the next PCB version with the STM32H733ZGT (LQFP-144, 1024kB).And finding that these are not available at our standard webshops. :-(Started CubeMX to look for 100% pin compatible MCUs, and lo and behold: none found!But I’m pretty sure that the following types are at least pin-compatible and mostly function-compatible (some only missing stuff like hardware encryption):STM32H723ZGT, STM32H725ZGT, STM32H730ZGT, STM32H735ZGTAm I correct, or are these not pin-compatible - maybe some internal LDO / SMPS stuff or some peripheral missing that I oversaw? I’m using the following peripherals:SAI1, SAI4, I2S3, Ethernet + PTP, I2C1, I2C4, 2x OctoSPI, DAC, ADC, UART3, SDMMC2, timers, … Oh my, what a project… there’s no way I’m gonna switch to some completely different MCU. Thanks in advance!

Hi there!I'd like to use the STEVAL-CAM-M01 P-board to evaluate the VD55G0 BrightSense image sensor with the Discovery kit for the STM32N6 MCU (STM32N6570-DK). The discovery kit does have a camera connector, however, looking at the schematics it seems that the polarity of the CSI data and clock lines is swapped compared to the P-board. Everything else looks fine.Is it possible to use the P-Board with the Discovery kit without destroying either of the two? ST's marketing material (slide 33) seems to suggest it is possible but the schematics are unclear. Note that a similar question has been asked in the MCU forum, but it was suggested to ask in this forum to be sure. Also note that I'm not asking about software driver support here, only hardware compatibility.Camera connector on STM32N6 discovery kit: Connector on P-board:Thanks a lot!Michael

How can I enable HSE on STM32U375K (32pin) in Cube MX?The option to enable HSE does not seem to be available in CubeMX. However, the option to select the HSE startup time is enabled.What am I missing?Does the STM32U375K support HSE? I couldn't find anything in RM0487 that indicates otherwise.   

I cannot get the VCP function of ST-LINK v3 mini working.Windows sees the com port and can open itConnected TX output of UART to pin 14 of ST-LINK 3 mini, but nothing is received on the PC side.Connected some other serial TTL-USB adapter (set to 3.3V), and it works properly.​However, the serial TTL-USB adapter has a ground connection and ST-LINK's VCP has common ground with other functions.The debugger function works properly.Is the TX level of VCP 3.3 or 5 V? Does the VCP function work for anyone?Thanks,-- pa

I need to view all Cortex-M7 debug and trace/debug subsystem registers during debugging—similar to how peripherals like DAV, RCC, and GPIO are displayed—but they do not appear in the SFRs list; specifically, I need to view the ITM, ETM, WDT, and SWO registers. 

What is LPS22HH conversion time in OneShot mode? I do not use interrupt line and do not want to poll the device until ready. The datasheet doesn’t specify it, it specifies available ODR only.

Hello everyone,I measure a voltage on a STM32L496 using the internal ADC and found the following issue:Setup:The voltage is scaled down via a high-impedance voltage divider (2 x 470kOhm). To avoid distortion by sampling, the voltage divider has a 100nF capacitor. Thus, the capacitive load while sampling is low and the breakdown is 1/20000 → i.e. way lower than the ADC’s resolution. So I do not have to care about source impedance limitations as described in the datasheet (Maximum ADC RAIN).Other data:VREF=VDDA=3.3V (stable) Voltage range of ADC input signal: 0 - 3V (never >3.3V)Effect:I experience a large voltage breakdown when I configure the ADC, via CubeMX generated function MX_ADC3_Init (same happens when I use ADC1). I found, that within MX_ADC3_Init the channel gets configured and the ADC sequencer register ADC_SQR1 is set (I only sample that one channel with the high-impedance voltage divider). As soon as ADC_SQR1 is set, the voltage breaks down, from anything >2.5V to appr

Hello STMicroelectronics Community,We are evaluating the following STM32 microcontrollers for long-term use in our drone flight controller development: STM32G431 STM32G431KBU6 STM32G474VET6 STM32H743VIT6 STM32H723VGT6 We would like to understand the long-term market availability and product lifecycle commitment for these MCUs.Could you please clarify the following points? Product Longevity: For how many years will these MCUs remain available for purchase and production? Lifecycle Status: Are these models active, recommended for new designs, or approaching end-of-life (EOL)? Long-Term Supply: Does STMicroelectronics provide a guaranteed supply period or product longevity commitment for these specific MCUs? EOL Notification: If any model is planned for discontinuation, how much advance notice will be provided? Replacement & Migration: If a model becomes obsolete, will a pin-compatible or functionally compatible replacement be available? Our concern is to avoid selecti

Hi, Good DayI am Mike, I work for Lenovo Japan, I am currently doing a POC for ML enabled embedded application using STM32N6570-DK. I just got stuck after debugging incremental update to my firmware (add ThreadX). Background / PretextWith the help of https://community.st.com/stm32cubeide-mcus-28/stm32n6570-dk-debug-keeps-failing-error-32-load-failed-not-sure-if-i-should-debug-fsbl-or-appli-168613?tid=168613&fid=28, and STMicro Template_Isolation_XIP project, I was able to setup a project that runs debug from FBLS to AppS to AppNS. I plan to build my target firmware bit by bit, and so I was able to add UART1 for debug log and it was working at that point.My next step was to add ThreadX, so I configured .ioc to add ThreadX and TIM6 as source clock to SYS_NS, then I forgot to turn on the RTOS awareness to ThreadX->CoreM55 and I begun to fail connecting when hitting debug.I kept a copy of basic Template_Isolation_XIP that was perfectly working, and event switching to that project, t

Hello,I am using:- NUCLEO-F401RE- X-NUCLEO-53L4A1- VL53L4CD_GUI (Rev 1.0.17549)The VL53L4CD sensor is working correctly with the X-CUBE-TOF1 example(53L4A1_SimpleRanging). I can read distance measurements through theST-Link Virtual COM Port.However, VL53L4CD_GUI cannot detect the sensor.When the GUI starts, it shows:"Failed To Connect to Nucleo Board: Com Port Not Detected"After pressing "Flash FW", it changes to:"COM9 Connected: Sensor Not Detected.Please ensure sensor connected then Press Black Reset Button on the Nucleo."Additional information:- ST-LINK is detected correctly.- STLink Virtual COM Port (COM9) is available.- STM32CubeProgrammer can connect successfully.- The VL53L4CD sensor is confirmed to be working with the  53L4A1_SimpleRanging example.- The GUI remains in OFFLINE MODE and API Version shows TBC.Has anyone successfully used VL53L4CD_GUI withNUCLEO-F401RE + X-NUCLEO-53L4A1?Is there a specific firmware required for the GUI?Thank you.

STM32CubeMX 6.18.1 + STM32Cube FW_G4 1.28.3Target: STSPIN32G4 / TIM1Asymmetrical Dead Time enabledCubeMX GUI:Dead Time = 50 Falling Dead Time = 50 Asymmetrical Dead Time = EnableGenerated LL code:C  TIM_BDTRInitStruct.DeadTime = 50;No write to TIM1->DTR2 is generated.Runtime observation:DTAE = 1 DTGF = 0Therefore CubeMX appears to generate DTAE but not DTGF.

Hi, Folks.I’m using a board with NUN code ending in $CR1, C260400252, MB...Q-C02 if that includes useful rev info.I started powering this ST Nucleo board with +12 from a bench supply, limited at 600 mA, into CN3 pin 24 with ground on pin 20 (19,20,22 all ground) and that was being regulated down to +5 by U25 just fine.  So I let the board see the +5 by inserting CN9:5-6 jumper.With nothing plugged in but power, LD1 was on (green), LD9 red on and green flashing, LD4 red on faintly, LD5 flashing red.  All this as expected except the state of LD9 which appeared to be due to 3V3_STLK existing (regulated from 5V) but no USB connection.  I checked and recorded all the voltages on CN2; everything looked reasonable except pins 9 and 10 pertaining to the internal SMPS which is free floating, because by default VDD1V8 is not being generated (low nonzero voltage at TP14).I was about to plug the cable I’d made into CN1 when I noticed LD5 had stopped flashing and the current being drawn from my 12V

Hi everyone,We are facing an issue with the RTC on our custom hardware based on the STM32N655X0 MCU and would appreciate any suggestions to help us identify the root cause.1. Project OverviewWe have configured the RTC in our application, and maintaining the correct time across power cycles is an important project requirement.Our firmware is stored in external flash. During development, we use J-Link for programming, and we have also implemented firmware flashing through USB using an FSBL with DFU support.Both flashing methods work successfully. However, we have observed unexpected RTC behaviour after flashing and subsequent power cycles.2. Issue DescriptionAfter flashing the firmware, if we remove the main supply (VDD) and power the board back on after a few minutes, the RTC does not account for the elapsed time correctly.For example, if flashing completes at 12:25 PM and we power off the board immediately, then power it back on at 12:30 PM, the RTC does not reflect the five-minute int

Hi, I'm designing the STUSB4500QTR into a board that can run from USB-C, PoE or a DC jack. VDD is on VBUS as usual, and I'd like to run VSYS (pin 22) from our 3.3 V supply instead of grounding it, so the part can't hold the shared I2C bus low when the board is powered from PoE or the jack and USB-C isn't plugged in. DS12499 Rev 8 seems to say two different things:- Section 6.1.1 (p. 23): "there is an interest in using VDD pin only to supply the STUSB4500. First of all, this is mandatory to enable VBUS input voltage monitoring."- Table 22 (p. 29): the VTHUSB (VBUS disconnection threshold) and VTH0V (vSafe0V threshold) rows give the condition "VSYS = 3.0 to 5.5 V". The table header says "Unless otherwise specified: VDD = 5 V, TA = 25 °C", so I can't tell whether those rows were measured with VSYS only, or with VDD and VSYS both present. My questions:1. With VDD on VBUS and VSYS at 3.3 V both present, does the STUSB4500 still monitor VBUS (VBUS_VS_DISCH, detach detection, and discharge at