Oaks not updating

[exeng]

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

[starwolf73]

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

[exeng]

Thanks. Next time I'm needing to update I will give your suggestions a try.

[vil]

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?

[starwolf73]

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

[vil]

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.

[starwolf73]

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.

[pauln]

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:

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):

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?

[TravisF]

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.

[emardee]

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

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!

[TravisF]

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:

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!

[digistump]

@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

[pauln]

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!

[spiderbike]

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


[spiderbike]

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

• Disabled - HT mode (802.11n)
• Removed Spaces, capitals, and full stops from SSID
• only used alphanumeric characters for password

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.