--- Quote Start ---
Yes I have sourced the file from within SystemConsole under TCL console. I have tried to source the jtag_cmds_sc.tcl for the de2 and also bemicro but when then try to change the LEDs , I receive error : "Sorry, no master nodes found
error: can't read "jtag(master)": no such variable" .
--- Quote End ---
Use this as an opportunity to understand what the scripts do :)
1. Make sure your design contains a JTAG-to-Avalon-MM bridge.
If you look in the hierarchy display in Quartus after synthesis, you should see an sld_hub, and then if you expand the Qsys system, you'll see the jtag_master.
2. Read the SystemConsole Tcl script and read the Quartus handbook section that describes the commands.
The "Sorry, no master nodes found" comes from the jtag_open command, i.e., the Tcl commands
set master_paths
if { == 0} {
puts "Sorry, no master nodes found"
return
}
The Quartus command "get_service_paths master" returns a list of JTAG-to-Avalon-MM bridge components in your design. The fact that it does not find any means that you've either forgotten to download the board, or some other issue.
--- Quote Start ---
I am looking at the System Console interactive session in Figure 13. Must I use these commands? I am just doing what is in Figure 14 , which is sourcing the tcl file and then trying to change LEDs etc.
--- Quote End ---
If you compare Figure 13 to the jtag_cmds_sc.tcl script, you'll see that the Tcl script simply wraps those commands in user-friendly set of procedures, so what you have done is fine. The problem is that your design is not recognized as having a JTAG-to-Avalon-MM master, i.e., the jtag_open procedure called the first time you try to use jtag_read or jtag_write is failing.
--- Quote Start ---
I also use pin planner to assign the LED ports to actual pins on the cyclone IV. Is this necessary, because I don't see this in the notes? If that is the case , must I assign all the ports there, including tck,tdi,tdo,tms?
--- Quote End ---
Yeah, you're right, this could be stated a little more explicitly. To a long-time user of FPGAs, its "obvious" that pin assignments change between boards, but this is not the case for new users :)
You must assign the clock and LED pins correctly. The JTAG pins are fixed, so don't worry about assigning them.
--- Quote Start ---
Sorry for the bombardment of questions, but we are determined to get it right ))
--- Quote End ---
No need to apologize. The tools are often annoying. I've already suffered through the pain and frustration, so I don't mind saving others some grief :)
Cheers,
Dave
Honored Contributor
