I hope the factory technical support staff can answer it, thank you
WINDOWS Device Manager Phenomenon:
After connecting the JTAG module to the computer, the USB device can only be found in the hardware manager, and the JTAG device cannot be found. Only one USB serial converter can be found as shown in the figure.
In the management menu of WIN10, you can see other devices displaying DIGILENT USB DEVICE, as shown
Under normal circumstances, a COM serial port will be displayed in the WIN7 device manager, but the damaged module cannot find the COM serial port in the WIN7 computer management.
VIVADO phenomenon:
Damaged Modules Using VIVADO Connections in WIN7 Scan to XILINX_TCF/DIGILENT/...
But can't connect as shown
After the module is replaced, the problem persists. If the damaged module is removed and USB is connected separately and the power is supplied, the device cannot be recognized. However, a short-time serial port can be automatically scanned in VIVADO. Using a backup scheme on the board, which uses an external JTAG scanning device connection to connect to the FPGA, the FPGA's JTAG chain is undamaged. Related drawings are shown below.
DIGILENT ADPET scanning phenomenon:
Using the DIGILENT ADPET scan can scan the device model of the damaged module, but no data can be scanned as shown in the figure:
The log is as follows:
Loading board information...
Warning: Could not find specific board information
Initializing Scan Chain...
Default information loaded.
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Initialization Failed.
However, the SN of the device can be scanned in the DEVICE MANAGER. as the picture shows
In the normally used board of the JTAG-SMT2-NC module, although the COM serial port is not visible in the WIN10 device manager, the device can be scanned using ADEPT as shown in the figure.
The circuit diagram related to the module and module is as follows
Which TDO from V7 after the level conversion chip is not actually connected in series 50OHM resistor directly to the module's TDO pin, suspected of causing problems after the TDO level conversion chip was replaced to prevent the TDO at the level The push-pull output of the converter chip causes damage to the JTAG module. An N-channel MOS transistor is used for level shifting. Both voltage sides are pulled up using 15K resistors, and then the new JTAG module is replaced, but the problem remains. Replacement level conversion chip circuit as shown, this circuit can make both voltage side signals are weak pull-up state.
MOS tube using BSS138, 1.8V pressure difference can meet the GS open voltage requirements.
In addition, this JTAG module is not damaged at the beginning of a power-on, but it can be used just after the DCB is completed, but it is unstable. After a few days, the JTAG module cannot be connected to the FPGA. After connecting the jumper cap in the above circuit diagram Using the reserved 6PIN pin to connect the external JTAG module can debug the FPGA normally, but it cannot be connected normally after replacing the JTAG-SMT2-NC module.
Question
yixiti
I hope the factory technical support staff can answer it, thank you
WINDOWS Device Manager Phenomenon:
After connecting the JTAG module to the computer, the USB device can only be found in the hardware manager, and the JTAG device cannot be found. Only one USB serial converter can be found as shown in the figure.
In the management menu of WIN10, you can see other devices displaying DIGILENT USB DEVICE, as shown
Under normal circumstances, a COM serial port will be displayed in the WIN7 device manager, but the damaged module cannot find the COM serial port in the WIN7 computer management.
VIVADO phenomenon:
Damaged Modules Using VIVADO Connections in WIN7 Scan to XILINX_TCF/DIGILENT/...
But can't connect as shown
After the module is replaced, the problem persists. If the damaged module is removed and USB is connected separately and the power is supplied, the device cannot be recognized. However, a short-time serial port can be automatically scanned in VIVADO. Using a backup scheme on the board, which uses an external JTAG scanning device connection to connect to the FPGA, the FPGA's JTAG chain is undamaged. Related drawings are shown below.
DIGILENT ADPET scanning phenomenon:
Using the DIGILENT ADPET scan can scan the device model of the damaged module, but no data can be scanned as shown in the figure:
The log is as follows:
Loading board information...
Warning: Could not find specific board information
Initializing Scan Chain...
Default information loaded.
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Found device ID: ffffffff
Initialization Failed.
However, the SN of the device can be scanned in the DEVICE MANAGER. as the picture shows
In the normally used board of the JTAG-SMT2-NC module, although the COM serial port is not visible in the WIN10 device manager, the device can be scanned using ADEPT as shown in the figure.
The circuit diagram related to the module and module is as follows
Which TDO from V7 after the level conversion chip is not actually connected in series 50OHM resistor directly to the module's TDO pin, suspected of causing problems after the TDO level conversion chip was replaced to prevent the TDO at the level The push-pull output of the converter chip causes damage to the JTAG module. An N-channel MOS transistor is used for level shifting. Both voltage sides are pulled up using 15K resistors, and then the new JTAG module is replaced, but the problem remains. Replacement level conversion chip circuit as shown, this circuit can make both voltage side signals are weak pull-up state.
MOS tube using BSS138, 1.8V pressure difference can meet the GS open voltage requirements.
In addition, this JTAG module is not damaged at the beginning of a power-on, but it can be used just after the DCB is completed, but it is unstable. After a few days, the JTAG module cannot be connected to the FPGA. After connecting the jumper cap in the above circuit diagram Using the reserved 6PIN pin to connect the external JTAG module can debug the FPGA normally, but it cannot be connected normally after replacing the JTAG-SMT2-NC module.
Link to comment
Share on other sites
2 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.