Solved

HiI am trying to port an example application from MDK to CubeIDE, the CubeIDE does not give me correct compilation result:1. It completes the compilation when code contains syntax error and it produces binary. This is quite different from past experiences with CubeIDE.2. The size of the binary is not correct (88 bytes for an LWIP application is imppossible)3. The CubeMX does not generate startup code startup_stm32f767igtx.s4. There's a warning: cannot find entry symbol Reset_Handler5. MDK uses ARM compiler, therefore how to rewrite the following delarations in CubeIDE:#if !(__ARMCC_VERSION >= 6010050) /* not AC6 compiler */ /* use AC5 compiler */ /* the following 3 declarations are reported syntax error by CubeIDE */ /* internal SRAM */ static __align(64) uint8_t mem1base[MEM1_MAX_SIZE]; /* external SDRAM */ static __align(64) uint8_t mem2base[MEM2_MAX_SIZE] __attribute__((at(0XC01F4000))); /* internal DTCM */ static __align(64) uint8_t mem3base[MEM3_MAX_SIZE] __attribu

Hello everybody,I have a question related to the STM32N6570-DK eval kit. Is it possible to change the position of the BOOT switches when the board is powered by USB-C ST-Link ?  Or do I always have to power-off the board ?Thanks  Max

I’m designing a custom board based on STM32N6 and using the same boot flash as the NUCLEO‑N657X0‑Q (MB1940). In the reference design, all OCTOSPI signals to the flash have 0‑Ω bridges in series, and the traces are length‑matched including those footprints.What’s the main reason for these 0‑Ω parts? Are they only for flexibility during bring‑up (e.g., swapping in damping resistors), or do they serve another purpose? Is it safe to omit them or do they serve a specific reason? Snippet from the MB1940 Schematic:Thanks in advance and best regards,Julius 

I'm encountering many issues while using the AIS2120 accelerometer sensor and would greatly appreciate your assistance. Thank you very much!After the sensor is powered on, a series of initializations (default configuration) are performed, then it enters normal mode, and then the corresponding acceleration data is read. Are these actions performed automatically by the sensor?Do I need to perform any operations to make the sensor enter normal mode?If I need to set it to 1600Hz, how should I operate? (I tried setting a soft reset and then writing to the configuration register, but it didn't work).I keep having communication issues, especially I'm not sure if the CRC check is correct. The manual is very vague. Attached is my CRC check function.I'm also unsure how to fill in the position indicating whether it is sensor data in the SDI frame.uint8_t AIS1120SX_ubCrcVal(int32u ulCrcVal) { uint8_t crc = 0x00; uint8_t poly = 0x97; for (uint8_t i = 0; i < 4; i++) { crc ^= (uint8_t) ((ulC

Hi everyone,I'm working with the VL53L0X sensor and have a couple of questions:Does noise affect the sensor's measurements? Does the sensor include a checksum or mechanism to verify the integrity of I2C messages? Can adding capacitors to the I2C bus help reduce noise interference?Thanks in advance for your help!

Hi everyone, I'm using a Riverdi board (STM32 10.1" Rev. 1.2) with an STM32H747XIH6, and I'm having trouble with the UART8 in single-wire mode. I can't get the interrupt callback function to be called when data is received on that port.This board uses TouchGfx and FreeRTOS.I'm using a test interrupt code just for the UART8, but it's not responding.If I use the blocking function HAL_UART_Receive(...), I receive consistent data, so I don't think it's a wiring or pinout issue. I have checked that the signal is coming in with the oscilloscope.I have the global interrupt enabled for the UART8.The code I'm using is this, in freertos.cvoid startUartTask(void *argument) { /* USER CODE BEGIN startUartTask */ memset(rxBuffer, 65, 128); HAL_HalfDuplex_EnableReceiver(&huart8); HAL_UARTEx_ReceiveToIdle_IT(&huart8, rxBuffer, 64); /* Infinite loop */ for(;;) { //HAL_UART_Receive(&huart8, rxBuffer, 128, 120); osDelay(10); } /* USER CODE END startUartTask */ } In mai

HelloI am trying to get the STMN32G431 processor to do what I want.If I set the baudrates 500kB / 2MB and a samplepoint of 87.5% for both and send a CAN packet with FDF and BRS I get after 3 ms:LastError = Recessive Bit Error and 8 Tx errorsand 2 ms later:LastError = Recessive Bit Error,  248 Tx errors and Bus OFF !Sometimes it is also a Dominant Bit Error.This happens even in Internal loopback mode!Therefore I set a Tx delay compensation of zero.But also with other values for Tx delay compensation, it never works.If I chose the samplepoint up to 85% all is still fine.But with 87.5% I get a BusOff which is 100% reproducable.Now comes the strange thing:HAL_FDCAN_ConfigTxDelayCompensation(&can_handle, 0, 0); HAL_FDCAN_EnableTxDelayCompensation(&can_handle);will produce this problem, but withHAL_FDCAN_DisableTxDelayCompensation(&can_handle);it suddenly works correctly!How is it possible that setting a delay of zero is not the same as a delay that is turned off?Here my set

I use the Flutter NFC Kit library.I enter the password and then use: Extended Read Multiple Blocks"2033XXXXXXXXXXXXXXX00003F00"Request_flags -> 20Extended Read Multiple Block -> 33UID -> XXXXXXXXXXXXXXXFirst block number -> 0000Number of blocks -> 3F00 == decimal 63 blocks (total read 64 blocks)With this line of code, I read 64 blocks, but if I try to read a larger number of blocks, for example, 128 blocks, passing 80h for Number of blocks, I receive an error message and the blocks are not read.Is it possible to read more than 64 blocks with smartphones?

HiI am using STM32MPU25 to evaluate object detection, when i use stai_mpu_object_detection binary to run default ssd_mobilenet_v2 models , i can see object detection works.when i run python scripts to launch application( example : launch_bin_object_detection_testdata.sh) i see below error.root@stm32mp25-discounknownunknown:/usr/local/x-linux-ai/object-detection# sh launch_python_object_detection.shstai_mpu wrapper used :machine used = stm32mp2x with GPU/NPUuser : weston-sh: /usr/local/x-linux-ai/object-detection/stai_mpu_object_detection.py: Permission denied i assume it may be due to weston user and root user.so i copied all objection detection samples to /home/weston and gave appropriate permissions and change user to weston and launch application, i see below errors.^^^^^^^^^^^^^^^^^^^^^File "/home/weston/test/Application/ssd_mobilenet_pp.py", line 129, in get_resultsreturn locations, classes, scores^^^^^^^^^UnboundLocalError: cannot access local variable 'locations'

Hello,i'm starting a project with STM32F407VG and ADAU1466 DSP. The ADAU1466 generates the MCLK for the audio codec (ADAU1701), so far so good.Now i'd like to implement full-duplex I2S communication between ADAU1466 and STM32 too using a different I2S port on the DSP. The idea is to set the STM32 as a slave receiver and let the DSP generate BCLK and LRCLK. In this context, do i need to provide master clock to STM32 too and if so, how? I mean, which pin should i use? For I2S2 i can see PC9 alternate function I2S_CKIN but i'm not sure if this is the proper way to provide external master clock. 

Hello, I'm trying to implement USB communication with a PC using USB1 (USB-C port) on an STM32N6570-DK with CubeMX. Most tutorials I've found on USBX are for older CubeMX versions and boards, so I'm a bit stuck. When I connect the board to my PC, I only get Error Code 43 in Device Manager. Here's what I've done so far: Enabled PA4 as shown in this diagram: Enabled USB1 in CubeMX. Enabled interrupt and feft default settings otherwise:   Enabled USBX. System stack size: 10 * 1024, Memory pool size: 15 * 1024 Additional settings: USB init code: void MX_USB1_OTG_HS_PCD_Init(void) { /* USER CODE BEGIN USB1_OTG_HS_Init 0 */ /* USER CODE END USB1_OTG_HS_Init 0 */ /* USER CODE BEGIN USB1_OTG_HS_Init 1 */ memset(&hpcd_USB_OTG_HS1, 0x0, sizeof(PCD_HandleTypeDef)); /* USER CODE END USB1_OTG_HS_Init 1 */ hpcd_USB_OTG_HS1.Instance = USB1_OTG_HS; hpcd_USB_OTG_HS1.Init.dev_endpoints = 9; hpcd_USB_OTG_HS1.Init.speed = PCD_SPEED_HIGH; hpcd_USB_OTG_

I am working on an STM32 H7 but I assume this applies to other series as well. I wrote an application function to set a timer period based on a uint32_t value which basically contains the following snippet: htim->Init.Prescaler = timerClockFreqInMHz - 1;htim->Init.Period = periodUs;if (HAL_OK != HAL_TIM_Base_Init(htim)){ Error_Handler();}Now this worked as expected for some timers but failed specifically when using timer TIM4. I took some time to debug but I realized only via cubeMX (and later on checked in the manual) that some timers do not have a 32bit ARR register but only 16bit and indeed my "non working behaviour" came from an overflow on the 16bit TIM4. Now going deeper in the HAL, it appears that HAL_StatusTypeDef HAL_TIM_Base_Init(TIM_HandleTypeDef *htim)calls void TIM_Base_SetConfig(TIM_TypeDef *TIMx, const TIM_Base_InitTypeDef *Structure)and here ARR is set /* Set the Autoreload value */TIMx->ARR = (uint32_t)Structure->Period;&n

I'm learning about the I2C interface. The polling method works properly, but the interrupt method is not working correctly.I enabled I2C listen mode, but when I send the address on the I2C line, the address match callback is not triggered.

Hi all,I'm using an stm32f746 and I switched to a stm32u5a9 mcu. I was learning about freeRTOS with the f746 and now it looks like I should be using threadX instead. Since I don't know much about RTOS, switching is not a big deal. But using cubeIDE build in cubeMX I could make multiple threads for freeRTOS before. Now it looks like I can make one in cubeMX by clicking the "generate app init code" and setting the "Create threadX application thread" to true. I know I can add more threads to the files manually. I'm wondering if I can make more than one in cubeMX ... like freeRTOS? Thanks 

Dear All,I am waiting for the availability of the x-Cube-ST67W61 package update to version 1.1.0 which is available on GitHub but doesn't show up in CubeMX at the moment. Do you know when it will be available via embedded package update?Best regards,Peter 

Hi, There's an image in the NUCLEO-WB55RG user manual (UM2435) with the phrase "Wrong Image". Not sure what this is suposed to mean, maybe an internal doc note?     ST Doc team, can you please review?   Best, Alessandro  

Hello ST Community,I am working with the STM32MP257F-EV1 Evaluation Board and following the steps described in the official STM32 DDR Firmware Util documentation as per attached document below.While performing the DDR firmware update and running the DDR utility using STM32CubeProgrammer, I encountered the following issues:When I try to load the DDR utility binary (STM32MP257F-EV1_DDR_UTILITIES_A35_nopad_no_el3lnch.stm32) and other binaries generated in the process have also been uploaded and downloaded same error as in the attached image we have used DFU mode 0000 and in USB connection is used, STM32CubeProgrammer shows an error message:“Error: Please specify Binaries path”for your reference we have attached the image .Environment details:Board: STM32MP257F-EV1Connection: USB (DFU mode)Tool: STM32CubeProgrammer (latest version)OS: Windows 11Binary used: STM32MP257F-EV1_DDR_UTILITIES_A35_nopad_no_el3lnch.stm32Repository: STM32DDRFW-UTILQuestions:How can I correctly set the binaries path

As you can see below picture, B-WL5M-SUBG1 Connectivity Expansion Board's UART pins are PC0 and PC1:But in the STM32Cube_FW_WL_V1.3.1 repository Sigfox_AT_Slave application for B-WL5M-SUBG1 describes uart pins are PA3 and PA2:So in this case, application's UART AT interface doesn't work. Buf if you change LPUART1 pin configurations, it works fine:  Thank you for your interest.

Hello, we are using a STM32H5 with TZ disabled. In firmware, we are doing the following:- set the product state to provisioning (0x17)- provision the debug authenticationThis already works fine. Afterwards, we can do a discovery an see the validity of the DA ( we read 0xeaeaeaea). Regression afterwards works fine.However, we would like to check this validity from within the firmware.1) where does this 0xeaeaeaea comes from? Can we also access it?2) reading back the storage area of the DA (0x0ffd0100) is not reliable. Sometimes, we can read the data we just wrote, sometime we just read 0xff... This depends on the code we execute after writing. It is not a timing issue, should we maybe set a certain flag or something like that? The code we used is based on the github project https://github.com/stm32-hotspot/STM32H5_DA_EmbeddedProvisioning Best regardsPeter

 Weird things are happening.The breakpoint  i set in the void Read_ToF_From_VL53L0X_FreeRTOS_Task(void *pvParameters) task is not getting hitthis task calls VL53L0X_Measure_Distance function in which i set a breakpoint which is working ok ! also i put another breakpoint in the file VL53L0X_FreeRTOS_Queues.c which is called upon initializationthis is also not getting hitis it a problem with teh specific folder?but the VL53L0X_Core_Functions.c also on the same main dirdoes the FreeRTOS dir have any problems?Has anyone experienced this problem?@Andrew Neil @mƎALLEm @TDK 

Hi there,after last Copilot update inside IDE 1.19.0, I always have an error after the project is loaded:After that the IDE close itself, a little window shows a message I'm not able to read (I think it is a update attempt, there is a red label on the bottom, too quick), and then everything is closed.Please, I can i solve it ?? -- ADDEDI found the c:\ST\STM32CubeIDE_1.16.0\STM32CubeIDE\configuration\1756799750460.log file that reports:!SESSION 2025-09-02 09:55:50.216 ----------------------------------------------- eclipse.buildId=Version 1.19.0 java.version=21.0.3 java.vendor=Eclipse Adoptium BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=it_IT Command-line arguments: -os win32 -ws win32 -arch x86_64 !ENTRY com.microsoft.copilot.eclipse.ui.terminal.tm 4 0 2025-09-02 09:55:51.033 !MESSAGE FrameworkEvent ERROR !STACK 0 org.osgi.framework.BundleException: Could not resolve module: com.microsoft.copilot.eclipse.ui.terminal.tm [991] Unresolved requirement: Require-Bun

I'm using several VL53L7CX sensors in a robotics application.  They work well except for when a retroreflective surface is present, which blinds the entire sensor, including SPADs not pointed at the retroreflective surface.  A large retroreflective area is not needed, only a few cm^2 patch.This is a big problem for us since industrial environments are full of retroreflective surfaces (e.g. safety vests, markings on the ground, etc.).I'm currently using the default values for sensitivity, sharpener, etc.  Any parameters you recommend tuning/adjusting to make this sensor more robust?

Hi,I'm try to communicate between my windows pc and my STM32GOB1RE Nucleo 64 board, with the CDC Class.To validate my hardware ( PA11 PA12 and gnd connected to usb pc), i did few dfu flahsing operation with CubeProg without issue. Windows detect properly my device in DFU mode, i can do the programmation and new firmware runs well. -> Hardware looks fine.  I have generated the code with CubeMX and i'm using the HSI to 60mhz. Just this simple code with USB_DRD_FS Usb clock derived from it at 48Mhz.I'm also using the SOF detection and CRS SYNC Source USB.I have added th Code line in usbd_cdc_if, but it is not really the problem.Windows generate Error of not Descriptor reading.Here is the log of the USB Device Viewer, a windows tool that bring information:[Port7] FailedEnumeration : Périphérique USB inconnu (échec de demande de descripteur de périphérique)[Port7] FailedEnumeration : Périphérique USB inconnu (échec de demande de descripteur de périphérique) Is Port User

Hello allI don't know if this is the right sub-forum, I chose the one that seemed the closest.I've been spending a bunch of time trying to find the part number of a seemingly simple IC, but just hitting walls. I've Googled using the manufacturers name and the #, and looked on the 2 companies I use that are also official suppliers Digikey and Mouser, but the 432 number is way too vague.There's IC's with this # in it,like the STM micto-controllers, but they seem too big and complicated, this just generates an error code down a wire to a microcontroller circuit.It seems to be for a LED circuit sensor/ error feedback circuit in a Martin moving light(Concerts, light shows, etc).It seems 432 is the common # between the same IC on the same board on different units on the same board I replaced in the past that the IC was actually cracked (432wp, or 432wq), it has the ST logo on it. It's rectangular 4.3mm x 3mm(.169" x .118"), with 8 pins(4 per side) on the short ends.Other than the error code

Hello,   I have been following a few different Ethernet tutorials for my MCU (STM32H750VBT6TR) I have on a dedicated PCB. Thus far, I have been unable to get a simple ping test working. For reference, I am mostly using this tutorial in combination with this one, but I am not using freeRTOS at this time. I simply want to get LwIP to set up correctly and ping the board so I can then adapt it to a UDP server.   I know my memory locations for the rx/tx designators, and rx pool base, and the LwIP heap are in the right locations (assuming they are as the tutorial states), but my code fails when the LwIP.c file calls netif_add(), which makes me think the issue does not lie within the memory.   Can anyone who is more experienced in simple LwIP implementations help me out here? I am not sure where to turn at this point, as it does not seem people on other posts are having the same issues. I will attach my project files, namely the IOC, so anyone can look to see if there are