Product forums

I have an STM32mp135f-dk board that I have been using openstlinux-6.1 to develop images on.For my board, I made a custom device tree "iris.dtb" which I intend to use instead of the default "stm32mp135f-dk.dtb".I ran into an interesting issue where u-boot on my board would not load the my modified uboot environment variables.For context, the following is my flash layout file with the u-boot-env at address 0x00904400  #Opt Id Name Type IP Offset Binary - 0x01 fsbl-boot Binary none 0x0 arm-trusted-firmware/tf-a-stm32mp135f-dk-usb.stm32 - 0x03 fip-boot FIP none 0x0 fip/fip-stm32mp135f-dk-optee.bin P 0x04 fsbl1 Binary mmc0 0x00004400 arm-trusted-firmware/tf-a-stm32mp135f-dk-sdcard.stm32 P 0x05 fsbl2 Binary mmc0 0x00044400 arm-trusted-firmware/tf-a-stm32mp135f-dk-sdcard.stm32 P 0x06 metadata1 FWU_MDATA mmc0 0x00084400 arm-trusted-firmware/metadata.bin P 0x07 metadata2 FWU_MDATA mmc0 0x000C4400 arm-trusted-firmware/metadata.bin P 0x08 fip-a FIP mmc0 0x00104400 fip/fip-stm32mp135f-dk

Hi, I use OEMiROT_Appli_TrustZone +OEMiROT_Boot to do some change in order to migrate to my project. Version: STM32Cube_FW_H5_V1.5.0 1.i change the secure image and non secure image size in flash_layout.h from OEMiROT_Boot. #define FLASH_S_PARTITION_SIZE (0x20000) /* 128KB for S partition */ #if defined(DEVICE_1M_FLASH_ENABLE) #define FLASH_NS_PARTITION_SIZE (0x30000) /* 192 KB for NS partition */ #else #define FLASH_NS_PARTITION_SIZE (0x60000) /* 384 KB for NS partition */ ​2.then rebuild the OEMiROT_Boot. it will autocratically change the ld file and image.xls size of OEMiROT_Appli_TrustZone. 3.rebuild OEMiROT_Appli_TrustZone secure ap and non secure app 4.execute STM32Cube_FW_H5_V1.5.0\Projects\NUCLEO-H563ZI\ROT_Provisioning\OEMiROT\provisioning.bat OK 5.reconnet the board with UART . it shows the error as follow:. INF] TAMPER Activated [INF] BANK 1 secure flash 0, 27] : OB [0, 14] [ERR] Unexpected value for secure flash protection

Hi,I am writing my own RTOS and I do not use CubeMX nor the HAL. I directly program the STM32N657 LTDC registers.The target is the STM32N6570-DK board with the original 800x480 RGB LCD.Problem descriptionThe LTDC background color is displayed perfectly.However, as soon as I enable Layer 1 with a framebuffer located in the internal AXI SRAM, the displayed image becomes corrupted.The corruption is unusual:the top of the image is correct, below approximately 320 lines, the image progressively becomes shifted, the bottom of the image looks like repeated square blocks shifted horizontally, no FIFO underrun is reported.The framebuffer contents themselves are correct when read back by the CPU.LTDC configurationFramebuffer:Address : 0x34200000Format : ARGB8888Size : 800 x 480Pitch : 3200 bytes Layer registers:L1CFBAR = 0x34200000L1CFBLR = 0x0C800C83L1CFBLNR = 480L1PFCR = 0x00000000 (ARGB8888)L1CACR = 0x000000FFL1BFCR = 0x00000607L1CR = 0x00000001 Global registers:GCR = 0x00

 This means that the links for both ‘Fixed Issues’ and ‘Known Problems’ in the release announcement don’t work: 

Hi! I'm working on setting up FDCAN communication using the STM32N6570X0-Q Nucleo Board. However, when I try to modify the bit timing parameters—such as the Nominal Prescaler, Nominal Time Seg1, or Seg2—the baud rate doesn't seem to change regardless of the values I set.On the receiving side, I'm using a STM32H533RE Nucleo Board to echo the messages, but it doesn't receive anything—so I suspect the issue may be with the timing configuration on the N6570X0-Q.Do you have any idea what might be causing this behavior?Thanks in advance! 

I am currently evaluating thefor use with 1000Base-T Ethernet and am attempting to configure the peripherals using STM32CubeMX. While following the same process as with other STM32 chips, I was unable to find the Ethernet configuration under Pinout & Configuration -> Connectivity. Could you kindly advise where I should configure the Ethernet settings?Thank you for your assistance.

STM32CubeMX generates by default a xx.ld file.It has copyrights from 2023. However, if I set "Apply Application Regions Settings to Linker File", it will generate a file with 2025 copyright, different template, also with XX.ld case, which on Linux, will give issues. Version 6.16.1

HiWhile reviewing some specs for the SW developers, we noticed some inconsitency between the datasheet and reference manual of the STM32H735.The DS states four VBOR thresholds (VBOR0 to VBOR3).In the RM, the description of Bits 3:2 BOR_LEV[1:0] is different for the read-only register FLASH_OPTSR_CUR and the programming register FLASH_OPTSR_PRG. The former states four VBOR thresholds (VBOR2 is 0b10), the latter refers to a nominal voltage level (2.4V - approx. VBOR2 - is 0b01). Can you please clarify. Thanks! 

I was able to sign properly a tf-a image using STM32_SigningTool_CLI STM32_SigningTool_CLI -bin tf-a.stm32 -o tf-a_Signed.stm32 --password password --public-key publicKey00.pem publicKey01.pem publicKey02.pem publicKey03.pem publicKey04.pem publicKey05.pem publicKey06.pem publicKey07.pem --private-key privateKey00.pem --type fsbl --header-version 2.2 -of 0x00000001 I was moving my setup to use a pkcs#11 to better manage my secrets. I was trying to use softhsmv2 as a first step. It seems that if -hv is specified the tool is failing while validating the inputs:STM32_SigningTool_CLI -bin tf-a.stm32 -o tf-a_Signed.stm32 --password password --header-version 2.2 -of 0x00000001 --module /usr/lib/softhsm/libsofthsm2.so -ki 00 01 02 03 04 05 06 07 -pwd password -si 0x00 -aki 0x00 --header-version 2.2This produces the error:Error: Invalid Header version valueHeader v2.2 accepts 8 public keys And if I don't define --header-version the tool works properly, but the output i

Dear ST Support Team,I am working on a custom BLDC motor controller using STM32G431CBU6 with STM32 Motor Control SDK 6.4.2 and DRV8316CT motor driver.I have created custom Control Board and Power Board JSON files using the Motor Control Board Designer. However, I am facing an issue configuring the current sensing topology for FOC.Hardware ConfigurationMCU: STM32G431CBU6 MCSDK Version: 6.4.2 Motor Driver: DRV8316CT Control Algorithm: FOC PWM Configuration: 3-PWM (TIM1) Current Sensing: Three Shunt Resistors (Amplified)Current sensing connections are:Signal MCU Pin ADC Function CURRENT_AMPL_U PA1 ADC1_IN2 / ADC2_IN2 CURRENT_AMPL_V PA2 ADC1_IN3 CURRENT_AMPL_W PA3 ADC1_IN4 ProblemWhen I configure Three Shunt Resistors, Motor Control Workbench reports the following warnings: CSConnect: ThreeShunt_AmplifiedCurrents DualADCs SharedSignalCSConnect: ThreeShunt_AmplifiedCurrents DualADCs NoSolutionI investigated the ParameterConnection.json file and found that the DualADCs im

I created a new project using CubeMX, and after that I plan to implement a framework for my firmware. I would like to better understand the best way to organize a clean and maintainable folder structure.A colleague told me that all folders should be created inside the Core directory. I would like to understand whether using Core to contain my framework is the best approach, or if it is acceptable to create additional source folders outside of it.Additionally, where can I find examples of STM32 firmware projects generated using CubeMX?

In my application I want to implement an custom inband communication between RX <--> TX。I've gone through the official datasheet but couldn't find clear information about the in-band communication data registers or buffers. Could you point me to any additional reference materials, application notes, or documentation on in-band communication?

Hi, I am using a STM32U375KEU on a custom PCB and I am trying to enter STOP2 mode. When flashing the code i the error: Target is not responding, retrying… and the current draw is the same as running the MCU normally at around 2mA. Here is the mainint main(void){HAL_Init();SystemClock_Config(); HAL_DBGMCU_DisableDBGStopMode(); // 3. KILL SYSTICK SO IT CAN'T WAKE THE CPUHAL_SuspendTick();SCB->ICSR |= SCB_ICSR_PENDSTCLR_Msk; // 4. ENTER DEEP SLEEP__HAL_PWR_CLEAR_FLAG(PWR_FLAG_SBF);HAL_PWR_EnterSTOPMode(PWR_LOWPOWERMODE_STOP1, PWR_STOPENTRY_WFI); // 5. IF IT WAKES UP, TRAP IT HEREwhile (1){}}}Does it have something to do with the Clock?

When I attempt to power cycle a STM32N6570-DK or NUCLEO-N657X0-Q board via the STM32_Programmer_CLI, I get the following error message:Error: Failed to Power ON the board ! Here is the full log:❯ STM32_Programmer_CLI --power off index=0 --power on index=0-------------------------------------------------------------------STM32CubeProgrammer v2.21.0 -------------------------------------------------------------------Power OFF...Drives the target power pin out of the (onboard) ST-Link.Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]Power OFF the board finished with success !Power ON...Drives the target power pin out of the (onboard) ST-Link.Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]Error: Failed to Power ON the board !  However, when I attempt the same command on other Nucleo boards, I don't get this error. Here's the same command run on the NUCLEO-H533RE:❯ STM32_Progr

Hi When I using STM32CubeProgrammer 2.22 GUI and try to control option byte, the page can't display.while CLI can read option bypte. 

STM32CubeProgrammer_CLI STM32TrustedPackageCreator problem with HSM, HSM_P11_Lib.dll cannot be loaded. GUI STM32CubeProgrammer works fine. Where that dll should be located? I Am using win11 pro. 

Hello Everyone please guide me in the stm32h7xx_hal_eth.c file a function which name is HAL_ETH_ReadData() is not properly working in this function while loop is not working the main specific this part => “ (READ_BIT(dmarxdesc->DESC3, ETH_DMARXNDESCWBF_OWN) == (uint32_t)RESET)”isn not working and i ma getting output is host unreachable  => PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data.From 192.168.1.10 icmp_seq=1 Destination Host Unreachablei am using NUCLEO-H723ZGT6 board   HAL_StatusTypeDef HAL_ETH_ReadData(ETH_HandleTypeDef *heth, void **pAppBuff){uint32_t descidx;uint32_t descidx_next;ETH_DMADescTypeDef *dmarxdesc_next;ETH_DMADescTypeDef *dmarxdesc;uint32_t desccnt = 0U;uint32_t desccntmax;uint32_t bufflength;uint8_t rxdataready = 0U; if (pAppBuff == NULL){heth->ErrorCode |= HAL_ETH_ERROR_PARAM;return HAL_ERROR;} if (heth->gState != HAL_ETH_STATE_STARTED){return HAL_ERROR;} descidx = heth->RxDescList.RxDescIdx;dmarxdesc = (ETH_DMADescTypeDef *)heth->R

Hi everyone,I am learning STM32 bootloader development and I would appreciate some guidance.Hardware STM32 Nucleo-G431RB Windows PC USB-to-TTL UART converter UART communication RequirementI already have an application HEX file.My goal is to update the firmware through UART using a custom bootloader.I do not want to use: STM32CubeIDE ST-LINK STM32CubeProgrammer Any IDE during firmware update The complete firmware update should happen only through UART.What I want to achievePC↓Application (my own program)↓UART (TTL)↓Custom Bootloader↓STM32 Flash Memory↓Jump to ApplicationQuestions What should be my first step to implement this? Should my PC application send the HEX file directly, or should it first convert it into BIN? Should the bootloader parse Intel HEX records, or is it better to send binary data? What communication protocol is commonly used for custom UART bootloaders? Packet format Start byte Length CRC ACK/NACK What is the recommended fl

Hello,We are using an STM32H743 MCU with the LI10600T070IA3098-TCF LCD panel (1024×600 resolution) through a 24-bit RGB LTDC interface. We are experiencing display flickering, as shown in the attached video.Could you please help us identify the possible root cause? Kindly let us know what additional information (schematic, LTDC timing parameters, oscilloscope captures, PCB layout, etc.) would be required from our side to assist in debugging this issue.Any guidance or recommendations would be greatly appreciated.https://drive.google.com/file/d/1wClnXqdIc8OI-4y19CmWxJERnSnIYUK-/view?usp=sharing 

[English was established as the common basis so that everyone in the global community can understand each other (see ST Community Terms and Conditions - STMicroelectronics Community, article 10)]Dear STMicroelectronics Technical Support,Hello,We are a company in the rail transport industry and are currently using your TL084AI operational amplifier. However, during use, we have noticed inconsistencies in the markings on the surface of the devices. I have attached an example in the image below. What does “MZE5303” mean? (Note: we currently have another batch, such as MZE4303. What does this represent?) Which characters indicate the date code (for example, the batch number)? We would appreciate your detailed explanation. Thank you in advance. 尊敬的意法半导体技术支持，您好，我们是一家铁路交通行业的公司，目前正在使用您的TL084AI运算放大器。然而，在使用过程中，我们注意到设备表面的标记存在不一致。我在附图中附上了一个例子。“MZE5303”是什么意思？（注：我们目前还有另一批，比如MZE4303。这代表什么？）哪些字符代表日期代码（例如批号）？我们希望能得到您的详细解释。提前感谢大家。 

Hi, we are in the initial stage of our project and planning to use STM32H7S7I8T6, we need to have a 128MByte of external RAM as per our requirements but only 64MByte of PSRAM is available in market currently, is it possible to add two 64MByte of PSRAM to the MCU (If any please provide the guidance/design note) or any other options ? 

TouchGFX 4.26.0Low severity bug. Only visual in Designer. In the generated code the correct alignment is used.Steps to reproduce:create TextArea. Disable “auto-size” Set textID with text element that has right alignment. The shown alignment is still left aligned.When Designer is restarted, the correct alignment is shown again.

Specific STM32H7 series MCUs have the DCMI peripheral greyed out in STM32CubeMX version 6.17.0.See this image:Hovering over the peripheral it displays "Not available: DCMI and PSSI are in exclusive choice"I opened a few projects with different MCUs and checked whether the DCMI was greyed out:​​STM32H723ZGIx - WorkingSTM32H725IEKx - WorkingSTM32H730ZBIx - WorkingSTM32H733ZGIx - WorkingSTM32H735IGKx - WorkingSTM32H742BITx - Not workingSTM32H743XGHx - Not workingSTM32H745BGTx - Not workingSTM32H747XGHx - Not workingSTM32H750IBTx - Not workingSTM32H753Allx - Not workingSTM32H755XIHx - Not workingThe PSSI peripheral is notably absent from the list of available peripherals (correctly as per the datasheet) in STM32CubeMX for the parts where DCMI has been disabled.This is clearly a bug in the mutually exclusive check in STM32CubeMX between the DCMI and PSSI, failing on the parts without the PSSI peripheral. See: STM32CubeMX 6.15.0 claims "DCMI and PSSI are in exclusive choice" for STM32H753ZIT

Hey,I want to enable a fast connection with the STM32WB09KE. How do i avoid that the services and characteristics are discoverd every connection? i toughts there was a option for that when using the full ble stack. But whit this firmware and mcu i don’t see it in the STM32CubeMX. So before is start is this possible with this MCU and ble firmware options? Thx in advance! Best regardsMathias 

I tried to program an STM32F407-DISC1 board in CubeIDE 2.1.1 after an IDE update and after a my break from programming.With "GDB server" I get an endless "Waiting for debugger connection..." state with "Configuring GDB" in the progress tab. With "OpenOCD" everything stops at:Listening on port 3333 for gdb connectionsInfo : [STM32F407VGTx.cpu] external reset detectedAt the same time I can download a .bin file through STM32CubeProgrammer, so the cable and the IC’s seem to be fine.I have upgraded the ST-LINK firmware, installed the stsw-link009 driver, and disabled Windows Firewall — none of this helped.What else could I try?