[G40]

Many thanks Ket.

Colour me impressed. Works right out of the box with an SSH connection to a Beaglebone. Super.

[G40]

Thanks Kets,

I assume the work-around is to specify the full path to VGDB make?

[G40]

Hello Kets.

Thanks. A few more questions …

I’m trying to set up a project using a different toolchain.

Here’s an example. I’ve got an installation of gcc tools from a vendor that I want to use under VGDB. I specify the path to the correct bin folder but leave the ‘Use GNU Make include with VisualGDB’ checked. Press OK. This returns me to the main Project Wizard page. Then when I hit ‘next’ the Wizard tries to validate the toolchain and it appears to fail at make (though I cannot tell as the error message is not very clear). Please see attached files.

[attachment=1:2bmz941y]vgdb-ext-tools.jpg[/attachment:2bmz941y]

[G40]

Hello Kets.

1. Re GCC include paths. Are these relative to the target source file or the project/solution file?
2. What is the time frame for the improved feature? It’s the kind of thing that drives me bats,
2. What then does .xml do?
3. Attached is a snap showing the JLink target question. What appended the (SPIFI)?

Many thanks

Help much appreciated.

[Author]

Posts