Digistump Forums

The Oak by Digistump => Oak Support => Topic started by: Grisbane on February 18, 2016, 03:10:35 pm

Title: Oaks not updating
Post by: Grisbane on February 18, 2016, 03:10:35 pm
I'd like to start a new thread for all of us who have not been able to get our Oaks updated.

I have 2 Oaks and have been trying to get them updated via http://rawgit.com/digistump/OakSoftAP/master/config.html for 3 weeks now with no success.  I've tried multiple times almost daily.

I'd love to hear what others have done to make this work.  Those who are also having trouble can join and get updates to this thread and hopefully drop off as their Oaks start updating.

Thanks!
Title: Re: Oaks not updating
Post by: koioslabs on February 18, 2016, 03:14:00 pm
I had a lot of trouble getting mine to update, what worked was to move it as far away from my laptop as i could, maybe I just got lucky. I also was as far from my multiple ap's (all on same ssid) as I could get in my home.

I'm on a late 2013 macbook pro...
Title: Re: Oaks not updating
Post by: DeuxVis on February 19, 2016, 07:48:15 am
What I don't understand is why there is no available information about how to update it through a usb-to-serial adapter.

This is certainly possible ? Or am I missing something obvious ?
Title: Re: Oaks not updating
Post by: Grisbane on February 19, 2016, 11:22:36 am
Thanks koioslabs!  I've tried configuring 2 different Oaks to go through 2 different wireless routers from different power supplies and different locations.  Still no go.  I don't think that the laptop/computer matters as much since it all happens through the rawgit.com site.

Which brings up DeuxVis's point.  Why can't we just access these devices through our USB ports on the computers like any other Arduino device?  Particle.io sounds convenient for some, but should not be the ONLY way to get updates and upload programs.

I'm sure DigiStump is working hard to get these fixed, but more communication would be nice, even if just to acknowledge the problems and let us know they are working on it.  If that is happening in a distinct location that I'm not aware of, please someone let me know.

Thanks!
Title: Re: Oaks not updating
Post by: tcarleton on February 19, 2016, 09:54:52 pm
Can someone post a list of "good" routers (aka: works with the current update process)  I'm not convinced this is a router issue, and I'm willing to run to the store and buy a couple of "good" routers for the cause to test that theory.

I've skimmed through the SoftAP repository and it appears (to me, who knows nothing about javascript) the connectivity to the cloud providers is obfuscated. There can be many valid reasons for it, I'm not criticizing that, but it makes it hard to reverse engineer the firmware download process for troubleshooting.   (Are we downloading multiple payloads from multiple hosts? Are the hosts globally load balanced but I'm getting sent to the other side of the world? Is there a bad hop on my providers side?)

Continually trying updates has shown that I have two different routers that sometimes work and sometimes fail. I've had Oaks activate in three attempts, others that took attempts over several days to activate. I'd like to help, but failing a method to load the firmware from my own network (eliminate everything past my router) I don't see a point in trying more updates.

So, if anyone has a list of known good routers for the firmware updates (ideally, Erik says they work), I'm willing to eat the cost for a couple of models and try them.
Title: Re: Oaks not updating
Post by: digistump on February 19, 2016, 10:16:28 pm
Acknowledgement and work on these issues is happening both on github.com/digistump/OakCore and on Kickstarter updates.

You can't connect an Oak to a USB port - as we've tried to make clear from the very start, it is an OTA only device, USB is power only. You can use a USB to Serial adapter to load things on to it (it works!), but that of course isn't the main goal. As far as Particle.io being the only way - you can also use a serial adapter, you can use a local particle server, or you can use your own custom update firmware. That said, the particle updates are working for everyone who has got that far, it is the initial update from our servers (not Particle) which comes to the Oak over HTTPS that isn't working for some.

As far as how to update with a usb to serial adapter - the reason for putting the Beta out there is to get feedback on the update process and firmware, if we opened that up right at the start then we would not have gotten much feedback that we need to solve these issues. Not to mention my focus has been on solving the issues as best I could first. We'll be releasing the bin file to update to the latest firmware along with the first non-beta firmware release, if nto sooner (as soon as I get a chance). You can build it form the OakSystem repo already.

-- while I was writing this tcarleton posted their message---

I'm not convinced it is a router issue either, not convinced either way, as I'm still only able to reproduce the issue very sporadically - and I'm working on some firmware that people with serial adapters that are having issues can run, and it will generate a better log to serial that might help discover what is wrong. I suspect it may have to do with connection speed/router speed/basically how quickly the data is being thrown at the Oak.

Everything is SoftAP is minified and pulled into a single file because your browser needs to have that whole file in memory, since you disconnect from your internet during the process. It has little to do with the update process, other than the wifi connection itself, if you watch the network inspection tab you'll see the Oak just gets your wifi connection data from setup, this triggers a restart to the update rom and that downloads the update from digistump's servers - the Oak doesn't get the update from Particle. That said, you can find all of the sources for the included js on particle's github (github.com/spark) in the SparkJS/ParticleJS project and the softap-setup-js repos - we should pull those all into sources file in our repo in the future.
Title: Re: Oaks not updating
Post by: tcarleton on February 19, 2016, 10:56:48 pm
Thank you for the update - it was very helpful!
Title: Re: Oaks not updating
Post by: PeterF on February 20, 2016, 02:44:26 am
Indeed... thanks for that Erik.

If you want any more Oaks donated to the debugging cause... I have three virgin Oaks (out of five) yet to be powered up for the first time, and have 3V3 USB-to-Serial adapters. The other two are running v0.9.3 and running some simple blinky sketches, after an hour or so of persuasion to update and register on Particle. I hit two hurdles in the end - the first update (two to  four tries fixed that), and particle registration (connecting via a second AP seemed to fix that). Haven't had any issues since then. I got SoftAP to kick in again, and connected back to the normal AP/router, and didn't have any issues with them since.

Pete
Title: Re: Oaks not updating
Post by: exeng on February 21, 2016, 11:00:26 pm
Been trying to bring a second Oak up to the beta 3 firmware without success. It's extremely frustrating to literally spend hours just trying to get firmware installed.  I have observed two patterns that present themselves when the upload fails. The first one, I typically see when starting a first update after a fresh restore. When the firmware update is initiated by SoftAP the rapid flash appears to last almost long enough to complete but does not yield a successful install. Subsequent retries more often than not, flash rapidly for about 5 or 6 times, then back to the slow flash. The latter is an obvious sign of failure but now I have to wait for the timer to run down to check for what I already know will be the result. Seems like the fails are either early in the update or very close to the end.

Has there been any clues as to why these uploads are failing? Is it dropped packets, timeouts, race conditions? Is there anything we can do to help debug the problem? I've literally spent half the day trying to update this one Oak. At least I have 1 that is up and running.
Title: Re: Oaks not updating
Post by: DeuxVis on February 22, 2016, 12:15:18 am
Thanks for taking the time to reply erik, I understand.

I've been unsuccessful in getting the initial update onto any of my 3 oaks, I'll try on a friends wifi router when I get a chance.
Title: Re: Oaks not updating
Post by: Grisbane on February 22, 2016, 08:52:45 am
Thank you for the reply Digistump/Erik!

I'll start looking for communication updates on the sites that you listed.  I think knowing where to look will help others having similar issues.

I just got my USB-Serial adapter in and will figure out how that works next.  I'll start with restoring them to factory and will move on from there.

Thanks for all your hard work!  I know this is beta and am glad to be a part, even if beta's can be quite frustrating at times.  The "happy dance" when it works will all be worth it though!

Thanks again!
Title: Re: Oaks not updating
Post by: exeng on February 22, 2016, 09:48:06 am
UPDATE... Tried again this morning and the Oak updated on the first try. All I can surmise is that Wireless network traffic is much lower this AM than it was last night and perhaps this helps ensure that packets are not dropped.

If my frustration (in my previous post) sounded like a complaint, it was not. Just an expression of the frustration that occurs when you just want to get the update to work and you have no control.

Yes, Erik (Digistump) is done an excellent job supporting the Oak and communicating to us all.
exeng
Title: Re: Oaks not updating
Post by: digistump on February 22, 2016, 05:17:10 pm
I was finally able to replicate the update issues reliably - specifically they seem to involve fast connections allowing the device to download data so fast that each loop to write the data to the Oak's memory goes so fast that it outpaces the Oaks ability to erase the next block of memory before writing it. (This bug seems to possibly have some deep roots in the chips internal libraries).

I was not able to reliably replicate this previously because, being in a rural area, my internet connection is slower than many (1.5mbps on a good day) and all of my local testing was done with extensive debugging output turned on, which slowed down the loops enough to prevent this from showing up. Stripping my debug output down significantly and ensuring no output occurred during the write/erase loops, while also hosting it locally within my network allowed me to reproduce the issue 100% of the time.

My fix is to have the web server send only one sector worth of data every 50 milliseconds. This results in a total time of at least 150ms per sector, which seems to fix this issue. I've tested it locally and remotely with 100% success.

This fix is live and you can test it by retrying the update (no changes to the Oak or Config App needed).

If the update still fails to work then please download the newest OakRestore here (https://github.com/digistump/OakRestore) and follow the instructions to provide the debugging output so we can look into it further, as this very well could be one issue of several.

(Sorry that's very long winded as I'm copying the text from a Kickstarter update I'm preparing, but seems worth posting here)
Title: Re: Oaks not updating
Post by: rwohleb on February 22, 2016, 05:54:42 pm
Does this server change only affect that initial update/provisioning via SoftAP? It took a crazy number of tries, but I was able to get it done last week. However, deploying code via Particle has been hit-or-miss and I'm wondering if it's a related issue.
Title: Re: Oaks not updating
Post by: digistump on February 22, 2016, 06:05:51 pm
Initial update only - Particle is a different beast that we haven't heard much feedback about issues with except for when the update does not start at all (hopefully fixed in the next release that I'm putting together now, along with wayy faster updates from particle) - please let me know if you are experiencing other issues with the Particle updates
Title: Re: Oaks not updating
Post by: TravisF on February 22, 2016, 07:42:20 pm
I just tried all my oaks again and they still won't download the firmware. My serial to USB adapter came in finally today so I'm trying the OakRestore but I'm running into a problem with that too. When I run the esptool command line it just gives a fatal error and says it couldn't connect to the ESP8266. Before it returns that I can see the LED on the adapter blinking like it is trying to talk to the Oak but then fails. I know the adapter is working because if I set the baud rate to 74880 and disconnect pin 2 from ground I get this: 
ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0


But then when I connect pin 2 to ground and try running the esptool program it can't connect:
C:\Users\Travis\Desktop\restore>esptool --baud 115200 --port COM4 write_flash -fs 32m 0x1000 blank.bin 0x2000 oaksetup_restore.bin 0x0081000 oakupdate_restore.bin 0x101000 blank.bin 0x102000 blank.bin 0x202000 blank.bin
Connecting...

A fatal error occurred: Failed to connect to ESP8266
Title: Re: Oaks not updating
Post by: digistump on February 22, 2016, 08:37:52 pm
Thanks for trying them again TravisF

A bad connection can cause that error, even if it is working to show the bootloader output - could be a bad USB TX to OAK RX connection (not used for boot message) or another one being flaky
Title: Re: Oaks not updating
Post by: TravisF on February 22, 2016, 08:47:47 pm
The correct pin to ground is the one labeled RST, right? I went ahead and soldered the headers on all 3 of my oaks but I'm getting the same error with all of them
Title: Re: Oaks not updating
Post by: digistump on February 22, 2016, 08:49:32 pm
Pin 2 should go to GND - meaning the pin labeled P2 on the back of the Oak - right next to the P3/RX pin
Title: Re: Oaks not updating
Post by: TravisF on February 22, 2016, 09:01:30 pm
OHHHHHHHHHHHHHHHHHHH

P2/SCL? I'll try that one now

It's flashing!
Title: Re: Oaks not updating
Post by: TravisF on February 22, 2016, 09:06:55 pm
 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
PARSING HTTP HEADER
HTTP/1.1 200 OK
FILE LENGTH: 778096
START WRITING UPDATE - NO OUTPUT SHOULD BE EXPECTED FOR UP TO 120 SECONDS
./+./+./+./+./+./+./+./+./+./+./+./+
Exception (28):
epc1=0x40103187 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000024 depc=0x00000000

ctx: cont
sp: 3fff1350 end: 3fff16f0 offset: 01a0

>>>stack>>>
3fff14f0:  3ffeb3ac 7fffffff 3ffeb3ac 00000001
3fff1500:  40104cc5 36363636 36363636 36363636
3fff1510:  00040000 00d960c2 505f2200 3ffeb37c
3fff1520:  4000050c 3fffc278 40104b48 3fffc200
3fff1530:  00000022 00000030 00000000 ffffffff
3fff1540:  4028293b 00000030 00000013 ffffffff
3fff1550:  40282938 0000002f 00000000 00000001
3fff1560:  fbf8ffff 04000002 3feffe00 00000100
3fff1570:  0000001a 00000018 04000102 00001000
3fff1580:  00001000 0000020d 0000000c 00000030
3fff1590:  3fff62e5 3fff1600 3fff2dd0 402995dc
3fff15a0:  8157e3f3 8e9b3ea3 dc312ff1 36aa44ed
3fff15b0:  5809fcee 00000000 3fff06d0 00005e3f
3fff15c0:  00000000 4000444e 40283e14 3fff06d0
3fff15d0:  00000000 400041bc 60000200 3fff57f0
3fff15e0:  00000100 40004b14 00001000 0020d000
3fff15f0:  00000100 3fff47f0 3fffc718 0020e000
3fff1600:  00001000 0000000f 401015f8 00001000
3fff1610:  3fff47f0 0000020d 0000000c 0000000f
3fff1620:  3fffc718 3fff47f0 00000000 401015fd
3fff1630:  0020d000 40282938 00001000 00001000
3fff1640:  3ffe9390 00000000 00002710 0000218d
3fff1650:  00000000 3fff2a40 3fff2d78 3fff2cf0
3fff1660:  0000000f 00000000 3fff2e98 0000002f
3fff1670:  00000001 00000001 40282c24 3fff045c
3fff1680:  000b1f70 00000000 00000001 00000000
3fff1690:  3fff47f0 00202000 00000202 40284dec
3fff16a0:  3ffe92d0 3fff06c8 3fff1740 3fff06c8
3fff16b0:  00003d34 3fff045c 3fff1740 402829fb
3fff16c0:  00003d34 3fff1740 3fff05b4 40282bca
3fff16d0:  3fffdc20 00000000 3fff06c0 40283e52
3fff16e0:  00000000 00000000 3fff06d0 40100114
<<<stack<<<

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - E,BU,0
Title: Re: Oaks not updating
Post by: TravisF on February 22, 2016, 09:16:45 pm
Tried again, this time it said this:

PARSING HTTP HEADER
HTTP/1.1 200 OK
FILE LENGTH: 778096
START WRITING UPDATE - NO OUTPUT SHOULD BE EXPECTED FOR UP TO 120 SECONDS
./+./+./+./+./+./+./+./+./+.SOCKET READ TIMEOUT
UPDATE FAILED

And a third time it just rebooted without saying anything:
PARSING HTTP HEADER
HTTP/1.1 200 OK
FILE LENGTH: 778096
START WRITING UPDATE - NO OUTPUT SHOULD BE EXPECTED FOR UP TO 120 SECONDS
./+./+./+./+./+./+./+./+./+./+./+
 ets Jan  8 2013,rst cause:4, boot mode:(3,0)

wdt reset
load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - H,BU,0
Title: Re: Oaks not updating
Post by: tcarleton on February 22, 2016, 10:04:45 pm
(Posting my logs @ https://github.com/digistump/OakCore/issues/47)

One thing that sticks out to me -- The ./+./+ sequence is really inconsistent. Sometimes it crawls, sometimes it fills the line almost immediately.
Title: Re: Oaks not updating
Post by: digistump on February 22, 2016, 10:33:01 pm
Thank you both - I was able to duplicate this and I"m working on it now
Title: Re: Oaks not updating
Post by: digistump on February 22, 2016, 10:52:16 pm
If either of you can retest I'd be interested to know if it is working for you now - note you will need to re-download oakupdate_restore.bin from the repository
Title: Re: Oaks not updating
Post by: tdk337 on February 23, 2016, 06:48:46 am
When you say not updating I'm assuming you mean you received an error message while registering your Oak to Particle.io via webconfig tool located at http://rawgit.com/digistump/OakSoftAP/master/config.html (http://rawgit.com/digistump/OakSoftAP/master/config.html). I've posted my solution at http://digistump.com/board/index.php/topic,1940.msg9203.html#msg9203 (http://digistump.com/board/index.php/topic,1940.msg9203.html#msg9203).
Title: Re: Oaks not updating
Post by: TravisF on February 23, 2016, 07:58:56 am
If either of you can retest I'd be interested to know if it is working for you now - note you will need to re-download oakupdate_restore.bin from the repository
I'll try it as soon as I get home tonight and report back here
Title: Re: Oaks not updating
Post by: TravisF on February 23, 2016, 08:00:19 am
When you say not updating I'm assuming you mean you received an error message while registering your Oak to Particle.io via webconfig tool located at http://rawgit.com/digistump/OakSoftAP/master/config.html (http://rawgit.com/digistump/OakSoftAP/master/config.html). I've posted my solution at http://digistump.com/board/index.php/topic,1940.msg9203.html#msg9203 (http://digistump.com/board/index.php/topic,1940.msg9203.html#msg9203).
Our problem is the firmware won't even finish downloading. Not even making it to the point of it trying to contact particle. Also for what it's worth I've had zero luck running the config.html from github. I have to download it to my computer and run it locally.
Title: Re: Oaks not updating
Post by: eumb on February 23, 2016, 01:19:31 pm
This is my attempt to update using http://rawgit.com/digistump/OakSoftAP/master/config.html

Serial log:


 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2


 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0



Oak is not updated.

I will attempt a force update and inform you how it goes
Title: Re: Oaks not updating
Post by: TravisF on February 23, 2016, 04:44:21 pm
No change with the newest oakupdate_restore.bin, still getting the socket timeout
Title: Re: Oaks not updating
Post by: exeng on February 24, 2016, 02:23:27 pm
Erik, here the debug for the quick fail (only a few rapid flashes 5-6) Followed by a long cycle fail (rapid flash for a long time but fails).

Quick fail:

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
NO CLIENT
COULD NOT CONNECT TO DIGISTUMP UPDATE SERVER
UPDATE FAILED

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0

Long cycle failure:

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
PARSING HTTP HEADER
HTTP/1.1 200 OK

FILE LENGTH: 778096

START WRITING UPDATE - NO OUTPUT SHOULD BE EXPECTED FOR UP TO 120 SECONDS
./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+.SOCKET READ TIMEOUT
UPDATE FAILED

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0


Title: Re: Oaks not updating
Post by: starwolf73 on February 24, 2016, 08:56:10 pm
If this can help, I just post my experience on upgrading my 10 succesfully OAKs. I did find some interesting trick that work for me to upgrade them, maybe it will work for you.
http://digistump.com/board/index.php/topic,2046.0.html
Title: Re: Oaks not updating
Post by: exeng on February 24, 2016, 11:04:04 pm
Thanks. Next time I'm needing to update I will give your suggestions a try.
Title: Re: Oaks not updating
Post by: vil on February 25, 2016, 11:59:19 am
My two oaks blink a new pattern which should mean initial firmware is updated but there is no wifi signal anymore. What can I do?
Title: Re: Oaks not updating
Post by: starwolf73 on February 25, 2016, 01:37:49 pm
You are almost there, just need to reconfigure your OAK again to completed the WIFI config and Cloud Particle portion. See my post on Phase 3 for more detail.  http://digistump.com/board/index.php?topic=2046.msg9239#msg9239
Title: Re: Oaks not updating
Post by: vil on February 26, 2016, 07:45:09 am
Thanks for your help Eric. You are right system-version of my oaks is 5 now.
But those cannot be registered in particle cloud even using your phase 3 way.

Is there any possibility to work with them without clouds?
Remote programming is very good thing but not required everywhere.
I need wireless communication with my websites simply.
Title: Re: Oaks not updating
Post by: starwolf73 on February 26, 2016, 08:27:26 am
That is interesting, my System-Version for all my OAKs is 2 and they all connect well to Particle Cloud. Maybe Erik or OAK team can shed the light on what those version mean. My recommendation is look at the Phase 1 of my post and change Wireless Type to B.

As for programming it remotely, I believe it is still in the plan of the OAK team to have a local cloud. We may have to wait until the dust come down and we have a stable firmware.
Title: Re: Oaks not updating
Post by: pauln on February 26, 2016, 08:11:14 pm
I've got the same issue as vil - after the firmware update, the LED gives the new blink pattern, but the Oak is neither connecting to my wifi network nor running its own ACORN-XXXXXX network for me to connect to in order to continue the process.  I've used OakRestore to restore back to the starting point and try again, but every time that the update actually runs, it appears to complete successfully (new blink pattern), but there's no wifi connection or hotspot.

I've connected a serial adapter and checked the debug output during the update; sometimes I get a failed attempt (failed to connect to digistump update server), but it typically seems to run fine: it ends with "UPDATE OK - BOOT TO ROM", followed by a number (the last couple of runs have produced 58 and 55), then a regular boot sequence.  Here's my most recent attempt:
Quote
ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
PARSING HTTP HEADER
HTTP/1.1 200 OK

FILE LENGTH: 778096

START WRITING UPDATE - NO OUTPUT SHOULD BE EXPECTED FOR UP TO 120 SECONDS
./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+UPDATE OK - BOOT TO ROM
55

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,8

In case the OTA update was somehow failing the same way repeatedly, I've now also tried the "force update" option (pushing the updated firmware via serial), as per the OakRestore readme; it leaves the Oak in exactly the same state: the "new" blink pattern, but no wifi.

When the Oak is in this state (either after OTA or forced update), the boot messages are as follows (at 74880 baud):
Quote
ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0

Could the current update be bugged?
Title: Re: Oaks not updating
Post by: TravisF on March 01, 2016, 10:26:15 am
So any updates on fixing the server hosting the firmware? Haven't heard anything for over a week since we posted all the debug logs and no changes, yet you keep pushing out updates to the arduino libraries that most of us can't even use ... it's frustrating that you keep barreling ahead with further development while leaving the majority of the users unable to do anything with the oaks.
Title: Re: Oaks not updating
Post by: emardee on March 01, 2016, 11:31:24 am
This was Erik's comment in on Kickstarter last night:

Quote
Creator Erik Kettenburg about 11 hours ago

Still working on the update - calling in a night early due to a fever and cold - but I'll finish it up and get it out tomorrow - highlights in short:

Beta 5 (0.9.5) is up and fixes issues that caused the rollback of 0.9.4, also adds status messages to uploads.

LiPo kits are leaving China tomorrow, once they get here those orders will ship!

We're still hard at work on the issues with the first update.

@Markus - yes this is a software issue, the oak ships with firmware to update itself, that firmware seems to have issues holding a wifi connection with certain router/connection speed/router setup combinations to download the update - this effects only the very first update when you configure a brand new device - our main focus to remedy this manipulating things on the server end to try to slow down the rate the data hits the Oak for this update, as well as provide some concise troubleshooting instructions for those who can't get it to work out of the box.

Sounds like he is very aware of the problems and doing his best to sort them. This is a combination of server tweaks, and working on some troubleshooting steps to get the first firmware installed for those with problems. Once first firmware is installed, you should be fine.

I'm expecting he will give a full Kickstarter Update in next day or so, with detailed info about latest beta 0.9.5, and hopefully said troubleshooting steps. However, bear in mind, this is still beta. Until the firmware is proved to be stable there will potentially be problems for everyone (hence having to roll back 0.9.4). The only way Erik can get us to stable is by advanced users testing each beta and giving him feedback so he can fix all bugs, (which people have been doing). Mainstream users are best to wait for stable though, and therefore stable is the ideal time for the majority to get on-board. Equally, Erik is clearly working on the connection problems too, so that there is a cast iron method to get everyone working by then. So I would say the firmware is in beta and the troubleshooting is also in beta. Hopefully both will come out of beta soon!
Title: Re: Oaks not updating
Post by: TravisF on March 01, 2016, 12:11:19 pm
Yes, I saw the update and I posted a comment on there too. My point is that I'm very frustrated that he continues to provide update after update on the firmware, instead of working on the server so that more people can test the firmware.

As soon as the updating is fixed, there are going to be hundreds of extra people to help debug the firmware and find new bugs to fix. In my opinion it would have been a better use of time to get the majority of people able to help test the firmware from the get-go, instead of alienating it to a select few who have the random luck of being able to install it.

It was a great step when he posted a new restore file that people could flash to get more debug information to help him, but the debug information is very generic and I don't think it has provided very much helpful information.  That was over a week ago and he hasn't provided a single update since then, and is instead back to working on the firmware that only a handful of people can install.

This was Erik's comment in on Kickstarter last night:

Quote
Creator Erik Kettenburg about 11 hours ago

Still working on the update - calling in a night early due to a fever and cold - but I'll finish it up and get it out tomorrow - highlights in short:

Beta 5 (0.9.5) is up and fixes issues that caused the rollback of 0.9.4, also adds status messages to uploads.

LiPo kits are leaving China tomorrow, once they get here those orders will ship!

We're still hard at work on the issues with the first update.

@Markus - yes this is a software issue, the oak ships with firmware to update itself, that firmware seems to have issues holding a wifi connection with certain router/connection speed/router setup combinations to download the update - this effects only the very first update when you configure a brand new device - our main focus to remedy this manipulating things on the server end to try to slow down the rate the data hits the Oak for this update, as well as provide some concise troubleshooting instructions for those who can't get it to work out of the box.

Sounds like he is very aware of the problems and doing his best to sort them. This is a combination of server tweaks, and working on some troubleshooting steps to get the first firmware installed for those with problems. Once first firmware is installed, you should be fine.

I'm expecting he will give a full Kickstarter Update in next day or so, with detailed info about latest beta 0.9.5, and hopefully said troubleshooting steps. However, bear in mind, this is still beta. Until the firmware is proved to be stable there will potentially be problems for everyone (hence having to roll back 0.9.4). The only way Erik can get us to stable is by advanced users testing each beta and giving him feedback so he can fix all bugs, (which people have been doing). Mainstream users are best to wait for stable though, and therefore stable is the ideal time for the majority to get on-board. Equally, Erik is clearly working on the connection problems too, so that there is a cast iron method to get everyone working by then. So I would say the firmware is in beta and the troubleshooting is also in beta. Hopefully both will come out of beta soon!
Title: Re: Oaks not updating
Post by: digistump on March 01, 2016, 12:40:44 pm
@TravisF - please see my response to your comment on Kickstarter, and todays update (when it is finished).

Shedding some light on system versions:
0.9.1-system version 1
0.9.2-system version 2
0.9.3-system version 2 (mistakenly not incremented)
0.9.4-system version 5 (see below)
0.9.5-system version 5

System version jumped to 5 at 0.9.4 because Particle wants to see a version 5 or higher reported to them to enable fast updates on their end. 0.9.4 was quickly rolled back due to major issues with wifi connectivity - since few people installed it I went ahead and kept the version at 5 for 0.9.5 as that allowed me to align the two as well
Title: Re: Oaks not updating
Post by: pauln on March 02, 2016, 02:18:01 am
Beta 5 appears to have fixed the issue I was having.  I used OakRestore to revert to the initial state again, and got a first-time successful update which allowed me to continue the process and claim the Oak on the Particle cloud.  Thanks for all the hard work!
Title: Re: Oaks not updating
Post by: spiderbike on March 02, 2016, 06:40:46 am
i restored my Oak following https://github.com/digistump/OakRestore

but Running the http://rawgit.com/digistump/OakSoftAP/master/config.html I get the following from the serial output

Code: [Select]
ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
NO CLIENT
COULD NOT CONNECT TO DIGISTUMP UPDATE SERVER
UPDATE FAILED

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0


 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
NO CLIENT
COULD NOT CONNECT TO DIGISTUMP UPDATE SERVER
UPDATE FAILED

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0


 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
NO CLIENT
COULD NOT CONNECT TO DIGISTUMP UPDATE SERVER
UPDATE FAILED

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0


 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
NO CLIENT
COULD NOT CONNECT TO DIGISTUMP UPDATE SERVER
UPDATE FAILED

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0


 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
NO CLIENT
COULD NOT CONNECT TO DIGISTUMP UPDATE SERVER
UPDATE FAILED

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0

rl▒▒r▒▒#▒n▒▒▒

▒▒p▒|▒▒▒▒x▒▒ǒ▒▒p
▒nn▒▒;▒nĒ▒▒
b▒$▒rrp▒n▒▒▒
▒▒▒l▒


b▒n▒▒n▒▒▒▒▒
b▒▒>~▒n▒▒▒▒l`▒▒#▒n▒rnr▒▒▒;▒▒
?▒;▒p▒n▒▒܀
▒r▒▒
p
p▒▒<▒▒l▒▒
b▒ľ~▒n▒▒▒
r▒▒#▒n▒rnr▒▒▒;▒▒
?▒rr▒ےn▒▒▒rr~▒▒9n▒nn▒▒▒▒lb▒▒|
▒▒▒b▒$`
 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
NO CLIENT
COULD NOT CONNECT TO DIGISTUMP UPDATE SERVER
UPDATE FAILED

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0


 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
NO CLIENT
COULD NOT CONNECT TO DIGISTUMP UPDATE SERVER
UPDATE FAILED

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0


 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
NO CLIENT
COULD NOT CONNECT TO DIGISTUMP UPDATE SERVER
UPDATE FAILED

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0


 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
NO CLIENT
COULD NOT CONNECT TO DIGISTUMP UPDATE SERVER
UPDATE FAILED

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0
Title: Re: Oaks not updating
Post by: spiderbike on March 02, 2016, 07:05:16 am
tried again, different error first time, then back to failure "COULD NOT CONNECT TO DIGISTUMP UPDATE SERVER"

Code: [Select]
ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
PARSING HTTP HEADER
HTTP/1.1 200 OK
FILE LENGTH: 778096
START WRITING UPDATE - NO OUTPUT SHOULD BE EXPECTED FOR UP TO 120 SECONDS
./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./                                                                                +./+./+./+./+./+./+./+./+.SOCKET READ TIMEOUT
UPDATE FAILED

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0


 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2

START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
NO CLIENT
COULD NOT CONNECT TO DIGISTUMP UPDATE SERVER
UPDATE FAILED

 ets Jan  8 2013,rst cause:2, boot mode:(3,0)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0

Finally managed to update by doing the following, ran OakRestore again, Added new wireless network, may be just coincidence the wifi changes

the things I changed were


I`ll solder on some more headers to other Oaks soon, and try with them, to see which change helped, or if it was just luck.
Title: Re: Oaks not updating
Post by: jdeon on March 02, 2016, 08:12:02 am
Been trying to update my Oak using my router, no dice so far.  Been trying last night and this morning.  My internet is 200 mbit, and my router is running Advanced Tomato firmware, although most/all the settings are pretty stock.  I've tried disabling WPA and setting the network to B only, no improvement. 

Code: [Select]
ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BP,2


 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

OakBoot v1 - N,BU,0

There's not much debug info here, so I don't know that it's getting that far in the update process.

I've got a total of 3 Oaks and a serial adapter.  I'm also a professional firmware developer (although I've never worked with this chip before and most of my experience is in C, not Processing).  I'm willing to try most anything and can give lots of debug help :) 
Title: Re: Oaks not updating
Post by: emardee on March 02, 2016, 01:48:47 pm
I've got a total of 3 Oaks and a serial adapter.  I'm also a professional firmware developer (although I've never worked with this chip before and most of my experience is in C, not Processing).  I'm willing to try most anything and can give lots of debug help :) 

I'm sure Erik can use your help. Have you seen the github $1000 bounty (https://github.com/digistump/OakCore/issues/54) with some testing Erik is happy to pay for?
Title: Re: Oaks not updating
Post by: exeng on March 04, 2016, 10:25:24 pm
Not sure what thread to post this on (there are so many discussing update fails)...

Tried to update a second Oak to 0.9.5 and was getting multiple fails of the could not connect to the digistump server flavor (should have saved the serial output). In any case, I reset my router (leaving all it's original settings in place B/G 54mbps) and bang, the Oak updated on the very next try. Don't know if this is repeatable, but it's worth a try if you are continually failing updates.
Title: Re: Oaks not updating
Post by: Joelbear5 on March 06, 2016, 10:44:31 pm
I just spent 10 hours updating 3 Oaks and eventually had success on all 3. The first one took 3 tries on my router (Netgear C3700-100NAS), the second 2 would not update with my router (through 1 wall, about 20 ft away). It said it failed updating the firmware every time.

I decided to hot-spot my phone and try that. This time success. When I used the SoftAP to log into my phone's hot-spot, I noticed the Oak connects, then disconnects, then connects again. This time, the Oak took more than the 60 second count-down to update the firmware (about 63 seconds as judged by the fast blinky LED). After updating firmware successfully, I shut down the hot-spot, power-cycled the Oak, then it went into AP mode where I used the SoftAP again to change the SSID/password for the Oak AP list back to my house router, and it worked fine.

Question: Is the **connect, then disconnect, then connect** having issues with some of the routers? I assume my phone (Samsung Galaxy S4) has a lot more processing power than my router, and had zero devices connected to it, while my router has about 6.
Title: Re: Oaks not updating
Post by: Mrb0y on March 08, 2016, 07:27:16 pm
My oak updated with the OTA http://rawgit.com/digistump/OakSoftAP/master/config.html
I attempted this several times at different distances from a decent router with no connectivity issues. On the last successful attempt I had ran through the configuration procedure and after connecting to my Wi-Fi / internet the oak only rapid blinked for a moment then back to the slow blink. I thought another failed update. I power cycled the oak by unplugging it from the USB and reconnecting. Once powered on again the oak started the rapid flashing indicating the firmware update. It finished and then started the 3 slow blinks that it was online. I already had a particle account for other products so I checked my account and it showed an unnamed photon on the device list. I checked my router and the oak was connected. The odd thing was the acornxxxx Wi-Fi was also open and once connected it showed "soft AP setup" at 192.168.0.1. I went through the set up script and it checked my oak and told me that it was updated and ready to use. I did all of this from my Android tablet using the chrome browser and the particle.io app. Hope this information helps.
Title: Re: Oaks not updating
Post by: Z69 on March 22, 2016, 11:11:56 am
I had my Oak working fine, just to find uploads failing again......
So i did the restore thing thinking that it has gone all wonky again....
No i get "SOCKET READ TIMEOUT" every time i try to update.

Changed my router to "B" , same. Here is the serial data and an attachment to show router trafic
 
START UPDATE ROM
WIFI
WIFI CONNECT
GO TO UPDATE
START UPDATE
HOST LOOKUP OK
PARSING HTTP HEADER
HTTP/1.1 200 OK
FILE LENGTH: 778096
START WRITING UPDATE - NO OUTPUT SHOULD BE EXPECTED FOR UP TO 120 SECONDS
./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+./+.SOCKET READ TIMEOUT
UPDATE FAILED

 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x40100000, len 3632, room 16
tail 0
chksum 0xc0
load 0x3ffe8000, len 352, room 8
tail 8
chksum 0x82
csum 0x82

Any idea where i can look?
Title: Re: Oaks not updating
Post by: pck on May 16, 2019, 10:30:09 pm
You know oak ??
สมัครufabet (http://www.ufabet99.vip)