Hi all,
Well, I was so happy that I can now design, simulate AND program the ATF16V8 and ATF22V10 devices, I launched full speed at doing similar for the ATF1504... I already knew that my current programmer (an Arduino "afterburner" spin-off) doesn't handle CPLDs, so I had spent some time working on using a "Altera USB Blaster 2" that someone gave me recently.

I couldn't get anything to work to start with, but someone here on the Forum talked about Quartus... so I installed that and got Quartus to talk correctly to the Blaster (I'm exclusively a linux (Mint) user, although I use wine for some apps such as WinCUPL...) but Quartus doesn't like the ATF1504 series chips, correctly identifies them but refuses to do anything with them (treats them as "unknown").

So next step was openocd... Again it took a while before I understood how it was supposed to work, but I got it to identify the Blaster, and to identify the JTAG chain with my ATF1504 at the end of it. But libusb, used by openocd, just cannot read or write any data from/to the chip, it fails with ERROR_IO...

Has anyone out there been there, done that, and knows what's happening ? AFAIK my system is up to date (Linux Mint 20.2 Uma base: Ubuntu 20.04 focal) although not the latest version : I'm of the school of "if it works, don't fix it"... Any pointers would be appreciated.

Thanks in advance

_________________
Glenn-in-France

So, bit by the clones...

The USB Blaster-II that I have is a sort of USB Blaster 1 and a bit. Quartus recognizes it as a 2, but opened is not easily fooled. The major difference is in the USB communication chip inside the device - the one I have is still based on the ftdi chip.

Once I had reconfigured to use the ftdi interface - IT WORKED !

_________________
Glenn-in-France

Are you saying you can program ATF1504 with USB Blaster II? Under Quartus?

No, spoiler alert : that Isn't what I meant. Quartus refuses to program the Atmel/Microchip devices. No, my problem was getting openocd to program the ATF1504 with the USB Blaster 1.something that I have.

Sorry if I've spoiled your day

_________________
Glenn-in-France

That’s great improvement already. Atmel’s programmer is quite expensive, so using openocd to drive the inexpensive USB blaster II clone to program ATF1504 is a great progress.
Bill

This thread will be very interesting to several people. It would be a great help if you could clarifty two things:

1. The toolchain you used to generate the Atmel .jed file
2. The actual openocd command line you used to program the .jed file into an ATF1504AS.

Thanks,

Dave

OK, after the weekend (v busy), I'll create a new thread with a "how to"...

_________________
Glenn-in-France

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

Thanks Dave! I really appreciate your help... download lagu