Solved

..

We have implemented a total of five push buttons—two connected to Port E and three connected to Port M. The GPIOs of Port E are functioning correctly. However, the GPIOs of the push buttons on Port M are not being detected properly by the MCU.Even when the switches are unpressed, the MCU is detecting a Pressed condition.PORT M GPIO Pin out: PM1, PM2, PM3.MCU part: #STM32H7R7L8H6HI have checked  push button from hardware side, its working fine.Attached example schematic snapshot of push button. Could you please advise if there are any specific settings or configurations required for Port M GPIO to function correctly?@Shubham Prakashpant BOHARAPI @Shailesh Patil @Krishan Kumar SOLANKI

Hi,I get this message when I open SPC5Studio: but I have already followed the istructions for Free Hightech license coping the new license in the requested folder.Does it means to have less functionalities with wizard to configure the MCU? 

Firstly, the installation process is pretty ugly and the documentation is very sparse.From the README.md file:This application runs from the external Flash memory (LwIP_TCP_Echo_Server Appli).It boots from internal Flash (Template_XIP_Boot) then jumps to the application code in external Flash.To configure STM32CubeIDE Debug Configuration, you must do the following : 1. Upload the template XIP2. Add the adequate external loader (MX25UW25645G_STM32H7S3L8-NUCLEO.stldr file) in Project->Debugger Configuration3. Add in the startup the template_XIP_Boot in Project->Debugger Configuration4. Move up the application in the startup Step 1, real helpful, what an ordeal.Step 2, could not find MX25UW25645G_STM32H7S3L8-NUCLEO.stldr used MX25UW25645G_NUCLEO-H7S3L8.stldr insteadEnvironment:STMCubeIDE V1.19.0STMCubeMX V6.15STMProgrammer V2.20.0ST-Link F/W V3J16M9 My problem:When I run the code in debugger mode, execution never gets out of Template_XIP_Boot.Ends up in error handler.

I can't find any example schematics for the stm32wba65ciWhere could I find them?

File: stm32u0xx_hal_gpio.c/** * @brief Lock GPIO Pins configuration registers. * @note The locked registers are GPIOx_MODER, GPIOx_OTYPER, GPIOx_OSPEEDR, * GPIOx_PUPDR, GPIOx_AFRL and GPIOx_AFRH. * @note The configuration of the locked GPIO pins can no longer be modified * until the next reset. * @PAram GPIOx where x can be (A..F) to select the GPIO peripheral for STM32U0xx family * @PAram GPIO_Pin specifies the port bits to be locked. * This parameter can be any combination of GPIO_Pin_x where x can be (0..15). * @retval None */ HAL_StatusTypeDef HAL_GPIO_LockPin(GPIO_TypeDef *GPIOx, uint16_t GPIO_Pin) {HAL_GPIO_LockPin() should return HAL_StatusTypeDef.But in Doxygen None 

Hi everyone :waving_hand:,I’m currently working on a bare-metal project using the STM32F4 Discovery (Disc1) board and developing my code purely with CMSIS header files (no HAL or CubeMX).I wanted to check if this board has any onboard MEMS sensors (like accelerometer or gyroscope) — similar to what some older STM32 Discovery boards include.If a MEMS sensor is present:What is the exact sensor part number?Which communication interface does it use (I2C/SPI)?Are there any reference manuals or example register-level code available to initialize and read data using CMSIS?If not available, could you suggest a good external MEMS sensor (like MPU6050 or LIS3DH) that works well with STM32F4 boards for motion or tilt detection?My goal is to implement tilt or motion detection completely in bare-metal C without HAL drivers.Any guidance, datasheets, or example code snippets would be really appreciated :folded_hands:Thanks in advance! 

Cube MX does not allow LWIP to be configured without the Ethernet controller enabled - for some strange reason. Any assistance would be appreciated.

Hello,I’m trying to setup the PSSI interface on the STM32H523RETx to transmit data. I cannot find how is the PSSI_PDCK configure. Neither in the clock tree nor in the RCC register the PSSI clock can be configured (except for enabling it). In RM0481 table 305 the AHB clock is listed for PSSI_HCLK, but how is PSSI_PDCK generated?Is it not possible to internally generate the clock? How is the requirement of AHB clock must be at least 2.5x PSSI_PDCK achieved?In CubeMX (v6.14.1) I also couldn’t find any parameters for the PSSI clock.Thanks!

 Hello everyone,I am using I2C to communicate between an STM32F411 Discovery Board and the on-board LSM303AGR sensor. I have already configured it for a 400Hz ODR, normal power mode, and am reading temperature values (around 25°C to 27°C).However, I am stuck on how to soft-reset the entire sensor. I tried to SET bit 5 in CFG_REG_A_MAG and adding a small delay, but this does not reset the values I configured in other registers. Those settings remain the same, no matter how many times I try to SET the reset bit.The registers only reset when I unplug and plug the power back in.Please help me.Thank you very much.bool LSM303AGR_softReset(const LSM303AGR_t* lsm303agrStruct){ uint8_t regVal = 0; if(!readMag(lsm303agrStruct, LSM303AGR_CFG_REG_A_MAG, &regVal)) return false; //Extract the current status bit-field and assign it to regVal /* Start to assign and write regVal to CFG_REG_A to start FULL CHIP RESET */ regVal |= (SET << REG_A_SOFT_RST_Pos); if(!writeMag(lsm303agrSt

Hi, I was trying to make the sensor sense slow rotation.I read the datasheet and I guess if I set HPM to work as normal mode, and High-pass filter for interrupt 1so CTRL_REG2 should have 0x81,Then I should read the REFERENCE (0x26) register, (according to the thread in here https://community.st.com/t5/mems-sensors/lis2dh12-measure-conversion/td-p/420708) My question is, is it even doable ? Can I sense slow rotations until it reaches some point ?Thanks in advance 

Hello,I am trying to get SWO output working in VSCode using the Cortex-Debug plugin (v1.12.1).My setup:Debugger: STLink V3-MINIEMCU: STM32H747IIT6IDE: VSCode with Cortex-DebugGDB Server: OpenOCDDebug config: Trace Asynchronous SW enabled in CubeMXWhen I run the project in STM32CubeIDE, the SWO output works as expected.However, in VSCode I don’t see any SWO output in the terminal.I overrode the write function like this:int _write(int file, char *ptr, int len) { int dataIdx; for (dataIdx = 0; dataIdx < len; dataIdx++) { ITM_SendChar(*ptr++); } return len; }My launch.json:{ "name": "CM7 SWO", "cwd": "${workspaceRoot}/CM7", "type": "cortex-debug", "executable": "build/Printf_CM7.elf", "request": "launch", "servertype": "openocd", "gdbPath": "/opt/ST/STM32CubeCLT_1.19.0/GNU-tools-for-STM32/bin/arm-none-eabi-gdb", "device": "STM32H747IITx", "svdFile": "/opt/ST/STM32CubeCLT_1.19.0/STMicroelectronics_CMSIS_SVD/STM32H747_CM7.svd", "configFiles": [ "interface/stlink.cfg", "ta

Hello everyone In my application using an STM32H7, I noticed that the VBAT pin, with VDD off, draws 1.9 mA. This is excessive current draw.I'm using a CR2032 battery in series with a 100R battery connected to the microcontroller's VBAT pin.What could be the cause?Is there any way to understand why it's drawing so much current?NB: The datasheet states that the RTC draws 225 nA at 1.2 V, including the LSE's power consumption. Thanks

I have spent about 1 day trying to get the latest pre-release version of the extension to install correctly. If only appears to be installing 2 of the bundled extensions, Memory Inspector and CMake Tools, out of the 15 extensions that are included in the bundle. No extension icon is appearing in the left panel and when I go to Settings/Extensions the extension is not listed.I've read another thread of someone reporting the same problem, but I could not determine a concrete solution.Is there a way to manually install this extension and the extensions in the bundle?

Thank you for your continued support.From your responses, I have made the following initialization procedure for ASM330LHH.POWER ONCTRL3_C <- 0x42(BDU,IF_INC)CTRL1_XL <- 0x9C(3333Hz,8G)CTRL2_G <- 0x92(3333Hz,125dps)INT1_CTRL <- 0x01(Accelerometer data-ready interrupt)Read STATUS_REG every 0.5ms to check if TDA is 1.Some units do not set TDA to 1. This is a problem.Is the ASM330LHH initialization procedure correct?Do I need to wait, etc.?

Hello everybody! I recently started experiencing weird, unstable behavior during debug on my Nucleo u575zi-q board. So, I don't use HAL, or any graphic programming, or any API, doing everything in pure C from scratch. The IDE I use is, of course, the STM32 CUBE. It is the Mac version, 1.19.0. When my project was simple, everything was okay; the ST-LINK debug worked great. At some point, though, the debug became unstable. Sometimes the debug freezes, but more often it somehow ends up doing more strange things. For example, I have an RTC module in my project, and in the code, I wait for the RSF flag:while(!(RTC->ICSR & RTC_ICSR_RSF)){};When I download the code to my NUCLEO board and run it, everything is fine. But when I debug the same code, press the "run" button, the debug gets frozen on waiting for this flag to be set, and it seems that the flag, for some reason, never sets! So the debug doesn't work. I turn off the debug session, and the code runs well again! Sometimes the boa

I am trying to load LwIP_TCP_Echo_Server (an example project created by STMicroelectronics) onto a Nucleo_H7S3L8 Evaluation Board (produced by STMicroelectronics) and it's crashing. I had some trouble getting the BootLoader to run through to the JumptoApp function (covered under a different post) and used a workaround fix it.I set a break point just before the jump and examined the App memory at 0x70000000 (memory mapped). It was all 0xFFFFFFFF. No wonder the code crashed. I used the STM Programmer, and the memory looked ok. Code at 0x70000000 looked like a vector table and definitely not 0xFFFFFFFF. I added the Template_XIP_Boot project to my build as described in the README.md.I really need to get this piece of ...    code to work. Like now. This stuff is basic startup operation. This is an ST example project on ST Nucleo hardware. What's going on? I've seen no other forum posts on my recent issues. Why is everyone else having fabulous success? Am I alone? What's wrong with

I'm trying to perform the first boot on the STM32MP257F-EV1 following this guide: STM32MP25 Evaluation boards - Starter Package.  I've connected the LCD screen to the board according to the instructions.The board is powered by USB-C on CN21, and the status LEDs are as follows:LD11 greenLD6 greenLD5 blinksI've tried to flash the microSD card (SANDISK 16GB) using both methods provided in the guide. 6.2. Image flashing ( STM32CubeProgrammer tool  DFU mode)I've followed all the steps and got the following messages: stm32mp2$ STM32_Programmer_CLI -l usb ------------------------------------------------------------------- STM32CubeProgrammer v2.17.0 ------------------------------------------------------------------- ===== DFU Interface ===== Total number of available STM32 device in DFU mode: 1 Device Index : USB1 USB Bus Number : 001 USB Address Number : 002 Product ID : DFU in HS Mode @Device ID /0x505, @Revision ID /0x100 Serial number : 00270

I am using LTDC for interfacing with a TFT LCD. The LCD is connected with 18 bit (RGB666) interface. I have selected the pixel format as RGB565, and I am using a frame buffer stored in the internal SRAM. The frame buffer has been populated with 16 bit RGB values. The problem is, I can only see the output when I enable the CLUT and populate the CLUT with RGB values. Otherwise, if CLUT is not enabled, I cannot see the output. As far as I know, CLUT is used in L8 pixel format, but for RGB565 CLUT is not used. I am confused about this situation. Any idea what may be happening here?

STM32H7 + SDIO + FATFS(use DMA template Disable) => works fine. I can read data from SD card without issue. STM32H7 + SDIO + FATFS(use DMA template Enable) => mount will fail The only difference is "use DMA template". Once this option is turned on, fatfs mount will fail...

Based on the information found in AN4286 rev 14, I am trying to command to bootloader to start executing the application.The setup is a H573 and a H563 connected over SPI @ 0.5 MHz. The 573 operates as SPI master, and the 563 as a slave. I know that the HW is fine as I have no problem with the communication (application to application) when booth are configured with BOOT0 = 0.Then I set BOOT0 = 1 on the 563, and tries the following code:void BootloaderTest(void) { clrEsbCsN; DelayUsBlocking(10); // Sync frame uart_printf("SEND SYNC 0x5A, RX: %.2X\r\n", SpiWriteEsb(0x5A)); DelayUsBlocking(10); // Get ACK. if (GetAck()) { // Send GO command. uart_printf("SEND SOF 0x5A, RX: %.2X\r\n", SpiWriteEsb(0x5A)); DelayUsBlocking(10); uart_printf("SEND CMD GO 0x21, RX: %.2X\r\n", SpiWriteEsb(0x21)); DelayUsBlocking(10); uart_printf("SEND CHKSUM, RX: %.2X\r\n", SpiWriteEsb(~0x21)); // single byte command, nothing to XOR. DelayUsBlocking(10); // Get ack of command. uart_printf(

I have a custom board with a STMU5F7VJT, programmed over SWD, with an on board MMC and a usb connector. I am trying to access the onboard MMC with FileX and ThreadX. Using USBX, I can access the MMC just fine, and even format it from my computer, so MMC, ThreadX and DMA should be working fine. When trying to format the MCU through FileX however it hard faults during the synchronization deep in the ThreadX stack when calling tx_semaphore get() in the auto generated macro FX_STM32_MMC_WRITE_CPLT_NOTIFY().Curiously, this hard fault only happens when the cpu is allowed to run. When manually stepping through, the hard fault never occurs. The hard fault is extremely cryptic. It fails within the function:VOID _tx_thread_system_suspend(TX_THREAD *thread_ptr) #ifndef TX_NOT_INTERRUPTABLE {At the line of the macro "#ifndef TX_NOT_INTERRUPTABLE before entering the function proper.I've increased the stack sizes/memory pool to a ludicrous amount, double checked memory alligned buffers and all

1. Problem DescriptionI am working on an STM32H7S3L8 Nucleo board and building a bare-metal project with the Mongoose networking library (no RTOS, no LwIP).The project compiles successfully after adjusting flash size in the linker script, but fails to load into the MCU via STM32CubeIDE or STM32CubeProgrammer.I consistently see this error:Error in final launch sequence: Failed to execute MI command: load ".../Mongoose_Webserver_Boot.elf" Error message from debugger back end: Load failed And from CubeProgrammer logs:Memory Programming ... File : Mongoose_Webserver_Boot.elf Size : 68.86 KB Address : 0x08000000 Download in Progress: Error: file size is bigger than the flash memory size. Error: failed to download Segment[0]Even though the ELF file size is only ~69 KB, CubeProgrammer reports it does not fit in flash.2. Development EnvironmentBoard: NUCLEO-H7S3L8 (STM32H7S3L8Hx)IDE: STM32CubeIDE 1.17.0Toolchain: GNU Tools for STM32 12.3.rel1Debugger: ST-LINK V3External libs: Mongoos

I am implementing a firmware-update mechanism on STM32H755 (Nucleo board, MCU rev U) in which the two flash banks are independent.  New firmware is flashed by erasing the "other" bank (which is always mapped at 0x0810 0000 and accessed with the ____2 register set, e.g. FLASH_CR2), then writing the candidate firmware image into that bank, verifying a SHA hash after programming, and finally toggling the SWAP_BANK bit in option bytes, performing an option-byte update, and software reset to boot into the new image.  This works, and I can perform one update after another, ping-ponging back and forth between the banks.  Note that the running application is always mapped at 0x0800 0000, is [much] less than 1 MByte, and never touches the other bank at 0x0810 0000 except to erase and program it when an update is requested.The issue I am having is that when the code runs in Bank 2 and an update commences, the bank erase of Bank 1 is stalling the CPU for several seconds.  The

Hi everyone,I'm a beginner when it comes to STM32 MPU, and from the very beginning I've had an issue with the HDMI output on my STM32MP257F-DK board, which I received from my university. Naturally, I wanted to start with the Starter Package to explore and see what the board can do (link to guide). I followed all the steps without any issues. After booting the board from flash memory, I was able to access the CLI via ST-LINK.Now I'm struggling with HDMI, which only shows a black screen. I can see that my monitor detects the board and establishes a proper connection using one of the supported modes (see weston.log at the end). I also went through this guide (How to display on HDMI) to make sure everything is set up correctly and that the HDMI mode matches between the monitor and the board.Has anyone experienced a similar issue? Or maybe I'm missing something? Any advice on how can I debug the issue further is welcome :)Thanks in advance! weston.logDate: 2024-02-27 UTC[19:02:43.