I’m using an STM32F7 and the board I am using is programmed using a HEX file compiled from my Continuous Integration (CI) server. The CI server has different paths to all of the STM32 HAL library than my local machine, so the final binary is not the same as my local compilation since some of the paths are encoded into it. Since the binary from the CI server is what gets programmed on the board, is there any way I can “attach to running embedded firmware” from my machine onto the programmed board? Is it possible to take the MAP or ELF file from the CI server and put that on my machine to allow the “attachment” to work better? Or perhaps a way to not have the paths be encoded (although I dont think there’s an easy way to do this).
The easiest way to get it working would be using Quick Debug. Once VisualGDB encounters mismatching file paths, it will show special GUI for locating them on your machine, and will guide you through setting up the path mappings.
You can disable the FLASH loading during Quick Debug by manually removing “load” from the startup commands in the Advanced view of the debug method.