Forum Replies Created
-
Posts
-
Hi,
Yes, you can add “VERBOSE=1” to make (not CMake) command template and rebuild the project. This should get CMake to print the command lines it is using.
Hi,
Thanks, we have added this to the backlog and will consider supporting it in the next version of VisualGDB (after v5.3).
Hi,
It looks like the arm_neon.h file contains some checks that deem the current configuration (determined from checking built-in preprocessor macros via #ifdef’s) invalid. The best way to investigate it would be to look into the file that produces the error and see which exact #ifdef tests it performs.
Hi,
The easiest way to do that would be to right-click on the project in Solution Explorer and select VisualGDB Project Properties. Then go to the Makefile Settings page and edit the CFLAGS via GUI. VisualGDB will automatically update the related Makefiles and reconfigure IntelliSense.
Please note that if you are using MSBuild, you would need to use the VS Project Properties instead.
Hi,
This error means that the machine where you compile your code is missing the gdb debugger. You can normally install it by running “sudo apt-get install gdb” or “yum install gdb”.
If you are using a cross-compiler, you would need to open the VisualGDB Project Properties and manually specify the location of the GDB executable that matches your cross-toolchain.
Hi,
Unfortunately this is a bit tougher one. As TI does not ship official register definitions, VisualGDB gets them from parsing the header files and this mechanism is not as precise as parsing a machine-readable definition. Currently our parser uses common register definitions for the entire device family and does not remove registers that are not available on all devices.
Unless this causes some serious issues (e.g. disrupts program flow due to collision with some other registers), we recommend simply ignoring the extra registers.
Hi,
The easiest way would be to upload the file to DropBox or other file sharing service and send us a link via our support form.
Hi,
We don’t offer any live support within our regular pricing, but you can submit the screenshots via our support page. We usually respond with detailed instructions within 24-48 hours.
Hi,
Good to know it works now. In case anyone else runs into the same problem, this usually happens when the build actually does not succeed and the main executable is not created.
Hi,
This could be caused by optimization. Please enure you have the “-O0” flag in the project settings.
You can diagnose this by injecting asm(“nop”) statements in the code and trying to set breakpoints there.
If your board is controlling a motor, it could make the power supply unstable and cause weird behavior like the one you are describing. Please try disconnecting the actual motor and see if the problem still occurs. If not, you would need to modify your board schematic to stabilize the power.
Hi,
You can do this by editing the %LOCALAPPDATA%\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\QuickSetup\interfaces.xml file.
Hi,
Please double-check that you have the access to the specified file and that it’s not open in any other program (sometimes refreshing the cache while Clang IntelliSense is still scanning the source gets this error). If nothing helps, please try closing Visual Studio and deleting the file (or the entire 0002 folder) manually.
Hi,
This is by design unless you built OpenCV from sources yourself (or manually downloaded/installed debug symbols if your distro ships them). We would recommend building OpenCV from scratch (e.g. by following this tutorial). The new CMake Project Subsystem in VisualGDB 5.3 should make it much simpler as well.
Hi,
Yes, the problem occurred because our register parsing was confusing offsets and absolute addresses. We have fixed that.
The window bug should be fixed in v5.3 Preview 2 (or you can simply restart VS and run the update again).
