STM32 MCUs

Unable to run the program in the MCU. When I try to execute the program in my Nucleof401re board, The IDE says it is not able to detect the board. I'm literally struck here just to blink an led. I kindly appreciate any possible solutions. But do explain it in simple terms as I'm new to this kind of stuffs.  

Hello,I'm working on a comprehensive project where I need to implement low-power modes without using a sequencer. However, nothing works after MX_APPE_Init. How can I deinit it?I am using MAC 802.15.4 /* Init code for STM32_WPAN */ MX_APPE_Init(NULL); HAL_Delay(5000); EnterRTCStandbyMode(10000); /* Infinite loop */ /* USER CODE BEGIN WHILE */ while (1) { /* USER CODE END WHILE */ MX_APPE_Process(); /* USER CODE BEGIN 3 */ tagReadResponseSend(); } To summarize, I want to know how to deinit MX_APPE_Init. Yes, there's a sequencer, and it works perfectly, but I want to disable MX_APPE_Init and use EnterRTCStandbyMode for sleep modes.

Hi Everyone,I'm using the P-NUCLEO-WB55 board and seeing an an issue when attempting an OTA firmware using the STBLESensorClassic mobile app running on iOS device. Execution is blocked waiting for the "FLASH_FLAG_CFGBSY"  to clear in FLASH_WaitForLastOperation() in stm32wbxx_hal_flash.c. Please see screenshot below of call stack and location.  SetupCubeIDE v1.14.1STM32Cube_FW_WB_V1.21.0ST BLE Sensor Classic 4.20.1 BackgroundIf I use the out of the box OTA example "BLE_Ota" on the P-NUCLEO-WB55 board the OTA update works fine.  However, this example uses the sequencer which is not representative of our end application. We are using FreeRTOS in our end application. In an effort to create an application that is somewhat representative of our end application I've combined/merged the "BLE_Ota" & "BLE_HeartRateFreeRTOS" examples into a single project. With this merged project running on the P-NUCLEO-WB55 board the issue is reproducible. I've attached th

G'day Brains Trust,Does anyone know where ST record the export classification for their products?Specifically looking for the ECCN for STM32G474RET3.RegardsGTC-BH

I have flash update operations working fine on an STM32U535 with 512kB flash, but am getting an error on a 256kB device.  Driving into the debugger, I find it coming out of the FLASH_WaitForLastOperation HAL routine, specifically after: reg_sr = IS_FLASH_SECURE_OPERATION() ? &(FLASH->SECSR) : &(FLASH_NS->NSSR) which returns 0b10001000, which winds up being the FLASH_NSSR_PROGERR, and FLASH_NSSR_PGSERR.  I am not sure why.   Code segment enclosed here: const uint32_t NVRAM = 0x0803E000; FLASH_EraseInitTypeDef EraseInitStruct = {0}; HAL_StatusTypeDef hfError; uint32_t PAGEError = 0; // To hold any page error code uint32_t pageNumber = (NVRAM - 0x08000000) / 0x2000; uint32_t progAddress = NVRAM; uint64_t *pSource = (uint64_t)&memory[0x1800]; // 1800 uint32_t quadWordCount = 0xFF / 16; if (HAL_FLASH_Unlock() != HAL_OK) { printf("Cannot erase FLASH memory.\n\r"); // Handle error, e.g., print error message return; } // Clear

I am using stm32cubeprg-win64-v2-21, and I am experiencing an error.After launching the program and clicking Open File, the Open File window appears briefly, and then the program closes unexpectedly.I uninstalled it and tried using a previous version of STM32CubeProgrammer, but the same issue occurs. Rebooting the laptop does not resolve the problem either.  I have captured a video of the issue and attached it.

hi, i trying DTLS on netXduomy goal is TLS and DLTS running independently (STM32H5 is server, PC is client) so i success mutual TLS(Ver 1.3) but failed DTLS runningi'm in situation that DTLS connection is completed at client but server is not answer about client hello(3 time ignored) i check variables and found handler pointer is null - active_dtls_session->nx_secure_dtls_tls_session.nx_secure_session_cipher_handler_server == nullso i guess DTLS initialization was not completed but i don't know what do i do i attach my code and variables please help me thank you DTLS_SESSION_CONFIG g_dtls_session_table[1]; #pragma data_alignment=8 NX_SECURE_DTLS_SERVER dtls_server; typedef struct { NX_SECURE_DTLS_SESSION sessions[1]; ULONG padding; UCHAR metadata[32*1024]; } DTLS_MEMORY_BLOCK; NX_SECURE_DTLS_SESSION *active_dtls_session = NULL; UCHAR dtls_reassembly_buffer[32*1024]; UCHAR dtls_client_cert_buffer[20*1024]; #pragma data_alignment=8 DTLS_MEMORY_B

..

Dear All,I am working on a project based on the STM32U5G9NJH6Q MCU.I have made a project using CubeMX v6.14. I am working on CubeIDE and I am using TouchGFX 4.25.0 for the GUI of my application.I have used the STM32U5G9-DK2 to verify my GUI design, using hardware accelerated vector fonts. On the DK everything seems to be working fine.But on the custom PCB I am working on, I see this:The larger font on the screen is a vector font, whereas the smaller fonts are bitmap, so I am using a mix of the 2.If I do not use hardware accelerated vectors (use software accelerated vectors instead) then the problem disappears, but the GUI is slow. My linker script looks like this:  /* ****************************************************************************** ** ** @file : LinkerScript.ld ** ** @author : Auto-generated by STM32CubeIDE ** ** @brief : Linker script for STM32U5G9NJHxQ Device from STM32U5 series ** 4096KBytes FLASH ** 3008KBytes RAM ** ** Set heap size, stack size and stack lo

I am developing a Battery Management System (BMS) for a hybrid inverter solar panel system. I am using the ADBMS1818 IC as the battery management chip from Analog Devices. Currently, I am looking for a suitable MCU for my system. I found that the CYT2B7 MCU from Cypress Infineon fits my system well. However, during the development process, I need to use an MCU from STMicroelectronics. Could you recommend a series that meets my needs? Below are the specifications of the CYT2B7 Thank you for your assistance.

I tried to use the internal watchdog IWDG and WWDG) on an STM32L433It worked fine until the device went into low power modes, standby and shutdown.Because the watchdogs still runs during low power modes, but as the prcoessor is not running the watchdog times out and keeps resetting the processor.So then I looked at using an external watchdog (STWD100) which can be disabled when in low power mode.  I wrote a post about the topic here...https://community.st.com/t5/others-stm32-mcus-related/how-to-interface-external-watchdog-stwd100-with-stm32/m-p/879006#M9433But a comment was made that "If you can enable and disable the watchdog, wild-running code can as well, and you cannot really rely on the watchdog"So how should a watchdog (internal or external) be handled in low power modes ?Surely you dont want to keep waking the processor every few milliseconds just to reset the watchdog timer, as the defies the point of being in low power mode to save battery power ?I was told that

I have an STM32H7S78-DK and I have used TouchGFX to create a GUI just fine. I am currently trying to use the fanout or the Arduino headers to communicate through SPI or UART to another board.  The first thing I tried was using the SPI through the fanout board as it's soldered for the SPI4 by default with the fanout board.  I used the female headers on the fanout board that corresponded with MOSI, MISO, etc for the SPI.  I configured SPI4 in STMCubeMX and generated the code in STMCubeIDE.  I just tried to send an array with Hello in the array in the form of hex values.  However, I saw nothing coming out of the pins when I hooked it up to a logic analyzer. I then thought maybe I was using the wrong header and soldered some male pins next to the female pins which said CN12 which corresponded to what it said in the fanout boards documentation. I thought maybe the microbus female headers were not the right ones to use.  Generated all the code and tried again an

Hello Support Team,Good day,For product development, we chose the STM32U585 family, a trust zone-based MCU. Consequently, we are having a problem when we generate projects using Cube Ide.I've listed the actions we're taking below.Selected IC STM32U585AII6Enabled TrustzoneEnabled X-CUBE-FREERTOS and active for non-secure regionGenerate a project codeCompile code as per generated toolWhen I compiled code we have seen below compilation error undefined reference to `SecureContext_SaveContext' portasm.c undefined reference to `SecureContext_AllocateContext' port.c undefined reference to `SecureContext_LoadContext' undefined reference to `SecureContext_Init'I've included a screenshot of the error for debugging. 

Hi everyone,I think I’ve messed up my NUCLEO-H755ZIQ board. A few days ago, I accidentally unplugged the board while an active debug session was running. Since then, the board "dies" every time I power it off.To get it back to a working state, I have to follow this tedious process every single time:Set Boot0 to VCC.Connect via STM32CubeProgrammer (Power Down mode).Perform a Full Mass Erase.Disconnect and set Boot0 back to GND.Connect again and flash a simple .elf file (a basic SPI project that toggles an LED) just to verify it's alive.After this, I can debug normally in CubeIDE—until I power cycle the board again.This was manageable until I started working on a Bootloader project. Today, it took me all morning to recover the board because the bootloader logic seems to interfere with my "recovery" steps.I’ve already tried messing with Option Bytes and performing several mass erases, but the issue persists. It feels like the flash or the option bytes are stuck in a state that prevents a

I’m working on an STM32H7R7 project using SDMMC1 + FreeRTOS (CMSIS-RTOS v2) + FatFs, all generated with STM32CubeMX.I’m facing an issue where f_mount(opt=0) works, but the system blocks inside f_open() and never returns, so the return value cannot be checked.A key aspect of the problem is that the behavior depends on how the device is started:After flashing the firmware with a debugger connected and running immediately, the system behaves differently.After a cold power-up (power removed and re-applied, no debugger connected), the same binary consistently freezes when reaching f_open().In both cases:The code is identicalThe clock configuration and FreeRTOS setup are unchangedNo additional initialization is performed when the debugger is attachedThis suggests a timing-, initialization-, or peripheral-state-related issue that manifests only on a true power-on reset and not after a debugger-initiated reset.Additional observations:f_mount(&SDFatFs, "0:", 1) initially caused a block, but

STM32F401 (Blackpill) – 2.4s Drift in 30 Minutes Between Two Identical Boards Using TIM2 (HSI Clock)I am working on time synchronization between two identical Blackpill STM32F401CCU6 boards.Both boards:Use internal HSI oscillatorSame firmwareSame clock configurationTIM2 configured as 1 MHz free-running counter (1 µs resolution)32-bit counter (auto-reload = 0xFFFFFFFF)Clock configuration:HSI ONPLL enabled (HSI → PLL → SYSCLK)SYSCLK = 32 MHzTIM2 prescaler = 31 → 1 MHz timer tickInitializationBoth boards started in STANDALONE modeBoth boards waited for button interruptThe board which gets interrupt became MASTERSynchronization MethodOne board acts as MASTEROther board acts as SLAVECommunication via UART (115200 baud)Master sends a 5-byte sync packet:0xAA + 4-byte counter valueSlave receives and sets:htim2.Instance->CNT = received_counter; UART disabled and connection removedInitial sync works correctly.ProblemAfter synchronization:Drift increases over timeAfter 30 minutes → ~2400 ms di

Hi, I'm starting to play with the SBSFU examples provided by ST. I'm trying to build the SBSFU (mcuboot based) example for the STM32L5 which can be found in the STM32SecuWS provided here . I'm stuck trying to build the TFM_SBSFU_boot (partial console output):arm-none-eabi-gcc "C:/STM32SecuWS/TFM/STM32Cube_FW_L5_V1.3.0/Projects/STM32L562E-DK/Applications/TFM/TFM_SBSFU_Boot/Src/low_level_com.c" -mcpu=cortex-m33 -g3 -DSTM32L562xx -DUSE_HAL_DRIVER -DNDEBUG -DTFM_DEV_MODE '-DMCUBOOT_TARGET_CONFIG=<flash_layout.h>' '-DMBEDTLS_CONFIG_FILE=<config-boot.h>' -DMCUBOOT_DOUBLE_SIGN_VERIF -DBL2 -c -I../../Inc -I../../../../../../../Drivers/CMSIS/Include -I../../../../../../../Drivers/CMSIS/Device/ST/STM32L5xx/Include -I../../../../../../../Drivers/STM32L5xx_HAL_Driver/Inc -I../../../../../../../Middlewares/Third_Party/trustedfirmware -I../../../../../../../Middlewares/Third_Party/trustedfirmware/platform/ext/common -I../../../../../../../Middlewares/Third_Party/trust

Hi Community,I am porting STM32Cube_FW_U5_V1.8.0\Projects\B-U585I-IOT02A\Applications\SBSFU example to be used with USB port for firmware upgrade instead of Uart. I use B-U585I-IOT02A board with U585. Because of some requirements I need to use bare metal USB stack and I successfully ported the classic STM one according to article How to use STMicroelectronics classic USB device middleware with new STM32 families . I have used it SBSFU example and the usb stack works fine when I use it in non secure environment and run Loader binary or Appli_NonSecure as separate application with TZEN=0 without bootloader - I was able successfully send fw image over usb using ymodem. But when I used it in full secure original setup as in the example, I mean TZEN=1, booting with bootloader, using Appli_Secure/Appli_NonSecure - I experienced board restarting when connecting board's USB to the PC - it looks like something goes wrong during USB enumeration process. I have checked that US

HiI am drawing a PCBA with STM32H7R3V8H6 but for the USB HS interface PHY its not clear which pins are USB differential D+ and D- data pins?krØystein

Hello, I am using the HAL for multi-master SMBUS operations on an STM32H753. I ran into a scenario in which the event handler interrupt function (I2C4_EV_IRQHandler() in my case) was repeatedly firing such that there was no CPU available for other code to run. It seems that the logic within HAL_SMBUS_EV_IRQHandler(), which the above function calls, may not be correctly identifying the source of the interrupt, and not clearing it. This code: /* SMBUS in mode Transmitter ---------------------------------------------------*/ if ((SMBUS_CHECK_IT_SOURCE(tmpcr1value, (SMBUS_IT_TCI | SMBUS_IT_STOPI | SMBUS_IT_NACKI | SMBUS_IT_TXI)) != RESET) && ((SMBUS_CHECK_FLAG(tmpisrvalue, SMBUS_FLAG_TXIS) != RESET) || (SMBUS_CHECK_FLAG(tmpisrvalue, SMBUS_FLAG_TCR) != RESET) || (SMBUS_CHECK_FLAG(tmpisrvalue, SMBUS_FLAG_TC) != RESET) || (SMBUS_CHECK_FLAG(tmpisrvalue, SMBUS_FLAG_STOPF) != RESET) || (SMBUS_CHECK_FLAG(tmpisrvalue, SMBUS_FLAG_AF) != RESET))) { calls SMBUS_CHECK_I

HiDo QUAD SPI require power on the VDDXSPI power pins?ADCs, what is the voltage reference buffer, VREF+ and VREF- , voltages? Can the internal reference buffer be used if VDDA is 3.3V and I want full scale 0-3.3V ADC conversion range?krØystein

The Reference Manual (RM0454) of the STM32G0B0 points to an old 2020 revision while on the website it shows 2025.I believe this is a mistake since there should be a newer revision of this RM with the fixed Flash section (STM32G0B0CE) unless ST only fixed the RM of the STM32G0B1.

Hey there community,As you can see I am trying to move the free Rtos and x-cube-st67w611 middle ware from the application context to the FSBL context, I am using the stm32n6 mcu series and MX 6.16.0 version.I failed to see the full message suggested by the MX tool, as to why this is, I also noticed that in the example projects the context is fixed to FSBL, hence doable. my intention is to develop in the FSBL content and latter migrate to the application content.Does any one have a idea of what I can do to?

Whenever I try to use the SFR view window, it consistently crashes the IDE. Completely hangs up, not responding to anything (e.g. resizing the window) anymore.. left it sit for 15min (way too long) no responsiveness.I can easily reproduce this by launching a debug session, and then e.g. trying to unfold "NVIC" item in the SFR listings. => IDE hangsAlso starting to type so I can narrow down the amount of entries in the panel => IDE hangsTyping "NVIC" somewhere else first, then copy-pasting it into the field (so it doesn't first go searching for everything with "N" in the name, and then having to read a few hundred registers) => IDE hangsI'm using STM32CubeIDE 1.13.0, installed last week. The target is a STM32U575 on a nucleo. None of my user code is running yet, because its still halted at the entry of main. I've not touched any of the debugger settings w.r.t. to the onboard STLink.OS is Manjaro Linux with all up to date packages.Please advice, as this makes developing for this

Inside Cube config, i do not get the other internal connected pins on pin 14, only PA8... in older versions it was available. The chip is STM32U031F8... What do i do wrong.. i need to use the uart_tx function on pin 14... Thank you  Old version from Cubeide... New version from Inet : 6.16.1