--- Quote Start ---
Another question I have is the following:
On page 37 I read the sentences:
This would mean that the program won’t run in my quartus 10.1 version?
Do you have a solution for this?
--- Quote End ---
Of course :)
Read the source code (jtag_server.tcl) ...
# SystemConsole (prior to Quartus 11.1sp1) # # * There is no support for fileevent, so SystemConsole# has to busy loop on one client at a time.# # * If the client closes its connection cleanly via# client_close, then the socket generates an EOF# and the server will wait for the next client.# # * However, if the client disconnection is not cleanm,# eg., the client uses exit or ctrl-C to exit, then# the server does not receive an eof, and it remains# blocked on the dead client connection. New clients,# will not be handled!# # In constrast, when the server is run under# quartus_stp, the server log indicates that a ctrl-C# from a client quartus_stp generates an # 'empty command' followed by 'disconnected'#
puts "Handle the client via a blocked read on the socket"
while {!} {
client_handler $client
}
Note that this applies to SystemConsole, whereas quartus_stp (another tool) works fine.
--- Quote Start ---
For example is it possible to split this up?
Meaning, if I install also quartus 11.1sp1 and run this tcl server/client program from a 11.1sp1 quartus_sh terminal, can I then still communicate to my sopc system generated in quartus 10.1?
--- Quote End ---
Yes, you can use a newer version of Quartus to communicate with the design after it has been downloaded. The JTAG protocol has not changed between Quartus versions.
Cheers,
Dave
Honored Contributor
