STM32 MCUs Embedded software

 I'm programming a STM32H503CBUx Timer3. NVIC settings are such that the count down event is trapped in void HAL_TIM_PeriodElapsedCallback(TIM_HandleTypeDef* htim)This is a global interrupt routine that takes care for other timer interrupts as well and on has to decide from the handle that is being passed, which interrupt has to be served.My requirement is that this interrupt has high priority and is handled as fast as possible.Timer CLK is 250MHz. The timer counts down with pre divider 1 and count down of around 15,000.In the ISR the counter htim3.Init.Period =14999 is being set to 1000 and should generate the next interrupt. Then follows another chain of such countdowns from 1000. The interval between the two subsequent interrupts is 4 µs. Can an ISR be served with such time constraints?How many instructions can be handled by the MCU at 250MHz clock? Alone the handle testing costs me valuable instruction time. Could I use a timer that has a uniquely asserted ISR?

I am using the USB CDC driver code provided by ST in stm32cubeide, and am trying to figure out a proper minimum heap size. I have found various slightly conflicting answers, but the consensus seems to be that 512 bytes is not enough.In the same application, I also use FATFS, but I'm not 100% sure if that is supposed to use the heap.Now I wanted to test just how much of the heap is in fact overwritten. To do this, I brutally stored the byte sequence AA BB CC DD over and over in the first 1 KB of the heap. I did that with this piece of code inserted in main.c, immediately after the entry point:uint32_t *heapPtr; uint32_t *heapOrigin; (...) /** * @brief The application entry point. * @retval int */ int main(void) { /* USER CODE BEGIN 1 */ uint16_t i; heapOrigin = malloc(4); free(heapOrigin); heapPtr = heapOrigin; slDebug6 = (uint32_t)heapOrigin; for (i = 0; i < (1024 / sizeof(*heapOrigin)); i++) { *heapPtr = 0xDDCCBBAA; heapPtr++; } /* USER CODE END 1 */The malloc(4

Hi, I am running firmware for USBX MSC device. The example project  "Ux_Device_MSC" on demo board STM32U575I-EV.  MSC device is enumerated on computer and FATS file system is used. It can transfer file from computer to storage on STM32U575I-EV.  I am trying to figure out the following parameters. 1. how many times the following function in source file "ux_device_msc.c" is called when transfer a large file UINT USBD_STORAGE_Write(VOID *storage_instance, ULONG lun, UCHAR *data_pointer, ULONG number_blocks, ULONG lba, ULONG *media_status) { UINT status = UX_SUCCESS; /* USER CODE BEGIN USBD_STORAGE_Write */ UX_PARAMETER_NOT_USED(storage_instance); UX_PARAMETER_NOT_USED(lun); UX_PARAMETER_NOT_USED(media_status); ULONG WriteFlags = 0U; /* Check if the SD card is present */ if (HAL_GPIO_ReadPin(GPIOI, GPIO_PIN_0) == GPIO_PIN_SET) { /* Check id SD card is ready */ if(check_sd_status() != HAL_OK) { Error_Handler(); } /* Start the Dma write */ status = HAL_SD_WriteB

Greetings, I am trying to do a POC of LVGL migration to the STM32N6DK, https://github.com/STMicroelectronics/STM32CubeN6/tree/main/Projects/STM32N6570-DK/Examples/BSP For the POC i tried porting the LVGL into FSBL example above, but I ran into memory overflow issues. So for the next step, I cloned and tried to port the drivers and dependent files into this repo's application project: https://github.com/stm32-hotspot/STM32N6_FSBL_Modes/tree/main In this I was able to display just the initial screen util clear screen function and then it crashes in the dma2d buffer transfer section, most likely the DMA2D CE bits were not being set and the timeout is not triggered because the hal tick fails and it is stuck in the while loop. Either way, I am unsure of the best approach, my goal is simple, to get a barebones LCD and touch working in the application region and link it with LVGL library to do the UI for my POC.  Could anyone please guide me to get the fastest approach to getting th

Hello,I'm currently preparing the firmware for a USB NFC reader (CCID). I'm working with the STM32F103 MCU and the ST25R3916 NFC reader.The STM32F103 MCU is programmed on a CCID USB device using the CCID USBD driver provided by STM32. The MCU acts as the mediator between the computer and the ST25R3916 NFC reader. It takes the APDU command sent by the computer and transfers it to the NFC reader, and takes the NFC reader's response and transfers it to the computer using the SC_Itf_XferBlock() function.The STM32F103 MCU supports usb full-speed, this means that the maximum amount of data to be transferred to the computer is 64 bytes. If you want to transfer data larger than 64 bytes, you transfer it using chunk-by-chunk methods.To transfer 253-byte data, the splitting is as follows:5 chunks: chunk 1 (54 bytes of data with 10 bytes of header), chunk 2 (64 bytes of data), chunk 3 (64 bytes of data), chunk 4 (64 bytes of data), and chunk 5 (7 bytes).The issue is that when I try to transfer 25

Hi,I am using STM32Cube_FW_H5_V1.5.0. I initialize a MPU region with the following code, using only LL-calls:LL_MPU_ConfigRegion(LL_MPU_REGION_NUMBER6, LL_MPU_REGION_PRIV_RW|LL_MPU_INSTRUCTION_ACCESS_DISABLE|LL_MPU_ACCESS_NOT_SHAREABLE, LL_MPU_ATTRIBUTES_NUMBER2, 0x90000000U, 0x9FFFFFFFU);The corresponding MPU register MPU_RLAR_Ax gets set to 0x9FFFFFE3, wich is obviously wrong because I wanted to select attribute#2 and instead the attribute field gets set to 0x1.For verification I did the same initialization using HAL-calls:MPU_Region_InitTypeDef region; region.Enable = MPU_REGION_ENABLE; region.Number = MPU_REGION_NUMBER6; region.AttributesIndex = MPU_ATTRIBUTES_NUMBER2; region.BaseAddress = 0x90000000U; region.LimitAddress = 0x9FFFFFFFU; region.AccessPermission = MPU_REGION_PRIV_RW; region.DisableExec = MPU_INSTRUCTION_ACCESS_DISABLE; region.IsShareable = MPU_ACCESS_NOT_SHAREABLE; HAL_MPU_ConfigRegion(&region);Now the MPU register MPU_RLAR_Ax gets set to the correct va

  I'm working with an STM32G431KBUx and trying to output a waveform via DAC1 using DMA and TIM6 as trigger (TRGO). I’ve successfully configured the DAC and DMA using STM32CubeMX.  However, the DMA callbacks HAL_DAC_ConvCpltCallbackCh1 and HAL_DAC_ConvHalfCpltCallbackCh1 never get called. Here’s what I’ve checked so far: DMA handle is linked manually:hdac1.DMA_Handle1 = &hdma_dac1_ch1; Trigger is set to Timer 6 Trigger Out event. DMA is configured in Circular Mode. I'm calling HAL_DAC_Start_DMA(...) with a buffer of 2 * 64 samples (12-bit aligned). Callback functions are correctly named and defined in main.c: void HAL_DAC_ConvHalfCpltCallbackCh1(DAC_HandleTypeDef *hdac1) {// Never called}void HAL_DAC_ConvCpltCallbackCh1(DAC_HandleTypeDef *hdac1) {// Never called} /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ***************************************

I am currently using the STM32N657 to drive an 800x480 pixel display with 24-bit color. The problem that I am running into is the buffer that I need uses 1.1MB (800*480*3 = 1.152MB). Using just FSBL, I am limited to 511KB of SRAM. I know that this chip has 4.2MB of SRAM on it, so how do I access that SRAM for my buffer?

We have a STM32070CBT6 with minimal connections (schematic below) and it appears to be unresponsive to USB enumeration, although it does pull DP low to trigger it. This occurs when hotplugging it or holding reset low for a few seconds. I've checked the input on PF0 and it is getting a clean 16 MHz. 

Hi, I am testing the System Memory UART protocol in STM32G070CB.I tried the Get command, the Go command, and the Read Memory command standalone, all success.However, when I try to execute the Read Memory command, which is successful, and then execute the Read Memory command, the ST does not send any response.Full pattern:Successful Enter Boot Mode:Read Memory CMD with Address = 0x0801FFF0 and read data size is 0x10Try to execute the Read Memory CMD again but without ACK/NACK As I know, the protocol is able to execute other CMD when the pervious CMD completed or Failed. How could I execute CMD continuously? Note: UART Protocol version of the MCU is V3.1    

Hello Community,I have been attempting to use the STM32CubeIDE to combine two examples:https://github.com/STMicroelectronics/STM32CubeU5/tree/main/Projects/NUCLEO-U545RE-Q/Applications/ThreadX/Tx_MPUhttps://github.com/STMicroelectronics/STM32CubeU5/tree/main/Projects/NUCLEO-U545RE-Q/Applications/ThreadX/Tx_SecureLEDToggle_TrustZoneWherein I want to have a ThreadX module within the TrustZone. I have been able to get both examples individually building, flashing, and debugging on my board. However any attempts to add modules/manager to the Trustzone example, and conversely Trustzone to the Module example have been entirely unsuccessful - due to my experience with the tool I am unable to add the middlewares.Is there any example out there doing what I want?Or if not, does anyone have any instructions on how to combine these two projects. My assumption is that the solution will have three subprojects with three distinct linker files, with relevant partitioning of memory:Secure (St

 I'm implementing UART communication between an Arduino Uno and an STM32L476RG. When the STM32 acts as the master (transmitter) and the Arduino Uno as the slave (receiver), data transmission works as expected. However, when I reverse the roles—making the STM32L476RG the slave (receiver) and the Arduino Uno the master (transmitter)—the STM32 fails to receive data correctly. I'm looking for a reliable solution to ensure proper UART communication in this configuration.

How is ThreadX expected to be used with the STM32U5 family using the STM32CubeIde?I was expecting to see an X-CUBE-AZRTOS-U5 package like there is for the STM32H7 family which is X-CUBE-AZRTOS-H7.  I don't see it.  I'm using a STM32CubeIDE 19.0 that I downloaded last night.  I do see there are ThreadX examples for the U5 development boards that I have not installed yet.  So ThreadX does seem supported.I'm wrapping up an H7 project where I used ThreadX, FileX, and USBX with the STM32CubeIDE with STM32CubeMX so got familiar with how all those work together. I'm in the earliest stages of a new project where I have different criteria so the H7 family isn't a good fit.  I'm much more board size and power constrained.  The U5 seemed like the best fit.Anyone out there using ThreadX and USBX with a STM32U5 processor? Your experiences? I haven't committed yet but am leaning towards the STM32U575.  I need Audio ADC support ie SAI and USB Class 1 audio support p

 Hello everyone,I’m currently working with the STM32H723ZG Nucleo board and am trying to interface microROS using UDP transport. I’m using the following environment:STM32CubeIDE: v1.16.1STM32Cube Firmware: H7 V1.11.2Toolchain: GNU Tools for STM32 (GCC 12.3.rel1)I’ve carefully reviewed several guides covering MPU, Ethernet, LWIP, and FreeRTOS configurations. I was able to get microROS working over USART (per the Micro_ROS guide), but when I attempt the UDP transport I encounter a hard fault. I’ve tried replicating setups from the STM32H723_Nucleo_ETH and LWIP_UDP_Echo_Server examples (generated by CubeMX), but they don’t work as expected.My project files are available here: tapererwaj/h723zg_microros_udpBelow, I have summarized my current configuration:MPU Configuration SCB_EnableICache(); SCB_EnableDCache(); /* Region 0: Ethernet DMA descriptors */ MPU_InitStruct.Enable = MPU_REGION_ENABLE; MPU_InitStruct.Number = MPU_REGION_NUMBER0; MPU_InitStruct.BaseAddress = 0x0; MPU_Ini

I am working with STM32 U575/U5A5 series of STM32 controllers in low power mode. I have programmed the controller to enter into Stop 3 mode and wake from stop3 mode based on wakeup Pin(High on PF2). With this implementation issue what we observed is once immediately flashing hex file into controller using STlink programmer, Controller is entering in stop3 mode but it is not waking up from stop3 mode even after low to high transistion on wakeUp pin(PF2). If I remove the power and connect it back, it is working as expected enterning into stop mode 3 and waking up from stop mode 3 on low to high transistion on wakeUp pin(PF2) all the time. The question here is why for the first time after flashing hex file into controller, entering into stop3 mode but not waking up from stop3 mode and requires power reset?low power mode is configured as follows:void LowPowerInit(){        LL_RCC_SetClkAfterWakeFromStop(RCC_STOP_WAKEUPCLOCK_SELECTED);    __HAL_RCC_PW

Hi everyone!I'm working on USB MSC implementation on STM32U0 series MCU with W25Q32JV (NOR Flash) by using USBX + ThreadX.W25Q32 Memory organization:- It has 64 blocks and each block is of size 64KB- Each block has 16 sectors and each sector is of size 4KB (Total 1024 sectors)- Each sector has 16 pages and each page is of size 256B (Total 16384 pages)- Total size of flash memory = 4MBI've already created and mounted a file system in W25Q32 using FatFS library. Also created one folder with one text file in it. Then, using USBX I tried to implement the MSC and till now I'm able to achieve these things:1) My laptop (USB Host) is able to detect the device i.e MCU as "USB Mass Storage Device" (in the Device Manager -> USB controllers) and "AzureRTO USBX storage dev USB Device" (in the Device Manager -> Disk drives)2) Coming to the capacity information of this disk, it is showing correctly as 4MB but the volume of the Drive (D:) as 2MB. And when I open the Properties of this Drive

I am trying to get USBX Device MSC to work in Standalone mode (without RTOS) on Stm32u083mc microcontroller. However, I am interested in configuring an external Flash as a mass storage device. i am using the same clock frequency of HID standalone example which i referred from official STM32U0 Work shop tutorial from youtube. Now i am planning for mass storage class, i am defining pool_size and stack_size is from app_usbx_device.h file #define UX_DEVICE_APP_MEM_POOL_SIZE (10*1024)#define USBX_DEVICE_MEMORY_STACK_SIZE (10*1024).from MX_USBX_Device_Init() function i am getting usbd_ok. before returing i am calling these function USBX_APP_Device_Init(); VOID USBX_APP_Device_Init(VOID){MX_USB_PCD_Init(); // Endpoint 0 (Control)HAL_PCDEx_PMAConfig(&hpcd_USB_DRD_FS, 0x00, PCD_SNG_BUF, 0x00); // EP0 OUT at PMA offset 0x00HAL_PCDEx_PMAConfig(&hpcd_USB_DRD_FS, 0x80, PCD_SNG_BUF, 0x40); // EP0 IN at PMA offset 0x40 // Endpoint 1 (MSC Bulk)HAL_PCDEx_PMAConfig(

Hi,I have been working on STM32F4 discovery board, I have developed Bootloader Code. There is 2 option to jump to application that includes blinking led app. First button interrupt runs perfectly, i mean hal_delay() runing with no issue.Second option is, if UART interrupt gets the jump command and address from my computer. In this situation it jumps to application and leds are turn on but not blinking because of hal_delay() func (i guess). In 2 option before the jump func if i use hal_delay() , it crahs also.

Product: STM32F401VET6Firmware Package: STM32Cube_FW_F4 V1.28.0Tool: STM32CubeIDE (latest version)Description:Hi!I’m currently working on a USB CDC device project using the STM32F401VET6 microcontroller with the STM32Cube_FW_F4 firmware package (V1.28.0) in STM32CubeIDE.I have encountered a series of issues when enabling USB_DEVICE with the CDC class. Specifically:The generated project fails to compile due to errors, such as USBD_ClassTypeDef being undefined in some modules (e.g., usbd_ioreq.h), even though usbd_def.h is included and USBD_ClassTypeDef  is defined in usbd_def.h.The structure USBD_HandleTypeDef is not recognized in some compilation units, leading to cascading errors.There seem to be conflicts or inconsistencies when including usbd_def.h, especially between header files like usbd_ctlreq.c, usbd_core.c, and usbd_ioreq.c.Even after ensuring all relevant include paths (e.g., Middlewares/ST/...) are configured correctly in the project, the problem persists.I found t

Hi ! I'm working on a STM32F429VET, with keil as an IDE. My problem is the next, this code which is NOT reached (because it need a command from the terminal to be). Make my entire program crash in contact of loop, causing an IACCVIOL if i let this part of the code commented, works fine if i uncomment it. Anybody have encounter similiar behavior ? I dont get it at all.void adc_measure(uint16_t channel, uint8_t *result) { measureInProgress = true; adc_init(channel); HAL_TIM_Base_Start_IT(&htim2); // while (measure_pending_count < NB_MEASURES) // { // // adc_read(); // __disable_irq(); // Prevent race condition // measure_pending_count++; // __enable_irq(); // // } HAL_ADC_Stop(&hadc1); float measure = adc_compute_value(channel); // convert the value toward needed unit (mA or V) //snprintf((char *)result, RESULT_PRECISION, "%f", measure); }   

We have been using some code to allow jumping into bootloader from the application that has been working well for many years, but has since failed on all our newest batches of PCBs. All PCBs have the same STM32H743ZIT6 processor, all revision V. The only difference is that the jump is working on processors with bootloader version 0x90, but not on boards with version 0x91. The code for the jump into bootloader is mostly taken from this post.#define USB void Bootloader_Jump(void) { uint32_t i=0; void (*SysMemBootJump)(void); /* Set the address of the entry point to bootloader */ volatile uint32_t BootAddr = 0x1FF09800; #ifdef USB __HAL_RCC_USB_OTG_FS_FORCE_RESET(); HAL_Delay(1000); __HAL_RCC_USB_OTG_FS_RELEASE_RESET(); #endif /* Disable all interrupts */ __disable_irq(); HAL_DeInit(); /* Set the clock to the default state */ HAL_RCC_DeInit(); /* Disable Systick timer */ SysTick->CTRL = 0; SysTick->LOAD = 0; SysTick->VAL = 0; /* Clear Interrupt Ena

Hello,I am making a new project by importing the .ioc file of example code "Ux_Device_CDC_ACM" of STM32U5G-DK2. All the .c files of USB_stack are also copied from the example project. Both, example project and My project, look same. My project builds also successfully. But no COMM port is being formed after loading the project to STM32U5G-DK2 whereas, COMM port is being formed with Example project.What could be the reason ? Please help. With regard,Sudarshan Chaudhary 

Hello,Because there is no active handle in DMA list for DCMI DMA initialization (bug!?) I searching for the ways to enable and use DMA, I can't find examples for parallel mode except for CSI serial, if I switch to use DCMIPP in parallel mode then the cubeMX do not generate msp initialization code function HAL_DCMIPP_MspInit for DCMIPP interface (no pinout, RCC, IRQ...), and in DMA list DCMI_PSSI handle stays inactive,all my attempts to setup DCMI DMA do not work and DMA throws error 0x40, DCMI and camera working well, I getting hsync and vsync callbacks firing and counters show correct values, I tryed various settings but still cant start DMA transfer, there is my test and msp initialization code, please check: uint32 err0 = HAL_DCMI_Start_DMA(&hdcmi, DCMI_MODE_CONTINUOUS, (uint32)frame_buff_DCMI, 320 * 240 / 2); uint32 err1 = HAL_DCMI_GetError(&hdcmi); HAL_Delay(5000); uint32 err = HAL_DCMI_GetError(&hdcmi); printf("DCMI %u %u, %u %u %u, %u %u\n", hdcmi.St

Hello,I'm working with the STM32N6570-DK board and trying to merge two example projects provided by ST:Project 1 (DCMIPP):https://github.com/STMicroelectronics/STM32CubeN6/tree/main/Projects/STM32N6570-DK/Applications/DCMIPP/DCMIPP_ContinuousMode Project 2 (USB CDC):https://github.com/STMicroelectronics/STM32CubeN6/tree/main/Projects/NUCLEO-N657X0-Q/Applications/USBX/Ux_Device_CDC_ACM While merging, I added the following files from Project 1(DCMIPP) into the Project 2(USB CDC) project in Keil: 1 . libn6-evision-awb_keil.a 2 . libn6-evision-st-ae_keil.aHowever, I’m encountering the following build issues:Build target 'Ux_Device_CDC_ACM'armclang: warning: ../../../../../../Middlewares/ST/STM32_ISP_Library/evision/Lib/libn6-evision-st-ae_keil.a: 'linker' input unused [-Wunused-command-line-argument]armclang: warning: argument unused during compilation: '-mfloat-abi=hard' [-Wunused-command-line-argument]armclang: warning: argument unused during compilation: '-mcmse

Hello,After loosing days trying to implement paho mqtt with lwip and freeRTOS on a nucleo-F207ZG, I restarted from scratch and try do implement it in bare-metal mode.After a few hour of debug, using wireshark and mosquitto on a PC :- Connecting to the broker as anonymous works- Connecting to the broker with user/pwd fails.Wireshark shows that there is no user/pwd on the CONNECT packet and the associated flags are reset.The official mqtt_client_connect() looks quite strange : it does not take care of the eventual user/pwd provided in argument (mqtt_connect_client_info_t *client_info)Flags are set to MQTT_CONNECT_FLAG_CLEAN_SESSION, and user/pwd are never used by this function. Is the provided MQTT file is just a demo file with limited functionalities ?Thank youRegards