Solved

Split from the Implementing a LwIP and FreeRTOS™ v1 UDP echo server on the STM32F7 series Tutorial;Moved to the forum for better visibility & discussion.@mƎALLEm Hi Sir,I am using the same code that works correctly on the development board. However, when I run the same firmware on the custom board, I am encountering an error.Is there any issue in the schematic related to Ethernet?Can I use the same libraries that are used in the Nucleo-H755ZI-Q board for this LAN?If I use the same library and it gets stuck at netif_add() what could be the issue?

Hi, I am using CubeMX 6.16.1 to work on a STM32F777ZIT6 target. However, the generated code does not have the Macro definitions of the GPIO pins in main.h. The GPIO init part IN MX_GPIO_Init() is also empty, as follows:/** * @brief GPIO Initialization Function * None * @retval None */ static void MX_GPIO_Init(void) { /* USER CODE BEGIN MX_GPIO_Init_1 */ /* USER CODE END MX_GPIO_Init_1 */ /* GPIO Ports Clock Enable */ __HAL_RCC_GPIOE_CLK_ENABLE(); __HAL_RCC_GPIOF_CLK_ENABLE(); __HAL_RCC_GPIOH_CLK_ENABLE(); __HAL_RCC_GPIOC_CLK_ENABLE(); __HAL_RCC_GPIOA_CLK_ENABLE(); __HAL_RCC_GPIOB_CLK_ENABLE(); /* USER CODE BEGIN MX_GPIO_Init_2 */ /* USER CODE END MX_GPIO_Init_2 */ } I also tried CubeIDE 1.19.0, have the same issue.Did I do anything wrong? I think it is really important to get this function work, as it would be cumbersome to manually init the GPIO pins. I attached the .ioc file, thanks in advance for your help.Thanks,Xiankun

Hello,I am working on the stm32mp257f-ev1 board and attempting to switch from the default USART2 early crash console output to USART6. I've successfully switch TF-A and U-BOOT console to USART6 but my OP-TEE console continuously outputs on USART2.I've made sure to change the serial0 alias from USART2 to USART6 in the OP-TEE device tree (as I've successfully done in the TF-A device tree) and I've also followed the directions to change the header file stm32mp2_def.h For USART6, I've changed the early crash console in stm32mp2_def.h to the following:#define STM32MP_DEBUG_USART_BASE                    USART6_BASE#define DEBUG_UART_TX_GPIO_BANK_ADDRESS    GPIOF_BASE#define DEBUG_UART_TX_GPIO_BANK_CLK_REG     RCC_GPIOFCFGR#define DEBUG_UART_TX_GPIO_BANK_CLK_EN        RCC_GPIOxCFGR_GPIOxEN#define DEBUG_UART_TX_GPIO_PORT                     

On AN4879, STM32N6 is marked as Type E (Universal serial bus full-speed host/device interface) But actually it has 2 HS OTG with phy as high-end line up (2* Type D)  

Hi! I’m starting design of a new board, on which I’d like to use an stm32h7 device. My board will also include an audio codec and usb hs phy.Historically I’ve used crystals to drive HSE of the mcu, but some reference designs I’ve been studying show the use of cmos oscillators to drive the clock. I am curious about the trade offs of this, or how/when I should prefer a crystal over an oscillator?thank you!

Hello,I am returning to STM32 development after about two years and I am preparing a new project that will handle multiple tasks using several peripherals.I have installed STM32CubeIDE version 2.0.0. The installation completes without errors, and I am able to create a new STM32 project. However, after the project is created, the .ioc file does not open

Hi!In version 4 of the reference manual for STM32U0, it is suggested that BOR is enabled and on Level 3 from the factory.Is that correct?I'm currently working on an construction running @ 2V, so it would never start up, if so. And when I read out the Option Bytes on a new MCU, BOR is disabled? https://www.st.com/resource/en/reference_manual/rm0503-stm32u0-series-advanced-armbased-32bit-mcus-stmicroelectronics.pdf

I have some text that should not be translated.If a translation field in the table is empty, is there a way to make it automatically display the text from the first translation box, instead of having to copy and paste the same text into every box?

Edited you post for the Book title in French. Hello, We are pleased to inform you of the publication of a new technical book dedicated to STM32 microcontrollers. Written by three professors at INSA Toulouse (engineering school, France), this book is available in French and English:          Programmation des systèmes embarqués. Application aux μcontrôleurs STM32F10x Microcontrollers - Vincent Mahout, Thierry Rocacher, Guillaume Auriol – ISBN 13: 978-1-83612-004-9 – ISTE Editions – 2024          Programming of Embedded Systems: Applications to SM32F10x μControllers - Vincent Mahout, Thierry Rocacher, Guillaume Auriol – ISBN 13: 978-1786309518 - John Wiley & Sons Inc, 2025 Designed with an educational approach built on 20 years of experience in the field of embedded systems, this book combines essential theoretical foundations with structured and rigorous practical application. It uses a common thread example to illus

I have been using PE micro Multilink FX for several years, but its Linux support is terrible. Is there a ST (or another) alternative with this functionality compatible with stm32CubeIDE? I just need to supply power (up to 100 mA at 3.3V) to my board for debugging. I don't need high tracing performance or anything like that. Thanks in advance,Gaston

In STM32CubeCLT (including latest 1.20.0 version), there is CMake but no make.To build projects from CubeMx gererated make projects, I have to install STM32CubeIDE and add below into PATH.  C:\ST\STM32CubeIDE_2.0.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.make.win32_2.2.0.202409170845\tools\bin Manually install standard GnuWin32 Make is not enough because it miss some additional tools such as rm.exe, mkdir.exe ... 

Hi Team,Issue summary: when button is clicked then other button callback function getting trigger on TouchGFX simulation and same on hardware.Hardware details: STM32F429 Disc1 boardTouchGFX version: 4.24.0UI snip: When I click within area marked in square sky color box which is button area then kitchen callback function is triggered which is fine; but which also covers the 30% around area of Lobby. So when I click on Lobby button which is part of Kitchen button(around 30%) then  kitchen callback function is triggered. So question is how to resolve this isseu.TouchGFX UI screenThanks MR

Hello, rm0456 in chapter 33.4.8. talks about "Software procedure to calibrate the ADC" and "Extended calibration mode" on some products. It is not clear, if "Software procedure to calibrate the ADC" is enough for products with "Extended calibration mode" or  if extended procedure should be done always when available?Please clarify! Thanks

Are the design files of this board available from ST website? I'd need to know where can I get 3.3V and tie it to pin1 (Target VCC) off CN14. Then I'll be able to power the target MCU through this connector. Please check next post for further information:https://community.st.com/t5/stm32-mcus-boards-and-hardware/arm-debug-probe-with-power-to-target-capability/m-p/878207#M29644thanks in advance,Gaston   

For the analysis and working of the gate driver L6491, we need the simulation model of the gate driver L6491 of LTspice or Pspice. Please provide the simulation model as soon as possible. It would be very helpful to us.Thank you!

I am porting Linux to a board that uses the STM32MP255F.I used the BSP from the STM32MP257F-DK board.For now, I was able to get the LCD panel to display, but the weston-graphical-session did not start.When I added the following line to /etc/default/weston, the weston-graphical-session started:OPTARGS=--use-pixmanThe demo menu appears, and I can launch the demos.However, the GPU demos do not run.As I understand it, the OPTARGS=--use-pixman setting is meant for when there is no GPU.Since the GPU demos also do not run, it seems that the GPU is not operating.Under what conditions does the GPU fail to operate?For reference, the Device Tree gpu section is configured as follows:&gpu {contiguous-area = <&gpu_reserved>;status = "okay";};Another thing I am concerned about is that the initialization around usb3dr does not match the custom board, so I have disabled it.&m33_rproc {mboxes = <&ipcc1 0x100>, <&ipcc1 0x101>, <&ipcc1 2>;mbox-names = "vq0",

I am configuring the RTC and using the user button on NUCLEO-H563ZI, but it is not working as expected. When I check the configuration in .ioc, I see that yellow signal in the RTC section. I have checked it and do not understand what is happening.Could someone guide me about that warning and how it affects the operation of the RTC?Thank you in advance.  

Hello guys,I have a stm32G474RET board. I am using tim1 in PWM input mode and i want to update on the fly the hrtimA period and compare values using DMA.  This is the code i have written: // Addresses for HRTIM registers (Timer A) destPER = (uint16_t*)&HRTIM1->sTimerxRegs[HRTIM_TIMERINDEX_TIMER_A].PERxR; destCMP = (uint16_t*)&HRTIM1->sTimerxRegs[HRTIM_TIMERINDEX_TIMER_A].CMP1xR; // Start DMA transfers in circular mode HAL_TIM_IC_Start_DMA(&htim1, TIM_CHANNEL_1, destPER, 1); HAL_TIM_IC_Start_DMA(&htim1, TIM_CHANNEL_2, destCMP, 1); HAL_HRTIM_WaveformOutputStart(&hhrtim1, HRTIM_OUTPUT_TA1); HAL_HRTIM_WaveformCounterStart(&hhrtim1, HRTIM_TIMERID_TIMER_A); HAL_TIM_IC_Start(&htim1, TIM_CHANNEL_1); HAL_TIM_IC_Start(&htim1, TIM_CHANNEL_2); My problem is that the period of the hrtim is changing dynamically based on the input PWM signal, but the CMP1 doesn't. The only thing I could find is that when i tried to configure the channel 2 of tim

I am developing a product using the NUCLEO-N657X0-Q dev board and have generated the configuration setup from CubeMX and developed the code in the CubeIDE. When I need to layout my own circuit board I will want to use the STM32N657A0 variant which has 169 pins and I was wondering if I am able to use CubeMX to change the existing configuration done for the Nucleo board to the STM32N657A0 169 pin device without destroying the code I have already developed? I have written the code using resources and pin outs available on the STM32N657A0 device but the actual pins are different on the two devices so need to know if I can make the transition using CubeMX or whether it will have to be done manually?

Setup Details:Board: STM32H750B-DK Discovery KitSTM32CubeIDE: Version 2.0.0 (Build 26820_20251114_1348 UTC)STM32Cube FW_H7: v1.12.1STM32CubeMX: v6.16.0TouchGFX Designer: v4.26.0 (MVP pattern)External Memory: 1GB QSPI Flash (MT25TL01G) + 8MB SDRAMProject Configuration:Created TouchGFX project in Designer, saved and generated codeOpened .ioc file in STM32CubeMX v6.16.0Configured:QSPI in memory-mapped mode with 30-bit addressing (1GB flash)SDRAM via FMCMPU configured with QSPI region execution enabled (0x90000000, 256MB)Vector table relocated to 0x90000000Linker script modified for external flash executionThe Problem:Debugger fails with protocol error when attempting to debug:Error in final launch sequence: Failed to execute MI command: monitor reset halt Protocol error with Rcmd Failed to execute MI command: monitor mww 0xE000ED08 0x90000000 Protocol error with Rcmd Failed to execute MI command: monitor reg pc 0x90000004 Protocol error with RcmdWhat Works::white_heavy_check_mark: Code pr

Since I upgraded to version 3.6.4 of STM32CubeIDE for Visual Studio Code, the style used for automatic code formatting has changed. For example, curly braces are now inlined, not wrapped as they were before.How can I revert to the old style? 

Dear Community,I think I have encountered an uncommon problem. The SW_RESET bit in CTRL3 on the lsm6dsv16x does not change to 0 again. In https://www.st.com/resource/en/datasheet/lsm6dsv16x.pdf it states that after the software reset this bit is automatically cleared. Even after disconnecting the power and doing a reboot, also of the chip itself this bit wont change back to 0. I use https://github.com/STMicroelectronics/lsm6dsv16x-pid to communicate with the chip, and other things like reading who_am_i and so on work normally. But otherwise, I only get meaningless readings from the sensor. What can be done about this, especially the reset bit?Thanks and greetings

Hello,I am trying to implement the Mifare Classic protocol with ST25R3916 and RFAL.For that CRC and parity bits processing need to be disabled, which ST25R3916 support, so I tried to experiment with disabling CRC and parity framing on a message sent by the tag to see how it is encoded.I am having a hard time figuring out exactly what's the encoding, and the datasheet of ST25R3916 doesn't say exactly what's in the FIFO.I set up X-CUBE-NFC6 with STM32CubeMX and simply modified the polling demo to send the command 6000 + CRC to the tag, which should respond with a 4-bytes nonce with standard ISO-14443-3A parity and no CRC.This is the only part of the code I added, after selecting the ISO-14443-3A tag:uint32_t flags = // CRC stuff RFAL_TXRX_FLAGS_CRC_TX_AUTO | RFAL_TXRX_FLAGS_CRC_RX_MANUAL | RFAL_TXRX_FLAGS_CRC_RX_KEEP | // parity bits RFAL_TXRX_FLAGS_PAR_RX_KEEP | RFAL_TXRX_FLAGS_PAR_TX_AUTO | // analog RFAL_TXRX_FLAGS_AGC_ON; uint8_t tx_buf[8] = {0x60, 0x00}; // use key A on blo

I just downloaded the Cube IDE (v2.0) and none of the tutorials will play in it, none of the tutorials online match this IDE and I do not have the MX tool because ST said it was included in the Cube IDE. I'm ready to delete all of this mess or can anyone point me to current (as of today, 2/2026) methods to start from scratch.  BTW, yes, I have seen how to import 'older' projects, I've read several other posts, but if ST is serious then the tools ought to work properly or I'd have to consider them (ST and their tools) to uncared-for; i.e. is ST disinterested in selling us some MCUs even if we can't get started with THEIR tools. Either the tools should work and the site's info should be correct or we will have no choice but to look elsewhere. There are plenty of MCUs around these days.

 I'm implementing a children's game board with 6 spaces to place nfc tags with 6 antennae multiplexed as described in AN6121 - which is a great application note and ideal for what I'm doing!   I've done rf and speed layout before but not anything for NFC and I'm a bit confused by a couple of things:- looking at the photos of the board in AN6121 there seems to be a thick and thin trace going to each antenna, and also a thick trace on the back of the board,  none of these look like a differential trace to me, is it just not that critical in this application or am I missing something here?  I wondered if the thick traces on opposite sides of the boards were matched to each other?- secondly I'm reading this "As shown in Figure 14, each antenna has its switching system close to the ports. This matching network is located directly on these ports."  to mean the switching should next to the loop antenna,  but this would leave 5 pairs of traces to nowhere and