ESP8266 Community Forum

Would be cool to see some documentation from anyone on how to modify and rebuild basic.

Anyone care to do some documentation on this I would like to possibly make some changes that would suit me but may not be good for the rest of the club.

To build you need to download the git repository. Copy all the libraries in to your local libraries folder. Install the arduino environment package for arduino indicated in the read me file for the branch you are working on. Once this is all done all you have to do is compile and hook your esp up to the computer via a usb to serial.

Nothing to fancy. Just like any other arduino sketch.

Initiating mmiscool decryption key........
Decryption Failed!

Lets say for instance I want to tinker with the latest version and see what I can come up with.

So I would download https://github.com/esp8266/Basic.git
This is the code that I will modify to fit my needs.

Copy all libraries into local libraries folder??? I assume that you assume I have messed around with the arduino sketches before basic not true in this case but will note I did purchase an uno some time back and never got around to using it at the time the wireless shields seemed a bit beyond my budget so I opted for a raspberry pi instead and the arduino sat shelved never messed with it then I came across this esp8266 module and the klunky LUA programming for it. Then came Basic which further eliminated a lot of the things I did not like about LUA. So this is where I set and my story short and sweet.

So in saying this I think you mean that I will need to download this https://www.arduino.cc/en/Main/Software and place my libraries into this folder ?

Then I would download 2.3.0 stable as stated on basics github
http://esp8266.github.io/Arduino/versions/2.3.0/

Then I would hook up usb to serial or in my case seeing as I have a nodemcu I just plug the USB in correct?

Mods I would like to make are interface based at first anyways:
I would really like to see the wifi information not password protected as a separate entity from the rest of the interface which would be locked down with a password.

This way if I helped a friend automate their house and they upgraded wireless routers for instance I could have them visit the wifi configuration and change only the needed info but yet it would protect the edited code from being modified or edited by mistake or on purpose so it saves me the trip from having to go pay them a visit and listen to them tell me that the boogeyman did it or it wasn't me etc...

And finally I just like having options I doubt I will be a guru overnight learning curve applies here for me but maybe with time I can figure some things out and do something useful and useable that I can share but I warn you don't expect too much prodigious information or builds from me as I am not as well versed as cicciocb, yourself or rotohammer and it really isn't my intention to make builds for public consumption unless they are useful in some way beyond what you already present obviously this idea is only really useful to me as I have suggested it many builds back but its just an example.

Either way the point of this post was to enable others to look into this as well. Some folks have lots of time and a good head on their shoulders maybe they also could contribute something to you never know.

Hello!

Forlotto, were you successful in putting together a working development station for modifying and building Basic?

I am not a guru either, but have programmed for many years and would love to be able to see if I can work on this project.

If you have successfully put a development environment together with your nodemcu please let us all know what you have found out and how you did it!

Thanks Very Much!!!