STM32 MCUs Embedded software

Problem:HAL_FLASHEx_Erase returns error 0x20000, and HAL_FLASH_Program does return HAL_OK but does not actually write any data to the flash.Goal: Erase and install new firmware on flash on its own inside the bootloader.I am developing a bootloader for the STM32H533RET6. I have TrustZone enabled, and configured the secure and non-secure regions. I am trying to erase and write to the non-secure part of the flash, from the bootloader which is secure (and separate from the actual application). I have disabled any write protection that I am aware of inside the option bytes. I also use the Memory Management Tool inside CubeMX to configure the secure and non-secure regions. For the non-secure region of the flash I have set "Access Permissions" to "RW by any privilege level". I do have a Flash watermark set on bank 1 but this does not cover any of the non-secure flash regions. No watermark is set on bank 2. Below is the code I use to erase and write to a sector on the flash:uint32_t Erase

Hello, While working with STM32F446RET6, I encountered a problem with I2C1. When using HAL_I2C_Mem_Read_IT(), an error occasionally occurs in the form of sending 0x00 instead of the address with the read bit after Repeated Start. The error seems to only occur with O3 optimization. I2C Configuration: NVIC Configuration: Only TIM1 update interrupt (TIM10 not used), DMA1 stream2 (SPI3_RX) and DMA1 stream5 (SPI3_TX) have higher priority than I2C1. Here is an example of a correct signal: The signal with error and I2C_Flush_DR() looks like this: static void I2C_Flush_DR(I2C_HandleTypeDef *hi2c) { /* Write a dummy data in DR to clear TXE flag */ if (__HAL_I2C_GET_FLAG(hi2c, I2C_FLAG_TXE) != RESET) { hi2c->Instance->DR = 0x00U; } } The signal and I2C_Flush_DR() looks li

Hello everyone,I am working with the NUCLEO-H723ZG board and attempting to establish Ethernet communication using TCP/IP. The firmware was built and flashed successfully using STM32CubeIDE version 1.19.0.However, I am facing issues with basic network connectivity. Below are the details of my setup and observations:Setup DetailsBoard: NUCLEO-H723ZGIDE: STM32CubeIDE v1.19.0Ethernet stack: LwIPPHY interface: RMIIFlashing tool: ST-LINK (onboard)Test performed: Ping test from PCObserved BehaviorThe Ethernet port LEDs (orange and green) remain solid ON after connecting the Ethernet cable.Ping requests consistently fail (Request timed out).No response is received from the board.Troubleshooting Already PerformedTested both Static IP and Dynamic IP (DHCP) configurations.Verified IP address, subnet mask, and gateway settings.Tried multiple Ethernet cables to rule out cable-related issues.Rebuilt and reflashed the project multiple times.Verified that the firmware flashes successfully and runs wit

Hi everybody,I'm learning to use the ADC in a STM32F411CEU in Continuous Mode and Single Conversion with Polling. When the code is downloaded to the MCU everything runs ok (I mean, when the MCU runs by itself without any ST-Link connected).The problem appears when I try to execute the code in a debugging session. The first time the function HAL_ADC_PollForConversion() is called, the result is HAL_OK, but in the next iterations the functions doesn't return HAL_OK anymore.I know, I know, with Continuous Mode I should be using DMA. But I'm trying to learn the different operation modes (single conversion, scan mode, polling, DMA, etc.)One thing I've found is that if I set the ADC parameter End Of Conversion Selection = EOC flag at the end of all conversions instead of End Of Conversion Selection = EOC flag at the end of single channel conversion , then the function HAL_ADC_PollForConversion() works ok in all the iterations when debugging. Can anybody explain m

I am trying to create a simple UDP server using the NUCLEO-H743ZI2 board. I will port this to a similar microcontroller in the same family (STM32H750B) once I get it working. I am able to build the example code from this repository: https://github.com/stm32-hotspot/STM32H7-LwIP-Examples/tree/main/STM32H743_Nucleo_ETHIt successfully responds to pings and shows up in my router device list. I used:STM32CubeIDE Version: 1.17.0 STM32Cube FW_H7 Version 1.12.1.Following the instructions in the README, I attempted to build the application from scratch on the NUCLEO board, but I haven't been able to get it to respond to a ping despite a few days of troubleshooting. Can someone tell me if there is something wrong with my configuration file? 

Hi, two years ago I posted this thread:Solved: How to set "Don't fragment" flag LWIP short TCP pa... - STMicroelectronics CommunityNow I just was reviewing it for another application that truly needed to send more data and was not allowed to wait 50ms for every sent packet.Final root cause explanationThe 415-byte packets were being ACKed after ~40–50 ms because I was only sending one TCP segment at a time and waiting for it to be acknowledged within my application code, before sending the next one.This behavior is due to the TCP Delayed ACK algorithm implemented by Windows. When Windows receives a single TCP segment smaller than the MSS, it does not immediately send an ACK. Instead, it waits approximately 40–50 ms before acknowledging it.This behavior is described in RFC 1122, section 4.2.3.2 ("When to Send an ACK Segment"), which explains that a TCP implementation may delay sending an ACK in order to reduce protocol overhead.If a second TCP segment is received before the delayed ACK t

Controller: STM32F303ZEWritten a function to read ROM memory as belowvoid ServiceROMRead(tst_ServiceDataset* ptrService){// Variable holds ROM addressDWORD ROMAdd = DIAG_ZERO;// Flag represents JUP service trigger state.RFJupExeFlag = TRUE;// Address from where the data needs to be readROMAdd = ptrService->DataAddr;//Check for the EEPROM addressif((ROMAdd > ROM_ENDADD)) //ROM_ENDADD is 0x0807AFFF{// wrong addressptrService->State = WRONG_DATA;//Indicator for wrong address passed}else{ptrService->ptrData = (BYTE *) ptrService->DataAddr;}}When I pass ptrService->DataAddr as 0x8000020 or 0x8000080 to the above function ServiceROMRead from my application it is sometimes leads to a system resetApplication is placed at 0x08003000 to 0x0807AFFFBootloader is placed at 0x08000000 to 0x08002FFF1. Why is the controller resetting when I try to read ROM from address 0x8000020 or 0x8000080?2. Will trying to read data from address 0x8000020 or 0x8000080

HelloI have a STM32H7R3V8T6 and want to use a few peripherals and GPIOs. However, I don't manage to see an output with my analyzer. The peripherals themselves seem to work: An XSPI receive for example does receive some dummy bytes and takes exactly the required time for the transfer (measured with the cycle counter), but the pins do not show anything.I reduced my code and came up with this simple demonstration of how I initialize a GPIO:int main(void) { SystemCoreClockUpdate(); HAL_Init(); SystemClock_Config(); __HAL_RCC_GPIOB_CLK_ENABLE(); GPIO_InitTypeDef GPIO_InitStruct = {0}; GPIO_InitStruct.Pin = GPIO_PIN_12; GPIO_InitStruct.Mode = GPIO_MODE_OUTPUT_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_LOW; HAL_GPIO_Init(GPIOB, &GPIO_InitStruct); while (1) { HAL_GPIO_TogglePin(GPIOB, 12); HAL_Delay(10); } }The debugger shows that I reach the loop. The registers of the peripheral seem to be correct, but the pin doesn't toggle. This als

HelloI'm developing on the NUCLEO-N657X0-Q board using the STM32N657X0H3Q.I'm trying to trigger the ADC when the CCR value on CH2 of TIM1 meets the up counter of TIM1. This triggers the ADC conversion. Once the ADC conversion is complete, a callback function is triggered to store the ADC value in a variable. To verify the callback function's operation, I'm trying to toggle the GPIO.When I debug and observe the waveforms, I see the waveforms on CH1 and CH2 of TIM as designed. However, the problem is that the GPIO toggles aren't observed. When I check the ADC values ​​in debug mode, the g_adc_raw value is stuck around 1290 and the g_adc_mv value is stuck around 566. Connecting the ADC pin to GND doesn't return 0.The STM32n6 example, ADC_SingleConversion_TriggerTimer_DMA, works normally, so there seems to be nothing wrong with the board itself.I plan to control the DC-DC converter, so I need to read the value for each ADC conversion and run the controller, so I don't think DMA is necessar

Вітаю. Створив DC-DC перетворювач на мікроконтролері G4 серії. У я кості регулятора використовую апаратний FMAC, current mode. Моє питання стосується перерегулювання рівня вихідної напруги при старті перетворювача. На борту маю апаратну кнопку вимкнення живлення, а саме фізичне від'єднання акумулятора від перетворювача, а також тактові перемикача для користувача, якими безпосередньо вмикається та вимикається процес перетворення, та налаштування користувачем деяких параметрів. М'який старт програмно не реалізовано. Ситуація наступна, перший пуск перетворювача після увімкнення кнопкою живлення проходить бех перерегулювання, що я можу підтвердити осцилограмами. А ось усі наступні пуски супроводжуються короткотривалим перерегулюванням рівня вихідної напруги. Будьласка, хто має бажання мені допомогти, відгукніться, за запитом надам усю необхідну інформацію. Осцилограми хочу скинути наступним постом.

Hi,I was wondering if there's any reference application or if you have any advice on drivers to capture video from a MIPI CSI-2 image sensor (perhaps Sony or the ST BrightSense image sensors (VB1940 (active) or VD1940 (preview) match the 5.1 MP dimensioning of the STM32N6) with STM32N6x7 or STM32N6x5 μCs?The aim would be to waken up the STM32N6 in response to an external digital input, record video from a MIPI CSI-2 image sensor to SD or eMMC then return to sleep mode.I'd be happy to consider bare metal, Zephyr or FreeRTOS - whatever you recommend.Thank you very much for your help and all the best for 2025!Will

Dear ST Community,I'm experiencing an issue with USBX Host implementation on STM32H573RIT6 where disconnect events stop working after enabling Host Controllers FS in CubeMX.Problem DescriptionEnvironment:MCU: STM32H573RIT6 (Custom board)Middleware: Azure RTOS USBX + FileX (MSC Host)VBUS: External constant 5V supply (no USBPD/VBUS sensing used)Connection detection: DP pin basedCubeMX: UX Host FS + Host Controllers FS enabledHAL setting: hhcd_USB_DRD_FS.Init.vbus_sensing_enable = DISABLEBehavior:Before USBX activation: Both HAL_HCD_Connect_Callback() and HAL_HCD_Disconnect_Callback() work perfectly with USB memory stick connect/disconnectAfter USBX Host Controllers FS activation:Initial USB memory connection: HAL_HCD_Connect_Callback() works fineUSB memory removal/reconnection: No HAL_HCD_Connect_Callback() and HAL_HCD_Disconnect_Callback() calledQuestions/RequestsHow to maintain HAL HCD callbacks when using USBX Host Controller

  After more debugging, the jump function works correctly (PC reaches 0x080208xx, SP and RST are valid), but the app never sends any UART message after jump — even with SystemClock_Config() completely commented out and only HAL_Init() + MX_UART_Init() remaining. The bootloader resets the clock to HSI before jumping. SCB->VTOR is set in SystemInit(). Linker is at 0x08020000. The app works perfectly when flashed directly at 0x08000000 via ST-Link. Something is killing the app immediately after the bootloader jumps but we can't figure out what — any ideas?this is the project : https://github.com/said-sketch/Flashing-by-UART---STM32-Bootloader/tree/main  

use stm32h743 with eth and a LTE moderm.OS theadx and netxduo ....eth works well I can't find where to congfig ppp, How to select serial port ,and so on.I search the  forum and find no answer.

求助篇！使用主控芯片STM32F405RGT6 在操作flash后 复位指令不起作用 这是什么问题呢？////////////////////以下是代码段/////////////////////////////*注释以下语句就可以自动复位成功*/Translation:I'm using STM32F405RGT6 microcontroller, the reset command doesn't work after flash operation. What could be the problem?HAL_FLASH_Unlock(); if (HAL_FLASH_Program(TYPEPROGRAM_WORD, FWR_ADDR, 0) != HAL_OK) { printf("Clear OTA flag error\n"); } else { HAL_Delay(10); uint32_t flag_sttus = HAL_FLASH_GetError; if(flag_sttus & HAL_FLASH_ERROR_PGA) { printf("flash_err!\r\n"); } printf("Clear OTA flag\n"); } HAL_FLASH_Lock();请各位大佬看看是什么情况 感谢！！！！Translation:Could someone please take a look and tell me what's going on? Thanks

To follow up this thread, CTS signal on USB CDC - STMicroelectronics Community I'm experiencing a similar issue. USBser.sys  have some problem 1. Only DTR Break can control alone you can set  DTR is 1  or 0,  but  RTS have change，RTS only change with DTR. 2.  CDC Serial State I  have test this code,  it  send from Endpoint 81h successfully,  but  PC USB Host  have no message CDC_IN_Buf[0] = 0xA1; /* bmRequestType 0xA1 (10100001B) */ CDC_IN_Buf[1] = 0x20; /* 0x21 (SERIAL_STATE) */ CDC_IN_Buf[2] = 0x00; /* wValue LowByte */ CDC_IN_Buf[3] = 0x00; /* wValue HiByte */ CDC_IN_Buf[4] = 0x00; /* wIndex LowByte Default 0 */ CDC_IN_Buf[5] = 0x00; /* wIndex HiByte */ CDC_IN_Buf[6] = 0x02; /* wLength LowByte Serial State Length 0x0002 */ CDC_IN_Buf[7] = 0x00; /* wLength HiByte */ CDC_IN_Buf[8] = 0x14; /* Data LowByte */ CDC_IN_Buf[9] = 0x00; /* Data HiByte */ /* CDC Serial State bit define (USB CDC 1.1 6.3.5 ) bit0 bRxCarrier 0x

Hi everyone,I’m working on an STM32U5G9 using USBX + ThreadX.I was able to make the device work as:MSC onlyCDC-ACM onlyMSC + CDC-ACM simultaneouslyThat part is fine. What I need now is more dynamic behavior: start the device as MSC, and when a button is pressed, stop USB, change the class to CDC-ACM and restart it (long term I’d like to switch arbitrary combinations of classes, but for now switching from MSC to CDC-ACM is the goal.)From what I understand, I must stop USB so the host will re-enumerate using the new device descriptor, and I’m OK with that. However, every approach I tried ends in a HardFault when I restart with the other class. I suspect I’m missing a call or doing things in the wrong order.How I start the device (this works):/* Start device with MSC only (initial boot) */ /* First I insert CLASS_TYPE_MSC is "UserClassInstance" variable in ex_device_descriptors.c (not shown here), then: */ ux_device_stack_initialize(...); /* Register MSC-only */ ux_device_stack_class_regi

I am working with [STM32F439ZI] and I am trying to initialize SDIO in 4-bit mode.I'm following "STM32 – Creating a File System on a SD card" this video for reference.However, SDIO initialization is failing during the power-on phase.The error occurs during HAL_SD_Init()The failure happens inside the power-on initialization sequenceThe function always returns an error statusThe board is currently tested using the DATA3 line only (this is the only difference from a standard setup)Even when I modify the function / test return values, the error still occurs at power-on initializationI changed the function for card detect so that the return status is always "card present".The error occurs inerrorstate = SDMMC_CmdAppCommand(hsd->Instance, 0);if(errorstate != HAL_SD_ERROR_NONE){return HAL_SD_ERROR_UNSUPPORTED_FEATURE;}}This function returns a CRC error.I have attached the hardware changes I did along with the clock config settings and sdio settings. Please help me resolve it.

  Hello ST Team, I developed a custom USB DFU HOST class on an STM32F446ZE. I soldered a USB-C cable directly to the D+/D-, 5V and GND pins. The Problem: The stack works correctly for transfers up to 128 bytes. However, when I set phost->Control.setup.b.wLength.w > 128 (e.g., 192 bytes) and call USBH_CtlReq, the code enters an infinite loop inside USB_WritePacket. I have traced the execution line-by-line, monitoring the HCTSIZ register values: size (Transfer Size) and cnt (Packet Count). Below is the detailed trace comparing a working 128-byte transfer vs. a failing 192-byte transfer. 1. Successful Scenario: Transferring 128 Bytes Initial State: size = 128, cnt = 2. Loop Iteration 1: i=15: USBx_DFIFO written. Register updates: size = 64, cnt = 2. i=31: USBx_DFIFO written. Register updates: size = 64, cnt = 1. Loop Iteration 2: Initial State: size = 128, cnt = 2. i=15: USBx_DFIFO written. Register updates: size = 64, cnt = 1. i=31: USBx_DFIFO written. Re

Using DMA to read 3 ADC channels. IN0, VSENSE & VREFINT all enabled in CUBEMX. First 2 channels read as expected but for VREFINT it seems to always read zero. Am I missing a setting in the CUBEMX?

Dear Sirs, we had a project with the F2 using HAL_I2C_Master_Sequential_Transmit_IT() with Option I2C_FIRST_FRAME and a second HAL_I2C_Master_Sequential_Transmit_IT() with Option I2C_LAST_FRAME.All worked perfect.Using this Software with a F7 did not work. After the first HAL_I2C_Master_Sequential_Transmit_IT() with Option I2C_FIRST_FRAME a STOP-Condition occured and transfer stopped. After hours of debugging through the HAL it turned out that I2C_FIRST_FRAME does notz set the RELOAD bit but I2C_FIRST_AND_NEXT_FRAME does and all workes fine.So my question is: What is the usage of I2C_FIRST_FRAME in a F7 context, becuase it sets AUTOEND and nothing else. So how can be I2C_FIRST_FRAME the correct option for a sequence of frames?best regardsAndy

Hello,I am working on SRM motor development for some application and plan to use the STEVAL-CTM015V1 (1 kW, 400 VDC, 3-phase SRM) evaluation board for in-house testing.I have reviewed UM3174 and DB4559, but I could not find any SRM control firmware or example project for this board.Could someone please clarify:Where can I obtain the SRM firmware / example source code for STM32F303CBT6 used on STEVAL-CTM015V1?Is there a ready-made SRM control algorithm (current chopping, turn-on/off angles, speed loop) provided by ST?How is this board intended to be programmed? (recommended IDE / reference project)Any guidance or pointers to official ST resources would be appreciated.

There is a bug in the above mentioned function in stm32f1xx_hal_flash_ex.c file. The function has a uint32_t type parameter WriteProtectPage which determines the flash page chunks to disable the write protection of. On my F103 MCU it means every bit corresponds to 4 pages (each page is 1 Kbyte, total of 128 Kbyte flash memory). This line then combines the currently write protected pages with WriteProtectPage (0 means protected, 1 means unprotected):WriteProtectPage = (FLASH_OB_GetWRP() | WriteProtectPage); The function then slices WriteProtectPage up into 4 pieces (4 WRP option bytes):WRP0_Data = (uint16_t)(WriteProtectPage & OB_WRP_PAGES0TO31MASK); WRP1_Data = (uint16_t)((WriteProtectPage & OB_WRP_PAGES32TO63MASK) >> 8U); WRP2_Data = (uint16_t)((WriteProtectPage & OB_WRP_PAGES64TO95MASK) >> 16U); WRP3_Data = (uint16_t)((WriteProtectPage & OB_WRP_PAGES96TO127MASK) >> 24U); It then erases the option byte area (r

Hello, when STM32CubeIDE generate code for STM32H523VCT6, VTOR_TABLE_NS_START_ADDR constant contain wrong value:#define VTOR_TABLE_NS_START_ADDR 0x04020000UCorrect value should be #define VTOR_TABLE_NS_START_ADDR 0x08020000U How to reproduce:STM32CubeIDE Version: 1.18.1STM32Cube FW_H5: 1.5.0Start new project -> for commercial part number select STM32H523VCT6 -> enable trust zone -> generate code.Check file main.c under secure directory. Regards,Slavomir Tomascik 

The conclusion is that setting filters and interrupts on FIFO0 leads to exception handlingFDCAN1_IT1_IRQHandler.The reason for this behavior is an error in the file. startup_stm32g431cbtx.s ERROR ...word ADC1_2_IRQHandler.word USB_HP_IRQHandler.word USB_LP_IRQHandler.wordh FDCAN1_IT0_IRQHandler.word FDCAN1_IT1_IRQHandler.word EXTI9_5_IRQHandler.word TIM1_BRK_TIM15_IRQHandler   ..   This is how it should be ... .word ADC1_2_IRQHandler.word USB_HP_IRQHandler.word USB_LP_IRQHandler.word FDCAN1_IT1_IRQHandler.word FDCAN1_IT0_IRQHandler.word EXTI9_5_IRQHandler.word TIM1_BRK_TIM15_IRQHandler ...       As an example, the code that I use is for testing so that there are no questions). void CAN_Config(void) { FDCAN_GlobalTypeDef *CAN = FDCAN1; uint32_t *filterRAM = (uint32_t *)RAMBaseFDCAN1; // Включение тактирования для CAN RCC->APB1ENR1 |= RCC_APB1ENR1_FDCANEN; RCC->CCIPR &= ~RCC_CCIPR_FDCANSEL; // PLL "Q" for FDCAN RCC->CCIPR |= (0x1 <<