|
From: Adrien Prost-B. <adr...@la...> - 2014-05-15 18:09:07
|
Aaaargh. You should really have a look at the Valgrind report (attached)... Adrien On Thu, 2014-05-15 at 19:12 +0200, Joris van Rantwijk wrote: > On 2014-05-15, Adrien Prost-Boucle wrote: > > JTAG loc.: 0 IDCODE: 0xf5059093 Desc: XCF32P Rev: O IR length: 16 > > JTAG loc.: 1 IDCODE: 0xf5059093 Desc: XCF32P Rev: O IR length: 16 > > JTAG loc.: 2 IDCODE: 0x59608093 Desc: XC95144XL Rev: E IR length: 8 > > Ok, two flash PROMs and one CPLD. > > > JTAG loc.: 3 IDCODE: 0x0a001093 not found in 'built-in device list'. > > This is a SystemACE controller. It is not supported by xc3sprog. > You probably don't need to talk to it, but an unrecognized device > in the JTAG chain makes it impossible for xc3sprog to talk to the > other device. > > To solve that, you could add an entry to devlist.txt with the > correct IDcode, instruction length and description. > Instruction length should be 8 according to xccace.bsd. > > > JTAG loc.: 4 IDCODE: 0x72ad6093 Desc: XCF32P Rev: G IR length: 10 > > This is the FPGA. It should be recognized as XC5VLX110T. > It is very strange that xc3sprog would label it as XCF32P; that > must be a weird bug in xc3sprog or something wrong with your devlist.txt > file. > > Joris. |