Author Topic: TE0720 custom carrier no JTAG access  (Read 508 times)

bigguiness

  • Jr. Member
  • **
  • Posts: 79
TE0720 custom carrier no JTAG access
« on: January 03, 2023, 10:17:56 PM »
Hello all,

I have a TE0720 board on a custom carrier board and cannot get the JTAG interface to work from Vivado.

I can connect to the board and I get this in the Hardware dialog:

Code: [Select]
localhost (1)                                   Connected
  xilinx_tcf/Digilent/251633000548BA (1)        Open
    Unknown_Device_0 (0)                        N/A

The Unknown_Device_0 has ID code 012BA043 and an IR length: 8, if that matters.

My carrier board has a TE0790-03 XMOD FTDI JTAG Adapter on it that I am trying to use as the JTAG interface.

I also have the BOOTMODE, JTAGMODE, EN1, and NOSEQ signals from the TE0720 connected to a dip switch. These signals are currently setup as:

Code: [Select]
MODE        HI   - QSPI boot
JTAGMODE    LOW  - Zynq SoC selected
EN1         HI   - on-board supplies enabled
NOSEQ       LOW  - Power sequencing enabled

I have also tried setting MODE LOW. When it is HI I see U-Boot start then the boot stops of I don't have an SD-Card installed. If it's installed the board boots. When MODE is HI I don't see anything on the console.

Changing the JTAGMODE setting does not seem to change anything.

Any ideas?

bigguiness

  • Jr. Member
  • **
  • Posts: 79
Re: TE0720 custom carrier no JTAG access
« Reply #1 on: January 03, 2023, 10:19:32 PM »
Oh, one other thing.

The Hardware Manager is also saying "There are no debug cores. Refresh device".

Clicking on the Refresh device does not change anything.

Thanks

bigguiness

  • Jr. Member
  • **
  • Posts: 79
Re: TE0720 custom carrier no JTAG access
« Reply #2 on: January 04, 2023, 12:07:10 AM »
I finally got the JTAG to work, but I'm not sure how....

Oh well...

JH

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2038
Re: TE0720 custom carrier no JTAG access
« Reply #3 on: January 04, 2023, 07:01:11 AM »
Hi,
good to hear that it works now.

Quote
Unknown_Device_0
this is normally the Lattice CPLD, in this case  JTAGMODE was wrong.

br
John