[support]

Hi,

This might be tricky as the solution-level variables are not available to some parts of the build logic. Could you please clarify where exactly would you envision using this variable so that we could see if it could be supported?

[support]

Hi,

Thanks for the link. That version actually uses a completely custom makefile layout, so minor glitches are to be expected. If manually copying the file works, this is the recommended way to go around it.

Regarding HTML, we could add an option to show the contents of additional manually specified directories in Solution Explorer for ESP-IDF projects. Would that work for you?

[support]

Hi,

That should work as well. As long as the GNUTargetID is set properly, the toolchain ID and version can be set arbitrarily – VisualGDB will still recognize the toolchain properly.

[support]

Hi,

Yes, we always twit about new tutorials and blog posts. Please consider following us on Twitter to stay tuned.

[support]

Hi,

Sorry for the delay, the Espressif toolchain has a few rough corners we had to investigate before publishing the integration instructions.

First of all, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.3.2263.msi

Then follow the instructions below to integrate the Espressif’s toolchain:

1. Unpack the toochain to an arbitrary directory on your machine and create a toolchain.xml file there with the following contents:

   <?xml version="1.0"?>
   <Toolchain xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <ToolchainName>ESP32</ToolchainName>
    <ToolchainType>Embedded</ToolchainType>
    <PathDetectionKeyStrip>0</PathDetectionKeyStrip>
    <GNUTargetID>xtensa-esp32-elf</GNUTargetID>
    <BuiltInBSPs>
    <string>esp32-bsp</string>
    </BuiltInBSPs>
    <ToolchainID>com.visualgdb.xtensa-esp32-elf.external</ToolchainID>
    <BinaryDirectory>opt\xtensa-esp32-elf\bin</BinaryDirectory>
    <Prefix>xtensa-esp32-elf-</Prefix>
    <Make>make.exe</Make>
    <IsCygwinBased>true</IsCygwinBased>
    <GCCVersion>5.2.0</GCCVersion>
    <GDBVersion>7.10</GDBVersion>
    <LIBCVersion></LIBCVersion>
    <BinutilsVersion>2.25</BinutilsVersion>
    <Revision>1</Revision>
    <MinimumEngineVersion>5.4</MinimumEngineVersion>
    <Comments>ESP-IDF 3.0</Comments>
   </Toolchain>

2. Copy the IDFCheckouts.xml file from our toolchain directory to the Espressif toolchain directory. This will ensure VisualGDB can find the esp-idf checkouts.
3. Copy the esp32-bsp directory from our toolchain to the Espressif toolchain directory. This will get the debugging plugin to be recognized.
4. Do not copy the esp-idf\v3.0 folder from our toolchain. Instead, create a recursive checkout of the Espressif repository manually using git from their toolchain. The 2 toolchains use different set of libraries and copying an existing checkout with prebuilt files will prevent the build from completing correctly. Also due to differences between the way git is installed in 2 toolchains, our ESP-IDF checkout manager won’t be able to use the git executable from the Espressif toolchain.
5. Open the ESP-IDF project wizard. On the toolchain page select “find a toolchain by locating gdb.exe”, then change the filter from “*gdb.exe” to “toolchain.xml” and point to the toolchain.xml file in your toolchain. This will add it to the VisualGDB toolchain list.
6. Create the project.
7. Open the VisualGDB Project Properties and change the path style from /cygdrive/xxx to MinGW (/c/xxx).

Now you should be able to build and debug the project as expected. Advanced functionality like opening the Cygwin shell might still not work though due to differences between toolchains.

Hope this helps. Let us know if you run into any problems or need further details.

[support]

Hi,

Sorry, we don’t have a specific deadline for this yet. The new SDK appears to merge the IoT functionality into the mainline SDK, so it might require extra effort on our side to ensure everything works smooth together. We will post an update on the forum once the new release is available though.

[support]

Hi,

Most likely this service was added after our major internal update, so it did not get picked up automatically by the BSP generator. As a workaround, please try adding the corresponding .c file to the project manually.

We might be able to address it in the upcoming SDK 15.0 update, although we cannot promise any specific deadlines for it yet.

[support]

Hi,

This code looks totally OK from the gcc standpoint. If might not compile if the header defining U8 is not included, but otherwise it should work.

Please feel free to attach the exact error message you get so that we could give you better advice.

[support]

Hi,

If you are using the Custom edition, you can use the Build Customization page of VisualGDB Project Properties to add steps for deploying custom binaries after build (or Debug Customization page to deploy them before debugging).

[support]

Hi,

Thanks for the suggestion. We will monitor the future development of the TrueStudio and will consider importing projects from it if ST keeps on maintaining and supporting it.

[support]

Hi,

No problem, we have resent the confirmation email. Please check your inbox.

[support]

Hi,

Please let us know the email address associated with your license key so that we could check your support status.

[support]

Hi,

According to our records, the confirmation was sent to the email associated with your forum login. Please double-check your spam folder. As Avangate (our payment processor) has recently rebranded to 2Checkout, your previous email sorting rules may not work properly.

[support]

Hi,

It looks like your project relies on some functionality that is not present in our toolchain. The only known workaround to this would be to try downloading a toolchain from a different source (there are a few independent MinGW builds available online) or switching to Cygwin that is actively maintained, patched and is fully supported by VisualGDB.

[support]

Hi,

OK, no problem, if we could reproduce this, we should be able to fix it or suggest a better workaround. Please let us know if you are using MSBuild or GNU Make (if you could send us a sample project demonstrating the issue, it would be the best).

[Author]

Posts