ESP8266 Parasite

Well, I seem to be having an issue at the moment, now that the control software is close to completion I can actually send data to the ESP at a higher data rate (about 90KB/s) and there seems to be an issue, this will run fine for a variable length of time and at that point, the ESP seems to experience a partial crash. The socket is left open on the ESP side, and the control program then sees communication timeouts. No further interaction can be seen from that port on the ESP. The strange bit happens after, the timer I have running to kick out broadcast packets the controller listens for still work. Even though the socket for main transfer is dead and appears to have had an exception, the rest of the program carries on

Spent today updating the build scripts and setting up a new IDE project. With Visual Studio setup, including the SDK headers and binding the build/clean/rebuild scripts means I get an IDE I am far more comfortable with, with the added bonus of Intellisense , this is one feature you very quickly miss when you don't have it.

Actually got the 201 to flash, its certainly worth remembering that on these larger boards, GPIO15 needs to be pulled to ground in order to flash, as well as GPIO0, will need a quick tweak of the design to compensate for that

Currently the 201 is leeching off a project using the ESP-01 for power so I dont have to send off for the boards until I'm sure there isnt going to be another subtle difference like there was with flashing.

Just finished up the first actual layout for the new board, a bit annoying to route around the FTDI chip, but everything connected up, allowing both the on board adapter, or an external serial controller to communicate with the device for programming.

Learning from previous mistakes, every pin is labelled on the silkscreen so once it comes back from manufacture, its alot easier to deal with

Well, finally got the schematic to where I am happy, and the PCB just had its first layout