j3kz Posted November 16, 2017 Share Posted November 16, 2017 I'm not able to update firmware from 1.4.0 to 1.296.0. I'm running Waveforms Live Version 1.3.0 on Safari, Chrome, ... macOS 10.13.1 Am I alone ? Any idea ? Jérôme Link to comment Share on other sites More sharing options...
Kristoff Posted November 16, 2017 Share Posted November 16, 2017 Hey J3kz, What part of the process fails? Is the Digilent Agent running? Are you able to add the Agent connection to WaveForms Live? Are you able to see the COM port for the device in WaveForms Live? Are you able to start the firmware update process? The more details you can provide the better. Let us know and we'll help you get this figured out. Thanks! -Kristoff Link to comment Share on other sites More sharing options...
j3kz Posted November 16, 2017 Author Share Posted November 16, 2017 Yes everything ok, except firmware update process starts but stop saying 'Update failed...' after a while. Link to comment Share on other sites More sharing options...
Kristoff Posted November 16, 2017 Share Posted November 16, 2017 Does the progress bar fill in at all or does it fail before the progress bar updates as all? -Kristoff Link to comment Share on other sites More sharing options...
j3kz Posted November 16, 2017 Author Share Posted November 16, 2017 No the progress bar doesn't fill. Link to comment Share on other sites More sharing options...
Kristoff Posted November 16, 2017 Share Posted November 16, 2017 Can you click the menu button in the upper left, and then click Settings. Expand Advanced and the click Change Console Log and choose Console (if you refresh the page these settings will go back to their defaults). Return to the device manager page (without refreshing the page) and try to update the firmware again. If you open the developer console (Option-Cmd-J in Safari I think) you should see a bunch of commands printed during the update. Wait until you get the error message about the firmware not uploading and then copy and paste the entire console log here. We'll have a look and see if we can figure out what went wrong. -Kristoff Link to comment Share on other sites More sharing options...
j3kz Posted November 16, 2017 Author Share Posted November 16, 2017 I already tried to see something on the console, but nothing is logged ??? Link to comment Share on other sites More sharing options...
Kristoff Posted November 16, 2017 Share Posted November 16, 2017 Just to confirm are you using waveformslive.com (as opposed to an offline build)? Are you able to see the console output in Chrome? You could also try putting the OpenScope in the bootloader before you upload the firmware. To do this press and hold the BTNP button on the open scope while you press and release the BTNR (reset) button. The red light should flash quickly to indicate that the device is in bootloader mode. Try updating running the firmware update from WaveForms Live again. I'd be interested to see the console output in both cases. -Kristoff (I have to run to a meeting shortly, but I'll be back later this morning.) Link to comment Share on other sites More sharing options...
j3kz Posted November 16, 2017 Author Share Posted November 16, 2017 Please find the console log file in attachment... Hope this helps. Jérôme (I have to go too, I will be back later) Firmware update 1.296.0.txt Link to comment Share on other sites More sharing options...
sudharsan.sukumar Posted November 16, 2017 Share Posted November 16, 2017 That's very useful thank you! It looks like the agent is returning an error status when starting the firmware flash. We will look into it and keep you updated. -Dharsan Link to comment Share on other sites More sharing options...
Kristoff Posted November 16, 2017 Share Posted November 16, 2017 Hey, Are you able to get to the instrument panel and acquire data (Click Single, then Force trigger) with firmware version 1.4.0? Were you able to put the device in bootloader mode first and then try updating the firmware? It's possible the firmware is not being downloaded from our server correctly. Can you try downloading the firmware manually from here. Then go through the update firmware process but rather than choosing a version of the firmware from the drop down click Browse and select the hex file from your computer. Let us know how it goes. -Kristoff Link to comment Share on other sites More sharing options...
j3kz Posted November 16, 2017 Author Share Posted November 16, 2017 Quote Are you able to get to the instrument panel and acquire data (Click Single, then Force trigger) with firmware version 1.4.0? Yes Quote Were you able to put the device in bootloader mode first and then try updating the firmware? Yes, I tried at least 2 times... Quote It's possible the firmware is not being downloaded from our server correctly. Can you try downloading the firmware manually from here. Then go through the update firmware process but rather than choosing a version of the firmware from the drop down click Browse and select the hex file from your computer. Yes, it gaves same result too ! Link to comment Share on other sites More sharing options...
Kristoff Posted November 17, 2017 Share Posted November 17, 2017 Hey, What version of the Digilent Agent do you have installed? You can see by right clicking the Agent Icon in the system tray / dock. Do any other firmware versions load correctly? Are you able to try uploading firmware from another computer? Thanks! -Kristoff Link to comment Share on other sites More sharing options...
j3kz Posted November 18, 2017 Author Share Posted November 18, 2017 Hi, I tried with Agent 0.3.6 (https://reference.digilentinc.com/learn/instrumentation/tutorials/openscope-mz/setup) and I also updated it to 1.0.1 (https://reference.digilentinc.com/reference/software/digilent-agent/start). I just succeeded to update the firmware with OpenScope attached to a VirtualBox Win10 with latest windows Agent 1.0.1 (https://reference.digilentinc.com/reference/software/digilent-agent/start) and latest Chrome. You're welcome, Jérôme Link to comment Share on other sites More sharing options...
Kristoff Posted November 20, 2017 Share Posted November 20, 2017 I updated the tutorial in the first link you posted. I'm not surprised 0.3.6 didn't work, but 1.0.1 should. I'm glad to hear that it worked from Win10, but I'm still not sure what the issue is in Mac OS. I've never personally tried on macOS 10.13.1 (only 10.11 and 10.12) so I'll see if I can round up a macOS 10.13.1 machine and test this. -Kristoff Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.