-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oak Update Debug Logs #47
Comments
r�l�Ørß�#�ânÀ��à���ì�p�<��ßì8���Ç��ä��pònnä��;òn��Üäbç$�r�r�pònàÃÜ�à�ÇÀl������bÀ�nâãnÀä��ì��bÀľ~ònî�ÄÁ��l`��Ü#�nÀ��r��nr��ß;�ÄÀ?�Ç;��pònàÃÜ�àr��â����pp��<��Çl�ÄbÀÄ> load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM wdt reset OakBoot v1 - H,BU,0 r�l��rß�#�ânÀ��à���ì�p�<��ßì8��ßÇ�Üä��pònnä�Ä;ònÄ�Üäbà$ r�r�pònàÃÜ�à��Àl������bÀ�nâãnÀä��ì��bÀľ~ònî�ÄÁ��l`��Ü#�nÀ�r��nr��ß;��À?�Ç;��pònàÃÜ�àr��â����pp��<�ÄÇl��b�Ä> load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM ets Jan 8 2013,rst cause:2, boot mode:(3,0) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BU,0 r�l�Ørß�#�ânÀ��à���ì�p�|��ßì8��ßÇ�Üä��pònnä�Ä;ònÄ�Üäbç$ r�r�pònàÃÜ�à��Àl������b��nâãnÀä�ì��bÀÄ>~ònî�ÄÁ��l`��Ü#�nÀ��r��nr��ß;��À���;�pònàÃÜ��àrÇ�âÜ���pp�Ü<��Çl�ÄbÀÄ> load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BU,0 r�l��r��c�ân���à���ì�p�<���ìx���Ç�Üä��pònnä�Ä;ònÄ�Üäb�#l load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM ets Jan 8 2013,rst cause:2, boot mode:(3,7) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BU,0 r�l��r��#�ân��à���ì�p�|��ßìx���Ç��ä��pònnä��;òn��Üäbà$�r�r�pònàÃÜ�à�ÇÀl������b��nâãnÀä�ì��b�Ä>~ònî�ÄÁ��l`��Ü#�nÀ��r��nr��ß;�ÄÀ��Ç;��pònà�Ü�àr��â����pp�Ü<��Çl�ÄbÀÄ> load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM ets Jan 8 2013,rst cause:2, boot mode:(3,0) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BU,0 r�l��r��#�ânÀ��à���ì�p�<��ßì8��ßÇ�Üä��pònnä��;ònÄ��äbç$ r�r�pònàÃÜ��à�ÇÀl������bÀ�nâãnÀä�ì��b�Ä> load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BU,0 r�l�Ørß�#�ânÀ��à���ì�p�<��ßì8��ßÇ�Üä��pònnä�Ä;ònÄ�Üäb�#l load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM wdt reset OakBoot v1 - H,BU,0 r�l��rß�#�ânÀ��à���ì�p�<��ßì8��ßÇ�Üä��pònnä�Ä;ònÄ��äb�bl load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM ets Jan 8 2013,rst cause:2, boot mode:(3,3) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BU,0 r�l�Ør��#�ânÀ��à���ì�p�|��ßì8��ßÇ�Üä��pònnä�Ä;ònÄ�Üäb�bl load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM wdt reset OakBoot v1 - H,BU,0 r�l�Ørß�#�ânÀ��à���ì�p�<��ßìx��ßÇ�Üä��pònnä��;ònÄ�Üäb�cl load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM wdt reset OakBoot v1 - H,BU,0 |
Thank you - I was able to duplicate this and I'm working on it now |
@ancientmidi If 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 |
Not noticing a difference but I'm going to re-clone OakRestore to make sure I didn't use the wrong oakupdate_restore.bin |
Will confirm with another in a bit. ets Jan 8 2013,rst cause:2, boot mode:(3,1) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM wdt reset OakBoot v1 - H,BU,0 r�l�Ørß�#�ânÀ��à���ì�p�<���ìx���Ç��ä��pònnä�Ä;ònÄ�Üäb�#l load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM ets Jan 8 2013,rst cause:2, boot mode:(3,7) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BU,0 r�l��r��c�ânÀ��à���ì�p�<��ßì8��ßÇ�Üä��pònnä�Ä;ònÄ�Üäbà$ r�r�pònà�Ü�à�ÇÀl������bÀ�nâãnÀä��ì��bÀÄ> load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM ets Jan 8 2013,rst cause:2, boot mode:(3,0) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,8 |
Sorry if that didn't sound like good news -- let me rephrase. The one I called "problem_child" activated after a few tries. :) |
Second Oak, not so good. ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM wdt reset OakBoot v1 - H,BU,0 r�l�Ør��#�ânÀ��à���ì�p�<��ßìx���Ç��ä��pònnä�Ä;òn��Üäb�cl load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM ets Jan 8 2013,rst cause:2, boot mode:(3,7) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BU,0 r�l�Ørß�c�ânÀ��à���ì�p�|��ßì8��ßÇ�Üä��pònnä��;òn���äb�#l load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM wdt reset OakBoot v1 - H,BU,0 r�l�Ørß�#�ânÀ��à���ì�p�|���ì8��ßÇ�Üä��pònnä�Ä;ònÄ�Üäbç$�r�r�pònàÃÜ�à�ÇÀl������bÀ�nâãnÀä��ì��b�Ä>~ònî�ÄÁ��l`��Ü#�nÀ��r��nr���;�ÄÀ?�Ç;��pònà�Ü�àrÇ�â����pp�Ü<�ÄÇl�Äb�Ä> load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM wdt reset OakBoot v1 - H,BU,0 r�l��r��c�ân��à���ì�p�|��ßì8��ßÇ�Üä��pònnä�Ä;ònÄ��äb�#l load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM wdt reset OakBoot v1 - H,BU,0 r�l�Ørß�#�ânÀ��à���ì�p�|���ìx���Ç��ä��pònnä�Ä;ònÄ�Üäbç$�r�r�pònàÃÜ��à�ÇÀl������bÀ�nâãnÀä�ì��bÀľ load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM wdt reset OakBoot v1 - H,BU,0 r�l�Ør��c�ân���à���ì�p�<��ßì8��ßÇ�Üä��pònnä��;òn���äb�cl load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM wdt reset OakBoot v1 - H,BU,0 r�l�Ørß�#�ânÀ��à���ì�p�|���ì8��ßÇ�Üä��pònnä�Ä;òn��Üäb�cl load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM wdt reset OakBoot v1 - H,BU,0 r�l�Ørß�#�ânÀ��à���ì�p�|��ßì8��ßÇ�Üä��pònnä�Ä;ònÄ�Üäb�cl load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM wdt reset OakBoot v1 - H,BU,0 r�l�Ørß�#�ân���à���ì�p�<��ßì8��ßÇ�Üä��pònnä�Ä;òn��Üäb�#l load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM wdt reset OakBoot v1 - H,BU,0 ���� |
Using the same Oak I've had fail 20+ times. I used OakRestore to restore it (took me a while to figure out...notes below) OakRestore Notes
TTL Cable: Adafruit USB to TTL Serial Cable Router: Asus RT-N66U
Another couple of tries later... TTL TX <-> Oak PIN3/RX Plug in serial cable Open command prompt to OakRestore directory Unplug Oak Launch SoftAP Config App and enter Particle credentials Connected to ACORN-XXXXXX WiFi network Selected WiFi network and entered passcode (Forgot to launch serial for debug...dangit!) Rapid LED flashes ~3 minutes later, ACORN-XXXXXX network is now visible Launching serial console Clicked "Next" on SoftAP Config App to check the update status Power cycling Oak Connecting to primary WiFi network Connected to ACORN AP WiFi details 1 LED flash per sec "UPDATE FAILED" Debug output:
Several more attempts and I still cannot get past the "SOCKET READ TIMEOUT" error. I've tried limiting bandwidth to the device and that did not help any. |
As with Dale, I was tricked by there not being a mention of a 'you can remove the P2 -> GND link after the restore firmware has been successfully downloaded'... unsurprisingly, not much happened until I did... lol Attempt 1: Power cycle after OakRestore
Attempt 2: Didn't bother power cycling manually, looks like SoftAP triggered a reboot itself
Attempt 3: Power cycle, complete log from powerup, retry update in SoftAP, to fail.
|
So I see a lot of "SOCKET READ TIMEOUT". Would it be feasible to handle this with a restart of the download, or even a restart at the bytecount it has downloaded, instead of rebooting? This way, if someone have a very crappy internet connection, eventually, it will have downloaded the whole file. Instead of downloading the start 20 of the image 50 times. Maybe it increases the size of the bootloader too much? But it should not really, if this is infact HTTP requests, you could just add a Byte-range: header? Just my two cents |
@digistump Is having access to more off-site Oaks of any benefit to you? If you are able to access other Oaks by having their deviceID, I am more than happy to leave the two Oaks that are talking to Particle online as remote programmable targets. At the moment they are simply running - there is nothing connected to them. They just publish a "loop()" event every 20 seconds (and blink their LEDs) to show they're still alive and kicking. btw, I don't know if this is directly related, but downloading new sketches seems to be having more trouble than it was the other day. Both Oaks have taken just over 5 minutes from the initial download starting event to it being successful. And I think in one case it automatically restarted the download. |
Dear Erik get the same error ... ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM FILE LENGTH: 778096 START WRITING UPDATE - NO OUTPUT SHOULD BE EXPECTED FOR UP TO 120 SECONDS ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BU,0 ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BP,2 START UPDATE ROM FILE LENGTH: 778096 START WRITING UPDATE - NO OUTPUT SHOULD BE EXPECTED FOR UP TO 120 SECONDS ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x40100000, len 3632, room 16 OakBoot v1 - N,BU,0 |
eth_trace.zip |
I was able to get my problem-child Oak to update using the latest beta and my iPhone in hotspot mode. |
Any updates?? How about giving us another oakupdate_restore.bin that will give slightly more meaningful debug information instead of just socket timeout? |
Still no dice trying to update my "problem Oak" from restore to 0.9.5: Router: Asus RT-N66U Attempt 1: failed with "SOCKET READ TIMEOUT"
Attempt 2: power cycled, failed with "SOCKET READ TIMEOUT"
Attempt 3: did NOT power cycle, failed with unknown error
Attempt 4: power cycled, failed with unknown error
Attempt 5: removed LeGioN Meter, power cycled, failed with unknown error
Attempt 6: power cycled, factory restored, power cycled, failed with "SOCKET READ TIMEOUT"
Attempt 8: did NOT power cycle, failed with unknown error
|
Please find the trace of my failed attempts.
If the file is really 778096-byte long, it is too big to download, even at 15 Mbps. The update through the FTDI cable is a safer solution. Anyway, this is an end-less game. Thank you for your help. |
Hey @rei-vilo - what you you mean by "too big to download, even at 15Mbps" - by my calculations, at 15Mbps, it would take less than half a second to download 778096 bytes! The bottleneck is how fast the ESP8266 can clear and write the saved data. And if you are trying to get an Oak to update so you can use it, trying retrying another 2-3 times (with power cycles) on your LAN-1, as it seemed to be the only one of the two downloading anything. And remember that you do have to connect the oaks ACORN-XXXXX AP again, and hit retry in the SoftAP config webapp, for it to actually retry the download - it doesn't retry automatically or anything. |
I've already tried 6 times with power cycles, to no avail. |
Leading garbage (wrong serial speed ?) removed
|
My short story: So i soldered the headers to the boards, upgraded on oak1 the firmware via Uart Adapter and afterwards (connected to my pc again, like the previous tries), the firmware download worked like a charm... Connected the second one to the pc again, tried it without firmware upgrade, and that also worked like a charm... well i guess i've found the perfect wifi spot... connected the third one. Didn't work. Upgraded the firmware. Tried it again multiple times(x), always failing. So i will flash the firmware via Uart Adapter to my last Oak now. I hope the normal connection when using them is more stable. :)
(x) multiple times = ~5 to ~10 |
The biggest problem is the Oak isn't reliable. I've given up. |
@rei-vilo wouldn't say so - the only difficulty (and a frustrating start) is to update the firmware to v1. After flashing the last one with my Uart adapter, they work fine... even installing my scripts over the cloud via Arduino IDE -> Particle.io -> My Oak But yeah... without an Uart adapter... i guess it would have been impossible :( |
Closing given the many ways to troubleshoot this now and logs not revealing anything new at this point: |
Please paste you Oak update debug logs here - or email them to [email protected] if you do not have a github account to comment here.
Reference: https://github.com/digistump/OakRestore
The text was updated successfully, but these errors were encountered: