Skip to content
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

Sonoff Touch doesn't react after flashing #167

Closed
xoseperez opened this issue Jul 18, 2017 · 11 comments
Closed

Sonoff Touch doesn't react after flashing #167

xoseperez opened this issue Jul 18, 2017 · 11 comments

Comments

@xoseperez
Copy link
Owner

Originally reported by: Florian P. (Bitbucket: icnw, GitHub: icnw)


I used the latest bin-file from the Downloads and wrote it to the Sonoff Touch. It worked like a charm. Unfortunatly, the device is not reacting afterwards: No LED, NO AP, nothing. I repeated the flashing a couple of times without any effects.
With the "simple" Sonoff, I never ran into trouble with that approach. Could it be that the bin-file is defect?

This is the log of my flashing:

#!bash
esptool.py v2.0.1
Connecting....
Detecting chip type... ESP8266
Chip is ESP8266
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 1MB
Compressed 422912 bytes to 312588...
Wrote 422912 bytes (312588 compressed) at 0x00000000 in 27.8 seconds (effective 121.7 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting...

@xoseperez
Copy link
Owner Author

It could be... I have not test it myself since I don't own a Touch.
Have you tried building the project for the Touch yourself?

@xoseperez
Copy link
Owner Author

Original comment by Florian P. (Bitbucket: icnw, GitHub: icnw):


Actually no. I tried once but it failed due to my inability and a documentation that was not detailed enough for my skills.
It can be as well that my touch is broken as it missed to test it with the factory image. I was hoping for somebody to confirm or to deny that the image is broken.

@xoseperez
Copy link
Owner Author

xoseperez commented Aug 6, 2017

Original comment by Andreas L. (Bitbucket: andreaslink, GitHub: andreaslink-de):


I found this topic too late, but I can confirm this "somehow", I have a more detailed description in #181 (https://bitbucket.org/xoseperez/espurna/issues/181/sonoff-basic-does-not-boot) for a basic sonoff. Probably this has somehow the same root as it might be hardware related?

@xoseperez
Copy link
Owner Author

xoseperez commented Aug 6, 2017

Original comment by Andreas L. (Bitbucket: andreaslink, GitHub: andreaslink-de):


I solved my issue and I guess, this might probably also fix your issue.

When flashing please change flash mode to DOUT when using it with esptool.py use --flash_mode dout as an additional param:

esptool.py --port /dev/ttyUSB0 --baud 115200 --flash_mode dout write_flash 0x00000 espurna-1.8.3-sonoff-debug.bin

(This should work, as I flashed from Arduino IDE, I did not test it.) See more in detail in #181.

@xoseperez
Copy link
Owner Author

Original comment by Florian P. (Bitbucket: icnw, GitHub: icnw):


Thanks for the hint but at least for me that didn't do the trick.

By the way, it must be

esptool.py --port /dev/ttyUSB0 --baud 115200 write_flash --flash_mode dout 0x00000 espurna-1.8.3-sonoff-debug.bin

@xoseperez
Copy link
Owner Author

xoseperez commented Aug 7, 2017

Original comment by Andreas L. (Bitbucket: andreaslink, GitHub: andreaslink-de):


Ok, thanks for the feedback, I was not sure, but good you found the correct place where to place the param. Probably this does not solve your issue as - I guess - the firmware also needs to be somwhat "DOUT-compiled". I'm not quite sure about this, but I read something like this somewhere else.
I would recommend, you install Arduino, get all libs ready and try to recompile on your own. Probably this might solve your issue?

@xoseperez
Copy link
Owner Author

Original comment by Florian P. (Bitbucket: icnw, GitHub: icnw):


Xose, as I'm not sure whether my Touch is broken or I made something wrong I got refunded in the meanwhile. I read that you can't reproduce the error as you don't own a touch.
What do you think of the following proposal: I'll ship you my (broken?) one for testing purposes - of course you can keep it in any case... That's somehow my limited contribution to this project...

@xoseperez
Copy link
Owner Author

xoseperez commented Aug 9, 2017

It could be that the SDK init got corrupted by the wrong flash method, you can first try to erase the flash and then reflash using DOUT gas @andreaslink-de suggests.

So go into flash mode and type:

esptool.py erase_flash

Then reboot into flash mode again and:

esptool.py --port /dev/ttyUSB0 --baud 115200 write_flash --flash_mode dout 0x00000 espurna-1.8.3-sonoff-debug.bin

@xoseperez
Copy link
Owner Author

With 1.9.0 all images are compiled with the DOUT flash mode.

@xoseperez
Copy link
Owner Author

Removing milestone: 1.8.4 (automated comment)

@xoseperez
Copy link
Owner Author

Original comment by treowayne (Bitbucket: treowayne, GitHub: Unknown):


I ran into the same problem. Xose, is it possible that the .bin file was compiled without switching the board type to ESP8285 first?

Nevermind, I compiled 1.9.5 myself with ESP8285 target, uploaded through the web UI, and a working Sonoff Touch broke.

1.9.5 works if I compile and upload directly to the Sonoff Touch through serial interface.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant