Product forums

My design requires a microSD with the G474RE MCU.  The Eval board schematic shows the design and some code in the \driver\BSP.  However, I do not see the application example.  My requirements are to read and write multiple data files.  Where can I find an example with these features?  Any other eval examples I can port over?

Hi!My Linux is booting on my custom board. This board is using 2 GB (16-bit density) instead of 4 GB (32-bit density).So, when Linux is booted. I get this.Can it be so CubeMX is only fixed to 4GB when selecting STM32MP257F? Any suggestions? The complete log is attached.I'm using USART6 as debugging tool. flags=600, drv->flags=0, err=-129 Sending event 6/(unknown) to spy 'efi_disk del' Sending event 6/(unknown) to spy 'efi_disk del' eth1_clk_mx-0: When removing: flags=600, drv->flags=0, err=-129 Sending event 6/(unknown) to spy 'efi_disk del' eth1_mdio_mx-0: When removing: flags=600, drv->flags=0, err=-129 Sending event 6/(unknown) to spy 'efi_disk del' eth1_rgmii_mx-0: When removing: flags=600, drv->flags=0, err=-129 Sending event 6/(unknown) to spy 'efi_disk del' sdmmc1_mx-0: When removing: flags=600, drv->flags=0, err=-129 Sending event 6/(unknown) to spy 'efi_disk del' usart6_mx-0: When removing: flags=600, drv->flags=0, err=-129 pinctrl@44240000: When re

Hello everyone!I am trying to get all services and characteristics from steval-stwinbx1 board running FP-SNS-Datalog2 function pack. Here's simple program I wrote:import asyncio from bleak import BleakClient MAC_ADDRESS = "DA:3E:83:DD:30:F8" async def discover_services(mac_addr): async with BleakClient(mac_addr) as client: for service in client.services: print(f"\n[Service] {service.uuid}") print(f"Description: {service.description}") for char in service.characteristics: print(f" |") print(f" +-- [Characteristic] {char.uuid}") print(f" Properties: {', '.join(char.properties)}") if __name__ == "__main__": asyncio.run(discover_services(MAC_ADDRESS)) I expected to get services listed by nRF Connect app.But the program output is empty. Why? PS: I have done some research and experiments. I have tried running same script on linux and it ran perfectly (I used 2 machines: same machine (dual boot) and raspberry pi). I have noticed that board crashes if you are trying to

I noticed that STM32CubeMX2 (DEBUG features page) offers only three debug modes: JTAG 4‑pin, JTAG 5‑pin, and Single Wire Trace Asynchronous.In many practical cases, developers use only the SWCLK and SWDIO lines to save pins, so the absence of a simple Serial Wire option (without Trace) seems to be a limitation of the current STM32CubeMX2 release.This option is still available in STM32CubeMX1 when working with similar MCUs, such as the STM32H5 series.Is this understanding correct?

Hello, I am preparing to develop a custom board based on the STM32MP15 series MPU and getting accustomed to the DDR testing procedures in the STM32Cube ecosystem with an STM32MP157F-DK2 evaluation board. However, I am running into issues with the SYSRAM loading option which seems to be the necessary method for DDR testing new, custom boards designed around the STM32MP157 MPU. Firstly, I am able to run the DDR Test Suite in STM32CubeIDE or STM32CubeMX after importing the STM32DDRFW-UTIL-main\DDR_Tool\STM32MP157C-DK2 project into STM32CubeIDE. I am able to run the test firmware on the evaluation board with the "Debug As" option (with boot switches set to Engineering Mode), and then I am able go to a new .ioc project file made for the STM32MP157F-DK2 (peripherals initialized in their default modes) and use the DDR Test Suite via the "DDR Interactive" mode with no issues. Similarly, I can open a serial connection in TeraTerm via the ST-LINK COM port and run the DDR tests the

when you enable SWD in CubeMX2 it automatically blocks the SWO pin as well (tested using C531FBP6), but I only need SWCLK / SWDIO to debug. please add a way to disable the use of SWO.

Hello everyone, I'm having issues with the Heap of the LWIP that is used/full, and I can't do any mem_malloc. I have dig a bit on why the log of LWIP tells me that  it couldn't allocate memory ("etharp_raw: could not allocate pbuf for ARP request"). As far as i understand, the mem_malloc used the struct mem *lfree variable to handle the allocation for the LWIP and which is the next/previous chuck and also if the next chunk is being used or not.     struct mem { /** index (-> ram[next]) of the next struct */ mem_size_t next; /** index (-> ram[prev]) of the previous struct */ mem_size_t prev; /** 1: this area is used; 0: this area is unused */ u8_t used; #if MEM_OVERFLOW_CHECK /** this keeps track of the user allocation size for guard checks */ mem_size_t user_size; #endif };     My issue is that the variable used in the mem struct is never null or zero. Which lead to the mem_malloc to always return NULL even after a fresh upload or power

 The GUI for the programmer shows:  RM0440 Rev 8 shows:Are ‘BOOT0’ and ‘nBOOT0’ different? As it stands, the programmer requires a value of ‘0’ to boot from FLASH, but the table wants a value of ‘1’. Is the value referenced by nBOOT1 the inverse of the value set in nBOOT0?

Hello,    I have designed a custom PCB using STM32N657I0HxQ and W25Q32JWZPIQ NOR flash. I am following the STM32N6 FSBL Load & Run tutorial https://community.st.com/t5/stm32-mcus/how-to-create-an-stm32n6-fsbl-load-and-run/ta-p/768206 , but have trouble getting the application running. I am using below setup:STM32CubeIDE - v1.19.0STM32CubeProgrammer -v2.21.0STM32CubeMX - v6.15.0I have created a custom external memory loader for W25Q32JWZPIQ and able to connect device in Dev boot mode (BOOT1 -1, BOOT0-0) and flash FSBL-trusted.bin and Appli-trusted.bin at 0x70000000 and 0x70100000 respectively. Also, I am able to verify the contents.  When I connect to Flash boot mode (BOOT1-0, BOOT0-0), Led is not blinking. I tried to debug by setting device into Dev mode and run FSBL directly into internal RAM, I can see the FSBL is properly copying the application code to 0x34000000 but JumpToApp() ends up in fault.I have tried the belowFSBL-t

Hi, I’m working with FATFS + SDIO + USB mass storage class.But I can’t seem to get writing and as a consequence reading working.in my main.c I do: //fatfs test makeFileData("test12.txt", "TEST123"); char* data = readFileData("test12.txt"); printf("read data = %s\r\n", data); And in my console I get as a response:D-SH 0 /System Volume Information---- 209 /x1_DEFAULT.JSON---- 211 /x2_DEFAULT.JSON---- 211 /x3_DEFAULT.JSON---- 211 /Ik_heb_iets_verzonne.JSONTotal blocks: 1922016 (961 Mb)Free blocks : 1921888 (960 Mb)SD Card Block size = 512SD Card Block number = 1953792SD Card size = 1000341SD Card Version = 1Init WVR complete!f_write failed: 1read data = So It can open the card and perform a ls command, but for some reason I can’t write. I spotted that some people look at DMA but I’m not using DMA.My entire SD card Handler:/* * SD_Card_Handler.c * * Created on: June 24, 2026 * Author: william.vanraemdonck */#include "WVR/SD/SD_Card_Handler.h"#incl

We are using the STM32WBA5MMG in our design but because of space and the shape of the board we need to be very precise with our components. The issue i'm having is with the documentation of the clearance required for the STM32WBA5MMG.In document “DS14801 @6.4 schematics and layout for pcb” the clearance on the left side of the package is 1.93mm from the side of the packageBut in “AN6305 @figure 35 to 39” the clearance on the side of the package is 1.93mm from the left side of pin 72.We are going to use the STM32 with the +10dB for Bluetooth and need the best option but also need to fit a lot of components on the PCB. Q.What clearance do i need to follow for the best Bluetooth signal, clearance in AN6305 or DS14801?

My test conditionAs you can see the detection volume of FoV is going outside the reflective block (blue block) and I am not getting accurate reading. I want to know whether there is a way to make the FoV much narrower so that I can concentrate on the reflective block placed opposite to the TOF sensor.

Hello,I’m struggling using STM32_USB_Device_Library V2.10.I’m developing a device with storage, and I want to transfer files via USB to a Windows PC using MTP.I currently have a simple setup using STM32H7B3 eval board. I have made a test project with STM32_USB_Device_Library using the USB HS.I have come so far that the device is showing up on the PC, and I can read contents (files) from the dummy file system on the device (currently I just fake the file system). Files are showing up correctly in File Explorer. I have 5 files, from 1K to 5K size, on the device.But when I try to transfer the files to PC, I only get 16 bytes of data. Size of file is showing correct in Windows Explorer for the device, but for the transferred file, it is only 16 bytes. It also does not contain correct data, only a chunk of the first data in the file.I have used usbd_mtp_if_template.c as start, and implemented the functions for reading file system data.The USBD_MTP_Itf_ReadData() looks like this:static uint3

After generating the BLE_Sensor project files for the B-WBA5M-WPAN board with STM32CubeMX Version 6.17.0, the STM32CubeIDE shown this error. I looked for the file in STM32Cube_FW_WBA_V1.9.0 and it is not there. Please advise.10:56:39 **** Incremental Build of configuration Debug for project BLE_Sensor ****make -j9 allmake: *** No rule to make target '/Users/user/STM32Cube/Example/BLE_Sensor/Drivers/STM32WBAxx_HAL_Driver/Src/stm32wbaxx_hal_pka.c', needed by 'Drivers/STM32WBAxx_HAL_Driver/stm32wbaxx_hal_pka.o'. Stop."make -j9 all" terminated with exit code 2. Build might be incomplete.

Hello, I am trying to create a very simple TZ-Enabled application on the STM32H573 in a CMake project. My application can build and flash to the IC and execute the main.c of the secure world but it hard faults, I believe when switching to the non-secure world. I am unsure of why it does this and would like help figuring that out. I’ve attached the project to this post and I will provide information below: Fault Analyzer OutputFault Analyzer OutputR0:      0x2009FC00 ← Non-Secure RAM (Non-Secure SP?)R1:      0x08110B68 ← Non-Secure FLASH (See Vector Table Non-Secure Memory (Non-Secure Main Entry?))R2:      0x08110B68 ← See AboveR3:      0x08110B68 ← See AboveR12:    0x08110B68 ← See AboveSP:      0x3004FF74 ← Secure RAMLR:      0xFFFFFFA9PC:      0x0C000FF6XPSR: 0x09000003 Vector Table Non-Secure MemoryThis is some data from memory address 0x0810 0000Address 0 4 8 C 0x0810 0000 200A 0000 0811 0B69 0811 0BC5 0811 0BC5 0x810 0010 0810 03BD 0811 0BC5 0810 03C3 081

Hello ST Team,The STM32N6 DK2 board includes the Sony IMX335 image sensor, but I have not been able to find the official sensor datasheet or a complete register reference document.For advanced development tasks such as HDR configuration, exposure control, gain tuning, and custom sensor initialization, access to the sensor register descriptions is essential.Could ST please clarify: Is the official IMX335 datasheet available to STM32N6 DK2 users? If the full datasheet cannot be shared due to Sony licensing restrictions, is there a register map, application note, or programming guide available that documents the sensor registers used by the STM32N6 DK2 BSP driver? What is the recommended process for obtaining the official IMX335 documentation required for sensor configuration and HDR development? Without access to the sensor register documentation, it is difficult to implement or evaluate advanced sensor features beyond those already exposed by the BSP driver.Thank you for your suppor

Hi, I am experiencing a technical issue with the ST 16GZMAI camera when connected to the EVK-U0I1 control board. While the system works fine with my 55G1MBI1 camera, the EVK GS 1.1.2 GUI fails to recognize this specific model and displays the following error: "Error: could not broadcast input array from shape (341,280) into shape (340,280)" I am also unable to change the detector format. Could you please refer me to a technical expert who can assist with the configuration of this model? Best regards, Sean

I recently tried to use -noreconnect via the cli on windows and it still attempted to reconnect.I was connected via UART and programming option bytes. Here was the command I used:& "C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" -c port=COM14 br=115200 -noreconnect -ob ndbank=0x0I see that there was fix put in for linux. Im wondering if the same bug exists on Windows.Thanks,Daniel 

I have ordered the Nucleo-C542C board. I am waiting on the board to arrive so I thought I would setup a blinky project to test on the board. i used MX2 to setup the GPIO, clock, etc. I then imported the project int CubeIDE using the CMAKE option.Apparently there is no way to build a release file. This means I will not be able to program the board. The build hammer only shows the debug build option.Also, I do not see the .ioc file in the project tree. Apparently I don’t understand how MX2 and CubeIDE link together. If I am able to ever find the .ioc file, will it be updated if I make changes in MX2? The old version of CubeMX linked the.ioc files together. If changes were made by CubeMX, those changes were reflected in CubeIDE.As a side note, there is one aggravating minor issue with CUBEMX2. Why are all the screens so washed out and difficult to see?. Everything that should be solid black is a barely visible light colored grey. This is particularly annoying in the GPIO chip pinout view.

Hello,I’m using the SBSFU by MCUboot implementation from the STM32CubeU5 Project (here).It works well on the target board (U585) and I succeeded at uploading a new firmware through Teraterm, as per the documentation :  But our teams cannot all have access to a PC with Windows, and as such I attempted to make an upload with Minicom on Linux (Ubuntu) instead, which did not work (I added the “Bytes” logging before the “Abort from user” message) :  I saw much discussions about a similar problem on the legacy SBSFU 2.4 / 2.7 (this one or this one for example), but none for the one using MCUboot. I’ve still tried most of the solutions proposed there, but to no avail. I’ve tried fiddling around the code to see why the Ymodem protocol was failing through Minicom, but haven’t found much actionable information up to now.Has anyone encountered this problem and may know how to patch it or work around it ?I’ll continue to investigate on my end and document my eventual findings here. Thanks in advan

Hi,I encountered problems during the development process of using FMAC. To illustrate the problem simply, I used FMAC to implement an RC filter, by which I mean to illustrate the calculation problems of FMAC.RC filter:10K+10nFIts discrete z-domain expression：（Ts=1e-6,Tustin）so I get fixed-point parameters :I referred to the example program of AN5305 and used a 1-us timer to trigger ADC sampling. After the ADC sampling is completed, DMA writes to the WriteData of FMAC, and then the ReadData is processed in the interrupt as follows:As shown above, my current ADC sample is 0, and my Vref is set to 800. I think the output of FMAC as an RC filter should be around 800 in the DC case, but actually it is not. It is a relatively small value. Why is that?May I ask if there is a problem with my configuration of FMAC?  

Dear Gentlemen,as a relative beginner using STM32C5 MCU-s,I need your help to resolve one issue.Namely,In new design,  where planned MCU is STM32C542CCT6 device, (LQFP48 package),I plan to use internal Comparator COMP2.Problem (for me) arises when I have to declare connection between Comparator nodes(INP-  (M), INP + (P) and OUTPUT) with some specific pins on LQFP48 package,    more precisely it would be ideal for me to use PA7 pin as Comparator2 Outputand pin PA2 as Comparator2 -INPut, and pin PA3 as Comparator2 +INPut.In short,it is not a problem to "connect" Comparator Output, COMP2_OUT as shown in Table 12 STM32C542xx pin/ball definition, on STM32C542xx data sheet (DS), page 41, or in Table 13 Alternate functions, since i will declare AF14 = COMP2_OUT in appropriate GPIOA_AFRL register, see page 352 in RM0522 Reference manual, (RM)but I have problem to declare Comparator2 INPut pins, since it is selected thru peripheral registers,as stated in Table 11 in device DS, ...Additional fu

Discrepancy between AN5967 and MB1940 schematic regarding VDDA18PMU / VDDSMPS connections in external SMPS mode Hello ST Team,We have a custom board based on the STM32N657X0H3Q, designed using the MB1940 (Nucleo-N657X0Q) schematic as reference. The board has been fabricated and assembled, and we are currently in the bring-up phase.During bring-up we encountered a failure on the external SMPS path (TPS62088YFP) used for VDDCORE generation. The external buck failed with a shorted high-side FET, driving 5V directly onto the VDDCORE rail. After investigation, we recovered the board by removing the failed external buck and switching to the on-chip internal SMPS, which is currently working correctly and supplying VDDCORE at 0.810 V.While reviewing the power supply architecture during this debug, we noticed a discrepancy between AN5967 (Getting started with hardware development for STM32N6 MCUs) and the MB1940 reference design that we would like clarification on.DiscrepancyAN5967, Sectio

hello,When using MDMA (STM32H753), and more than one transfer, the code generated doesn't align correctly the struct MDMA_LinkNodeTypeDef. This structure should be aligned with 64 bits.Please, see : https://community.st.com/t5/stm32-mcus-embedded-software/stm32h753zi-mdma-issue-with-linked-list-dma-adc/m-p/897390CubeMX : V6.17Thanks,best regards,Laurent  

Hello,We are evaluating ST microcontrollers for a new product and would like some clarification regarding long-term availability.The STM8 family is now marked as NRND, and I have seen references in community discussions to a possible discontinuation around 2032.Could ST please clarify: What is the official long-term availability plan for the STM8 family and is there currently an announced End-of-Life date for STM8 devices? As STM32C0 is often presented as the migration path from STM8, I would also like to know whether the STM32C011 is covered by ST's longevity program and what its currently committed availability date is.Thank you for your help.