[support]

Hi,

We simply connected Beaglebone to our internal network with a DHCP server via an Ethernet cable. Then we used the stock firmware listed here and were able to create new projects. If this does not work for you, please let us know which problems you are encountering so that we could help you resolve them.

[support]

Hi,

We do mention supported kernel versions on the kgdboe page.

We are not planning to support older kernels as their popularity is declining over time as people are switching to newer ones.

COM port-based debugging should work. Let us know if you encounter any problems with it.

[support]

Hi,

KGDBoE usually does not work on ARM devices because their network drivers do not implement all the necessary interfaces.

If you want to try it nonetheless, you can simply comment out the code calling the cpu_down() function, as it should be irrelevant on a single-core device. Otherwise, we generally advise using JTAG to debug kernel on embedded ARM boards.

It is hard to say what causes the KernelDebugHelper to crash from your log, most likely some kernel modifications break some assumptions. Please try disabling the “build/install a custom kernel module for collecting module information faster” checkbox. This should eliminate the need to build KernelDebugHelper and use an alternative slower mechanism instead.

[support]

It looks like the configuration file is missing. Normally it should be created when you build the kernel as described in this tutorial. Have you managed to build the kernel successfully?

[support]

Hi,

Wow, thanks a lot for trying this out. This is definitely not something we could have figured out without the hardware. We can certainly add an option to configure the delay in the debugging plugin.

Just to double-check: did you manage to get the bootloader test tool to repoer a successful sync? The output you shared still says “timeout reading reply”. Does it get even more reliable if you increase the delay to 100 ms?

[support]

Normally the ‘None’ item type is used to add Makefile and the .mak files to your project. “None” indicates that the file does not participate in the build. If your VS does not recognize it, most likely your installation is corrupt. Please try repairing it via Add/Remove programs.

[support]

Hi,

The ST-Link programmer uses a special high-level interface that may be specific to ARM cores. If you are looking for an inexpensive JTAG programmer that will work with ESP8266, we would support anything that is FT2232-based (e.g. Olimex), as it essentially exposes the low-level JTAG interface to OpenOCD and does not impose any limitations.

[support]

Hi,

If you don’t want to use Makefiles, you can create a file called build.bat, place the compilation commands there and switch the Build System on the first page of VisualGDB Project Properties to custom. Then you can simply point it at your .bat file and VisualGDB will run it for you each time you build the project.

Your Linux command line (g++ -std=c++11 -I/usr/local/lib -I/usr/lib -I/usr/local/include/raspicam -c /home/pi/projects/wicam/wicam.cpp -o /home/pi/projects/wicam/wicam.o) will need to be adjusted to use the cross-compiler:

arm-linux-gnueabihf-g++ -std=c++11 -I=/usr/local/lib -I=/usr/lib -I=/usr/local/include/raspicam -c c:/projects/wicam.cpp -o c:/projects/wicam.o

If you have troubles setting up the manual build with VisualGDB, let us know so that we could share some screenshots.

[support]

OK, let’s try to simplify things and do them step-by-step. When you create a new Linux project with VisualGDB targeting the same machine (not using gdbserver), does the output work as expected?

[support]

Hi,

The only other place that could be related is the HostWideSettings.xml file in the same directory. Please try removing that file.

[support]

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.

[support]

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.

[support]

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?

[support]

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?

[support]

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.

[Author]

Posts