Solved

  I'm working with an STM32G431KBUx and trying to output a waveform via DAC1 using DMA and TIM6 as trigger (TRGO). I’ve successfully configured the DAC and DMA using STM32CubeMX.  However, the DMA callbacks HAL_DAC_ConvCpltCallbackCh1 and HAL_DAC_ConvHalfCpltCallbackCh1 never get called. Here’s what I’ve checked so far: DMA handle is linked manually:hdac1.DMA_Handle1 = &hdma_dac1_ch1; Trigger is set to Timer 6 Trigger Out event. DMA is configured in Circular Mode. I'm calling HAL_DAC_Start_DMA(...) with a buffer of 2 * 64 samples (12-bit aligned). Callback functions are correctly named and defined in main.c: void HAL_DAC_ConvHalfCpltCallbackCh1(DAC_HandleTypeDef *hdac1) {// Never called}void HAL_DAC_ConvCpltCallbackCh1(DAC_HandleTypeDef *hdac1) {// Never called} /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ***************************************

We have a 480W 800H  TFT display that TouchGFXDesigner can nicely display in landscape mode instead of portrait.The trouble is that the device UI is now upside down. TouchGFXDesigner doesn't seem to accept other display rotations such as 180 and 270. Correct? The designer does allow for the text to be rotated 180 which would look correct on our display. But that has other consequences.Has anyone else had this issue?      

 Hi all, I'm back with another question re: our 5-TOF setup (VL53L4CX x 5, all 'looking' out of the centre of a spherical sculpture, trying to detect and interpret people approaching and interacting with it).I posted earlier about trying to multiplex these 5 sensors to avoid crosstalk, and that sort-of-worked but introduced enough lag that it wasn't worth it -- we have carefully managed the positioning of the cones and I don't think we are getting much crosstalk, or at least, once we started throwing out rangeStatus 4, 12, and 11 we got pretty good results.  We are basically only using rangeStatus 0 readings now.Further note: we are looking for targets at about .75-2.5m, so right at the edge of where these results seem reliable.My question is:I'm seeing a bit of 'bouncing' where on one read a sensor will report 2 targets, then just one, then back to 2... since we're only taking the 0 rangeStatus readings, I'm going to assume that it's basically having trouble confirming a sec

I am currently using the STM32N657 to drive an 800x480 pixel display with 24-bit color. The problem that I am running into is the buffer that I need uses 1.1MB (800*480*3 = 1.152MB). Using just FSBL, I am limited to 511KB of SRAM. I know that this chip has 4.2MB of SRAM on it, so how do I access that SRAM for my buffer?

I am developing a board using an STM32U535RETQ - 64 pin QFP pkg. The part is an SMPSU capable "Q" variant - although we are only using the STM's internal LDO... NOT the SMPSU.I am using CubeMx 6.14 and StmIDE 1.18 to produce my ioc and compilation.The 14bit ADC1 is performing as expected when set to convert internal signals - Vdd and Vbatt.The signal to be converted is a low frequency DC signal - we're measuring current via a precision sense resistor and instrumentation amplifier.Calibration performed during programme "init" :-  ADC_ChannelConfTypeDef sConfig = {0}; hadc1.Instance = ADC1; sConfig.Channel = ADC_CHANNEL_3; // Ch3 intended- ****************************************** sConfig.Rank = ADC_REGULAR_RANK_1; sConfig.SamplingTime = ADC_SAMPLETIME_12CYCLES; sConfig.SingleDiff = ADC_SINGLE_ENDED; sConfig.OffsetNumber = ADC_OFFSET_NONE; sConfig.Offset = 0; if (HAL_ADC_ConfigChannel(&hadc1, &sConfig) != HAL_OK) { Error_Handler(); } if ( HAL_ADCEx_Calibr

 Hello,I want to interface NHD-2.7-12864WDW3 OLED display with STM32H755 Nucleo and show some data in display-4 wire SPI-. I had connected all OLED pins to STM32 correctly and than tried to flash this code (that I've attached). But i did not get any output, OLED display did not even glow.I dont know where i am doing wrong, can you help me on this regard? Pin 1 (VSS) → GNDPin 2 (VDD) → +3.3 VPin 3 (NC / BC_VDD) → no connectionPin 4 (D/C) → PA9 (GPIO Output)Pin 5 (VSS) → GNDPin 6 (VSS) → GNDPin 7 (SCLK) → PB13 (SPI2_SCK, AF5)Pin 8 (SDIN) → PB15 (SPI2_MOSI, AF5)Pin 9 (NC) → no connectionPin 10 (VSS) → GNDPin 11 (VSS) → GNDPin 12 (VSS) → GNDPin 13 (VSS) → GNDPin 14 (VSS) → GNDPin 15 (NC / VCC sense) → no connectionPin 16 (/RES) → PA10 (GPIO Output, active LOW reset)Pin 17 (/CS) → PB2 (GPIO Output, active LOW chip‑select)Pin 18 (/SHDN) → +3.3 VPin 19 (BS1) → GND (BS[1:0]=00 → 4‑wire SPI)Pin 20 (BS1) → GND (BS[1:0]=00 → 4‑wire SPI)  Note: The pins seen as short circuit i

Hello Because we need to use linux 6.1.x, so I try to compile the optee 3.19.0 which is from the source package of ST web.But there is a compile issue:$ make -f $PWD/../Makefile.sdk CFG_EMBED_DTB_SOURCE_FILE=stm32mp257f-ev1 allmake[1]: Entering directory '/home/llf/linux-kernel/stm32mp2-openstlinux-6.1-yocto-mickledore-mpu-v24.06.26/sources/aarch64-ostl-linux/optee-os-stm32mp-3.19.0-stm32mp-r2-r0/optee-os-stm32mp-3.19.0-stm32mp-r2'GEN /home/llf/linux-kernel/stm32mp2-openstlinux-6.1-yocto-mickledore-mpu-v24.06.26/sources/aarch64-ostl-linux/optee-os-stm32mp-3.19.0-stm32mp-r2-r0/optee-os-stm32mp-3.19.0-stm32mp-r2/../build/stm32mp257f-ev1/core/include/generated/arm32_sysreg.hGEN /home/llf/linux-kernel/stm32mp2-openstlinux-6.1-yocto-mickledore-mpu-v24.06.26/sources/aarch64-ostl-linux/optee-os-stm32mp-3.19.0-stm32mp-r2-r0/optee-os-stm32mp-3.19.0-stm32mp-r2/../build/stm32mp257f-ev1/core/include/generated/arm32_sysreg.SCHK /home/llf/linux-kernel/stm32mp2-openstlinux-6.1-yocto-mickledore-m

Hello, I spend a lot of time to tried running HW SPI on H523CET6.  On the other mcu like F411 it work without any problems. In this case SPI work only when I do it in software mode://===================================================================================== #define DO_LO HAL_GPIO_WritePin(LCD_MOSI_GPIO_Port, LCD_MOSI_Pin, GPIO_PIN_RESET); #define DO_HI HAL_GPIO_WritePin(LCD_MOSI_GPIO_Port, LCD_MOSI_Pin, GPIO_PIN_SET); #define CLK_LO HAL_GPIO_WritePin(LCD_CLK_GPIO_Port, LCD_CLK_Pin, GPIO_PIN_RESET); #define CLK_HI HAL_GPIO_WritePin(LCD_CLK_GPIO_Port, LCD_CLK_Pin, GPIO_PIN_SET); //===================================================================================== static void Transmit_Byte(uint8_t transfer){ //========================================================== #define HW_SPI //============== #ifdef HW_SPI extern SPI_HandleTypeDef hspi1; HAL_SPI_Transmit(&hspi1, &transfer, 1, 100); //========================================================== #else u

Hi, I am testing the System Memory UART protocol in STM32G070CB.I tried the Get command, the Go command, and the Read Memory command standalone, all success.However, when I try to execute the Read Memory command, which is successful, and then execute the Read Memory command, the ST does not send any response.Full pattern:Successful Enter Boot Mode:Read Memory CMD with Address = 0x0801FFF0 and read data size is 0x10Try to execute the Read Memory CMD again but without ACK/NACK As I know, the protocol is able to execute other CMD when the pervious CMD completed or Failed. How could I execute CMD continuously? Note: UART Protocol version of the MCU is V3.1    

I configured SYSCLK to 480 MHz and set the I2C1 peripheral clock frequency to 120 MHz. For I2C1's timing settings, I selected Fast Mode Plus (1 MHz) and applied the timing register value 0x0050174F, the setting about maximum output speed of SDA and SCL are Very High.However, when observing the I2C1_SCL line with a logic analyzer, the actual output clock frequency is only 890 kHz.

Dear friends, I am playing around with NUCLEO-H745ZI-Q.I generated example motor control project from en.X-CUBE-MCSDK-FUL_6.4.0 for CubeIDE v.1.18.1. This example project utilizes CM4 core. Clock frequency for CM7 core can be twice higher than the clock frequency for CM4. Therefore, I believed that CM7 core can run code twice faster than the CM4. I use GPIO Output to measure code execution time on the oscilloscope.To estimate completion time, I use a code in a while() like this: HAL_GPIO_TogglePin(GPIOK, GPIO_PIN_0);Ialphabeta = MCM_Clarke(Iab);HAL_GPIO_TogglePin(GPIOK, GPIO_PIN_0);HAL_Delay(100); I/O pin is in “Very High Speed Mode”. So, running it on CM4 @240 MHz, I get:-         630 ns without optimization;-         230 ns with FAST optimization; Surprisingly, after migrating code on CM7@480 MHz, I get worse results:-   &nbsp

Hi all,I'm designing STM32N655L0 based board and I've one question.I'm using XSPI1 and XSPI 2 peripherals.XSPI2->Octa SPI mode, NOR FlashXSPI1-> SDRAM, Hexa SPISo my question is can I use unused CS, NCLK pins as an IO?I just wanted to be sure. BR

I have stm32u5g9j-dk1 demo board. The LCD on it is J025F1CN0201W. But I am not able to find its data sheet or technical spec. May I have copy of it? Thank you. Kelly

I'm trying to port the VL53L0X library for use with the RP Pico W for academic reasons, but I can't map the calls between the VL53L0X SDK and the RP Pico W SDK. For example, the function int32_t VL53L0X_read_multi(uint8_t address, uint8_t index, uint8_t *pdata, int32_t count) would theoretically need to be adjusted to call the function int i2c_read_blocking(i2c_inst_t *i2c, uint8_t addr, uint8_t *dst, size_t len, bool nostop) Attempt to read specified number of bytes from address, blocking. Am I right? Or should it be another way?Thanks

Hello,the following code is generated by CubeMX 6.11.1 in module stm32l4xx_it.c:/** * @brief This function handles TIM1 trigger and commutation interrupts and TIM17 global interrupt. */ void TIM1_TRG_COM_TIM17_IRQHandler(void) { /* USER CODE BEGIN TIM1_TRG_COM_TIM17_IRQn 0 */ /* USER CODE END TIM1_TRG_COM_TIM17_IRQn 0 */ HAL_TIM_IRQHandler(&htim1); HAL_TIM_IRQHandler(&htim17); /* USER CODE BEGIN TIM1_TRG_COM_TIM17_IRQn 1 */ /* USER CODE END TIM1_TRG_COM_TIM17_IRQn 1 */ } /** * @brief This function handles TIM1 capture compare interrupt. */ void TIM1_CC_IRQHandler(void) { /* USER CODE BEGIN TIM1_CC_IRQn 0 */ /* USER CODE END TIM1_CC_IRQn 0 */ HAL_TIM_IRQHandler(&htim1); /* USER CODE BEGIN TIM1_CC_IRQn 1 */ /* USER CODE END TIM1_CC_IRQn 1 */ }Interrupts for TIM1 (capture) and TIM17 (global) are both activated, but with different priorities.The problem is that TIM1_TRG_COM_TIM17_IRQHandler() handles also the capture interrupts from TIM1 with same function&n

Hello,I was looking into this wiki tutorial on setting up a UDP echo server by @mƎALLEm , and the clock configuration caught my eye and wanted to confirm a few things.On the nucleo board , the 8 MHz crystal (X3) is not soldered and the 8 MHz clock signal comes directly from the ST-Link MCU (U2) via SB149. I have checked this on a oscilloscope. But in the tutorial , in Section 2.1 Clock configuration Section , the screenshot shows the input frequency set to 16 MHz. As far i am aware this should be 8 , not 16 MHz. Can someone please confirm this? 

arm-none-eabi-gcc -mcpu=cortex-m4 -g3 -DDEBUG -c -x assembler-with-cpp -MMD -MP -MF"Core/Startup/startup_stm32f429igtx.d" -MT"Core/Startup/startup_stm32f429igtx.o" --specs=nano.specs -mfpu=fpv4-sp-d16 -mfloat-abi=hard -mthumb -o "Core/Startup/startup_stm32f429igtx.o" "../Core/Startup/startup_stm32f429igtx.s"arm-none-eabi-gcc "../Core/Src/eth.c" -mcpu=cortex-m4 -std=gnu11 -g3 -DDEBUG -DUSE_HAL_DRIVER -DSTM32F429xx -c -I../Core/Inc -I../Drivers/STM32F4xx_HAL_Driver/Inc -I../Drivers/STM32F4xx_HAL_Driver/Inc/Legacy -I../Drivers/CMSIS/Device/ST/STM32F4xx/Include -I../Drivers/CMSIS/Include -I../LWIP/App -I../LWIP/Target -I../Middlewares/Third_Party/LwIP/src/include -I../Middlewares/Third_Party/LwIP/system -I../Drivers/BSP/Components/lan8742 -I../Middlewares/Third_Party/LwIP/src/include/netif/ppp -I../Middlewares/Third_Party/LwIP/src/include/lwip -I../Middlewares/Third_Party/LwIP/src/include/lwip/apps -I../Middlewares/Third_Party/LwIP/src/include/lwip/priv -I../Middlewares/Third_Party/LwIP/sr

I am working with STM32 U575/U5A5 series of STM32 controllers in low power mode. I have programmed the controller to enter into Stop 3 mode and wake from stop3 mode based on wakeup Pin(High on PF2). With this implementation issue what we observed is once immediately flashing hex file into controller using STlink programmer, Controller is entering in stop3 mode but it is not waking up from stop3 mode even after low to high transistion on wakeUp pin(PF2). If I remove the power and connect it back, it is working as expected enterning into stop mode 3 and waking up from stop mode 3 on low to high transistion on wakeUp pin(PF2) all the time. The question here is why for the first time after flashing hex file into controller, entering into stop3 mode but not waking up from stop3 mode and requires power reset?low power mode is configured as follows:void LowPowerInit(){        LL_RCC_SetClkAfterWakeFromStop(RCC_STOP_WAKEUPCLOCK_SELECTED);    __HAL_RCC_PW

Dear all,I'm encountering a strange issue with the STM32N657.I have a very simple test application that successfully turns on an LED — everything works as expected.Now, I need to switch the stack and enable the PSP. To do so, I’m using the following code:uint8_t PSPstack[800] __attribute__((aligned(8))); __set_PSP((uint32_t)(PSPstack + sizeof(PSPstack))); __set_CONTROL(__get_CONTROL() | 0x2); // Set SPSEL = 1 to use PSP __asm volatile ("isb"); However, as soon as I execute this code — specifically the line setting CONTROL to 0x2 — the system enters an exception (likely a fault handler), and execution stops.Do you have any idea how to debug this or what could be going wrong?Thanks in advance for your help.Kind regards,Edo

Hello,I was able to make the SDL2 library works with KMSDRM with kernel 5.15 Kirkston but with kernel 6.6 Scarthgap it doesn't work. I also configured the kmsdrm to work in the .bbappend file since I am using Yocto. I can see from the log.configure that the kmsdrm is on but the application which was working with 5.15 is still not able to run with 6.6. However, KMSCube is working means KMSDRM is working from the kernel point of view. The messages that I got when debug are below:INFO: video driver in use is: (null)INFO: video driver 0: waylandINFO: video driver 1: KMSDRMINFO: video driver 2: (null)INFO: video driver 3: (null)INFO: Failed to initialize SDL: No available video device Even if I specify the driver to be kmdrm I see the followingINFO: video driver in use is: (null)INFO: video driver 0: waylandINFO: video driver 1: KMSDRMINFO: video driver 2: (null)INFO: video driver 3: (null)INFO: Failed to initialize SDL: kmsdrm not available I don't know why it is still unavailabl

I designed a custom board using the STM32H725ZGT3. The references I followed include the datasheet, application note AN5419, and the STM32H745ZIT6 Nucleo board design, among others. After powering up the board, I was able to connect to it via ST-Link using STM32CubeProgrammer, and successfully uploaded a simple blink code using STM32CubeIDE. The code worked, and the LED started blinking. However, after a power cycle (i.e., turning the main power off and on again), the board stopped running the code, and the LED no longer blinked. I tried reconnecting with STM32CubeProgrammer, but I received a "Target not found" error. After that, I connected the BOOT pin to 3.3V. This allowed me to connect to the board again using STM32CubeProgrammer, but I couldn’t upload code using STM32CubeIDE. I then changed a setting in the CubeIDE: System Core → RCC → Parameter Settings → Power Parameters → PWR_LDO_SUPPLY After this change, I was able to successfully upload the code. Howe

Hello!!I just started with the ASM330LHHX DIL24 module for the X-NUCLEO Boards, the module is listed as compatible with the IKS4A1 (sensors below):I have read some documents related to the procedure to make it work but it's an "old" document (see below), I look for general advice:Once the module is inserted do I need to configure any jumpers in the XNUCLEO board?If there is no need to modify jumper configuration on the board, does that mean that all configuration is done via software, correct?Once I gain access to the ASM330, the rest of the sensors onboard the IKS4A1 will be available? all of them + the ASM330?> If you have a tip or advice related to the configuration to enable the ASM3330 feel free to share it.Document: an5353-how-to-use-a-sensor-on-a-dil-24-socket-in-xcubemems1-package-applications-stmicroelectronicsThanks!J.D 

Hi,I have been working on STM32F4 discovery board, I have developed Bootloader Code. There is 2 option to jump to application that includes blinking led app. First button interrupt runs perfectly, i mean hal_delay() runing with no issue.Second option is, if UART interrupt gets the jump command and address from my computer. In this situation it jumps to application and leds are turn on but not blinking because of hal_delay() func (i guess). In 2 option before the jump func if i use hal_delay() , it crahs also.

I want to interface  NHD-2.7-12864WDW3 OLED display having SSD1322 controller with STM32F407G-DISC1.I am doing 3 wire SPI Communication, So i have connected all 20 PINS as follows:Pin1 ---> GNDPin2 ---> 3VPin3 ---> NC (No connection)Pin4 ---> PD9 (DC; GPIO_Output, assigned by cubeide) Pin5 ---> GNDPin6 ---> GNDPin7 ---> PA5 (SCLK; SPI1_SCK, assigned by coubide)Pin8 ---> PA7 (SDIN; SPI1_MOSI, assigned by coubide)Pin9 ---> NC (No connection)Pin10 ---> GNDPin11 ---> GNDPin12 ---> GNDPin13 ---> GNDPin14 ---> GNDPin15 ---> NC (No connection)Pin16 ---> PB12 (RES; GPIO_Output, assigned by cubeide) Pin17 ---> PB13 (CS; GPIO_Output, assigned by cubeide) Pin18 ---> PB14 (SHDN; GPIO_Output, assigned by cubeide) Pin19 ---> PB15 (BS1; GPIO_Output, assigned by cubeide) Pin20 ---> PD8 (BS0; GPIO_Output, assigned by cubeide)  After flashing the code into the STM32F407G-DISC1 board, OLED displa

Hello Everybody,MCSDK:6.3.2CubeMX: 6.1.4Workbench : 6.3.2 I want to test the motor first with the open loop APIs. I follow the instructions of the user mannual and write the code as follows:My question is: I captured the U, V, and W three-phase waveforms using an oscilloscope and found that the duty cycle settings are correct. However, the waveforms remain stuck in only one section (they never change) and fail to drive the motor through all six sections. Could you help analyze what might be causing this issue? Thanks!