support

Forum Replies Created

Viewing 15 posts - 2,536 through 2,550 (of 7,852 total)
  • Author
    Posts
  • in reply to: Unit test xml report not Junit compatible #26737
    support
    Keymaster

    Hi,

    Although VisualGDB cannot directly generate a Junit-compatible output, it can be configured to generate the outputs in the Visual Studio/MSTest test report format.

    You can do this via the following command line

    VisualGDB.exe /runtests <...> /vsoutput:<output file>

    As both JUnit and MSTest test report formats are very popular, there are various open-source translators between them, so we would advise simply running one of them after VisualGDB returns.

    in reply to: Visual gdb option disappeared #26736
    support
    Keymaster

    Good to know it works. If you encounter further problems, feel free to get back to us.

    in reply to: ESP32 Static/Shared Library Wizard or Project #26735
    support
    Keymaster

    It looks like you are not using the ESP-IDF component GUI. Please ensure you use the Advanced ESP-IDF project wizard as suggested by VisualGDB and shown in this tutorial.

    in reply to: Arduino STM32 error finding file #26734
    support
    Keymaster

    Unfortunately we are not able to guarantee that every possible combination of Arduino targets and libraries will work. Please consider posting on the Arduino forums for further support.

    in reply to: Failed to debug if multiple STM32 are connected #26733
    support
    Keymaster

    We have determined that the problem occurs in a 3rd-party component: OpenOCD. Please contact OpenOCD support for further help with this.

    in reply to: STM32H747XI & Dual Core Debugging #26719
    support
    Keymaster

    Hi,

    We are currently preparing a tutorial on the multi-core STM32 devices, so if the time permits, please consider waiting for 1-2 weeks and we will publish detailed steps to get it working.

    Although debugging both cores within the same debug session is not possible due to gdb limitations, it should be possible to debug them from 2 independent Visual Studio instances, as long as your debug probe supports it.

    If you need to get started faster, please consider creating a project using STM32CubeMX and importing into VisualGDB and then debugging it with Segger J-Link. The J-Link debug probe comes with its own low-level software that works out-of-the-box with multi-core devices and requires no special configuration.

    in reply to: Get CPU device from code (build defines) #26718
    support
    Keymaster

    Hi,

    If you are using MSBuild, the output verbosity is controlled by Visual Studio itself and can be configured via Tools->Options->Projects and Solutions->Build and Run.

    You can also find the preprocessor macros in the .rsp files inside your build directory (search for -D<macro> strings).

    Normally, something like this would work:

    #ifdef STM32L431CC
    Report.DeviceType = MyIDForSTM32L431CC;
    #elif defined (...)
    Report.DeviceType = MyIDForSomethingElse;
    #else
    #error Unknown device. Add a check for it above.
    #endif
    support
    Keymaster

    Hi,

    Sorry, the latest ARM toolchain (gcc 9.2.0) is based on the official GNUARM toolchain and does not contain automatically discoverable source packages.

    We are planning to address this in one of the next toolchain updates, however currently the workaround would be to either download the sources from the ARM site manually, or to switch back to gcc 7.x that includes the automatic source packages.

    support
    Keymaster

    Thanks for renewing your support. VisualGDB indeed has an IntelliSense cache located in the CodeDB directory (the exact location depends on the project type). Please try closing the solution, deleting the CodeDB directory and reopening it.

    If it doesn’t help, please clarify what exactly do you mean by “all links are lost”. If you could attach a screenshot highlighting the problem, it should be easy for us to understand what is going on and suggest a more specific solution.

    support
    Keymaster

    Thanks for clarifying this. Please try the latest VisualGDB 5.5 Preview 2. Each time you open a solution containing VisualGDB projects, it will automatically find missing toolchains, BSPs and other items and will show a list of them, allowing you to download or substitute them. You can then use the substitution GUI to find and import the custom toolchain (that should already contain the CustomToolchain.xml file). As long as the ID is the same as the project file references, the .vgdbcmake file won’t need to be updated.

    The FindToolchain.props file is not used by Advanced CMake projects. It is only required by VC++-based projects (e.g. MSBuild, GNU Make, etc) and is regenerated automatically based on the known toolchains and other packages each time you start Visual Studio (or specifically, start using VisualGDB functionality inside a newly launched VS instance).

    Also, if  Team Settings looks like a good fit for you, we can easily update it to allow packaging custom toolchains and automatically installing them on all relevant machines.

    support
    Keymaster

    Hi,

    Thanks for the suggestion. Indeed, importing the toolchains via the Package Manager window is geared towards embedded toolchains. As a workaround, please consider one of the following options:

    1. Try importing the toolchain from the toolchain selector (i.e. anywhere where you would normally change the toolchain, such as the the project wizard or VisualGDB Project Properties). This will automatically use the toolchain type based on the project type and will allow editing various toolchain parameters.
    2. You can also simply edit the Toolchain.xml file after the toolchain was imported. The toolchain type and ID are stored in separate XML elements that should be very easy to modify. If you later try to import a toolchain that already has a Toolchain.xml file (or CustomToolchain.xml), VisualGDB will ask whether you want to reuse the existing toolchain definition instead of regenerating it.
    in reply to: VisualGDB with VisualAssist #26703
    support
    Keymaster

    Unfortunately, as you have created a high amount of highly specific inquiries (45 topics with 88 posts altogether), we are not able to provide a detailed reply. The documentation about VisualGDB’s and Visual Assist features is available online.

    We have to prioritize our support based on the amount of affected users and are not able to provide any further details in this case.

    in reply to: VisualGDB with VisualAssist #26701
    support
    Keymaster

    Sorry, we do not support Visual Assist.

    support
    Keymaster

    The new build should report missing platforms as well, however only if they are known to VisualGDB (i.e. listed in one of the platform_index.json files configured via Tools->VisualGDB->Arduino->Package index URLs).

    in reply to: Visual gdb option disappeared #26698
    support
    Keymaster

    Please try clicking “Yes” in the message asking to repair the environment variable and restart your computer. If nothing helps, please make sure you follow all steps from the troubleshooting guide and if this doesn’t help either, please let us know exactly what happens on each step (which files are present, what you have deleted/modified) and we will help you resolve it.

Viewing 15 posts - 2,536 through 2,550 (of 7,852 total)