ESP8266 Wizard 1.3.1 OpenSource for Visual Studio 2013, 2015 & 2017 with FlashTool, Intellisense and VIDEO Tutorial

[Fleuve]

This tool is incredible you made a great work, as a suggestion, is there any chance to add the MESH_DEMO to the supported SDKs and examples?

Ok, the exercise can be more easier that you think, but i need to have more information:

• Where i can find the proper example?
• Does RTOS or NON-OS Compatible?

If you can respond to that, you can see if the current version gonna support it.

• First open your installation folder. (C:\Program Files (x86)\Relentless.rad\ESP8266Wizard\ESPressif)
• Go inside Non-OS or RTOS Folder
• Choose your version folder
• Go inside Example Folder
• Copy your MESH_DEMO project inside example folder (respect folder structure ...Examples\mesh_demo)
• Restart your visual studio and your wizard (example folder must be listed now)
• Adjust your -l parameter by looking makefile inside Mesh_demo (if exist - see video tutorial).

If you need more assistance, tell me...

thanks..

[lele]

visualGDB ( https://visualgdb.com/tutorials/esp8266/gdbstub/ ) has some example usage of serial debugging with gdb stub.
May be could help download the trial.

[yellowbit]

Hi, my antivirus reports a virus (URL:Mal) under the download link (http://www.mediafire.com/file/xh58jgi4x ... 1.2.8b.exe) Can you check it, please?

[Fleuve]

Hi, my antivirus reports a virus (URL:Mal) under the download link (http://www.mediafire.com/file/xh58jgi4x ... 1.2.8b.exe) Can you check it, please?

Sorry, but on my side everything is perfect. I scan with malware-byte, Eset NOD32 and windows defender.

Which one did you use?
I recommend you to scan your system with malware-byte and try again.

Hope that will help.

[skibeest]

After my post from yesterday I have done some more investigation and discoverd some differences between Visual Studio 2015 and Visual Studio 2017 as well as between some SDK versions (1.5.4, 2.0.0 and 2.1.1).

The first tests I did was with an empty project (which isn't actually empty but a small application):

1. SDK1.5.4: VS15 and VS17 OK
2. SDK2.0.2: Function user_rf_cal_sector_set as well as a reference to "user_interface.h" had to be added. After inclusion of both building the executable was OK for both VS versions.
3. SDK2.1.1:
   
   1. compiling failed: user_main.c (52,5): error: passing argument 1 of 'ets_timer_disarm' discards 'volatile' qualifier from pointer target type [-Werror]. This is a warning so I cancelled the error as warning option. The warning should be avoided in the code however. Occured both with VS15 and VS17.
   2. After changing the warning option I got the linking error as with SDK2.0.0. After adding the extra code I could build the app with no errors in VS15.
   3. VS17, however, is a different story. After changing the warning option I got a new error: "string.h" not found (file osapi.h).I also got some additional errors as result of the missing header file. But then something strange happened. Linking started (while there were compilation errors) and I got only 1 error: 'user_rf_cal_sector_set' missing. Next I included the additional code and the build of the app was succesfull but the compiler still reports errors.

The second test I did was with the example app at. With VS15 the app could be build without error for both version 2.0.0 and 2.1.0 after adding the airkiss lib.With VS17 I had the same results with version 2.0.0. version 2.1.0 however resulted in a link error: '.rom0.text' will not fit in region 'irom0_0_seg'. I can't explain the differences. Same code, same compiler, same linker.
I have compared the object files and noticed a difference: user_main.o is with VS15 15036 bytes and with VS17 15504 bytes, for at_upgrade.o it is 25476 and 24896 respectively. Also the generated Libuser.a differs: 40910 versus 40798).

I hope this information is usefull to you to maintain the tool, I like it. For now I will stick to VS15. Hope the problems are solved swiftly.

[Fleuve]

After my post from yesterday I have done some more investigation and discoverd some differences between Visual Studio 2015 and Visual Studio 2017 as well as between some SDK versions (1.5.4, 2.0.0 and 2.1.1).

For the moment, I've stop to develop, because I'm own a motel and it's summer time. But, I transfer inside the bug list and gonna check soon (in falls). For the moment, i didn't test version 2.1.1, but I'm gonna check for major update of firmware (NON-OS, RTOS and MESH_DEMO).

For '.rom0.text' will not fit in region 'irom0_0_seg' error... .check for size of rom (since 1.5.0 or before. 512kb was too small... try 1024kb)

Thanks.

[quickshat]

Hi,

i've tried to use the 1.28b version of the wizard but: Visual Studio does not let me include things from SDKs folder.
I have already checked project import settings and the paths are all included by default.
Also these paths are correctly included and i am able to open them with my explorer.

But if i hover on a

Code: Select all

#include <sdk_relevant_header.h>

, Visual Code only tells me that it was unable to find .h file in the first path of the settings include-path list.

My include-path list looks a bit like this:

C:/some_visual_studio/path
E:/Wizard/SDK
E:/Wizard/SDK/subfolder_01
E:/Wizard/SDK/subfolder_02
E:/Wizard/SDK/subfolder_03
etc.

(Visual Studio is only targeting the first entry).

Second:
When i was installing the wizard the following error occurred:
The COM-Classfactory for the following component with CLSID (see attachment) could not be called due to following error: 80040154 class not registered.
Exception from HRESULT:0x80040154 REGDB_E_CLASSNOTREG.

errorvsix.png (9.24 KiB) Viewed 36243 times

Regards,
quickshat

[Fleuve]

Hi,

i've tried to use the 1.28b version of the wizard but: Visual Studio does not let me include things from SDKs folder.
I have already checked project import settings and the paths are all included by default.
Also these paths are correctly included and i am able to open them with my explorer.

But if i hover on a

Code: Select all

#include <sdk_relevant_header.h>

, Visual Code only tells me that it was unable to find .h file in the first path of the settings include-path list.

Give me, sometime to create a proper examples and test if that fail the test or not.

[cheblin]

Hi ALL

You can force plugin project start recognize included files if after install plugin in the folder
C:\Users\USER_NAME\AppData\Local\Microsoft\VisualStudio\

find all files with name
ESP8266.vcxproj
and edit it
replace

Code: Select all

<Import Project="$(MSBuildToolsPath)\Microsoft.Common.Targets" />
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.DesignTime.targets" />

with

Code: Select all

<Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" />
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />

and recreate your projects
==============================================
You can eliminate manual adding includes if add what you need in advance

in MSBuildTemplate folder of the plugin installation directory in file XtensaGcc.props add
after string

Code: Select all

$(VisualStudioXtensa)ESPressif\$(SelectRelease)\$(SelectVersion)\include;

this

Code: Select all

$(VisualStudioXtensa)ESPressif\$(SelectRelease)\$(SelectVersion)\driver_lib\include;

add more if you want

For author: Dear AUTHOR, please continue your nice project!
Find me at https://github.com/cheblin if you need any my help

With Best regards, Cheers!

[Musher40]

Hello

Thanks for your work.

I have installed ESP8266 Wizard 1.2.9.with visual studio community 2017.

All are good with c language but i have a problem with C++:

when i compiled: C++ compiler not installed on this system.

Is it in your package or configuration problem ?

I am Non-OS and SDK 2.0.0
xtensa-lx106-elf-gcc.exe (GCC) 4.8.2
xtensa-lx106-elf-c++.exe (GCC) 4.8.1 ??

Thanks