Requesting help with error

[lucid]

OAK no longer is broadcasting SSID. 

Status LED on OAK is always on -very small, size of pin head.

Using CH340 USB to Serial converter in an attempt to fix OAK.

When I execute:  esptool --baud 115200 --port COM4 write_flash -fs 32m 0x1000 blank.bin 0x2000 firmware_v1.bin 0x101000 blank.bin 0x102000 blank.bin 0x202000 blank.bin

I receive this error: 

Traceback (most recent call last):
  File "<string>", line 22, in <module>
ImportError: No module named serial
esptool returned -1

Do I need to install python and python serial? 

Operating system is Windows 10 64 bit

William

[digistump]

Please send us an email support at digistump dot com, this sounds like a faulty Oak, we'd like to replace it

[PeterF]

Hi William, Just checking - are you using the copy of esptool downloadable from the OakRestore page? As that error sounds more like something wrong with the executable (and I notice that Erik has just uploaded a new version which seems to be related to this error). You shouldn't need to download Python/PySerial - the executable should be self-contained.

EDIT: There was an fault in the last update to the esptool executable on the page, and Erik has just uploaded a new copy of the file, so give the new copy a try.

[lucid]

Thank you.   Will try new executable to restore Oak.

Appreciate the help!

William

[lucid]

Still not Broadcasting SSID of Oak; after trying the last uploaded esptool.exe.  Status LED is off; does not light at all.

Esptool.exe gives following error; after executing this command line:

esptool --baud 115200 --port COM4 write_flash -fs 32m 0x1000 blank.bin 0x2000 firmware_v1.bin 0x101000 blank.bin 0x102000 blank.bin 0x202000 blank.bin
Connecting...

A fatal error occurred: Failed to connect to ESP8266

Are Oaks still available?   I will go ahead and order a couple.  No need to replace this one. 

I appreciate all that is done for the Oak Community!!!

William

[PeterF]

Hi William,

I think you can order more oaks from the digistump website. I'll let Erik confirm or deny that as last time I looked it says pre-order stll! 

With your problem child (Oak), can I just check the sequence of events and wiring just in case it is recoverable?

You should have three wires connecting your Oak and CH430 - any of the GND pins of the Oak to the GND pin of the CH340, RX on the Oak (P3) to TX of the CH340, and TX on the Oak (P4) to RX of the CH340. You then to connect P2 of the Oak to GND, and power up the Oak. You then run the esptool command, and get the "A fatal error occurred: Failed to connect to ESP8266" message.

Is that all correct? If so, I'm afraid I think it's dead... 

[lucid]

I disconnect the CH430 from the Oak yesterday.  Will make sure pins are reconnected correctly.

Additionally, I will recheck my soldering; could have a cold or bad solder connection.

Thanks for posting.

William

[lucid]

  Confirmed solder joints; re-heated couple of solder connections.  Verified CH430 connections.  Restored Oak to factory.

Successfully updated firmware.  Wiki articles and this Forum are the BEST!  Thank you!

William

[PeterF]

Wooho! Back from the dead... hopefully not as a Zombie Oak!    

Have fun... these Oaks can be a pain in the bleep at times... but that is all part of the fun of a good challenge 

Pete

[lucid]

Tried uploading Arduino OAK Blink example  http://digistump.com/wiki/oak/tutorials/arduino when OAK was doing this:
Oak blinking 0.5 seconds off, and then three blinks of 0.1 second
This resulted in this error:

Sketch uses 259,590 bytes (24%) of program storage space. Maximum is 1,040,368 bytes.
Global variables use 51,076 bytes (62%) of dynamic memory, leaving 30,844 bytes for local variables. Maximum is 81,920 bytes.
OakCLI tool version 1.0.1
Using config file at: C:\Users\lcs--\AppData\Roaming\oak\config.json
Sending file to cloud, to flash Oak-610 (Device ID: d9570401135abc35341c6b28)

Error : An error occurred while flashing the device:

Does the device need reset to Factory and Firmware update done again?

William

[PeterF]

Since it was doing the triple blinks (like this?)... I'm presuming this was the first lot of code since its firmware update? I'd be checking two things...

1) Are you trying to program the right Oak - is Oak-610 the one you're trying to program? If not, you need to run the OakCLI tool to switch between oaks. You can either download it from here or run the copy that is probably located in (on your system) "C:\Users\lcs--\AppData\Roaming\Arduino15\packages\digistump\tools\oakcli\1.0.1". You need to run it every time you want to change Oaks to program.

2) What is happening on the particle dashboard logs when you're trying to upload to this Oak? For starters, you can unplug it from the power, and power it up, and see if the log says it's in config mode. If not, remove the power, connect Pin 1 to GND, and re-connect the power. You can remove the jumper after 2-3 seconds. It should now be in safe/config mode, and the particle logs should indicate that. If not, maybe the wifi is not configured properly, and you'll need to use SoftAP Configurator to connect to your WiFi again. Otherwise, it should be in config mode, and you should see a spark/flash/status message indicating that a firmware update has started shortly after the Arduino IDE indicates that the firmware is being uploaded, and a matching spark/flash/status fail message (known particle bug) indicating that the firmware update attempt has completed.

Pete

[lucid]

 

Found I had left Wifi router in repeater mode from an earlier project; switched to access point mode.  All is working!!!   

It really makes it difficult to be behind a second router!
Quite the learning experience!


William

[PeterF]

Oh dear... that does make things a bit hard!  Thanks for the good laugh... it's not just me who does not so clever things like that... like the never to be mentioned again scratching head for around 30 minutes thinking I had a dead pin on the Oak or dead led, trying all sorts of different code, only to realise that I hadn't specified the pin to be an output... doesn't blink very well when you miss that line! 

Pete