Programming / Flashing a Blank Pluto Board

Please take a look at the content of the pluto-jtag-bootstrap files released with each release.

https://github.com/analogdevicesinc/plutosdr-fw/releases/download/v0.29/plutosdr-jtag-bootstrap-v0.29.zip

It's important to initialize the PS in particular the clocks and the DDR memory. Otherwise you can't load uboot.

This step is done my sourcing he ps7_init.tcl script and then running ps7_init and ps7_post_config.

run.tcl: 

connect arm hw
stop
xreset 64

source ps7_init.tcl
ps7_init
ps7_post_config

dow u-boot.elf
run

disconnect 64

-Michael

Hello, thank you for the reply. 

So the revised steps then, would be:

1. Ground JTAG_BOOT pin, power on Pluto.

2. Program bitstream

3. Run TCL source described above. 

I have followed these steps, taking care to specify the path to these files when running the commands in the TCL window within vivado. 

I can program the bitstream just fine, meaning the connection to my SmartLynq seems to be working. 

But when I run the TCL described in your initial reply, I can see that the TCL source is running but I get the following error. 

"Error Occured"

"Cable is not connected to the host."

Likewise, If I run the command "connect arm hw" in the TCL console alone, I get the error: "Unknown Command"

Why would vivado think that the cable is not connected properly if I was able to program the bitstream without an issue?

Hello, thank you for the reply. 

So the revised steps then, would be:

1. Ground JTAG_BOOT pin, power on Pluto.

2. Program bitstream

3. Run TCL source described above. 

I have followed these steps, taking care to specify the path to these files when running the commands in the TCL window within vivado. 

I can program the bitstream just fine, meaning the connection to my SmartLynq seems to be working. 

But when I run the TCL described in your initial reply, I can see that the TCL source is running but I get the following error. 

"Error Occured"

"Cable is not connected to the host."

Likewise, If I run the command "connect arm hw" in the TCL console alone, I get the error: "Unknown Command"

Why would vivado think that the cable is not connected properly if I was able to program the bitstream without an issue?

Seems like this could be an issue with a program called ISE from Xilinx?

What version of vivado are you using?

I am using Vivado V2017.4

I found this thread that shows some steps to install cable drivers. I am going to try this without the VM. 

forum.digilentinc.com/.../

Trying to move away from the VM has not worked...Seems like this issue is persistent whether i am using a VM or not..

Any suggestions on what else I can try?

XMD was completely replaced by XSDB only in SDK 2018.1, so the commands posted by Michael should be valid for your version.

However, try to use the XSDB commands instead of the XMD ones. Most of them are similar, except connect/disconnect, targets: instead of "connect arm hw", try "connect" and instead of "disconnect 64", try "disconnect". To find out the available targets type "targets" and to select one target as the active one, type "target id" - have a look here for more details: https://www.xilinx.com/html_docs/xilinx2018_2/SDK_Doc/xsct/connections/reference_xsct_connections.html

Thanks,

Dragos

Hello, Thank you for the reply.

I have tried instead using the XSDB commands.

Upon executing the "connect" command, I can see that the hardware sever is successfully connected to.

"xsct% connect
attempting to launch hw_server

****** Xilinx hw_server v2017.4
  **** Build date : Dec 15 2017-21:02:11
    ** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.

INFO: hw_server application started
INFO: Use Ctrl-C to exit hw_server application

INFO: To connect to this hw_server instance use url: TCP:127.0.0.1:3121"

I then use the "targets" command to list all available targets.

The terminal replies with nothing.

I did have an issue programming the bit-stream until i decreased the jtag frequency. I am wondering if there is a similar issue here.

From there I went and referenced the Xilinx XSDB page for jtag commands and found the following here:

Xilinx XMDB Commands

If i use the "jtag targets" command, which is supposed to list available targets, the terminal also replies with nothing.

It is odd because when trying to use the "jtag frequency -list" command, I receive from the terminal:

"Invalid target. Use "jtag targets" command to select a target"

I think this may be a jtag frequency issue as I am able to connect to the hw server but am not able to connect to the target once connected to the hw server.

Any ideas on how to specify jtag frequency without first connecting to a target?

According to the XSDB documentation, I should instead of using "connect arm hw" be using the two commands: "connect", then "targets" to list available targets, then "targets idcode" to connect to a specific target.

Right now it seems like I cannot connect to the targets while using either xmd or xsdb.

Works for me - that's what I did:

****** Xilinx System Debugger (XSDB) v2018.2
  **** Build date : Jun 14 2018-20:18:43
    ** Copyright 1986-2018 Xilinx, Inc. All Rights Reserved.


xsdb%                                                                                                                                                                                                       
xsdb% connect                                                                                                                                                                                               
tcfchan#0                                                                                                                                                                                                   
xsdb% targets                                                                                                                                                                                               
xsdb% targets                                                                                                                                                                                               
xsdb% targets                                                                                                                                                                                               
xsdb% Info: ARM Cortex-A9 MPCore #0 (target 2) Stopped at 0xffffff28 (Suspended)                                                                                                                            
xsdb% Info: ARM Cortex-A9 MPCore #1 (target 3) Stopped at 0xffffff34 (Suspended)
xsdb% targets                                                                                                                                                                                               
  1  APU
     2  ARM Cortex-A9 MPCore #0 (Suspended)
     3  ARM Cortex-A9 MPCore #1 (Suspended)
  4  xc7z010
xsdb% targets 2                                                                                                                                                                                             
xsdb% source build/ps7_init.tcl                                                                                                                                                                             
xsdb% ps7_init                                                                                                                                                                                              
xsdb% ps7_post_config                                                                                                                                                                                       
xsdb% dow build/u-boot.elf                                                                                                                                                                                  
Downloading Program -- /home/michael/devel/pluto/plutosdr-fw/build/u-boot.elf
	section, .text: 0x04000000 - 0x0403f613
	section, efi_runtime_text: 0x0403f614 - 0x0403f62b
	section, .rodata: 0x0403f630 - 0x0404ef2c
	section, .hash: 0x0404ef30 - 0x0404ef47
	section, .dtb.init.rodata: 0x0404ef50 - 0x0405130f
	section, .data: 0x04051310 - 0x04053537
	section, .got.plt: 0x04053538 - 0x04053543
	section, efi_runtime_data: 0x04053548 - 0x0405360f
	section, .u_boot_list: 0x04053610 - 0x04054413
	section, .rel.dyn: 0x04054414 - 0x0405ce73
	section, .bss_start: 0x04054414 - 0x04054413
	section, .bss: 0x04054414 - 0x040a4e53
	section, .bss_end: 0x040a4e54 - 0x040a4e53
100%    0MB   0.1MB/s  00:05                                                                                                                                                                                
Setting PC to Program Start Address 0x04000000
Successfully downloaded /home/michael/devel/pluto/plutosdr-fw/build/u-boot.elf
xsdb% con                                                                                                                                                                                                   
Info: ARM Cortex-A9 MPCore #0 (target 2) Running                                                                                                                                                            
xsdb%                                                                                                                                                                                                       
xsdb% 

I have tried to replicate your terminal output in both Vivado 2017.4 and 2018.2 and in both situations I get stuck at the targets command

"xsct% connect
attempting to launch hw_server

****** Xilinx hw_server v2017.4
  **** Build date : Dec 15 2017-21:02:11
    ** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.

INFO: hw_server application started
INFO: Use Ctrl-C to exit hw_server application

INFO: To connect to this hw_server instance use url: TCP:127.0.0.1:3121

tcfchan#1
xsct% targets
xsct% targets
xsct% targets
xsct% targets
xsct% targets
xsct% targets
xsct% "

as well as:

"disconnect
xsct% Info: tcfchan#1 closed
connect -url TCP:127.0.0.1:3121
xsct% tcfchan#2
xsct% targets
xsct% targets
xsct% targets
xsct% targets
xsct% "

On my smart lynq, I have all the jtag connections made except for the "SRSTn". Vref, GND, TDI, TDO, TCK and TMS are all connected. And I am able to at least program the bitstream.

I'm using -

Xilinx Platform USB Cable II in conjunction with the ADALM-JTAGUART adapter.

I also installed the Xilinx cable drivers.

-Michael