Forum Replies Created
-
Posts
-
Can you please create a new project with the default debug method (e.g. GDB simulator) and send us the created files? This will help us analyze your problem and suggest a solution.
Additionally could you please check your firewall settings? Visual Studio process needs to have internet access in order to download additional packages. If this is not possible, we can provide you with instructions on manually downloading and installing those packages.
Hi,
Which toolchain are you using? Please use our arm-eabi toolchain (it is installed automatically when selected on the toolchain page). Please also note that OpenOCD/J-Link is available starting from VisualGDB 4.0 and won’t work on 3.x.
How often does this happen? We have encountered similar behavior on some versions of MacOS and it looked like a bug in their end of SSH. Could you build newer GDB from sources in your home directory and let VisualGDB use it explicitly?
Hi,
Thanks for your explanations. We have fixed it in Beta 3. We have also added an option (Tools->Options->VisualGDB->General) to override the default file masks used when creating projects.
Hi,
Thanks for reporting this. Could you please let us know how what exactly you are doing to browse the folder? Please feel free to attach a screenshot or a step-by-step description.
Hi,
First starting the app and then attaching to it is the default behavior of the Android debugger.
You can override it by selecting Android->Debug Options->Debug App Startup in Visual Studio.
Once you select that option, starting debugging will take slightly longer, but all your initialization breakpoints will be hit.Hi,
Thanks for reporting this. Please feel free to report further bugs on this forum or simply send emails to support.
There was indeed a bug on our side. The build/debug customization pages were intended to appear in Custom and Ultimate editions only and activating them in other editions crashed the dialog as the underlying logic was not present.
We have updated the installer.Hi,
Thanks for reporting this. We could not reproduce it on our side. Could you please send us your .vgdbsettings file so that we can diagnose this further?
Hi,
Thanks for reporting this. The project settings from the previous versions of VisualGDB are saved to the -.old file. Simply change the extension back to .vgdbsettings to restore it.
Hi,
Unfortunately this is not possible in the currently available release, however it will be significantly improved in the upcoming release.
The beta is scheduled to be released within a month from now.Hi,
Currently the /rebuild command simply executes a clean sequence followed by the build sequence.
You can safely ignore the warning message after replacing the build commands. As long as you keep the “primary output” point to the .vgdbsettings file all VisualGDB functionality will work.Hi,
Yes, VisualGDB expects the single-threaded output as it’s the only way to detect the full path of files (so that Visual Studio can show them) when GCC reports the relative path. If this is not a problem for you, you can safely ignore those warnings.
Hi,
You can run GDB manually (msp430-gdb.exe
) and run the following commands to program it:
target remote :
loadYou can automate it using a script. Alternatively you can change the makefile to produce Intel HEX file instead of a binary file. Look for the line that calls objcopy and change it so that it produces Intel HEX format instead of bin. Run msp430-objcopy.exe –help to get more information about supported formats.
Hi,
This still looks like an incompatibility between your programmer and the msp430.dll. It is a known issue for Olimex devices (e.g. see https://forum.sparkfun.com/viewtopic.php?t=13349).
Please try copying ALL dlls from the Olimex directory (also hil.dll) into the msp430 bin directory. If this does not help, please also contact Olimex support asking whether your programmer supports debugging at all and whether it needs a firmware update. Please also inquire whether they provide a GDB server.The download errors can be caused by various factors (e.g. what is the size of the BIN file?) but should not be related to the “Device not found” bug as device detection happens before downloading the firmware.
