Build against SDK 1.0.1b2 is broken

[nekromant]

Looks like we have a problem with 1.0.1b2 SDK, something's changed and it can't ever connect to a network. Now trying to figure out where the insect came from.

[d-a-v]

I did not try, but I came into this: espressif/esptool#33
Could it be related ?

[nekromant]

Unlikely. My guess is that something's changed in headers yet again, but I may be wrong.
The firmware is working, I can access commandline and even scan for networks, but whenever I try to connect the console becomes laggy and occasionally ends up in an exception and a reboot. I could never connect to a network on 1.0.1b2, while 1.0.1b1 worked awesomely.

[susisstrolch]

On 04/30/2015 12:43 PM, Andrew wrote:

Unlikely. My guess is that something's changed in headers yet again,
but I may be wrong.
The firmware is working, I can access commandline and even scan for
networks, but whenever I try to connect the console becomes laggy and
occasionally ends up in an exception and a reboot. I could never
connect to a network on 1.0.1b2, while 1.0.1b1 worked awesomely.

—
Reply to this email directly or view it on GitHub
#82 (comment).

Another flaw - not really the reason for that problem - is the default
base address for environment.
According to SDK doc, the last 16k are used by the system.
So, the default should be set to 0x7B000 instead 0x7C000.

[nekromant]

Now fixed, and builds against 2.0