- Sun Sep 03, 2006 7:53 am
#18284
The IDCODE setting in the configuration doesn't seem to be used by anything anymore.
I'm currently working on an USB-Blaster driver for OpenOCD and it definitely IS able to read the idcode of a Cyclone. Not sure if the script shown below is the correct way to do it, but it works:
Code: Select all
I have not found a single line in the sourcecode where device->idcode is set... it is always zero. Once an "idcode" command existed, right?Open On-Chip Debugger
> scan
0: idcode: 0x00000000 ir length 10, ir capture 0x155, ir mask 0x3ff, current instruction 0x6
The IDCODE setting in the configuration doesn't seem to be used by anything anymore.
I'm currently working on an USB-Blaster driver for OpenOCD and it definitely IS able to read the idcode of a Cyclone. Not sure if the script shown below is the correct way to do it, but it works:
Code: Select all
KoljaOpen On-Chip Debugger
> var idcode 32
> endstate rti
> irscan 0 6
> drscan 0 idcode
> var idcode
idcode (1 fields):
0x20830dd (/32)