I've upgraded my project from 2.0.17 to 3.0.4, now everting seems stuck, no more answer from serial port so no more able do upgrade/downgrade. The usb driver not detect the board (ESP32 DEVKIT V1) anymore. There is a way to roll back to previous version ?
thanks
Simple to roll back, just nopen the board tab and click the combo box that is now showing 3.0.4. Click on 2.0.17 and done.
well, I've taken in consideration that option, but unfortunately doesn't appear so simple (to me) since when I connect the board via usb no serial port appear so I don't know how to downgrade it.
All that is happening under the covers is that the library code that is board specific is either upgraded or downgraded. I don't have anything attached to my laptop when I do this.
That means something else is (also) wrong. Regardless of the core you used when uploading, the Serial / com port should show up within the IDE, this has nothing to do with whatever core you used.
Close The IDE, grab a fresh USB cable, reboot and try again.
Well, already tried to use different cables and and PC.
At first impression seems an hw issues, but nothing is changed. I mean that the board work fine before to update it to a fw compiled vs. 3.0.4 .
Exactly how did you do this upgrade?
My application is a wheather station, I usually upgrade it via OTA (internet).
In this case Arduino IDE ask me to make an library/board upgrade. After that some small modification was needed (about watch dog ewt management) in order to compile. After that I made the update as usual and the board no answer anymore. Finally to check what happen I'v tried to connect it by usb/serial to better debug the issue but starting from that point I was no more able to comunicate to the board.
Sorry, I have no experience with the OTA upgrade process and what can go wrong.
Hopefully another forum member can help.
Ok, thanks anyway. The OTA update could fail, of course, but what is strange is the fact that the board is no more detected from windows usb driver. I've tried to update the windows driver too:CP210x USB to UART Bridge VCP Drivers - Silicon Labs
I don't know how the serial boot loader is managed from ESP32, could be that the 3.0.4 upgrade change the serial bootloader too so this fire up my issue ... it just my hypothesis , I don't know what else think.
I've rolled back , thanks.
But anyway the windows serial driver is not able to detect the board .
I am not sure what you mean, do you mean there is no port? That is usually a windows device manager issue. Make sure you shutdown ALL IDE windows including serial monitors. If that does not help, a reboot may be needed.
No answer meaning your board is no longer connected to the network or the port does no longer show up, even though the board is connected to WiFi ?
Anyway, yes this can happen with OTA. If you upload with the wrong type of board, or the wrong partition scheme, OTA upload may longer be available to you. Also if you upload a sketch which does not support OTA but it does not make sense if that is what you did.
Regardless, updating the core can break all sorts of code, though generally at compile time, not at run-time. For running projects i avoid upgrading the core, also because many times the backwards compatibility is not that good for ESP boards. Some libraries will need to be updated or won't work anymore etc. I have different core versions in my sketchbook for the ESP8266, because some of the newer core have features that i do want to use etc.
That means there is a hardware issue.
No that is not possible, or at least not as far as i know. Is there anything else you have (had) connected to the Serial pins on your board ? Just to clarify, what is the exact board you are using ?
yes but without the port available that doesn't help i guess. My best advice is to also roll back to the previous version of the code and get a fresh ESP32 although they may take some time to arrive. The USB to TTL converter may have broken somehow, you could consider trying to upload to the esp using an external one.
For rolling back core versions, i do recommend first to full un-install the latest version before installing the older one, and one of the reasons for not using IDE 2.x.x is that it keeps bugging you about newer version you could install, which in this case may be part of the cause.
Also you should roll back to previous library versions, just in case.
Still i don't see how a software update can cause a full hardware malfunction. I have not experienced that ever.
Just some information after some deepr investigation:
- the usb-ttl converter is on board I connect the DOT DevKit directly to PC usb port (no external one)
- apparently the ESP32 run for a while, since I see some blink the user led (My application do it while waiting to get wifi connected)
- I've checked with an oscilloscope the 3.3V and it has a periodic (one or 2 sec) power hole and this could explain lot of things.
But what is so strange to me is this happen after a sw update , so difficult to imagine that I've broken the onboard usb/ttl converter in that way.
My only hypothesis is that the 3.0.x version had managed in a different way the wifi part so that that it increase power consumption during the connection and this lead to my power hole.
The issue is how (if possible) I can get by board to life , I mean there are a way e.g. to make a flash erase before the application start, so I get rid of my flashed 3.0.x app?
(well in the meantime I've ordered some other boards but this is a debacle from my point of view
)
No idea how that could happen, but you could try to supply the 3.3v from an external source without the USB connected and see if the esp at least start working through the sketch normally. You could even try with the USB, but there is a risk involved so i do not recommend it.
Not very likely, even if there is a bigger power demand, the 3.3v regulator should be able to provide what can be required. If the current draw is that big, then i would say the esp is anyway broken. Does it also get hot near the regulator or near the esp chip ?
There is a good chance that the 2 things are actually not related but somehow just happened at the same time.
I mean the software update and the malfunction.
If you have another working USB to TTL converter you can try to connect it to the TX & RX pins and use external power to 3.3v. It is worth a try.
just as an update:
as you suggested I've tried to connect an external usb/ttl conv to the TX0/Rx0 pin directly, and everting seems correct in this way. So I've uploaded an empty sketch (just in the case mine was bad) in order to have a clean situation.
The result is that the ESP32 and the Wifi it's working (although the WROOM -32 seems quite hot) but the onboard usb/ttl still doesn't work since it's not detected by the PC.
So my conclusion is that the onboard CP210x usb/ttl conv is damaged, and as you said, seem very strange that a sw update could lead to this, I must conclude that it was damaged for some other reason (take in consideration that the weather station was running for weeks before the insane ver update).
Well great that's been resolved. Rather strange that also OTA updates had stopped working though.
They anyway tend to get fairly warm, even more so if running at 240MHz. If it is more near the regulator, it might be worth checking how much current is actually being drawn. The CP210x may be damaged in such a way that it is shorting out a bit, in that case, maybe it is better to remove it. Still it might be a different part that is connected to it, like the auto reset system. It is all a bit strange.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.