IMPACT : Can't open /dev/parport0: No such file or directory - Page 1
Forum section: electronics / general

author: promach
author_rank: Frequent Contributor
timestamp: April 18, 2021, 11:03:38 am
content: I have the following IMPACT log with JTAGCode:Can't open /dev/parport0: No such file or directoryCan't open /dev/parport1: No such file or directoryCan't open /dev/parport2: No such file or directoryCan't open /dev/parport3: No such file or directoryCode:GUI --- Auto connect to cable...// *** BATCH CMD : setCable -port autoAutoDetecting cable. Please wait.*** WARNING ***: When port is set to auto detect mode, cable speed is set to default 6 MHz regardless of explicit arguments supplied for setting the baud ratesPROGRESS_START - Starting Operation.Using windrvr6 driver.Connecting to cable (Usb Port - USB21).Checking cable driver.File version of /opt/Xilinx/14.7/ISE_DS/ISE/bin/lin64/xusbdfwu.hex = 1030.File version of /usr/share/xusbdfwu.hex = 1030.libusb-driver.so version: 2021-04-18 11:44:26.Cable connection failed.Connecting to cable (Parallel Port - parport0).libusb-driver.so version: 2021-04-18 11:44:26.LPT1 Base Address set from env variable = 0.LPT base address = 0000h.LPT1 Ecp Address set from env variable = 400.ECP base address = 0400h.LPT port is already in use. rc = FFFFFFFFhCable connection failed.Connecting to cable (Parallel Port - parport1).libusb-driver.so version: 2021-04-18 11:44:26.LPT2 Base Address set from env variable = 10.LPT base address = 0010h.LPT2 Ecp Address set from env variable = 410.ECP base address = 0410h.LPT port is already in use. rc = FFFFFFFFhCable connection failed.Connecting to cable (Parallel Port - parport2).libusb-driver.so version: 2021-04-18 11:44:26.LPT3 Base Address set from env variable = 20.LPT base address = 0020h.LPT3 Ecp Address set from env variable = 420.ECP base address = 0420h.LPT port is already in use. rc = FFFFFFFFhCable connection failed.Connecting to cable (Parallel Port - parport3).libusb-driver.so version: 2021-04-18 11:44:26.LPT4 Base Address set from env variable = 30.LPT base address = 0030h.LPT4 Ecp Address set from env variable = 430.ECP base address = 0430h.LPT port is already in use. rc = FFFFFFFFhCable connection failed.PROGRESS_END - End Operation.Elapsed time = 2 sec.Cable autodetection failed.WARNING:iMPACT:923 - Can not find cable, check cable setup !

author: Psi
author_rank: Super Contributor
timestamp: April 18, 2021, 11:13:40 am
content: I can see a reference to libusb.Are you using a USB to LPT port adapter?Those are intended for printers and do not implement a full hardware LPT port with all the hardware registers.To get a proper printer port you need either one built onto the motherboard or added with PCI/PCIe card.If you are using a proper hardware LPT port, check if you have permission to access the /dev/parport0 devices

author: promach
author_rank: Frequent Contributor
timestamp: April 18, 2021, 12:45:42 pm
content: I am using FT2232H which does USB-to-JTAGSeehttps://ftdichip.com/wp-content/uploads/2020/07/AN_129_FTDI_Hi_Speed_USB_To_JTAG_Example.pdfAs in why IMPACT tool requires parallel LPT port, I have no idea at all.

author: bingo600
author_rank: Super Contributor
timestamp: April 18, 2021, 12:50:16 pm
content: To me it seems like it has problems detecting the usb cable.And because the cable type is set to Auto , it tries parport as other option./Bingo

author: promach
author_rank: Frequent Contributor
timestamp: April 18, 2021, 01:03:37 pm
content: The JTAG cable detection issue is solved by inserting "source /opt/Xilinx/14.7/ISE_DS/settings64.sh" into $HOME/.bashrcHowever, I still have the following CRC error even though IMPACT tool said that bitstream loading is completed.WARNING:iMPACT:2217 - Error shows in the status register, CRC Error bit is NOT 0.'1': Programming terminated. DONE did not go high.Code:'1': Loading file '/home/phung/Downloads/DDR_backup/DDR_Xilinx_ISE/test_ddr3_memory_controller.bit' ...done.INFO:iMPACT:1777 -Reading /opt/Xilinx/14.7/ISE_DS/ISE/spartan6/data/xc6slx16.bsd...INFO:iMPACT:2257 - Startup Clock has been changed to 'JtagClk' in the bitstream stored in memory,but the original bitstream file remains unchanged.UserID read from the bitstream file = 0xFFFFFFFF.Data width read from the bitstream file = 1.INFO:iMPACT:501 - '1': Added Device xc6slx16 successfully.--------------------------------------------------------------------------------------------------------------------------------------------Active mode is BSGUI --- Auto connect to cable...INFO:iMPACT - Digilent Plugin: Plugin Version: 2.4.4INFO:iMPACT - Digilent Plugin: found 1 device(s).INFO:iMPACT - Digilent Plugin: opening device: "JtagSmt1", SN:210203367162INFO:iMPACT - Digilent Plugin: User Name: JtagSmt1INFO:iMPACT - Digilent Plugin: Product Name: Digilent JTAG-SMT1INFO:iMPACT - Digilent Plugin: Serial Number: 210203367162INFO:iMPACT - Digilent Plugin: Product ID: 30800151INFO:iMPACT - Digilent Plugin: Firmware Version: 010AINFO:iMPACT - Digilent Plugin: JTAG Port Number: 0INFO:iMPACT - Digilent Plugin: JTAG Clock Frequency: 10000000 HzINFO:iMPACT - Current time: 4/18/21 8:53 PMMaximum TCK operating frequency for this device chain: 25000000.Validating chain...Boundary-scan chain validated successfully.'1': IDCODE is '01000100000000000010000010010011''1': IDCODE is '44002093' (in hex).'1': : Manufacturer's ID = Xilinx xc6slx16, Version : 4INFO:iMPACT - Current time: 4/18/21 8:53 PMMaximum TCK operating frequency for this device chain: 25000000.Validating chain...Boundary-scan chain validated successfully.'1': Usercode is 'ffffffff'INFO:iMPACT - Current time: 4/18/21 8:53 PMMaximum TCK operating frequency for this device chain: 25000000.Validating chain...Boundary-scan chain validated successfully.'1': Reading bootsts register contents... VALID_0 - ERROR OR END OF STARTUP (EOS) DETECTED : 0 FALLBACK_0 - FALLBACK RECONFIGURATION ATTEMPT DETECTED : 0 RESERVED : 0 WTO_ERROR_0 - WATCHDOG TIME OUT ERROR : 0 ID_ERROR_0 - FPGA DEVICE IDCODE ERROR : 0 CRC_ERROR_0 - CYCLIC REDUNDANCY CHECK (CRC) ERROR : 0 VALID_1 - ERROR OR END OF STARTUP (EOS) DETECTED : 0 FALLBACK_1 - FALLBACK RECONFIGURATION ATTEMPT DETECTED : 0 RESERVED : 0 WTO_ERROR_1 - WATCHDOG TIME OUT ERROR : 0 ID_ERROR_1 - FPGA DEVICE IDCODE ERROR : 0 CRC_ERROR_1 - CYCLIC REDUNDANCY CHECK (CRC) ERROR : 0 STRIKE CNT - STRIKE COUNT FOR FALLBACK ATTEMPTS : 0 STRIKE_CNT - STRIKE COUNT FOR FALLBACK ATTEMPTS : 0 STRIKE_CNT - STRIKE COUNT FOR FALLBACK ATTEMPTS : 0 STRIKE_CNT - STRIKE COUNT FOR FALLBACK ATTEMPTS : 0'1': Reading status register contents... CRC ERROR : 0 IDCODE ERROR : 0 DCM LOCK STATUS : 0 GTS_CFG_B STATUS : 0 GWE STATUS : 0 GHIGH STATUS : 0 DECRYPTION ERROR : 0 DECRYPTOR ENABLE : 0 HSWAPEN PIN : 0 MODE PIN M : 0 MODE PIN M : 0 RESERVED : 0 INIT_B PIN : 0 DONE PIN : 0 SUSPEND STATUS : 0 FALLBACK STATUS : 0INFO:iMPACT - Current time: 4/18/21 8:53 PMMaximum TCK operating frequency for this device chain: 25000000.Validating chain...Boundary-scan chain validated successfully.'1': DNA = '000000000000000000000000000000000000000000000000000000000'INFO:iMPACT - Current time: 4/18/21 8:53 PMPROGRESS_START - Starting Operation.Maximum TCK operating frequency for this device chain: 25000000.Validating chain...Boundary-scan chain validated successfully.'1': Programming device...LCK_cycle = NoWait.LCK cycle: NoWaitdone.'1': Reading status register contents... CRC ERROR : 1 IDCODE ERROR : 0 DCM LOCK STATUS : 0 GTS_CFG_B STATUS : 0 GWE STATUS : 0 GHIGH STATUS : 0 DECRYPTION ERROR : 0 DECRYPTOR ENABLE : 1 HSWAPEN PIN : 0 MODE PIN M : 0 MODE PIN M : 0 RESERVED : 1 INIT_B PIN : 0 DONE PIN : 0 SUSPEND STATUS : 0 FALLBACK STATUS : 0WARNING:iMPACT:2217 - Error shows in the status register, CRC Error bit is NOT 0.INFO:iMPACT:2219 - Status register values:INFO:iMPACT - 1000 0001 0001 0000INFO:iMPACT:579 - '1': Completed downloading bit file to device.INFO:iMPACT:188 - '1': Programming completed successfully.LCK_cycle = NoWait.LCK cycle: NoWaitINFO:iMPACT - '1': Checking done pin....done.'1': Programming terminated. DONE did not go high.PROGRESS_END - End Operation.Elapsed time = 0 sec.

author: rstofer
author_rank: Super Contributor
timestamp: April 18, 2021, 03:08:21 pm
content: You might try DigilentInc's Adept software as a stand-alone programming tool. I haven't played with 14.7 in a long time but it seems to me that I was always using Adept rather than Impact. I have never used it on Linux.https://store.digilentinc.com/digilent-adept/ETA: I do know that Adept works on Linux because it is required for Waveforms. I just haven't used it with ISE.

author: promach
author_rank: Frequent Contributor
timestamp: April 18, 2021, 03:15:37 pm
content: @rstoferThanks for your link, but I am already usinghttps://wiki.archlinux.org/index.php/Xilinx_ISE_WebPACK#Digilent_USB-JTAG_Drivers

author: rstofer
author_rank: Super Contributor
timestamp: April 18, 2021, 03:33:17 pm
content: @promachYou may have the correct drivers but the problem is likely with Impact.That you are having a problem is no surprise to Xilinx:https://www.xilinx.com/support/answers/20762.htmlAmong other things, Impact is not supported under Linux 64 bit other than RedHat.

author: promach
author_rank: Frequent Contributor
timestamp: April 18, 2021, 04:15:07 pm
content: @rstoferThanks for the Xilinx website link and your advice,setup_pcusbis actually already settled byhttps://wiki.archlinux.org/index.php/Xilinx_ISE_WebPACK#Xilinx_Platform_Cable_USB-JTAG_Driversthough

author: jmelson
author_rank: Super Contributor
timestamp: April 23, 2021, 11:31:11 pm
content: Quote from: rstofer on April 18, 2021, 03:33:17 pmI use Impact just fine on an Ubuntu 12.04 x64 system. Did I have to install a library? Quite possible, it has been a while.Jon

author: bingo600
author_rank: Super Contributor
timestamp: April 25, 2021, 06:14:44 am
content: Quote from: rstofer on April 18, 2021, 03:33:17 pmI'm running ISE 14.7 with no problems on a Mint 17.3 x64 - (Ubuntu 16.04 base i think).I use a $20 Xilinx clone programmer (the one that looks like the original)I seem to remember that i had to set an environment variable telling impact to use LIBUSB/Bingo

author: promach
author_rank: Frequent Contributor
timestamp: April 25, 2021, 08:55:09 am
content: The real root cause for my JTAG cable detection issue is due to the unreliablePHYSICALcable wire connection, in other words, signal integrity issue.I am able to connect and detect JTAG adapter cable now, but I am pretty sure this issue will haunt me in the future again.By the way, for those looking for some solution, insert the following two lines into $HOME/.bashrcCode:export LD_PRELOAD=/opt/Xilinx/usb-driver/libusb-driver.sosource /opt/Xilinx/14.7/ISE_DS/settings64.shBesides, why the generation error for chipscope ?Quote