support

Forum Replies Created

Viewing 15 posts - 91 through 105 (of 7,512 total)
  • Author
    Posts
  • in reply to: Debug settings -> Failed to load page #34885
    support
    Keymaster

    Strange. Could you please share a screenshot of the Help->About VisualGDB window?

    in reply to: typo in flags names #34883
    support
    Keymaster

    Thanks, we have fixed it on our side and will include the fix in the upcoming VisualGDB 6.0 Beta 3.

    If you do not want to wait, you can patch it on your side in the %VISUALGDB_DIR%\MSBuild\PropertyPages\armclang\compiler.xml file.

    in reply to: .S files compiled the same way as .c files issue #34882
    support
    Keymaster

    Hi,

    This behavior was added because the recent versions of the ARMClang toolchain have deprecated the armasm executable, recommending to build them with armclang instead.

    You can always restore the old behavior via VS Project Properties -> Configuration Properties -> Keil Settings -> General => Build assembly files with the C compiler = false.

    in reply to: Mismatch in axf/elf file due to -MD -MP -MF flags #34881
    support
    Keymaster

    Hi,

    These options should not affect the compiled program. The exact -MD -MP -MF <dep file> combination tells the compiler to produce a dependency file (.dep) for tracking the headers used by this source file (so that VisualGDB would know which files to rebuild if a header changes). If you omit the -MF option, the compiler will try to automatically derive the dependency file name from the object name (which could be different between different compiler types/versions), so VisualGDB uses it to explicitly tell where the dependency file should be created.

    The -MP option adds extra Make targets for the header files themselves. They are not directly used by VisualGDB, but they won’t affect the code produced by the compiler either.

    You can read more about these options in the GCC documentation. Clang/ARMClang reuses the same syntax.

    That said, if you can confirm that changing these options does change the actual code produced by ARMClang, we can gladly investigate it further.

    in reply to: Problems with adding CppUTest to existing project #34879
    support
    Keymaster

    Hi,

    Based on what you described, including a specific header file from your project into a CPPUtest project results in a build error. VisualGDB doesn’t crash or do anything unexpected – it reports the build error as it is supposed to.

    In general, VisualGDB cannot automatically fix errors in the code, or automatically make different libraries compatible. It’s up to the user to make sure the code they are trying to build does not contain errors, and that different pieces they are trying to put together are compatible.

    You can try exporting the build command line used by VisualGDB into a batch file as shown here and building it manually. Once you reproduce the same build error, you can troubleshoot it just as if it was a regular CMake C++ project not involving VisualGDB.

    in reply to: Missing 'Convert to a Stand-alone Framework' #34875
    support
    Keymaster

    Hi,

    It’s a part of the project template mechanism, so the GUI for managing it is indeed only available starting from the Custom edition.

    That said, the add_bsp_executable() and related commands work with all editions, are fully documented and are expected to remain fully backward-compatible in the future VisualGDB releases. So you can still rely on the VisualGDB’s CMake framework as long as you define the frameworks manually.

    in reply to: Missing 'Convert to a Stand-alone Framework' #34870
    support
    Keymaster

    Hi,

    It’s hard to say why exactly the command would not be visible. Perhaps, you selected a different project type, or are not using the Custom edition.

    If you could attach a screenshot of the entire uncropped Visual Studio window and the context menu with the missing command, we might be able to suggest something.

    in reply to: Intellisense (Github Copilot) #34868
    support
    Keymaster

    Hi,

    Based on what we tested, CoPilot works just fine with the Clang IntelliSense engine. It shows a different language type – C/C++ (VisualGDB) instead of just C/C++, but otherwise works the same:

    Also it appears to only use the current source file contents for figuring out the completion. You can try creating a new Win32 Console Application, adding the ESP32 source file there, and it will generate the same suggestions regardless of the unresolved headers and other errors. Note that the suggestions are very sensitive to the exact location in the file – generating a body for the same function defined at the beginning, end, or somewhere in the middle yielded completely different results in our tests.

    As for why the original C/C++ engine is disabled, it only works with the project types managed by Visual Studio itself (i.e. native VC++). ESP32 projects are managed by VisualGDB – they don’t use the .vcxproj files and instead dynamically show the exact project structure reported by the ESP-IDF build tools. Regular Visual Studio IntelliSense doesn’t know how to work with such dynamic projects, hence we only allow selecting it for the vcxproj-based projects where it can work.

    Attachments:
    You must be logged in to view attached files.
    support
    Keymaster

    Hi,

    It looks like your technical support period has expired. We would be happy to help you, however we would kindly ask you to renew your technical support on the following page first: https://sysprogs.com/splm/mykey

    in reply to: No rule to make target error with Raspberry Pi toolchain #34840
    support
    Keymaster

    Hi,

    This is a known issue between GCC and GNU Make. Some GCC variants produce the dependency files with “c\:\xxx\yyy” path syntax that breaks GNU Make when it tries to recompute dependencies (hence it only happens on the second build).

    The workaround is very easy – simply use CMake with Ninja or MSBuild instead, and it will work just fine.

    support
    Keymaster

    Sorry, there is no quick fix. If you would like to port a CMake-based project to run outside VisualGDB, you will have to learn CMake. If you do not wish to do it, just keep using VisualGDB so that it will handle it for you 🙂

    in reply to: Building project failed #34830
    support
    Keymaster

    This means that at some point some settings in the project were changed to hardcode the toolchain paths, and regenerating the MCU files reset those settings. Without knowing what exact settings were changed, it is not viable to suggest anything meaningful.

    in reply to: Problems with adding CppUTest to existing project #34829
    support
    Keymaster

    Hi,

    The embedded unit test projects are completely separate from other projects. So just including a header file from a different project will not work in most cases. You would need to also have the correct preprocessor macros, include paths, sources, libraries and other relevant settings.

    It is not specific to VisualGDB or unit tests – a good starting point would be to create a new embedded application (non-test) from scratch, move the relevant sources there and fix the build errors. Once you get it working, the same steps will work for a unit test project.

    support
    Keymaster

    Hi,

    The easiest way to get it working would be to use exactly the same CMake command line that is used by VisualGDB. You can export it into a batch file (together with the relevant environment) as shown here.

    in reply to: FreeRtos 10.2.1 and GnuToolchain ARM GCC 12.3.1 #34813
    support
    Keymaster

    Hi,

    Different GCC versions use slightly different optimization logic, so it’s fairly common for a GCC update to trigger previously dormant bugs in the code.

    You can try using the new Live Tracing functionality in VisualGDB 6.0 – it can record various function calls on both old and new versions of the firmware into trace files, where you can compare them side-by-side. It won’t directly show the root cause, but it will point to the moment in time when the behavior starts being different.

Viewing 15 posts - 91 through 105 (of 7,512 total)