Skip to main content
Explorer
January 30, 2025
Solved

NUCLEO-H7S3L8 USB-HS & XSPI problems

  • January 30, 2025
  • 1 reply
  • 712 views

 

I have several problems with the NUCLEO-H7S3L8 board

 

1) When initializing the USB - HS peripherals, I getting stuck in the "USB_CoreReset" function:

Related problem

Shpegun60_0-1738247929301.png

and after some time when (count > HAL_USB_TIMEOUT) the program goes to Error_Handler(). This happens identically when I initialize the project with the board selection (file nucleo_h7s3l8_test.rar)

The project is launched on an internal flash drive without using XSPI, i.e. only the ..._BOOT project is used and ...APPLI is always closed.

 

2) Then I started digging into the examples and using the UM3294 instruction 5.2.3 Developing an application in the external flash memory, page 21

The project is presented below: STM32Cube_FW_H7RS_V1.1.0\Projects\NUCLEO-H7S3L8\Applications\USB_Device\CDC_Standalone

Shpegun60_1-1738251040439.png

But the program never goes into debug and gets stuck at a strange address.

Shpegun60_2-1738251337311.png

 

Shpegun60_3-1738251362022.png

I tried to run only ..._BOOT but the initialization of the external memory is going through errors and as a result, the transfer of control to the external flash does not occur.

Shpegun60_4-1738251607295.png

Shpegun60_5-1738251687254.png

I am attaching photos of the ordered board:

Shpegun60_0-1738251987917.pngShpegun60_1-1738251998430.png

Shpegun60_2-1738252008357.png

 

 

 

    This topic has been closed for replies.
    Best answer by FBL

    Hi @Shpegun60 

    Check compiler optimization and set it to None. It could be linked as well to synchronization with PHY frequency and CPU frequency. I assume this is quite complex to insure in the USB_CoreInit function. If still having issues, try to decrease CPU frequency.

    1 reply

    FBLAnswer
    Technical Moderator
    March 18, 2025

    Hi @Shpegun60 

    Check compiler optimization and set it to None. It could be linked as well to synchronization with PHY frequency and CPU frequency. I assume this is quite complex to insure in the USB_CoreInit function. If still having issues, try to decrease CPU frequency.