Dead ESP

User avatar
rudi
Posts: 197
Joined: Fri Oct 24, 2014 7:55 pm

Re: Dead ESP

Postby rudi » Sat Jul 30, 2016 1:28 am

scargill wrote:
..a couple of people wrote into me to say they had killed their boards....
.. I tried the same on 3 new boards of my own - and killed all three...


R.I.P.

:D

do not play with protected area on flash - this is no bug - this is a future -
for more detail, ask your WINBOND dealer.

FYI: if you have the wrong sequence, you kill ( protect ) the flash.
if killed ( protected ) then you can not ( writeable & saved ) flash on this area.

if firmware use protection user key and they crash with RBOOT configs,
then rboot can not boot on the sequence; and if you have the wrong sequence
you can flash new - but your firmware was not written totally - cause -
you have protected area - that can not overriden. ( user key, config key, orig firmware )

please, read data sheets
for I2C Theme: -> I2C
for extended future function -> winbond

then this would help you to understand how you must going on in the future

also, use the search function on the forum,
i have wrote moretimes about protection and firmware protection.
there are possibles ways.

-> protection area on flash
-> protection area on µSDHC ( SDIO ) ..

.. if you boot from µSDHC or load Firmware from µSDHC with combined RBOOT.
you can use a catalog of firmware, that RBOOT can boot/load by reference from µSDHC.
..

regards..

-------------------------------------
love it, change it or leave it.
-------------------------------------
問候飛出去的朋友遍全球魯迪

SpenZerX
Posts: 41
Joined: Thu Apr 16, 2015 9:30 pm
Location: Germany
Contact:

Re: Dead ESP

Postby SpenZerX » Wed Aug 03, 2016 5:49 pm

scargill wrote:It LOOKs like it was not RBOOT after all..

2. After my initialisation of ports - and other stuff - I finally called a routine to do with WIFI....

wifi_set_opmode(0);

and that was fine until SDK 1.54 - after that - I'm getting no serial output (other than the 78k startup stuff) UNTIL that function is called.


May be you should not use wifi_set_opmode(0); in start up code, because it will do a flash write of settings.

luis_filipe
Posts: 2
Joined: Thu Aug 04, 2016 10:22 am

Re: Dead ESP

Postby luis_filipe » Thu Aug 04, 2016 10:28 am

Hello guys,

sorry for not open a new topic, but I cannot.

Anyway, i would like to ask who can I fix this error:

Code: Select all

Sketch uses 221,995 bytes (51%) of program storage space. Maximum is 434,160 bytes.
Global variables use 31,568 bytes (38%) of dynamic memory, leaving 50,352 bytes for local variables. Maximum is 81,920 bytes.
C:\Users\root\AppData\Local\Arduino15\packages\esp8266\tools\esptool\0.4.9/esptool.exe -vv -cd ck -cb 115200 -cp COM6 -ca 0x00000 -cf C:\Users\root\AppData\Local\Temp\buildde9605d9d67ae2595f4f5b9646f4a46e.tmp/firstConnection2.ino.bin
esptool v0.4.9 - (c) 2014 Ch. Klippel <ck@atelier-klippel.de>
   setting board to ck
   setting baudrate from 115200 to 115200
   setting port from COM1 to COM6
   setting address from 0x00000000 to 0x00000000
   espcomm_upload_file
   espcomm_upload_mem
   setting serial port timeouts to 1000 ms
opening bootloader
resetting board
trying to connect
   flush start
   setting serial port timeouts to 1 ms
   setting serial port timeouts to 1000 ms
   flush complete
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
   serialport_receive_C0: BB instead of C0
trying to connect
   flush start
   setting serial port timeouts to 1 ms
   setting serial port timeouts to 1000 ms
   flush complete
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
   serialport_receive_C0: 36 instead of C0
trying to connect
   flush start
   setting serial port timeouts to 1 ms
   setting serial port timeouts to 1000 ms
   flush complete
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
   serialport_receive_C0: 36 instead of C0
resetting board
trying to connect
   flush start
   setting serial port timeouts to 1 ms
   setting serial port timeouts to 1000 ms
   flush complete
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
   serialport_receive_C0: BB instead of C0
trying to connect
   flush start
   setting serial port timeouts to 1 ms
   setting serial port timeouts to 1000 ms
   flush complete
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
   serialport_receive_C0: 36 instead of C0
trying to connect
   flush start
   setting serial port timeouts to 1 ms
   setting serial port timeouts to 1000 ms
   flush complete
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
   serialport_receive_C0: 32 instead of C0
resetting board
trying to connect
   flush start
   setting serial port timeouts to 1 ms
   setting serial port timeouts to 1000 ms
   flush complete
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
   serialport_receive_C0: B3 instead of C0
trying to connect
   flush start
   setting serial port timeouts to 1 ms
   setting serial port timeouts to 1000 ms
   flush complete
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
   serialport_receive_C0: 32 instead of C0
trying to connect
   flush start
   setting serial port timeouts to 1 ms
   setting serial port timeouts to 1000 ms
   flush complete
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
   serialport_receive_C0: B7 instead of C0
warning: espcomm_sync failed
error: espcomm_open failed
error: espcomm_upload_mem failed
error: espcomm_upload_mem failed


I cannot upload any sketch from arduino IDE and when I open the serial monitor I only see garbage.

Who can I do to fix this problem?

Thanks in advance

Who is online

Users browsing this forum: No registered users and 5 guests