Hello All
 
My XProtolab used to say v2.0 when I started it so I thought I'd upgrade it to 2.12.
There is nothing on the back to indicate the hardware version, not that I could see.
I installed dfu-programmer on Linux and confirmed that using lsusb I could see the USB bootloader like below.
 
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub/\r\n/Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub/\r\n/Bus 001 Device 006: ID 03eb:2fe4 Atmel Corp. ATxmega32A4U DFU bootloader
 
I assumed that I had hardware later than 1.5 as 1.5 or earlier can't do a USB upgrade.
So I used the hex file in the folder marked 'hardware1.7-1.8'.
~/Documents/hex$ sudo dfu-programmer atxmega32a4u flash xprotolab.hex/\r\n/Bootloader and code overlap./\r\n/Use --suppress-bootloader-mem to ignore
I used this command because I thought that maybe it needed to be overwritten.
 
~/Documents/hex$ sudo dfu-programmer atxmega32a4u flash xprotolab.hex --suppress-bootloader-mem/\r\n/Validating.../\r\n/32466 bytes used (113.23%)/\r\n//\r\n/
 
Well 113.23% is more than 100% and now the red LED won't light up in USB bootloader mode. I now know not to do that again.
Can anyone suggest how I can resurrect my XProtolab and what files I need to do this? I expect I may need access to a programmer and hoping I can get one at work or our hackspace.
 
 
 

Hi! The bootloader should not have been overwritten. Can you try again after restarting? Can you try on a Windows computer? You could send the device back and I can reprogram it.

Hi Gabriel that's a kind offer but I'm in the UK. I've not got a Windows computer at home so will try read the USB again tonight on Linux and tomorrow bring it in to use on my work Windows PC. I'll keep you posted. Leon.

I've tried again and if I hold K1 it does go into the USB bootloader.
I'll try again but should I try a different firmware version if that one gave a message 'bootloader and code overlap'?

The hardware version is marked on the back of the baord, but since you have USB, you should have hardware 1.7 or 1.8. Are you programming the HEX file? If you try to program the ELF file, you might get past the size of the flash memory. The ELF file is used if you have an external programmer.

Hi Gabriel

I used the Flip programmer with the .HEX file and then the .EEP file as in the instructions in the manual.
It's all working with v2.12 now.

I suppose the technique to program on Linux must be different.

Leon.