STM32 MCUs

Hello,the SPI does work with NSSP(Negative Slave Select Pulse-Mode), but it does not work if I disable NSSP. As someone pointed out the SPI NSS(P) may only work if the Pulldown of that pin is enabled, but I’m not 100% sure on that one, but it seems to wirk for NSSP-En that way. For NSSP-Disabled I could not get the SPI-Controller to control the NSS(CS).I observed two issues:1) On Reset the NSS(CS) is low and will stay low until the first SPI Transaction. I tried to set it via HAL_GPIO_WritePin( … , GPIO_PIN_SET); but that has no effect, maybe because the Pin is controlles by the SPI-HW.2) Is the serious issue is, if I disable the NSSP, the CS does not work at all.How can I make the Hardware NSS work with NSSP disabled?Thanks a lot, Best Regards, SeppelP.S.This is the Setup and Waverforms for the NSSP-Disabled, I have a 2s delay on startup, which you can see on the scope-pictures.: This is the setup for the NSSP Enabled, the same was used for NSSP-Disabled(only that NSSP was set to

I am trying to implement TFTP file transfer on my STM32 module (Nucleo-H723ZG). I have taken reference from:https://github.com/STMicroelectronics/STM32CubeF4/tree/master/Projects/STM324xG_EVAL/Applications/LwIP/LwIP_IAPhttps://github.com/JoeMerten/Stm32-Tools-Evaluation/tree/master/STM32Cube_FW_F4_V1.9.0/Projects/STM324xG_EVAL/Applications/LwIP/LwIP_TFTP_Server For file transfer I am using tftpd64 software. I used the software for PC-PC file transfer which were on the same local network and it was successful. But when I am trying to send file from PC-STM32 module I am only receiving write request from the client (PC). After that  I am suppose the get a block 0 acknowledgement from the server (STM32 module) which I am not receiving. I tried debugging the code but in the code the acknowledgement is being sent successfully. For more information:- my ethernet is up - I have successfully ping the IP address that I have assigned or configured for the module. - Moreover, I am using

I've read other posts and the relevant app notes about this and tried some testing on my side but still not finding an easy or even effective way to do this.I have a CubeIDE project built on a CubeMX ioc file for STM32G0B1KEU6 and want to change to STM32G0B1KCU6 (smaller flash). Same package, same core, same pinout, just smaller flash size. Should be easy.CubeIDE 2.1.0CubeMX 6.17.0I open the CubeIDE project and then the existing ioc file within that.I click Pinout -> List Pinout Compatible MCU's and select new the MCU. I click Import.It creates a new ioc file (instead of updating the existing file within this project which is what I actually want) and attempts to import all of the existing ioc project settings. It fails to import DAC and USB settings for some reason which I now need to go and manually edit and hope that everything else is correct. It is completely unclear what has and has not ported over successfully so I'll need to very carefully review everything. Now I

Hello, As part of a new project, I'd like to use DFU mode for programming my STM32F303VET6. I have a button that controls BOOT0. If the button is pressed during the microcontroller reset, there's no problem; I successfully enter DFU mode and can reprogram without any issues. I'd like to be able to perform this step without any physical intervention on the board, but rather by creating a 'jump' from my application to the internal ST Bootloader. My board is connected to the PC via a CDC connection. Using HyperTerminal, I send a command that calls a JumptoBootloader function. My function is as follows:   void JumpToBootloader(void) { // 1. Stop USB peripheral RCC->APB1ENR &= ~RCC_APB1ENR_USBEN; // Disable USB clock RCC->APB1RSTR |= RCC_APB1RSTR_USBRST; // Reset USB RCC->APB1RSTR &= ~RCC_APB1RSTR_USBRST; // 2. Put USB pins (PA11/PA12) in analog mode RCC->AHBENR |= RCC_AHBENR_GPIOAEN; GPIOA->MODER |= (3U << (11 * 2)) | (3U << (12 * 2)); // Ana

Hi there,I am currently trying to create a custom power board in the Board Designer software and I am running into issues. I am using the NUCLEO-G431RB as the control board. In the designer for my custom power board, I have configured pins PB4 (MR27), PC7 (MR19) and PB0 (ML34) as Phase Voltage Generation Pins using the configuration "Driving HighSidesAndOneEnable". When I then try to configure a project, in the project creation phase I get the error "DrivingHighSidesAndOneEnable: No timer matches all signals requirement". However according to CubeMX, on the STM32G431RBTX MCU, all those pins are connected to three TIM3 channels respectively. Not sure where I am wrong, any help would be appreciated thank you. Additional Info:Version: 6.4.1Tool: MCSDK - Board Designer/Project CreationHow to Recreate: 1. Open the Board Designer and try to create a power board2. Configure the Phase Voltage Generation pins as states above3. Configure the Current Sensing Hardware config with other a

Hi everyone,As part of one of my projects, I have to use an SD card to store my data. Since the final board has not yet been manufactured, I started developing my software on the STM32303E-EVAL evaluation kit.For reference, it uses the same microcontroller that will be on my own board.Back to the STM32303E-EVAL. When I received this board, the provided demo worked correctly (GUI display and so on).I wanted to test the examples dealing only with the SD card (FAT32 format), which are available in the repository:→ STM32Cube_FW_F3_V1.11.0\Projects\STM32303E_EVAL\Applications\FatFs\FatFs_uSDImported into CubeIDE, it does not compile, files are missing – in short, it is a mess.So I started over from scratch, installed AC6, opened the project, flashed it, started a debug session, and I get stuck in f_mount().The SD card is correctly inserted.Could you help me?Or, failing that, provide me with a working example?

Hi, I was just reading about the new STM32C5 processors. The press release states: Enhancements to the development ecosystem include a new STM32CubeMX flavor, STM32CubeMX2, which introduces a preview feature that allows faster access to reference code thereby accelerating development and easing code reuse. Also new in the STM32CubeC5 embedded software offer, the latest code-size optimized hardware abstraction layer (HAL2), gives access to all MCU features and allows more of the MCU’s memory to be used for application code. What is CubeMX2 and HAL2?   A

[PN]: EVSPIN32G4-DUAL[VERSION]: MCSDK 6.3.2[TOOL]: Firmware[DETAILS]:Hello,I am working on a dual-motor application using the EVSPIN32G4-DUAL board with MCSDK 6.3.2.I observe the following behavior:when both motors are running at the same time, the speed regulation is stablewhen only one motor is running, strong speed oscillations appearThis behavior is observed when running either motor alone. In other words, the issue does not seem to be linked to one specific motor channel.The motors are custom motors designed/manufactured by us, with the following configuration:5 pole pairsRs / Ls identified with the profilerHall phase shift = 121°Rotor angle measured using Hall sensorsPWM frequency = 16 kHzThe attached speed plot illustrates the issue:first phase: only one motor running → oscillations visiblemiddle phase: both motors running → stable behaviorlast phase: only one motor running again → oscillations visibleThe current regulator seems very stable, only the speed loop is going crazy wh

Hi,After updating to the latest VS Code extension pack v3.8, what is the recommended path for executing CMake commands from command line? I uninstalled the STM32CubeCLT since it's now bundled, perhaps this the wrong choice?I want to test running commands to upgrade our CI/CD pipelines to be up-to-date.  Also found following path which contains `cube.exe` as a CLI wrapper. My concern is setting an environment variable to a path with a version number (`/...-core-1.2.0-.../`) that ends up being a moving target.> `C:\Users\USERNAME\.vscode\extensions\stmicroelectronics.stm32cube-ide-core-1.2.0-win32-x64\resources\binaries\win32\x86_64`Any assistance would be greatly appreciated. 

I use touchgfx on u599 ,internal flash is 4MB.My project have 2.4M fonts and images,so I devide internal flash to two parts,like this:RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 2496KSRAM4 (xrw) : ORIGIN = 0x28000000, LENGTH = 16KFLASH (rx) : ORIGIN = 0x08000000, LENGTH = 1024KASSETSFLASH (rx) : ORIGIN = 0x08100000, LENGTH = 3096K because the assets are not changed everytime ,So I am thinking stop CUBEIDE to downloadASSETSFLASH and only download FLASH form 0x08000000. How can I do this ?

I'm using an STM32G0 with a 240 x 160 monochrome 1bpp SPI display. Is it possible to use the QR code component from the TouchGFX library?I'm using TouchGFX version 4.26.0.Many thanks!

The original question is here I too have experienced something like this with my STM32F407ZET controller. TCP Client mode was not working in IAR whereas it worked CubeIDE. Dont know the reason, but had to migrate my whole code to IDE.

Hi,is there any HW guidelines to configure a USB OTG port with STM32H563VIT6 with VBUS detection?

Hello.I recently experienced an unusual MCU Problem and need to analyze it. Please help me. The FW program download to the MCU is successful, but it does not operate after a reset. I performed a short circuit test after disconnecting the power(Battery)but even when measuring VCC-GND and GND-VCC at the power supply, a resistance value of approximately 500 ohms is detected. When I disconnect only the MCU from the PCB and re-measure, the 500 ohm value disappears from the PCBbut this value persists when measuring directly from the MCU pins. Can I conclude that the MCU is dead due to a power supply failure?And in what cases does this problem occur?

Hello,  Began learning STM32 MCUs with my Nucleo-H753ZI board and I think I found a bug. The IO configurator on CubeIDE thinks user LED2 is on PB7 and is blue coloured. I'll paste the code it generates below. But in fact, the user manual UM2407 says user LED2 is on PE1 and is yellow coloured, which is indeed correct. Generated code from CubeIDE for Nucleo-H753ZI:#define LED2_PIN GPIO_PIN_7 #define LED2_GPIO_PORT GPIOB Appears to be a bug that should be fixed in the BSP.

Hi Team,Could you please confirm whether the following SPI erratum is considered in HAL version 1.11? I am currently using an MCU with revision V.

Hello,We are currently working on STM32C542CCT6 from the STM32C5 series and developing custom Flash and Data Flash drivers.Issue 1 – Hard Fault when accessing FLASH_SIZEWhile executing code generated by STM32Cube, the following check causes the system to enter the Hard Fault handler:if (FLASH_ADDR < (FLASH_BASE + FLASH_SIZE)) /* Main User Flash */The FLASH_SIZE macro reads the value from the device information area. However, when the code attempts to access FLASH_SIZE, the system immediately enters the Hard Fault handler.If we manually hardcode the flash size value, the code works correctly.Our questions are:Is there any specific register configuration or initialization required before accessing FLASH_SIZE on this device?Is this region restricted due to Trust Zone or privileged access on STM32C5 devices?Issue 2 – NMI when reading Data FlashWe have enabled Data Flash by setting: EDATA_EN = 1We are trying to read from the Data Flash base address:0x09000000using a pointer-bas

New question split from this post.One additinal request: When checking if bootloader pin configuration has an impact on the real application it would be helpful to know the default level for output pins, likedoes the UART_TX pin drive active high or low?does the boot loader drive the SPI MISO output pin HI, LO or Z?is the CAN_TX pin drven HI or LOW?Thank you!

It seems that after I updated MacOS to Tahoe 26.2 the IDE does not show selected text if over multiples lines correctly. This is a nightmare to work with, as it does not show selected text and can make you delete (overwrite) lines while editing.Anyone else? Is there a setting to fix it?

Hello, I am using an STM32F407VGT6 board with the ST-LINK debugger.When I plug the USB cable into the board, the LD1 LED on the ST-LINK stays Green and does not turn Red. From what I understand: Green LED indicates that ST-LINK is powered and idle. Red LED should appear during debugging or when an error occurs. However, in my case the LED always remains Green. My questions: Why does LD1 remain Green when I connect the board? Under what conditions does LD1 turn Red? Does a constant Green LED indicate that the MCU is stuck (for example in HardFault or reset)? I am using STM32CubeIDE for programming and debugging. Any guidance would be appreciated. Thank you.

Hi,I have this toolchain and need to generate a SBOM:STM IDE v1.18STM IDE GNU Tools for STM32 13.3.Rel1STM32Cube FW_L4 V1.18.1, specified in `\*.ioc` fileSTM32_USB_Device_Library (v2.0_Cube)STM32CubeMX 6.14.0FreeRTOS (10.3.1)How could I turn this into a SBOM?I tried scanning the folder strucutre with syft but this did not work. I then tried to manually make a syft Json file, but when testing for vulnerabiliteies (like e.g. here ) i could not find them. I am not sure how to specify the above components, such that they get recognized by the automated search engine (Grype).I found a statement from ST, that SBOMs will be provided for their products, but I could not find said lists for my toolchain. Some repositories on the GitHub Repositores contain `sbom_cdx.json`. However, I struggle to connect my Toolchain components to the repositories on Github (there are over 700 and for example "stm32cubeIDE" returns 0). Any help is appreciated! Related Links:Wikip

Hi,When reviewing the descrption of MCU pins used by the integrated system bootloader, I came across several documentation bugs in the latest AN2606 (rev70). Inparticular, Table 164 lists:USART1_TX pin - PA9 pin: USART1 in transmission mode. Used in input no pull mode: Input mode for an output pin? Same issue with USART2 and USART3.SPI1_MOSI pin - PA7 pin: slave data input line, used in push-pull, pulldown mode: Input pin does not have push-pull mode.SPI1_NSS pin - PA4 pin: slave chip select pin used in push-pull, pulldown mode: NSS ist used as an input, so it does not have push-pull mode.Same issues with SPI2 descrpition.The same problems are in Table 166. I have not checked the tables for the other CPUs, but I suggest a review of the document might reveal more issues.RegardsNorbert Unterberg   

I am using stm32f407 and stm32wb series for sending the data usimg uart.first i send th data using the stm32wb uart to the stm32f407 uart the data is correctly sent.After receiving the data i will return the data back to the stm32wb from the stm32f407 but this time the data is corrupted.I am using the hal_uart_receiveto_idle and hal_uart_transmit_it to send and receive the data. I will share the code please review and tell me if i need to make any changes.

#ifdef HWVR_AC_CG_NOV25 #include "lpuart.h" #include "main.h" UART_HandleTypeDef hlpuart1; DMA_HandleTypeDef hdma_lpuart1_rx; DMA_HandleTypeDef hdma_lpuart1_tx; #define LPUART_RX_BUF_SIZE (uint8_t)1 static volatile uint8_t lpuart_rx_buffer[LPUART_RX_BUF_SIZE]; // Buffer for DMA reception #define LPUART_TX_BUF_SIZE (uint8_t)64 static volatile uint8_t lpuart_tx_string[LPUART_TX_BUF_SIZE]; static uint8_t lpuart_tx_string_size = 0; // Size of the lpuart_tx_string buffer #define LPUART_FLAG_RX_COMPLETE ((uint8_t)((uint8_t)1U<<(uint8_t)0U)) #define LPUART_FLAG_READY_TO_SEND ((uint8_t)((uint8_t)1U<<(uint8_t)1U)) #define LPUART_FLAG_TX_ONGOING ((uint8_t)((uint8_t)1U<<(uint8_t)2U)) static volatile uint8_t lpuart_flag = 0; void_const_uint8_t_p_callback_t lpuart_fill_callback = NULL; // Callback for the loop function void_void_callback_t lpuart_loop_callback = NULL; // Callback for the loop function static volatile uint32_t last_timestamp = 0; void HAL_UART_RxCp

After updating the STM32CubeG4 Firmware Package from version 1.6.1 to 1.6.2, I discovered a bug that causes incorrect deadtime prescaler settings for HRTIM when using the LL driver and CubeMX. As a result, the deadtime value can change to a fraction of the original value without anyone noticing, which can lead to hardware damage.If I set in STM32CubeMX 6.17.0:HRTIM -> Timer x -> Dead Time -> Prescaler = "fDTG = fHRTIM * 2"The generated code contains:LL_HRTIM_DT_SetPrescaler(HRTIM1, LL_HRTIM_TIMER_x, LL_HRTIM_DT_PRESCALER_MUL2);LL_HRTIM_DT_PRESCALER_MUL2 is defined as HRTIM_DTR_DTPRSC_2 -> Register HRTIM_DTxR DTPRSC[2:0] = 0x4This results in the deadtime value:t_DTG = 2^4 * (t_HRTIM / 8) = 2 * t_HRTIM = fHRTIM / 2So instead of "fHRTIM * 2" I get "fHRTIM / 2"!I think the confusion comes from the fact that in CubeMX the prescaler is set as a multiple of the frequency, but in the datasheet and driver the multiple of the period is described.Before the driver update, there was an