New Contributor
Super ContributorHi @kopdcom ,
Or try to replace the code section below in tcl script jtag_instance_check.tcl:
# PRINT OUT INSTANCE ID INFO FOR EVERYTHING:
set i 0
foreach path [lsort -command compare_node_number [get_service_paths bytestream]] {
# If this path corresponds to a JTAG UART, incr i
if {[string match *$cable_name* $path ] && [string match *jtag_uart* [marker_get_type $path] ]} {
puts "[marker_get_info $path] (INSTANCE_ID:$i)"
incr i
}
}
set i 0
foreach path [lsort -command compare_node_number [get_service_paths processor]] {
# If this path corresponds to a NiosII, incr i
if {[string match *$cable_name* $path ] && [string match *nios2* [marker_get_type $path] ]} {
puts "[marker_get_info $path] (INSTANCE_ID:$i)"
incr i
}
}
With the code section below:
# PRINT OUT INSTANCE ID INFO FOR EVERYTHING:
set i 0
foreach path [lsort -command compare_node_number [get_service_paths bytestream]] {
# If this path corresponds to a JTAG UART, incr i
if {[string match *$cable_name* $path ] && [string match *jtag_uart* [marker_get_type $path] ]} {
set info [marker_get_info $path]
if {[string first "|" $info] == -1} {
set info [string map {"FULL_HPATH " "FULL_HPATH a:b|"} $info]
}
puts "$info (INSTANCE_ID:$i)"
incr i
}
}
set i 0
foreach path [lsort -command compare_node_number [get_service_paths processor]] {
# If this path corresponds to a NiosII, incr i
if {[string match *$cable_name* $path ] && [string match *nios2* [marker_get_type $path] ]} {
set info [marker_get_info $path]
if {[string first "|" $info] == -1} {
set info [string map {"FULL_HPATH " "FULL_HPATH a:b|"} $info]
}
puts "$info (INSTANCE_ID:$i)"
incr i
}
}
Best Regards,
Sheng
p/s: If any answer from the community or Intel Support are helpful, please feel free to give best answer or rate 4/5 survey.
New ContributorDear Sheng,
I have replaced the code section mentionned in jtag_instance_check.tcl, unfortunatly, still the same error message. I have made screen-prints of all steps:
** Nios II Console:
** Downloading the system associated with the project:
-----------------------------------------------------Info& Erros:-----------------------------------------------------
C:/intelFPGA_lite/18.1/quartus/bin64/quartus_pgm -c "USB-Blaster [USB-0]" --auto
1) USB-Blaster [USB-0]
020F70DD 10CL120(Y|Z)/EP3C120/..
Info: *******************************************************************
Info: Running Quartus Prime Programmer
Info: Version 18.1.0 Build 625 09/12/2018 SJ Lite Edition
Info: Copyright (C) 2018 Intel Corporation. All rights reserved.
Info: Your use of Intel Corporation's design tools, logic functions
Info: and other software and tools, and its AMPP partner logic
Info: functions, and any output files from any of the foregoing
Info: (including device programming or simulation files), and any
Info: associated documentation or information are expressly subject
Info: to the terms and conditions of the Intel Program License
Info: Subscription Agreement, the Intel Quartus Prime License Agreement,
Info: the Intel FPGA IP License Agreement, or other applicable license
Info: agreement, including, without limitation, that your use is for
Info: the sole purpose of programming logic devices manufactured by
Info: Intel and sold by Intel or its authorized distributors. Please
Info: refer to the applicable agreement for further details.
Info: Processing started: Mon Oct 31 13:49:56 2022
Info: Command: quartus_pgm -c "USB-Blaster [USB-0]" -m jtag -o P;C:/intelFPGA_lite/18.1/lights.sof@1
Info (213045): Using programming cable "USB-Blaster [USB-0]"
Info (213011): Using programming file C:/intelFPGA_lite/18.1/lights.sof with checksum 0x00687B2D for device EP4CE115F29@1
Info (209060): Started Programmer operation at Mon Oct 31 13:49:57 2022
Info (209016): Configuring device index 1
Info (209017): Device 1 contains JTAG ID code 0x020F70DD
Info (209007): Configuration succeeded -- 1 device(s) configured
Info (209011): Successfully performed operation(s)
Info (209061): Ended Programmer operation at Mon Oct 31 13:50:04 2022
Info: Quartus Prime Programmer was successful. 0 errors, 0 warnings
Info: Peak virtual memory: 312 megabytes
Info: Processing ended: Mon Oct 31 13:50:04 2022
Info: Elapsed time: 00:00:08
Info: Total CPU time (on all processors): 00:00:10
------------------------------------------------------------------------------------------------------------------------
** After choosing COMPILE (in ACTIONS tab):
** After choosing LOAD (in ACTIONS tab):
Regards...
