Sorry, you need to enable JavaScript to visit this website.

Cannot detect Ultrazed Board on host PC using UART and JTAG.

Unsolved
24 posts / 0 new
smhroot
Junior(0)
Cannot detect Ultrazed Board on host PC using UART and JTAG.

Hi there, 
    Recently I upgrade my development board from zedboard to ultrazed (including IO carrier). And now I met a strange problem:
My host PC and Vivado cannot find the connected UltraZed, which means: the seriel cannot open the COM(or ttys) port using USB-UART, and Vivado cannot program bitstream to FPGA using JTAG as well.
OS : ubuntu14.04
Vivado: 2017.1
 
I followed the start kit tutorials:

  1.  Install USB UART Drivers (CP210x)
  2. set boot mode to QSPI
  3. connect JP1 on IO Carrier Card
  4. connect the power
  5. start the Tera term and set the parameters...

And cannot open the serial port. I use 'ls /dev' and no /dev/ttyACM0 or other serial port find. Tera Term shows no characters.
Then I followed the start kit Vivado tutorials (led example):

  1.  design the 'bd'
  2. generate the bitstream
  3. set the boot mode to JTAG
  4. programming bitsteam

But I cannot open the target FPGA, which means no board detected by USB-JTAG. 
What's more, the host PC can detect and program my ZedBoard.
 
The board is new bought, is it possible there are some problems with it?  Any one can give some advise? Thanks in advance.
 

JFoster
Moderator(67)
Hello Smhroot,

Hello Smhroot,

1)  Are you absolutely sure the boot mode switch positions are all set to ON? The ON position is clearly marked on the switch.

2)  To eliminate issues with the USB-JTAG module on the Carrier Card, do you have a Xilinx USB JTAG cable you can use instead? You can plug the USB JTAG cable into the J6 JTAG header on the Carrier Card (make sure to disconnect the USB cable from the USB-JTAG module when using the USB JTAG cable).

--Josh

prevotet
Junior(0)
Cannot detect JTAG cable

Hi,
I have the same issue with my UltraZed board. My jtag cable is not recognized and I don't see any device in the Hardware Manager.
When the board is on and the cable attached to it, I don't see anything even in the Windows Peripherals Management. Nothing happens !
I don't see any led on the SMT2 JTAG. Is this normal ?
I have made sure that the boot configuration is OK (All switches to ON) and I unfortunately have no other Xilinx JTAG cable to test with the J6 header. Can you help me ?

JFoster
Moderator(67)
Hello Prevotet,

Hello Prevotet,

Just to confirm, Does your board power on properly? Here are a few things to check

1. Does the fan turn on?

2. Is the PWR Good LED enumerated?

3. If JP1 on the SOM is present please remove it.

4. Please make sure the Carrier Card and SOM are properly Mated.(Please detatch and then reatach the SOM to the Carrier Card)-I have had quite a few people have this issue.

Could you also try the USB-JTAG Module that is populated on the IO Carrier Card and see if you are still encountering this issue?

Thank you,

Josh

prevotet
Junior(0)
Hi, thank you for your prompt

Hi, thank you for your prompt answer,
actually,
1) the fan does turn on
2) the PWR led is on
3) I removed JP1 on the SOM board (but left the one in the carrier board)
4)I did this too
Concerning JTAG, I noticed that the SMT2 component heats up very much but still no connection. I have tried using a Xilinx JTAG cable but although the cable is recognized, the device is not.
Everything else works (SD CARD, QSPI)
JC

JFoster
Moderator(67)
Hello JC,

Hello JC,

Would you say your problem is similar to what is described in this post?

http://zedboard.org/content/smt2-jtag-board-overheating

--Josh

prevotet
Junior(0)
Hi Josh,

Hi Josh,
at least we have this problem of overheating. However, the PS red light is not flashing but always turned on, and most important, the JTAG device is not seen in any tool ! Shouldn't we expect to detect it at least in the peripherals' management ?
thank you
JC

JFoster
Moderator(67)
Hello JC,

Hello JC,

So what your saying is that when the out of box design is running you do not see the PS on-board user Red LED flashing? Or are you refering to when in JTAG boot mode the LED is solid red?

--Josh

prevotet
Junior(0)
Hi,

Hi,
When I run the out of box design, the PS red light is flashing correctly. In JTAG mode it is solid red, which might be normal. Do you know if I should see any led on the SMT2 JTAG component ?
thank u
JC

JFoster
Moderator(67)
Hello JC,

Hello JC,

Please refer to your private messages.

Thank you,

Josh

egor777
Junior(0)
Hello,

I have a same problem - Hardware Manager don't see a board and SMT2 heats up very much.
OS: Win 10
Out-of-box design works correctly, but in jtag boot mode HW Manager can't  find board (via USB JTAG cable and Xilinx Platform Cable too).
Please, send the answer to me (in PM).
Thanks
 
 

JFoster
Moderator(67)
Please see your private

Please see your private messages.

Thanks!

Josh

mattg
Junior(0)
Same Problem

Hi,
 
I've the same problem as well. OOB design ist running like a charme. But if I change the boot mode to JTAG, I can't see the board in the HW manager. SMT2 seems to get rather hot as well, but can't really check due to lack of a heat camera.
 
Have you found a solution to this problem?
 
Best,
Matthias
 
 

JFoster
Moderator(67)
Hello Matthias,

Hello Matthias,

Please refer to your private messages.

Thank you,

Josh

dyessgg
Junior(0)
Similar but no overheating

I have a similar problem, but no overheating of the SMT2. This is a new kit (received it just 3 weeks ago and the first week was out of town).

The SOM and IOCC are perfectly fine (boots Ubuntu from SDCard and accesses SATA drive and network).

I changed the boot mode switch settings to all ON, connected USB cable to SMT2 and tried to "Open Target".
Vivado sees the JTAG adapter just fine but no devices on the target. I also have an HS3 adapter and that has the same results:

connect_hw_server
INFO: [Labtools 27-2285] Connecting to hw_server url TCP:localhost:3121
open_hw_target
INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/210251A4F888
ERROR: [Labtools 27-2269] No devices detected on target localhost:3121/xilinx_tcf/Digilent/210251A4F888.
Check cable connectivity and that the target board is powered up then
use the disconnect_hw_server and connect_hw_server to re-register this hardware target.
ERROR: [Common 17-39] 'open_hw_target' failed due to earlier errors.

I've reseated the board, tried multiple host machines, tried Ubuntu 16.04 and Windows 7 hosts, tried with and without JP1, visually inspected the IOCC to SOM connectors for damage. Nothing makes a difference. It's almost as if the JTAG signals are not getting from the IOCC to the Zynq chip or they're shorted somewhere.

Any ideas?

dyessgg
Junior(0)
More info

I forgot to mention the USB serial ports are working fine as well when running Ubuntu.

JFoster
Moderator(67)
Hello dyessgg,

Hello dyessgg,

Please remove and reatach your SOM. Can you program your bitstream via SDK?

-Josh

dyessgg
Junior(0)
No Joy

I've reseated the SOM a number of times, but I reseated it again and no joy. I've tried with and without the screws in the SOM standoffs.

No joy on SDK access either. Everything sees the JTAG adapter but no devices after the adapter.

I have probed the JTAG signals via the PC4 connector. It appears the SMT2 is functioning as I see activity on the JTAG_TDI pin when the hardware is open. There is nothing on the JTAG_TDO. It remains high the entire time. I also see what appears to be a clock signal on JTAG_TCK. The INIT line is high and VREF is 1.8V.

Thanks,
Greg

JFoster
Moderator(67)
Hi Greg,

Hi Greg,

Please confirm your SOM is in JTAG boot mode.

—Josh

dyessgg
Junior(0)
Confirmed.

All4 boot mode switches are in the ON position as labled on the switch. I also tried all 4 in the opposite direction just to make sure I was not misreading the switch markings.

Just to make sure the SOM had not become damaged from all the removal/reinsertions, I set the boot mode switches back to SD card and booted Ubuntu again. UltraZed booted Ubuntu with no problems. Ethernet, Serial console and SATA all functioned perfectly.

Any other ideas befoer I RMA this kit? I really need it next week so I don't want to have to send it back and wait another month.

JFoster
Moderator(67)
Hello dyessg,

Hello dyessg,

From what your describing there appears to be some sort of short after the SMT2 module.

Do you have an HS3/HS2/platform cable you could try plugging into the provided JTAG header?

If you do and can program the bitstream that way it would indicate there is an issue with the SMT2.

Regardless of the outcome I would suggest you contact Avnet for an RMA(unless your OK with the malfunctioning SMT2 pending the JTAG header experiment).

--Josh

dyessgg
Junior(0)
My thoughts too

I've tried a HS3 adapter connected to the PC4 JTAG connector with no success.

I also have tried a DSTream (with the adapter) where I can control the connection parameters much more closely. It also says there is a failure. It sees the device is powered up and attempts to send commands but gets no response. I've asked a coworker who is a JTAG/debug expert and he's stumped as well.

I need the board next week for some things that don't require JTAG. I'll contact Avnet support to see what the next steps need to be.

Thanks for your help.

dyessgg
Junior(0)
Anyone know how to get an RMA?

I've been trying for over a week to get an RMA from Avent. I sent an email to the support address and got the standard Microsoft CRM response that I would hear something back within 72 hours. That was over a week ago.

Does anyone still work in Avnet?

JFoster
Moderator(67)
Hello dyessgg,

Hello dyessgg,

I am unaware as to what devision receives those emails. Please call to get your issue elevated. I found some customer support phone #s here

https://www.avnet.com/wps/portal/us/company/help/

--Josh