[SOLVED] Flashing Sketch on ESP8266-01

Other Hardware 3rd Party Boards
1

Actually when I flash the module it does compile and wrote on it, until the compiler has to soft-reset it.
As the screenshot attached:

ESP01_Saved_Data (1)
ESP01_Saved_Data (1)1333×601 17.3 KB

My main concern was about its Flash memory, no problem at all on this.
The module is connect to Arduino UNO Rev3 in this way:

  • RX > RX
  • TX > TX
  • 3v3 > 3.3V
  • EN > 3.3V
  • IO0 > GND
  • GND > GND

Arduino is bridged by connecting its RST > GND.
I'm trying to upload on it this sketch: Firebase-ESP8266/TestMode.ino at master · mobizt/Firebase-ESP8266 · GitHub

Using another library without the requirement of soft reset after the upload does actually worked quite well, but using the old one I cannot authenticate into the db before pushing data, and it is a main security concern that I don't want.

Any ideas on how to solve the problem?

2

This looks wrong

An Rx pin usually goes to a Tx pin and vice versa but I know nothing of your setup so you need to check it

3

the pin labeled RX on Uno is the TX of the USB chip

1 Like
4

Sure, I know. I mainly followed this guide, that use a different library and a different baud rate to communicate to ESP01:
https://create.arduino.cc/projecthub/pulasthi-Narada/send-multiple-sensors-data-to-firebase-using-esp8266-f2f38b

As you can see to upload the code to ESP01 he uses the RX to RX and TX to TX connection.

Maybe this library has been created to work with a baud rate different to the one i flashed on my module.
That's what I'm looking for. For the library that I want to use now I tried searching in all the resources into the repository, some requirements to flash the code onto the module, how it is cabled, something like this... Nothing found.

5

There are three ways to solve this problem, when it doesn't upload the code:

  1. Check the pins
  2. Unplug Arduino, change the board to another one (either from ESP) and then again on the one we want to use, plug Arduino and upload.
  3. If none of the above worked: restart your PC, and redo again point 1 and 2.
6

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.