Develop applications based on STM32H7RS MCUs using VS Code.

[taokhe]

Hi everyone, I am developing an application for the NUCLEO-H7S3L8 kit using VS Code with the STM32 VS Code Extension. I have successfully built both the 'Boot' and 'App' projects.

Currently, I am struggling with flashing the 'App' project firmware into the external Flash memory. In STM32CubeIDE, selecting an External Loader (.stldr) is very intuitive within the Debug Configuration, but I haven't found the equivalent setting in VS Code for the STM32H7RS series.

Could you please guide me on how to configure VS Code to recognize the External Loader and the proper workflow for flashing code to external memory for this specific MCU?
PS: On STM32cubeIDE, I'm referring to this example: https://github.com/ST-TOMAS-Examples-ExtMem/stm32h7rs_ospi/tree/main. Now, using the same example, how would I implement it if I used VS Code as my development environment?

[Cartu38 OpenDev]

@taokhe see https://community.st.com/t5/stm32cubeide-for-visual-studio/debugging-stm32h735g-dk-with-external-flash-fails/m-p/856055#M1483

[Sambsc]

Im also using h7rs and just started building cube cmake projects with vscode yesterday. If you try flashing your app .elf with cube programmer and it fails u likely have not linked it correctly. In your build logs verify your app memory stats show 0x70000000 not 0x20000000 or 24.. or 90.. in your app cmakelists search for ".ld" to see where you have linked your app to be flashed. Also you need to ensure you've configured your xspi2 peripheral in cubemx. Its actually easy enough thank god. Find xspi2 in "pins and config" and have a look at the options. It will be red if its wrong. I've managed to debug the io toggle sample in bootloader but haven't successfully jumped to app yet. Happy enough with what I achieved in a couple of hours, excited about running cube apps with vscode instead of the mindmelt ide :grinning_face_with_sweat:. Hope this gets u a little further.