Product forums

Hello everyone,I am trying to establish IO-Link communication between the P-NUCLEO-IOM01M1 (STEVAL-IOM001V1 + NUCLEO-F446RE) and an external IO-Link sensor, the Wenglor P3PC012 (COM3, 230.4 kbaud), using the STSW-IOM001 firmware.Hardware setup:STEVAL-IOM001V1 powered with 24V on CN1Sensor connected on CN3: L+ on pin 1, GND on pin 3, CQ on pin 4NUCLEO-F446RE connected via USB to PCWhat works so far:I2C communication with L6360 confirmed working (LED1/LED2 registers write correctly, LEDs blink as expected)L+ enable working correctlyConfiguration register writable (CQ Push-Pull mode)What I am trying to do:Read process data (distance measurement) from the sensorAny advice or working example code would be greatly appreciated. Thank you.

Hi,When I worked on the Discovery kit with STM32F769NI MCU it supported in the STM32CubeIDE/MX the  LWIP package (from 2025) with FreeRTOS/V1. Now when I pass my project to NUCLEO-H563ZI I see in the TM32CubeIDE/MX that ST will not support the LWIP with FreeRTOS anymore. FreeRTOS is only v2 in this board.Is someone integrete the LWIP package on NUCLEO-H563ZI with FreeRTOS/v2? The code main files that should be changed from STM32F769NI to NUCLEO-H563ZI  are LWIP/App/lwip.c, LWIP/Target/ethernetif.c/h, LWIP/Target/lwipopts.h, main.c.Is there any project in git that have done this miggration for LWIP package (code from 2025) and using FreeRTOS/v2 in it's LWIP package? Or share with me those 4 LWIP files for NUCLEO-H563ZI board. Thanks.

Hi everyone,I just started developing software for a new project containing on of the STM32L4P5 series microcontrollers. Therefore I bought the NUCELO-L4P5ZG starter-kit to get used to the IDE, HAL and so on. I use the STM32CubeMX IDE (Version 6.16.1) to configure the board and generate the basic initialization sources. Further code writing is done in STM32CubeIDE (Version: 2.1.1).For the beginning I configured three GPIO pins for the LEDs on the board and the LPUART for simple data transfer to terminal on host computer. For the transmission I want to use DMA . After generating the code with CubeMX and implementing some simple blink logic for the LEDs, I added the line HAL_UART_Transmit_DMA(&hlpuart1, buffer, 14); to the main loop. I debugged the code and saw that the code ran into the infinite loop in the DefaultHandler in the startup file startup_stm32l4p5zgtx.s: After searching for two and a half hour I finally found the problem: the generated names for the interrupt h

Hi Everyone,I have been using SPC563M64L7 MCU Discovery board and created simple application utilizing PIT  with two channels , which interrupts with 1Hz and 10Hz frequency.The following main.c code toggles LED1 for Channel1 with 1Hz frequency and LED2 for Channel2 with 10Hz frequency (by using callbacks of two channels) . While this works well (according to logic)  with Load in RAM (Boot Mode) it does not work with Execute from Flash (Boot Mode).Does anyone know any root cause of this ? What I should be investigating ?  Regards,Mirek 

Hi, I am trying to develop a capacitive liquid level detector with the STM8L152 adapting an example of the STMTouch Library.It is fine to detect if there is water or not inside a container. But when I try it in my final solution, that is to detect the presence of battery liquid inside a battery container, it does not able to differenciate the presence of the liquid. The reason is that there are metalic plates inside the battery container and I believe that the plates are blinding the capacity of the sensor to detect the liquid.Do you know if there is any fine-tuning that I can use to help the application differentiate the the liquid from the metalic plates?Thank you,Rodrigo

See Inconsistent pin naming for CubeMX - does the same apply to CubeMX2 ?   (Cross-posting at the request of @Ghofrane GSOURI; again, no label available for "Suggestions")

Hi all, I have a small issue with the STM32N6570-DK board and the VENC_SDCard example code. The PN12 pin has a voltage of 0V (card inserted) or 1.80V (no card inserted); on the MCU side, the GPION data register (IDR) always shows a logic 0 in both situations. The VENC_SDCard / VENC_SDCard_ThreadX example code basically jumps over SD Card detection as it assumes a logic level of 0 == card present. If there is no card, mounting fails and aborts further processing. I have the requirement to react to card inserts / removals, so I'd like to trigger an interrupt or at least be able to read a logic high once in a while but could not find out what exactly is missing in the code. * I tested with an empty CubeMX project and set this PN12 to input; here I do see logic level changes.   * I susptected the VDDIO voltage domains to be at 3V3 for that block and manually switched VDDIO_SD to be at 1V8, but that did not show a change as well * I did not fiddle with security bit settings... may

Hi. I want to use the A HRTIM timer to independently control two MOSFETs. Namely, I have a transformer with the midpoint connected to the positive pole of the power supply, and these two transistors switch the 2 halves of the winding as lower switches to generate 2 half-waves of a sine wave.But I can't configure it in STN32CubeMX for the second output the condition for set. STN32CubeMX "Set Sources: nothing to set as Dead Time is enabled, Output2 signal is defined based on Output1 Configuration Set Sources must be 0." although the channels are configured as independent. Moreover, before the update there was no such problem. Now STM32CubeF3 Firmware Package V1.11.5Why the problem? 

We are currently evaluating the following STMicroelectronics IC for our application:SPV1040TTRAs part of our reliability and performance assessment, we kindly request your support in providing:Temperature vs. efficiency curves across the specified operating temperature rangeMTBF (Mean Time Between Failures) data or estimated MTBF hours for the above-mentioned ICs

Hi,Greeting!I am working on the STM32MP135F-DK board and trying to interface a 4x5 matrix keypad using GPIOs.I configured the keypad as follows:Columns (C1–C5):C1 → PE1 (Pin 37)C2 → PF11 (Pin 35)C3 → PF9 (Pin 33)C4 → PD13 (Pin 31)C5 → PE6 (Pin 29)Rows (R1–R4):R1 → PA0 (Pin 40)R2 → PA5 (Pin 38)R3 → PA7 (Pin 36)R4 → PE5 (Pin 32)After modifying the device tree and flashing the updated .dtb, I observe the following issues:The display becomes glitchy.The boot logo appears corrupted.The system becomes unresponsive after boot.Recovery is only possible after reflashing the starter package using STM32CubeProgrammer.From my analysis:Manual GPIO control seems to work correctly.The matrix_keypad driver is loaded not properly.matrix_keypad 20480 0 matrix_keymap 12288 1 matrix_keypadI suspect this might be related to incorrect GPIO or pinmux configuration, possibly causing a conflict with other peripherals (e.g., display).Could you please help identify:The root cause of this issue?Whether these GPIO

Good day folks,I have the DCMI camera interface on a STM32N6 streaming to the SDCard, and I am noticing that there are cases that the DCMI reports an Overrun when a SD access occurs at the same time that the Hsync interrupt was meant to occur.Digging into it I believe its due to congestion on the underlying AXI bus, and the IDMA of the SDMMC taking priority over the DCMI DMA. I have set the DCMI and its DMA to the highest possible priority as below. HAL_NVIC_SetPriority(GPDMA1_Channel12_IRQn, 0, 0); HAL_NVIC_EnableIRQ(GPDMA1_Channel12_IRQn); HAL_NVIC_SetPriority(DCMI_PSSI_IRQn, 0, 0); HAL_NVIC_EnableIRQ(DCMI_PSSI_IRQn); HAL_NVIC_SetPriority(SDMMC1_IRQn, 5, 5); HAL_NVIC_EnableIRQ(SDMMC1_IRQn); gpdma_dcmi.Instance = GPDMA1_Channel12; gpdma_dcmi.Init.Request = GPDMA1_REQUEST_DCMI_PSSI; gpdma_dcmi.Init.BlkHWRequest = DMA_BREQ_SINGLE_BURST; gpdma_dcmi.Init.Direction = DMA_PERIPH_TO_MEMORY; gpdma_dcmi.Init.SrcInc = DMA_SINC_FIXED; gpdma_dcmi.Init.DestInc = DMA_DINC_INCREMENTED;

Hello,In my project, I want to hold boot params in BKPSRAM so "Application project" can also write and read this section easily. If boot is needed, "Application project" will set boot params as required and after that it will use "NVIC_System_Reset".Therefore, I tried to write and read some parameters in this area. I can see the datas is written successfully in "BKPSRAM_BASE_S" section while debugging but when I restart the debug session, BKPSRAM section is all fill with zeros. I know that I am missing something but did not find it. - STM32N655 custom board. #define BKP_SRAM_START_ADDRESS ((uint32_t)BKPSRAM_BASE_S) #define BOOT_PARAMS_PTR ((BootParameters_t*)BKP_SRAM_START_ADDRESS) /* USER CODE BEGIN Init */ __HAL_RCC_PWR_CLK_ENABLE(); __HAL_RCC_RAMCFG_CLK_ENABLE(); __HAL_RCC_BKPSRAM_MEM_CLK_ENABLE(); HAL_PWR_EnableBkUpAccess(); HAL_PWREx_EnableBkupRAMRetention(); /* USER CODE END Init */ /* Configure the system clock */ SystemClock_Config(); /* Configure the per

I entered the lengths of the DDR traces from the ST official evaluation board into Excel, and the maximum length deviation is 3 mm. Is the trace routing on the evaluation board reasonable, and can I reuse it directly on my own board?   

Hello ST Community,My name is Gorakhnath. I am currently pursuing M.Tech (Power Electronics and Drives) at NIT Kurukshetra. I am using the STM32F4DISCOVERY (STM32F407VGT) board and I need stable DAC outputs for my hardware application.What I need (requirement)When the DAC command is 0 V, I need the output to be as close as possible to true 0.0000 V, because my external circuit maps:0 V → 0 A3 V → 50 AEven a small voltage like 0.045–0.05 V produces unwanted current (~0.5 A) in my system.Issue / ObservationOn both DAC pins:PA4 (DAC_OUT1)PA5 (DAC_OUT2)I measure about:~0.05 V (sometimes ~0.045 V) when the command is 0 VThis happens even when I am not sending any command from LabVIEW, or when I send 0,0.What I tried (software checks)Set DAC values to 0 using HAL on both channels:HAL_DAC_SetValue(..., 0) for DAC channel 1 and channel 2Forced PA4/PA5 to GPIO output LOW when command is 0 V:Configured PA4/PA5 as GPIO_MODE_OUTPUT_PP and wrote&nbs

Hello,I got a radio MCU which connects to cloud and can receive binaries from database. And I got a STM32 that controls some stuff, including other MCUs. In production this means a lot of headers and programming time for all of them, no way to update remotely, and even if the code is thoroughly tested - glitches are still possible.So I want to connect things in a chain, so that if something apart from the radio crashes - radio MCU could re-flash the whole system. This of course could be done with UART when using bootloaders, but this again means you have to pre-program bootloaders on MCUs, and there's still a very slim chance it might fail.So I need an example of how one MCU can flash another via JTAG or SWD (preferably), and then verify the result. From there I could get it to work on Arduino / STM / AVR / radio ARM. What I really want is a proof of concept simple test example to show it works with the peripheral (bit banging is always possible, but surely there is a smarter way to do

I am trying to develop a GUI application with the STM32H7S78-DK.  I want to send uart data from the board over wires to a raspberry pi.  To simplify the process without graphics I'm just trying to send a simple "Hello" string over UART7.  From what I can see from the data sheet, UART7 is connected to pins PE7 and PE8, which correspond to D0 and D1 on CN14 on the arduino headers by default.  Please correct me if I am wrong.  So I first am just initializing those pins with uart on STM32CubeMX then I was just sending a simple HAL_UART_Transmit() with a 2 second HAL_Delay().  However, I see no data coming through when putting a logic analyzer on those pins. What am I doing wrong?  Here is the very simple basic uart code in main.  /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************

Dear Support Team,I am planning to implement a circuit based on the TDA7293V. In this design, the IC will remain powered on, so I intend to use the circuit shown in Figure 6 (Single signal standby/mute control circuit) to prevent 'pop' noise. Given that my supply rails are ±44V (+Vs = +44V and -Vs = -44V), what is the recommended voltage range for the MUTE/ST-BY signal to ensure reliable operation?Thanks in advance!! With warm regards, Daniel.  

Unfortunately we experienced some serious issues with the Teseo-LIV4F regarding custom configurations on the CDB-ID 201 register.While the issue with broken NMEA output seems resolved by disabling I2C (See other topic)https://community.st.com/t5/gnss-positioning/teseo-liv4f-broken-nmea/m-p/886937#M1324Another issue remains: Completely missing $GNGGA frame at 9600 baud, but only when the device has a fix.Steps to reproduce:Flash the latest firmware (4.6.8.5.11)Disable I2CDisable GSV, VTG, GST, GSASet Baudrate to 9600Save settings and restartCommands:$PSTMSETPAR,1263,0x1,2 $PSTMSETPAR,1201,0x8001C,2 $PSTMSETPAR,1102,0x5 $PSTMSAVEPAR $PSTMSRR Connect to the device using 9600 baud, above should output RMC, GGA and GBS frames. At first this works, but as soon as a fix is reached the GGA frame is omitted: (Optionally send another $PSTMSRR to catch initial situation where GGA is still present)$PSTMVER,FreeRTOS_V10.4.3_ARM*57 $PSTMVER,BINIMG_STA8041_4.6.8.5.11_ARM*34 $PSTMVER,SW

HI,I am working on a board using STM32H573V and have a working solution with UCPD detecting an inserted memory stick and running the MSC class. In an other part of the software I am using PC9 as an GPIO push-pull, low speed output and as soon as I set it to high, the voltage at PB14 (UCPD CC2) drops from 3.3V to 1.5V and my UCPD handler signals a device attached and turns VBUS on even though nothing is attached. There is no other electrical connection between PC9 and PB14 on the board. I am using a TCPP03-M20 for VBUS switching. The board is acting as VBUS source.

About EVSTSPIN32G4, I started the code generated by MotorControl Workbench 5. Y.3 normally.If you transplant the IIC configuration of the pre drive and enable PWM output, the VDS will report an error.After carefully reading the generated code, it is found that before PWM complementary output, the lower tube is opened for charging, and the output PWM pre drive or VDS protection is written. Is there a routine for STSPIN32G4 IIC to configure PWM output?

It's telling me (for example) there's a "Path Entry Problem":Invalid project path: Include path not found (C:\Users\xxx\Documents\xxx\USB_CDC\USB_Device\Target).The Tool Settings / MCU GCC Compiler / Include paths contains"${workspace_loc:/${ProjName}/Application/USB_Device/Target}"and in my project there is a folder Application/USB_Device/Target, it links to a folder C:\Users\xxx\Documents\xxx\USB_CDC\STM32CubeIDE\Application\USB_Device\TargetHow can I figure out where this warning is coming from?(notice - the project builds just fine, it's just a warning, but company policy is to build without warnings)

Hello all,I've designed a board around a STM32H743 (LQFP-100) and am running into the following issue.On 2 boards out of 10, the HSE seems not to start properly. The HSE_RDY flag is never set after enabling HSE. I have checked it's not in bypass mode. On the other boards, it works perfectly.The crystal is a ABM3B-8.000MHZ-10-1-U-T and the load caps are 10 pF. We checked possible soldering issues, tested different load cap values just to see, and even replaced the crystal on the failing boards - to no avail.Looking at the OSC_IN/OSC_OUT signals (PH0/PH1) on a scope does not show a significant difference between the working and non-working boards. Maybe just a very slight difference in p-p amplitude.I have looked at the AN2867 app note, and the gain margin seems sufficient according to the formulas given there. I have heard that this crystal may have a bit too high ESR (200 ohm) for the STM32H7 HSE, but again, the gain margin seems alright.Any idea? I have tested with a minimal

Continued from: STM32 Host with ST67W611 Wifi BLEHi everyone, Currently, I'm trying to re-flash firmware for ST67W61 module via UART without host ( use USB TTL), and I got the issue in below:[22:36:53.388] - Serial port is COM5 [22:36:53.394] - ================================================== [22:36:53.394] - FW get address from partiton file C:\Users\Admin\STM32Cube\Repository\Packs\STMicroelectronics\X-CUBE-ST67W61\1.2.0\Projects\ST67W6X_Scripts\Binaries\NCP_Binaries\./partition.bin [22:36:53.394] - Address=0x10000 [22:36:53.394] - FW get size from partiton file C:\Users\Admin\STM32Cube\Repository\Packs\STMicroelectronics\X-CUBE-ST67W61\1.2.0\Projects\ST67W6X_Scripts\Binaries\NCP_Binaries\./partition.bin [22:36:53.394] - Size=1785856 [22:36:53.397] - Program Start [22:36:53.397] - ========= eflash loader cmd arguments ========= [22:36:53.397] - serial port is COM5 [22:36:53.397] - cpu_reset=False [22:36:53.677] - com speed: 2000000 [22:36:53.677] - ========= Interface is

I am running into issues building for the eMMC storage target for the `stm32mp25-disco` MACHINE type.I thought that adding "emmc" to `BOOTDEVICE_LABELS` should be enough to trigger building emmc flashlayout files. Is that not the case? I haven't found clear documentation on the subject.I tried making modifications to both `local.conf` and the machine conf directly. I was able to confirm the change takes affect with `bitbake -e`. Each time I build an image it only builds the flashlayout files for `sdcard`. What am I missing?mkdir yocto cd yocto repo init -u https://github.com/STMicroelectronics/oe-manifest -b refs/tags/openstlinux-6.6-yocto-scarthgap-mpu-v25.08.27 repo sync DISTRO=openstlinux-weston MACHINE=stm32mp25-disco source layers/meta-st/scripts/envsetup.sh printf "%s\n" 'BOOTDEVICE_LABELS = "emmc"' >>conf/local.conf bitbake core-image-minimal ls -l tmp-glibc/deploy/images/stm32mp25-disco/flashlayout_core-image-minimal/optee/ FlashLayout_sdcard_stm32mp257f-dk-ca35tdcid-os

Summary: When enabled st67w61 forcefully keeps MISO low and doesn't let other slaves use SPI. In our setup: - STM32L452: Is master SPI with latest mission_profile_t02. - st67w61: Is SPI slave 1 with dedicated CS pin - 3rd party SPI slave 2 with dedicated CS pin SPI bus speed is 2MHz, and CPOL, and CPHA are 0 Reproducing problem: 1.  st67w61 is enabled (CHIP_EN is HIGH), - BLE initialized W6X_Ble_Init() successfully - Advertisement starts - We are able to pair with st67w61 successfully via our phone - We then try to start SPI slave 2 with no success. Data is being sent via MOSI but MISO stays low. We have tried this with other types of slaves with no success. After turning OFF (CHIP_EN to LOW) st67w61 module, we can communicate successfully with Slave 2. However we need to have both slaves enabled for our application to work. Note that CS pins are in the correct state. It seems like the st67w61 forcefully pulls MISO line low when enabled and doe