Solved

I am using an stm32c011 MCU and want to put my device into standby mode and then periodically wake it up (every 30s or so).I have seen guides which use the RTC to do that, but cube mx doesn't show me a WakeUp option on my RTCAm I missing something or how am I supposed to continue from here?

Issue DescriptionI am experiencing a debugging issue with a project generated using TouchGFX Designer 4.24.2 for STM32H7B3I-DK, running on STM32CubeIDE 1.17.0. When I attempt to start debugging, I get the following error:   Failed to execute MI command: load C:\TouchGFXProjects\Test01\STM32CubeIDE\Debug\STM32CubeIDE.elf Error message from debugger back end: Load failed   Tests PerformedProject generated with TouchGFX 4.24: If I generate the project from TouchGFX and try to debug, I get the error mentioned above.The firmware loads correctly when flashed (.hex) manually via STM32CubeProgrammer, but the graphics appear corrupted.Empty STM32CubeIDE Project (No TouchGFX): If I create a new empty project for the STM32H7B3I-DK in STM32CubeIDE 1.17.0, the debugger works without any issues.Flashing and debugging function properly.ObservationsThe issue seems specific to projects generated using TouchGFX 4.24.2There might be a problem with memory configuration, linke

Hello, does anyone know how these two components (STM32H753XIH6 and STM32L4S7AII6) verify that the data in both internal and external memories(Ram, Rom, Nor and Nand) are not corrupted?Thanks for your help?

I am trying to use the built-in bootloader to flash a new firmware onto my MCU (STM32H723). Unfortunately, I cannot get any reaction from the MCU when trying to connect to it, and I am struggling to diagnose which step is going wrong.Short version of my steps:I pull BOOT0 high & NRST low (before this point, the MCU is running the normal firmware code)I release NRST, the MCU starts up again (attaching the ST-Link debugger, I confirmed that the code being execute is around 0x1FF00000, i.e. the MCU is somewhere in the bootloader code)I try to connect to the MCU using the STM32CubeProgrammer, set to UART (MCU pins PA9/PA10), baud 9600 (tried everything up to 115200), even parity, 8 data bits, 1 stop bit, flow control off. Whatever settings I try, I always get: Port configuration: parity = even, baudrate = 9600, data-bit = 8, stop-bit = 1.0, flow-control = off Timeout error occured while waiting for acknowledgement. Error: Activating device: KO. Please, verify the boot mode configu

 int loopTime = 0, maxLoopTime = 0;/* Private function prototypes -----------------------------------------------*/void SystemClock_Config(void); int main(void){   /* MCU Configuration--------------------------------------------------------*/   /* Reset of all peripherals, Initializes the Flash interface and the Systick. */  HAL_Init();   /* Configure the system clock */  SystemClock_Config();   /* Initialize all configured peripherals */  MX_GPIO_Init();  MX_DMA_Init();  MX_ADC1_Init();  MX_ADC2_Init();   MX_COMP1_Init();  MX_COMP2_Init();  MX_COMP4_Init();  MX_DAC3_Init();  MX_OPAMP1_Init();  MX_OPAMP2_Init();  MX_OPAMP3_Init();  MX_TIM1_Init();  MX_IWDG_Init();  MX_I2C3_Init();  /* USER CODE BEGIN 2 */  SystemManager_Start();  /* USER CODE END 2 */   /* Infinite loop */  /* USER CODE BEGIN WHILE */  while (1) 

openstLinux version: 1. en.SOURCES-stm32mp1-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.062. en.SDK-x86_64-stm32mp1-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06command: $ cd tf-a-stm32mp-v2.10.5-stm32mp-r1 $ export FIP_DEPLOYDIR_ROOT=$PWD/../../FIP_artifacts $ make -f $PWD/../Makefile.sdk TF_A_DEVICETREE=stm32mp157d-openedv DEPLOYDIR=$FIP_DEPLOYDIR_ROOT/arm-trusted-firmware stm32 -j2 $ cd optee-os-stm32mp-4.0.0-stm32mp-r1 $ export FIP_DEPLOYDIR_ROOT=$PWD/../../FIP_artifacts $ make -f $PWD/../Makefile.sdk CFG_EMBED_DTB_SOURCE_FILE=stm32mp157d-openedv DEPLOYDIR=$FIP_DEPLOYDIR_ROOT/optee optee -j2 $ cd u-boot-stm32mp-v2023.10-stm32mp-r1 $ make -f $PWD/../Makefile.sdk ARCH=arm CROSS_COMPILE=arm-ostl-linux-gnueabi- DEVICE_TREE=stm32mp157d-openedv all -j2  tvs: #Opt Id Name Type IP Offset Binary - 0x01 fsbl-boot Binary none 0x00000000 arm-trusted-firmware/tf-a-stm32mp157d-openedv-optee-programmer-usb.stm32 - 0x03 fip-boot FIP none 0x00000000 fip/fip-

I am working on a low power mode in a freeRTOS ble application. On a user request the device is to go into low power mode Stop2. In order to achieve the lowest power consumption ~2µA (stm32wb55) the ble activity has to be deactivated and the cpu1 & cpu2 has to go into lp-mode. In order to deactivate the ble antenna hci_reset is used. The low power mode implemented with hci_reset() works when tested on a Nucleo-STM32wb55 board based on the BLE_HeartRateFreeRTOS example. When I set it up on another project the hci_reset deletes all threads BLE threads (expected), but also deletes the working thread which means it doesn't excecute the the rest of the LP sequence. Here is the setup so far:  void LowPowerThread(void *argument) { HAL_EnableDBGStopMode(); for (;;) { osDelay(5000); HAL_GPIO_WritePin(GPIOD, GPIO_PIN_12, GPIO_PIN_RESET); /* Turn off DEBUG LED */ hci_reset(); /* resets the Link Layer on an LE Controller (ble_hci_le.h) */ LL_C2_PWR_S

I Enabled LWIP DEBUG options in CUBEMXin lwipopt.h  /* USER CODE BEGIN 1 */ #define LWIP_DEBUG 1 /* USER CODE END 1 */ in main.c  int __io_putchar(int ch) { ITM_SendChar(ch); return ch; }  But I am not getting anything in SWVITM Data Console

I am a novice, would like to ask if anyone will write a set of library files only for a single model of microcontroller because of the bloated official library files, is this common? For example, I was looking at the stm32h7 series recently, and the idea came to me because the layers of hal library nesting were very annoying.

Moved from MPUs forum.Hi, I looking to use the Nucleo WB55RG board to prototype some BLE firmware.I was looking through the examples in Cube MX but that particular board wasn't listed but there were a few similar choices, (see below). I was thinking the NUCLEO-WBAA55CG or the P-NUCLEO-WB55-NUCLEO?

I've already become familiar with the NUCLEO-C071 by creating some additional hardware (display, encoder, etc.). Now, I want to design a board using the smaller 32-pin version. However, in this smaller version, I find some differences that I don't know how to address (I have read the datasheet thoroughly multiple times but cannot find any answers):1) In the 64-pin version, pin 6 is the VBAT to connect a battery or a supercapacitor to maintain the RTC operation in case of power loss. Where has it gone in the 32-pin version?2) In the 64-pin version, both the quartz for the CPU and for the RTC can be mounted. Can you confirm that in the 32-pin version, the CPU only works without quartz? Even for managing USB?Thank you to anyone who can help me.Luca.

Dear Sir/Madam,Good day~I am trying to build a custom PCB with an STM32 chip.Currently, NUCLEO-F439ZI Demo Board is used, but only few pins/functions of the STM32F439ZI chip are necessary for me, the used pins shown as below (20 out of 114 pins are utilized):Then, I started to search appropriate chip by STM32 CubeMX, but the search list included more than 300 parts.Therefore, is it possible for you to provide suggestions for an alternative STM32 MCU that has the following features:1x CANBUS Interface1x SPI interface1x Ethernet Secondly, I would like to have the same debugging capabilities as the Nucleo boards which embed an ST-LINK. Hence, I would like to know more about the chip STM32F103CB which seems to be the one used to manage the ST-LINK on NUCLEO boards..May I confirm that if I purchase several STM32F103CB chips, in order to use them for ST-LINK purpose.Should I write program and flash it on each chip? Or each chip will be flashed in manufacture?I will be gra

I am using the STM32H562ZGT to generate center-aligned PWM with TIM1. Since I also want to use TIM1 for 20kHz periodic interrupts, I set the Period so that overflow/underflow occurs every 40kHz and set the Repetition Count to 1. This ensures that UEV occurs at the underflow timing every 20kHz, which I confirmed to be working as expected by combining an oscilloscope and GPIO Output. Here, I want to set the center alignment of the PWM to High based on the overflow timing (which is offset by 40kHz from the above interrupt) rather than the underflow timing. However, when I used PWM mode 2 and observed the PWM output on the oscilloscope, the High period was 0.6-0.7 microseconds earlier than expected. For example, with TIM1 generating 40kHz using 6249 counts at 250MHz, if I specify CH1 to be active at 3124 counts or more, the time from the underflow interrupt to PWM active was 11.8 microseconds. Ideally, this should be around 12.5 microseconds, which is almost 50% Duty. If you have any insig

Hi, We are trying to write some key values directly into a particular address of NVM from STM32Cubeprogrammer, but rest of the sector are also getting erased. Is there any way to prevent it? Tested with Cubeprogrammer CLI also, but facing the same issue.

I'm trying to convert the BirdNET-Analyzer (https://github.com/kahst/BirdNET-Analyzer/tree/main) model to run on a STM32U5A5. However, both the TFLite and STM32Cube.AI MCU Runtime fail.The TFLite runtime fails with: Operator REDUCE_MIN not supported The STM32Cube.AI MCU Runtime fails with: INTERNAL ERROR: Invalid size_splits configuration: [1 1 0] As I'm by no means a ML expert, I was wondering how to fix these conversion issues. I've tried to convert the TF SavedModel (.pb) to a .tflite model with the TFLiteConverter in python with the following enabled:  converter.target_spec.supported_ops = [tf.lite.OpsSet.TFLITE_BUILTINS]  However, this gives no warning and converts the model with a REDUCE_MIN operation.  I haven't been able to find any information to mitigate the STM32Cube.AI MCU error.  I'm on the latest STM32Cube.AI package in CubeIDE (v10.0.0) and Tensorflow V2.18.0. Any help is very appreciated!

Hello,I am trying to setup CANbus on the STM32MP157f-dk2 board, but I am unable to get any CAN interface to appear. I have installed the STM32MP1 OpenSTLinux Developer-Package onto the board, and I am using an SN65HVD230 transceiver.First I tried enabling pins PB12 and PB13 for FDCAN2, and connecting the transceiver to GPIO pins 10 and 36 on the board.For device tree configuration, I generated a device tree source file with STM32CubeMX and copied the pinctrl and m_can2 bindings from the generated file into "stm32mp157f-dk2.dts" located in the kernel sources. I then compiled the device tree using "make ARCH=arm dtbs". I then copy stm32mp157f-dk2.dtb to the board.I attached the exact dts file I am using.For driver configuration, I believe the BOSCH M_CAN driver is enabled by default, so I did not change anything in Menuconfig. Although I doubled checked that the selections were correct.  The can0 interface does not appear as an available network interface:root@stm32mp1:~# ls /s

Hello.I would like to request MTBF data for STUSB4700QTR at the request of the client company.I would appreciate it if you could reply.

need to know dev board for the STM32L552RET6TR. Also what is the specific part number used on this dev board.

Hello, I have a question regarding write access to a PSRAM connected via XSPI in memory mapped mode on a STM32H7RS. I do not completely understand if having the PSRAM memory mapped makes it available to the ECU as if it is internal RAM, meaning that it can be used to perform read and write operation of any size. Reading some docs (e.g. the reference manual), it seems that every aspect of PSRAM management in memory mapped mode is handled automatically by the MCU configuring parameters like the CSBOUND chip select bound. But looking at the code samples (such as this one https://github.com/STMicroelectronics/STM32CubeH7RS/blob/d06484d3e19c7d6fc963bbec5d754637f237c1ed/Projects/STM32H7S78-DK/Examples/XSPI/XSPI_PSRAM_MemoryMapped/Boot/Src/main.c#L200), it looks that the user must take into consideration aspects like page crossing and write time as indicated by the comment     /* In memory-mapped mode, not possible to check if the memory is ready after the programming. So a d

Hello,I am using the Nucleo-STM32F411RE development board and require support for cryptographic functions, particularly ECC NIST P-256, MAC, etc, for my development use cases.To achieve this, I downloaded the X-CUBE-CRYPTOLIB v4.3.0 package as it was mentioned in the product brief. However, I could not find any example projects specifically for the STM32F4 series.I also attempted to modify examples from other STM32 series, but I encountered faults and was unable to successfully run the code.Could anyone provide a working example for the STM32F4 series, or share a step-by-step user guide? As I am new to STM32 MCU boards, this has been quite time-consuming, and any guidance would be greatly appreciated.Thank you for your help!Best regards,Akash M

I am interfacing a 5V PWM signal with an STM32F030K6T6 MCU using PB0. According to the datasheet this pin is 5V Tolerant. In the past, regardless of a pin's "tolerance" to 5V I have always used a level shifter to change this 5V signal to a 3.3V signal before it gets to the MCU; "Just to be safe". This application I am trying to limit the number of parts on the PCB for both size and cost reasons. Testing on a Nucleo board seems to work and the MCU seems to tolerate this well, but for long term use in the field is it better to run this signal through a level shifter or does it not matter since the pin is "5V Tolerant"?

HiCan you tell me how I can calculate a value for ARR for timer 2(32bit timer) and timer3(16bit timer)I am using STM32F407 APB1 timer clock is 12MHz prescaler is 6

Hello,I am trying flash my STM32F746G Discovery board with new code from Linux. I run into this issue after running "dmesg -w": "can't set config #1, error -32". ST-Link is not being detected by either STMCubeIDE and STMCubeProgrammer. Has anyone run into this issue before?Furthermore, I had code flashed to the Discovery board that had a screen show, but I am met with a black screen when I connect it to power. The LED next to the ST-Link flashes red. I've also tried changing my debugger from ST-Link to SEGGER, but I met with the error "Could not determine GDB version using command: arm-none-eabi-gdb --version," and I am currently looking into this. I'm hoping that this is not a board issue but rather a software issue, but at this point it seems like this may be a board issue.Regardless, has anyone had any issues like this, and can provide any tips on what to do from here?

Are there any plans to have a video tutorial on the biosensor eval board?  (ST1VAFE3BX)? I connected it to MEMS Studio via the MKI109V3.  I'm experimenting with the "Features Demo" but it's not behaving as I expect.  Perhaps there's documentation about what I should be expecting in the MEMS Studio somewhere that I'm missing? 

I am using Mems-Studio for my FSM project. I am testing the state machine, and everything is working fine; I can see interrupts. However, in the debug tab, when debug mode is enabled, the table does not compile, and I cannot observe the program's behavior. I used LSB data as shown in the examples for unico gui