Solved

 Hello ST Community,I am working with the STM32N6570-DK and the USBX Ux_Device_Video example fromSTM32Cube_FW_N6_V1.3.0\Projects\STM32N6570-DK\Applications\USBX\Ux_Device_Video.I followed the README instructions exactly:Built FSBL and Ux_Device_Video projects successfully in STM32CubeIDEGenerated FSBL.bin and Ux_Device_Video.binSigned both binaries using STM32_SigningTool_CLIProgrammed:FSBL-trusted.bin at 0x70000000 (external flash)Ux_Device_Video-trusted.bin at 0x70100000 (external flash)Set BOOT0 and BOOT1 to boot from external flash and reset the boardHowever, the application does not run as expected. When the board is connected to a Windows PC, the Windows Camera application fails with the error:   Can't start your camera0xA00F4241 <CameraSwitchFailed> (0xC00DABE7)From my understanding, the Ux_Device_Video example should enumerate as a USB UVC camera and stream video to the Windows Camera app. Since the camera app fails, it seems the firmware may not be executi

Hi everyone,I’m experiencing unexpected behavior while testing 9-bit SPI on an STM32, observed with a logic analyzer. The issue only occurs when the MOSI line is physically connected to the slave.Observations::keycap_1: MOSI not connectedCS and SCLK are correctMOSI stays highSPI decoder shows 0x1FF Expected behavior for a floating MOSI line:keycap_2: MOSI connected to the slaveMOSI data becomes correctBut a very brief rising edge (glitch) appears on CS during data transmissionCS immediately returns active → causes unintended slave deselectionResult: data loss during the SPI frameAdditional info:STM32 model: stm32u5g9j-dk2SPI mode: 9-bit, masterSCLK frequency: 10 MHzIs this a known issue with 9-bit SPI on STM32?Should I add a pull-up/pull-down on CS or MOSI?Any other suggestions to avoid this glitch?Attached are screenshots showing the behavior.Thanks in advance for your help!MOSI connectedMOSI not connected

Hi Team, Urgent help required!! Today I have update my CubeIDE to the latest version, before the update i have had several projects saved, but none of it is launching in CubeIDE, when i click on the .IOC file from CubeIDE it opens on CubeMX and when i clock on generate code it says "The Code is successfully generated under :C:/Users/S****** H******/STM32CubeIDE/workspace_1.16.0/Door Module Testing" and as soon as i click on Open Project it goes to CubeIDE and shows main.c file. When I try to open the .IOC in CubeIDE it redirects to CubeMX again, a never ending loop has formed. Attaching screenshots for your review. Someone from ST Electronics please look into my issue and give me a quick fix or a workaround. Regards, Prateek

Im trying to run SYSCLK from LSI on a STM32C011. But it appears as if the MCU is not running. I cant see anything in the datasheet that says the clock cant be used and it can be routed fine in the clock configurator. Am I missing something in the datasheet or does the HAL not support it?

Hello fellow readers,##Disclaimer##I am using a Nucleo Board, the Nucleo H7S3L8, and HAL_ERROR ist laughing me since 2 days in my face# I think you, dear reader, have heard about the SWR-Bit, which vanishes out as soon the software has restarted succesfully, everything seems perfect and you have finally the feeling you found the solution to world piece.But I am currently at the brink of insanity, because this little ******* ***** ** **** wont clear itself after I forced the reset. What do I mean specifically?HAL_StatusTypeDef HAL_ETH_Init(ETH_HandleTypeDef *heth) { uint32_t tickstart; if (heth == NULL) { return HAL_ERROR; } if (heth->gState == HAL_ETH_STATE_RESET) { heth->gState = HAL_ETH_STATE_BUSY; #if (USE_HAL_ETH_REGISTER_CALLBACKS == 1) ETH_InitCallbacksToDefault(heth); if (heth->MspInitCallback == NULL) { heth->MspInitCallback = HAL_ETH_MspInit; } /* Init the low level hardware */ heth->MspInitCallback(heth); #else /* Init the low lev

Hi,I can't find a way to select in MEMS Studio which MLC filters are passed FIFO and how to enalbe MLC result in FIFO.Configuration created by MEMS studio enabled MLC_FILTER_FEATURE_FIFO_EN in EMB_FUNC_FIFO_EN so I see selected MLC features in FIFO but nothing more - no filters, no results.I manually enabled MLC_FIFO_EN but MLC results didn't appear in FIFO.I tried to enable filters manually in mlc.json by adding "fifo": "true" to filters in json file, but it didn't help.  I've attached MLC files. Best regardsTomasz 

Hi I am using Nucleo H753zi board, can I use X-CUBE-MEMSMIC1 expansion for sound source localization.

Hello ST Community, I am seeking assistance with a project generation issue using STM32 Motor Control SDK (v6.x) and the EVLSPIN32G0A1 evaluation board. The Problem: Even though I explicitly select the EVLSPIN32G0A1 board (which features the STSPIN32G0A1 / STM32G071 core) in the Motor Control Workbench, the generated .ioc file and STM32CubeIDE project target the STM32G031C8Tx instead. Consequences: Debugger Error: When attempting to flash the code, the ST-LINK GDB server returns: "Target no device found" or a Device ID mismatch because it is looking for a G031 but finding a G071 core. Configuration Mismatches: The clock tree and memory boundaries in the .ioc are being set for the G031 (64KB Flash) instead of the STSPIN32G0 (128KB Flash). What I have tried: Creating a new project in MC Workbench and selecting the board from the "Boards" tab. Configuring

Hi,I’m developing an application on multiple STM32H563 units on the same board. Although all units use the same firmware, the logic depends on each unit’s position, so I need a way to identify which unit it is.Currently, I program the full flash memory (.bin/.elf) with STM32CubeIDE or STM32CubeProgrammer. Is there a standard or recommended way on STM32H563 to store small per-device information (like unit ID or role) separately from the main application flash, so the firmware can read it at startup? Thanks for any guidance!

Hello,I got back to my issues from this post.I was able to connect wires to SPI lines, and get the measurements to logic analyzer. These are the results:Logic2 screenshot Now i can see that the issue is the CS line, but i dont know why it is being changed to HIGH in these short pulses.  The GPIO config: /*Configure GPIO pin : SPI1_CS_Pin */ GPIO_InitStruct.Pin = SPI1_CS_Pin; GPIO_InitStruct.Mode = GPIO_MODE_OUTPUT_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_HIGH; HAL_GPIO_Init(SPI1_CS_GPIO_Port, &GPIO_InitStruct);SPI Config:hspi1.Instance = SPI1; hspi1.Init.Mode = SPI_MODE_MASTER; hspi1.Init.Direction = SPI_DIRECTION_2LINES; hspi1.Init.DataSize = SPI_DATASIZE_8BIT; hspi1.Init.CLKPolarity = SPI_POLARITY_LOW; hspi1.Init.CLKPhase = SPI_PHASE_2EDGE; hspi1.Init.NSS = SPI_NSS_SOFT; hspi1.Init.BaudRatePrescaler = SPI_BAUDRATEPRESCALER_32; hspi1.Init.FirstBit = SPI_FIRSTBIT_MSB; hspi1.Init.TIMode = SPI_TIMODE_DISABLE; hspi1.Init.

My goal is to use USART6 as debug output because I haven't route the dedicated BootROM pins of the USART2.Anyway! It seems that the BootROM is trying to read my SD card. First sequence:CMD and CLK of SDMMC1 seems to be talking to the SD card in a very low speed. Here I'm talking about kHz. I don't know what they are saying. The signals are perfectly square waves.Second sequence:Suddenly the CLK become a fast sine wave. I still don't know the frequency, but it's defently much faster than the first sequence. Now, the D0 is a digital input of BootROM. This D0 looks like a sword shaped signal. I don't know if it's my configure at my osciloscope that cause this view.After the second sequence as ended. There are no more data passing between the SD card and MP257. The clock is still running at the same frequency.I don't know if the TF-A firmware has been read or not. I haven't tested the USART6.Question:Where can I find the commands/data that are passing between the SD card and the MP257

Introduction: While testing the U575 with external PSRAM connected over OCTOSPI1, certain memory test scenarios fail deterministically.   Setup: Using a STM32U575, connected on OCTO-SPI1 to PSRAM (IS66WVH8M8) 8MB in size. The STM is configured in memory mapped mode, hyperbus enabled, no DMA or Cache enabled, & wrap/burst mode disabled.   While testing the PSRAM using Barr tests, found that the data bus and address bus test pass, but the device test had a deterministic pass/fail behavior. The device test passed for any size as long as the test wasn't crossing the 2MB boundary.  Base (start) address Size Result 0x9000 0000 2 MB Test passes (also for 0x9020k,0x9040k, 0x9060k resp.) 0x9010 0000 2MB Test fails, around 0x9020 0000.  0x9030 0000, 0x9050 0000 respectively 2MB Test fails, around 0x9040 0000 and 0x90600000 respectively. 0x901FF000 2 kB Test fails around 0x9020 0000.    While debugging/analyzing code found something inter

Hello there,I'm trying to create a project for stm32h7s7 with external loader. But when i added the external loader in IOC file the all indexes were lost in editor mode. But I checked for building, i can't see any problem. I tried index -> rebuild but it could not help me

Hi!I'm working on a Trustzone enabled application in STM32U5A5 nucleo board and have some questions in my mind. I have used the configurations of the example project for the Trustzone, which you can find below: - TZEN=1 - SECWM1_PSTRT=0x0 SECWM1_PEND=0xFF meaning all 128 pages of Bank1 set as secure - SECWM2_PSTRT=0xFF SECWM2_PEND=0x0 meaning no page of Bank2 set as secure, hence Bank2 non-secure I have enabled SAU and left it with the default configuration. I've also enabled the GTZC_S. In my application, I'm using TAMP mechanism of the RTC to create an interrupt when the output signal doesn't match the input signal. First question:My application can boot from the secure app and jump to non-secure app without any problems. But in the MX generated NonSecure_Init() function, after the line SCB_NS->VTOR = VTOR_TABLE_NS_START_ADDRThe SCB->VTOR_NS register doesn't change, remains as 0x0 (according to the SFR in the debug interface). After the boot to non-secure

I have an ILI9341 SPI screen and a small self-made library that can display different numbers on the screen. I want to be able to update the screen (display a new number) every time there is an interrupt. I have tested the screen functions independently, and they work properly. But when I call them from the interrupt handler, they fail. The board is STM32F407G-DISC1. Timer configuration static void MX_TIM2_Init(void) { /* USER CODE BEGIN TIM2_Init 0 */ /* USER CODE END TIM2_Init 0 */ TIM_ClockConfigTypeDef sClockSourceConfig = {0}; TIM_MasterConfigTypeDef sMasterConfig = {0}; /* USER CODE BEGIN TIM2_Init 1 */ /* USER CODE END TIM2_Init 1 */ htim2.Instance = TIM2; htim2.Init.Prescaler = 999; htim2.Init.CounterMode = TIM_COUNTERMODE_UP; htim2.Init.Period = 335900; htim2.Init.ClockDivision = TIM_CLOCKDIVISION_DIV1; htim2.Init.AutoReloadPreload = TIM_AUTORELOAD_PRELOAD_DISABLE; if (HAL_TIM_Base_Init(&htim2) != HAL_OK) { Error_Handler(); } sClockSourceConfig.ClockS

Our product is a space device and as a result, we've had to recently do some radiation testing of the device. In particular, focused on the STM32H755 processor that runs the board.I'm looking for any papers/references/app_notes, anything, that can help me to gather details about how the processor performs in a radiation environment.And yes, I realize this is not a rad-hard or rad-tolerant processor. 8-)Thanks.-brad w. 

Hi there !i work with DS2482 I2c to one wire . After i send the command reset i need the read the status register until i find one bit at 1, so i wrote my routine in this way  static uint8_t DS2482_Status_Register(void) { uint8_t register_status=0; uint8_t data=0; while(register_status !=0x02 ) { Master_Recive_Data(DS2482_Addr, &data, 1); // HAL_Delay(1); dato= data; register_status = data; register_status &= 0x02; } if(register_status != 0x02) { return HAL_TIMEOUT; } return HAL_OK; } when i run the program i recive error 4 from i2C formvoid HAL_I2C_ErrorCallback(I2C_HandleTypeDef *hi2c) { } But if in the code below i put one delay of 1ms everything work perfect . So there is one "elegant" way to resolve the problem  ? or there are other solution  ? Thanks a lotSergio

STM32CubeIDE Version: 2.0.0When trying to create a new project from the IOC of another project, I can't find a way to do it. Is this feature lost or BUG ? Thanks in advance.

Hello,   I’m starting a new design with the STM32H755. I also have the dev board (Nucleo-H755ZI-Q), but I do not have its schematic. So far, the closest schematic/design reference I’ve found is Figure 18 in AN4938 (“Getting started with STM32H755”).   Could you please share more schematic references?   I was thinking about the following: The complete NUCLEO-H755ZI-Q schematic and the BOM Any additional pages/details related to the Figure 18 schematic (it appears to reference a multi-page schematic, but we only have the first page in this document) Any other official schematic/reference design examples for STM32H755 that I could use as a starting point   Thank you for your time and help!  

I am working on STM32N6570-DK board. I am trying to run a code for three channels ADC+DMA, INP8, INP10, INP16. The output at USART is coming out to be zero in all three channels. I am attaching the code here. 

I have a project for a battery-powered clock using the STM32WBA55 chip. The battery is replaceable; the device can sit unused on a shelf for up to 4 months without the battery. Since the STM32WBA55 doesn't have VBAT or VRTC pins, how can I keep the backup recorder, time, and date active?

After updating and restarting my PC with Windows 10, my old version of CubeProgrammer would not open at all. The version number is unknown. Other STM32 software works without any issue such as CubeMX and CubeIDE.I then tried installing the latest version, 2.21.0. The program launched (even when run as administrator), but it did not function fully. I attached a screenshot for reference. None of the four icons on the top-left responded, and I received error messages when clicking the icons on the right.I also tried installing previous versions from 2.16.0 to 2.20.0, but none of them worked. Specifically:Versions 2.16.0, 2.18.0, and 2.19.0 briefly showed the launch logo, then closed immediately.Versions 2.20.0 and 2.21.0 would open, but the program remained unusable. 

Hi everyone,I am bringing up a custom board based on the STM32H743VIT6. I am trying to connect via ST-Link (SWD), but I am getting the standard "Can not connect to target" error in STM32CubeProgrammer.The Setup:MCU: STM32H743VIT6Debugger: ST-LinkInterface: SWD (SWDIO, SWCLK, GND, 3.3V detected)Power Supply: External 3.3V. Board voltage source to provide the necessary power for the system, something that ST-Link alone cannot do.The Problem: After failing to connect, I probed the power pins and found abnormal values:VCAP Pin: I measured 2.7 V on the VCAP pin. As I understand it, VCAP corresponds to the internal LDO output for VCORE and should normally be around 1.2 V. Does a reading of 2.7 V indicate an internal short circuit to VDD or a blown LDO?VDD Drop (Pin 75): On Pin 75 (VDD input), I have a known bad solder connection (trace compromised). I measured 2.3V on this pin.Question: Since the other VDD pins are correctly supplied with 3.3V, shouldn't the internal silicon power mesh maint

My STM32H533VE works as PD Sink.We connected CC1/CC2 with DBCC1/DBCC2 (as AN5225), STM32 cannot power up with a USB PD adapter. The adapter supplies power for ~20ms then stops the supplying.If I remove the long time initialization code (LSE initialization), system can boot up and USB PD works fine (PDO can switch).Is this normal? if yes, I may move the LSE initialization later.

Hi everyone,I’m feeling a bit defeated by a task that should be "Hello World" level simple. I’m trying to get a basic printf to show up in PuTTY using a NUCLEO-G474RE, but I’m getting absolutely nothing in the terminal.I do this all the time with my NUCLEO-H723ZG using USART3 and it works like a charm. For the G4, I’ve switched over to USART2, but no luck.Here is my setup:Toolchain: CubeMX + CMake.The Logic: I've overwritten __io_putchar() with a HAL_UART_Transmit call.The Config: USART2 is enabled, baud rate matches PuTTY (115200), and the clocks seem fine.I even had a friend who uses G4 boards regularly take a look, and even he couldn't figure out why the data isn't hitting the ST-Link. It feels like I'm missing one tiny, G4-specific checkbox or jumper setting.I've put together a bare-bones repository with just the code for the printf here: https://github.com/mpek29/nucleoG4Has anyone else run into similar issues ?Thanks in advance for any pointers, I'm sure it's something silly I've