STM32 MCUs Embedded software

I'm developing a project with the dual-core STM32h755zi-q, but when I run the m4 core while debugging, I encounter the error, "Break at address "0xa05f0000" with no debug information available, or outside of program code." I've configured the debugging settings according to the documentation and video shared by ST. I'm currently working on the m4 core, and I'll switch to the m7 core later, but I'm not making any progress due to the error I mentioned above.I would like to express my gratitude to everyone who helped.

I’m using the NUCLEO-N657X0-Q board and I'm creating a custom NN project using lwIP (that has the necessary weights stored at 0x7100 0000 - external Flash) and I'm trying to make it run when booting from Flash.I am currently using the “Template_FSBL_LRUN” example from STM32Cube_FW_N6_V1.2.0 as my first-stage bootloader. The FSBL correctly copies my main application from external Flash (mapped at 0x7010 0000) into internal RAM and then jumps to it. But then I noticed my app crashed when including parts of the code related to lwIP or the NN and after reading some XSPI2 registers I saw that the SR register had a value of 0x 0000 3C20 when entering my application which means the XSPI2 is already busy and its FIFO is full, so every fetch hangs.When trying to debug to see when the XSPI2 gets busy I noticed it was after this line in stm32_boot_lrun.c:source = (uint8_t*)(MapAddress + EXTMEM_LRUN_SOURCE_ADDRESS);Also when running the application straight from the STM32CubeIDE I noticed that the

Greetings! I am testing a touch button in a custom board using stm32u585 mcu. I try to follow the following workshops available on YouTube: Workshop 1 Workshop 2 The thing is, I tested in Debug Mode like in Workshop 1 in minute 15 and I could see the Delta value changing. Since the thing was working I try to implement the touch in my project. The thing is, now Delta is staying fixed, and I have absolutely no idea why it is happening. I can see the p_Data->StateId changing (PROX, DETECT, etc) but Delta value is the same. Any clue where I could be having the problem? I did not do the "MyTKeys[0].p_ChD->Delta /= 3;" in tsl_user.c, nor in the first test, and it worked at the first time.So basically my code in main.c was something like this:  #include "tsl.h" #include "touchsensing.h" ... int main(void) { "ALL THE INITS" tsl_user_Init(); tsl_user_status_t status; while(1) { tsl_status = tsl_user_Exec(); if(tsl_status != TSL_USER_ST

Hi all, SynopsisI have just found a severe error in FileX that looks like buffer overrun in fx_file_read(), but the problem is much deeper. This function leads to the function sd_read_data() which when invoked with use_scratch_buffer = 0 reads sectors to a user buffer directly. Unfortunately caller of the sd_read_data() (function fx_stm32_sd_driver()) checks buffer alignment for 4 only despite if project uses data cache or not. What happens next is very simple: sd_read_data() invalidates the cache for the entire buffer. If it is not aligned to cache line size then some bytes around it are also invalidated. If these bytes were dirty in cache they are lost. If the user buffer is allocated in the heap it hopelessly corrupts it.  Workarounds In the function fx_stm32_sd_read_blocks(), in /*USER CODE*/ section BEFORE the call to HAL_SD_ReadBlocks_DMA(), add the following code:clean_cache_by_addr(buffer, 1);clean_cache_by_addr((((char*)buffer) + hs

Hello,I'm working with STM32H745ZITX on a dual-core setup. I configured USART3 on the CM7 core. The communication flow is:TX: Using HAL_UART_Transmit (polling)RX: Using HAL_UART_Receive_ITThe first message reception works correctly. The HAL_UART_RxCpltCallback function is triggered as expected — however, the received data buffer remains empty (i.e. I can't read the data).On subsequent transmissions, no interrupt is triggered, and the RX remains in HAL_BUSY state. As a result, no new data is received, even though I can see the incoming data on the RX pin via an oscilloscope.I verified:USART3_IRQHandler is implemented and calls HAL_UART_IRQHandler(&huart3)Only the CM7 core handles UART3; CM4 does not touch itHAL_UART_Receive_IT returns HAL_BUSY after the first useQuestion: Is there any dual-core-specific configuration I need to apply to use UART interrupts reliably on CM7?Could D-Cache or I-Cache being enabled affect UART RX interrupts even when not using DMA?If yes, what is the

Subject: STM32F746G‑DISCO | SDMMC + DMA + D‑Cache – hangs at state 5, FR_DISK_ERR / empty files → root‑cause & minimal fixesCube / HAL versionsCubeF7: v1.28.0CubeMX: 6.11Board: STM32F746G‑DISCOMiddleware: FatFs R0.14, _USE_LFN = 3, _MAX_SS = 512Cache: I‑ & D‑cache enabled (default)1 – Read path: card never leaves RECEIVING (0x5)SymptomHAL_SD_GetCardState() polled after HAL_SD_ReadBlocks_DMA() stays at 0x05 → loop never exits.Root causeSD_DMAReceiveCplt() does not re‑enable the DATAEND interrupt, so the SDMMC ISR never runs and HAL state is never cleared.Fix (HAL driver)File: stm32f7xx_hal_sd.c/* inside SD_DMAReceiveCplt() */ __HAL_SD_ENABLE_IT(hsd, SDMMC_IT_DATAEND); /* <- add this line */After this patch the DATAEND IRQ fires, HAL_SD_IRQHandler() sends CMD12, sets hsd->State = READY, and the read loop exits.2 – Write path: f_sync() returns FR_DISK_ERR / file size stays 02.1 Cache coherencyBefore starting a DMA write, the sector buffer FatFs passes to disk_

I am currently using the v1.6.1 of STM32CubeIDE and a STM32G473 MCU.I have implemented an I2C bus and have noticed a major bug with the I2C_WaitOnFlagUntilTimeout functions. There is this condition:if (((HAL_GetTick() - Tickstart) > Timeout) || (Timeout == 0U)) which is supposed to guarantee that the program doesn't get stuck into the while loop above (while (__HAL_I2C_GET_FLAG(hi2c, Flag) == Status)), but the tick value stop incrementing as soon as the program enters the function for a reason I don't understand. I have tried to increase the preempt priority of System tick timer (by lowering the value) but it didn't change a thing.Does anyone know how to fix that?

Hello,I'm slowly losing my sanity so I figure I'd make a post here. I set up SAI4 to interface with BDMA, hoping to retrieve data from the onboard MEMS microphone and store it in a buffer in RAM_D3. Ideally I'd like for that data to be processed by the CPU, but I can't even get the buffer to fill up.The following code produces the output below:audio_buffer[0] = 5; audio_buffer[1] = 6; audio_buffer[2] = 7; audio_buffer[3] = 8; // ... // Inside main loop: printf("SAI State: %d \r\n", HAL_SAI_GetState(&hsai_BlockA4)); printf("SAI Error: %lu \r\n", HAL_SAI_GetError(&hsai_BlockA4)); printf("SAI Buffer Address: 0x%08lx\r\n", SAI4_Block_A->DR); printf("DMA State: %d \r\n", HAL_DMA_GetState(&hdma_sai4_a)); printf("DMA Error: %lu \r\n", HAL_DMA_GetError(&hdma_sai4_a)); printf("Pointer location: %p \r\n", audio_buffer); printf("Audio Buffer Data:\r\n"); for (int i = 0; i < 10; i++) { printf("[%d]: %d\r\n", i, audio_buffer[i]); } As you can see, SAI4 is in HAL_SAI_ST

Hello,Working on STM32F767BITx and using Free RTOSEnable USART2, here is the init codestatic void MX_USART2_UART_Init(void) { huart2.Instance = USART2; huart2.Init.BaudRate = 115200; huart2.Init.WordLength = UART_WORDLENGTH_8B; huart2.Init.StopBits = UART_STOPBITS_1; huart2.Init.Parity = UART_PARITY_NONE; huart2.Init.Mode = UART_MODE_TX_RX; huart2.Init.HwFlowCtl = UART_HWCONTROL_NONE; huart2.Init.OverSampling = UART_OVERSAMPLING_16; huart2.Init.OneBitSampling = UART_ONE_BIT_SAMPLE_DISABLE; huart2.AdvancedInit.AdvFeatureInit = UART_ADVFEATURE_NO_INIT; if (HAL_RS485Ex_Init(&huart2, UART_DE_POLARITY_HIGH, 0, 0) != HAL_OK) { Error_Handler(); } }So I can see even just after init or even after some times, the gstate == 0x20 always, and thats why unable to transmit any message over uart as it is not ready.Please guide me what is missing here.Thanks,Nitin 

Hi,I'm using an STM32F746G-DISCO board and I'm just trying to build a build a simple project with LWIP and FreeRTOS using CMSIS V2 however after enabling the minimum hardware using CubeMX I am unable to get any ping replies from the board. If I use CMSIS V1 for the config, then the board responds with ping.The reason why I want to get this working with V2 is that I'm planning to use TouchGFX in my project and when creating project using the TouchGFX, it defaults to CMSIS V2 and I've not seen any option to change that. I've tried generating project using TouchGFX and then changing it using CubeMX to CMSIS V1 however then the project falls apart and it seems like HAL_Delay which is used in some of the initialisation functions stops working.I'm using CubeIDE 1.16.0.Attaching the project for reference.

Hello everyone,I'm developing an application using USBX CDC ACM class in standalone mode. I've written an execution loop for scheduling USB stack operations and there are no problem with READ transaction; i'm able to receive correctly every data from my host pc.There is a problem or perhaps my misunderstanding on WRITE transaction (i mean from STM32 device to host pc). I'm not sure how to interpret state returned by ux_device_class_cdc_acm_write_run function. The device receive a packet (few bytes from host) and it has to answer back few bytes. On first packet, my host receive every byte sent by device but when the host send another packet, the device will send back data but nothing is received; i need to send another packet to "push" data to host.It is not very clear (for me) what is the correct behavior in respect of ux_device_class_cdc_acm_write_run exit status.when device has to send N bytes so the write_run function is called with requested_length == N;the write_run func

Hi,1. I have my own application (migrated from H7 to N6) with FileX writing to the SD card in real-time.And I see that 4-bit data bus is unusable at all (a lot of disk errors).The 1-bit data bus in NORMAL mode works sometimes. HIGH-SPEED is not working properly.The same data throughput was recorded on STM32H747I-DISCO perfectly via 4-bit bus.Could you please advise on this?2. Looking at STM32CubeN6\Projects\STM32N6570-DK\Applications\FileX\Fx_MultiAccess example,I see that 1-bit data bus in Normal mode is used.Is there any issue with the SDMMC on STM32N6 chip or STM32N6570-DK board (signal integrity)? Regards,A 

I can't get TIM1 to trigger DMA in my code (main.c)Am I missing something? 

I am working on programming a custom-designed board featuring the STM32H747IGT6 MCU using the Keil MDK-ARM environment. While I can successfully program and debug the Cortex-M7 (CM7) core, I encounter an "INTERNAL PARAMETER ERROR" when attempting to flash the Cortex-M4 (CM4) core.Current Configuration:Software Versions:STM32CubeMX: 6.8.1Keil MDK: 5.31 with the latest Device Family Pack (DFP) version 4.1Debugger:STLINK-V3SETMemory Allocation (as per STM32H747IGT6 Reference Manual):IROM1: Start Address = 0x08100000, Size = 0x00100000IRAM1: Start Address = 0x10000000, Size = 0x00048000RAM for Algorithm: Start Address = 0x10000000, Size = 0x00001000I have also experimented with alternative IRAM1 configurations via Keil's "Options for Target" settings, but the issue persists.Observations:The CM4 core can be programmed successfully using the STM32 Programmer tool, indicating that the hardware is functional.I have followed the guidelines provided in ST's Application Note AN5286 for dual-core

I try to create a new project, nothing is written in main.c! It is a first check after setting up 'LWIP', 'SDIO' and Freertos in the GUI and got this mistake!multiple definition of `errno'; ./Middlewares/Third_Party/LwIP/system/OS/sys_arch.o:/home/denis/STM32CubeIDE/workspace_1.9.0/FreeRtos_SDIO_Web/Debug/../Middlewares/Third_Party/LwIP/system/OS/sys_arch.c:45: first defined hereSTM32CubeIDE Version: 1.9.0 PS - This error not appear then I was on STM32CubeIDE Version: 1.8.0

Hello!I am writing a program that uses FreeRTOS and LwIP libraries. I would want to check ARP table, but functions from ip4 directory are not considered thread-safe. How can I check ARP table when using FreeRTOS or how can I make sure calling thread-unsafe functions won't break my program?I saw that there is an LwIP mutex that can be used to lock the stack via LOCK_TCPIP_CORE() and UNLOCK_TCPIP_CORE() macros, but I am not sure how to use them properly or if it is even a good approach. Thank you in advance!

Hi everyone,I'm currently working on a project to turn an STM32 microcontroller into a USB printerdevice. I have spent a considerable amount of time searching for a comprehensive guideor a complete implementation for the classic USB printer device class on the STM32platform, but unfortunately, I haven't found a solution yet.I did find this valuable ST Community post that provides a walkthrough for setting up aUSB Communications Device Class (CDC): LINK, This has led me to a few specific questions:1. CDC vs. Printer Class: For those experienced with both, how significant is thedevelopment effort to move from a CDC implementation to a compliant USB PrinterClass (Class Code 07h) device? I understand the Printer Class has its own setof specifications, but I'm trying to gauge the complexity of adapting the existingCDC examples.2. Successful Implementations: Has anyone in the community successfully configuredan STM32 as a USB printer device? I've come across a few forum posts where this hasb

I've got an STM32G491RE on a NUCLEO-G491RE board and I'm driving the DAC using TIM4's TRGO and pulling values out of a memory buffer using DMA.  It was a bit of a challenge getting set up, but now that it's running it's beautiful.What's weird is that I've got TIM4 initialized with both prescaler and counter set to 4, and since that board is running at 72 MHz that means I'm triggering the DAC every 347 ns but it's supposed to have a max of 1 Msps.Am I correct in assuming it's just ignoring those extra timer triggers?  Are there any error bits set when you "overdrive" a DAC like this? 

Good afternoon Team,I am working on a project where I need to interface two SPI peripherals with an ST microcontroller (STM32G070RBT6).One peripheral (ADS124S06) operates in SPI Mode 1 (CPOL=0, CPHA=1), and the other (64128L FC BW-RGB Display) in SPI Mode 0 (CPOL=0, CPHA=0).Both peripherals must operate concurrently to ensure real-time data visualization.Is it possible to use a single SPI interface for both peripherals, even though they require different modes?If yes, what is the best way to handle this?  ---Should I reconfigure the SPI mode dynamically before communicating with each device?Are there any potential timing or synchronization issues to consider?Thank you in advance for your support!

Dear all,I'm working on an custom hardware project using the STM32G0B1 MCU running ThreadX.  My goal is to use/port the USBPD stack for both source as sink device, but I'm failing to do so partly because the stack provided is closed source.The CubeMX skeleton code generated for my project does not offer a working solution and all example code nor documentation available is not targeting ThreadX.Also I'm somewhat confused about which PD stack to use since X-CUBE-USB-PD is no longer recommended? Then what would be the alternative stack to use?Does anyone have practical experience, can provide meaningful documentation or example code porting USBPD to ThreadX? I would be forever thankful.Thanks and looking forward to your replies.With regards,Peter  

Hi. I have a  NUCLEO-N657X0-Q board with MB1854B. Yes, exactly nucleo, not discovery one. Im trying to recreate RTSP example fron discovery board. As netxduo from cubemx is kinda buggy, i manually added it along with other necessary middlewares from github repo. After configuring all peripherals according to VENC RTSP example for disco board on video side and UDP ECHO Server example for nucleo board, i copied application files from VENC RTSP example.Application starts but fails to get IP by dhcp. I have tripple-checked all the things. ETH configuration and driver are correct for my board and my PHY(lan8742). ETH is inited without errors, memories for descriptors and buffers are marked as non-cached in MPU. Pin assignment also correct. Netxduo creates DHCP packets and descriptors for them. Then _nx_driver_packet_send is triggered. But i checked with my oscilloscope TX lines on the RMII interface, and there are no activity. I also checked, UDP Echo exam

As the title says, I've got a (circular) buffer of uint16_t values that I want to send to the DAC every time the timer updates.  It seems like it's 95% working, in that if I manually trigger the DAC:for (int i = 0; i < 10000; ++i) { LL_DAC_TrigSWConversion(DAC1, LL_DAC_CHANNEL_1); HAL_Delay(1); }I can see my waveform on the output pin. But when I try to have the DMA send the values to the DAC, the output never changes.One complication is that I need to run in two modes - in one mode I'm taking the ADC input, processing it, and sending that to the DAC, in the other mode (I'm calling "inject" mode) the ADC is ignored and the DAC values come from my memory buffer.The code to switch between modes looks like this:if (inject && !Inject) { // Turn on inject mode // HAL_DAC_Start_DMA(&hdac1, DAC_CHANNEL_1, (uint32_t*)Transfer, 4096, DAC_ALIGN_12B_R); LL_DMA_DisableChannel(DMA1, LL_DMA_CHANNEL_3); while (LL_DMA_IsEnabledChannel(DMA1, LL_DMA_CHANNEL_3)); // Wait till of

Hi as part of my project I am trying to integrate the mentioned parts in subject to control modbus eth relay over tcpip.What I have done so far.1. Integrated Lan chip driver to stm32 library and initalization done.2. Integrated LwIP stack from online resources and confirmed LwIP integration succeeded. (Since i'm using STM32H563RGT6 MCU and it doesnt have inbuilt LwIP stack with in it).3. Initially tried to establish a connection with my PC and try a ping test.4. I'm facing ARP Resolution initally but somehow it resolved and now i can find my MCU ip and mac address on my PC, but still ping is not reachable.5. My POV is that if its capable of handling etherent packets then i can start work on with modbus packets to trigger the relay module.Pls help me with this case...  

Hello, I’m trying to drive LEDs using all four PWM channels of TIM8 on a NUCLEO‑H755ZI, but I’m running into this issue:CH1 (PC6) and CH2 (PC7): When I measure with a multimeter, I see the expected voltage fluctuations/average corresponding to the configured frequency and duty cycle.CH3 (PC8) and CH4 (PC9): I’ve removed the LEDs and measure the pins directly with a multimeter; they always read 0 V. I’m attaching the project archive, which includes the CubeMX .ioc file, tim.c , gpio.c , the driver layer, and all HAL settings. I’d appreciate any suggestions or insights you might have. Thanks in advance!

Hello,From my understanding in FreeRTOS, there is a defined highest priority one should set for interrupts whose ISRs may call RTOS APIs (configMAX_SYSCALL_INTERRUPT_PRIORITY).For the same reasons, I would expect ThreadX to have a similar limitation, and to that extent I have found other ST forums posts suggesting one should set lower priorities for any interrupts whose ISRs may call RTOS APIs, but I can't find any documentation that explicitly states what the highest safe/allowable priority is, similar to FreeRTOS.How do I know what's the highest interrupt priority I can safely set in such cases? Is there any documentation from ThreadX that I'm missing, because I can't seem to find any mention of this.For context, I am using a U5 series MCU and I want to call queue related APIs in my CAN Rx callback.