USB blaster and LCOMX256C Lattice

Hello,

I come again for the same problem (Sorry)

For more than 15 days I try desperately to read ID code of an LMCOMX256C. (Lattice product)
I tried with Quartus, TopJtag and TopJtagProbe.
TopJtagProbe has a log, and gives me that it finds an IDCode, which should match nothing or incomplete??


Some idcode(s) collected
NO JTAG chain found
Analyzing the JTAG chain...
TAP reset
DR scan...
Bits to be shifted in:
11111111000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
000000000000
Bits shifted out:
11000010000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
000000000000
TAP reset
DR scan...
Bits to be shifted in:
11111111000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
000000000000
Bits shifted out:
11000010000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
00000000000000000000000000000000+
000000000000

.......

Checking for all bits are either ones or zeros...
Last 500 bits we received are either only ones or only zeros
JTAG chain NOT found, checking for Atmel ATmega bug...
Reçu des bits ont deux ones et zeros
IDCODE register
11000010000000000000000000000000

.......

On the attached example, you will be able to see a case that works in string extracted from another forum. (This is the result I should have)
As it never worked in chain, I remind you that I tested the components one by one.
This works for the analog device BF532, but never for lattice with my USB Blaster.
I have read literature about this problem on the net, there are often this case cited.
It is explained that the connection must be modified by adding resistance/+ capacitor, especially on the clock.
I didn’t try anything.
For the case cited as an example, this was done with a WIGGLER connection, so on a sponsor port.
So I’m wondering, is there not a speed problem or what like that?

1) So I wonder if this component is "referenced" in these softwares or that it should appear in all cases even if it is a new one. Then the BDSL file of the manufacturer would be important. Or device not compatible with these sotfware??

2nd) I would like to try with the Quartus string debugger, but I don’t know the commands to enter.
If someone could give me an example (Copy screen), I think there are only 3 fields to fill in (command, TAP State and clock) and do it several times. I think you understood me

I thing that this chinesse USB Blaster work

here the init:

Creating CrUsbBlaster
Loading USB-Blaster FTD2XX interface:
Loading usbblstr32.dll ... OK
Found 1 USB-Blaster device(s)
Destroying CrUsbBlaster
Creating cable object ALTERA_USB_BLASTER
Creating CrUsbBlaster
Loading USB-Blaster FTD2XX interface:
Loading usbblstr32.dll ... OK
Device successfully opened
Initialization succeeded

Thank's for your help