I’m getting further – I’ve scoured the web and no-one as yet has made significant improvements to the ESP8266 code or if they have, they’ve hidden it – but at least now I can compile the code. For Windows users out there who are about to pull out their last hairs, I hope this is helpful.
I tried the compile-in-windows versions and got no-where – either the MAKE file was wrong or SOMETHING – SO I went back to the LINUX version much as I HATE Linux and command lines.
So in my previous blog it tells you how to get Virtualbox running (trivial – it just works) – and how to then add the relevant image…
This video https://www.youtube.com/watch?v=Cga2XTifqQ8 is very helpful and in particular OSCAR has been MORE than helpful – but I could not get that to work as such – Oscar helped me.
So I didn’t quite do it the same way as his video – I grabbed the two files, put them in a directory call ESP on my desktop (after unzipping them.
That’s it – the VirtualBox, the image file as per previous blog or indeed Oscar’s video – this lot and NOTHING ELSE – well apart form Windows (I’m using Windows 8 made to look like Windows 7 but that’s it – oh and I use Notepad++ to edit files.
First attempts at doing anything with this failed miserably – either I didn’t have permissions of the directory could not be found… so we went through various iterations and eventually came up with this – and this is repeatable on my system (the laptop shut down so I had to start from scratch.
So open linux – with the ESP folder on the desktop – SHARED – go into the settings for the image – and share that ESP directory – if it has another shared directory scrap that.
sudomount -t vboxsf esp /mnt/Share
You’ll get asked for the password it is espressif.
All of that should work. us ls and you should see the two directories…I KNOW – what’s wrong with DIR…
cp -R at_v0.19_on_SDKv0.9.2/* esp_iot_sdk_v0.9.2/app
These two commands above merely make a copy of the AT demo directory (into the SDK directory under a subdir called APP. You could do that in Windows really – the second command merely moves you to the app directory.
Now you are cookling…
Those two commands will compile and prepare the files and generate some BIN files… here in my case (I’m Peter)
I have NO idea why the BIN files don’t end up in the same directory as the app itself but never mind… the point of this is to get you to the point where you can successfully generate bin files. And at that point on my PC indeed the files ARE generated.
The bit I have not done yet is blow the chip – but there are plenty of Windows Tools to do that including ESP FLASH DOWNLOAD TOOL which is a windows EXE with a load of support files and has a nice pretty interface to allow you to send multiple BIN files to multiple locations. Here’s where they go.
And that is as far as I’ve gotten – at the weekend hopefully these will blow into my ESP-01 board, the baud rate will revert back to 9600 and I can then use the AT+CWMODE=115200 to shift it back to 115,00 baud (it stays that way once programmed). That should hopefully take me to the same point as everyone else – at which point I can start looking at the BUSY S problem unless someone else has beaten me to it by then – oh and to change that awful NO IS FUN into “ERROR” – also there’s a READY which needs to be turned into an OK – THEN we might start doing something useful with this little board.
If any of the above was clear as mud, let me know. Better still if you’re way ahead of me and have this working all in Windows – please do a video ensuring you make NO assumptions – and we can all benefit from that.
Oh, one last thing, the compile process outputs a LOT OF STUFF which might get boring if you’re testing changes… I’ve no idea if you miss anything important by this but you can get rid off much of the output as follows..
type “make > /dev/null” and “./gen_misc.sh > /dev/null”