STM32 MCUs Embedded software

Dear allI am relatively new to STM32, using STM32H563 as an SPI slave to receive data and send some feedback data as same time, The SPI master is a Tiva MCU form Ti,  as data is relatively long, I need to use DMA, I tried to find an example for it, but there is none with DMA, could some one please provide some starting point for me? Thanks in advance.Ping 

Hi you all,as a breef summary; I set up a timer to trigger an adc that should than use the DMA to transfer the data to memory, i need 111 samples at a time. Sadly for some reason this only works for one sample so if i check  __HAL_DMA_GET_COUNTER(g_hadc1->DMA_Handle) it will get stuck at 110.and subsequently my  HAL_ADC_RegisterCallback(g_hadc1, HAL_ADC_CONVERSION_COMPLETE_CB_ID, ADC_LineScanComplete_Callback); is never called.Though the timer and ADC for sure triggeres as i can the see the DR register updating its value.And as far as the reference manual goes (Page 961 DMA One-shot) it should be possible to use  HAL_ADC_Start_DMA(g_hadc1, (uint32_t*)dest, 111); to get like 111 sequential timer triggered samples, that are transfered to memory via DMA I tried various combinations of all possible adc settings, and all of them keep beeing stuck on 110 remaining DMA cycles. As well as trying to look up the resgisters for any errors that might have been accured, but

Dear @YutinhLin , Post Edited by ST moderator to apply source code formatting and translate from Chinese to English to comply with the community rule: Best regards, Gyessine   晶片型號 : STM32H723VGTx RX 與 TX Buffer 都已配置到 D2 區塊 使用狀況 : 第一次執行 HAL_UART_Transmit_DMA 正常 執行 HAL_UART_AbortReceive() -> HAL_UARTEx_ReceiveToIdle_DMA() 後 再執行 HAL_UART_Transmit_DMA 無法正常工作 請問這樣的使用方式是否正確 或是需要另外的設定動作才能再正常使用 Chip model: STM32H723VGTx Both the RX and TX buffers are allocated in the D2 domain. Usage scenario: The first execution of HAL_UART_Transmit_DMA operates correctly. After executing HAL_UART_AbortReceive() followed by HAL_UARTEx_ReceiveToIdle_DMA(), subsequent execution of HAL_UART_Transmit_DMA does not function as expected.  

I’m attempting to learn BLE and IoT and have purchased the following boards to get started.NUCLEO-F401RE    MCU brdX-NUCLEO-IDB05A2  BLE Expansion brdDownloaded:STM32CubeIDE Version: 2.0.0 Build: 26820_20251114_1348 (UTC)STM32CubeMX Version: 6.16.1x-cube-ble1   BLE DemoThe main program calls HAL-Init() which goes directly to the HardFault_Handler()My preliminary conclusion is that Version 20.0.0 is not compatible with the demo program based on help I sought on ChatGPT. It recommends Version 1.19.0. Is this correct?May need to back up and start from scratch and would appreciate a point in the right direction to avoid going down any unnecessary rabbit holes.Thank you, BareMetaler

Hi,I made a custom bootloader to upload my application using the virtual com port by the USB interface.This works nicely, but my application also has a part in flash to store its configuration. When I flash my user program, I do not want to overwrite the configuration. Therefore, this is a special part in the flash memory.Is it possible in the STM32CubeIDE to generate a bin-file for this configuration to have a default configuration?Is it also possible to generate a bin-file using my bootloader, by reading the flash memory where the configuration starts? Because it would be great to backup a configuration.Greetings,ErX  

Hi ST team,I am using STM32U5G9 MCU. After modifying option bytes, HAL_FLASH_OB_Launch() would be called to apply the changes.But in the launch function, it states that "Option byte launch generates Option byte reset". I have other tasks need to be done after calling HAL_FLASH_OB_Launch(). I don't want device to be reset after calling HAL_FLASH_OB_Launch() immedately.Is there a way to trigger reset manually after modifying option bytes?1. Modify option bytes2. Call HAL_FLASH_OB_Launch()3. Reset device manually Thank you.

Hello,I'm wondering if Cube's generated code for is thread safe. In particular, whether malloc can be safely used in a multi-threaded FreeRTOS setup.The broken malloc behavior was first described by Dave Nadler in 2019 here. He has also written about it on his webpage.In 2021, ST seems to have introduced some "fixes" to this problem, by adding a thread-safe code generation option in CubeMX and implementing the various __retarget_lock* newlib functions to make sure that newlib can behave correctly in a multi-threaded environment.However, it seems like that these implementations are buggy. One such issue is reported here, where the lock's nesting level is (incorrectly) modified before entering the critical section. I've just reproduced this exact issue today, with Cube version 6.11.1.I'm quite confused about the current state of this issue. Are the things described by Dave Nadler still relevant or applicable? Is ST going to fix the bugs in the __retarget_lock* implementations? For people

I'm using STM32N6 with stm32-mw-camera to communicate to CAM-66GY sensor. I also have CAM-16GZ sensor, but looks like this sensor is not supported (because of VD6G_BAYER_NONE when I use vd6g driver). What are my options to integrate CAM-16GZ into the same project?Thank you

 Hello ST team,I am developing a camera application on STM32N6570-DK + IMX335.The entire capture/display pipeline follows the official DCMIPP_ContinuousMode example:  IMX335 RAW10 → CSI → ISP → PixelPacker RGB565 → LTDC However, the LCD output shows a corrupted pattern like in the attached video:The image reacts to hand movement (so the sensor is streaming), but the content becomes color-shifted, diagonal, and distorted. The pattern matches the behavior when:RAW10 is fed directly into the PixelPacker interpreted as RGB565,meaning the ISP output is never routed to Pipe1. What currently works1. IMX335 is clearly streaming (image brightness changes when covering the lens).2. CSI + Pipe1 receive real frames.3. LTDC and framebuffer work correctly (solid-color test OK).4. All registers after DCMIPP init match the official demo.5. ISP_Init() and ISP_Start() both return OK (0).6. ISP_BackgroundProcess() also returns OK. What is incorrectAfter ISP_Start()

I am just curious about information in the flash.  #ifndef DEVICE_VERSIONING_INFORMATION_H #define DEVICE_VERSIONING_INFORMATION_H typedef struct { uint32_t magic; // 0x46575652 = 'FWVR' uint8_t major; uint8_t minor; uint8_t patch; uint8_t build; } fw_version_t; __attribute__((used, section(".fw_version"))) const fw_version_t fw_version = { .magic = 0x46575652, .major = 1, .minor = 3, .patch = 2, .build = 7, }; #endif // DEVICE_VERSIONING_INFORMATION_H I wrote in the linked script file (.ld) some versioning information. I guess it is the best way to store the device versioning information because that way allows the swd to get directly from the flash the version, although, I can get it too by request and response by uart. However, why there is more data after the version information in the flash memory?Is this normal? Should the user defined constants in the flash be followed by other information?/* ******************************************************

Hi everyone,I am working on a project with the NUCLEO-H7S3L8 and trying to read 2 ADCs simultaneously in Continuous Conversion mode using HPDMA.The Goal:ADC1 & ADC2: Reading 7 channels each (14 channels total).Mode: Continuous Conversion, Circular Mode.Transfer: HPDMA to SRAM (AHB SRAM).The Problem: I am receiving data, but the values are extremely unstable/fluctuating.When running a smaller example from a ST-Employee, values were stable (around 400).With the full 7-channel scan, the data fluctuates significantly, at a level where data should be wrong.Can someone take a look at it? They both use the same bootloader. I honestly cant see any issues with my custom config.Thanks in advance.  This is also my linker if relevant:/* ****************************************************************************** ** ** @file : LinkerScript.ld ** ** @author : STM32CubeIDE ** ** Abstract : Linker script for STM32H7Sxx Device ** 128KBytes FLASH ** 456KBytes RAM ** ** Set heap size, sta

Hi experts:I'm working on STM32U575 evk, using ADC1 including two channels enabe interrupt, attached file is my test project, only one interrupt in the callback function, I don't know why, if I changed the end of conversion selection to end of sequence of conversion, no interrupt triggered, please help to check if anything missing in my project, thanks.Bill

Hi there!I start to work with this sensor and i want use this functionHAL_I2C_Mem_Write_IT(I2C_HandleTypeDef *hi2c, uint16_t DevAddress, uint16_t MemAddress,uint16_t MemAddSize, uint8_t *pData, uint16_t Size)so the pointer address register of the sensor is 8 bit but the data  are 16bit is correct if i do that  example:  data[0] = MSB; data[1]=LSB; HAL_I2C_Mem_Write_IT(&hi2c1, INA226_Addr , 0x00, I2C_MEMADD_SIZE_8BIT, data, 2); and i do the same when i want read data from register.Sorry if i ask a silly question thank you Sergio

How would I go about implementing a USB host for a usb printer. I would like to send things through my STM32 to be printed. I’ve seen adaptations or some work done on the USB printer class as a device but I am unsure how I would do this as a host? Any ideas or already implemented libraries?

Hi there!i start one of my new project with STM32cubeide 2.0. First i start with configure mu MCU in STM32CUBEMX in this casa STM32G031K8T6 afther i configurate all pin i create a poject . So afther i import my project in STM32CubeIde 2.0 and i build gave me this error:Core\inc\main.h: fatal error: stm32g0xx_hal.h: No such file or directory #include "stm32g0xx_hal.h" but i check with F3 and this file exist , so please someone can help me ? Thank youSergio

Posted on July 25, 2013 at 11:26 Hi ! When running the VCP USB Stack (STM32_USB-Host-Device_Lib_V2.1.0) on my STM32F4 i got an error code on my Win7 x64 sytem. ''This device cannot start(code 10)'' I'm using the USB HS Port on PORTB in FS mode. Finally i found a solution for it. The source code of the file usbd_conf.h must be changed in the following way: Old: /* CDC Endpoints parameters: you can fine tune these values depending on the needed baudrates and performance. */ #ifdef USE_USB_OTG_HS #define CDC_DATA_MAX_PACKET_SIZE 512 /* Endpoint IN & OUT Packet size */ #define CDC_CMD_PACKET_SZE 8 /* Control Endpoint Packet size */ New /* CDC Endpoints parameters: you can fine tune these values depending on the needed baudrates and performance. */ #ifdef USE_USB_OTG_HS #define CDC_DATA_MAX_PACKET_SIZE 64 /* Endpoint IN & OUT Packet size */ #define CDC_CMD_PACKET_SZE 8 /* Control Endpoint Packet size */ This change is only necessary when using t

I've had problems with sd_diskio.c used for SD card I/O with FatFs.CubeMX version is 6.16.0.I'm using SDMMC with DMA, so consideration needs to be given to cache coherency and alignment.I have both these set:#define ENABLE_SD_DMA_CACHE_MAINTENANCE  1#define ENABLE_SCRATCH_BUFFERHowever, I've found some bugs in the code:In SD_read, the alignment check:#if defined(ENABLE_SCRATCH_BUFFER)if (!((uint32_t)buff & 0x3)){#endifshould have the 0x3 changed to 0x1f, as cache alignment requires 32-byte alignment, not 4-byte.There's another case of this in SD_write.Furthermore, there's a bracketing problem in SD_write with the code under ENABLE_SCRATCH_BUFFER conditional compilation, which is supposed to be invoked when the buffer is misaligned as an else condition for if (!((uint32_t)buff & 0x1f), but is instead an else condition for a DMA success check. This means that the scratch buffer code does not run at all when a buffer misalignment is detected.To fix it, I added a closing brace

Hi, I'm using an stm32f102 for making usb game controller (custom hid) with 29 buttons. The problem is, that the latency if I check on PC is feelable, too high. I made some tests to figure out the problem, but I don't have any idea yet. If I just report continiusly in the main while with 50ms delays, the indicator led on game controller window on pc just blinks with ~1s. So, seems, don't receive all of the data. If I increase this delay to 100ms it looks almost fine. I tried also to measure latency with camera (measure the time between click sound and the indicator on pc screen). For STM32 was around 5-6 frame with 30fps. I tried also with a good working game controller, it is 2-3 frame. If I report with every 1ms from systick, it's not better. I looked into the send report function and experienced, that the function sometimes returns with busy, even if data send is with 50ms interval. Why? :o In the MCU runs everything on 48MHz and in the test is just a gpio read and report. Any idea?

Im using STM32SD library on my stm32f407vet6 board.  I want to make a logging system for my application. My initial logic is: on setup we count number of files in our root directory and create a new file named dataLog{fileNumber}. Then we write data into that file and check if its not empty. In given code example im always getting only last write into file (fouth write). As ive got this library only works in FILE_WRITE or FILE_READ modes. I trtied to use FA_OPEN_APPEND modifier but when im using this im getting errors while file creating.And another thing is that im always getting a lot of initialization errors and file open errors overall while using this library, maybe it depends on me using stm32f407vet6, any advices would be great. Now i will try to use an advice from github issue of "unstable work with sdcard on stm32f4" - i'll try to redefine the value of the SD_CLK_DIV to bigger value.     #include <STM32SD.h> int fileNumb

Hello,I am trying to get Ethernet-over-USB working on a STM32U585. I want to be able to use both RNDIS and CDC-ECM, but I decided to start with RNDIS first. After a lot of trial and error and research, I am running out of ideas as to why my PC does not show any devices in USB Viewer on the port where I connected the circuit board. I am developing on a B-U585I-IOT02A.I based my work on the following example: https://github.com/STMicroelectronics/stm32-usbx-examples/tree/main/Projects/STM32H735G-DK/Applications/USBX/Ux_Device_RNDISI provide my code here (if not mentioned it is generated by CubeMX). I did not touch files if code is not shown here:main.c: int main(void) { /* Reset of all peripherals, Initializes the Flash interface and the Systick. */ HAL_Init(); /* Configure the System Power */ SystemPower_Config(); /* Configure the system clock */ SystemClock_Config(); /* Initialize all configured peripherals */ MX_GPIO_Init(); MX_ICACHE_Init(); // HINT: this function

我使用的芯片是G071RB，当我使用STM32UCPD发status，直接从FF01(PD协议的DP模式)变成0x00000，并且在抓包发现再发送的时候没有发VDO000000001，返回的数据中HPD为0，有没有大佬知道怎么解决 Translation: I'm using the STM32G071RB MCU. When I send a status update using STM32UCPD, it jumps directly from FF01 (DP mode of the PD protocol) to 0x00000. Packet capture shows that VDO000000001 is not sent during retransmission, and HPD is 0 in the returned data. Does anyone know how to solve this?

I have one question regarding the HAL_FLASH_Program function. I use the HAL_FLASH_Program many times during the runtime of the firmware. I use it to store log, warnings and errors in the several flash pages. When the page is full and I must write into it I erase the page, obviously.   However, at the very begining I also want to store the "reset cause" (an entry in the flash pages) of the last power cycle (switch on off). Was it a BOR, WWDOG, IWOG, PINRST, etc, etc,..? Unfortunately, I am unable to successfully use HAL_FLASH_Program with a HAL_OK. It seems as if HAL_FLASH_Program does not work at the very beginning of the firmware application... does it sound crazy? Could it be that this function needs some time to work.  /** * @brief The function's role is to save the log data into the log page/s. */ mid_error_t flash_program_loop_2(const uint8_t * data_in) { HAL_FLASH_Unlock(); /** * first we check if the next position to writ

下面是我的部分函数，普通串口按照这个配置，是可以正常进入回调函数，但是LPuart却不能进入回调函数，不知道问题出在哪里，使用stm32cubemx6.16.0,附件是ioc文件，   Post Edited by ST moderator to apply source code formatting and translate from Chinese to English to comply with the community rule:   Below are some of my functions. With this configuration, the standard serial port can enter the callback function normally, but LPuart cannot. I'm unsure where the issue lies. Using STM32CubeMX 6.16.0. The attached file is the I/O configuration file.   void StartControlPowerTask(void const * argument) { /* USER CODE BEGIN StartControlPowerTask */ HAL_StatusTypeDef ret; __HAL_UART_ENABLE_IT(&hlpuart1, UART_IT_IDLE); __HAL_UART_CLEAR_IDLEFLAG(&hlpuart1); ret = HAL_UARTEx_ReceiveToIdle_DMA(&hlpuart1, rxl1_dma_buffer, RX_BUFFER_SIZE);//rs232 /* Infinite loop */ for(;;) { osDelay(1); } /* USER CODE END StartControlPowerTask */ } void HAL_UARTEx_RxEventCallback(UART_HandleTypeDef *huart, uint16_t Size) { if (huart->Instanc

When using a USB CDC device, especially at high data rates, there is a possibility for packet loss. This post illustrates the issue with what I consider convincing evidence. This isn't a STM32 bug, but it's something you may encounter when interfacing with an STM32 device so I felt it is relevant here. As a bonus, this also shows the achievable speeds with USB FS CDC to be ~9.2 Mbps under ideal circumstances (fast, good code on both sides of the connection).   Here's the setup to illustrate the issue: On the STM32, I'm initializing a USB FS CDC device (sometimes also called a VCP) and sending out packets as fast as possible. The bus speed of USB FS is 12 MHz. Buffers of 16 kB are sent which contain increasing uint64_t values (e.g. 0x0000000000000000 0x0000000000000001, etc...) When one buffer finishes, the next one is sent out. (I used STM32CubeMX to do the initialization code and it worked perfectly.)   On the PC side, I'm opening the serial port in Python and reading data

Good evening, now that I can ping my F767ZI board with my laptop, I'm trying to use some tutorials on the web to be able to send data (numbers or message strings) to a server (Hercules software set as a TCP server), but I'm having some difficulties (I don't know whether to use semaphores or timers as interrupts, and for semaphores, it's not entirely clear to me how to use them). I'm wondering if there's a short guide for my board that can give me a starting point. I'm using CUBE IDE V1.18.1. I tried starting from the project that allows me to ping my board, but as soon as I try to make some changes, the ping no longer works, and the timer set as an event interrupt doesn't work anymore, so I would need a tutorial as an example (the tutorial I followed successfully had a UDP library, but now I'll have to use the TCP libraries I already have, but I'm having some difficulties).   Here below the code that I used for start point and that is give to me the way to ping my board succesflul