- This topic has 2 replies, 2 voices, and was last updated 3 years, 11 months ago by
.
-
Posts
-
I’m developing a project with an STM32H7 microcontroller that will perform heavy and complex mathematical computations. So far, I’m very pleased with VisualGDB, it has some annoyances but overall it does its job well. It’s a sure buy.
Because of the heavy computation I need to verify the code on the device while debugging. There are many options but I’d like to interfere the least with the device for testing. I only have 112 KB flash memory, I cannot keep test code in the final production code, and also test code tends to change the behavior of the device (changes in instruction timing etc). So, my approach would be to perform a memory dump at certain points via SWD and verify the memory on the host system. It would be so much easier.
Now, the question is.. can I do that? Via Visual Studio script? Something? Automated. Or issue a gdb request command? The CPU is in stop/break mode, how can I access the memory and possibly registers in an automated way?
Hi,
VisualGDB itself does not provide any special commands for programmatically dumping the memory, however you might be able to achieve this via gdb commands (since it’s not a VisualGDB feature, the specifics are not covered by our technical support, but we can do a detailed research and share detailed instructions via our consulting track if you prefer).
On the VisualGDB side, you can issue GDB commands via the GDB Session window, or create your own gdb scripts (e.g. with actions bound to breakpoints) and load them by adding the “source” command to VisualGDB Project Properties -> Additional GDB Commands.
You can also try using the Embedded Integration Tests. They support running arbitrary gdb commands.
- You must be logged in to reply to this topic.