STM32 MCUs

I'm working with the STM32U385/375 for a project, and have started my investigation into how to convert it to a secure root of trust application by working with the OEMiROT examples.In stock form it works well. The provisioning works, the update over the y-modem link works just fine, etc. However, I want to build a combined binary and not deal with separate non-secure and secure binaries to apply for an update.Accordingly, I changed MCUBOOT_APP_IMAGE_NUMBER in OEMiROT_Boot/Inc/flash_layout.h from 2 to 1, like so:#define MCUBOOT_APP_IMAGE_NUMBER 1 /* 1: S application only if FLASH_NS_PARTITION_SIZE = 0 , else S and NS application binaries assembled in one single image. 2: Two separated images for S and NS application binaries. */The build works fine, the first part of the provisioning script works fine, the appropriate value is updated in appli_flash_layout.h, and the programming begins. However, it fails with this error:========== Error while executing "Programming the option bytes and

Hi All,Please could somebody offer some words of wisdom to resolve the apparent ambiguity in the C0 datasheet, which on the one hand states that once IWDG is started it cannot be stopped, yet on the other hand offers a IWDG_STDBY bit in the OPTION registers to allow it to be stopped during Standby. The latter does not appear to work, since my system wakes itself after the prescribed watchdog period, so it seems like the first statement is the correct one.Since the watchdog definitely CAN be stopped during debug if DBG_IWDG_STOP is set, there is clearly a mechanism by which it can be stopped under certain circumstances, suggesting the first statement is not correct, or at best is not the whole story.If it can't be stopped in Standby....a) what's the point of the IWDG_STDBY bit?b) how can I keep my system in Standby? I must have the watchdog running while awake. Many thanks

Hello,I stumbled over a weird problem when trying to debug Memory Protection Unit (MPU) settings which I want to document here in case any other people have the same issue:SetupThe used MCU is a STM32H7S3L8H6 on a STM32H7Rx/7Sx Nucleo-144 board (MB1737)Core frequency is 400 MHz.Enabling or disabling the cache has no impact on the problem.The code is executed from the internal flash, the stack and variables are placed on the DTCM.The debugger which I use is a Lauterbach CombiProbe 2 attached to a Power Debug Pro Ethernet. TRACE32 PowerView software version is R.2025.09.000186004.The executed software is a custom operating system which uses the MPU to prevent user-space threads from accessing memory regions not allocated to the threads. For this, one MPU region each is used for ROM, RAM and stack. The MPU is activated before the thread is executed and disabled afterwards. The background region is active.I have not tried to reproduce the error by using similar MCUs or other debu

Hello ,   I'm desining a PCB for the H7S7 and the PSRAM on the discovery board is : APS256XXN-OBR-BGBut it seems to be NRND.Can you confirm that this chip can be used in remplacement ?APS256XXN-OBx9https://www.apmemory.com/en/downloadFiles/0325021716tb786912Thanks

Hai All!I use 2 pieces of APS25608N PSRAM on OSPI bus with memory mapped mode. The MCU run at 1.8V, 160MHz system clock. Previously, I used APS12808N at 80MHz and 3.3V VDD without any issues.Currently, the PSRAMs run at 50MHz, but need to speed up to 100 or 160MHz.I thought the aps256's default settings should be good up to 100MHz, but they weren't.My working settings at 50MHz was ( relevant source in attachment): MR0: Fix type latency, latency code 5, and full strength (25 ohms).MR8: 32Byte Warp burst and without crossing.OSPI settings are:Dummy cycles:  Read = 8, Write = 4 hospi->Init.FifoThreshold = 4; hospi->Init.DualQuad = HAL_OSPI_DUALQUAD_DISABLE; hospi->Init.MemoryType = HAL_OSPI_MEMTYPE_APMEMORY; hospi->Init.DeviceSize = 25; hospi->Init.ChipSelectHighTime = 2; hospi->Init.FreeRunningClock = HAL_OSPI_FREERUNCLK_DISABLE; hospi->Init.ClockMode = HAL_OSPI_CLOCK_MODE_0; hospi->Init.WrapSize = HAL_OSPI_WRAP_NOT_SUPPORTED; hospi->Init

Hello,I have a issue with my STM32U5G9. It does not go into standby or shutdown mode. I want to achieve a wake-up by the power button of my device. The powerbutton is connected to PWR_WKUP6 (pin PB5). The button has a 100k pull-up. I verified the voltage levels with a scope (3.3V --> 0V).I checked with the examples in the STM32CubeU5 Github repo. This my code: void LowPower::EnterStandbyMode(void) { PrepareForLowPower(); __disable_irq(); for(int i = WWDG_IRQn; i <= JPEG_IRQn; i++) { NVIC_ClearPendingIRQ((IRQn_Type)i); } /* Enable WakeUp Pin PWR_WAKEUP_PIN6 connected to PB.5 */ HAL_PWR_EnableWakeUpPin(PWR_WAKEUP_PIN6_LOW_0); /* Clear all related wakeup flags*/ __HAL_PWR_CLEAR_FLAG(PWR_WAKEUP_FLAG6); HAL_DBGMCU_DisableDBGStandbyMode(); /* Enter the Standby mode */ HAL_PWR_EnterSTANDBYMode(); // If entry fails (e.g., if a debugger is attached), reset the system NVIC_SystemReset(); } I have a similar function for shutdown mode. I tried to clear all inte

Hello, I am having an SPI communication issue between an STM32H743BIT (SPI master) and a TI ADS7066IRTER ADC using SPI Mode 0 (CPOL=0, CPHA=0). I write a configuration register and immediately read it back, but the read value does not match what was written. The logic analyzer shows correct MOSI data, but MISO often returns 0xFF or 0x80, and the SPI decoder reports “Settings mismatch”. The write/read sequence is: SPI_ADS7066_writeSingleRegister(hADS7066, GENERAL_CFG_ADDRESS, OPMODE_CFG_CLK_DIV_6); if (SPI_ADS7066_readSingleRegister(hADS7066, GENERAL_CFG_ADDRESS) != OPMODE_CFG_CLK_DIV_6){Throw(EMBL_ERROR);} Write and read functions used: void SPI_ADS7066_writeSingleRegister(HANDLER hADS7066, uint8_t address, uint8_t data){PSPI_ADS7066DESC pADS7066Desc = (PSPI_ADS7066DESC)hADS7066;uint8_t dataTx[4] = {0};uint8_t numberOfBytes = SPI_CRC_ENABLED(pADS7066Desc) ? 4 : 3;EMBL_RETCODES ret; dataTx[0] = OPCODE_WREG;dataTx[1] = address;dataTx[2] = data;if (SPI_CRC_ENABLED(pADS7066Desc))dataTx[3]

Hi everyone,I’m experiencing a new issue with STM32CubeProgrammer and I’m wondering if anyone else has run into the same problem.Starting today, every time I try to select a file (for example, when choosing a .bin or .hex to flash), the program freezes as soon as the Windows File Explorer window opens. After a few seconds, the whole application closes without any error message.This has never happened before — the tool was working perfectly yesterday. The only thing that changed is that Windows installed an update overnight. Since then, STM32CubeProgrammer consistently crashes whenever it tries to open the file picker dialog.Has anyone seen this behavior after a recent Windows update?Any ideas on how to fix or work around it?Thanks in advance!

Hello everyone. I am trying to write a bootloader with STM32H750IBT6 and mt25ql512. I am trying to adapt the ExtMem_Boot example of STM32H750-DK to STM32H750IBT6 by modifying it, but I can't succeed. It doesn't make sense why STM32H750IBT6 does not work. In the software; JumpToApplication = (pFunction) (*(__IO uint32_t*) (APPLICATION_ADDRESS + 4)); __set_MSP(*(__IO uint32_t*) APPLICATION_ADDRESS); JumpToApplication(); but JumpToApplication(); enters HardFault and I get SCB->CFSR = 1025. Whatever I did, I was not successful. Attached I share the bootloader and application projects.   typedef void (*pFunction)(void); pFunction JumpToApplication; int main(void) { /* USER CODE BEGIN 1 */ CPU_CACHE_Enable(); /* USER CODE END 1 */ /* MPU Configuration--------------------------------------------------------*/ MPU_Config(); /* MCU Configuration--------------------------------------------------------*/ /* Reset of all peripherals, Initializes the Flash interface and

Hey guys, I'm looking for some suitable HexaSPI PSRAM and also the OctoSPI Flash for the STM32N645 board I am just building.. I cant find the parts used on the DK so do you have a list of supported memories? I need 256Mb PSRAM and will start with a 1Gb Flash as per the DK..  Richard

In the version of cube mx 6.4.0 you can set parameters and advanced parameters, but in the version of cube mx 6.16.1 you can only select the chip in the platform setting in the LWIP in middleware. I configured the firmware by installing the KSZ8863RLLI LAN driver in the STM32F407VET6 MCU. Cube IDE used version 1.18.1. Ping test went well in the version of cube mx 6.4.0 and it doesn't work in the version of cube mx 6.16.1. Is there a way to do it in the version of cube mx 6.16.1? What are the problems?The 00.ETH file is the firmware created in the version of cube mx 6.4.0 and the 02.ETH_16.1 file is the firmware created in the version of cube mx 6.16.1

Hello,Normally we use HAL_GetTick() in HAL driver.I want to use GetTick() in STM32 LL driver. How to get and use GetTick() in STM32 LL driver?

..

I was able to successfully build a TouchGFX demo project for a development board with clang+cmake using STM32CubeMX and STM32Cube plugin for VSCode. Although it required tweaking as it didn't work out of the box.Before ST officially supported clang I was able to build a simple blinky project using clang for arm and cmake and then analyze the code using clang-tidy. Now I want to use clang-tidy on the project, but I get several errorsIf I use clang-tidy from clang 1.19.5 I get the following issues:PS C:\LLVM_19.1.5\bin> ./clang-tidy.exe -p C:\TouchGFXProjects\MyApplication_24\build\Debug C:\TouchGFXProjects\MyApplication_24\Core\Src\main.c21 errors generated.Error while processing C:\TouchGFXProjects\MyApplication_24\Core\Src\main.c.error: too many errors emitted, stopping now [clang-diagnostic-error]error: unknown argument: '--multi-lib-config=C:\ST\STM32CubeCLT_1.19.0\st-arm-clang/multilib.gnu_tools_for_stm32.yaml' [clang-diagnostic-error]C:/TouchGFXProjects/MyApplication_24/cmake/s

When we want to debug only the M7 core, we use the following line and connect from VsCode:/c/ST/STM32CubeIDE_1.14.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_2.2.200.202505060755/tools/bin/ST-LINK_gdbserver.exe -cp '/c/ST/STM32CubeIDE_1.14.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.200.202503041107/tools/bin/' -d -e -v -m 0 -gBut the problem is that always the whole processor is reset because of the following as described in https://www.st.com/resource/en/user_manual/um2576-stm32cubeide-stlink-gdb-server-stmicroelectronics.pdf-g, --attach Attaches to the running target. Attach is aimed to be used to connect to a running program in the device without doing a reset or downloading a new program. [STM32_Programmer_CLI is always started with “mode=UR reset=hwRst” so that a device reset is done when loading a new program independent of this option. This guarantees that the flashing of the device is mad

Hello, I am planning to use the STM32G474RET6 and would like to confirm whether I can use the internal VREFBUF. This product's package is LQFP-64 and while reading the datasheet I noticed the note : ''The VREF+ pin is double-bonded with VDDA on some packages''. Could you verify whether the internal reference voltage can be used with this package?   Thanks.   

Hi everyone,I’ve spent the last few hours troubleshooting SWO (Serial Wire Output) trace within VS Code. I know this is a recurring issue in the forums, and while ST employees have mentioned they are working on a native implementation, I wanted to share a solid workaround that is currently working for me.It’s a bit tricky to set up the first time, but once you have your launch.json and OpenOCD paths configured correctly, it works great.The steps are:1. Install Cortex-Debug1. Run & Debug - > Add Configuration -> Modify the launch.json file2. launch.json:{ "version": "0.2.0", "configurations": [ { "name": "Cortex Debug", "type": "cortex-debug", "request": "launch", "servertype": "openocd", "serverpath": "C:/ST/STM32CubeIDE_2.0.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.openocd.win32_2.4.300.202509300731/tools/bin/openocd.exe", "cwd": "${workspaceFolder}", "executable": "${workspaceFolder}/build/Debug/project.elf", "device": "STM32L471RETx", "conf

STM32CubeMX generates by default a xx.ld file.It has copyrights from 2023. However, if I set "Apply Application Regions Settings to Linker File", it will generate a file with 2025 copyright, different template, also with XX.ld case, which on Linux, will give issues. Version 6.16.1

Hello,The datasheet and reference manual are missing information about the 4 KB Backup SRAM in the memory map.Where can I find details about it?We need to use this memory in both Secure and Non-Secure projects.Thank you. 

Hello there, I'm trying to create an external loader for my stm32h7s7-dk board via MCE.I followed this https://www.youtube.com/watch?v=JxhKmVUB2Ws&list=PLnMKNibPkDnFQXYK0ztHV9iMVS6EAtKpD&index=10 tutorial series and i check the github repo of this project. But the repo and the video series can be different. The instructor might add some new things. But the methodlogy cant work. Its really stupidly. The loader writes only 0x00 to flash for app size.Im adding my ss of the mem_copy, mem_write and mpu init codes here.   Please help me.

Hi,The external nor flash AT25XE321D is 32Mbits, support quad IO/XIP spi operation, max. 133MHz Freq. Std. JEDEC/SFDP. It is connected to STM32H7R7Z8J6 with with XSPI1 port-1 interface.I am using MX v6.116.1 to setup project for my board. By IDE v2.0.0, the project 'Boot' works from internal flash but it is failed to run 'Appli' from external AT25XE321D. And the project 'ExtMemLoader' is successfully built and deployed:File copied successfully under STM32CubeProgrammer.File copied successfully under STM32CubeIDEI tried STM32CubeProgrammer v2.21.0 to program the AT25XE321D with using the ExtMemLoader.stldr I just built, but failed too. "Error: Mass erase operation failed." See attached log for more logs.Back to my settings in MX:1) 100MHz XSPI1 clock source2) XSPI1 settings and GPIOsThere 4 memory types available and no 'custom' option. I pick the 'Macronix' as it is most close to AT25XE321D.3) ExtMemLoader settingsI also go through followings but did not help me to solve the probl

Hi,Can anyone point me in the direction of some more information about the custom timing under the I2C parameter settings?Are we modifying a specific register? or something else? Do each of the 8 bits do something different?  

Hi,I’m new to using the STM32 plugin for VS Code, as well as to VS Code itself. I’m currently using a J-Link programmer and have successfully set it up for debugging.Could you please advise on how to setup and configure VS Code and the STM32 plugin to flash firmware onto the microcontroller for a production release (i.e., programming the device not for/in debugging mode)?Thank you for your help.

Cube setting is OK!First run OK!if(HAL_OK != HAL_UART_Transmit(CO_INFO.channel, co_dma_tx_data, send_len, 0xFFFF))    {        DEBUG_PRINT("CO MODULE SEND DATA ERROR!!\r\n");    } Then setting OK!if(HAL_OK==HAL_UART_AbortReceive(CO_INFO.channel))if(HAL_OK==HAL_UARTEx_ReceiveToIdle_DMA(CO_INFO.channel,(uint8_t*)CO_INFO.RX.data,CO_UART_BUF_LENGTH)) But second run Fail !!if(HAL_OK != HAL_UART_Transmit(CO_INFO.channel, co_dma_tx_data, send_len, 0xFFFF)) trace HAL_UART_Transmit() functionif (huart->gState == HAL_UART_STATE_READY) the huart->gState value always 0x33so always return HAL_BUSY

Touchgfx 4.26.0 (and was same on 4.24.0) keyboard examples are the same resolution although there are (3) resolution of display resolution selectionsThey all display the keyboard size as approx. measured 43 mm (1.7 inches) X 33mm (1.3 inches) on a 5-inch display 800 X 480 resolution. To be usable we believe the keyboard needs to be about 1.5 to 2 times larger than present. (about 25% LARGER) See details in pdf attachment