No best answer

Hello, I mistakenly programmed the HSM enable record into the host core DCF area at address 0x29F81A10. Could this introduce any risk of incorrect configuration? I found that I can overwrite the incorrect DCF record by programming all 0xFF. However, I am concerned that the programmed 0xFF may differ from the 0xFF of an unprogrammed blank device. Could you advise whether this operation is valid?

Hi,I'm working on a product based on the STM32WB5MMG module, running the BLE + Thread dynamic concurrent CPU2 binary (stm32wb5x_BLE_Thread_dynamic_fw.bin v1.24.0, FUS 2.2.0). Our boards are Thread routers.The 802.15.4 link margin is too low for us. Two boards 1 m apart see each other around -85 / -88 dBm, so I'd like to raise the Thread TX power. BLE is set to +6 dBm with aci_hal_set_tx_power_level(1, 0x1F) and works fine. For Thread we never set anything, so it runs at the stack default. The SMPS is not enabled in our code, so the chip is powered in bypass at 3.3 V.I tried otPlatRadioSetTransmitPower(NULL, x):called at Thread start on both boards with 6, -6, -20 and 0x1F: the boards don't attach to each other anymore. Remove the call, reflash, and everything works again. 6 on one board only, at the end of our Thread init (before BLE advertising starts): the board attaches and goes up to router, and it receives the multicast CoAP messages from the other board. But the other board never

I am following https://www.st.com/resource/en/product_presentation/evlspin32g4-act-and-stwinbox-high-speed-datalogging-for-motor-control-and-sensors-quick-start-guide.pdf using hardware STEVAL-STWINBX1+EVLSPIN32G4-ACT  https://github.com/STMicroelectronics/stdatalog-pysdk.git v1.5.0 stdatalog_MC_GUI.py is able to start/stop the motor operated in sensorless mode, correct GUI view and .dat file stored for all onboard sensors. But enabling slow/fast motor telemetries leads to error message: “HSDatalogApp.stdatalog_gui.HSD_GUI.HSD_Controller - ERROR - No data from fast_mc_telemetries Component.” For suggestion “Restart the acquisition lowering component ODR to acquire data correctly.”, I tried to only enable one data item in slow telemetry, and had the same failure. FW build env for both PMSM and STWIN.box:MotorControl Workbench_6.3.0 STMCubeIDE 2.1.1 STMCubeMX 6.12 STM32 FW V1.5.2 When importing the STWIN.box FW project, among three projects(DATALOGMC, DATALOGMC_CubeAI, DATALOGMC_NanoEdge

Hi all,I'm trying to flash a fresh STM32G0x1 MCU (Device ID: 0x466, Revision ID: Rev 1.1) using ST-LINK V2 (FW: V2J48S7) in Hot Plug connect mode with Hardware reset mode, SWD frequency 100 KHz, target voltage reading 3.26V.ST-LINK connects and correctly reads the Device ID and Revision ID, but then fails with:Error: Unable to get core IDError: Unable to get core IDUPLOADING OPTION BYTES DATA...Bank: 0x00Address: 0x40022020Size: 108 BytesError: Uploading Option bytes bank: 0 failedError: Initializing the Option Bytes failedDisconnected from device. Things I've tried: 1. SWD wiring (SWDIO, SWCLK, GND, NRST, 3.3V) checked Target voltage reads 3.26V, stableTried Hot Plug + Hardware reset modeAny guidance on the issue would be appreciated.Thanks!

I created simple project using STMCubeMX2 for MCU STM32C552. I configured the clock by choosing HSIS on System MUX.  When I compile and run generated code it ends in HardFault_Handler. When using PSIS option - the same result. HSISDiv3 clock works well. When I divide HSIS or PSIS clock by 2 on AHB prescaler it also works.   Any idea? Thank you  

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. 

Hi everyone,I'm using a custom board with minimal circuitry; currently, only an STM IC with a reset circuit is installed. The SWD analysis using a data logger shows that the chip is responding and the electrical connections are fine.I’m using the Nucleo-F401RE as a programmer; programming the onboard chip works without errors, but not when communicating with the target controller via the SWD interface.I get the following message:Error: Database: There's no active configuration for this device. All 2 configurations are disabled!I have selected the “Hardware reset” and “Under reset” settings.Here is the report15:42:31 : STM32CubeProgrammer API v2.23.0 | Windows-64Bits 15:44:00 : UR connection mode is defined with the HWrst reset mode15:44:00 : ST-LINK SN  : 0672FF49525083676702230915:44:00 : ST-LINK FW  : V2J48M3515:44:00 : Board       : NUCLEO-F401RE15:44:00 : Voltage     : 3.26V15:44:00 : SWD freq    : 4000 KHz15:44:00 : Connect mode: Under Reset15:44:00 : Reset mode  : Hardware reset1

The latest listed is v6.17.x:https://wiki.st.com/stm32mcu/wiki/Category:STM32CubeMX_errata Yes, I know that v6.18.1 errata is available here (via here) - but shouldn’t it be also linked via the wiki ?Or, if the wiki is no longer being maintained, it should point to the new location.

All previous versions listed at https://wiki.st.com/stm32mcu/wiki/Category:STM32CubeMX_errata (viz, v6.17.x back to v6.10.x) had this example under How to improve the wake-up from Stop sequences without relying on the global SystemClock_Config():(note the typo in the comment on checking LSE ready) v6.18.1 still has the exact same erratum - but now there is no example: 

Mostly, the forum converts a link to a post/thread to a “preview” showing the author’s avatar and post title.But sometimes it doesn’t.Example:Both of those links came from the menu ‘Copy link’ option.Here: In the above case, it was the same both in the editor and after posting.Sometimes, the “preview” doesn’t show in the editor, but does show once posted.

Hi,I am working on CAN FD communication using the STM32C542RCT6. CAN FD is working properly when I use an external clock source. However, when I switch to the internal clock, the controller starts reporting errors such as Error Passive, followed by Bus-Off.My suspicion is that the internal clock may have a slight frequency deviation, which could be affecting CAN FD communication. Since this is a new controller, I would like to understand whether the internal clock can reliably support CAN FD communication or whether an external clock is required.My current CAN FD configuration is: Arbitration bit rate: 500 kbps Data bit rate: 2 Mbps Bit Rate Switching (BRS): Enabled Could you please clarify whether the internal clock can support this configuration and what could cause the controller to enter Error Passive and Bus-Off states when using it?

Hi what is the crrent state of agentic programming with cub ide? Like I want Claude code to add an EMMC driver to my existing project. Is this possible? 

 Hi,I am working on an offline Flyback converter utilizing a UCC28C50 primary side PWM controller. Originally, the converter was configured for Constant Voltage (CV) mode using a standard TL431 and optocoupler circuit, which operated correctly.To convert this design into a Constant Current / Constant Voltage (CC/CV) supply, I replaced the TL431 with an STMicroelectronics SEA05 advanced controller on the secondary side. My implementation strictly follows the secondary-side configuration from STMicroelectronics' application note "10W offline LED driver based on VIPER27" (DN0002/AN4376).10W offline LED driver based on VIPER27 (DN0002)  Circuit Parameters and Component Values: Target Output Specifications: V_OUT = 15 V, I_OUT = 3 A (Test Target) Current Sense Resistor (R_SENSE / R16, R22): 18 mΩSEA05 Pin Configuration Components: R₁₈  = 3.75 kΩ, R₂₀ = 10 Ω,  R₅ = 10 kΩ, C₈ = 100 nF, C₁₀ = 1 nF, R₁₅ = 120 kΩ, R₇ = 10 kΩ,  R₆ = 51 kΩThe Problem: According to the SEA05's internal 50 mV curren

i’m trying to use stm32h735 chip in my custom board , when it comes to flashing or starting new debug session it gives error like   when i’m trying to access it through stm32programmer it gives it work and connect after many times of trying to turn off power, or remove the st link cable and put it again, when it connected, I erase the full chip to access it, then try to flash it in the ide, it works for 3 times, then repeat the error again, and I tried in cube programmer to change the mode to under reset mode and press reset button and press connected, it failed, I need to know permanent solution not every time it gives me this 

I was trying to edit my post here:https://community.st.com/feedback-forum-118/inconsistent-presentation-of-links-167657?postid=747370#post747370 After inserting images and links and stuff, the “Send” button was grayed out. I had to hit “Cancel”, edit the post again, redo everything, and hit send (which was not grayed out this time). No indication as to why it was grayed out. 

Dear ST Team,  We have recently received parts of STM32G474CET6 & STM32F103RBT6 which there are no COO information on Label. Is this normal observation?  Could you please help advise if this is due to label format restriction of tariff issue or other reasons? All the COD and COO info the parts are visible on chip itself. Appreciate your explanation and advise.   

I need the CPU to copy camera frames for tasks like screenshot-based recognition and uploading. However, in the data path (sensor → CSI → DCMIPP → DMA → DDR), the DMA mapping layer marks the memory as uncached, resulting in very slow speeds; the CPU read bandwidth is only ~143 MB/s—just one-eleventh of the speed of standard cached memory (1619 MB/s).Copying a 1280x960 image from DMA takes around 25ms, and the process becomes even slower at higher resolutions, leading to a poor user experience.Is there a way to make the DMA copy speed match that of standard cached memory (1619 MB/s)? 

Hi everyone,I'm using UART Receive-to-IDLE with circular linked-list GPDMA on an STM32H7RS and ran into a problem where reception stopped with HAL_DMA_ERROR_DTE.The DMA node and RX buffer are both in DMA-accessible, non-cacheable RAM and aligned to 32 bytes.The DMA handle and queue structure are in normal BSS. Everything is global/static and zero-initialized.I checked the queue/node connection and the source address in LinkRegisters[3], which correctly pointed to UART RDR. The node address reconstructed from CLBAR and CLLR was also correct when checked.However, these were the actual DMA register values in the working and failing cases: Working FailingCBR1 0x00000080 0x0000049BCSAR 0x40007824 0x00000005CDAR 0x24001960 0x200065A0After the DMA error, UART error handling stopped reception and disabled the IDLE interrupt, so I stopped getting HAL_UARTEx_RxEventCallback() calls.What fixed it was adding __DSB() inside HAL_DMAEx_List_Start_IT(), after the CLB

Hello,Do you have a FDA accession number for the VL53L1X  ToF chip? thanks.

Hi, Thank you for your support. I was able to get VL53L4CD_GUI working using the firmware file:VL53L4CD_PSNRun_F401.bin However, the connection is very unstable and I am having difficulty using the GUI reliably. Current status:1. I programmed VL53L4CD_PSNRun_F401.bin into the NUCLEO-F401RE using STM32CubeProgrammer.2. Initially, VL53L4CD_GUI could not connect.3. I noticed that if I enable the option "Run after programming" in STM32CubeProgrammer during programming, VL53L4CD_GUI sometimes connects successfully.4. When the connection succeeds, the GUI displays:   Device Name : VL53L4CD   API Version : api rev 0.2.2 build 3   and I can acquire ranging data correctly.5. However, after power cycling the board or reconnecting later, the GUI usually shows:   "Failed To Connect to Nucleo Board: Com Port Not Detected"6. In Windows Device Manager, the board is still visible as:   "STMicroelectronics STLink Virtual COM Port"   and the COM port is recognized correctly.7. Reprogramming the same fir

Hi ST Community & Support Team,I am working with the NUCLEO-H755ZI-Q (Board MB1363) and I noticed a potential typo in the User Manual UM2408 (Rev 6). 31/57In Section 7.12 - Ethernet, Note 3 states:"On MB1363 Rev.C: Ethernet PHY LAN8742A must be set in the Power-down mode [...] SB13 can also be removed to get the same effect."However, when checking the schematic (mb1363-h755ziq-d01_schematic.pdf), SB13 is actually located in the ST-LINK Virtual COM Port level translator circuit (U1: SN74LVC2T45DCUT) between STLK_VCP_RX and T_VCP_TX, and is already marked as DNF (Do Not Fit).It seems SB13 in Note 3 is a documentation typo pointing to the wrong solder bridge.Based on the schematic, there is no dedicated hardware jumper or solder bridge (SB) to physically disconnect the power or clock lines of the LAN8742A PHY.Furthermore, upon a detailed review of the schematic, there is no dedicated hardware jumper or solder bridge (SB) to physically disconnect the power or clock lines of the LAN8742

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

Hello everyone,I am using a VL53L0X and have encountered an intermittent failure. I would like help identifying the possible cause and the next debugging steps.Hardware setup: MCU: Cortex-M0, model MM32SPIN06PF I2C: GPIO bit-banged I2C in open-drain mode, with 4.7 kΩ pull-ups. An ENS210 temperature/humidity sensor is also on the same I2C bus. ENS210 address: 0x43. VL53L0X 7-bit address: 0x29; 8-bit address: 0x52. The VL53L0X XSHUT pin is only pulled up to 3.3 V through a 10 kΩ resistor. It is not controlled by an MCU GPIO. VL53L0X supply voltage: 3.3 V. VL53L0X API version: 1.0.4. Failure symptoms: The VL53L0X works normally at first, but occasionally malfunctions. When the failure occurs, no IR emission can be seen from the VL53L0X using a phone camera. Can IR normally be seen with a phone camera? ____ Pressing a hardware button to re-initialize the VL53L0X does not recover it. Only after power-cycling the VL53L0X alone and then pressing the button to re-initialize i

In release configuration, the flash usage is 65%,but in debug configuration, it is 98.1%. What’s more ,when i download my app to stm32f103c8t6, it will be debug configuration.