Product forums

I am trying to use VL53L4CD to detect whether there is a car on top of the sensor or not...I am placing my sensor on the ground and trying to detect if a car is parked on top of the sensor. But it is not able to detect the cars bottom surface. However if I place any other object it is able to detect that....Is this the right sensor for this application?

Hi Team,I have design for the custom inverter for the STM32G4A1VET6 controller and motor driver is Infineon.custom board is designed and the while generating the code getting error as "1.4.0psdc: PSDC Version is not supported"while I tried to download this package manually couldn't download showing error "FP-SNS-STBOX1" support package.

Hello,when doing code generation by CubeMX, it seems, that there's no Pin-remapping done in certain cases, at STM32C092FCP6.In my case, I chose SPI2 in master full-duplex mode. SPI2_CLK is on PB8 at Pin1. A remapping from PB7 to PB8 has to be done by setting PINMUX4 in SYSCFG->CFGR3 register. I thought this would be done by CubeMX code generation, but i didn't. The same is with SPI1 SCK, at Pin 20 with PB6/PB3. Is this the desired behaviour?

I'm working with an STM32WB55 Nucleo board and encountering a strange issue. My project uses an SPI display and an I2C accelerometer, along with BLE.When the board is powered via the ST-Link/USB, everything works perfectly: the BLE functions, the onboard LEDs toggle, and both the SPI display and I2C accelerometer work as expected.However, when I try to power the board from a Nordic Power Profiler Kit (PPK) and remove the jumpers as instructed to isolate the ST-Link (see attached image), the SPI display and I2C accelerometer stop working entirely. The BLE and LED toggling functions continue to work correctly, which is puzzling.Why would the peripherals fail in this specific power configuration, while the rest of the code continues to run? Any insights into what could be causing this are greatly appreciated.

Hi everyone,I’m working with the STM32C011F6U6 in my design and would like to flash it using the system bootloader (USART1 on PA9/PA10 as described in the datasheet).Before finalizing my design, I ordered the MB1684B board with the STM32C011F6U6 to test this.However, I’m struggling to get the MCU into bootloader mode. It seems like the device never enters the system bootloader at all.Here’s what I did:I previously flashed a simple LED blink program, which works fine.I connected a push button to the BOOT0 pin (pressing the button ties BOOT0 to VDD).While holding BOOT0 high, I pressed the NRST button to reset the MCU.After reset, the LED is still blinking, which suggests the code in flash is running, not the system bootloader.On my NUCLEO-L412RB-P, doing the same BOOT0 + reset sequence works correctly and I can flash via UART. I assumed the STM32C0 family would behave the same, since the

Hi, There is a blatant bug in the STM32CubeIDE that has costed me a board iteration on a professional product. It says that pin PA3 is positive comparator input. When it isn't. Look here This is what the datasheet says.

Hi Team,   We are running into a problem on TouchGFX (v4.25) on configuring our 480x272 display on the above discovery board I mentioned. We want to configure a text box and display this  color I attached below. We found that the RGB we have is RGB565 and we may need RGB888. But I do not see any difference even after the change in this configuration. We want to understand if it is really possible to achieve this color or is it a limitation of the board selected?This information will help us to choose this controller for our further development or

I've created a project for my Nucleo MB1404 - STM32HM563ZI board which uses USART2 and USART3 to send and receive data to a computer. I've just configured both UARTS in the same way with the same parameters with STM32CubeMX. The USART3 works without problems ( can send and receive data),that is the UART connected to the onboard debugging microporcessor which implements a USB virtual COM and  the debugging functionallities. The problem is with USART2. I connected a "FTDI like" device that connects and converts the USART2 lines to a virual COM through USB in the computer. I can send bytes from the nucleo board to the computer and read them in the terminal s

Hello,On a custom-designed PCB, I am using an STM32H745IIT6 (LQFP176) MCU. I am actively using analog channels, various I/O pins, Ethernet, QSPI, and other peripherals. The code I am using was previously running on an F7 series MCU. It has been fully ported to the H7 version and tested. However, during testing, I noticed an issue with sampling on the PA0 pin, which is configured as ADC1 INP16 in single-ended mode. A total of 19 analog channels are active, and 18 of them show no problems, but on this particular channel I can clearly observe a shift in the raw ADC values.- ADC1-2-3 are running in independent mode, 16-bit, triggered by Timer1.- Data is read via DMA.When I monitor with Serial Wire Viewer (SWV), I observe sampling behavior as shown in the image. The channel where I am experiencing the issue is the red signal shown with the name adc_bc. The other three signals were added for comparison. A single source was used to provide the signa

I am using the STM32H753VI chip, it's on a proprietary PCB but the layout is very similar to the nearest NUCLEO board so I am not ready to consider that the issue.I am working on a very low power application, using CubeIDE but minimal HAL, preferring bare metal. When I execute __WFI() to put the device to deep-sleep, D1 and D2 enter standby (D2 is always standby, actually), and D3 is supposed to stop and allow LPUART1 and RTC to run in autonomous mode (LSE clock). This works exactly as expected, drawing about 250 uA from my power supply (via LDO). The device is set to wake from deep-sleep on LPUART1 RX event. When it wakes, my program can discriminate between the original Power-on Reset and the Wake from Standby. The PWR_CPUCR register is set to 0x1A3, which corresponds to SBF_D2, SBF_D1, STOPF, PDDS_D2, and PDDS_D1 all set, exactly as anticipated.The issue occurs the next time __WFI() is called. As best as I can tell the settings have not changed, but D

Hello everyone,I am performing some tests over the NUCLEO-WBA65RI board, related to low power mode and BLE functionality.I managed to test the BLE_p2pserver example correctly and checked the current consume is about 500 μA on this case until it goes on low power mode and changes to 20 μA.The low power mode stays like that and we are not publishing unless B1 button is pushed.I was wondering if there is any document that explains how this is performed and to ask if it was possible to have the BLE stack publishing in low power mode(stop2mode) like it could be done in in the WB55 which is a dual core.Thanks in advance!

Hello,  I am currently using the EVB-LIV4F and using page 8 of the UM3212 document to measure the current draw of the module. I am then placing it into SW-standby mode by sending the $PSTMFORCESTANDBY,<seconds>,1 command that I found on this post: https://community.st.com/t5/gnss-positioning/teseo-liv4f-wakeup-interrupt-and-nreset-confusion/td-p/615973 Under these conditions, I am measuring 0.0mV on the VCC (pin #9) and PM_VCC (pin #10) pins and 9.1mV on the VBAT (pin #7) and PM_VBAT (pin #8) pins. From the conversion given, the GNSS module is drawing 91uA on VBAT and not the advertised 10uA. Does the evaluation board need to be in a specific configuration to achieve the 10uA? Any jumpers that need to be added/removed?Where is the documentation

Hello STM32 Community,I'm working on a project using the STM32WB55RG microcontroller (specifically the P-NUCLEO-WB55 evaluation board) to implement a sleepy end device in a Zigbee network. The goal is to transmit data over Zigbee periodically and then enter shutdown mode, with the RTC serving as the wake-up source to minimize power consumption during sleep periods.Setup and Configuration:Hardware: P-NUCLEO-WB55 EVM based on STM32WB55RG.Functionality: The device wakes up from shutdown mode via RTC, enters active mode to perform Zigbee transmission, and then returns to shutdown.Clock Settings:Cortex-M4 core clock set to 32 MHz (default).Cortex-M0+ core clock also set to 32 MHz (matching the M4 frequency).Note on M0+ Clock: We attempted to reduce the M0+ clock frequency for potential power savings, but the IOC (STM

Split from TOUCHGFX and CPU.My screen resolution is 480 * 800. When I use a dynamic graph with a capacity setting of 300 and add 30 points each time, the number of executions of handleTickEvent per second drops from 30 to 2. What solutions are there? 

Hello everyoneI am trying to flash the STM32MP257F-EV1 board using Programmer and now I am getting this error. Before that I followed the instructions of enable secure and ssp.And can I renew the board Thank 

Hello, meanwhile i tried for ethernet udp several examples. But either these could not be importedin STMCubeIDE 1.19.0 or were based on RTOS. Did any know or have an example for it? Thank you! Best regards, HiST

Dear ST,I'm trying to get USB CDC device working on custom STM32H7R3L8HxH based board. Host (Windows) detects it but unfortunately the USB device fails to enumerate with error:Windows has stopped this device because it has reported problems. (Code 43)A request for the USB device descriptor failed.USB FS based Boot ROM works in DFU mode so I know hardware should be okay.I found a bug in CubeMX code generator. USBPHY clock source is configured to be HSE (which is 24 MHz):However code generator creates usbd_conf.c function HAL_PCD_MspIn

Hello,Currently I am facing a issue where my CUBE monitor is not able to parse the ELF files. It gets stuck at 10% completion while loading it. I have attached my workflow below:The Error is as follows: 

Hello, I am using the ST-25R200 ready-to-use NFC evaluation board for my application. I have already used the ST25R200 EVAL GUI software which functions without any problem.  Since I want to develop my own software and integrate it for the application which requires to read/write to the NFC tags, I went through the forum and found out some much helpful ST25NFC_Embedded_Lib_ST25R200_1.8.0. After installing, I went through the example ndef_read.c and ndef_write.c codes (which are very thorough in and of themselves). I am trying to use these codes along with the required drivers and header files using VS code. I have properly included the paths for all the required headers. However, while compiling I am getting the error: reent.h source file (dependency of rfal_nfc.h) could not be opened. I am also unable to find the said header file in the installed embedded library folder. Request for a

Hi Engineer, I purchased the part of ESDA5WY, and the type number showing on the label is 'AESDA5WY '. Could you suggest the meaning of the letter "A"? Thanks, Gloria

Hello,I am trying to make an external loader for a STM32H5 to program a QSPI flash MX25L12835F with STM32 Cube Programmer.In my project I add files Dev_inf.c .h ans Loader_Src.c .h from :https://github.com/STMicroelectronics/stm32-externaloader/tree/main/STM32H5x_boards/MX25LM51245G_STM32H573I-DKAnd modify them to adapt to my board :- Dev_inf.c  : update StorageInfo struct- Loader_src.c : reimplement Init() , MassErase() , Write(), SectorErase() with my flash driver.I test these functions in debug with the original linker STM32H562RGTX_FLASH.ld and these functions works ok.After I change the linker file with linker.ld of the branch contrib stm32-external-loader\Loader_Files\other devices and build and generate the file

I have a project which uses both OPAMPs. For both OA I use dedicated VINM pin.OPAMP1 works correctly.OPAMP2 behaves like the dedicated pin (M2 ball) is not connected to the input multiplexer.I 've tried - mode FOLLOWER: OK - mode STANDALONE, reconnected the signal on the board and used PA7 for VINM: OK - mode STANDALONE, using the dedicated pin: the output is saturated at VDDA.Checked the PCB connection, OK. Checked on 3 boards, identical results.Is it possible it is really a bug in the silicon? What else should I check?(I would like to use OPAMP tag, but it is not available :(  ) Initialization code:(GPIO to analog)LL_APB3_GRP1_EnableClock(LL_APB3_GRP1_PERIPH_OPAMP);LL_OPAMP_InitTypeDef OPAMP_Init;OPAMP_Init.PowerMode = LL_OPAMP_POWERMODE_NORMALPOWER_NORMALSPEED;OPAMP_Init.FunctionalMode = LL_OPAMP_MODE_STANDALONE;OPAMP_Init.InputNonInv

Hello,in my app I am using a listLayout that is inside a scrollable container. In that listLayout I dynamically add and remove elements based on user touch. Each element has multiple wildcards in textAreas.Functionality is ok, but when one of the elements(MOTOR) is open, left to right flicker starts happening. When I close the element the flicker completely stops. Video of flicker: https://www.youtube.com/shorts/Qo5VO2ftH8UUsing: TouchGFX 4.25.0 designerSTM32h757 board (Riverdi 70STM32H7 config) Any ideas would be appreciated. 

Hi, I have the following code inside a function that writes data into flash memory. I noticed that on the first iteration of the for loop, when HAL_FLASH_Program is called, it fails to write at the flash starting address 0x0801F080. However, from the second iteration onward, it successfully writes data into flash. Because of this, the initial data is missing. While debugging, I found that the failure occurs due to this line: error = (FLASH->SR & FLASH_FLAG_SR_ERROR); The error value I get is 128 (decimal). is there anything I am doing wrong? 1.JYI, I have erased the memory before write to confirm this I am observing FF bytes  2.To confirm again I have changed the address from 0x0801F080 to 0x0801F088 still same scenario occours 

Hi all,I'm trying to create a custom bootloader with openbl on rak3172 sip buil with stm32wl, so Ive used this repos here. I've just ipdate the main like this#define APP_ADDRESS 0x08008000U HAL_PWR_EnableBkUpAccess(); __HAL_RCC_RTC_ENABLE(); init_led(); if(get_bootloader_flag() == BOOTLOADER_MAGIC){ set_led_bootloader(); OpenBootloader_Init(); while (1) { OpenBootloader_ProtocolDetection(); } }else{ set_led(); jump_to_app(APP_ADDRESS); } void jump_to_app(uint32_t address) { uint32_t i=0; void (*SysMemBootJump)(void); __disable_irq(); /* Disable Systick timer */ SysTick->CTRL = 0; /* Set the clock to the default state */ HAL_RCC_DeInit(); /* Clear Interrupt Enable Register & Interrupt Pending Register */ for (i=0;i<5;i++) { NVIC-&