ESP8266 Community Forum

- Fri Oct 21, 2016 3:53 pm #56924

I'm game: where is the 'dev' branch?

We mean the NodeMCU dev branch.

LOL: there is 100 Github (now that it works) repositories, the NodeMCU that I used to download the flash tool has one branch, nothing listed as changed in over a year.

- Fri Oct 21, 2016 7:11 pm #56931 finally got esptool.py working:
C:\ESP\esptool-master>esptool.py --port COM5 erase_flash
esptool.py v1.2-dev
Connecting...
Running Cesanta flasher stub...
Erasing flash (this may take a while)...
Erase took 0.0 seconds

It didn't take long because it can't tell how much memory is on the device and without knowing how much memory it must have aborted. Someone mentioned that esptool could calculate the size of memory, wrong.

- Sat Oct 22, 2016 2:48 pm #56962 read the doc.
know what you are doing. why you are doing.
then you can solve problems.

frustrated of solving problem?? stop living

- Sun Oct 23, 2016 11:00 am #56985

read the doc.
know what you are doing. why you are doing.
then you can solve problems.

frustrated of solving problem?? stop living

"Read the Doc" without a reference is as useless as the rest of our comment.

1. Espressif documents programmable pull up/down GPIO pins but then never states what state at boot all pins are, that I can find.
2. Espressif never documents the values used in pull up/down that I can find
3. The reference to work done on NodeMCU Flash tool would indicate the Github site would reflect this, the last update to https://github.com/nodemcu/nodemcu-flasher was Sept. 30 2015.
4. The readthedocs.io (https://nodemcu.readthedocs.io/en/master/en/flash/) is dated and the links are broken.

So "addicted", please point out something that I can read that is relevant otherwise keep your snide, demeaning comments to yourself.