Digistump Forums
The Oak by Digistump => Oak Support => Topic started by: emardee on March 14, 2016, 09:36:30 pm
-
Please only use this thread for Poll answers. Put your questions or problems in their own thread elsewhere. (You can put a link to your problem thread from your Poll answer here if you want, but please keep this thread clean! Thanks)
POLL - Have you managed to install and use firmware v1.0.0 yet?
- Success - It went just fine. = 10 Person & 22 Oaks
- Eventual Success - I got there in the end, but it took some messing around = 19 People & 57 Oaks
- Particle Failure - Firmware installed fine, but having trouble connecting with particle = 7 People & 10 Oaks
- Firmware Failure - I have played around, but still haven't got firmware to install at all = 7 People & 13 Oaks
- Not Tried Yet - I'm waiting for others to test it before I try. = 4 People & 18 Oaks
Total Reports: = 35 People & 120 Oaks
I wanted to gather an overview of people's experiences with v1.0.0 (eg update v6) in one place, so the community (and Erik) can see at a glance how the new firmware is doing overall. I figured this was best done as a POLL, but it seems I can't post one. :(
So I will run it as close to a poll as possible using text! Please only answer the main question in this thread (without pouring out your woes!) so we keep the thread clean for assessing people's success / failure with v1.0.0 (just that version please, NOT experiences with v0.9.x in this thread).
I will then try to update the thread with a tally periodically, so we keep track of the changing status.
If you want to reference your experience in more detail, create a separate thread for it, and then put just a link to that thread to more info under your POLL answer.
If you've tried multiple OAKs please give a tally of each: eg Success = 3 OAKs; Firmware Failure = 2 OAKs; Eventual Success = 4 OAKs; Particle Failure = 1 Oak
If you have a future update to change your reply, post it as a new reply, but mark it as an "update", with your new answer, and I'll remove your old answers from the tally, when I next summarise.
Firmware is now officially released.
Update: I've added a new answer "Particle Failure" for those that have the firmware correctly loaded, but having issues connecting to Particle (either at all, or intermittent problems loading a sketch).
To avoid confusion with this new answer, I've also re-named two previous answers:
I changed the title of "Partial Success" to be now called "Eventual Success", which is a better name for people who got there in the end but had some faff in the process (and avoid confusion for those with Particle Issues instead). Hopefully this makes it clear it this option is only for those with a fully working Oak on Particle.
For the same reason, I've renamed "Failure" to be now called "Firmware Failure".
I've done my best to reallocate the answers into these new categories so that the old fail and partial answers no longer contain the Particle Failures. This should hopefully show clearer the distinction between Success: (Either with or without troubles getting there) and Failure: (Either due to Particle Issues or Firmware failed to load).
Thanks.
-
Not Tried Yet = 10 OAKs
Update:
Success = 7 Oaks
Particle Fail = 0 Oak
Not Tried Yet = 3 Oaks
-
As of 15/03, 5PM local time: 4 - Not Tried Yet.
---
I will probably try to do the update tonight or tomorrow and will update this post with my revised response.
---
After a night off due to a blown up power supply :'(
17/03, Number 1 (of 5), updated via official server after one retry, so 1 Success
17/03, Number 2 (of 5), had issues ('NO CLIENT' or 'SOCKET TIMEOUT') with official server, updated 1st go with jldeon's server (online, not local), so 2 Partial Success
17/03, Number 3 (of 5), had issues ('NO CLIENT' or 'SOCKET TIMEOUT') with official server, updated 1st go with jldeon's server (online, not local), so 2 Partial Success
18/03, Number 4 (of 5), had issues ('NO CLIENT' or 'SOCKET TIMEOUT' and wdt resets) with official server, updated 1st go with jldeon's server (online, not local), so 2 Partial Success
19/03, Number 5 (of 5), had issues ('NO CLIENT' or 'SOCKET TIMEOUT') with official server, updated 1st go with jldeon's server (online, not local), so 2 Partial Success
All five updated Oaks appear on the Particle dashboard, and all work properly when programmed. The forth (which had disconnect/reconnect issues with 0.9.5) no longer plays up.
-
Out of curiosity, can someone explain how this is done? I still see the procedure for 0.9.5 on git. If I just revisit the SoftAP site and re-run the process, will it detect I'm on 0.9.5 and automatically try to re-flash? Or is everyone here talking about something else?
Edit: now I'm thinking this is just setting up for the trials/poll and v1.0 is not actually out...
-
Partial Success - 5 OAKs after several tries
-
Fail 2 Oaks - :'( Can't upload simple Blink sketch OTA Using V1.0.0
get the following error:-
Sending file to cloud, to flash OakDigistump_1 (Device ID: xxxx x x xxxxx x x x x x) (Device ID: OakDigistump_1)
Flashing................
Error : Oak is back online before flash sucessfull.
Seem to have issues with the Oaks disconnecting from particle.
-
I'm getting the same "Error : Oak is back online before flash successfull." error too
Edit: After reconnecting using the SoftAP page i managed to flash a sketch, having problems with connectivity though...
-
I was finally able to get 1 out of 2 Oaks to update.
The one that did update worked on the first "Retry". The other Oak would not update after several attempts.
No idea what was different.
Now to figure out how to program the one that did work!
-
10 oaks: 2 success (first or second try), 6 partial success (usually just repeated process a few more time), 2 failed (updated but still serious connectivity issues that I can't fix).
-
Could someone clarify how this is accomplished? I've got serial programming working via an Arduino, but don't quite follow the firmware flashing. I figured this would be similar to the procedure for OakRestore, but the contents look like an Arduino library. Am I supposed to upload something, or flash over UART?
-
Not Tried Yet = 10 OAKs
-
@jwhendy, can't say for certain... am currently making it up as I go... but... so far it looks like.
On you computer:
- Completely remove the Oak core from your Arduino IDE - in my case with Arduino 1.6.7 (1.6.5 will be AppData\Roaming instead of AppData\Local) - went to "%userprofile%\AppData\Local\Arduino15\packages\digistump\hardware" and deleted the Oak folder.
- To get around a Arduino bug in installing new updates, go to the "%userprofile%\AppData\Local\Arduino15\staging" folder either delete all the files as the IDE will simply download them again if it needs them, or specifically win32-xtensa, esptool2, mkspiffs, oakcli and core-0.9.x
- Install the Oak core again via the Arduino Board Manager - it will now be Version 1.0.0!!!
On your Oak (this is what I have to do now):
- Do an OakRestore, to reset your Oak to factory defaults
- Get your Oak connected to your Wifi again via SoftAP, and let it do a firmware update. If it is stubborn, use jldeon's local server package (https://github.com/digistump/OakCore/issues/54#issuecomment-192752288)
- Hopefully your Oak will now be running system version 6!!
Pete
-
I'll just break this out into another topic (http://digistump.com/board/index.php/topic,2088.0.html), so not to clutter this poll/thread.
-
Whoops... Sorry and good point. I'll move my stuff over there.
-
Now that I understand v1.0.0 is just doing the same SoftAP process described for 0.9.5, I realized I'm 2 successes out of 2.
-
I used the Oak config app (web) not Arduino serial and my results are:
Monday 14:
- Oak 1: first try = success
- Oak 2 and 3 just blinked a few times but no download; tried several times.
Thursday 17 decided to try again: both Oak 2 and 3 worked from first try. Not sure what changed between Monday and Thursday, definitely nothing in my setup, but it worked way better.
So now I'm all set with all 3 Oaks but it took some fiddling with the last 2.
-
@emardee - I'm not sure if I have confused you by editing and updating my earlier post. Hopefully not! I ended up with 1 x Success, and 4 x Partial Success in the end.
-
I used the Oak config app (web) not Arduino serial and my results are:
Monday 14:
- Oak 1: first try = success
- Oak 2 and 3 just blinked a few times but no download; tried several times.
Thursday 17 decided to try again: both Oak 2 and 3 worked from first try. Not sure what changed between Monday and Thursday, definitely nothing in my setup, but it worked way better.
So now I'm all set with all 3 Oaks but it took some fiddling with the last 2.
This is good to hear, and worth noting for those that tried before Thursday - Thursday I updated some settings on the servers to further improve update reliability
-
1 Oak = 1 failure.
I manage to configure the Oak and connect it to my LAN.
But every-time I upload a sketch from the Arduino IDE using Particle OTA, the board never reboots.
Sending file to cloud, to flash myOak (Device ID: xxxxxxxxxxxxxxxxxxxxxxxx) (Device ID: Oak)
Flashing..........................
Rebooting Oak...
Error : Reboot timeout - flash likely failed.
Subsequent tries fail.
Sending file to cloud, to flash myOak (Device ID: d957040101dadd31c5168980)
Flashing...
Error : Flash timeout - flash failed.
Going through Oak WiFi Config (http://rawgit.com/digistump/OakSoftAP/master/config.html) again doesn't help. The only solution so far is to perform a factory reset (http://github.com/digistump/OakRestore) and start again the whole procedure.
-
Got me 3 Oaks.
On 2 the installation went well.
On 1 it took LOT of tries to connect to it and finally when connected it took three attempts to install 1.0.0 and a few more to claim it with Particle.
After that it was doing the quick-triple-flash thingy and I managed to flash it a few times with some example code. But it's still the black sheep: it cannot connect to Particle anymore and I can't flash it either :(
Update 26 Mar: today I performed a factory restore (using an Arduino in stead of an FTDI breakout board) without any issues. Afterwards the same behaviour returned:
- it takes many attempts to connect to the Oak's AP, even though the signal is plenty strong
- one connected the LED blinks quickly, indicating new firmware is downloaded
- Oak reboots
- Error in the Oak Wifi Config page that it cannot establish a connection with the oak
- retried with the slow update server - same result
From then on the Oak still behaves as an access point but does not allow me to connect to it anymore (using Linux, KDE, Networkmanager app)
Update 2, 26 Mar: Performed the local update (http://digistump.com/wiki/oak/tutorials/local_update) (with a Samsung alaxy Tab 2, FWIW) and succeeded at the first try :)
Result:
2 success
1 eventual success
-
i have managed to update the firmware, but have been unable to upload code,says the device is not available on my account.
-
Fail here
2016-03-20 11:44:25 New connection from: 10.0.0.223
2016-03-20 11:44:25 Starting firmware transfer to: 10.0.0.223
2016-03-20 11:45:18 Connection lost to: 10.0.0.223
2016-03-20 11:45:18 Firmware request finished for 10.0.0.223 (Reason: [Failure instance: Traceback: <class 'OpenSSL.SSL.Error'>: [('SSL routines', 'ssl3_read_bytes', 'sslv3 alert bad record mac')]
site-packages\twisted\internet\selectreactor.py:149:_doReadOrWrite
site-packages\twisted\internet\tcp.py:209:doRead
site-packages\twisted\internet\tcp.py:215:_dataReceived
site-packages\twisted\protocols\tls.py:422:dataReceived
--- <exception caught here> ---
site-packages\twisted\protocols\tls.py:360:_flushReceiveBIO
site-packages\OpenSSL\SSL.py:1320:recv
site-packages\OpenSSL\SSL.py:1187:_raise_ssl_error
site-packages\OpenSSL\_util.py:48:exception_from_error_queue
])
2016-03-20 11:45:18 Early termination to: 10.0.0.223 (530432 bytes written, fail count = 1)
2016-03-20 11:45:18 Finishing firmware transfer to: 10.0.0.223 (1 transfers done)
-
1 Oak : Success!
I had a lot of problems trying to do it on my work laptop, but I think IT has something blocked. I tried it on my home computer and it worked first time. Whoopee!
-
Partial Success.
I got my oak online, but both the main update server and the backup/slower server did not work. I used the local update server and that worked the first time.
I had no problems getting the device connected to my network (though my first connection to the softAp took a long time to go through), or my particle account.
The first sketch upload from the Arduino IDE threw the "Oak is back online before flash sucessful." error. I read through this post and a couple other threads and didn't see an obvious solution or explanation, so I just tried it again twice and it worked both times. I'll chalk it up to cosmic rays.
A couple bumps in the road, but nothing too serious.
-
Partial something...
I have two Oak's and updating the firmware went without a problem, i am just unable to upload any code to them
-
1 Oak = FAILURE after Hours of attempts and following forums, multiple Wi-Fi networks. Will see other networks will never connect to them
-
Note the changed permissible answers for added clarity!
POLL - Have you managed to install and use firmware v1.0.0 yet?
- Success - It went just fine. = 6 Person & 11 Oaks
- Eventual Success - I got there in the end, but it took some messing around = 3 People & 15 Oaks
- Particle Failure - Firmware installed fine, but having trouble connecting with particle = 8 People & 11 Oaks
- Firmware Failure - I have played around, but still haven't got firmware to install at all = 4 People & 4 Oaks
- Not Tried Yet - I'm waiting for others to test it before I try. = 2 People & 20 Oaks
Total Reports to date (including up to mfelling above): = 18 People & 61 Oaks
Update:
I've added a new answer option "Particle Failure" for those that have the firmware correctly loaded, but having issues connecting to Particle (either at all, or intermittent problems loading a sketch).
To avoid confusion with this new answer, I've also re-named two previous answers:
I changed the title of "Partial Success" to be now called "Eventual Success", which is a better name for people who got there in the end but had some faff in the process (and avoid confusion for those with Particle Issues instead). Hopefully this makes it clear it this option is only for those with a fully working Oak on Particle.
For the same reason, I've renamed "Failure" to be now called "Firmware Failure".
I've done my best to reallocate the answers into these new categories so that the old fail and partial answers no longer contain the Particle Failures. This should hopefully show clearer the distinction between Success: (Either with or without troubles getting there) and Failure: (Either due to Particle Issues or Firmware failed to load).
Thanks.
-
Total failure and regret of doing the FORCED update 😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡
-
Firmware Failure = 5 Oaks
:(
does anyone know if its possible to flash the oaks into a "normal" esp8266 ?
-
Firmware Failure = 5 Oaks
:(
does anyone know if its possible to flash the oaks into a "normal" esp8266 ?
+1
-
Eventual success: 2 Oak
Particle Failure: 1 Oak
Third Oak, status unknown. I've tried it previously, and I think it might be bricked (need serial programming), because last time I powered it up, I got no blinking LED and no Soft AP. But I'm going to give it another try after I work on number 2 some more.
UPDATE: I was able to claim Oak #2 by going to my Particle dashboard, viewing devices, clicking "Add a device", and entering the Device ID (the one reported in the 'id' field when you visit the '/info' url on your OAK device).
-
Serial Firmware Update: 1 Oak
OTA Firmware Update: 0 Oak
Particle Failure: 1 Oak
-
Firmware Failure = 2 OAKs
-
After spending 1/2 day trying to use multiple (fast/slow svr) online updates and trying different router settings & various tips found in this forum, I could not get the initial update to work. Finally I tried the local update server (http://digistump.com/wiki/oak/tutorials/local_update). Using that, all four of my Oaks updated first time with no problems. This is with my router set to it's normal settings. Interesting that using the same router (& settings), power supply and proximity of the oak to the router, the local server update works fine, but the online update server does not.
Following that I used the Arduino method (& OakCLI tool) of loading a first sketch to all four Oaks successfully.
Poll:
Online Update Fail: 4 Oaks
Local Svr Update Success: 4 Oaks
Particle Failure: 0 Oaks (all 4 worked fine)
Note regarding the Windows version of the local update server - I have Windows 10 and the tool fails with a certificate failure (running as administrator). I don't know how to get around that, so I used the linux version which worked fine.
-
Poll:
Beta Board During Beta success: 1 ( particle reg and IDE program )
Online Update Fail: 6 Oaks
Local Svr Update Success: 7 Oaks ( redid the BETA too! )
Particle Failure: 0 Oaks (all 7 worked fine)
IDE 1.6.8 : Programming success (After Local Update ) : 7 Oaks
My Success with http://digistump.com/wiki/oak/tutorials/local_update#local_update_tool (http://digistump.com/wiki/oak/tutorials/local_update#local_update_tool) [using Windows10 and Android Phone]:
http://digistump.com/board/index.php/topic,2103.msg9700.html#msg9700 (http://digistump.com/board/index.php/topic,2103.msg9700.html#msg9700)
-
Eventual Success:
I had 1 work fine during the beta with the serial pushed firmware 0.9.5.
The other 4 I've had to run the local update server because I couldn't get them to update from the oakota server on 4 different internet connections, all different internet provider services. Every other Oak backer I've spoken to in Australia is having the same issue, so I suspect it's an internet related issue.
-
Managed to finally get my 2 oaks working, took a massive amount of trial and error.
Windows 10 laptop still won't connect directly to the oak AP, but tried that on both.
My phone would connect but failed to get things going, had to try that on both oaks.
I dug out an old android tablet that eventually got things started, but both devices failed to update on my main network. Tried that several times, then tried the slow server, then tried messing with my router.
Next I tried the manual server option, but that failed on my windows 10 laptop, so I dug an old laptop out of storage and managed to get it running enough to see that both oaks could get 3 maybe 4 of the update transfers before failing.
Then dug an old router out of storage, messed with the settings, use a lam cable to the laptop. This seemed like it was trying to work but still failed, on both oaks.
Finally as a hail-mary attemp I tried going back to the original digistump server, failed once, and worked on the second try.
All that was probably 6 hours of time, wasted in 180 second chunks between tries.
Now what???
-
Suggestion: could the poll instructions be updated to more explicitly tell users to start separate threads for their update issues? There are a lot of detailed accounts of the update attempts coming in here, and I fear they'll just be lost since this isn't what this thread is for. This thread has a lot of activity and thus it will probably keep getting attention from new users wanting to get help.
I could also see a thread specifically for update issues, but that could get complicated. I was going to suggest at least asking users to list out specifically which step during the first connect (http://digistump.com/wiki/oak/tutorials/connecting) fails, as the descriptions I see are ambiguous. For example, "My phone would connect but failed to get things going..." Then I re-read the original post and see users are already advised to start new threads.
-
Starting with 5 Oaks:
1x Oak - Eventual Success (Had to reset because of Beta FW and new update had trouble twice before final success)
1x Oak - Success (worked perfectly the first time)
3x Oaks - Not tried yet (haven't needed to use them yet)
-
10 Oaks from the Kickstarter campaign. Waited patiently for the V1 firmware release before I powered anything up.
6 have been successfully updated OTA after much pain... ended up using my cell phone WiFi hotspot functionality to bypass my home router.
Even then all of them took 3 attempts, some of them as much as 6 attempts.
2 not tried yet.
2 I think are bricked after unsuccessfully trying serial UART update. I will come back to them later.
-
Eventual Success - Oak
-
I have two Oaks and both registered OK with Particle.
Both failed the OTA firmware update so I moved on to the local server update. Both failed this as well.
I have a 3.3V serial adapter and used this on both successfully.
Post update, I find that flashing new software is very hit and miss OTA but 100% successful over serial so I'm sticking with that for now.
FYI - my development is a Mac with the latest OS installed and fully patched.
Regards,
Mark
-
Eventual success with 3 oaks registered and able to upload simple code to.
-
4 oak = success (finally!, spent all today on it)
-
2 oaks, success on first upload for both.
-
1x Oak - "Eventual success"
It took a while, but I got there in the end. Using the local updater (http://digistump.com/wiki/oak/tutorials/local_update), this guide (http://digistump.com/board/index.php/topic,2046.0.html) and lots of fiddling w/ routers and devices I managed to flash the v1 firmware.
The standard update failed probably a half-dozen times, and so did the local version of the update script. I have multiple WiFi routers, one of which I reconfigured to a channel other than 1. Then I moved stuff around, trying to give the Oak as good a signal as possible while keeping all other WiFi devices as far away as I could. Not sure what did the trick, but eventually it worked.
Oddly, the setup page was still counting down when the Oak rebooted after the successful flash. Upon reboot, it connected to the WiFi as configured and also registered itself with Particle.io. I never saw the "Your Oak updated successfully" screen, But I'd run enough prior attempts to know that the LED triple-blink was new. I scanned my local network and found the Oak at the same IP reported in the oakupsrv logs, checked http://<oak_ip>/system-version and did a fist pump when I saw the response (6 instead of File not found). Then I went to the Particle dashboard (https://dashboard.particle.io/) and the Oak was listed as a new device.
This is what the LED looks like after successful configuration (https://www.youtube.com/watch?v=ETodpf6kgM8)
I wasn't quite sure how to know the difference between "slow" and "faster" until I saw it.
-
Eventual Success
hooked to Raspberry Pi...ran the manual updater Python.
Windows Surface to push the update.
Seems like I got it.
-
Long time passed playing with my OAK's before posting here those days, not easy in fact...
Upgrade to latest firmware was successful at office with 2 units, failed with one that I cannot recover. I still need to try serial...
On the 2 successful units, I was able to upload my sketch. Back to home, nothing worked anymore, upload was always failed but oak was connected to wi-fi and particle. Then, regarding the number of messages related to wifi quality, I switched from my classical home network (Same as office, Ubiquity Access Points) to one old Linksys that I put in 11b mode only with a max TX rate of 2 Mbps. Then suddenly all was back again and working !
Thanks for that to the boot with Pin1 connected to ground to force OAK to enter SoftAP mode.
Now I have to understand why I read from port P6 and P5 does not work the same manner... :-(
In conclusion, try to one old and very crappy WIFI, set it to the lowest possible speed to play with your oak, at least for me this is the working solution I found.
-
Eventual success - about 5 retries before it took. One Oak, four to go ...
-
Eventual success. Tried 10+ times the "standard" way, then moved to creating my own server / client with 2 computers, worked on the 3rd try. Using Ubuntu 14.01 FWIW.
-
1 Success
4 Eventual Success
3 Particle Failure
Eventually claimed the 3 manually on Particle. Everything was a huge hassle trying to run on Windows 10 and ended up using an iPad and/or WiFi Hotspot on my phone. Eventually fixed it all on Ubuntu 14.04 and they all seem to be working at this point. Need to try putting code on all of them using Arduino and should be good to go.
-
Eventual Success = 1 Oak
Not Tried Yet = 9 Oaks
-
Success = 3 Oaks