Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
21594 Discussions

Excalibur FPGA JTAG Issues

Altera_Forum
Honored Contributor II
‎11-01-2011 06:08 PM
1,786 Views

Hey all, 

I'm working on a legacy project that is using an EXPA10 FPGA with an ARM922T processor built in. I'm currently trying to program it via JTAG, but when I scan the chain, It comes up saying that there is a problem with the JTAG chain. When I go into Debug, I can see the EXPA10 Device, and the ARM922T shows up as "Unkown9220DD". 

 

I've checked the solder joints, and have checked the signal integrity on the JTAG lines and everything seems to be built correctly, but I can't seem to detect the full JTAG chain. 

 

The board was designed to have MSEL 0, MSEL 1 tied low and the Boot Flash is tied high, so it's suppose to boot from flash, but there is nothing loaded into flash yet. 

 

I guess my question is should I be able to see the full JTAG chain? or do I have to have something in the flash first to tell the PLD to connect to the ARM section of the FPGA? 

 

Thanks!!!
0 Kudos

Link Copied

7 Replies
Altera_Forum
Honored Contributor II
‎11-01-2011 06:57 PM
1,043 Views

try quartus 5 or so.

0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎11-01-2011 07:07 PM
1,043 Views

I've tried different versions of Quartus (ver. 11, 2.2, currently on 9) and haven't had any luck with any of those.

0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎11-01-2011 07:35 PM
1,043 Views

Please cut and paste the output from `jtagconfig --debug` as that should make it obvious what is going on. I suspect that the excalibur part has been removed from the Quartus parts database which is why you're seeing this behaviour.

0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎11-01-2011 07:58 PM
1,043 Views

I have a feeling of that to, but what's interesting is that I have another board (golden unit that has been programmed, not by us thou) that actually detects the JTAG chain just fine. 

 

At any rate, when I use jtagconfig, the response I get is 

'1) ByteBlasterMV [LPTL1] "ByteBlasterMV or ByteBlaster II" 

Unable to read device chain (JTAG chain broken)
0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎11-01-2011 08:00 PM
1,043 Views

wombat, looks like EXPA parts are still listed in pgm_parts.txt in 11.0sp1

0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎11-01-2011 08:06 PM
1,043 Views

in that case you've pretty well narrowed it down to a board/fpga issue

0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎11-01-2011 08:12 PM
1,043 Views

I had a feeling it was that, but I wanted to make sure that I was debugging this correctly before I chalked it up to the part / board. I think the root cause of everything is that the TMS or TCK lines within the FPGA are garbage, that's why I'm seeing both devices in debug, but not detecting the full chain like I should be able to. 

 

Thanks everyone for your input! If anybody else has input / feedback, it is greatly appreciated.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.