NUCLEO-H7S3L8 Bad Application Start Address

[potatobandit]

I have a NUCLEO-H7S3L8 board, and I am unable to debug any of the projects. I receive a sigtrap error upon debugging. I have tried multiple projects in ST's Github.
 STM32CubeH7RS/Projects/NUCLEO-H7S3L8 at main · STMicroelectronics/STM32CubeH7RS

All projects have the same issue.

After further investigation, we have determined that the default start address for the application is incorrect. 
If I make a fresh project and select the chip itself rather than the eval board during project setup, I am able to debug.

Is this a known issue with this NUCLEO board?

Is there a way to change the address so we can explore the example projects?

Is there an alternative NUCLEO board that is not in the R/S family that I should explore instead?

Thanks 

[Pavel A.]

> Is there a way to change the address so we can explore the example projects?

Yes, in the debug configuration.

 

[mƎALLEm]

Hello,

Did you read the README.md file? especially the part: "How to use it ?"?

https://github.com/STMicroelectronics/STM32CubeH7RS/blob/main/Projects/NUCLEO-H7S3L8/Examples/GPIO/GPIO_IOToggle/README.md#how-to-use-it-

[potatobandit]

Thank you both for your responses. I walked through the instructions on the readme and was still struggling to get the project to flash. With some more forum surfing, I did find this instruction helpful.
STM32CubeIDE: How to debug an STM32H7Rx/Sx project... - STMicroelectronics Community

Just needed more visuals trying to navigate CubeIDE. Thanks. I previously used the H5 eval and must of been spoiled by how quick it was to get these running. The H7S series seem to have configuration steps than I was expecting.

 

[potatobandit]

I have followed the instructions in the readme, and I am still unable to debug/flash my nucleo board. Could you please advise to what step I may be overlooking or any settings that are incorrect? Thanks

 

 

[Pavel A.]

@potatobandit On your 3rd screenshot please note the "Start Address" box. This allows you to specify the start address. Probably you want to start running from the bootloader in internal flash (0x08000000).

[potatobandit]

I updated the Start Address for "vector table" to be 0x08000000, same issue. The application's .map shows the _FLASH_BEGIN is set to 0x70000000. I tried using that value as well, as that aligns with image in the ST Forum example. This address however cannot be read.

 

[potatobandit]

I am just trying to prove that I can run a basic demo project with this eval board to determine if we want to develop our project with this chip. 

I have cloned the ST Repo for the STMH7RS, performed the Debug Configuration, as the README has specified, then attempted to debug/flash the NUCLEO board. I either gets errors that the elf cannot be loaded or that the memory address cannot be accessed. I've tried these steps on multiple example projects in this repo.

Does ST have any other configuration or documentation that includes any other additional steps that may be needed to get a basic GPIO toggle project running on the NUCLEO-H7S3L8?

[Pavel A.]

>  I either gets errors that the elf cannot be loaded 

Do you still have this error?

[potatobandit]

Hello @mƎALLEm, Thank you for your reply. 
I have confirmed the Boot_XIP.hex is flashed on my board. 

I then flash the GPIO_IOTOGGLE_Appli.elf file and receive this error.

 

[mƎALLEm]

Hello,

From this screenshot we cannot see what you upload as file:

---

@potatobandit wrote:

I then flash the GPIO_IOTOGGLE_Appli.elf file and receive this error.

---

If you download the application with CubeIDE what do you get?

[potatobandit]

In CubeIDE, when I debug I currently have this error.

Debug Configuration is setup as mentioned in the README.md matching the photos I previously posted. 

[Pavel A.]

> Is there an alternative NUCLEO board that is not in the R/S family that I should explore instead?

H7R/S is a new product. You may indeed want to start with a more familiar MCU. In which aspects of STM32 or peripherals are you interested? 

 

 

 

[potatobandit]

My manager purchased the H753ZI to continue our prototyping efforts, since this board has been a dead end for us. 

[Duc]

I have the same issue as you. You can check this one for a solution.

https://community.st.com/t5/stm32cubeide-mcus/break-at-address-quot-0x8000b2c-quot-with-no-debug-information/m-p/827984/highlight/true#M37911