Solved

Got a message: " Break at address "0x8001c50" with no debug information available, or outside of program code." and exited. Please help. If you need more info please advise.

Board: STM32H750B-DK (DK32H750B$AT1)IDE: STM32CubeIDE 1.14.1CubeMX: 6.11.1TouchGFX: 4.23.1Firmware: STM32Cube FW_H7 V1.12.1Problem Description:I created a new TouchGFX project for the STM32H750B-DK board. The project builds successfully (0 errors, 1 warning), but I cannot debug it. When starting a debug session, I get the error: "Cannot access memory at address 0x90000000".The project is configured to use external QSPI flash (0x90000000) for code execution (XIP) since the code size (424KB) exceeds the H750's internal flash (128KB).What Works:Project builds successfullySimple non-TouchGFX blinky projects debug successfullyWhat Fails:Debug session fails with memory access errors at 0x90000000Attempts to set SP/PC from external flash vector table failAs found STMicroelectronics ST-LINK GDB server. Version 7.12.0Copyright (c) 2025, STMicroelectronics. All rights reserved. Starting server with the following options:Persistent Mode : DisabledLogging Level : 1Listen Port Number : 61

Hello,I have a PCB with two microphones (IM66D132HV01) with an STM32U575RGT6 (64pin) micro.Both microphones are connected (L+R) to a single input {PC0, PC2} = {MDF1_SDI4, MDF1_CCK1}Firstly I cannot find any example code that produces output samples in the MDF1_Filter3->DFLTDR,  MDF1_Filter4->DFLTDR data registers -- they are always zero.I can get the MCU to produce a clock signal and I can see a data bit stream coming to the MCU, from the microphones.       As I was a bit stuck, I resorted to using CubeMX to hopefully get some working code --- however -- with CubeMX the common clock was no longer visible.I also notcied that if I set up MDF1_F3, and MDF1_F4, that  I cannot tell CUBEMX that actually I only need the 'MDF1_SDI4' input since the two filters share the same MDF1_SDI4 bus (one outputs on low clock, the other on high).Also,  I'm looking for some sample code that can give me interrupts for each of the left and right samples, as

Hello,I am currently testing out the model zoo examples, following https://community.st.com/t5/stm32-mcus/how-to-run-ai-models-from-model-zoo-on-stm32n6/ta-p/814254 and the READMES. Programming the .hex files to the STM32N6-DK works and produces a running firmware. However, when I compile the application using the provided makefile and flash it onto the MCU as described in the README, the screen just remains black. I tested this for object-detection, face-detection and pose-estimation.Best,Steve

Hi all,I’m trying to compile an ONNX model that has float32 input and output. When I compile the model using ST Edge AI, the generated output ONNX shows both input and output as INT8 instead of float32. I wanted to understand:- Is this behavior because the model is being compiled specifically as an ONNX model?- Or is there a specific reason STEdgeAI is forcing INT8 input/output during compilation (e.g., quantization settings, optimization constraints, or tool limitations)? Any clarification on how STEdgeAI handles mixed-precision models and I/O types would be really helpful.Thanks in advance!

Hello,I use a STSAFE-A110 chip on a own board based on STM32 MCU.As I was unable to integrate the STSAFE library provided by ST on my specific fw, I wrote features whom I need as as echo, generate random, retrieve product data, generate host key, retrieve product data partition, read/update NVM.All works fine but when I am unable to read a NVM zone with 'host' access condition. NVV zones with no specific AC are well read. Find below configuration of the NVM of my STSAFE chip.+=======+================+==============+========+==============+========+==============+| Zone | Data segment | Read AC | Read | Update AC | Update | One-way || index | length (bytes) | change right | AC | change right | AC | Counter |+=======+================+==============+========+==============+========+==============+| 0 | 1000 | False | always | True | never | False, 0 || 1 | 700 | True | always | True | always | False, 0 || 2 | 600 | False | host | True | always | False, 0 || 3 | 600 | True | always | True

Code is written using stm32CubeMX. Connecting with stmlink V3 Minie. Executing step by step, it appears that debug fails (lose connection) when executing debug_init. In fact debug_init creates the problem when programming pa13.When removing the initialization of PA13 and PA14 in debug init, things seems to work but I have no idea of potential side effect. An recommendation?

Hi,On the SR6P3C4 page (https://www.st.com/en/automotive-microcontrollers/sr6p3c4.html) there's a databrief. But not much about a datasheet, specification, or any deeper information about the modules associated with it. Is there a way to access those?Also (still related to the first question), the data brief does say something about maximum junction temperature of 165C, with a note:Nominal specification up to 150 °C. Delta specification up to 165 °C.I'm not sure to understand what does the delta specification means.Thank You

I want to interface STM32G474 MCU with DS18B20 digital temperature probe in my project. The DS18B20 uses one-wire interface. Is one wire interface supported with this MCU?  Kindly provide a detailed explanation. Help please. Datasheet link for DS1B20: EVVO DS18B20Axx Regards,Sreejith

Hi STM32 experts, I've been digging through the STM32WBA65RI datasheet and the RM0515 STM32WBA6xxx advanced Arm®-based 32 MCUs but can't seem to locate the factory default values for the FLASH_OPTR register for the STM32WBA65. Unliked the solution from this thread, where the RM0440's Option Bytes Descriptions section indicates ST Production Value, the RM0515's Option Bytes Descriptions section starting on page 206 doesn't contain the factory production value. Am I missing this information elsewhere in the RM0515 or STM32WBA65RI datasheet? Thanks and Best Regards,-Eric

Hello everyone, I’m working on a project to interface an OV5640 camera module with an STM32H743 MCU via the DCMI interface. I’ve set up the STM32H743 in CubeMX and generated a basic project, but I’m looking for supporting documents, example projects, or reference drivers to help with the integration. Specifically, I am looking for guidance on: OV5640 initialization sequence (XCLK, SCCB/I2C configuration, reset/power-down sequence) Recommended CubeMX DCMI + DMA settings for QVGA RGB565 capture Memory placement for DMA frame buffers (AXI SRAM vs DTCM vs SDRAM) Minimal working register tables to enable QVGA or VGA output Any ST or community examples of STM32H7 + OV5640 projects   I understand DCMI + DMA basics, but I am aware that OV5640 requires stricter timing and more complex initialization. Any pointers to example projects, application notes, or reference drivers would be extremely helpful.   Thank you in advance!

Split from this thread for a new question. Thank you. I've changed the programmer, and it now programmed without errors. I however get a Hard Fault, sitting in HardFault_Handler(), as soon as I run. It happens before the code gets to main(). It also does not look like it is matching symbols to files correctly, because it is not showing code. I did check that Load Symbols is checked in debugger settings. Can this HardFault be related, or should I start new post to help with that?

I have been using Scool together with Keil for years, but last tuesday after I started my PC and a win11 update was installed, I started Scool but got this error: "The PC/SC access cannot be enabled for the reader (driver not installed?) SdtReaderDllLoader Function name:ENABLE_PCSC_ACCESSParameter 1:SCtool Virtual Reader" When trying to update driver in Device Manager, I get code 31. (Well known win error code it seems, and I've tried all sugested solutions from AI and others without success.)My HW card readers also failed, but I managed to find and install newer drivers for them from the internet, so they are running again, only Virtual SCtool drivers I can't find, so the question is, are there any new win11 drivers for SCtool? (My present SCtool Virtual Driver is version 1.1.0.0) Helpdesk sugested I tried to install Scool on a new PC win11 25H2, and drivers worked fine on that. (My present PC is version win11 23H2, and my collegue has exact same PC and win version, where dr

Post moved from this thread. @ STTwo-32 I am using the same STM32H755ZIQ board and facing the same issue where the target is not detected by ST-Link after uploading the program.This is the code link: https://github.com/kavyammengineer/stm32debug/tree/main/led_on_offThe code works correctly on the Nucleo-H755ZIQ board, but when I upload it to my customized board, the target gets stuck and is no longer detected by ST-Link.this is my sysclk 64Mhz 

Hi,Since we haven’t received the datasheet yet, we’d like to confirm the following information:If the receiver side (RX) uses the STWLC89 15 W solution, what is the corresponding 15 W transmitter (TX) model?Which Qi standards are supported by STWLC89? (Qi 2.1 or ....)

Hello everyone,MCU in use: STM32H745XI (dual-core, Bootloader v9.1, CubeIDE 1.16.1, HAL v1.11.3, CubeProgrammer v2.17.0)Hardware status: BOOT0 HIGH works perfectly, I can access the system bootloader over USART1 (PA9/PA10), and program via UART. Hardware is validated and all connections are good. PB15/PB14 pins are floating, not connected anywhere.My need:I want to jump from user application (C code only, no BOOT0 pin) to the internal ROM system bootloader for firmware update purposes, so that I can upload new firmware over UART (using CubeProgrammer or similar), and then return to normal application on the next reset.Here are the methods I have tried (none worked):Set MSP to 0x1FF09800, jump to 0x1FF09804 (function pointer), disable all interrupts (NVIC->ICER), set PRIMASK/FAULTMASK, disable and invalidate caches (SCB), disable SysTick, deinit all peripherals (HAL_DeInit, RCC_DeInit, etc.).Disable MPU/SAU regions (including secure/privileged regions).Put all GPIOs (including used U

Title edited to correct part number: it is a Geehy APM32F103CBT6 - not an STM32.See this post.Hi everyone,I am working on a project using the STM32F103CB MCU and implementing Standby (low-power) mode in the firmware. Development is done using Arduino IDE v2.3.2. I want the standby mode to be implemented to reduce the current consumption since my device is battery-operated. Problem OverviewThe firmware flow is as follows:On power-up, setup() runs.In loop(), if the reset reason is a power-on reset, the device enters Standby mode.The MCU wakes up from Standby via an interrupt on PA0 (Wakeup Pin).Execution flow and timing are monitored using the Serial Monitor.With the same firmware and library versions, I am observing different behaviour on two PCBs that:Have identical schematicsAre manufactured by the same vendorObserved BehaviorWithout Standby mode implemented, both PCBs behave correctly.With Standby mode enabled:Serial prints before entering Standby appear corr

Hello,I am trying to integrate an STSAFE-A110 chip into my product for keys/data securely storage.The communication with the chip works fine (approved by simple command as echo or generate_random).So I tried to generate a key in a local envelope key slot (first step of command flow in the "Local envelope wrapping/unwrapping" process). For that I queried the STSAFE-A110 to randomly generate a local envelope key in slot #0 and #1, using the STSAFEA_CMD_GENERATE_KEY (0x11) command.> 11 07 00 00 AF C1> 11 07 01 00 B6 19The chip answers OK as status code (correct crc) but I missed to keep data.But when I query the STSAFE-A110 to retrieve local envelope keys information (slot number, presence & key length), I get a key presence flag to 1 but with zeroed key length for the 2 slots.> 14 07 89 09< 00 00 09 02 00 01 00 01 01 00 FC 88status=OK(0x00)slot_nb=2Slot #0:- key_presence=1- key_length=0Slot #1:- key_presence=1- key_length=0How is it possible?Unable afterwards to gene

Hi,We are trying to make use of the ethernet interface in this fashion:- The board is a custom one with a soldered module from Karo, the qsmp-2550, that includes an stm32mp255fa.- The eth2 is connected to a PHY (TI DP83869HM) in RGMII.- The PHY is then configured to output Base100-FX to an SFP cage.- There is no CLK125, we use ck_ker_eth2 configured at 125Mhz (confirmed in /sys/kernel/debug/clk/stm32_clk_summary), we use the `st,ext-phyclk` DT property.The PHY is reachable via mdio using the CLI from mdio-tools and seem to be working as intended.We checked that the PHY sends the correct clock, the RX one, with a scope: it does.Then when enabling the link using `ip link set up eth0` we are greeted with:```root@qsmp-2550:~# ip link set up eth0[ 16.583371] stm32-dwmac 482d0000.eth2 eth0: Register MEM_TYPE_PAGE_POOL RxQ-0[ 16.586971] stm32-dwmac 482d0000.eth2 eth0: Register MEM_TYPE_PAGE_POOL RxQ-1[ 17.123948] stm32-dwmac 482d0000.eth2 eth0: PHY [stmmac-1:00] driver [TI DP83869] (irq=

I just like to configure the ISM330DHCX for vibration measurement. Is that an example or a sample code(using its C driver ) of it somewhere. Please give me a pointer. Thanks.

In AN2606 Rev 69, the STM32WBA6x system bootloader section describes the UART interface as USART3, but there appear to be errors:1. Inconsistency within the same entry:The TX pin description mixes USART2 and USART3 in the same sentence:USART3_TX pin Output PA12 pin: USART2 in transmission mode. Kept in reset configuration until 0x7F detected on USART_RX.While the RX pin description correctly uses USART3:USART3_RX pin Input PA11 pin: USART3 in reception mode. Used in alternate push-pull, pull-up mode.2. PA11/PA12 are assigned to USART2, not USART3:According to the STM32WBA62 datasheet, PA11 and PA12 are mapped to USART2 (USART2_RX / USART2_TX), not USART3.Question:Does the STM32WBA6x system bootloader actually use USART2 on PA11/PA12? It seems the document should read USART2 throughout, and the current "USART3" label is an error.Could ST please clarify and correct this in the next revision of AN2606?Environment:- Document: AN2606 Rev 69- MCU: STM32WBA62CGU6- Section: STM32WBA6x boo

Hi, I'm developing a project for STM32N657X0HxQ MCU and I need to run a NN model on it. I installed the 10.2.0 package for X-CUBE-AI and I've selected Core for Artificial Intelligence X-CUBE-AI in the Software Packs component selector. However, whatever Device Application I select, I always get when I'm on the Configuration Tab in Pinout & Configuration "Warning: This peripheral has no parameters to be configured" and I cannot upload my NN model, even when Artificial Intelligence X-CUCE-AI checkbox has been selected.I'm using the 6.16.1 Version of STM32CubeMX.Thank you for the cooperation

In section 19.6.2 LCD frame control register (LCD_FCR) of the STM32U0 RM0503 Reference Manual, the examples provided for PS and DIV initially count up in decimal, but finish in binary. This looks like an accident and is confusing to the reader. https://www.st.com/resource/en/reference_manual/rm0503-stm32u0-series-advanced-armbased-32bit-mcus-stmicroelectronics.pdfAll other examples further down in section 19.6.2 correctly count up in binary and do not mix in decimal numbers:  

helloDescription:I'm currently working with the STM32U585 and encountered an issue related to USART3Most of the time the code works fine, but it occasionally gets trapped in HAL_UART_IRQHandlerI am using the DMA Receiver Timeout (RTO) and DMA TX, may code is:void uart_tx_complete_cb(UART_HandleTypeDef *huart) { if (...) HAL_UART_Transmit_DMA(huart, buf, len); } void uart_rx_error_cb(UART_HandleTypeDef *huart) { HAL_UART_AbortReceive(huart); if (huart->ErrorCode & HAL_UART_ERROR_RTO) { ... } HAL_UART_Receive_DMA(huart, rx_buf, rx_buf_len); } HAL_UART_RegisterCallback(&huart3, HAL_UART_ERROR_CB_ID, uart_rx_error_cb); HAL_UART_ReceiverTimeout_Config(&huart3, 100); HAL_UART_EnableReceiverTimeout(&huart3); HAL_UART_Receive_DMA(&TD_UART_HANDLE, rx_buf, rx_buf_len); HAL_UART_RegisterCallback(&huart3, HAL_UART_TX_COMPLETE_CB_ID, uart_tx_complete_cb); When the issue occurs, I found that the TC (Transmission Complete) flag is not being cleared:an

HiMAC BOOK PRO is using apple silicon(arm), i downloaded STM32CubeCLT-mac, but it seems installation is not sucessful, maybe it because it's x86/amd64 version.Do ST have plan to release STM32CubeCLT apple silicon version? ThanksPeter