Hi folks, the answers the first quiz have made some smile to my face, so I decided to make it more interesting and am actually offering prizes for the first correct answer, prizes will be FPGA miniconsole from www.xiltendo.com for first answer that is correct (to each quiz posted by me to C.A.F.), or for first question that requires me to answer in way that solution is obvious. the first quiz was the 2 LED one, already posted on C.A.F. so here comes the second (this is much much simpler) Xilinx Spartan3A on custom PCB. was working ok was stressed VCCINT=1.8V (regulator IC current limit 150ma) it does configure ok from external configuration memory JTAG scan returns JTAGID from Virtex-II family. what is wrong? Antti PS the prizes will be sent to the winner free of charge from first production batch. (and thats all public info til that time)
FPGA quiz2: spartan3A return Virtex JTAGID. Also prizes for quiz1 and quiz2
Started by ●October 16, 2007
Reply by ●October 16, 20072007-10-16
Antti wrote:> Xilinx Spartan3A on custom PCB. > was working ok > was stressed VCCINT=1.8V (regulator IC current limit 150ma) > it does configure ok from external configuration memory > > JTAG scan returns JTAGID from Virtex-II family. > > what is wrong?Delays in the JTAG chain that shift the data by 1 bit ? Was the JTAGID manufacturer field still the Xilinx ID ? Laurent Pinchart
Reply by ●October 16, 20072007-10-16
On 16 Okt., 09:51, Laurent Pinchart <laurent.pinch...@skynet.be> wrote:> Antti wrote: > > Xilinx Spartan3A on custom PCB. > > was working ok > > was stressed VCCINT=1.8V (regulator IC current limit 150ma) > > it does configure ok from external configuration memory > > > JTAG scan returns JTAGID from Virtex-II family. > > > what is wrong? > > Delays in the JTAG chain that shift the data by 1 bit ? Was the JTAGID > manufacturer field still the Xilinx ID ? > > Laurent PinchartJTAG ID returned vendor Xilinx family Virtex-II device 0 (invalid) this same (wrong!) JTAGID returned all the time
Reply by ●October 16, 20072007-10-16
Antti wrote:> On 16 Okt., 09:51, Laurent Pinchart <laurent.pinch...@skynet.be> > wrote: >> Antti wrote: >> > Xilinx Spartan3A on custom PCB. >> > was working ok >> > was stressed VCCINT=1.8V (regulator IC current limit 150ma) >> > it does configure ok from external configuration memory >> >> > JTAG scan returns JTAGID from Virtex-II family. >> >> > what is wrong? >> >> Delays in the JTAG chain that shift the data by 1 bit ? Was the JTAGID >> manufacturer field still the Xilinx ID ? >> >> Laurent Pinchart > > JTAG ID returned > vendor Xilinx > family Virtex-II > device 0 (invalid) > > this same (wrong!) JTAGID returned all the timeTDO driven by more than one component ? If two Xilinx parts drive TDO in sync (instead of being properly chained) conflicts will occur for the family and device ID by not the vendor ID. Laurent Pinchart
Reply by ●October 16, 20072007-10-16
On 16 Okt., 10:17, Laurent Pinchart <laurent.pinch...@skynet.be> wrote:> Antti wrote: > > On 16 Okt., 09:51, Laurent Pinchart <laurent.pinch...@skynet.be> > > wrote: > >> Antti wrote: > >> > Xilinx Spartan3A on custom PCB. > >> > was working ok > >> > was stressed VCCINT=1.8V (regulator IC current limit 150ma) > >> > it does configure ok from external configuration memory > > >> > JTAG scan returns JTAGID from Virtex-II family. > > >> > what is wrong? > > >> Delays in the JTAG chain that shift the data by 1 bit ? Was the JTAGID > >> manufacturer field still the Xilinx ID ? > > >> Laurent Pinchart > > > JTAG ID returned > > vendor Xilinx > > family Virtex-II > > device 0 (invalid) > > > this same (wrong!) JTAGID returned all the time > > TDO driven by more than one component ? If two Xilinx parts drive TDO in > sync (instead of being properly chained) conflicts will occur for the > family and device ID by not the vendor ID. > > Laurent Pinchart- Zitierten Text ausblenden - > > - Zitierten Text anzeigen -single IC chain Antti (sorry for posting from different account, google goups asserted temp. block on my primary account)
Reply by ●October 16, 20072007-10-16
avrbasic@hotmail.com wrote:> On 16 Okt., 10:17, Laurent Pinchart <laurent.pinch...@skynet.be> > wrote: >> Antti wrote: >> > On 16 Okt., 09:51, Laurent Pinchart <laurent.pinch...@skynet.be> >> > wrote: >> >> Antti wrote: >> >> > Xilinx Spartan3A on custom PCB. >> >> > was working ok >> >> > was stressed VCCINT=1.8V (regulator IC current limit 150ma) >> >> > it does configure ok from external configuration memory >> >> >> > JTAG scan returns JTAGID from Virtex-II family. >> >> >> > what is wrong? >> >> >> Delays in the JTAG chain that shift the data by 1 bit ? Was the JTAGID >> >> manufacturer field still the Xilinx ID ? >> >> >> Laurent Pinchart >> >> > JTAG ID returned >> > vendor Xilinx >> > family Virtex-II >> > device 0 (invalid) >> >> > this same (wrong!) JTAGID returned all the time >> >> TDO driven by more than one component ? If two Xilinx parts drive TDO in >> sync (instead of being properly chained) conflicts will occur for the >> family and device ID by not the vendor ID. >> >> Laurent Pinchart- Zitierten Text ausblenden - >> >> - Zitierten Text anzeigen - > > single IC chain > > Antti > (sorry for posting from different account, google goups asserted temp. > block on my primary account)Could the family and device ID be stored as some kind of fuses that got burnt when VCCINT was raised to 1.8V ? Laurent Pinchart
Reply by ●October 16, 20072007-10-16
On 16 Okt., 13:42, Laurent Pinchart <laurent.pinch...@skynet.be> wrote:> avrba...@hotmail.com wrote: > > On 16 Okt., 10:17, Laurent Pinchart <laurent.pinch...@skynet.be> > > wrote: > >> Antti wrote: > >> > On 16 Okt., 09:51, Laurent Pinchart <laurent.pinch...@skynet.be> > >> > wrote: > >> >> Antti wrote: > >> >> > Xilinx Spartan3A on custom PCB. > >> >> > was working ok > >> >> > was stressed VCCINT=1.8V (regulator IC current limit 150ma) > >> >> > it does configure ok from external configuration memory > > >> >> > JTAG scan returns JTAGID from Virtex-II family. > > >> >> > what is wrong? > > >> >> Delays in the JTAG chain that shift the data by 1 bit ? Was the JTAGID > >> >> manufacturer field still the Xilinx ID ? > > >> >> Laurent Pinchart > > >> > JTAG ID returned > >> > vendor Xilinx > >> > family Virtex-II > >> > device 0 (invalid) > > >> > this same (wrong!) JTAGID returned all the time > > >> TDO driven by more than one component ? If two Xilinx parts drive TDO in > >> sync (instead of being properly chained) conflicts will occur for the > >> family and device ID by not the vendor ID. > > >> Laurent Pinchart- Zitierten Text ausblenden - > > >> - Zitierten Text anzeigen - > > > single IC chain > > > Antti > > (sorry for posting from different account, google goups asserted temp. > > block on my primary account) > > Could the family and device ID be stored as some kind of fuses that got > burnt when VCCINT was raised to 1.8V ? > > Laurent Pinchart- Zitierten Text ausblenden - > > - Zitierten Text anzeigen -it was my first guess too, but no this is not the case Antti
Reply by ●October 16, 20072007-10-16
On Oct 16, 6:45 am, Antti <Antti.Luk...@googlemail.com> wrote:> On 16 Okt., 13:42, Laurent Pinchart <laurent.pinch...@skynet.be> > wrote: > > > > > avrba...@hotmail.com wrote: > > > On 16 Okt., 10:17, Laurent Pinchart <laurent.pinch...@skynet.be> > > > wrote: > > >> Antti wrote: > > >> > On 16 Okt., 09:51, Laurent Pinchart <laurent.pinch...@skynet.be> > > >> > wrote: > > >> >> Antti wrote: > > >> >> > Xilinx Spartan3A on custom PCB. > > >> >> > was working ok > > >> >> > was stressed VCCINT=1.8V (regulator IC current limit 150ma) > > >> >> > it does configure ok from external configuration memory > > > >> >> > JTAG scan returns JTAGID from Virtex-II family. > > > >> >> > what is wrong? > > > >> >> Delays in the JTAG chain that shift the data by 1 bit ? Was the JTAGID > > >> >> manufacturer field still the Xilinx ID ? > > > >> >> Laurent Pinchart > > > >> > JTAG ID returned > > >> > vendor Xilinx > > >> > family Virtex-II > > >> > device 0 (invalid) > > > >> > this same (wrong!) JTAGID returned all the time > > > >> TDO driven by more than one component ? If two Xilinx parts drive TDO in > > >> sync (instead of being properly chained) conflicts will occur for the > > >> family and device ID by not the vendor ID. > > > >> Laurent Pinchart- Zitierten Text ausblenden - > > > >> - Zitierten Text anzeigen - > > > > single IC chain > > > > Antti > > > (sorry for posting from different account, google goups asserted temp. > > > block on my primary account) > > > Could the family and device ID be stored as some kind of fuses that got > > burnt when VCCINT was raised to 1.8V ? > > > Laurent Pinchart- Zitierten Text ausblenden - > > > - Zitierten Text anzeigen - > > it was my first guess too, but no this is not the case > > AnttiIs this the Spartan 3A that was originally going to be a Virtex family chip, then they rebranded it but did not change the ID? S Woods
Reply by ●October 16, 20072007-10-16
Antti wrote:> On 16 Okt., 13:42, Laurent Pinchart <laurent.pinch...@skynet.be> > wrote: >> avrba...@hotmail.com wrote: >> > On 16 Okt., 10:17, Laurent Pinchart <laurent.pinch...@skynet.be> >> > wrote: >> >> Antti wrote: >> >> > On 16 Okt., 09:51, Laurent Pinchart <laurent.pinch...@skynet.be> >> >> > wrote: >> >> >> Antti wrote: >> >> >> > Xilinx Spartan3A on custom PCB. >> >> >> > was working ok >> >> >> > was stressed VCCINT=1.8V (regulator IC current limit 150ma) >> >> >> > it does configure ok from external configuration memory >> >> >> >> > JTAG scan returns JTAGID from Virtex-II family. >> >> >> >> > what is wrong? >> >> >> >> Delays in the JTAG chain that shift the data by 1 bit ? Was the >> >> >> JTAGID manufacturer field still the Xilinx ID ? >> >> >> >> Laurent Pinchart >> >> >> > JTAG ID returned >> >> > vendor Xilinx >> >> > family Virtex-II >> >> > device 0 (invalid) >> >> >> > this same (wrong!) JTAGID returned all the time >> >> >> TDO driven by more than one component ? If two Xilinx parts drive TDO >> >> in sync (instead of being properly chained) conflicts will occur for >> >> the family and device ID by not the vendor ID. >> >> >> Laurent Pinchart- Zitierten Text ausblenden - >> >> >> - Zitierten Text anzeigen - >> >> > single IC chain >> >> > Antti >> > (sorry for posting from different account, google goups asserted temp. >> > block on my primary account) >> >> Could the family and device ID be stored as some kind of fuses that got >> burnt when VCCINT was raised to 1.8V ? >> >> Laurent Pinchart- Zitierten Text ausblenden - >> >> - Zitierten Text anzeigen - > > it was my first guess too, but no this is not the case > > AnttiDid the JTAGID change after you applied VCCINT=1.8V or was it already defective before ? Laurent Pinchart
Reply by ●October 16, 20072007-10-16
On 16 Okt., 15:02, Laurent Pinchart <laurent.pinch...@skynet.be> wrote:> Antti wrote: > > On 16 Okt., 13:42, Laurent Pinchart <laurent.pinch...@skynet.be> > > wrote: > >> avrba...@hotmail.com wrote: > >> > On 16 Okt., 10:17, Laurent Pinchart <laurent.pinch...@skynet.be> > >> > wrote: > >> >> Antti wrote: > >> >> > On 16 Okt., 09:51, Laurent Pinchart <laurent.pinch...@skynet.be> > >> >> > wrote: > >> >> >> Antti wrote: > >> >> >> > Xilinx Spartan3A on custom PCB. > >> >> >> > was working ok > >> >> >> > was stressed VCCINT=1.8V (regulator IC current limit 150ma) > >> >> >> > it does configure ok from external configuration memory > > >> >> >> > JTAG scan returns JTAGID from Virtex-II family. > > >> >> >> > what is wrong? > > >> >> >> Delays in the JTAG chain that shift the data by 1 bit ? Was the > >> >> >> JTAGID manufacturer field still the Xilinx ID ? > > >> >> >> Laurent Pinchart > > >> >> > JTAG ID returned > >> >> > vendor Xilinx > >> >> > family Virtex-II > >> >> > device 0 (invalid) > > >> >> > this same (wrong!) JTAGID returned all the time > > >> >> TDO driven by more than one component ? If two Xilinx parts drive TDO > >> >> in sync (instead of being properly chained) conflicts will occur for > >> >> the family and device ID by not the vendor ID. > > >> >> Laurent Pinchart- Zitierten Text ausblenden - > > >> >> - Zitierten Text anzeigen - > > >> > single IC chain > > >> > Antti > >> > (sorry for posting from different account, google goups asserted temp. > >> > block on my primary account) > > >> Could the family and device ID be stored as some kind of fuses that got > >> burnt when VCCINT was raised to 1.8V ? > > >> Laurent Pinchart- Zitierten Text ausblenden - > > >> - Zitierten Text anzeigen - > > > it was my first guess too, but no this is not the case > > > Antti > > Did the JTAGID change after you applied VCCINT=1.8V or was it already > defective before ? > > Laurent Pinchart- Zitierten Text ausblenden - > > - Zitierten Text anzeigen -I did not observe the wrong ID before. I did some rework on the PCB, the VCCINT regulator VCCADJ did fell off, and i was suddenly measuring 1.8V after fixing the supply and completing my PCB rework, the ID was wrong. the problem has been fixed, and the same FPGA now works fully ok again and returns correct ID too. Antti
