Product forums

Hello!I wanted to set up some settings from CubeMX, specifically NX_IP_PERIODIC_RATE in NetXDuo and Rx Descriptor Length in ETH section. NX_IP_PERIODIC_RATE default value is set to 100, but when I set it to 1000, the value does not change when re-generating the code.Rx Descriptor Length default value is set to 4, but when I set it to 8/16/32, the value does not change when re-generating the code. Right now, whenever I re-generate the code, I just manually change these settings in my code due to these settings being set to their default ones. The same problem occurred in CubeMX version 6.15. One thing to point out also, is that the settings I changed are not set back to their default ones in CubeMX, only in the generated code. Also, no errors or warnings are displayed.Is this a bug or am I supposed to do something else before being able to change and apply these settings?

Hello,(@Gidi)Does a FreeRTOS BSP for SR5E1-EVBE5000P exist?Yacob. 

I need help to setup TMP102 alarm function. My board is NUCLEO-F439ZIReading the temperature is working fine.uint8_t TMP102_ADDR = 0x48 << 1;uint8_t REG_TEMP = 0x00;uint8_t buf[12];buf[0] = REG_TEMP;ret = HAL_I2C_Master_Transmit(&hi2c2, 0x90, buf, 1, 10);    // OKret = HAL_I2C_Master_Transmit(&hi2c2, 0x90, 0x00, 1, 10);   //OKret = HAL_I2C_Master_Receive(&hi2c2, 0x90, buf, 2 , 10);    //OKreads the temperature correctly. Buf[0] and buf[1]has correct temperature data. I am trying to setup the alarm function. Reading/writing the Limit registers are failing.Datasheet states that Thigh=80C, and Tlow=70C. After Reset.I am reading the Thigh registers, with the following code:uint8_t reghi = 0x03;ret = HAL_I2C_Master_Transmit(&hi2c2, TMP102_ADDR, reghi, 1, 10); // failis sending 0x00 on reghi. I verified by scope.ret = HAL_I2C_Master_Transmit(&hi2c2, TMP102_ADDR, 0x03, 1, 10);  //fail     it i

Hello Community,I have just started working with the Stellar SR6P3 microcontroller.Do you have any CAN XL application examples or CAN XL driver examples available?I have searched within the Stellar SDK, but I could only find examples related to CAN / MCAN, not CAN XL.Could you please help me with this?For your information, we have already signed the NDA.Thank you very much in advance.Best regards,

Hello,I am using STM32U5 with an external Winbond W25Q128 (Quad SPI NOR via OctoSPI).Could you please clarify from where an external loader (.stldr) for STM32U5 OctoSPI NOR can be obtained, if available?I checked the following locations and did not find any loader for STM32U5:STM32Cube_FW_U5/UtilitiesSTM32Cube_FW_U5/ProjectsSTM32CubeProgrammer default ExternalLoader directoryIs there an official external loader provided by ST for STM32U5 + OctoSPI NOR, or is it currently not supported?Thank you for the clarification

OverviewI’m working on a custom PCB based on STM32H757BIT6, conceptually similar to the STM32H747I-EVAL board. The original EVAL board uses a Micron MT25TL01G (dual-die) QSPI flash on BK1_CS (PG6). On my board, the flash is replaced with MT25QL01G (single-die) and connected to BK2_NCS (PC11).I need to know what changes are required in the BSP and external loader (.stldr) to make them work with this new flash and cs pin changes.HardwareMCU: STM32H757BIT6QSPI Flash:Original: MT25TL01GHBB8ESF (dual-die)New: MT25QL01GBBB8ESF (single-die)New QSPI CS is connected at BK2_NCS (PC11); BK1_CS is tied to BK2_NCS.ToolsSTM32CubeIDE 1.18.xExternal loader build: IAR EWARMProgrammer: STM32CubeProgrammer v2.18.0ST-LINK FW: V2J46S7Differences vs EVALFlash changed to single-die MT25QLCS moved to BK2Hardware is fixed; BSP/loader adapted from EVALCurrent StatusApp firmware: QSPI init works after making few changes like  FlashID = QSPI_FLASH_ID_1, DualFlash = DISABLE, memory-mapped mode initialization

I'm looking to upgrade one of my years-old BLDC 6 step designs which used STM32F401 and too many other components! I like the look of STSPIN32G4 and so purchased an EVSPIN32G4 development platform.It seems I have successfully worked through MC Workbench 6 Step Wizard, including adding my test motor, without error and one warning - pwm generation "Danger: there is no OCP nor Driver Protection enabled" - this despite there being everything required for this on the EVSPIN board but no option to enable it (can we add this to the wish list please).'Generate the Project' works, I've followed through with CubeMX and IDE, produced code and downloaded to EVSPIN32G4 - all good.ST Motor Pilot connects ok with board, clicking on 'Start', motor briefly kicks before Pilot reporting 'Speed Feedback' fault. Using 'Ack Faults' to clear the error, 'Start' again produces same effect consistently.In 'Advanced Configuration' I notice a 'Speed Kp' value of 2038.  Changing this to -2038, I can now run t

Hello We are implementing the memory CRC generation sequence as described in the reference manual. According to the documented procedure, the following steps must be executed:1. Write 0x0 in CRCC[1:0] of RAMCFG_xCCR1 to deactivate the CRC.2. Write 1 in SRAMHWERDIS of RAMCFG_xCR to disable the hardware erase.3. Select the buffer size to take into account during the CRC computation by settingCRCBS[2:0] in RAMCFG_xCCR1.4. Write 0x1 in CRCC[1:0] of RAMCFG_xCCR1 to activate the CRC.5. Write 1 in CRCCS of RAMCFG_xCCR2 to start the CRC computation.The calculated signature is stored in RAMCFG_xCCSR when CRCEOC is setin RAMCFG_xCSR.While following this sequence, the CRCEOC flag never becomes set. We have attached the code segment used to trigger the CRC operation and to subsequently start the Cortex-M33 boot process. Could you please review the implementation and confirm whether the initialization flow is correct?void ConfigRetram(void){/********************** 1 Enable ECC*****************

Despite enabling ADC, the ADC clock option is greyed out for MCU STM32G0B1KBUx. I'm using version 6.16.1

Hello team,I am using the GUI demo (single) for BMSCCTX and C4MINI with 4 LFP Batteries. I have followed the steps described by @ritehracingteam in this thread.After I run the program from the AutoDevKit Studio, my D9 and D2 LED are lit up and D8(Blue) is blinking. D7 remains turned off. Which according to the documentation means SPI is not working.I made sure Hotplug connection is made and the pin configuration is correct, also checked all the connections.Is there something I might be missing?Regards,Zen

Hi STNow I am using ST25R3916B evaluation board, it works well with the project code you provided.My final target is using 3920B on automotive for demostrating NFC card detection as well as digital car access to customer.But we will finally change to other platform's MCU, not use ST's hsot MCU.Due to our MCU has limited Fash / RAM size, we are considering to build our own middleware code to drive NFC frond end. but it looks like it's hard to understand the protocol through I2C waveform, and no any protocol document is avaiable on your website.Is migating RFAL the only way I can do for realizing NFC function with 3916B / 3920B? ThanksLeo   

Howdy!I'm encountering a peculiar issue using STM32CubeMX ( version 16.6.1 ) and configuring the I2C1 peripheral with firmware version STM32Cube FW_G4 V1.6.1.In short, I'm trying to configure it for SMBus-two-wire-Interface, but this option fails to appear in the drop-down, only making SMBus-Alert-Mode available. This is a problem since the alert pin is already being utilized for a different purpose.This appears to be true for all the I2Cx on this device, and in desperation, I checked a handful of other STMG4x microcontrollers, and this issue remains present throughout. Additionally, I randomly checked STM32H7x, and it appears these did NOT share this issue, with the SMBus-two-wire-Interface option appearing as expected.We have a client with a tight deadline, and using SMBUS is essential. Any updates on when this could be fixed, or workarounds would be greatly appreciated.Thanks a million in advance!

Hi,I can't seem to find the launch configuration setting to specify a device in the JTAG chain by its position and IRpre length. I'm using a J-link programmer and I can usually do this from the command line by passing the -jtagconf x,y argument to the J-link executable. However, the debug console in VScode shows that the debug launch config called the Segger J-link GDB server without this argument. I can't seem to find how to make the debug config to append this to the J-link server call Is this supported by the STM32Cube extension?Thanks

Hello ST Community, I am working with the NUCLEO-WL55JC1 and the official Sigfox_PushButton example. When running the application, the firmware consistently fails during EEPROM emulation initialization. The execution enters E2P_Init() and stops very early inside the function. Observed behavior: After that, the application ends up in Error_Handler() The failure happens every time during startup Project details: Board: NUCLEO-WL55JC1 MCU: STM32WL55JC1 (dual-core CM4 + CM0+) Toolchain: STM32CubeIDE Firmware package: STM32CubeWL Example: Sigfox_PushButton EEPROM configuration:In sgfx_eeprom_if.h, EEPROM emulation is configured as follows: Flash page size: 0x800 (2 KB) EEPROM bank size: 2 pages (4 KB) EEPROM base address set to the last two Flash pages:   EE_BASE_ADRESS = 0x0803F000 (256 KB Flash device, address range 0x08000000 – 0x0803FFFF) I already performed: Full chip erase Clean rebuild Debugging on Cortex-M4 Verification that EEPROM does

Environment:STM32CubeIDE version: 1.16.1MCU: STM32H753RTOS: Azure RTOS ThreadXDebug probe: ST-Link (V3)RTOS Proxy plugin:com.st.stm32cube.ide.mcu.externaltools.rtosproxy.win32_1.1.1.202408301240OS: WindowsIssue description:RTOS-aware debugging for ThreadX breaks completely when at least one ThreadX thread name length exceeds ~20 characters.ThreadX itself has no limitation on thread name length (thread name is CHAR *).However, STM32CubeIDE RTOS-aware debug stops working if any thread name is longer than ~20 characters.When this happens:RTOS thread list becomes incomplete or unusableSwitching between threads is not possibleCall stack for inactive threads is missingGDB console shows warnings like: warning: while parsing threads: not well-formed (invalid token) RTOS-aware debugging works correctly only when all ThreadX thread names fit into a 20-byte buffer including the null terminator (maximum 19 visible characters).The issue is 100% reproducible.Steps to reproduce:Create a Thr

I've noticed a behavior with MX25UM5124G_STM32U5x9K-DK External loader over the past 2 years that I feel is a bug. I think the bug lies within the sectorwise erase of the MX25UM5124G_STM32U5x9K-DK External loader fw. If you flash a bin to external flash using the external loader with "erase before programming" enable , there is near 100% likelihood the verification step will fail. I believe this caused by the sectorwise erase not working as intended. The work around has been to do full chip erase on external flash then attempt the flash again. This will succeed almost every time. The behavior that led me to suspect the issue lies within the external loader is when I wrote a proprietary external flasher onboard the stm32. It uses sectorwise erase and has high reliability. This proves to me that flash chip and flash driver on the STM32 are working as intended. Note: We use this proprietary flasher for customer flashing updates but still use Cubeprogrammer for developm

Hello,Due to limitations with the STM32WBA's silicon & Bluetooth stack we've had to significantly re-engineer our hardware and add an external Bluetooth chip. As part of this, we updated our SAI blocks so that one block is transmit and one is receive, and moved our PDM microphones to a SPI bus.Since we have two PDM microphones, we've followed AN5027 "Interfacing PDM Digital Microphones":In our setup, we have SPI2 SCK (mapped to PB10) connected to PA1, and connected PA9 to the DMIC_CLK line. Our plan has been to map PA1 (input) -> TIM17_CH1, which then triggers (via ITR8) TIM3_CH2 which is mapped to PA9 (output).However, I'm struggling to set up the signals properly. I am able to configure TIM17_CH1 so that I can count SPI2_SCK. However, I am unable to trigger TIM3 to count at all.I've attached my example project for the NUCLEO-WBA65RI board.Any insight on this issue?Thank you,Jonathan

Hey guys, can you help me find the datasheet for the L9790 chip? It's in the automatic transmission control unit. Thanks.

Experimenting with STM32F427 and STM32F446 I found out, that the RCC_CR.HSEBYP bit is *not* reset by Software reset. It is reset only by NRST and Power-On reset.While applications where this could lead to problems (i.e. where HSE clock source is changed on-the-fly and software after performing Software reset relies on reset state of this bit) are probably very rare, it may result in an "interesting" surprise if one stumbles upon it, and deserves to be documented.Can ST please confirm/explain and document?Thanks,JW

Hello sir/miss , According to the STM32H7 datasheet, the range of the HSE external crystal oscillator is 4M - 48MHz. However, when we used the STM32H7IIT6-EVAL evaluation board and replaced the original 25MHz surface mount passive crystal oscillator with a 48MHz passive crystal oscillator, we were unable to obtain the corresponding 48MHz frequency from the MCO-PA8 pin. Summary: All conventional passive crystals from 4M to 40MHz were tried and worked fine. However, for external passive crystals above 40MHz , just like 48MHz, the MCO output waveform frequency was 16MHz, which is 1/3 of the HSE frequency, and it was unable to output 48MHz. Please provide a solution or suggest areas where we can improve the test. Thank you very much!

The callback messages seem corrupt and I get a connection error or -162025-12-09 12-05-03.130|INFO||: Type = 0 Message = USB speed : Full Speed (12MBit/s)2025-12-09 12-05-03.130|INFO||: Type = 0 Message = Manuf. ID : 2025-12-09 12-05-03.130|INFO||: Type = 0 Message = Product ID : STMicroelectronics2025-12-09 12-05-03.130|INFO||: Type = 0 Message = SN : STM32 BOOTLOADER2025-12-09 12-05-03.130|INFO||: Type = 0 Message = DFU protocol: 1.12025-12-09 12-05-03.130|INFO||: Type = 0 Message = Board : --2025-12-09 12-05-03.130|INFO||: Type = 0 Message = Device ID : unknownShould be:2025-12-04 14-55-46.892|INFO||: Type = 0 Message = USB speed : Full Speed (12MBit/s)2025-12-04 14-55-46.892|INFO||: Type = 0 Message = Manuf. ID : STMicroelectronics2025-12-04 14-55-46.892|INFO||: Type = 0 Message = Product ID : DFU in FS Mode2025-12-04 14-55-46.892|INFO||: Type = 0 Message = SN : 2003645000002025-12-04 14-55-46.892|INFO||: Type = 0 Message = DFU protocol: 1.1|2025-12-04 14-55-46.892|INFO||: Typ

I am working on STM32H753 (with eval board EVAL 2).I am modifying an existing firmware built without libc and without startup files.I need to convert floating point variables to strings, so I want to use as little as libc as possible. I choosed newlib-nano for memory size.I compiled with `-mfpu=fpv5-d16 -mfloat-abi=hard -specs=nano.specs ...` and linked with `-mfpu=fpv5-d16 -mfloat-abi=hard -specs=nosys.specs -specs=nano.specs -u _printf_float -nostartfiles ...`I also added the definition of symbols required by the libc and reserved a memory area for the heap. I tried to write a string from a double variable with the following code (it's code for debug only, I know it may overflow the char array depending on float value):char my_string[64]; double my_double = 1.3; sprintf(my_string, "%.3f", my_double);But the content of the string (checked by dumping the memory on debugger) is `1300` and not `1.300`(i tried with different values and format specifiers)Am I missing something ?

Hi ST teams,I am currently planning to develop a project using the STWBC2 series. However, I have found that the technical resources available on the official website are very limited. Could you please provide or recommend a more comprehensive set of resources, such as the Full Datasheet, Reference Manual, and Firmware Development Guide, to support our design process?" thank you   

When i give varying PWM signal at high frequency under range, the motor sometimes produces noise and gets stuck (0 speed even though pwm signal is valid). What is the issue? I feel its due to PID tuning. Kindly share PID tuning method.Thanks 

Hi, i have bought a Nucleo-U575ZI-Q coupled with a X-Nucleo-67W61M1 i have upload the exemple ST67W6X_MQTT, after reading the doc i have complete the configuration and i run well.  I use it with mosquitto or nanomq brokers (same results) but on both the broker inform me than the QoS=0 (with publish and subscribe) The documentation of the AT-command of ST67W indicate that i can use 0,1 or 2 for the Qos. In the exemple the drivers don't use the Qos and force it to zero. I have modify it but the result is always the same. I would like to use QoS=1 to be sure the message arrived. Have you an idea ? I have verify than the broker accept all levels in the conf. I have also publish with MQTTX(with Qos=1) and the broker notify the good level of Qos