Solved

Hello.   I bought Riverdi board and start to develop my code. I found in FREERTOS_M7 Config parameters RTOS CHECK_FOR_STACK_OVERFLOW.   Documentation says   CHECK_FOR_STACK_OVERFLOWParameter Description:FreeRTOS provides two optional mechanisms that can be used to assist in stack overflow detection and debugging.- when CHECK_FOR_STACK_OVERFLOW is set to 1 (option1), one mechanism is used- when CHECK_FOR_STACK_OVERFLOW is set to 2 (option2), both mechanisms are used.If CHECK_FOR_STACK_OVERFLOW is not set to 0 (Disabled), the application must provide a stack overflow hook (or callback) function: void vApplicationStackOverflowHook( xTaskHandle xTask, signed char *pcTaskName );The kernel will call that stack overflow hook whenever a stack overflow is detectedNote: when set to 1 or 2, a function with an empty body is generated in the freertos.c file (to be completed by the user)   So I set CHECK_FOR_STACK_OVERFLOW = 1, trigger a stack overflow by an infinite re

Hello, I am using CubeMX 5.1 and I am aware that it is not possible to activate FREERTOS when STM32_WPAN is activated. Is there any way to integrate FREERTOS with BLE? Is the feature maybe coming out in the future?

Hello, my CubeIDE stuck while looping trying to access  the marketplace where I need to download and install EGit plugin. During this "looping" the window cannot cancel the operation , neither close the window - typical of Java' "runaway" ... After  probably 15 min it reported "internet connection failure" yet the Marketplace window is still looping and unresponsive to any input neither to cancellation attempts. I am using internet non stop while the marketplace is still searching... Also immediately prior to accessing marketplace I logged-in and accessed the STM site to check for updates and got a fast positive reply.This problem with marketplace continues since yesterday.... does it have to do with new updated version 1.18.1 of CubeIDE which I updated recently?Does anybody else have this problem with new IDE ?

I applied real-time patches to the Linux kernel, but when I measured the RT performance using rt-tests, I found that these two services were affecting it: "stm32mp-calibration.service" "stm32mp-calibration.timer." What is the reason for this?Is it appropriate to disable them?thanks~~

I have a board NUCLEO-WL55JC1 and download a LoRaWAN End-Node Example on it form STM32CubeIDE, but it not join to LoRaWAN network sucessfully.My LoRa Gateway is Drgaino-LG308 with TTN(The Thing Network) Server, the frequency is EU868.After some checking, I found the TX is work, the server was accepted and responsed the JOIN request, but my board don't receive any LoRa packet. I also add some log in RadioIrqProcess() when it get irq about Rx but it show nothing.How do I fix it OR figure out what problem is it?

Hi all,I'm running into an issue when trying to deploy a model from to my STM32N6 board.I am following this guide: https://github.com/STMicroelectronics/stm32ai-modelzoo-services/blob/main/object_detection/deployment/README_STM32N6.mdrunning script:python stm32ai_main.py --config-path ./config_file_examples/ --config-name deployment_n6_yolov8_config.yamlBut ending up with following error:deployment yaml:general: model_path: https://github.com/stm32-hotspot/ultralytics/raw/refs/heads/main/examples/YOLOv8-STEdgeAI/stedgeai_models/object_detection/yolov8n_256_quant_pc_uf_od_coco-person-st.tflite model_type: yolo_v8 operation_mode: deployment dataset: class_names: [person] preprocessing: resizing: aspect_ratio: crop interpolation: nearest color_mode: rgb postprocessing: confidence_thresh: 0.6 NMS_thresh: 0.5 IoU_eval_thresh: 0.4 max_detection_boxes: 10 tools: stedgeai: version: 10.0.0 optimization: balanced on_cloud: False path_to_stedgeai: C:/ST/STEdgeAI/2.1/Utili

I am working with the NUCLEO-C031C6 board and tried to to make the user push button toggle the user LED but it stays stuck with no change to the buttonStatus variable, always high (1).I added the counter variable to see if it is continuously incrementing, however, it appears that the code does not loop and gets stuck somewhere, and thus when I press the push button, it is not updating the buttonStatus variable.Can you please see where the issue is:#include "stm32c0xx_hal.h" //Blue button = PC13, BUS AHB1 EN bit 0 #define BLUBTN_Port GPIOC #define BLUBTN_Pin GPIO_PIN_13 //Green LED = PA5, BUS AHB1 EN bit 2 #define GRNLED_Port GPIOA #define GRNLED_Pin GPIO_PIN_5 void PA5_LED_init(void) { __HAL_RCC_GPIOA_CLK_ENABLE(); GPIO_InitTypeDef GPIO_InitStruct = {0}; GPIO_InitStruct.Pin = GRNLED_Pin; GPIO_InitStruct.Mode = GPIO_MODE_OUTPUT_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_LOW; HAL_GPIO_Init(GRNLED_Port, &GPIO_InitStruct); } void PC13_

Hello,      I am trying to work with ST25R3918 part.    I have followed the suggestion here: Solved: ST25R3918 - STMicroelectronics Community for firmware and example usage.    The board itself is a NUCLEO-WL55JC1. I have tried both I2C and SPI communication but I cannot even read chip id reg(0x3F). According to the datasheet Datasheet - ST25R3918 - Multi-purpose NFC transceiver SPI/I2C should work even if the rfid is not in power wake up mode so reading the chip id register should be possible. ST32CubeIDE examples also seem to do the ID reading before any other configuration.   I don't receive anything on SPI/I2C when reading that reg.    I would like to know if somebody which is familiar ST25R3918 is aware of any additional register configuration before being able to retrieve the chip id reg.  Thanks,      Mihai 

I am trying to communicate with an external flash chip “MX35LF1G24AD” using QSPI protocol, but I am not able to. Simple test I implemented was to read chip ID to validate I could get data from external flash (I am using OCTOSPI1 interface). From manufacturer datasheet it is mentioned that command should be sent using 1 line on SDIO0. However, when probing communication, data is sent from SDIO3.   Is it possible to send command, on 1 line, on SDIO0 pin instead of SDIO3?

Hi all,I need to insert fault on upper key of the driver. In order to achive this Im changing dedicated  TIM1 output to Input to output low. After inserting fault motor stops. Is it possible to achive this? Could someone explain what Im doing wrong. Thanks on advance.Dawid 

According to "STM32H562xx/563xx/573xx device errata" (ES0565 - Rev 6 - March 2025).There is three revisions (Rev.A, Rev.B and Rev.X).What is the difference?All revisions in the market for now?If so, how can we oreder Rev.X chip in the market?We would like to use Rev.X chip.

Hi everyone,I'm currently developing firmware for the VL53L1X Time-of-Flight sensor on a breakout board using STM32CubeIDE, and I’m working with the bare driver provided by ST (not the ULD). I’d like to implement the complete calibration sequence, but I’m unsure about the correct procedure and how to manage the physical steps during calibration.Based on the documentation, the recommended calibration order is:RefSPAD CalibrationCrosstalk CalibrationOffset CalibrationI have a few questions regarding the practical and programmatic steps for performing these calibrations using the bare driver functions:1. RefSPAD CalibrationShould this be performed with no target in the Field of View?What environmental conditions are ideal — e.g., should the sensor be facing open space, a dark surface, or something else?2. Crosstalk CalibrationI understand that a grey target should be placed at about 600 mm from the sensor for Full ROI crosstalk calibration.How should I structure the calibration code to pa

Hi,I am using the STM32F103RB (NUCLEO-F103RB) and trying to configure the clocks using STM32CubeMX.According to the official reference manual (RM0008) and datasheet, the maximum allowed APB2 clock frequency is 72 MHz, and I know that peripherals like TIM1 or ADC are connected to APB2.I have tried several combinations of PLL settings:HSE = 8MHzPLL Multiplier = x9 → SYSCLK = 72MHzAHB Prescaler = /1APB2 Prescaler = /1 (PCLK2 = SYSCLK = 72MHz)However, in the CubeMX Clock Configuration tab, even when I do this, the APB2 clock (PCLK2) never goes above 64 MHz. CubeMX simply refuses to allow me to set it to 72MHz. It caps it at 64 MHz.My questions are:Is this a limitation of STM32CubeMX, or does STM32F103RB actually not support APB2 at 72MHz despite the datasheet?If this is a CubeMX issue, is there a workaround or a manual fix for it?How can I really run TIM1 or ADC at their maximum clock (72MHz) as stated in the datasheet?I'd appreciate any clarification or feedback from ST engineers or other

I've just compiled the USB_Example.cpp example and its reporting an initialization error on running (The application could not initialize correctly (0xc000007b)), I have VS 2022 fully updated, I did not migrate the project to the latest toolset to avoid problems.Any ideas STM team? D:\Program Files (x86)\STMicroelectronics\STM32Cube\STM32CubeProgrammer\api\project\Visual Studio\x64\STM32CubePrgAPI\/../../../../lib/STM32CubePrgAPI.exe (process 25224) exited with code -1073741701 (0xc000007b).To automatically close the console when debugging stops, enable Tools->Options->Debugging->Automatically close the console when debugging stops.Press any key to close this window . . .

I have installed and working Cube programmer v2.13 in a Windows 7 32bits machine. Today, I tried to update it but it threw an error:I tried reinstalling and have the same results. I also tried older versions and the last one that works for me was the v2.15. I update java as well but nothing changes.This means that newer versions will not work on Windows 7 32bits machines?

Hi,I am trying to interface Stm32h745 controller with a 240x320 TFT LCD over FMC. Interesting thing is, when I manually control lcd control and data pins(Set them as GPIO_OUTPUT_PP), Lcd works, but when I switched to FMC it does not. Tried lots of timing configuration but it did not help.Here is the init for FMC .Instance = FMC_NORSRAM_DEVICE; .Extended = FMC_NORSRAM_EXTENDED_DEVICE; .Init.NSBank = FMC_NORSRAM_BANK1; .Init.DataAddressMux = FMC_DATA_ADDRESS_MUX_DISABLE; .Init.MemoryType = FMC_MEMORY_TYPE_SRAM; .Init.MemoryDataWidth = FMC_NORSRAM_MEM_BUS_WIDTH_8; .Init.BurstAccessMode = FMC_BURST_ACCESS_MODE_DISABLE; .Init.WaitSignalPolarity = FMC_WAIT_SIGNAL_POLARITY_LOW; .Init.WaitSignalActive = FMC_WAIT_TIMING_BEFORE_WS; .Init.WriteOperation = FMC_WRITE_OPERATION_ENABLE; .Init.WaitSignal = FMC_WAIT_SIGNAL_DISABLE; .Init.ExtendedMode = FMC_EXTENDED_MODE_DISABLE; .Init.AsynchronousWait = FMC_ASYNCHRONOUS_WAIT_DISABLE; .Init.WriteBurst = FMC_WRITE_BURST_DISABLE; .Init.Conti

Hi,I am currently working with the STM32F334 and STM32G474 microcontrollers, and I have a couple of technical questions that require deeper insight into how the HRTIM (High-Resolution Timer) operates in these devices.Q1. Can HRTIM generate a high-resolution variable-frequency waveform?From my own testing, it appears yes, but I would like to confirm this officially. To clarify what I mean: suppose I am designing a resonant converter operating at 1 MHz. In the STM32F334, the HRTIM supports an effective edge resolution of ~217 ps, equivalent to a virtual clock of 4.608 GHz. This means the period register value for 1 MHz would be 4.608GHz/ 1MHz = 4608. Now, if I reduce the period by just one count 4.608GHz / 4607 = 1000217MHz This implies a frequency resolution of ~217 Hz. However, if high-resolution control were not supported for the period register, the period would instead be based on the timer base clock 144 MHz / 143  = 1.006993MH

I'm trying to test writing my own DFU client and I have the simplest of code to start with, see below: #include <CubeProgrammer_API.h> int main() { dfuDeviceInfo* dfuList = nullptr; // Enumerate the available DFU devices int iCount = ::getDfuDeviceList(&dfuList, 0xDF11, 0x0483); if (iCount != 1) { return 0xFFFFFFFF; } int iResult; //#define TRY_VERSION_2 #if defined(TRY_VERSION_2) dfuConnectParameters params; params.usb_index = dfuList[0].usbIndex; params.rdu = 0; params.tzenreg = 0; if ((iResult = ::connectDfuBootloader2(/*m_pDFUDeviceUSBIndex*/params)) != 0) #else if ((iResult = connectDfuBootloader(dfuList[0].usbIndex)) != 0) #endif /* TRY_VERSION_2 */ { ::deleteInterfaceList(); return 0xFFFFFFFF; } ::disconnect(); ::deleteInterfaceList(); return 0; } connectDfuBootloader and connectDfuBootloader2 always return:  /** Operation not supported or unimplemented on this interface */ CUBEPROGRAMMER_ERROR_NOT_SUPPORTED = -5, I'm b

Hi,I am trying to plot an array of 512 values in a dynamic graph in touchgfx. This is working as intended but I am experiencing poor performance. When in histogram mode the graph updates quickly however I wish to use line mode and when in this mode, the graph will take between two and three seconds to update. I'm aiming to get the graph to update in around one second. Any ideas on how to optimise the plotting of the graph. Perhaps the way in which the data is passed from Model.cpp into the screenView.cpp?Currently I am passing the data through as such:for(int i = 0; i < 512; i++) { modelListener->UpdateGraph(i, graphData[i]); }Any help would be greatly appreciated.Thanks.

We set up classic CAN on the stm32h747I-DISCO dev board and listen for interrupts on every message:extern "C" void HAL_FDCAN_RxFifo0Callback(fdcan_handle* hfdcan, std::uint32_t RxFifo0ITs) { if ((RxFifo0ITs & FDCAN_IT_RX_FIFO0_FULL) != RESET) { LOG_ERROR("FIFO0 full\n"); } if ((RxFifo0ITs & FDCAN_IT_RX_FIFO0_MESSAGE_LOST) != RESET) { LOG_ERROR("FIFO0 message lost\n"); } if ((RxFifo0ITs & FDCAN_IT_RX_FIFO0_NEW_MESSAGE) != RESET) { if (auto* can_reader = can_reader_instance.load(); nullptr != can_reader) { can_reader->flush(can::fdcan1); } } } in flush(), we call HAL_FDCAN_GetRxMessage() over and over to read the FIFO elements into an std::vector and then we print them from the vector. We are anticipating an average message frequency of 1 message per 1ms, but at this speed, we are seeing the FIFO fill up faster than we can read from it. The fastest I have seen a message be handled on our device is around 7ms per message. Should we be able to read the me

I'm trying to crank up the clock to Timer1 to be able to count high frequency events with better resolution.  If I set the SYSCLK to 128 I get a hard fault when my code reaches SystemClock_Config().  Even if I keep the AHB bus at the same speed (64Mhz) using prescaler.  In this case the only clock difference seems to be SYSCLK value.Here's the first configuration which works ok:and here's the other where it will hard fault:Since the IDE says I should be able to take HCLK to 160Mhz which would require a much higher SYSCLK, I don't see why this SYSCLK value should cause a fault.

Hi,I would like to know why when I sent the 202 bytes from pc to dev-board via USB HID, the buffer size would only get 32 byte each time, (byte[0]-byte[31])*several times until finished print out all 202 bytes?Couldn't it recieved whole 202 bytes then print out continuously from byte[0] to byte[201]?ux_device_keyboard.c /** * @brief USBD_HID_Keyboard_SetReport * This function is invoked when the host sends a HID SET_REPORT * to the application over Endpoint 0. * @PAram hid_instance: Pointer to the hid class instance. * @PAram hid_event: Pointer to structure of the hid event. * @retval status */ UINT USBD_HID_Keyboard_SetReport(UX_SLAVE_CLASS_HID *hid_instance, UX_SLAVE_CLASS_HID_EVENT *hid_event) { UINT status = UX_SUCCESS; /* USER CODE BEGIN USBD_HID_Keyboard_SetReport */ UX_PARAMETER_NOT_USED(hid_instance); UX_PARAMETER_NOT_USED(hid_event); //Receive Output report from PC if (hid_event == UX_NULL || hid_event->ux_device_class_hid_event_length < 2) return UX_ER

Hi everyone,I’m working with an STM32H753ZI and trying to interface a 32GB SDHC card via SPI using FatFs.The SPI connection seems fine (I can read 0xFF repeatedly), but the SD card does not respond to CMD0 or CMD8 — both return 0xFF. As a result, f_mount fails with error code (3).Test setup:STM32H753ZISPI1 @ 256 prescaler3.3V SD Card Module (Pzsmocn PZSSD001)Netac 32GB SDHC card (format is FAT32 )Observed:SPI lines work (0xFF received repeatedly).CMD0 and CMD8 always return 0xFF.Tried keeping CS low, delaying, reformatting — no change.Questions:Is 32GB SDHC over SPI known to have compatibility issues on STM32H753ZI?Any proven SD cards or modules you recommend?Any other suggestions to debug this issue? Thank you for any help or advice!

Hi guys.I am using STM32H7B3LIHQ MCU, MX25LM51245GXDI00 flash and IS42S32800J-6BLI RAM with NHD-4.3-800480CF-ASXP-CTP TFT screen. I configured the LTDC, FMC, OCTOSPI, TouchGFX and FREERTOS settings. I have a 2 problem.1- I added textArea in the screen for trying. I am increasing the "counter" register and displaying its value in the textArea at 100 mS intervals. But counter register does not inreasing the 100mS intervals, it increasing in 1000mS intervals. FREERTOS TICK_RATE_Hz = 1000 and this is code;void screenView::handleTickEvent() { static int tickCount = 0; if (tickCount++ >= 100) { Unicode::snprintf(textArea1Buffer, TEXTAREA1_SIZE, "%u",counter); textArea1.invalidate(); tickCount = 0; } if (counter >= 17000) counter = 0; else counter++; }2- I added an image with a resolution of 800x480 to the screen. The textarea is on this image. Every time I refresh the screen (textArea1:invalidate()), the screen dithering. But sometimes (1 time i

Hi everyone,I'm trying to drive a WS2812 LED strip (20 LEDs - Strip has 60 LEDs) using an STM32L432KCUx, but so far without success.I've tested multiple approaches — PWM with DMA, SPI-based encoding, and bit-banging via GPIO — but none of them produce stable or correct results. Sometimes up to 22 LEDs light up instead of 20, and the colors are often wrong or appear white.Occasionally, the first LED doesn’t light up at all, which seems to indicate timing jitter or inaccurate bit timing.Setup:Microcontroller: STM32L432KCUxNo external HSE crystal or LSE availableSYSCLK = 48 MHz, tested using both MSI via PLL and HSI via PLLOutput pins used:PA12 for SPI and bit-bangingPA9 for PWM (TIM1_CH2)SPI clock set to 2.4 MHz (used for encoded WS2812 bitstream) SYSCLK = 38MHz3.3 V logic level used for WS2812 data line (no level shifter)LED strip powered with 5 V USB - GND connectedAdditional info:I confirmed the LED strip and wiring are working:Using an Arduino, the same strip works immediately and re