Solved

Dear all,I'm unable to connect via SWD to my STM32F103C8T6. What ever I try I get no target found with STM32CubeProgrammer or ST-LINK Utility (I have tried all combinations at slow and high speeds). - device is virgin- BOOT0 is low- NRST unconnected (shows 3V3) and connected/removed while testing- Connections go through from ST-Link to STM32 pins- 30 Ohm and 0 Ohm tested for SWCLK and SWDIO (GND and 3V3 connection to ST-Link with no resistor)- Correct mapping of ST-LINK pins to STM32 checked multiple times- There are no obvious shorts between any of the paths- 3V3 is stable and GND closed- The ST-Link was tested with a "blue pill" board with the same STM32 on it and it worked flawlessly I have also tried:- Cutting the path to the esternal 16MHz crystal curcuit- Connecting/Disconnecting VCC- Soldered a new STM32 onto the board I am currently running out of ideas, I think there is either a fault in the PCB design that damages the MCU or prevents booting or maybe some confi

Hello,after setup SPI1 and setting CSTART=1, I expected that SPI is send immidiatly on bus.(I toogled PE00 with CSTART=1)I couldn't find some that explains that behaviour. It behave  the same, if I use DMA or writing directly to TXDR.Do you have an idea ?My testcode. SPI1->IFCR = 0xFFFF; // Clear all flags MODIFY_REG(SPI1->CR2, SPI_CR2_TSIZE, BufferSize); SPI1->CR1 |= (SPI_CR1_SPE); SPI1->CR1 |= SPI_CR1_CSTART; GPIOE->ODR &= ~(1 << 0); for (u32 i = 0; i < BufferSize; i++) { LL_SPI_TransmitData8(SPI1, pBuffer[i]); }CPU is set to 160Mhz and SPI Prescaler is 256 

I've been using this part from NXP (originally Freescale, I think)  for a while now.I've just noticed that it now has an ST Product Page:https://www.st.com/en/mems-and-sensors/fxls8967af.htmland the datasheet says:The ST Accelerometers portfolio page also lists a few other NXP part numbers: Is this a 2nd-source arrangement, or have these products fully transferred from NXP to ST ?  

Hi,We are running a crypto key generation library on both an STM32G474 (170MHz) and an STM32H563 (240MHz).Over about 80 runs, the average generation time is around 12 seconds for the H5 and 38 seconds for the G4.These times are fine for our application (although faster would be better) but I am curious why the G4 is over 3 times slower as I would have expected something more like 40% longer generation times.The arithmetic part of the library uses some assembler functions for long multiplications and, for both processors, these seem to have picked a section for "Armv6-M (or later) with DSP Instruction Set Extensions."The compiler flags being used are listed here. The repeated sections are because I still haven't really figured out how cmake is generating them but I believe the relevant differences are:-mcpu= cortex-m4 or cortex-m33-mfpu= fpv4-sp-d16 or fpv5-sp-d16compile C with /usr/bin/arm-none-eabi-gcc__VERSION__ "14.2.1 20241119"G4 Flags:C_FLAGS = -mcpu=cortex-m4 -mfloat-abi=hard -mf

  Hello everyone, I’m facing an issue while trying to debug my project custom_for_stm32f103c8t6 in STM32CubeIDE. When I launch the debug session, I get the following error message: Error in final launch sequence:Failed to start GDB server What I’ve tried so far: Installed ST-LINK driver (STSW-LINK009). Changed USB cable and port. Reset the STM32F103C8T6 board. Interestingly, I can still flash the firmware successfully using STM32CubeProgrammer, but debugging through STM32CubeIDE fails with the error above. Unfortunately, the error still persists. Has anyone encountered this problem before and found a solution? Any guidance would be greatly appreciated. Thank you in advance!    

I've got some trouble with the CRC unit in an STM32L475.At first, I got wrong CRC results, but then it dawned on me that the compiled code didn't force only 8 bits at a time into CRC->DR. So I added what I've used elsewhere, to force the compiler to store only 8 bits in a 32-bit register.*(__IO uint8_t *)(CRC->DR) = Temp;Temp is a uint8_t variable. Below, it certainly looks like a single byte is transferred to CRC-DR (strb instruction). *(__IO uint8_t *)(CRC->DR) = Temp; 80013ea: 683b ldr r3, [r7, #0] 80013ec: 7018 strb r0, [r3, #0]However, after I modified my code that way, it would seem that nothing is calculated at all. No matter how many (non-zero) bytes I throw into CRC->DR, the output just stays at 0.If I revert back toCRC->DR = Temp;at least I get something, albeit an incorrect value as soon as I enter more than one byte.I initialise the CRC unit like this: CRC->POL = 0x04C11DB7; CRC->INIT = 0; CRC->CR = CRC_CR_RESET;Is there something blatantly obv

I’m choosing a microcontroller for a new STM32 design and I’d appreciate some recommendations.I don’t have particular requirements for compute performance, memory size, or ultra‑low power — just solid peripheral support and a Nucleo board available for development. Required peripherals: 1 × FDCAN (CAN FD) 3 × SPI (in practice only 1 SPI with multiple CS likely) 3 × I2C  Constraints: Prefer MCU in LQFP / QFN (no BGA) Compact (48 pins)  Development on a Nucleo board  I’ve looked at parts like STM32C552VET6 and STM32L552CCT6 as potential targets, but I can’t find a dedicated Nucleo board for them.   Any suggestion? thank you,   best regards,   Gianluca

I've implemeted a vision transformer for STM32N6 NPU.Repository: https://github.com/minchoCoin/stm32n6-transformerBatchMatmul operator is not yet supported on NPU and run on the CPU, but it is much faster than STM32H7(inference time was reduced by about 90% than STM32H7) because fully connected layer and convolutions is executed on NPU.Vision Transformer for STM32N6 NPU has three differences from the original ViT(A. Dosovitskiy et al., 2020)1. Patch Embedding (PE) is configured to be performed in the pre-processing process before model input: Because if the model has PE and self attention, it is not possible to interpret the model structure using STEdgeAI (I don't know why yet...)2. Remove bias parameter from Fully Connected layer or change fully connected layer to 1x1 Conv2D:  fully connected layer of onnx should have 2-dimensional input. however, fully connected layer of ViT has 3 dimensional input(batch,patch,embedding), so compiler removed the batch axis, and ma

HiAs I experienced some problems with 2.1.0, I reverted to 2.0.0 and in that process I seem to have gotten the error:Program "gcc" not found in PATH - "[Discovery options] page in project properties"I followed the instructions found in the stm32CubeIDE user guide https://www.st.com/resource/en/user_manual/um2609-stm32cubeide-user-guide-stmicroelectronics.pdf, but the problem persists.Is there a way to manually clear this from any of the configuration XMLs perhaps?The code does still compile and creates binaries, so the error is just a nuisance.[Edit] spellingBest regardsMartin 

I updated the STM3CubeProgrammer to version v2.22.0, and after restarting the app, it started showing a blank page. I was also not able to close the application directly. I had to end the task from the task manager. I uninstalled the latest version and installed v2.20.0, but it is also showing a blank page. Also, in STM32CubeIDE, I am not able to run and debug code. It gets stuck at  "Download in progress". Are both problems related?

Hi, I tried to configure the USB Host for a project, but it’s difficult to configure, and I am not finding any online support available for the STM32H5 series controller.My requirement: I configured PB4 as an output, which is connected to a green LED. Whenever I plug the USB into my controller, the green light turns on, and whenever I remove the USB from the controller, the green light turns off.I’ve tried some methods, but they are not working. Can anyone please help me?

I have been using a STM32F469i Disco board to interface with a 800x800 LCD in MIPI DSI video burst mode. In order for this to work from the DISCO board, I have an adapter PCB to connect from the DISCO board to the LCD.It took a while to get going, but the setup with the custom LCD and DISCO board is working fine.I have recently moved to a custom board; I have intentionally made the video dependent aspects of this board the same as the disco board so that I can run my software on either the disco or the custom board without making any changes.The custom board sometimes exhibits odd behaviour when rendering from the SDRAM via the LTDC.Enabling the test colour bars from the DSI always display ok without any problem.From SDRAM/LTDC, the horizontal start point shifts from the left side of the display to some arbitrary location across the width of the display. This occurs randomly, it can be running for hours and remain stable, other times it may shift once, then be stable for a time and may

What is recommended way to change or override the 'SYSTEM_CLOCK' symbol defined in 'tx_initialize_low_level.S' , that feeds into the threadX systick period calculation?  I could change the SysTick after threadX is started -- that is probably the easist fix. I dont want to modify the threadX submodule in my project, as its pulled from the internet at some pinned version. I've currently made a local copy of 'tx_initialize_low_level.S', and then I use CMake to select that particular S file - so that solves the problem, but I dont like having a personal copy of a file from the submodule. After experimenting for some time, and then scouring the web, I cant find any suggestions on this issue, there are some changes that can be imported via having your own 'tx_user.h' -- but I cant see anything that can override the SYSTEM_CLOCK.   Cheers, Nick

Hello,I found a bug in STM32CubeMX code generation for STM32H7S3.When configuring Ethernet with external clock input (ETH_CLK pin,PD6 with AF4_ETH) as PHY clock source, CubeMX does not generateGPIO initialization for this pin in HAL_ETH_MspInit().Workaround - must add manually:__HAL_RCC_GPIOD_CLK_ENABLE();GPIO_InitStruct.Pin = GPIO_PIN_6;GPIO_InitStruct.Mode = GPIO_MODE_AF_PP;GPIO_InitStruct.Pull = GPIO_NOPULL;GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_HIGH;GPIO_InitStruct.Alternate = GPIO_AF4_ETH;HAL_GPIO_Init(GPIOD, &GPIO_InitStruct);Without this, Ethernet does not work even though all otherETH pins are correctly initialized by CubeMX.Steps to reproduce:1. Select STM32H7S32. Enable Ethernet (ETH)3. Set clock source to external clock via ETH_CLK pin (PD6)4. Generate code5. ETH_CLK pin GPIO init is missing in generated codeCubeMX version: 6.17.0MCU: STM32H7S3Thank you

Dear ST Support Team,I’m currently trying to run the ST67W6X_CLI application (from the Wi-Fi ST67W6X CLI Wiki)using the following setup:Wi-Fi Expansion Board: X-NUCLEO-67W61M1Host MCU Board: NUCLEO-F446REIDE: STM32CubeIDE (latest version)Middleware: FreeRTOS (as provided in the ST67W6X_CLI example)The project builds successfully and the firmware is programmed without errors, but at runtime, I encounter a HardFault_Handler.The fault occurs inside the FreeRTOS queue management code, specifically during a call to xQueueReceive() in queue.c. Debug Information:When the fault occurs, the debugger stops inside:prvCopyDataFromQueue(pxQueue, pvBuffer);and the corrupted member is:pxQueue->uxItemSizeObserved value: 536871212 (0x2000412C) — which clearly points to an invalid or corrupted queue structure.Call stack snapshot:HardFault_Handler()prvCopyDataFromQueue() at queue.cxQueueReceive() at queue.cspi_get_txbuf() at spi_iface.cPlease see the attached screenshot (from STM32CubeIDE) showin

Hello, I am reviewing the reference design for the ST87M01 and noticed that a 1nF capacitor is specified for the DC block on the GNSS RF path. In many high-sensitivity GNSS designs, 100pF is the standard choice for the 1.5 GHz L1 band to ensure the Self-Resonant Frequency (SRF) remains well above the operating frequency. Questions: Why was 1nF selected for this specific SiP instead of the typical 100pF? Does the internal matching of the ST87M01 rely on the specific reactance of a 1nF series capacitor at 1575 MHz? For a design strictly optimized for GNSS sensitivity, would a 100pF High-Q (C0G) capacitor offer any measurable improvement in insertion loss or noise figure compared to the 1nF reference value?   Greetings, Andreas

I created a GUI with TouchGFX, enabled UART and created a custom task in freeRTOS in STMCubeMX.  When running the code the display is just blank when I add this code inside of my custom taskif(xQueueReceive(queueHandle, &message, 0) == pdPASS) { printf("Message received"); }If I comment this code out the gui displays.  However, I found something interesting that if I debug and set a breakpoint at the for(;;) loop statement on line 729 in main in the UART_Task and another breakpoint on the print message and then press play to continue, the GUI displays and when I tap a button on my GUI I get to the breakpoint on the printf message which is exactly what I'm trying to do and it works perfectly.  I'm not sure why it works when I first breakpoint there, but won't work just loading the program onto the board.  Here is the main code/* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @bri

I have a NUCLEO-F103RB (MB1136 rev C05). My goal is to remove the ST-LINK and power via a hat supplying 3.3v. For the 3.3v I have: Moved JP5 to pins 2-3. Checked JP1 is removed. Removed SB2 zero ohm resistor. Removed SB12 zero ohm resistor. Verified my shield is putting out a good 3.3v which is attached to connector CN7 pin 16. For the HSE I have: Removed SB54 and SB55. Soldered zero ohm resistors to R35 and R37. Soldered 20pf capacitors to C33 and C34. Removed SB16. Removed SB50. Added 8Mhz 16pf crystal X3. The ST-LINK is still physically attached at the moment, but I do plan to cut it off once things are working. The board comes up and accepts programming and works in the debugger. Stepping through the initialization it gets to where the HSE is set up and then sits in an infinite loop waiting for the HSE to come ready. I tried replacing the crystal X3 just in case I got a bad one but there was no change in behavior. The clock config is unchanged, other than setting HSE to "crysta

Please use English on this forum.Translated: The development board is STM32H723, using stm32cubemx for development, debug is disabled, using stlink to burn found that it can be burned, and it can also be debugged, which is very strange! (The development board is STM32H723.) It was developed using STM32CUBEMX. The debugging option is set to "Disabled". Programming with stlink, discovering that it can be programmed and debugged. It's weird! ）Original:开发板为STM32H723，使用stm32cubemx进行开发，debug勾选禁用，使用stlink烧录发现可以烧录，并且还可以调试，非常奇怪！（开发板是STM32H723。它是使用stm32cubemx开发的。调试选项设置为“禁用”。使用stlink进行编程，发现可以编程，也可以调试。这很奇怪！） 

Hi guys,I am a newbie in STM world. I am struggling with a small code but failing every attempt modifying the code googling for several times. Please have a look to my code. I have defined three functions, i.e. inv_on(), inv_off(), and sw_state().  When these functions are called in other defined functions, two errors, i.e. missing ')' and missing ';' are showing against each called functions. But when called in main(), one error i.e. missing ')' is showing. The error messages are given as comment. Suggestion is solicited please. Regardsankhola #include "STM8S.h" #include "ccp.h" void inv_on(void); void inv_off(void); void sw_state(void); unsigned int pwm_duty1 = 40; unsigned int pwm_duty2 = 50; unsigned int i=0; unsigned int duty; unsigned char toggle=0; unsigned char off_state; unsigned char on_state; @far @interrupt void TIM2_UPD_OVF_IRQHandler(void) { // 1. Clear the Interrupt Pending Bit if (TIM2->SR1 & TIM2_SR1_UIF) { if (toggle == 0) { TIM1_SetC

I am facing an issue in STM32CubeIDE on Windows where the I/O Configuration / Pinout & Configuration window is not appearing after creating or opening a project.Normally, when opening the .ioc file, the Device Configuration Tool (CubeMX interface) should open showing the MCU pin diagram and peripheral configuration options. However, in my case, this interface is not appearing.Issue Details:Operating System: WindowsSoftware: STM32CubeIDEWhen I create or open an STM32 project, the Pinout & Configuration view does not open.The .ioc file either does not open correctly or the graphical configuration window is missing.Because of this, I cannot configure GPIO, ADC, UART, or other peripherals.Expected Behavior:Opening the .ioc file should display:Pinout & ConfigurationClock ConfigurationProject Managerwith the MCU pin diagram and peripheral configuration options.What I Have Tried:Opening the .ioc file manually from Project Explorer.Restarting STM32CubeIDE.Resetting the perspective.

Any way how can I get in touch with ST on availability on this product? We would like to implement this into our devices, a devkit or hardware preview would help, we had previously integrated with the VL53L8 and VL53L5 which the result are good, and with the release of VL53L9, it will produce even better result for 3D mapping. ThanksVince 

Hi, I'm using a STM32MPU157C with linux 6.6, uboot, OP-TEE 4.0 and TF-A 2.10 and I have a Device Tree (for linux and uboot) which declares the USB OTG node as following : &usbotg_hs { compatible = "st,stm32mp15-fsotg", "snps,dwc2"; pinctrl-names = "default"; dr_mode = "host"; pinctrl-0 = <&usbotg_hs_pins &usbotg_fs_dp_dm_pins>; vbus-supply = <&vbus_sw>; /delete-property/ wakeup-source; }; usbotg_hs_pins: usbotg-hs-0 { pins { pinmux = <STM32_PINMUX('A', 10, ANALOG)>; /* OTG_ID */ }; }; usbotg_fs_dp_dm_pins: usbotg-fs-dp-dm-0 { pins { pinmux = <STM32_PINMUX('A', 11, ANALOG)>, /* OTG_FS_DM */ <STM32_PINMUX('A', 12, ANALOG)>; /* OTG_FS_DP */ }; };I explicitly use it in FS as a Host and remove the wakeup-source declared by the stm32mpu151.dtsi.My problem is that I can see that when entering in suspend, there is a difference of ~4-5mW in power consumption depending on if the USB node is enabled or not in the device t

Hi everyone,I just started developing software for a new project containing on of the STM32L4P5 series microcontrollers. Therefore I bought the NUCELO-L4P5ZG starter-kit to get used to the IDE, HAL and so on. I use the STM32CubeMX IDE (Version 6.16.1) to configure the board and generate the basic initialization sources. Further code writing is done in STM32CubeIDE (Version: 2.1.1).For the beginning I configured three GPIO pins for the LEDs on the board and the LPUART for simple data transfer to terminal on host computer. For the transmission I want to use DMA . After generating the code with CubeMX and implementing some simple blink logic for the LEDs, I added the line HAL_UART_Transmit_DMA(&hlpuart1, buffer, 14); to the main loop. I debugged the code and saw that the code ran into the infinite loop in the DefaultHandler in the startup file startup_stm32l4p5zgtx.s: After searching for two and a half hour I finally found the problem: the generated names for the interrupt h

See Inconsistent pin naming for CubeMX - does the same apply to CubeMX2 ?   (Cross-posting at the request of @Ghofrane GSOURI; again, no label available for "Suggestions")