Hi,

It looks like your ESP8266 Arduino core might be corrupt. The easiest way to fix this would be to delete it and let VisualGDB automatically download the latest version of the core and all related tools.

Based on your log, you are still using the old version of the ESP8266 core (2.4.1):

C:\Users\Sharon\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.4.1

Please follow the instructions from our previous reply and actually remove the core so that VisualGDB can install the latest one (version 2.5.0). We have checked it with the WeMOS D1 R1 target and it did build out-of-the-box.

Thanks for clarifying this. Removing the Arduino IDE from the system was not necessary, as the problem is likely caused by the ESP8266 Arduino core that we suggested to delete (if you are not familiar with this term, please see this explanation on StackExchange).

The directory of the core is actually mentioned in the error message you posted, so it should be very straight-forward to locate it.

That said, to reduce the chance of interference from other components you might have installed earlier, please try deleting (or actually first renaming) the entire Arduino packages folder:

C:\Users\Sharon\AppData\Local\Arduino15

This will ensure that there are no leftovers and you should be able to create the project per our tutorial.

Unfortunately, we could not reproduce the problem you described. Most likely it is caused by a corruption of some software components on your side. Please try installing VisualGDB on another machine and follow our ESP8266 tutorial to create a project.

The problems you mentioned with STM32 arised from creating a non-relocatable type of project (despite the other type clearly shown in our tutorials) and ignoring the error messages that clearly showed the paths of the files that were not relocated, despite the editing instructions provided by our support. We do our best to make VisualGDB support many different scenarios and platforms and also publish tutorials describing various different setups, however it is beyond our capacity to guarantee that VisualGDB will work when the necessary setup steps shown in our tutorials are not followed.

The problems with ESP8266 you mentioned look like a corruption of a 3rd-party component (ESP8266 core) that is specific to your machine and unfortunately cannot be reproduced on our side (or fixed on the VisualGDB level).

The last STM32 problem you reported is caused by trying to manually build the STM32F3-specific peripheral driver for the STM32H7 device, despite VisualGDB having a clear and automatic system for selecting the drivers and libraries that are compatible with each device type.

We understand that you were looking for something different and wish you the best in finding the tool that will suit your requirements, however it looks this is not something we could offer.