Tutorial: Using the USB-Blaster as an SOPC/Qsys Avalon-MM master

If you do not use 8/10B encoding, then you have to synchronize the links yourself. For example, I have used the transceiver sync pattern detect logic, and hard-coded it to the start of a PRBS sequence and used that to synchronize lanes.

Hi all,

Hi Dave,

Hi!

tcl> tcl> 
JTAG: USB-Blaster , FPGA: @1: EP2C(15|20) (0x020B30DD)
tcl> 
         Hub info: 0x8086E04
      VIR m-width: 4
      VIR n-width: 1
  Manufacturer ID: 0x6E
  Number of nodes: 1
       IP Version: 1
tcl> jtag_print_node_info
invalid command name "jtag_print_node_infojtag_print_node_info"
tcl> 
tcl> jtag_print_node_info
       Node index:    0
    Node instance:    0 (0x0)
Node manufacturer:  110 (0x6E)
          Node ID:  132 (0x84)
     Node purpose:    1 (0x1)
     Node version:    1 (0x1)
tcl> jtag_read 0 0
Sending 4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A007B000000040000107A007CFC00
Received 4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A4A0000
Error: incorrect number of response bytes! (Got 0, expected 8)
tcl> 

Hi Michael,

Hi, I am working on the tutorial and get stuck at the master_write or master_read command line. I'm using the Quartus Prime Lite 19.1 and Platform Designer (formerly Qsys), I wrote those line command in TCL console in System Console and get the error saying the transaction is taking longer than 10 seconds and continue for another 50 seconds, then it said the system console is giving up. I tried everything to rectify the problem like correcting the path for the environment variable, update to latest Quartus Prime (on having the problem I used version 18.1). Is there any specific set up before using the command line that I need to set in my computer? Any helps are indeed great.

@Altera_Forum Thank you for these files.

I have been able to use them on System Console 12.1 CLI for awhile now. It works great.

I recently updated to newer versions (Version 18.0, Version 21.1 850, Version 22.2 94) CLI and unfortunately there I cannot send commands from the client to the server anymore. It crashes here:

proc client_handler {client} {
[...]
# Execute the command and return the response
# puts "CLIENT ($client): $cmd"
if {[catch {eval $cmd} rsp]} {

The same exact code works on the GUI (non-CLI).

I can connect just fine. I can modify the TCP starting script, and execute commands anywhere (ex: puts [get_service_types]) outside of server_accept, & client_handler.

Executing the same one inside of either, Java VM JRE crashes (similarly to any command passed through by the client).

Would anyone have an idea of what is happening?

right here it crashes XXserver_acceptXX
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006182ba52, pid=23628, tid=0x000000000000550c
#
# JRE version: OpenJDK Runtime Environment (8.0_322-b06) (build 1.8.0_322-b06)
# Java VM: OpenJDK 64-Bit Server VM (25.322-b06 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# V  [jvm.dll+0x13ba52]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Program Files (STL)\quartus_systemconsole_21_1\sopc_builder\bin\hs_err_pid23628.log
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
#

# Start the server on the specified port
proc server_listen {port} {
	puts "right here it works XXserver_listenXX"
		puts [get_service_types]
		puts "it just worked"
		
	global jtag
	if {[catch {socket -server server_accept $port} result]} {

#		error "Error: Server start-up failed\n -> $result"
		puts "Error: Server start-up failed\n -> $result"
                exit
	}
	set jtag(port)   $port
	set jtag(socket) $result
	return
}
# Server client-accept callback
proc server_accept {client addr port} {
		puts "right here it crashes XXserver_acceptXX"
		puts [get_service_types]
		puts "uh oh"