Solved

All related to the deadtime settings are disabled, but the Set Source of Output 2 can't be set up. It keeps constant 0, and says the deadtime is enabled? why??? @Aimen1

Hi,I found an issue when generating code for a BLE application with STM32CubeMX v6.17.0.In particular, I have a service called DataTransferService with three characteristics:DataStreamCommandControlTransferStatusThe DataStream characteristic is configured as a notification with a fixed value length of 100 bytes.When I try to increase its length up to 250 bytes and regenerate the code, the following functions in custom_app.c are removed:Custom_Datastream_Update_Char()Custom_Datastream_Send_Notification()I have attached the .ioc file for reference.

Code generation of the attached .ioc file (copy of ST example file of similar name) does not generate clock init for UART4.  This means the example application hard faults.  I see no reason why the UART clock should not be initialised here and would save someone time debugging in the future!In stm32mp2xx_hal.c:void HAL_UART_MspInit(UART_HandleTypeDef* huart) { GPIO_InitTypeDef GPIO_InitStruct = {0}; if(huart->Instance==UART4) { /* USER CODE BEGIN UART4_MspInit 0 */ // TODO: Need this here! __HAL_RCC_UART4_CLK_ENABLE(); /* USER CODE END UART4_MspInit 0 */ /**UART4 GPIO Configuration PH8 ------> UART4_RX PH7 ------> UART4_TX */ GPIO_InitStruct.Pin = GPIO_PIN_8; GPIO_InitStruct.Mode = GPIO_MODE_AF_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Alternate = GPIO_AF4_UART4; HAL_GPIO_Init(GPIOH, &GPIO_InitStruct); GPIO_InitStruct.Pin = GPIO_PIN_7; GPIO_InitStruct.Mode = GPIO_MODE_AF_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Sp

When configuring the LTDC Layer Settings for an STM32N6 chip in CubeMX, the Layer 0 - Color Frame Buffer Start Address is missing: This parameter is available with other chips, such as STM32F750:

The STM32N6 supports YCbCr as an input format (see reference manual RM0486 section 21.3.5). As of version 6.16.1, this option is still not available in STM32CubeMX. The generated code can be manually modified to make it work by settinghdma2d.LayerCfg[x].InputColorMode = DMA2D_INPUT_YCBCR;   

CubeMX 6.16.0 "Memory Management" used for ethernet and with enabled linker file generation creates the following [ORIGIN adapted from default]:RxDescripSection (rwx) : ORIGIN = 0x30040000, LENGTH = 0K TxDescripSection (rwx) : ORIGIN = 0x30040060, LENGTH = 0K Rx_PoolSection (rwx) : ORIGIN = 0x30040200, LENGTH = 1KWhat I would have expected was:RxDescripSection (rwx) : ORIGIN = 0x30040000, LENGTH = 96 TxDescripSection (rwx) : ORIGIN = 0x30040060, LENGTH = 96 Rx_PoolSection (rwx) : ORIGIN = 0x30040200, LENGTH = 1536[with just 1 ETH RX buffer - see this other post ].Can someone explain to me whether this is intentional - maybe because of a constriction with the MPU granularity?Or whether CubeMX handles this wrong and should allow sub-kilo-byte granularity?Best regardsJohannes 

Hi,Good day,may we seek your expertise regarding L9959U/L9959T.is there any difference for these mpn below?L9959U-TR-D L9959T-TR-W L9959U-TR-W thank you.

Is this parameter dimensionless or in volts? I've tried many values, but I keep getting a yellow warning icon indicating an error, such as with 0 or 1 or 1.65 or 0.5 

Hi,My actual CubeMX v. 6.17 offers some updates, but these update are for Cube MX 6.18. Cube Mx 6.18 is not available yet. When can we expect the MX update ? St. 

Hi everyone,I am new to Android development, and I have two questions about OpenSTDroid v6.2.0.I followed the official documentation to build OpenSTDroid, but I encountered a build error. The details are shown in the attached error.txt.How to build OpenSTDroid distribution - stm32mpu   For OpenSTDroid, is the Device Tree workflow similar to Yocto? In other words, should the Device Tree be generated by STM32CubeMX and then integrated into the OpenSTDroid source tree?Any guidance or suggestions would be greatly appreciated.Thank you.

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

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?

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. 

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

[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 ?