Forum Replies Created
-
Posts
-
Hi,
The only other place that could be related is the HostWideSettings.xml file in the same directory. Please try removing that file.
Hi,
No problem. BTW, we have released an update to the Segger J-Link package that will set the flag automatically for new Nordic projects. Feel free to update it via Tools->Embedded Tools Manager.
Hi,
Are you able to install it by downloading and running the installer manually?
Note that the arm-elf toolchain was replaced with the arm-eabi one and you should not need it at all.
Hi,
The sequence we used in the bootloader test program and in the VisualGDB was taken from esptool.py:
self._port.setDTR(False) self._port.setRTS(True) time.sleep(0.05) self._port.setDTR(True) self._port.setRTS(False) time.sleep(0.05) self._port.setDTR(False)
We assumed that it corresponds to the wiring diagram of most of the ESP8266 modules. Have you managed to get it to boot into the bootloader by modifying the sequence according to the schematics?
Hi,
We have actually used a clean Raspberry Pi image when making that tutorial and built the raspicam library using the cross-compiler.
VisualGDB will actually automatically deploy the raspicam library to the same directory as your executable as long as:
- It is specified in the “debugged program” field (see step 26 of the tutorial)
- The project you are debugging references the raspicam project
It looks like in your case something prevents CMake from linking the library (EXEC : CMake error : cmake_symlink_library: System Error: No error). Please try running CMake in verbose mode to figure out what breaks it or run it on a different machine. Perhaps you are using a non-NTFS filesystem and CMake fails to create a symbolic link?
Hi,
Most likely one of the .sshconnection files in %APPDATA%\VisualGDB\SSHConnections got corrupt. Please try removing those files and recreating the connection via Tools->SSH Connections.
Hi,
As a temporary workaround we would suggest creating a symbolic link to the shared header directory near your project directory, e.g.:
cd <project>\.. mklink /d includes c:\common-include-dir
Then you can specify the relative path to the directory (e.g. ..\includes) on the IntelliSense page of VisualGDB Project Properties.
Hi,
You can use VisualGDB to develop C/C++ applications for Beaglebone. VisualGDB uses SSH to build and debug your code.
You can build it either directly on the Beaglebone or by using a cross-compiler provided by us. We recommend starting by following our BeagleBone tutorial.
You can make any application type that is based on C/C++, e.g. Qt-based ones.
Hi,
When you are not using gdbserver, VisualGDB opens a separate SSH console within the main SSH session and redirects your program output to that console using the ‘tty’ command in GDB. Perhaps something about this mechanism is broken? You can see the tty name by switching the GDB Session window to the “All GDB Interaction” mode. Can you reproduce the problem on a clean “Hello, World” project for the same target?
Hi,
VisualGDB parses this file to build a list of all source files in your project and synchronize it with the Makefile.
Please send us the file using our support ticket system so that we could see why it is not being parsed.
Hi,
Do you have the “Reset device after programming” flag enabled in the Debug Settings as described in the tutorial?
Hi,
The “EXEC : CMake error : cmake_symlink_library: System Error: No error” looks very strange. Please try using a newer version of CMake.
If this does not help, please try running it on a different machine.
Hi,
That usually happens when the stack pointer points to an invalid location. Please double-check your MCU type. You can also try using the Memory window to edit the memory at the $sp address to see if the memory there is writable. If you find out that it’s not writable, please change the MCU type to a one with a smaller RAM.
