I got my new DStream box weeks ago. When I updated its FW with Development Studio v2009.0, the progress stayed at 94% for very long time, and finally the studio complains "Timeout waiting for reboot to complete". (The message at the bottom right corner is "Firmware Installation ...007136: (94%)). The STATUS LED keeps flashing.
I have tried normal update, and FW restoring process. It seems both action stuck at 94%. I used Ethernet to communicate with DStream.
Any suggestions how to fix it?
The firmware install process takes about 5 minutes - I assume you have waited significantly longer than that.
If you power cycle the unit, can you reconnect to the DSTREAM via the firmware update utility - does it report that firmware is updated correctly?
If not, I recommend holding the reset button down for 10+ seconds to put the unit back into factory mode. Is it possible for you to install the firmware via USB?
If you continue to have issues, I recommend raising an official support request:
After I power cycle the unit, it takes very long time for it to boot (The STATUS LED in flashing for very long time), but finally it can get back, and I can connect to it. The new FW version is the updated version. But something muse be wrong as it shouldn't take that long time to boot.
I have tried the factory mode and USB connection. And the issue is still there： Rebooting does not complete until timeout:
I found why. I didn't connect the probe to my DStream. After I connect the probe, the unit boots quickly. Obviously the older version of FW coming with my DStream does not behave like this. It boots fine without the probe. But I would say this new behavior is annoying. FW updating and Dstream configuration should not need the probe at all.
Hi Oscar - thanks for the follow up, glad to hear you found a solution. I tested locally here with my DSTREAM and I see the same behavior. I will discuss this internally.
Is it common for you to detach the probe in this manner?
I think it is common for new DStream initial setup. For real debugging, usually we have the probe connected. It's no longer an issue for me as I already knew it. But I guess people can easily get trapped when doing initial setup without knowing this.
If it is a requirement to connect the probe before updating FW, this should be documented clearly in the document. (Is there any piece of FW stored in the probe that needs to be updated as well??)
The firmware update to the unit did complete successfully. However the latest versions of the firmware now require the header card to be present for it to boot up completely. Cancelling out of the firmware update utility as you did is a suitable workaround.
View all questions in Arm Development Studio forum