Successfully firmware update, failed particle registration

[driffster]

Hi, I managed to update to v5 firmware manually, but the wireless still refused to work, until I put my network exactly like it was the first time: guest network with the same broadcasted SSID. It would not connect to my main network or even the same guest network with same SSID if it was not broadcasted. It almost looks like this oak refuse to change its wifi parameters, even after 2 factory resets. Are the wifi parameters kept when we factory reset it?

Now though it still didn't get claimed on particle (despite being online as far as I can tell by my router). I could do it manually, didn't find how searching around. Not that useful if I can't change its wifi parameters though.

I can't connect to it once it is connected to the guest network. I had to disable the guest service for the oak to broadcast again. After doing it that tried changing settings for the wifi, still not connecting to the secured network..

Do you want a full dump of that oak?

here is the info I get now from it:
{"id":"d957040013e4a82b75daf520","claimed":0,"claim_code":"mkwSHAe/xFDBT0DFKx3vOSjpyvVzg6uhlx1oRJ65HKl7IAzvlf46NuobiwNbrmh~","server_address_type":1,"server_address_domain":"device.spark.io","system_version":5,"version_string":"1.0.2","meta_id":0,"meta_data":"","first_update_domain":"oakota.digistump.com","first_update_url":"/firmware/firmware_v1.bin","first_update_fingerprint":"98 66 d5 5c 3d 4a 49 24 e3 1b 72 8b 8f 2e 65 2e 32 2a 7b 95"}

[digistump]

After doing a factory restore you'll need to do the config app steps again to change you wifi settings - it does not erase your wifi settings - are you saying that after doing that and going back through the config app and changing your wifi settings they are not changing?

[driffster]

Well that what I was thinking not making much sense I know.. Yesterday I was just not able to connect at all to my wifi.
Now today it just connected on the guest and I just checked, it still connects if I change  the SSID name. Still no luck on the protected network though.

I checked with a laptop and the IP address and wireless network assignment reported by the router is quite lousy and doesn't update between guest and standard, but it does show (with a rather long delay) if a device is online or not. Possibly the Oak does connect on the standard wireless, but shutdowns too fast for my router to report it on. (note my wifi router is integrated in my telephone company modem).

If I can manually assign to the particle account it might work, how would I proceed?

I do see it reboot when using OaksoftAp, From the serial I got out this information:

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

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

[PeterF]

I found that the other day, so can tell you now For the manual claim, it seems to be in an odd spot. When you are at the particle dashboard (https://dashboard.particle.io), you can click on the < / > icon at the bottom left of the screen which takes to you to the build online Particle IDE or just go to https://build.particle.io. You then click on the crosshairs / target icon at the bottom left (second from the bottom). This will let you add a device, and enter your device ID if your oak is connected to your wifi, but didn't register on particle for some reason.

[driffster]

Tried entering the device id in the particle , only got could not claim the device. Tried both while oak is connected in guest mode (seen on my router) and when I try (and probably fail) to connect to the protected wifi.

Just to be certain redid a factory restore.
On protected network got this  error on serial:

Code: [Select]

Exception (28):
epc1=0x402394a6 epc2=0x00000000 epc3=0x00000000 excvaddr=0x0000002c depc=0x00000000

ctx: sys
sp: 3ffffdc0 end: 3fffffb0 offset: 01a0

>>>stack>>>
3fffff60:  4021b003 3ffe9720 00000002 60000600
3fffff70:  402211fd 40221239 3ffe9a5c 4021ad51
3fffff80:  3ffed5b8 40220d99 3fffdab0 00000000
3fffff90:  3fffdcc0 3ffe9f90 00000000 4020f5f5
3fffffa0:  3ffe9f90 40000f49 3fffdab0 40000f49
<<<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
Moved then to the guest wireless, it flawlessly updates, but always stay connected after and can't connect to it until I disable the guest wireless, after that I back at the beginning with the oak not connecting and wont register.
I got this output once I put it back on the normal network:

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,BC,8


[driffster]

I don't have the luxury of having another wifi router to test if it could work, but I used connectify, a software to create another protected access point with my laptop. Unfortunately after a reset I could not get the oak to talk to me or the wifi (no connection and no output on the serial channel).

Again it connects and updates on an unprotected network but does not complete the registration to particle, nor can I register manually through particle..

I am out of ideas on things to test or how to fix it.

Update: I had a new router and retried all the previous steps, I still have the same issue.
I updated all my 10 oaks, one other board as the same exact problem.