[support]

Hi,

Thanks for letting us know. We actually used the latest SDK from Espressif. Could you post a link to the update you have used so that we could include it in our toolchain as well?

[support]

As we mentioned before, there is not a lot of difference from turning on the compression. You can close the Threads and Call Stack windows in Visual Studio, then it will query less things and the overall performance should increase.

You can also try using a cross-toolchain with gdb running on the Windows side. This may improve the performance a bit more.

• This reply was modified 9 years, 2 months ago by support.

[support]

Hi,

The wizard layout depends on whether you are using a cross-compiler and where do you store the source files. Please provide us more details on the previous choices in the wizard so that we could check why it is disabled.

As an alternative solution you can import the project from folderA, select “Do not import files to Solution Explorer” and then add the root folder manually via Add->Import Folder Recursively. This way the main source directory from the VisualGDB’s point of view will be folderA, but the Solution Explorer contents will look like you have imported the parent folder. Let us know if that works.

[support]

Hi,

We are not aware of this problem. Where did you get that linker script? The ones shipped with VisualGDB should not contain any ‘mdata’ sections. Perhaps there is a newer version of the script available?

[support]

Good to know it works. Note that you can simply put the library directories in the ‘library directories’ field and library names without ‘lib’ and ‘.a’ or ‘.so’ to the “library names” if you want to simplify your setup.

[support]

Hi,

Yes, the gdb stub sometimes produces strange results. Generally the ESP8266 is much less stable than the ARM devices like CC3200, albeit much less expensive.

We would recommend trying to get JTAG to work if the gdbstub does not work. We have just released a new toolchain version that improves the JTAG debugging stability by resetting some of the registers that interfere with debugging. Please try using it and let us know if it works.

[support]

Hi,

We have just released an updated version of our ESP8266 toolchain with improved stability. Could you please try it and let us know if the problem still exists?

[support]

Hi,

Thanks for pointing that out. It does indeed look like we shipped the old one. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.4.683.msi

[support]

Hi,

VisualGDB is using the version 1.6.0 (June 12 2015) that should include that fix. If it does not work with your machine, most likely it is another bug of libssh2. We will consider updating to 1.7.0 in one of the next VisualGDB releases.

[support]

Hi,

The _estack and main() errors are not critical and can be ignored. They are displayed because the structure of an esp8266 image is different from many other architectures and some auxiliary features do not work with those. It should not interfere with the debugging. Does the LED actually blink? Are you able to stop at breakpoints?

[support]

Hi,

We are not using OpenSSH. We are using libssh2, which is a different library.

[support]

Hi,

Do you see the programming progress bar while VisualGDB is programming the module? If yes, the connection is OK and the problem is with the SPI FLASH.

We have received feedback that some of the modules come with very unreliable FLASH chips that have troubles being reprogrammed. We would recommend getting a dev board from Olimex as they seem to be using better SPI FLASH chips.

[support]

This might the case if the error output format of the compiler has changed. The regexes are indeed case-sensitive. Please try moving the file out of the way, building the project to see the raw error message and then using the online regex debugger to see whether the regex in the file matches the output. If not, you should be able to easily adjust it. Let us know if you need help.

[support]

Hi,

It looks like you are trying to add header files (.hpp) to the library list. This won’t work as those are different types of files. Header files contain definitions of your functions and you should be referenced by adding their directories to the Include Directories field. Then the #include<> directories will handle them properly. When this is not setup properly, you will get errors like “cannot open file xxx.h”.

Library files (.a or .so) contain compiled implementations of your functions and should be added to the Library Names field (without the ‘lib’ prefix and extension, more details here). When some libraries are missing, you will typically get errors like “unresolved reference to xxx”.

We would recommend first solving the problems with the header files (the code should at least compile and then get stuck at ‘unresolved reference’ problems) and then add the missing libraries to VisualGDB Project Properties. You can find the libraries by simply searching the OpenCV build directory for .a and .so files.

[support]

Hi,

This is not supported directly, however can be easily achieved with per-user variables: simply set them so that other users will have an irrelevant mapping (like /tmp/suchpath <=> c:\nosuchpath) and you will get the same effect.

[Author]

Posts