Custom debug stub issues and function suggestions

Sysprogs forums Forums VisualGDB Custom debug stub issues and function suggestions

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #28968
    chinanier
    Participant

    I am using visualgdb for embedded development. I am using a non-standard debug stub. There are three problems:
    1. “Program and Start Without Debugging” did not find the custom command configuration, and the “Program offset address” cannot be configured. It is not applicable when I hope to program a font file to the specified offset address
    2. Using “Full-custom mode” Debug setting, you cannot customize the commands that gdb stub needs to execute before debugging (in the case that gdbserver does not support the “mon” command)
    3. No menu item (custom command tool) that can expand like “firmware package” is found

    #28970
    support
    Keymaster

    Hi,

    You can do that with a custom debug method definition. The easiest way to do it would be to select PyOCD in the debug settings, and then locate and copy the %LOCALAPPDATA%\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.pyocd directory under a different name. You can then edit the EDP.XML file inside the new method directory to change the startup commands, stub location, or even define extra configuration properties.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.