Error Occurred while Flashing Device with Digistump Oak

Troubleshooting
21

You have to remember also that println is Oak specific, although I do believe Particle is there in the back end. So the Particle.publish() limits may or may not apply - I suspect they would though.

As far as vagueness of the documentation, it is and it isn’t! :smiley: Basically, you should post one event per second. You are permitted to send more events back to back(up to a maximum of 4), but that is stealing from the future, which is frowned upon, and thus must cool your heels! :open_mouth: So if you post two events back to back, you must wait for two seconds before posting the next if you want it to be accepted. Post three, wait for three. Post four, wait for four. Post five, fifth messages is lost, and you have to wait for four seconds still.

Recent gremlins mentioned on the forum seem to have been resolved (for a couple of people, anyway) with a update to the firmware (now 1.0.5), which tells Particle that it doesn’t need a system update, and lets things carry on normally.

Hey @bjrohan, have you had a chance to see if 1.0.5 will fix your problem (you’ll need to update the board package via the Arduino Board Manager if you haven’t already)? To see if it fixes the problem, basically what you need to do is power on the Oak (you can boot it in config mode if you wish, but it probably doesn’t matter), and then leave it online for 10/15 minutes (or until you see a “spark/status/safe-mode” event in OakTerm/Particle Dashboard Logs) and then try flashing it again.

2 Likes
22

Thank you for the info. I believe I will have a problem in doing so because I can’t flash my Oak. I show that it is connected in the dashboard.particle.io, however when going to the events page nothing reports.

Again, when trying to Flash via arduino, the program uploads to Particle, then I get an error message on the failure to flash.

Every single day since this has occurred, I have unplugged my Oak, let it sit powered off for several minutes and reboot just to see if there are any changes, of which there are none.

On your recommendation, I loaded the Arduino IDE, went to Tools, Board, Boards Manager, searched of Oak, in that section, chose version 1.0.5, and waited for the download to complete. I then put my Oak into config mode and went through the process as if it was a new Oak, including connecting to the Oak wifi, setting the wifi and password, after which it connected to Particle (that’s what the browser window said)

After waiting approx 15 minutes, I logged into my particle dashboard, which showed my Oak connected, but again, no events. I logged into Oakterm, same as before, it showed as offline, however the last_heard timer was up to date, and updating. What did change is I went to my digistump dashboard for the program I have, and it was updating (particle.publish) which lists the output of my photocell. It wasn’t doing this before this update.

I tried to flash the basic LED tutorial, and this time I received an error message that my Oak wasn’t registered or something like it). I ran the Oak tool, selected my Oak, and restarted the IDE. I again tried to flash the LED program, and again received the error message an error occured while flashing device right after it showed the program was uploaded.

Any other suggestions?

23

@bjrohan, You are not alone. I too am seeing OTA upload error on one of my Oaks that may be the same thing you are seeing. This all started when I noticed this OAK was not publishing events to Particle. So I updated to version 1.0.5 and now cannot do OTA updates to this Oak even though it is claimed on Particle. The message is the same as your first post “Error : An error occurred while flashing the device:”. Interestingly I brought up a fresh out of the bag Oak today with no problems. Still trying to figure out what the issue is with the Oak that won’t OTA upload.

There is a thread on the Digistump forums here discussing the ongoing saga.
http://digistump.com/board/index.php?topic=2373.msg11226;topicseen#msg11226 (latest post by me).

I’ve created a custom CLI with debug to try and glean what the error may be. Here is what it reports…

“OakCLI tool version 1.0.2
Using config file at: C:\Users\Stephen\AppData\Roaming\oak\config.json
Sending file to cloud, to flash OAK_GD (Device ID: d9Removed for public consumption)
Get ready to flash C:\Users\Stephen\AppData\Local\Temp\build8316527855105053068.tmpBlinkTestPgm.cpp.bin
null
{ ok: false,
code: 200,
errors:
[ { id: ‘d9d9Removed for public consumption’,
status: ‘Update failed - File was too big!’ } ] }”

I think the error is being reported by a callback from the Particle side.

Like you, I am very anxious to have this understood and resolved.

24

Just so we are clear what follows the debug detailing the error in my previous post is…
“Error : An error occurred while flashing the device:”

25

190+ days and I don’t see any replies, is this fixed?

26

Wow that was back in August 2016. Yes for me the problem was solved by rewriting some sectors on the Oak with balnk bin files using this command…
python esptool.py --baud 115200 --port YOUR_COM_PORT write_flash -fs 32m 0x3FC000 blank.bin 0x3FD000 blank.bin
0x3FE000 blank.bin 0x3FF000 blank.bin

The last sector in the list did not complete but this fixed worked never the less. It was suggested by the creator of the Oak at Digistump.