Discuss here different C compiler set ups, and compiling executables for the ESP8266

User avatar
By pcsrule
#2216 I seem to be having a similar problem. No matter which flash tool I use I can't seem to get anything other than a single .bin file like the 0.9.2.2 AT image to successfully boot. All self compiled images and even images from other people with multiple files just will not boot. I'm beginning to think these two .bin files aren't to be written to 0x00000 and 0x40000 after all. I'll pick apart one of the stock .bin files in a hex editor and see if I find anything interesting.

Edit: I tried a hex editor and it seems 0x00000 and 0x40000 are reasonable. After much frustration I tried the esptool.py script to flash the chip and it works! I must have missed something the last time through with this programming tool.
User avatar
By MrLight
#2552 Hi all,
I'm trying to complie the IoT Example out of the 0.9.2 SDK and always when I'm calling make i get this Error:
Code: Select allmake: Nothing to be done for `FORCE'.


BUT it has worked a few days before.... Today I'm not able to get it working. I although have reinstalled the VM but without any luck..
Can anyone give me a hint?
Thanks a lot!

PROBLEM SOLVED: To use the given Makefile from the IoT Example it is not possible, to compile out of the example subfolder. So just copy the IoT Folder in the sdk root...
User avatar
By Busti
#2573 Hello,
I can't seem to get the VM to boot correctly. It always gives me a "Kernel Panic - Not Syncing - Attempt to kill Init" Error followed by a couple error log lines.
I followed the readme but I set a different share folder and deleted the D:// one since I don't have a D:// drive.
User avatar
By Busti
#2742
Busti wrote:Hello,
I can't seem to get the VM to boot correctly. It always gives me a "Kernel Panic - Not Syncing - Attempt to kill Init" Error followed by a couple error log lines.
I followed the readme but I set a different share folder and deleted the D:// one since I don't have a D:// drive.


I already solved it...
It was a VirtualBox problem.