Solved

NUCLEO-V873XJ board bring-up.STM32CubeIDE 2.2.0 includes support for the STM32V8 series devices; however, the NUCLEO-V873XJ board is currently not available within STM32CubeMX board configurations

Hi,I'm trying to setup HSO on the G431, I used the B-G431B-ESC1 board as a starting guide. I'm trying to use differential sensing with internal OP-AMPs and internal PGA. I have split the currents and phase voltages across ADC1 and ADC2 but I still cannot get the HSO option to show up with MC workbench. I'm using the latest version. I have attached my board JSON file, any guidance will be appreciated.Thanks,Ray

Hello,        I am new to STM32 MCUs. We are looking for a low-pin-count MCU with DAC, CAN, and Timer peripherals. Currently, we         are working on a DAC application using the NUCLEO-F429ZI board.       Could you please suggest a suitable STM32 MCU with fewer pins that supports mainly DAC, CAN, and Timer peripherals? Thanks and Regards,

Hello everyone,I am bringing up a custom motor control inverter board based on the  STEVAL-TTM001V1 evaluation kit. I am using StellarStudio, OpenOCD, and the Stellar Motor Control Tool Kit (MCTK with StellarESDK-1.7.0).The Problem: My firmware runs perfectly when launched via a Debug session in StellarStudio. I can step through the code, initialize peripherals, and hit my main loop. However, if I disconnect the debugger and power-cycle the board (or press the physical Reset button), the application completely fails to start.What I have verified so far: Flash Linking: My linker script is correctly pointing to Flash (core1_nvm at 0x08000000). OpenOCD successfully flashes and reports ** Verified OK **. The Trap Location: If I power-cycle the board, let it fail, and then hot-attach the debugger without resetting, I find the PC is trapped in an infinite assembly loop. No Hardware Faults: While trapped in this loop, I checked the CFSR register (0xE000ED28), and it reads 0x00000000. This

Context : I want to write a FSBL load and run application on a custom minimal PCB based on STM32N6-DK design. The board uses SMPS power supply and not the default power supply of the STM32N6-DK. I follow this original tutorial  as a main example. Problem faced: CubeProgrammer SigningTool version compatibility and header size 1) Write a custom external bootloader to write and read external flash memoryModify the power supply parameter (System Core --> RCC --> SupplySource) in CubeMX to `PWR_SMPS_SUPPLY`Generate ExtMemLoader template from CubeMX Build ExtMemLoader to generate .stldr filemake sure the post build script can be executedmanually copy the .stldr file generated in `/STM32CubeProgrammer.app/Contents/Resources/bin/ExternalLoader/` if necessary  2) Modify SigningTool header generation command in FSBL post-build Build FSBL & Application following the original tutorialCheck heading size, it might be different from the 0x400 that is defin

I have some stored links, which use the stcommunity.st.com third-level domain (note that it is not community but stcommunity), for example https://stcommunity.st.com/t5/stm32-mcus/empty-check-mechanism-on-stm32/ta-p/49369These now display a message saying Khoros is down. As it’s an st.com domain, i.e. under ST’s control, these may be changed.A proper redirection would be nice.JW  

Hi,I have a firmware running on an STM32H753 that was working correctly. After updating the STM32H7xx_HAL_Driver (by performing the migration in STM32CubeMX), the MCU gets stuck during the execution of SystemClock_Config().While debugging, I noticed that before the migration CubeMX generated:HAL_RCC_ClockConfig(&RCC_ClkInitStruct, FLASH_LATENCY_2)After the migration, the same function is generated as:HAL_RCC_ClockConfig(&RCC_ClkInitStruct, FLASH_LATENCY_0)If I manually change it back to:HAL_RCC_ClockConfig(&RCC_ClkInitStruct, FLASH_LATENCY_2)the MCU works correctly again. However, every time I regenerate the code from CubeMX, it goes back to FLASH_LATENCY_0.I have already tried changing the PLL and clock parameters in the Clock Configuration tab of CubeMX and then restoring the original values, to check whether CubeMX was not correctly updating the clock tree calculation, but the generated code still contains FLASH_LATENCY_0. Is this a bug introduced in the new HAL driver/C

I am using a STM32G071CB MCU on a device that connects to a battery that supports USB PD and I would like to get a battery status periodically. Code generated by STM32CubeMX that includes trace and GUI code works as expected when using STM32CubeMonitor-UCPD. However, the return path of a battery status reply message does not go through usbpd_dpm_user.c, but through GUI code instead. I would like my application to use usbpd_dpm_user.c as the interface using STM32Cube_FW_G0_V1.6.3, but information on how to do that is incomplete and examples are outdated. There seems to be more required than just selecting appropriate usbpd PE options and adding code to USBPD_DPM_SetDataInfo().Currently, USBPD_DPM_RequestGetBatteryStatus() returns USBPD_ERROR, but a request is send to the battery anyway. However, the battery status reply message does not trigger a call to USBPD_DPM_SetDataInfo() or USBPD_DPM_ExtendedMessageReceived(). What am I missing? Is there any documentation other than usbpd basics?

Dear STM Support Team,the following CLI command takes about 30 seconds on a Raspberry Pi (thanks again btw!) compared to 1 second max on windows: STM32_Programmer_CLI -c port=swd sn=xyz I am using this in a loop to detect whether a MCU is connected.All other commands i tried are comparable in speed to windows so i guess this is a bug.The Pi is a Model 5 running Bookworm and a 6.12 kernel. Thank you very much!   

Hi there, Is there a drop in replacment for the IS42S32800G-6BLI (besides the obselete MT48LC4M32B2B5)? Or one that is recommended with the STM32H757?

Hi,I am in the middle of migrating a project from STM32F767 to STM32H743. Both MCUs being compatible helped a lot.But there have been still a few road blocks, the last of which seems to be SPI. We use SPI3 to interface with a RA8875 based LCD. With DMA, we were able to get good results on F767, but so far not so much on H743. After connecting MOSI/MISO/CLK/CS lines to a logic analyzer, I noticed there both MOSI and CLK lines idle about the half of the time. Please see the screenshot below. During a supposedly active session of data transmission, either through DMA, or blocking write, there are several gaps. The measured during of those gaps are about either 5ms or 6ms.My question is: when would a SPI instance go into idle state? waiting for TX data to be ready (related to the famous D-cache issue on H7)? Please advise. Thanks in advance.ZL  

Hi,In my project with STM32N6 am not using CSI interface, so in this case, all CSI pins are not connected.But what about CSI output CSI_REXT where according to the manual must be connected 200 Ohm resistor to GND?Can I keep this pin unconncted too? In the manual there is only information that resistor is for setting current for RX/TX driver. Similar situation is in USB interfaces, but in STM32N6 Nucleo-144 development board is one of the USB completly unconnected (including OTG2_TXRTUNE pin with similar function like CSI_REXT pin). Which I take as an aswer in case of USB.I dont know what is diferences in internal structure between RX/TX driver in USB and CSI, but i case of USB in my project (USB is not used too) i wil keep every pins unconnected. But can I afford it in case of CSI? Thanks a lot.Rddk. 

Hello,On an STM32H725, changing RDP from Level 0 to Level 1 causes the firmware to stop running. In my device, the LED and FDCAN stop responding, even without a debugger connected. During debug session, this occurs in “HAL_FLASH_OB_Launch()”, more specifically after “SET_BIT(FLASH->OPTCR, FLASH_OPTCR_OPTSTART);”.  After a manual power cycle, the firmware runs normally and RDP Level 1 is successfully applied.Is this expected behavior? Is a reset required after changing RDP from Level 0 to Level 1,Thanks!

Dear community, I’m sharing an application that has been highly requested recently: a demo running TouchGFX on the STM32N6570-DK with a camera module.Please note that this demo is NOT yet finalized. We plan to significantly enhance it over the coming weeks, and once it is ready, it will be directly available in TouchGFX Designer as a board-specific demo (under the Demo tab).In the meantime, since there has been strong demand, here is an early draft that you can already use and draw inspiration from.Another note, we’ll provide only limited support for any questions about this draft, as we are aware of the application’s limitations and are working on a much better version. Again, this demo is not final and does not reflect the quality of an official demo.The project works with TouchGFX 4.25.0 and with STM32CubeIDE. We advise NOT to regenerate code from STM32CubeMX (because there is a limitation here). You can use the flashing scripts provided in the project to flash your board.  

Hi ,I'm developing a product on an STM32N6 using TouchGFX. I need to display the image coming from the camera input on the product on the TouchGFX. During our tests, we were able to directly print the image from the DCMI input to the screen and it worked. However, we need an example that takes this image and displays it on the TouchGFX. The AI ​​example prepared for the N6 actually includes this type of work, but the code is not accessible. Could you please share the relevant project or the relevant part so I can integrate it into my project, or could you provide an example project for this?

Hello ST Team,I am working with the STM32N6570-DK board and trying to display the live camera feed on a TouchGFX application.I cannot find any ready-to-use example that integrates DCMIPP (Camera) and TouchGFX.Current Situation:TouchGFX Designer: I have created a UI with a transparent area in the center (Alpha = 0) to display the camera feed. (Please see the attached screenshot).Cube IDE Firmware:  I found the DCMIPP_ContinuousMode example and confirmed that it works fine independently. However, merging it into a TouchGFX project manually is quite difficult for me.My Question:Is there a simple, official example or Application Note demonstrating Camera Preview (maybe on Layer 0) + TouchGFX UI (maybe on Layer 1) for the STM32N6570-DK?Since I am new to the STM32N6 series, a detailed, step-by-step explanation would be very helpful.I would appreciate a quick guide or a GitHub link.Thanks.

Table 73 of STM32WL33xx Datasheet indicates an “A” option for Frequency band options (398-464 MHz). I cannot find this variant in stock anywhere. How/when can I purchase this? Will there be a breakout/demo/nucleo board for this “A” version? Thank you.

Hello dear ST Community,I am not sure I can get help here as this topic is related to a WeAct Studio STM32F412 board and not a Nucleo or Discovery board from ST. If not that is fine , no problem.So, back to my issue : For this particular type of project, in the past we used STM32F411 boards but this time we had to change to a board with more RAM's ...The rest of the code in the MCU works as expected.When we connect the USB cable to PC in the Device Manager we get this error :"Unknown USB Device ( Device descriptor Request failed )"We using CubeMX and STM32Cube in VSCodeIn CubeMX I setup now just the basic USB_OTG_FS : Device onlyMiddleware : USB Device as Human Interface device class (HID)** We can share code or ioc file if needed …What I did :- USB Clock is set 48MHz- I tried HSI and HSE for the clock - there is said for the USB to work it requires HSE- I changed the USB cable- I revert to just basic HID and the default report ( but anyway Windows didn’t asked for it yet … )Could you

Dear ST Support Team,I am an embedded systems engineer currently designing a custom PCB around the STM32MP257F microprocessor for a product application (a camera-based embedded system). I am using the STM32MP257F-EV1 evaluation board as our reference design for both hardware and software bring-up.We are now finalizing our own DDR memory design and are running into difficulty sourcing a DDR part that is confirmed compatible with the STM32MP257F. We understand the EV1 reference design uses two 16-Gbit DDR4 DRAMs (16-bit wide, populated for a 32-bit total bus), and that the STM32MP257 DDR controller supports DDR3L up to 2133, DDR4 up to 2400, and LPDDR4 up to 2400, in 16-bit or 32-bit configurations. However, when we check current market availability, we are not able to find DDR parts that are clearly qualified or validated against the STM32MP257F DDR controller, and we want to avoid selecting a part that causes signal integrity, timing, or DDR-training issues on our own layout.Could you

EDIT: Solved. It seems to just be that one pin that isn’t working. I tried a couple other ones and they work fine.Hello, sorry if this is a silly question, but I'm pretty new to all of this. I've recently picked up Israel Gbati's Bare-Metal Embedded C Programming. It gives a step-by-step walkthrough on how to turn on an LED using pin D12/PA5, but I'm struggling to connect to any of the other pins.I've been trying to connect my LED to pin D0/PA3. My code is below.#define PERIPH_BASE (0x40000000UL)#define AHB1PERIPH_OFFSET (0x00020000UL)#define AHB1PERIPH_BASE (PERIPH_BASE + AHB1PERIPH_OFFSET)#define GPIOA_OFFSET (0x0000UL)#define GPIOA_BASE (AHB1PERIPH_BASE + GPIOA_OFFSET)#define RCC_OFFSET (0x3800UL)#define RCC_BASE (AHB1PERIPH_BASE + RCC_OFFSET)#define AHB1EN_R_OFFSET (0x30UL)#define RCC_AHB1EN_R (*(volatile unsigned int *) (RCC_BASE + AHB1EN_R_OFFSET))#define MODE_R_OFFSET (0x00UL)#define GPIOA_MODE_R

Hi! I tried to stream a 1080p (big buck Bunny) video with gstreamer. It seems that it was falling back to software and starts lagging.Are there any known issues with gstreamer for the MP2 i should be aware of? I have not used the latest OpenSTLinux version yet. I'm using v26.02.18. Still: kmscube is working perfectly in 1080p. So, I assume the the Vulkan/OpenGL ES is working properly as it should.

Hi,I was trying to figure out how to use external memory and flash with xcubeai, and I found a video posted by STM32 says there is an example food recognition code in stm32ai-modelzoo-services on Github. However, I couldn't find it. Was it deleted?thanks.

“STM32CubeMX FMC pin solver hangs on STM32H7R7 when legal alternate FMC address mappings are present; removing redundant A16–A23 alternate functions avoids the hang.”… attached is project with stm32H7R7L8H3 with FMC32 configured with 4x SRAM and 2x SDRAM but for this was used patched mcu definition file “STM32H7R7L8HxH.xml” (included, has commented alternate address lines on upper pins which point to bottom address pins in fact, the “solver” is probably confused - I opted to forced exclusive one selected variant and then FMC configurrator stopped hanging on multiple selected SRAM/SDRAM … without patch it is impossible to configure … it probably MUST beheve similary on different parts also - provided is also list of potential other packages … I used chatgpt (high) to analyze this and she found issue also with help of log …I also tried to configurpart stm32H7R7L8H6H (only 16bit FMC) - this worked … and surprisingly worked also stm332F429NEHx with FMC32 - I was confused too, where is prob

Hi,I am using an STM32H7S3L8 with D-Cache enabled and want to place DMA buffers in a dedicated non-cacheable SRAM region.My linker script places the DMA section in SRAM2:SRAMAHB (rw) : ORIGIN = 0x30000000, LENGTH = 16KSRAM_DMA (xrw) : ORIGIN = 0x30004000, LENGTH = 16K.dma_buffer (NOLOAD) :{ . = ALIGN(32); __dma_buffer_start__ = .; KEEP(*(.dma_buffer)) KEEP(*(.dma_buffer*)) . = ALIGN(32); __dma_buffer_end__ = .;} > SRAM_DMAThe DMA buffer is correctly linked at 0x30004000.I configured the MPU according to the non-cacheable DMA buffer strategy described in ST's article. The relevant configuration is: static void MPU_Config(void){ MPU_Region_InitTypeDef MPU_InitStruct = {0}; /* Disables the MPU */ HAL_MPU_Disable(); /* Disables all MPU regions */ for(uint8_t i=0; i<__MPU_REGIONCOUNT; i++) { HAL_MPU_DisableRegion(i); } /** Initializes and configures the Region and the memory to be protected */ MPU_InitStruct.Enable = MPU_REGION_ENABLE; MPU_InitStruct.

Hello ,I am planning a new NB-IoT design using the ST87M01 module. I am currently using a Nucleo-U545RE-Q host board paired with the EVKITST87M01-2 evaluation kit.The application involves downloading weather observation files (TXT and XML formats, each under 100 KB) from a public server over HTTPS. Since the target server requires TLS 1.3, a large HARICA RSA ROOT CA 2021 (RSA-4096) certificate, and specific Cipher Suites not supported natively by the module, I have decided to run the TLS 1.3 stack directly on the STM32U545 host MCU. The ST87M01 will be used purely as a transparent TCP/IP pipe.Specifically, the server enforces strict cryptographic handshakes with the following parameters, which I will process on the host MCU:TLS 1.2: ECDHE_RSA with curve P-256 and AES_128_GCM TLS 1.3: X25519 key exchange and AES_256_GCM During early tests, I have noticed that the module frequently transitions from RRC Connected to RRC Idle mode, indicated by the unsolicited notification changing from +C