Forum Replies Created
-
Posts
-
Hi,
Please try checking the output window (View->Output) for the complete build log. It should contain more information about the error, explaining what exactly went wrong.
If you are not sure, please share the entire log and we will help you understand it.
P.S. Please consider using MSBuild or Advanced CMake instead of GNU Make. It is much better integrated with the VS GUI and will have a much lower chance of random failures due to misaligned settings.
Thanks, this might be related to a glitch that was recently fixed on our side. Please try this build: VisualGDB-5.5.8.3769.msi
No problem, please see this page for more details.
Hi,
We haven’t tested the tumpa adapter directly, but for the directly supported interfaces, VisualGDB can handle multiple instances automatically. Please try locating the %LOCALAPPDATA%\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\QuickSetup\interfaces.xml file and search for Olimex ARM-USB-OCD-H.
You can create a similar entry for tumpa, specifying:
- USB VID/PID/interface
- OpenOCD script file
- OpenOCD command for setting the serial number (should be ftdi_serial, same as for Olimex)
You will also need to update the EDP.XML file (search for Olimex ARM-USB-OCD-H again).
Once you edit the files and restart Visual Studio, Tumpa devices will appear in the “USB Devices” view inside Debug Settings, and VisualGDB will automatically pass the serial number to OpenOCD when it detects multiple instances.
Feel free to attach the edited files here (please pack them into a .zip or .7z file) and we will ship the changes together with the upcoming OpenOCD updates.
No problem, please try this build: VisualGDB-5.5.8.3769.msi
Yes, Quick Debug has its own path mappings stored in the .quickdbg files under %LOCALAPPDATA%\VisualGDB\QuickDebugPresets.
You can edit the Quick Debug path mappings using the path mapping icon in the GDB Session window (item #3).
Hi,
No problem, we will be happy to look into this. Would you be able to share a basic project that reproduces both issues? You can either attach it here as a zip file (make sure you delete the built files), or upload it to an external file sharing service.
Thanks, we have updated VisualGDB to fix the issue: VisualGDB-5.5.8.3753.msi
Good to know it works. BTW, if the file uses the SVD format, it should have been imported automatically together with the rest of the SDK. Feel free to share a link to the SDK and we will make sure it gets handled fully automatically next time.
Thanks for confirming your license, we have linked it to your account.
Indeed, VisualGDB internally uses its own format to define the registers. However, it also supports the SVD file format used for modern ARM devices. Normally, if the register file was not automatically imported, you can click the “locate” link in the Hardware Registers window and point VisualGDB to the SVD file, and it will get automatically converted into the VisualGDB format.
The logic for importing the SVD files is open-source and is available here: https://github.com/sysprogs/BSPTools/blob/master/libraries/BSPGenerationTools/SVDParser.cs
If this doesn’t help, please upload the SDK that did not get properly imported to a file sharing service (e.g. DropBox) and post a link there so that we can investigate it further.
Hi,
This looks like a proxy server configuration issue. Please see the following page for a detailed explanation: https://visualgdb.com/documentation/proxy/
Hi,
This is likely by design, as you have not included the header file declaring the function. This will not cause a critical build error, since C99 does support implicit declarations.
You can read more about this warning, and implicit declarations here: https://stackoverflow.com/questions/32703675/implicit-declaration-of-function-enterchar-wimplicit-function-declaration?rq=1
No problem, we have updated the version parsing logic in this build: VisualGDB-5.5.8.3747.msi
OK, as it looks like something very rare and specific, the easiest way to us to narrow it down would be if you could share the exact steps to reproduce it on our side.
Please try creating a new project completely from scratch, make sure the problem still exists, and then share the complete steps we could follow on our side to reproduce it.
Sorry, we thought you were asking about merging the contents of 2 project files.
Merging the functionality of 2 projects is a complex engineering task that requires the understanding of both projects, the underlying software frameworks and its limitations. Hence, it cannot be done automatically.
If you need help with this, please consider contacting our sales and we will give you a quote.
