-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
esp12s firmware upgrade #6
Comments
You are trying to flash the C17GH3? I'm not sure if there is an easy way to do it. You could try to increase the baud rate for flashing and perhaps that would succeed. I wasn't able to flash so I cut the RX/TX traces on the PCB. After flashing, I scrapped the mask above the traces near the cut and applied a solder bridge across the cut. Here are my notes: Reading flash: Writing: After that you should be able to flash from platformio: platformio run --target upload --upload-port 192.x.x.x (thermostat ip address) |
Hell
pointed the chip manually, we get the same fun:
add stub - we get
Was your version without these problems? PS commands erase_flash & region also unsupported :( |
Did you cut the traces on your PCB? |
I am in no way an expert on this, coding is not one of my virtues! I have 5 Floureon C17.GH3 thermostats in my house controlling the floor heating. A sixt is available for an upstairs extension. I have not modified them yet, but want to. Meanwhile I successfully converted all kind of "tuya compatible" devices using the tuya-convert from Tasmota. Did you try that route? Tuya-convert captures and reroutes the device to a temporary wifi and does not let it connect to the Tuya cloud. Could it be that is your problem? |
Great point. Tuya-Convert is probably the first thing to try. I didn't know about it when I was flashing my device. If you can get it to work, please keep notes and send them to me so I can add them to the documentation. |
I'll try to Tuya-Convert my spare thermostat in the next few day and keep you abreast on this channel. |
yes, rx and tx lines cutted |
Are you using the latest version of esptool from github? |
yes 3.0 dev |
It looks like secure download is a feature of ESP32-S2 (see here) so perhaps there is a bug with 3.0.dev that you are trying. Try using the latest released versoin which is 2.8. |
Hell. Not esptool ... USB-TTL fried to hell CH340 TTL poured out without problems with cut rxtx. It would be nice to describe these points in the instructions. The question is, can the firmware display the temperatures of both sensors? PS Thank you so much for the cutting tip. I already wanted to dry the ESP with a hairdryer! |
Great news! I'm glad you were able to get it flashed. The firmware will send changes for both internal and external temperature over mqtt and also display them on a very rudimentary webpage. I only have the internal sensor enabled so I haven't really tested this. |
hello :) can you share the firmware you uploaded to esp? |
Dear comrades, help with the equipment is required.
The wires were soldered to the board to the rx-tx connectors
ground is also connected to USB-TTL
power is used externally, and soldered to the legs of the ESP.
GPIO hooked to 0
When turned on, the microcontroller does not enter the firmware mode.
One gets the feeling that the internal communication is decoupled on the same rx-tx ports to which it is connected.
I ask for help with the firmware.
I did not check the option with full soldering of the ESP module with a hairdryer, and I would not like it, because there is a great chance of damage to the display.
Board version c17_6.0
Which raises questions:
I connect to port monitoring, on speed 9600
and I get a strange answer: Some of the data is readable, some are not. there is a feeling that the port is transmitting data to a neighboring microcircuit.
screenshot
https://dl.dropboxusercontent.com/s/hxyf1ud335lyxin/javaw_2020-09-03_01-24-34.png
Thanks for reply
The text was updated successfully, but these errors were encountered: