STM32 MCUs

Hello all,I have a custom board using an stm32h747bit6. I am able to flash it and it works exactly as intended, but if I power cycle it then it stops working?  If I flash it and then reset the chip it still works fine.I tried some debugging, I configured the error handler to toggle a gpio pin on / off but it doesn't do that, the voltage just sits at ~0.8v after I power cycle it? Any ideas?

Upgraded to v2.  I know this is a general question and I can elaborate but I'm having issues with my project NOT finding files.  First, has there been some change in the formatting for the entries in the Include portion of the project properties, General, Paths and Symbols...?  I'm doing a project where the paths are provided in an .xml file to be imported.  Most of it works but it appears some random files are not found.  I say random because if I fix one, two or more files are not found.  There must be some formatting issue OR maybe I'm not clear of the ORDER of the includes that may make a difference.  I've gotten the errors to drop from 15 down to 2, then fixing those 2 then results in 5 more.  I'm doing something incorrectly and not recognizing the problem, most likely.   Any suggestions would help. Thanks, Tony

Suppose I want to implement firmware for STM32U3 without TZ enabled and without the use of GTZC, then I could mostly use the MPU_NS and the TZ-Aware peripheral protection (EXTI, FLASH, RCC, PWR, GPDMA, SYSCFG, RTC & TAMP).   My goal is to limit unprivileged code execution to main FLASH, no SRAM, no OCTOSPI NOR/PSRAM.   The problem is now the ICACHE. Is there a way to force it to be privileged only ?   If not, assuming that I am allowing only unprivileged execution access via MPU_NS to the main FLASH (0x08000000 - (0x08000000 + size of flash)), could the remapping feature of the ICACHE be used to map say SRAM into this region and somehow unprivileged execution access this way ?   The docs are unclear there. The remap mechanism is described as a generic mechanism, not limited to any subset of the 0x00000000 - 0x1fffffff address space. Which means that in theory one could replace the mapping at 0x08000000 to say the SRAM1 base address.   - Thomas  

I'm a novice to ESP32 programming and LoRa, and I'm finding myself stuck with simple interfacing.I have a L073RZ connected to a Semtech SX1280 Evaluation Board, but I don't have a display attached to it (didn't come with one). I'm wondering how I can connect the ESP32 to my PC to control the SX1280. I'm trying to use the LoRa for its ranging abilities.I can't seem to find any firmware for the L073RZ+SX1280 combo, on either Semtech or NUCLEO.

Hello,   I have a board STM32F746G-DISCO from Farnell and I noticed that stm32cubeprogrammer is not showing the correct target board information. I have tried different version of stm32cubeprogrammer using different PC (2.15.0 due to usage of Windows 7) and 2.22.0 on my laptop and both are showing the target board as the discontinued STM32F7508-DK. The board system information appears to be showing correct information on its screen when it is being powered up but not in stm32cubeprogrammer and it also appears that the PC is detecting the device with removable storage for STM32F746G-DISCO DIS_F750N8, hinting of the discontinued board name which is very similar to STM32F746G-DISCO . I tried to reload the demo example to the board and it seems fine. The board appears to be a CU4 version board [not exactly sure there is any relation to that]. Is there anyway for the stm32cubeprogrammer to display the correct board information? Thank you for your attention to this matter.   Best r

tl;dr - HAL_UART_Receive_XXX, HAL_UART_Transmit_XXX == happiness; HAL_UART_Transmit_XXX, HAL_UART_Receive_XXX == misery.  The call to HAL_UART_Receive_XXX causes the transmission started by HAL_UART_Transmit_XXX to stall in both interrupt and DMA modes.Longer story:This affects both interrupt-driven and DMA operation, which is why I've added the DMA label.I am using FreeRTOS, and implementing a serial protocol that, while practically half-duplex in behavior, is written in a full-duplex form.  What I mean is the protocol doesn't really expect both sides to be transmitting at the same time, but the code isn't written to prevent it.  Theoretically parts of the protocol could overlap.The typical behavior for a transmission is to first call HAL_UART_Receive_DMA(..) to prime the receiver for a response, and then call HAL_UART_Transmit_DMA(..) to send a message.When the calls occur in that order, everything works perfectly.Unfortunately, sometimes the task responsible for

Problem:HAL_FLASHEx_Erase returns error 0x20000, and HAL_FLASH_Program does return HAL_OK but does not actually write any data to the flash.Goal: Erase and install new firmware on flash on its own inside the bootloader.I am developing a bootloader for the STM32H533RET6. I have TrustZone enabled, and configured the secure and non-secure regions. I am trying to erase and write to the non-secure part of the flash, from the bootloader which is secure (and separate from the actual application). I have disabled any write protection that I am aware of inside the option bytes. I also use the Memory Management Tool inside CubeMX to configure the secure and non-secure regions. For the non-secure region of the flash I have set "Access Permissions" to "RW by any privilege level". I do have a Flash watermark set on bank 1 but this does not cover any of the non-secure flash regions. No watermark is set on bank 2. Below is the code I use to erase and write to a sector on the flash:uint32_t Erase

Hi,I wanted to use an external voltage reference of +2.048V on the Nucleo Board. To do so I removed SB57 as dictated in UM1724 document: SB57 (VDDA/VREF+)ON VDDA/VREF+ on STM32 is connected to VDD.OFF VDDA/VREF+ on STM32 is not connected to VDD and can be provided frompin 8 of CN5 (Used for external VREF+ provided by ARDUINO® shield) The Absolute Maximum Ratings for STM32F072xB (table 21) give the following:VDD–VDDA Allowed voltage difference for VDD > VDDA - 0.4 V Does this mean I am bound to a 3.3V reference and can not use lower voltages? On Arduino boards these normally accept other voltages.

I would like to ask if there has been any change in the screen printing of STM32L433RCT6 from Taiwan, as the Z next to the ARM in the first line is not close, while the Z next to the ARM in China is close. As shown in the following figure.

Hello, While working with STM32F446RET6, I encountered a problem with I2C1. When using HAL_I2C_Mem_Read_IT(), an error occasionally occurs in the form of sending 0x00 instead of the address with the read bit after Repeated Start. The error seems to only occur with O3 optimization. I2C Configuration: NVIC Configuration: Only TIM1 update interrupt (TIM10 not used), DMA1 stream2 (SPI3_RX) and DMA1 stream5 (SPI3_TX) have higher priority than I2C1. Here is an example of a correct signal: The signal with error and I2C_Flush_DR() looks like this: static void I2C_Flush_DR(I2C_HandleTypeDef *hi2c) { /* Write a dummy data in DR to clear TXE flag */ if (__HAL_I2C_GET_FLAG(hi2c, I2C_FLAG_TXE) != RESET) { hi2c->Instance->DR = 0x00U; } } The signal and I2C_Flush_DR() looks li

Hi,Ref.manual (RM0477 Rev 8) in chapter 32.3.3 PSSI clock saysIn case when PSSI transmitting data, then RDY pin is input.Datasheet (DS14360 Rev 2) shows setup and hold time of RDY pin (input) referenced to rising edge as well as data pins (outputs).I think that's a contradiction. So how is it really and to which edge do RDY setup and hold times relate ?Thanks,Michal Dudka

Hi,I am using the following environment and found two bugs.OS : Ubuntu 20.04 LTSSTM32CubeMX : 6.15.0Toolchain / IDE : CMakeBoard : NUCLEO-H563ZIBug 1 : After reconfiguring the memory address and size with Memory Management Tool following code generation, the .ld file does not follow the configuration.This bug can be reproduced by following the steps below:Configure the FLASH region on MMT. Generated code and .ld filesUpdate the FLASH configuration on MMT. (e.g. change the start address of the FLASH region)Re-generated code and .ld files Bug 2 : The vector table offset value is not updated from 0x00U even if the ISR vector checkbox is enabled and the start address of the FLASH region is changed from 0x08000000The VECT_TAB_OFFSET value in system_stm32h5xx.c is not updated after generating code. I think this value should be updated according to FLASH region configuration./************************* Miscellaneous Configuration ************************/ /*!< Uncomment the f

I have successfully run the USB HS Mass storage on a new project without the use of freertos and touchgfx , But when the touchgfx code  for STM32H750B-DK is modified to run the code I am getting hard faultsstatic uint8_t usb_done = 0; extern ApplicationTypeDef Appli_state; extern USBH_HandleTypeDef hUsbHostHS; extern FATFS USBHFatFS; extern char USBHPath[4]; void Debug_Print(char *str) { HAL_UART_Transmit(&huart4, (uint8_t*)str, strlen(str), 100); } static uint8_t file_written = 0; void StartDefaultTask(void *argument) { Debug_Print("Task Started\r\n"); for(;;) { USBH_Process(&hUsbHostHS); if (Appli_state == APPLICATION_READY && file_written == 0) { Debug_Print("USB Detected\r\n"); if (USBH_MSC_IsReady(&hUsbHostHS)) { Debug_Print("MSC Ready\r\n"); FRESULT res; FIL file; UINT bw; /* Mount USB */ Debug_Print("Mounting...\r\n"); res = f_mount(&USBHFatFS, USBHPath, 1); if (res == FR_OK) { Debug_Print("Mount OK\r\n"); /* Create

Hello everyone,I am working with the NUCLEO-H723ZG board and attempting to establish Ethernet communication using TCP/IP. The firmware was built and flashed successfully using STM32CubeIDE version 1.19.0.However, I am facing issues with basic network connectivity. Below are the details of my setup and observations:Setup DetailsBoard: NUCLEO-H723ZGIDE: STM32CubeIDE v1.19.0Ethernet stack: LwIPPHY interface: RMIIFlashing tool: ST-LINK (onboard)Test performed: Ping test from PCObserved BehaviorThe Ethernet port LEDs (orange and green) remain solid ON after connecting the Ethernet cable.Ping requests consistently fail (Request timed out).No response is received from the board.Troubleshooting Already PerformedTested both Static IP and Dynamic IP (DHCP) configurations.Verified IP address, subnet mask, and gateway settings.Tried multiple Ethernet cables to rule out cable-related issues.Rebuilt and reflashed the project multiple times.Verified that the firmware flashes successfully and runs wit

Hi everybody,I'm learning to use the ADC in a STM32F411CEU in Continuous Mode and Single Conversion with Polling. When the code is downloaded to the MCU everything runs ok (I mean, when the MCU runs by itself without any ST-Link connected).The problem appears when I try to execute the code in a debugging session. The first time the function HAL_ADC_PollForConversion() is called, the result is HAL_OK, but in the next iterations the functions doesn't return HAL_OK anymore.I know, I know, with Continuous Mode I should be using DMA. But I'm trying to learn the different operation modes (single conversion, scan mode, polling, DMA, etc.)One thing I've found is that if I set the ADC parameter End Of Conversion Selection = EOC flag at the end of all conversions instead of End Of Conversion Selection = EOC flag at the end of single channel conversion , then the function HAL_ADC_PollForConversion() works ok in all the iterations when debugging. Can anybody explain m

Hello everyone,I am currently working on a project using the STM32F030C, and I have a question regarding the GPIO speed configuration (slew rate) for SPI pins.Here is my setup:MCU: STM32F030CInterface: SPI (configured as Slave)SPI Clock Frequency: 13.5 MHzTo keep EMI (Electromagnetic Interference) emissions as low as possible, I was considering setting the GPIO output speed for the SPI pins (specifically MISO, since the MCU is the slave) to GPIO_Speed_Level_Low.However, according to the datasheet (see attached screenshot), the "Low" speed setting is specified for a maximum frequency of 2 MHz.My questions are:Is it practically possible to run a 13.5 MHz SPI signal with the GPIO speed set to Low, despite the datasheet specs?Does this pose a high risk of corrupted/poor communication due to the slew rate being too slow (e.g., degraded signal integrity, failing to meet setup/hold times for the master)?Has anyone here tried this approach to reduce EMI at similar frequencies, or is it strictl

I am trying to create a simple UDP server using the NUCLEO-H743ZI2 board. I will port this to a similar microcontroller in the same family (STM32H750B) once I get it working. I am able to build the example code from this repository: https://github.com/stm32-hotspot/STM32H7-LwIP-Examples/tree/main/STM32H743_Nucleo_ETHIt successfully responds to pings and shows up in my router device list. I used:STM32CubeIDE Version: 1.17.0 STM32Cube FW_H7 Version 1.12.1.Following the instructions in the README, I attempted to build the application from scratch on the NUCLEO board, but I haven't been able to get it to respond to a ping despite a few days of troubleshooting. Can someone tell me if there is something wrong with my configuration file? 

Hi, two years ago I posted this thread:Solved: How to set "Don't fragment" flag LWIP short TCP pa... - STMicroelectronics CommunityNow I just was reviewing it for another application that truly needed to send more data and was not allowed to wait 50ms for every sent packet.Final root cause explanationThe 415-byte packets were being ACKed after ~40–50 ms because I was only sending one TCP segment at a time and waiting for it to be acknowledged within my application code, before sending the next one.This behavior is due to the TCP Delayed ACK algorithm implemented by Windows. When Windows receives a single TCP segment smaller than the MSS, it does not immediately send an ACK. Instead, it waits approximately 40–50 ms before acknowledging it.This behavior is described in RFC 1122, section 4.2.3.2 ("When to Send an ACK Segment"), which explains that a TCP implementation may delay sending an ACK in order to reduce protocol overhead.If a second TCP segment is received before the delayed ACK t

When using a STM32H757, with external QSPI, on an STM32H757I-EVAL, I am experiencing some programming issues when programming an .elf file with sections pointing to external QSPI. I am using the ST External Loader for MT25TL01G_STM32H747I-EVAL. Programming does work successfully, but on newer versions of cube programmer, there are warnings about 32 byte alignment, and then verification fails. The addresses mentioned are in AXI SRAM, and are .bss sections, which are marked NOLOAD, so it's confusing why that memory is trying to be programmed and this error is coming up in the first place. Manually setting the ALIGN markers in the linker file to be 32 instead of 4 does seem to get rid of the warning, and fix the issue. I've seen this issue on with versions 2.19 and 2.21 Is this a known issue? I haven't seen this issue with 2.17. Attached are logs files with the warnings and errors. Thanks for the help!

Controller: STM32F303ZEWritten a function to read ROM memory as belowvoid ServiceROMRead(tst_ServiceDataset* ptrService){// Variable holds ROM addressDWORD ROMAdd = DIAG_ZERO;// Flag represents JUP service trigger state.RFJupExeFlag = TRUE;// Address from where the data needs to be readROMAdd = ptrService->DataAddr;//Check for the EEPROM addressif((ROMAdd > ROM_ENDADD)) //ROM_ENDADD is 0x0807AFFF{// wrong addressptrService->State = WRONG_DATA;//Indicator for wrong address passed}else{ptrService->ptrData = (BYTE *) ptrService->DataAddr;}}When I pass ptrService->DataAddr as 0x8000020 or 0x8000080 to the above function ServiceROMRead from my application it is sometimes leads to a system resetApplication is placed at 0x08003000 to 0x0807AFFFBootloader is placed at 0x08000000 to 0x08002FFF1. Why is the controller resetting when I try to read ROM from address 0x8000020 or 0x8000080?2. Will trying to read data from address 0x8000020 or 0x8000080

HelloI have a STM32H7R3V8T6 and want to use a few peripherals and GPIOs. However, I don't manage to see an output with my analyzer. The peripherals themselves seem to work: An XSPI receive for example does receive some dummy bytes and takes exactly the required time for the transfer (measured with the cycle counter), but the pins do not show anything.I reduced my code and came up with this simple demonstration of how I initialize a GPIO:int main(void) { SystemCoreClockUpdate(); HAL_Init(); SystemClock_Config(); __HAL_RCC_GPIOB_CLK_ENABLE(); GPIO_InitTypeDef GPIO_InitStruct = {0}; GPIO_InitStruct.Pin = GPIO_PIN_12; GPIO_InitStruct.Mode = GPIO_MODE_OUTPUT_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_LOW; HAL_GPIO_Init(GPIOB, &GPIO_InitStruct); while (1) { HAL_GPIO_TogglePin(GPIOB, 12); HAL_Delay(10); } }The debugger shows that I reach the loop. The registers of the peripheral seem to be correct, but the pin doesn't toggle. This als

There is a problem with STM32 signing tool version 2.21.0. When header version is 2.3 and alignment flag is used, then image length in header is greater by the alignment byte count.To reproduce:Create dummy.bin that is filled with 256 bytes of FF's. For example with HxD tool.Sign it with no keys:STM32_SigningTool_CLI.exe -bin dummy.bin --type fsbl --no-keys --option-flags 0x80000000 --output signed.bin --dump-header signed.bin --header-version 2.3 --alignView the signed.bin with hex viewer (e.g. HxD) at offset 0x6C which is Image length by UM3234 rev 2:It is 0x2C0 = 704. This is 448 bytes more than original 256 bytes.When removing --align flag from signing call, the length becomes correct, but this image is not bootable anymore because STM32N6 Boot ROM expects FSBL image start address to be aligned to 0x400.I want to use this length field to check during OTA that FSBL upgrade file size and checksum are correct before programming it into Flash. But I wonder how does N6 Boot ROM treat th

I have created a UI in touchgfx designer, after I opened CubeMX and based .ioc file from touchgfx designer generate codes for stm32n6.Now I want to build these codes in Cube IDE but get this Error .   Errors occurred during the build.Errors running builder 'CDT Builder' on project 'STM32N6570-DK-FreeRTOS_Appli'.Cannot invoke "com.st.stm32cube.common.mx.registry.IIdeHelper.getRootProject(org.eclipse.core.resources.IProject)" because the return value of "com.st.stm32cube.common.mx.registry.MxRegistry.getIdeHelper()" is null  

HI, I am using STM32H745BIT6 ST controller in my custom board.Configured in Direct SMPS mode. When the board is powered on the VCAP voltage is 1.2V and settling at 1V as expected when we try to flash the program to controller the voltage is same, but when we are trying to enter into debug mode the voltage is dipping from 1V to 0.6V and after 5uS its coming back to 1.2V.( Image is attached for reference)Due to this issue, I am not able to enter to debug mode controller is getting disconnected and showing the pop-up as TARGET IS LOST. I have taken all the precautions mentioned in datasheet and reference manual.1) Shorting all three VCAP pins.2) Connected two 2.2uF capacitor near to the pins.3) Even tried with higher capacitor value.4) Checked the shorts in the pins and board with the help of multimeter.5) The PWR_CR3 register is also set to Direct SMPS mode and verified the last 4 bits as 0100.6) Verified in the IOC that it is configured to Direct SMPS

Hi ST Community,I try to write the OTP Memory on NUCLEO-H563ZI Board with STM_Programmer_CLI (Debian Linux).With STM32CubeProgrammer GUI application I can access OTP memory (beginning 0x08FF_F000).When I try to access the otp memory via CLI:./STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -otp displI receive:Error: OTP programming commands are not supported with STLINK interfaces for this device. With lsusb I can see my STLINK-V3:Bus 001 Device 011: ID 0483:xxxx STMicroelectronics STLINK-V3 But also with the command (port=usb1 or usb0):./STM32_Programmer_CLI -c port=usb1 mode=HOTPLUG -otp displI receive:Error: Target device not found.Establishing connection with the device failed. Do you have any ideas/hints what I am mistaking here?Thanks in advance!