Forum Discussion
WZ2
Frequent Contributor
2 years agoHi there,
Regarding this issue, first, we need to clarify which step is causing such a slow rate. Remote debugging involves the following steps: Remote PC -> JTAG server -> SSH 1309 port -> network -> SSH 1309 port -> JTAG server -> local PC -> USB driver -> USB -> JTAG port.
If you can ensure that there are no issues between your local PC and the JTAG port, I recommend focusing on the server on the remote PC, the network speed, and the local JTAG server. You may want to consider trying different remote PCs and network connections. If there is still no improvement after these changes, I suggest monitoring the data throughput on the 1309 port both locally and remotely during the loading process.
Best regards,
WZ
FvM
Super Contributor
2 years agoHi,
your mentioning of virtual USB suggests that you are not using Intel remote JTAG server but connecting JTAG programmer through generic remote USB connection. This can lead to very inefficient operation. I also noticed that programming time with some third party USB Blaster replacements with own drivers is considerably slower than original USB Blaster.
your mentioning of virtual USB suggests that you are not using Intel remote JTAG server but connecting JTAG programmer through generic remote USB connection. This can lead to very inefficient operation. I also noticed that programming time with some third party USB Blaster replacements with own drivers is considerably slower than original USB Blaster.