Page 2 of 2

Re: UART dark after flashing

Posted: Thu Apr 20, 2017 8:38 am
by Wilberforce
I have a similar issue after flashing where I can't connect with the Espruino IDE after a flash and

Code: Select all

--after hard_reset
The delay - close - delay update does not work.

in the Espruino ide I get:

Code: Select all

Connected
>
Disconnected
and in the console:

Code: Select all

>>> Sent
ERROR: RECEIVE ERROR: {"connectionId":1,"error":"overrun"}
Disconnect callback...
WARNING: [notify_warn] Disconnected
>>> Disconnected
However, If I flash instead of:
esptool.py --chip esp32 --port COM3 --baud 921600 --before esp32r0 --after hard_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0x10000 ../../espruino_esp32.bin

but with soft_reset:
esptool.py --chip esp32 --port COM3 --baud 921600 --before esp32r0 --after soft_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0x10000 ../../espruino_esp32.bin

I get a warning:

Code: Select all

Hash of data verified.

Leaving...
Soft resetting...

A fatal error occurred: Soft resetting is currently only supported on ESP8266
But I can then go into the Web ide directly.

As this stage I'm not confirmed if it is booting into the new firmware or the old.

Re: UART dark after flashing

Posted: Thu Apr 20, 2017 8:45 am
by BuddyCasino
Hmm, inserting the pauses totally fixed it for me.
There is probably a hardware bug in all SiLabs devices manufactured before 1639:
Silicon Labs is also pleased to announce the following Errata update:
The CP2102N A01 errata includes the following errata for A01 revision. These issues will be solved in
A01 devices with a date code of 1639 or later.
1. Systems using CP2102N may see devices fail to respond until a power-on reset. If a device fails
to respond properly, remove and replace power until the device properly responds. Devices with a
date code of 1639 or later will not have this issue.
(see http://community.silabs.com/t5/Interfac ... 6137#M3980)

Re: UART dark after flashing

Posted: Tue May 16, 2017 9:15 pm
by BuddyCasino
Theres a new driver available: http://community.silabs.com/t5/Interfac ... alse#M4104
Fixed it for me.