Might of Bricked Unit Attempting Update using dfu (Linux) programmer

More
12 years 6 months ago - 12 years 6 months ago #741 by jdinsmore
I might of bricked my Xprotolab Portable while attempting to update its firmware. I do not have a Windows machine (I use Ubuntu Linux 13.10), so I tried using dfu programmer instead. Here are the steps I used:
Open terminal, navigate to directory containing hex files:
~$ dfu-programmer atxmega32a4u erase
~$ dfu-programmer atxmega32a4u flash xprotolab-p.hex
~$ dfu-programmer atxmega32a4u start
~$ dfu-programmer atxmega32a4u flash-eeprom xprotolab-p.eep
~$ dfu-programmer atxmega32a4u start
On the 'flash-eeprom' command I got the error message "Error while programming eeprom."
?
Now the unit will not turn on, nor wil it come up in boot mode.
?
Another note, my Xprotolab was not recognized until I loaded the same rules file that i needed to do on another computer for Mojo FPGA developement and firmware update, here is a link to that operation (and the rules file is attached)? embeddedmicro.com/tutorials/mojo/updating-the-mojo
What can I do to resussitate my scope!?
?
James
Last edit: 12 years 6 months ago by ganzziani.

Please Log in or Create an account to join the conversation.

More
12 years 6 months ago #742 by jdinsmore
I also got this error message when I flashed the xprotolab-p.hex file, /\r\n/"Bootloader and code overlap. Use --suppress-bootloader-mem to ignore"./\r\n/The unit will come up in boot mode when it is plugged into the computer.

Please Log in or Create an account to join the conversation.

More
12 years 6 months ago #743 by jdinsmore
I changed the line where I load the xprotolab.hex to:/\r\n/~$ dfu-programmer atxmega32a4u flash xprotolab-p.hex --suppress-bootloader-mem/\r\n/and I can see that loading OK, I still get an error message when trying to load the eeprom using/\r\n/~$ dfu-programmer atxmega32a4u flash-eeprom xprotolab-p.eep/\r\n//\r\n/"Error while programming eeprom."/\r\n//\r\n/James

Please Log in or Create an account to join the conversation.

More
12 years 6 months ago - 12 years 6 months ago #744 by ganzziani
I don't think the Xprotolab Portable is bricked, but if updating the firmware had errors, you might need to reset the micro. You will need to open the device and short pins 5 and 6 on the PDI connector (behind the display).
I'm not familiar with updating the firmware in Linux, but if you are still unsuccessful, you can simply skip the EEPROM step. When you turn on the unit, go to the factory settings (keep pressing the MENU button during the splash screen), then press RESTORE,
This will set the correct settings on the EEPROM.
The only drawback of not programming the EEPROM during the firmware update is that the custom AWG wave will not be present.
Last edit: 12 years 6 months ago by ganzziani.

Please Log in or Create an account to join the conversation.

Time to create page: 0.153 seconds
Powered by Kunena Forum