- Tue Jul 21, 2015 2:36 pm
#23858
Good day everyone,
I currently have a ESP-07 module, 16 pin variant, red power led and blue activity led, lying here.
I have already configured and tested it using AT firmware (connecting to my own AP) and it's also connecting after restart without fail, so the module is definitely working, as is the connection via my FTDI USB-to-Serial adapter (3.3v of course).
The ESP is mounted on perfboard using a custom 2.54mm to 2mm spacing adapter (and yes, it's looking just as atrocious as you'd think it does!)
Now I wanted to flash NodeMCU on that little thingy for which I made the following connections:
First, I established a ground rail (a 2.54mm jumper with 4 pins) to which I connected GPIO0, GPIO15, GND pins from ESP and GND pin from the FTDI.
I then went on to doing the same for VCC. Currently, CH_PD (labelled "EN" on my silkscreen, so I did it according to the available pinout online) and VCC of the ESP are connected to the VCC line of the FTDI using another jumper bridge.
Furthermore the serial connection is connected correctly (TX/RX switched on each end).
When I start the module like this I can connect to serial just as ever and I get the bootloader crap but fine transmission otherwise. Module upstart looks like:
Mind that this is in what's supposed to be flash mode!
Furthermore take note that not even the normal "AT" command is working. Every command I issue returns error.
For connection to the module via serial I use:
For flashing I tried:
and
(yes, I did replace the path)
Hope someone here can shed some light..
- rjhllr
I currently have a ESP-07 module, 16 pin variant, red power led and blue activity led, lying here.
I have already configured and tested it using AT firmware (connecting to my own AP) and it's also connecting after restart without fail, so the module is definitely working, as is the connection via my FTDI USB-to-Serial adapter (3.3v of course).
The ESP is mounted on perfboard using a custom 2.54mm to 2mm spacing adapter (and yes, it's looking just as atrocious as you'd think it does!)
Now I wanted to flash NodeMCU on that little thingy for which I made the following connections:
First, I established a ground rail (a 2.54mm jumper with 4 pins) to which I connected GPIO0, GPIO15, GND pins from ESP and GND pin from the FTDI.
I then went on to doing the same for VCC. Currently, CH_PD (labelled "EN" on my silkscreen, so I did it according to the available pinout online) and VCC of the ESP are connected to the VCC line of the FTDI using another jumper bridge.
Furthermore the serial connection is connected correctly (TX/RX switched on each end).
When I start the module like this I can connect to serial just as ever and I get the bootloader crap but fine transmission otherwise. Module upstart looks like:
Code: Select all
Terminal ready
rl��r��c�n��
�
��p�|����x��ǒ��lp
�nn��;�nĒ��
b�$rrp�n��
��l�
�
�
b�n��n�$���
b��>~�n����l`��#�n�rnr���;��
l`nn��
�r��
�
p
p��<��쎜
b��>~�n���
r��#�n�rnr���;��
l`nn��
�r����
p
p��<��l�
b��>~�n���
r��#�n�$�l`8`rn|��n��b��l`8���;��
l``|���x~�n��ܒ��r�#�n���
��b`�x�l
�l��$����
�
�
r!��d���F��nĒ�
�ldb�lc`��l�Đx��n��$bb���
rb��;l��;�
��Ē�<��r���l``r�]�
Ai-Thinker Technology Co. Ltd.
ready
WIFI CONNECTED
WIFI GOT IP
AT
ERROR
Mind that this is in what's supposed to be flash mode!
Furthermore take note that not even the normal "AT" command is working. Every command I issue returns error.
For connection to the module via serial I use:
Code: Select all
sudo picocom -b 115200 --omap crlf /dev/cu.usbserial-*For flashing I tried:
Code: Select all
sudo python esptool.py --baud 115200 --port /dev/cu.usbserial-* write_flash 0x00000 /path/to/nodemcu_latest.binand
Code: Select all
sudo python esptool.py --port /dev/cu.usbserial-* write_flash 0x00000 /path/to/nodemcu_latest.bin(yes, I did replace the path)
Hope someone here can shed some light..
- rjhllr
