I Bricked my Lattice programmer

[xuio]

Hi,

while trying to programm an MACHXO2-256HC, the diamond programmer software did not correctly recognize my FPGA. (screenshot attached)
I thought there was a problem with the JTAG-ID and tried to fix that by erasing the complete flash of the FPGA, but quickly recognized that i had just erased the flash of the programmers internal FPGA 

It would be really nice if someone, who has a similar programmer (HW-USBN-2B), could dump the firmware (Diamond Programmer -> Firmware tab -> Save exsisting Firmware) and send it to me, so I can un-brick my device.

Thank you for your help! 

Moritz

EDIT: the firmware files are now available at: http://www.latticesemi.com/cables

[JoeN]

This is the Lattice cable and not a clone right?  It's business hours right now, why not ask Lattice themselves?  techsupport@latticesemi.com  Also, are you sure there is no feature in the programming software to update the firmware?  I've had several cables I own update themselves when I start them from time to time to support new devices (Atmel Studio does this) because the manufacturer supplies new firmware from time to time to solve bugs and support new devices.

[xuio]

Yes this is an original cable. I have already submitted a ticket to the Lattice support system last thursday, but I haven't got an answer yet.

The Diamond Programmer software displays "WARNING - A new firmware version for this cable is available. Please visit the Lattice website and download and install the latest cable firmware.", but I couldn't find any firmware download on their website at all.

The software has a firmware tab for updating the cable, but you have to point it to a .jed file, no auto-update.

Moritz

[xuio]

Got a reply from Lattice today:

Code: [Select]

Thank you for contacting Lattice Technical Support.
We have received your request and your email address is considered a public domain email address.
Your request is kept on hold in the Lattice Technical Support System and will be deleted in next 24 hours.
Thank you very much 

So I guess I'll have to buy another programmer.

If someone runs into the same problem, feel free to contact me and I'll send you the (proably outdated) firmware file.

Moritz

[JoeN]

Got a reply from Lattice today:

Code: [Select]

Thank you for contacting Lattice Technical Support.
We have received your request and your email address is considered a public domain email address.
Your request is kept on hold in the Lattice Technical Support System and will be deleted in next 24 hours.
Thank you very much 

So I guess I'll have to buy another programmer.

If someone runs into the same problem, feel free to contact me and I'll send you the (proably outdated) firmware file.

Moritz

If you can get the old programmer up and running again at least you have a backup, or maybe you can sell it on eBay.  Sorry this didn't work out so well for you.  I would call them on the phone and raise hell, but that's me.

[xuio]

Update:
I was contacted by someone from Lattice this morning - they offered me a free replacement for my programmer, or to send me the firmware so i can un-brick my device.

Sadly, I already had ordered a second programmer, which arrived on monday and I was able to get my programmer up and running. So the money is gone anyway.

They should really put some donwload links on their website, or implement something inside the programmer software.
I was contacted yesterday by someone who ran into the same problem, so I think i'm not the first one with this problem.

Moritz

[JoeN]

Update:
I was contacted by someone from Lattice this morning - they offered me a free replacement for my programmer, or to send me the firmware so i can un-brick my device.

Sadly, I already had ordered a second programmer, which arrived on monday and I was able to get my programmer up and running. So the money is gone anyway.

They should really put some donwload links on their website, or implement something inside the programmer software.
I was contacted yesterday by someone who ran into the same problem, so I think i'm not the first one with this problem.

Moritz

Well, unless you are contractually obligated not to do so, at least you can help the other guy out and get +1 Karma or whatever...

[xuio]

Well, unless you are contractually obligated not to do so, at least you can help the other guy out and get +1 Karma or whatever...

Yes, I already have he got his device up and running again.

Moritz

[xuio]

Hi,

Nice that you have already found the firmware. If you are sucessful with your clone programmer, please post it in the forum.
If it doesn't work, I have a spare programmer, which I can offer you at a cheaper price, if you are interested.
Is there only an eeprom in the programmer? I thought this was only the case with the integrated programmers.

Moritz

[mikeselectricstuff]

FWIW I just got one of these Chinese clone Lattice programmers

http://www.ebay.co.uk/itm/251686578853

Works well - actually better than the original Lattice one I had, which had nasty captive leads and usually needed bodge caps on TCK to work reliably.
 
BTW last time I compared it, Lattice's standalone ISPVM software was about twice as fast than Diamond programmer - Diamond seems to sit doing nothing for a few secs before programming, which gets really annoying during development.

[ts-mp]

This is the Lattice cable and not a clone right?  It's business hours right now, why not ask Lattice themselves?  techsupport@latticesemi.com  Also, are you sure there is no feature in the programming software to update the firmware?  I've had several cables I own update themselves when I start them from time to time to support new devices (Atmel Studio does this) because the manufacturer supplies new firmware from time to time to solve bugs and support new devices.

On the note of emailing lattice support, I'm having the same problem as the OP, but I emailed them.  This is what came back.

My frustration level right now is indescribable.

[ts-mp]

The information in this thread implies I might be able to de-lobotomize my programmer myself, but I'm having a hard time sorting the details on how this is done.  I have the firmware, but am not certain how to program the device with it while the device is bricked... I'm probably just being dense.  If anyone can spell it out for me I'd appreciate it.

[ts-mp]

Thanks for that.  I'd actually already obtained the programmer from FTDI and flashed the new XML, that part seems to work fine, but when I get into the Diamond Programmer, I just keep getting the latter part of this:
<paste start>
WARNING - A new firmware version for this cable is available. Please visit the Lattice website and download and install the latest cable firmware.
Lattice VM Drivers detected (HW-DLN-3C (Parallel), HW-USBN-2B (FTDI))
Programmer device database loaded
INFO - Scanning USB2 Port FTUSB-0...
ERROR - Scan Failed - Creating Blank Programmer Project.
ERROR - Failed to Open FTDI USB port. Make sure to select the right cable type.
If you have not installed the FTDI Windows USB Driver, follow the instructions in the Programmer Help topic:
"Installing/Uninstalling Parallel Port Driver and USB Driver".
If you have installed the driver, if you recently plugged in the cable, please wait a few seconds and try again.
This will give the operating system time to recognize the cable.
<paste end>

... with that last bit about failing to open the port repeating for every action I attempt.  It feels like a driver problem, but the FTDI utility doesn't seem to have a problem, so I'm at a loss.

I notice I'm a couple Diamond versions behind so I'm downloading the latest (3.5) right now.  I'll post an update if anything changes.  Thanks for the advice.

[ts-mp]

Success!  Thanks for the help.  There were two tricks to this: 

First, use the Diamond Programmer and "create a blank project" <--- that's important otherwise it'll try to detect the cable and break itself.  In Diamond 3.3 it would just fail to work.  In Diamond 3.5 it actually crashes the programmer.
Second, go straight to firmware and don't "detect" anything.  Give it the firmware and tell it to update.  If it tries to detect then it'll break again.