Product forums

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

I have a project which could use both OCTOSPI RAM and Flash but I also need an OCTO or Quad SPI port for a high speed ADC.It is unclear whether OCTOSPIM_Px_NCS1,2 can be configured to allow the memory to share one OCTOSPI portand, if so, how to do it.  It is entirely possible that I am missing something but I would appreciate input on the topic.Thanks. 

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: 

New question split from this post.HiThank you for your response. Unfortunately, our PCB is already in the prototype phase and we need to find a solution to power up the board for at least some basic testing.Then, on STM32H725REV6, are both Direct SMPS and Bypass (external VCORE on VCAP, VDDSMPS tied to VSS, PWR_EXTERNAL_SOURCE_SUPPLY) officially supported supply configurations?BRGilberto

I am trying to configure IEEE 802.15.4 packet sniffing on a NUCLEO-WB55 using STM32CubeMonitor-RF and Wireshark.I flashed the following firmware: Wireless coprocessor (M0+): stm32wb5x_Mac_802_15_4_fw.bin from STM32Cube_FW_WB_V1.24.0 Application (M4): Mac_802_15_4_Sniffer_Nucleo.bin from STM32CubeMonitor-RF IssueThe sniffer is detected successfully as a USB Virtual COM Port, and Wireshark recognizes it as an STM32CubeMonitor-RF 802.15.4 sniffer.However, no packets are captured, even when transmitting IEEE 802.15.4 frames from another STM32WB board.Troubleshooting Performed Tested both USB and ST-LINK/SWD connections. Verified USB device and serial port detection. Verified Python, PySerial, and Wireshark compatibility. Confirmed Wireshark recognizes the sniffer interface through extcap. Tested direct capture using stm32cubeMonRf_sniffer.py. Tested capturing through Wireshark and STM32CubeMonitor-RF. Configured matching IEEE 802.15.4 channels. Verified that the transmitter

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

The MCU STM32G031K8T6 has the BOOT pin is in the same pin as the SYS_SWDIO. Should I just disregard the BOOT pin and allocate the function to SYS_SWDIO? I am not sure what is the function from the BOOT pin... the internet says:“Flash Memory Boot (Normal Operation): When the BOOT pin is pulled low (to ground), the microcontroller boots from its internal main flash memory, running the primary user application. [1, 2] System Memory Boot (Firmware Updates / ISP): When the BOOT pin is pulled high (to VCC), the chip bypasses user flash and boots into a factory-installed, read-only bootloader in system memory. This allows you to program or update the chip's firmware via serial interfaces like UART, USB, SPI, or I2C without needing an external hardware programmer. [1, 2]” The Nucleo (Nucleo NUCLEO-G031K8 Eval Kit) schematic for the G03 MCU does uses SYS_SDIO (the T_JTCK),and depopulates the pull down resistor from BOOT.Will my board NOT run my code automatically UNLESS I pull that resistor dow

Can I attach a hand-wound enamelled copper wire coil (about 0.05 to 0.1 mm wire) directly to the AC0 and AC1 pads of the UFDFPN5 package, with the chip mounted pads-up and the wire joined using solder or conductive epoxy, and no PCB? Is there any ST guidance or reliability concern with this?

Hi,  we use on a design a ISM6HG256X. We want to detect a shock end event using the interrupt INT2.We use this configuration :    * INT2_HG_WU = 0    * INT1_HG_WU = 0    * INT2_HG_SHOCK_CHANGE = 1     * INT1_HG_SHOCK_CHANGE = 0Logically, we should have an interrupt INT2 only when the shock event end is detected. In fact, we have an interrupt at wake_up event and at the shock end and sometimes we have interrupt on INT1. We use a STEVAL - MKI248KA to evaluate the ISM6.Do you have some tips to solve this problem?

HelloWe are currently using the ASM330LHH in our product and conducting ATP (Acceptance Test Procedure). During the thermal cycling/temperature test phase of the ATP, we have observed significant fluctuations and instability in the sensor outputs.To resolve this issue, we are considering migrating to the ASM330LHHXG1.While we have already reviewed the standard datasheets for both parts, we would like to request additional engineering insights or internal test data regarding their temperature stability. Specifically, we would appreciate your guidance on the following:Does the ASM330LHHXG1 feature any hardware, packaging, or calibration improvements that provide better thermal stability or lower thermal drift compared to the standard ASM330LHH? Have there been any reported cases or internal ST data showing that the ASM330LHHXG1 delivers more stable and repeatable results under stressful temperature environments like ATP? Beyond the datasheet specifications, are there any specific PCB lay

 @JL. Lebon Hello ST Engineer,I would like to ask a follow-up question regarding the LPD pin timing.In the ST25 application manual, I found a timing diagram for LPD and VCC in ultra-low power mode. It states that when the RF field is absent and LPD switches to LOW, we need to wait for tbootLPD (0.6 ms) before communication, as shown in the figure below. However, I also noticed another description in the ST25 datasheet regarding the LPD pin. It mentions that to ensure the internal regulator turns on, its turn-on time (approximately  0.1 ms) must be added to the boot duration, as shown in the figure below.Given these two pieces of information, could you please clarify: Does this mean that after pulling LPD low, I need to wait for a total of 0.7 ms (0.6 ms + 0.1 ms) before starting communication? Or does the specified tbootLPD (0.6 ms) already include the 0.1 ms regulator turn-on time?I look forward to your reply.

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?

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  

Rather than having to select my IDE every time I create a new Project, it would be nice to be able to set my own default.Similarly for other settings; eg, I always like to have the generated code as .c + .h file pairs.

Hello to all, I follow the creation of OEMiROT_Boot, app secure, app not secure with NUCLEO-H563ZI like suggested into  https://wiki.st.com/stm32mcu/wiki/Security:How_to_start_with_STM32CubeMX_OEMiRoT_Boot_path_on_STM32H563.I want to use Visual studio Code with  extension STM32CubeIDE.Follwing the instructions into the web page “:How_to_start_with_STM32CubeMX_OEMiRoT_Boot_path_on_STM32H563.” I have to compile the OEMiROT_Boot, if I import the project OEMiROT_Boot from STM32Cube_FW_H5_V1.7.0 for NUCLEO-H563ZI, into vs code there are error I have to copy  “stm32h5xx_bl2.ld” to utput.ld into the same folder to let vs code to import without error but it’s not possible to compile the project, then I’ll compile the other with keil without problem.After I’ve follwed the list of operation to do but at the point “ 5. Debug Authentication configuration” I cannot select configure (into the project configuratione of MXCube I’ll try to create a project KEIL and CMAKE without lack because I can comp

Hey everyone,I'm having a rough time getting my NUCLEO-H755ZI-Q board to talk to my PC. Whenever I try to connect using STM32CubeProgrammer or debug from STM32CubeIDE, I keep hitting the same error: Error: No STM32 target found!I'm using the onboard ST-LINK/V3 plugged in via the USB ST-LINK port. The board lights up fine, and the OS detects the ST-LINK interface without issues, but the moment I try to probe or connect to the target MCU, it fails.Here is what I've tried so far to troubleshoot: Switched between Normal, Hardware Reset, and Software Reset modes in CubeProgrammer. Lowered the SWD frequency down to 480 kHz. Updated the ST-LINK/V3 firmware to the latest version. Double-checked physical jumpers and power source configuration. Has anyone run into this specific issue on the H755 before, or know a reliable way to force it into bootloader mode to erase the flash? Thanks in advance for any advice!

Hi,May I know the ASIl rating of L9663?If this device is functional safety complaint, Is there a safety manual existing that I can request for?

Here the UIF waveform shifted to high when counter register equaled to 0x02. Isn’t it supposed to shift at the moment the UEV is set? Figure148 also has this problem. And I traced back to the earlier versions. As far as I can reach, the figures were good until rev11, and they were changed since rev17 or earlier. 

Dear all,I am using an application on the NUCLEO-F401RE board. I wrote and successfully compiled a program (with no errors), but I am encountering an error during debugging with the message: "Failed to execute MI command: remote target localhost:61234".The ST-LINK (ST-LINK GDB server) is configured as the debug probe and SWD interface.I have replaced the communication cables and reinstalled the STM32CubeIDE software. It used to work normally.The log is attached below:

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 

When using an STM32 timer to control LED brightness, is it generally better to keep the timer period fixed and adjust the compare value, rather than changing the timer period as well?My understanding is that changing the compare value allows the duty cycle to vary while keeping the PWM frequency constant. Are there any practical considerations when selecting the timer prescaler and auto-reload value, particularly when aiming for smooth dimming across the full brightness range?I’d appreciate any guidance on the timer configuration and potential trade-offs.

Hellow everyone, i am facing this issue that when  connect my nulceo-WL55JC1 with perfectly working cable to my PC it rapidly connects and disconnects again and again i tried to update its driver and mass erase but it connect and disconnects so fast i am not able to do it and i read its quick guide and all the jumpers are in its place once is tried to upload the code to it and in between it got connect the again disconnect some behavior every time.  This is the log when is was able to upload the code on it :STMicroelectronics ST-LINK GDB server. Version 5.7.0Copyright (c) 2020, STMicroelectronics. All rights reserved.Starting server with the following options:        Persistent Mode            : Disabled        Logging Level              : 1        Listen Port Number         : 61234        Status Refresh Delay       : 15s        Verbose Mode               : Disabled        SWD Debug                  : Enabled        InitWhile                  : EnabledWaiting for debugger connection...