STM32 MCUs Products

Hello,I implemented a virtual com port using the usbx stack for the stm32U575 in standalone mode and it basicaly works.My problem is that I just can't put more than 8 bytes in the TX buffer at the time. If I do the program gets stuck (in the main loop)I tried both: ux_device_class_cdc_acm_write_with_callback and ux_device_class_cdc_acm_write_runbut they only work when the buffer length is less than 8 bytes.I have the following code in app_usbx_device.c: /* USER CODE BEGIN MX_USBX_Device_Init1 */ /* Initialize the USB Peripheral */ MX_USB_OTG_FS_PCD_Init(); HAL_PCDEx_SetRxFiFo(&hpcd_USB_OTG_FS, 0x80); HAL_PCDEx_SetTxFiFo(&hpcd_USB_OTG_FS, 0, USBD_MAX_EP0_SIZE / 4); HAL_PCDEx_SetTxFiFo(&hpcd_USB_OTG_FS, 1, USBD_CDCACM_EPIN_FS_MPS / 4); HAL_PCDEx_SetTxFiFo(&hpcd_USB_OTG_FS, 2, USBD_CDCACM_EPINCMD_FS_MPS / 4); /* Link the USB drivers with the USBX DCD and check if it return

I am working on an  application where I plan to relocate all non-safety modules to the CM4 core. To achieve full safety, I need a mechanism to lock the peripherals so that the CM4 core cannot access any peripherals configured in the CM7 core, including multiple instances of SPI, UART, I2C, CAN, and GPIO (on register level).As per the reference manual, I did not find a mechanism to lockout specific cores.One alternative I tried is using the Memory Protection Unit (MPU). However, my investigation revealed that the CM4 MPU can lock CM4 from accessing only 6 regions. Given that we have more than 6 regions, configuring the MPU seems insufficient based on our requirements. Can it be done with MPU or Is there any alternatives for this ? 

Can anyone comment on the prologue and epilogue of following CM7 code, particularly the content of r7 when the routine returns? { 0: b480 push {r7} 2: af00 add r7, sp, #0 if ((ANADIG_MISC->MISC_DIFPROG & ANADIG_MISC_MISC_DIFPROG_CHIPID(0x10U)) != 0U) 4: 4b0b ldr r3, [pc, #44] @ (34 <RamBased_ROM_API_Init+0x34>) 6: f8d3 3800 ldr.w r3, [r3, #2048] @ 0x800 a: f003 0310 and.w r3, r3, #16 e: 2b00 cmp r3, #0 10: d005 beq.n 1e <RamBased_ROM_API_Init+0x1e> { g_bootloaderTree = ((bootloader_api_entry_t *)*(uint32_t *)0x0021001cU); 12: 4b09 ldr r3, [pc, #36] @ (38 <RamBased_ROM_API_Init+0x38>) 14: 681b ldr r3, [r3, #0] 16: 461a mov r2, r3 18: 4b08 ldr r3, [pc, #32] @ (3c <RamBased_ROM_API_Init+0x3c>) 1a: 601a str r2, [r3, #0] } else { g_bootloaderTree = ((bootloader_api_entry_t *)*(uint32_t *)0x0020001cU); } } 1c: e004 b.n 28 <RamBased_ROM_API_Init+0x

Hi Team,I am observing a shift in a data each time i am sending same data from ESP8266 master to STM32f103RCT6 slave controller but each time i am getting different data and seems to be the shifted data as i can see some part of strings sent. I have observed with the logic analyzer and it is showing same data each time. I have attached the project and logic analyzer traces and data printed over putty from stm32 MCU, Please check the SPI configuration if i am doing anything wrong. Please help debug this issue. Thank you in advance! Best Regards,Aadesh

Hi everyoneI'm using a STM32F401RCT6 to control a valve actuatorThere is a counter of number of cycles for the actuator (RunTime), and when its value changes, the value of that counter must be stored in the memory for tracking and support.The actuator is powered by an external power supply and additionally there's a battery in case the power fails.In some rare cases, the memory storage process is corrupted, and we lose the complete storage values previously saved.We are trying to replicate the fail, but it is really impossibleDo you have any idea of what can cause that loss of information in the memory and how could we replicate this failure in order to fix the bugbelow is part of the code that writes to memoryThank you very much int WriteToFlash(bool force) { uint8_t NibleH=0; uint8_t NibleL=0; int16_t AuxData=0; uint32_t Variable_Guardar; uint32_t PAGError = 0; FLA

I tried flashing a project created for the STM32H745I-DISCO board in CubeMx. The only change I made was disable a few unused peripherals, enable memory caching. I set the clock speed for the M7 core to 480MHz and the M4 core speed to 240MHz. I added a couple of lines of code to blink the LD1 LED in the CM7 project and blink the LD2 LED in the CM4 project. Programming CM7 from IAR went ok and I was able to observe the LD1 LED blink, but once I programmed the CM4 core, the board stopped being recognized by IAR and the ST-Link utility. The ST-Link still works (the ST-Link utility can see its serial number and a USB mass storage device shows up in the file system when I connect the board to the USB port), but neither IAR nor ST-Link utility can recognize the target device (the MCU). The ST-Link utility says "Detection Failed" under "Target" on the Settings dialog. I checked my ST-Link utility setup by connecting an identical Discovery board to my computer, and it worked well. What can I

Hi, I want to do something extremely basic. Trigger a pulse using software for Timer 1 which is configured in Retriggerable One-Pulse Mode. Background: I can do the above if the Timer 1 is in normal One-Pulse mode. By simply Writing the CEN bit in TIM1->CR1. Now, as soon as n set me registers to the above settings I cannot generate a pulse using Software. I don't want to go and mess with timer settings after I've triggered a manual software pusle to "brute" force the solution. I have confirmed with my debugger that CEN is i

Greetings to the community,I have a problem with creating a firmware for the bootloader. I'll start a little differently:Some time ago I made a bootloader for STM32F407VET6. The only thing I did was change the memory length in the STM32F407VETX_FLASH.ld file to:FLASH (rx) : ORIGIN = 0x8000000, LENGTH = 16Kand after jumping to the FW I jump to the correct addressIn the FW I changed the STM32F407VETX_FLASH.ld file:FLASH (rx) : ORIGIN = 0x8004000, LENGTH = 496Kand in the main.c file I added the line:int main(void){/* USER CODE BEGIN 1 */SCB->VTOR = 0x08004000;/* USER CODE END 1 */......Everything works without any problems, even when I run the debugger from FW, the bootloader is not deleted and the program jumps directly to the FW address. I am satisfied.Now I am making a bootloader for STM32F103C8T6, I proceed exactly the same way and nothing works. The program is correctly written to the

Hello,In one of our products we've moved from a PIC32 to a STM32F7. The product is self powered and has a USB connection (USB-Device Full-Speed, HID). Everything works as expected normally. Sometimes however, when I plug in the USB cable, I get an error on Windows "USB device not recognized" and the connection will not work. When this happened once, the USB will not work anymore even if I reconnect the device again. It does also not help when using another USB port on the PC or even connect the device to another PC. The only thing that helps is resetting our device.I have added some loggings inside the usbd_core.c file. When unplugging the cable, USBD_LL_Suspend will get called once. When Inserting the USB cable, I see multiple USBD_LL_Resume / USBD_LL_Suspend (about 3 each most of the time). When the device is in the "error mode" I get a ton of USBD_LL_Resume when plugging in the cable until the windows message that the device is not r

This is my setup, STLINKV3+CubeProgrammer (trough CAN) accesing Systembootloader of stm32f405RGIt doesnt work.Ive tried no Canbus transceiver , digital connection with the onboard diodes from STLINK expansion (blue pcb) and everything works fine. Maybe im messing up the STLINKV3 wiring?

Hello, I new to STM32Cube IDE and am starting out with the STM32F031C6T7 device. My development computer at work does not have an internet connect so I must download any required software and manually install it. How do I manually install the following:I ask because when I try to create a project for the STM32F031C6T7  device I get the following warning: I believe it wants the file "Patch for STM32CubeF0" installed b

Posted on November 30, 2015 at 13:35Whats the internal resistance of SYS_WAKEUP pin when in standby mode...? I dont see any info about it in reference manuals..   #stm32-power-mod #standby

Hello,I am trying make a USB device MSC.It works fine with SD card, but I want both SD card and flash.( I set max_lun to 1.)I have wrote the SPI_Flash_Write and  SPI_Flash_Read that can be called by MAL_Write and MAL_Read.It seems work fine cause I can format the flash disk on my computer and put files into the disk.However, everytime I turn off my board and turn on it, it ask me to format the disk again and again.I have searched many solutions. Someone said that I should use FATFS f_mkfs to format first.I tried but not worked , is that true or any other problem I missed ?  Regards,thonsha 

Hello, i have an stm32h723zgt6 project and sd is not working, i tried modifying my code to write to the card and it doesn't work/* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2025 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file * in the root directory of this software component. * If no LICENSE file comes with this software, it is provided AS-IS. * ****************************************************************************** */ /* USER CODE END Header */ /* Includes ------------------------------------------------------------------*/ #include "main.h" #include "dac.h" #include "fatfs.h" #include "memorymap.h" #include "sdmmc.h"

Hi there, I am designing a product using an STM32H7RS-series MCU, and am looking for some clarification about the operation of the HSE oscillator. I see the H7RS has the option of an "analog" external oscillator in HSE bypass, in addition to the usual "digital" HSE bypass of previous products, and I am very interested in using that analog mode to use a lower voltage clipped sinewave output external oscillator, such as an NDK NT2016SE. My question is do I need anything in series between the STM32H7RS OSC_IN pin and the output pin of the analog (clipped-sine in this case) TCXO? I would assume I'm not supposed to use a series capacitor like the datasheets of these oscillators tend to show, because the STM32H7RS appears to be looking for a DC-biased signal, but before I make a board with no provision for such an inline passive and find out it doesn't work I figured I should double check here. Thanks!

Hi, to whom it may be concerned,I have a question about how to debug. I recently moved my successed project from stm32u585ci without smps with QFN to this lower mass and lower power consumption package, stm32u585ciy6qtr. This is my first time doing smps, and I think I wrongly connected the vss_smps directly to one of the vss. And I did not put extra 0.1uf caps for VDD_11, only those 2.2uf.  Because of the fabrication limits, we only have two layers of FlexPCB.I can see that the I2C2 and I2C3 work well, but ONLY I2C1 is blocked when the core is doing the computing work, and the ramp-up time is more than 1000ns in the oscilloscope. Even after we used a very small (<300ohm) value pull-up resistor and closely connected to the i2c1 pin area, the I2C1 still has a very high ramp-up time (fast mode) and will be blocked by core computing. However, the I2C1 can send out data by DMA. Then, I tried reconnecting the VLX_SMPS, VDD_SMPS, and VSS_S

I am using a custom board which is using stm32l4r9aii6 as the main microcontroller . The full name of the microcontroller is following :- stm32l4r9aii678a3n . The firmware for this board was developed on stm32l4r9 discovery board which uses the following controller :- stm32l4r9aii6u78a5u . The problem i am facing in my dev board are following:1. The first issue is if i enable any of the interrupts my code breaks and the lr and pc value goes to an undefined location outside of flash memory after the code runs for a few seconds . 2. No hard fault handlers get triggered when this happens Please let me know if any of you have faced similar issues or if you need any more data to know what might be happening

 As shown in the screenshot below. RUN_PD bit is mentioned here and nowhere else in the entire Reference manual.  

 Good morning everyone!I'm working on a project involving FreeRTOS, lwip, and Ethernet with the ST32H563VGT6 MCU on a custom PCB.I'm attaching the hardware schematics, which we've taken from ST's schematics of the NUCLEO-H563ZI board. I'm including a PDF with the schematics distributed by ST.The schematics of my board are shown below: In previous versions of the custom board, we used a different hardware design:

Good morning. I am working with the Discovery kit with STM32H7B3LI MCU and want to get its internal resistance. I want to use 10 buttons, each with one resistance, and then get the correct value for my MCU. I already know how to get the values between 12000 and 64000. but I do not get what Voltage they describe. I saw on the datasheet of the Chip that it has a linear relation with the voltage and receives a voltage between 1.62 and 3.6V. Still, I have no accurate Information on the internal resistance to calculate my voltage divider. I can do it with the information I have, but I feel like I am missing something. When I put a 120-ohm resistance or shortcut directly to the ADC with 3.3V, it also gives me the maximum value.

I can program my bespoke board using a repurposed USB port. It would normally be used by a mouse.I was under the impression that if I powered up the board with BOOT0 pin held high the MCU would be in a state to connect to USB and do it's enumeration. However, using USB Device Tree Viewer I can see the 43 error.If I then hold the NRST pin low for a few seconds, and then release enumeration follows and I am able to program the device.Is this expected operation? I thought simply powering up the PCB with BOOT0 high would place the MCU in the correct state ready for programming?

Hello,  I am working with STM32G030K8T6 microcontroller and I am using an independent watchdog (IWDG). The device goes into standby mode under certain conditions, but since I cannot turn off the IWDG, I am trying to reset the IWDG by waking up with RTC wake-up before the watchdog expires. The reset time of the IWDG is set to 32.8 seconds, so I am trying to set the RTC wake-up timer to 30 seconds so that the device wakes up before the IWDG expires. During normal operation I disable RTC wake-up, before going into standby I enable it and after 30 seconds I expect the RTC wake-up interrupt to run and reset the IWDG with the “HAL_RTCEx_WakeUpTimerEventCallback” function. However, after standby the system seems to reset completely and the wake-up callback function does not work, so the device resets without resetting the IWDG. My thought was that the “HAL_RTCEx_WakeUpTimerEventCallback” function will work while in standby and then it will go back to standby mode. But it doesn'

I am using the latest version of CubeIDE (1.17.0), a STM32F765 Nucleo board with Ethernet. I am configuring the project to run lwIP using the internal Ethernet MAC. I am using FreeRTOS (CMSIS V2). CubeMX configures this LWIP_RAM_HEAP_POINTER to a default value of 0x30004000 which is NOT a valid address in the processor. I have gone through the reference manual to find out that nothing is present on this address and it is a reserved address. This causes a hardfault whenever I execute the code. However, if I comment the definition of LWIP_RAM_HEAP_POINTER, in that case lwIP uses normal buffer declared in RAM as heap and my code runs without any problem. I am making a course on this, so I just wanted to confirm if this is a bug in CubeMX or what? 

Hello,I'm trying to use a STM32H743XI to run a 1280x800px LCD display. I'm using an external 32bit SDRAM (IS42S32200L) running at 110MHz.The active framebuffer (RGB565) is located in the first SDRAM bank and I can display a stable image with LTDC clock at 50MHz. However, as soon as I start to use the DMA2D (or another bus master) to write data somewhere else in the SDRAM, the display starts to show random flickering behavior (happens every few seconds):This is how the stable image looks like without flickering:

Hello community :)I need help using the EEPROM Memory 24LC1025.I've this address for the 24LC1025 EEPROM ( A0 = 0, A1 = 0 and A2 = 1). And I'm trying to write/read on the data address range 10000h-1FFFFh but I'm not able to, when I try to do anything in this sector it rollovers to the data address range 0000h-FFFFh and I haven't figured out why.Here's part of my code:I2C_HandleTypeDef hi2c1; uint8_t dataread[127]; int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_DMA_Init(); MX_I2C1_Init(); MX_USART6_UART_Init(); HAL_I2C_Mem_Read(&hi2c1, 0x54<<1, 0x0000, I2C_MEMADD_SIZE_16BIT, dataread, sizeof(dataread), 1000); HAL_UART_Transmit(&huart6, dataread, sizeof(dataread), HAL_MAX_DELAY); while (1) { } }I've modified the Mem_Read function incresing MemAddress from uint16_t to uint32_t because I wasn't able to reach one of the higher address