Solved

Hello,We are working with an STM32F03 and an ECS-320-8-37B-CKY-TR 32 MHz crystal (CL = 8 pF).Our earlier design used an 8 MHz crystal (CL = 8 pF) with 4 pF load capacitors and a 5.1 kΩ series resistor. After switching to the 32 MHz crystal, the HSE no longer starts. This sparked criticism about the correct component values depending on the crystal used.Here are some results from my testing with 32 MHz + 5.1 kΩ:Startup works reliably at ~0 Ω and ~1 kΩMarginal at ~1.5 kΩFails at ≥2 kΩBased on the ECS-320 datasheet (CL = 8 pF, and estimated ~3 pF stray), the correct load capacitors should be ~10 pF each, not 4 pF.Where we are unsure is the interpretation of AN2867:Harmonic suppression (§3.5.3): Formula Rext = 1/(2πfCL²) → ~1.2 kΩ at 32 MHz with 4 pF loads, which matches our *failing* results.Drive level trimming (§3.3): Says to use Rext = 0 Ω unless the drive exceeds the crystal spec. We don’t have low-C probes to measure the drive directly.Empirical: Anything in the hundre

Hi, Dear STM experts:I used MCSDK6.3.2 HSO for BLDC control when porting from stm32Q473 to stm32f405, but when using void IMPEDCORR_setLs_si(IMPEDCORR_Handle pHandle, const float_t Ls_H); A hardware failure occurred during the function, and the possibility of external parameter input has been ruled out. Therefore, I would like to confirm again that the libImpedCorr. a library file must rely on the stm32Q47x chip to run?If necessary, then I can only give up the transplant.Hope to receive a reply。Best Regards.

I am using NUCLEO-WL55JC1 to use LoRa communication. And I add acceleration sensor of LSM6DSOX to this board and I want to get  acceleration data while communicating LoRa. But I could not get correct acceleration value. And I could get correct acceleration value when I comment out  MX_LoRaWAN_Process() in main.c. So It seems that acceleration sensor doesn't work when LoRa is enable. Do you know why and could you give me advices of this issue.    

 Hello Community, I am using 2 function calls __LL_ADC_CALC_VREFANALOG_VOLTAGE();__LL_ADC_CALC_TEMPERATURE_FLOAT();My implementation:uhADCxConvertedData_VrefAnalog_mVolt = __LL_ADC_CALC_VREFANALOG_VOLTAGE(aADCxConvertedData[1], LL_ADC_RESOLUTION_12B);temperature = __LL_ADC_CALC_TEMPERATURE_FLOAT(uhADCxConvertedData_VrefAnalog_mVolt, aADCxConvertedData[2], LL_ADC_RESOLUTION_12B); I am seeing the above macros not respond and there is a hard-fault whenever I call the above functions. Any help would be appreciated.  Thank you

Hello,I am trying to use the GPDMA linked list on an STM32U5 to toggle seven chip-select GPIOs before and after SPI transfers.Setup:MCU: STM32U575ZITXI build a linked list of nodes:Write CSx_Pin to GPIOx->BRR (drive CS low)Dummy delay node (memory→memory)Write CSx_Pin to GPIOx->BSRR (drive CS high)word width, DataSize = 4, SrcInc = FIXED, DstInc = FIXED.Destination addresses are the GPIO BSRR/BRR registers.Problem:Only 3 out of 7 chip-select pins actually toggle when the DMA queue runs. The working pins are:PE3PE1PB6The non-working ones are on GPIOG (PG9, PG11, PG13) and PB8.If I write to these pins directly from the CPU with HAL_GPIO_WritePin, they work correctly. Only DMA writes fail.Questions:Are all GPIO ports on STM32U5 supposed to be reachable by the GPDMA?Is there a known limitation where certain GPIO ports (e.g. GPIOG) cannot be written by DMA?Any clarification on which GPIO ports are DMA-accessible would be appreciated.Thank you.Linked List Setup Code :#define ADC_COUNT

Hi all, I'm using Nucleo H755 I have configured UART with 115200 baud rate and the Rx in Interrupt mode issue: While the STM is configured with 115200 baud rates, when I transmit some data with the same baud rate either the data is corrupted or data is not read/ transmitted, if I reduce the baud rate of the other device by 3 times the baud rate set in ST the Data is read properly. if anyone have any solution regarding this issue, please let me know in this thread I have checked with different STM ide versions, different H755 boards I'm facing this same issue also, I have checked with H723 which is working fine for the same setup. there are different issues with the H755 boards. also, if anyone from STM team finds this message I'm also facing a issue while reconfiguring the ioc file from cube ide some pins get reset every time If any other details required, please feel free to ping me

I have a custom stm32f746 project.  Touchgfx main app is working.  LCD is 800x480I developed a bootloader that is also working.Now just want minimum necessary peripherals to allow simple TEXT output to LCD to show bootloader status.  Trying to keep bootloader to ~64k, so no TouchGFX.But, I have setup FMC, MPU, and LTDC similar to the main TouchGFX app.I am able to print 3 colored bars to the screen:    uint16_t *fb = (uint16_t*)0xC0000000; // RGB565 view const int W = 800, H = 480; for (int y = 0; y < H; ++y) { uint16_t color = (y < H/3) ? 0xF800 : // Red (y < 2*H/3) ? 0x07E0 : // Green 0x001F; // Blue for (int x = 0; x < W; ++x) fb[y*W + x] = color; }Then when I try to print a smaller green box, it still fills across the width of the screen, distorted, and does not go from 40,320?:  for (int y = 40; y < 120; ++y) for (int x = 40; x < 320; ++x) fb[y*800 + x] = 0x07E0;Then when I try to write text I get a thin fluctuating li

Hello everybody,in our application, we want to avoid using the ADC software calibration procedure (not even once).We hence think about writing a fixed value to the Calibration register CALFACT as we saw that most of the times the calib value is very close to 64 (half of the 7-bit range).We can accept a comparably high offset error of the ADC (+-12LSB at 12 bit) and from our measurements so far we think we can work without calibration, however we cannot find any worst-case offset values for the uncalibrated ADC anywhere. So our questions are:Can you confirm that 64 is the somewhat "neutral" value for CALFACT?Where can I find the worst case offset error of the ADC without calibration? Best regards and thank you very much in advanceSamuel

We are interfacing a Chafon MU910-M UHF RFID reader module with an STM32F103C8T6 (Blue Pill) board using UART communication. During loopback testing, we observed that individual UART ports are functional and can transmit single byte, but when attempting to transmit an entire byte/frame, the transmitted data is not received back.We have verified the following:External connections are correct (Tx ↔ Rx, common GND).Code implementation is correct based on STM32 HAL/LL libraries.UART peripheral initialization works when tested with single-byte transmission.However, the issue arises when transmitting multiple bytes (frames), where the data is either not looped back correctly or is lost.Have anyone faced this kind of issues? We are looking for guidance on the next debugging steps, specifically why the UART works for single-bit/byte transmission but fails for multi-byte frames during loopback testing.

Hi,We are using the LSM6DSO in our project to find the euler angles.we are new to this motionfx in stm32. please tell us from where we have to start to find the euler angles.Do we need to add any of the files in the stm32?please tell us from the beginning.

Hi, I am evaluating the STM32H7R7Z8J6, intended to working with a TFT-LCD which is working in parallel RGB interface with DE mode only. The HSYNC and VSYNC signals are not connected. Both AN4861 (Introduction to LCD-TFT display controller (LTDC) on STM32 MCUs) and RM0477 (STM32H7Rx/7Sx Arm®-based 32-bit MCUs) documents only SYNC+DE mode, but the does not mention if the DE-mode-only is supported or not? Could you help to point out the documentation where explains how the LTDC working for DE mode in detail?  Thanks! Leo    

Hi,Im analyzing the circuit of the STGAP3SXS in EVLSTGAP3SXS-.I want to ask what's the purpose of this capacitance in the soft off pin, I thought it was filtering by why does it go to the VL instead of GND_ISOThank you.

Hi everyone,I am working on an STM32H7A3ZI and I'm trying to to exchange audio data with an SGTL5000 audio codec. Because i want to both send and receive data from the codec i configured the I2S peripheral on the STM32 to Full-Duplex Master mode in Cube MX.My problem:Transmitting data using the HAL I2S functions (HAL_I2S_Transmit, or HAL_I2S_Transmit_DMA) works fine, but when i try to receive data (also using the HAL functions) the bit- and word-select-clock won't start. If i first transmit data and then try to receive everything works fine, because the clocks stay on. If i change the I2S config to Half-Duplex Master Receive mode, just receiving also starts the clocks.So in Full-Duplex Master mode i have to transmit data first (or at least write some data into the transmit data register, which starts the clocks), before i can receive data.My question:This seems to be intended behavior, but i couldn't find any documentation on it. Why is this implemented like that?

Sorry, I'm very new to microcontrollers in general and was wondering if I would need more SRAM or if I could successfully just write to the display driver's memory and not worry about a big frame buffer. I hope to use LVGL to control a 320x240 16 bit colour depth display using this method, any help on this topic would be greatly appreciated, thank you.For reference, the reason I'm interested in doing this is because I'm using the STM32 F4VE Black board and I can see it has a TFT interface.

Hello everyone,I tried to create an STM project using existing .ioc files from my friend. They suggested choosing the Migrate option, but unfortunately, it didn’t work for me. For context:I’m using Windows.The same migration process works perfectly on Mac.When I open the main code, I only see the basic template code that appears when starting a new project—all the code from my friend has disappeared.I’ve already tried reinstalling the STM software, but that didn’t help either.Has anyone encountered this issue or can suggest a workaround?Thanks in advance for your help! 

Hi,I am trying to get the USBX CDC working on a NUCLEO-U083RC, but with no luck.I have tested that the USB port (PA11 and PA12) works, because I can do firmware upgrade using the STM32CubeProgrammer.But I cannot find any example on how to get the USB CDC (Virtual Comport) working.I have spend most of a day trying different examples, but nothing seems to work for me.Do anyone have any help to offer regarding a working example ? Best RegardsJakob

We sincerely appreciate your continued support. We have been able to resolve many questions.In the CTRL1_XL register of the ASM330LHH, when setting ODR_XL[3:0] from 0000 (OFF) to 0011 (52Hz) and then to 1001 (3333Hz), does ODR_XL[3:0] need to be set back to 0000 (OFF) once ?

Hello, I installed X-CUBE-AI 10.2.0 from STM32CubeMX in STM32CubeIDE 1.18.1. After enabling X-CUBE-AI in the ioc file and performing code generation, the folders /Middlewares/ST/X-CUBE-AI/Inc and /Middlewares/ST/X-CUBE-AI/Lib are created, but no code is generated in those folders. Therefore, when building the project, I get an error such as:fatal error: ai_platform.h: No such file or directoryIn Project Manager → Code Generator → Generated files panel, I unchecked the option “Delete the previously generated files when not regenerated” and regenerated the code, but the problem was not solved. Please help me.If there is any necessary information that I have not provided, please let me know.This message was translated into English using generative AI. I apologize for any awkward sentences or expressions.Thank you.

RAM Overflow and X-CUBE-AI Quantization Analysis Error with PyTorch Model on STM32F401REHello everyone,I'm working on deploying a PyTorch model to an STM32F401RE NUCLEO board and encountering some challenging memory and quantization issues that I hope the community can help me resolve.Project ContextMy project involves running a custom PyTorch model (converted to ONNX format) on the STM32F401RE NUCLEO board. The system already has USB Host (Audio Class) library and FreeRTOS integrated as essential components for my application, which means I need to work within the remaining available memory space.Development EnvironmentBoard: STM32F401RE NUCLEO (96KB SRAM)IDE: STM32CubeIDE 1.18.1X-CUBE-AI: 10.2.0Additional Libraries: USB Host (Audio Class), FreeRTOSModel: PyTorch → ONNX convertedProblem 1: RAM Overflow During BuildWhen I configure X-CUBE-AI with compression set to high and optimization set to ram, the build process fails with a linker error:C:/ST/STM32CubeIDE_1.18.1/STM32CubeIDE/plugi

Hi. I just ordered a brand new NUCLEO-N657X0-Q, and cant connect to it using STM32CubeProgrammmer. I tried using ST-Link in different modes and reset modes. I also tried using external loader, and discovery under debug authentication, got the error message in the screenshot.Would appreciate some help.

I have a problem I can't solve.In a previous project, I used an STM32L4A6 and set the PC8 and PC9 lines high before entering the system bootloader. After starting the system bootloader, these lines remained high. They were used to maintain power to the device.In the new project, the MCU was changed to an STM32F446. I used the PD10 and PD12 lines to maintain power after confirming with the AN2606 that they were not being used by the system bootloader. Unfortunately, after starting the bootloader, both lines are reset.Why does this happen?

Apologies if this is the wrong group for this query. I have implemented a library from scratch which performs the host side of a DFU upgrade (avoids the dependencies in CubeProgrammer_API.dll, for which I could not find source). The code works just fine but I have a question about the expected values of bAlternateSetting across the whole range of STM32 devices.For the STM32U575, there are three DFU Interface Descriptors with bAlternateSetting values of 0, 1 and 2. These correspond to 0=Internal Flash, 1=Option Bytes, 2=OTP Memory. [This is very clear from the memory descriptor string corresponding to the iInterface value of each interface.]My question is: are these values consistent across the range of STM32s, or might some devices have (say) 1=Internal Flash or whatever?Is there any available documentation for this? I've spent quite a bit of time trawling various UMxxxx and ANxxxx as part of creating this library, but have not found much about bAlternateSetting.The behaviour of D

Hello,I have already use VL53L0X sensor provided by AZ-Delivery.My main problem is that I2C address can be changed but NOT permanently.I am looking to "Adafruit VL53L4CX Time of Flight Sensor". But I don't want to discover the same problem, that is I2C address can not be change permanently. Does the base-component VL53L4CX have the same "disability" ?Is there a TOF component allowing to set and fix this important behavior ?Best regards.

HiReading this post https://community.st.com/t5/stm32-mcus-security/x-cube-azure-h7-hw-cryptographic-acceleration/m-p/634818/highlight/true#M6417 it seems like ST employee is saying STM chips will not support Azure RTOS going forward? Has any decision on this been made? 

I want to add a custom BLE service in STM32CubeMX. I saw on a website that the Add Custom Service feature could be used for this. However, I don't know the procedure for adding a service using this feature. Please tell me the steps to add a service using the Add Custom Service feature in the latest IDE and MX environment.