Solved

Does this demo is open source? Where can I find the demo source code?

Hi everyone, I am trying to deploy a pose detection model on stm32n6570-dk board but I am getting the following error. (st_zoo) kartikkhandewal@ATL-HPZG14-99:~/stm32packages/stm32ai-modelzoo-services/pose_estimation/src$ python3 stm32ai_main.py --config-path ./config_file_examples --config-name deployment_n6_yolo_mpe_config.yaml WARNING: All log messages before absl::InitializeLog() is called are written to STDERR E0000 00:00:1740729082.336274 136562 cuda_dnn.cc:8310] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered E0000 00:00:1740729082.339482 136562 cuda_blas.cc:1418] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered [WARNING] The usable GPU memory is unlimited. Please consider setting the 'gpu_memory_limit' attribute in the 'general' section of your configuration file. [INFO] : Running `deployment` operation mode [INFO] : The random

Hi everyone,I am currently working with the STM32N6570-DK board and would like to integrate the STEVAL-56G3MAI camera module with it. The camera's overview page mentions that it supports the STM32N6 series. However, I have been unable to locate any STM32N6 header files to facilitate this integration.I did come across the STSW-IMG502 software package, which also lists STM32N6 compatibility, but it only includes drivers for Raspberry Pi and Linux platforms.I would greatly appreciate any guidance or resources (e.g., example projects, driver libraries) that could help me successfully interface this camera with the STM32N6570-DK board.Thank you in advance for your support.

Hi : I want to know which MCU support BC1.2, how can I use CubeMX to filter these MCU? 

Hello!I recently bought a OV5640 Adafruit breakout board from here and I was having some issues with using the I2C bus. I downloaded the libraries from the stm32_ov5640 GitHub page. Whenever I run the HAL_I2C_Mem_Write or HAL_I2C_Mem_Read functions, an error is returned. I read online that configuring the registers is needed before reading the chip, but even writing doesn't work. The following is my write register function:static int32_t OV5640_IO_ReadReg(uint16_t DevAddr, uint16_t Reg, uint8_t *pData, uint16_t Length) { HAL_StatusTypeDef status; uint8_t reg_addr[2]; // OV5640 uses 16-bit register addresses (big-endian) reg_addr[0] = (Reg >> 8) & 0xFF; // High byte reg_addr[1] = Reg & 0xFF; // Low byte // Send register address then read data status = HAL_I2C_Mem_Read(&hi2c1, OV5640_I2C_ADDRESS, Reg, I2C_MEMADD_SIZE_16BIT, pData, Length, HAL_MAX_DELAY); // OV5640_I2C_ADDRESS = 0x3C but I tried with 0x3C << 1 and 0x79 if (status != HAL_OK) {

Hello, I am having an issue implementing a 32 bit CRC 0x04CDB117I am quite confused by the documentation on how to set the a 32 bit CRCI don't understand section 53.5.3 on the most significant bit in in CRCPOLY must be larger than the data size.I don't understand what register CRC33-17 is referring to.Any help or clarification would be appreciated.Thanks

Hi  I use stm32f412 vet6.Flash size is 512kbye.But stm utility program is 1mbyte size. Why??

Hello,Despite the mandatory `rfalWorker()` hell> "It MUST be executed frequently in order to execute the RFAL internal states and perform the requested operations"... the RFAL is very interesting to have a flexible way to communicate with the ST25R family - current and future (my opinion only :')) Especially for the amount of standards it helps to follow. But, please, can you consider to make it usable not only for a single chip? It use a lots of unique global variables (gNfcDev, gNfcip, gNfca, etc...), use same timers, communication bus, etc...All of that make it unusable to control multiple chips, a shame when we now have multi cores ARM :(

Hi all, I'm fairly new to programming an STM32 :) Is there a simple way of getting started with the above wireless development kit? The documentation on the product page isn't very helpful.

We have designed and shipped a water level sensor based on the VL53L1X. It works well in most situations, but we have one issue in a particularly large tank (3m tall, 2m diameter). I believe this is due to reflections in the tank. It is a black tank, but the surface is glossy.I thought reducing the FoV might help with reflections, but the datasheet states this reduces range, but I can't really understand why. If the laser is pulsing light at the same power, and that light falls back on the SPAD, why does only looking at the center diodes affect range?I think I'm misunderstanding how it works so I thought I would ask. I'm not sure there is much I can do in this situation and it may just be unsuitable for this particular tank.Thanks

The DBATTEN setting in the UCPD_CR register claims the following But as far as I know, the dead battery functionality is always present. It would have to be to work unless this is stored in NVM.Maybe this DBATTEN is some other Rd value? Maybe the ANAMODE is a proper Rd but this one is a sortof Rd light that is only sufficient to wake the MCU? I can't tell because no information is provided.If the MCU is powered there is not really a "dead" battery condition. If the MCU is not powered this setting can't take effect.Any ideas?

Hello ST Community ,I am currently using the EEPROM part M24128-BFDW6TP (TSSOP-8 package) in a design. However, I’m facing difficulty in locating the Pin 1 marking on the IC. There is no visible notch or dot on the top side of the package that would typically indicate Pin 1, as referenced in the datasheet.The IC top surface only contains part marking text, but no discernible Pin 1 indicator (notch or laser dot).We’ve verified this across multiple units.This is making it difficult to confidently orient the IC for placement.I’ve attached a clear screenshot for your reference.Could you please confirm:The official Pin 1 location with respect to the printed text on the IC?Whether this is a known marking issue or within tolerance of ST's marking process?Any additional guidance or recommendations for identification?Thanks and Best regards,Ananda

I am currently using a VL53L1X Sensor to read a distance in the range of 40cm to 130cm. I initialized the Sensor to work in the short distance mode, so the range should not be a problem. I used the VL53L1X_calibration library to get the values for offset and xtalk. In the Datasheet i read that with the function VL53L1X_GetDistance() the distance should be returned in mm. The value i get returned from that function does change when i change the physically measured distance, but it is not the expected value. For example when i want to measure a distance of 1m i get a value of about 55500. Also the measurement change on the same height in a range of 1000. For the offset and xtalk calibration i set the physical distance to 1m and gave that as a parameter in the function as 1000(mm). I copied the values i got from the function to the function setoffset and setxtalk. To calibrate i used the following diagramm:And my init in my software looks like

What is the maximum current that the STM32 GPIO can withstand when set to open-drain mode and the NMOS is on without getting damaged?

Hello everyone,I've noticed that several users have experienced issues related to the LDO power supply setup for the STM32H757A. I’m currently working on a design using this MCU in LDO mode, and I’d like to confirm whether my power supply implementation is correct. Just to turn On the LED. Could someone please review my configuration and let me know if there’s anything I should adjust or improve?Thanks in advance for your help!

Hi, Is there an option to program the STM32L412RB with DFU / Serial interface? I was programming the STM32F407 with DFU and Serial before and now I want to use the STM32L412RB and program it the same way. I can't find any information on the BOOT1 pin in this MCU to enter the system memory boot modeThank you in advance for your help, Ron. 

Hello,I’ve configured SPI in CubeMX with DataSize = 12 bits. However, when I use the HAL function HAL_SPI_Transmit, the pData argument seems to require a uint16_t (or at least 16-bit aligned) buffer.I'm a bit confused about how this works in practice. Since I'm sending a 16-bit word, but only configured 12-bit frames, does the SPI peripheral transmit just the lower 12 bits of each word? Or do I need to pack the 12-bit values differently?I'm still fairly new to STM32 development, so I appreciate any clarification you can offer!Best regards,Kewin

Hi guys, i am an embedded firmware engineer, with a lot of projects on stm32 micro controllers, including the communication protocols, battery management systems , ultra wide band, and EV charging, i wanted to know if i can post or share my projects or libraries on stm32 knowledge base ?or it is restricted to some people ?if yes then how do i get access to posting knowledge base articles,?Thankyou.

Following this post describing how to disable speculative accesses on external memories range (0x6000 0000 to 0xDFFF FFFF) on Cortex®-M7 processors, I'm wondering if such mechanism should be done to:- memory regions marked as reserved:Source - DTCM / ITCM memory regions not mapped:ITCM_AXI_SHARED[1:0] and DTCM_AXI_SHARED[1:0] can be used to change the memory allocation.   

MCU: STM8L151G3U6ISSUE: TIM4 interrupt doesnt seem working Connections:                 1. LED on pin PB0                 2. Push button/ switch on pin PC5Scenario:1. User press the push button2. Toggles the LEDObservation:Without using the TIM4 interrupt, the code works perfectly fine, when the TIM4 is used, the excutions reaches the first wait_50ms(); (red colour) and never go beyond this line, I would appreciate if any one would address the issue. BTW: I have used IRQHandler, 23  also but same result./===== Header files ====== #include "stm8l15x.h" // Software timing counters volatile uint16_t tick_1ms = 0; volatile uint8_t flag_50ms = 0; volatile uint8_t flag_100ms = 0; volatile uint8_t flag_1min = 0; volatile uint16_t soft_50ms = 0; volatile uint16_t soft_100ms = 0; volatile uint16_t soft_1min = 0; //==== System Clock Configuration ===== void CLK_Config(void) { CLK_DeIn

I want to let the user LEDs blinken, however it is not working. When I run the code the LD4(COM) is blinking red and green. after the run the LD4(COM) is red the whole time and the user LEDs do not blink. Should the LD4(COM) be lighting green?

Hi everyone,I'm working with the STM32F303CCT6 chip, and I've configured the system clock such that HCLK is running at 72 MHz.I'm trying to configure SPI1 in full-duplex master mode using CubeMX / STM32CubeIDE. However, when I attempt to set the prescaler to 2, it gives me the following warning:"With this Prescaler value and APB2 Clock Frequency (72.0 MHz), Baud Rate is more than 18.0 MBits/s.Please set Prescaler more than 4."This is confusing because I thought SPI1 could go up to 32 Mbit/s.Has anyone encountered this?Is this a limitation from CubeMX or HAL?Is it safe to ignore this warning and proceed manually in code?Or is there a hardware limitation I'm overlooking?Any insights or workarounds would be greatly appreciated!Thanks in advance!

Hi Community,I am about to work on STM32H7471-DISCO Development BoardCan you provide Schematic of this Board.I found all the technical documents from https://www.st.com/en/evaluation-tools/stm32h747i-disco.html# but I do not found board schematic.  

Hi I'm trying to reset the stm h563 to factory settings because I do some test before and I would like to use the stm for other things but I can't reset the changes I made with CubeProgrammer. I have those errors....   

Hi, I am using Nucleo-144 boards in my project where I have changed the clock source for STLINK IC to external crystal using STLINK firmware upgrade tool. Before it was HSI/2 =8MHz. Now I am trying to revert the configuration back to 8MHz but I am not able to detect the Nucleo board now with 8 MHz. Is this known issue? I tried configuring it back to 5MHz using tool below and it works fine , detects all the time in MATLAB. But not with 8MHz (HSI/2).  How to revert back the configuration and make the board detectable?