Steve

Members
  • Content Count

    4
  • Joined

  • Last visited

  1. Hi JColvin, To draw most of a line underneath this issue I was finally able to get back to this board and try it again. This time I used windows, and the Vivado software was not running. Firstly I installed: digilent.adept.system_v2.16.1.exe and digilent.adept.utilities_v2.2.1.exe I then powered the board up with both Digilent JTAG-SMT2-NC cards enabled. C:\Users\Steve>dadutil enum Found 1 device(s) Device: JtagSmt2NC Product Name: Digilent JTAG-SMT2NC User Name: JtagSmt2NC Serial Number: 210308A1CB76 C:\Users\Steve>dadutil setsn -d JtagSmt2NC -sn 210308A1BEEF Serial number set to: 210308A1CB76 C:\Users\Steve> (Weird that it reported it was set to the old serial number) After I cycled power I obtained the following result. C:\Users\Steve>dadutil enum Found 2 device(s) Device: JtagSmt2NC Product Name: Digilent JTAG-SMT2NC User Name: JtagSmt2NC Serial Number: 210308A1CB76 Device: JtagSmt2NC Product Name: Digilent JTAG-SMT2NC User Name: JtagSmt2NC Serial Number: 210308A1BEEF C:\Users\Steve> Two cards appeared with two serial numbers... Fixed... One thing of note, it appears I was only talking to one card in the first instance, even though there were two enabled. This is actually a good thing, as it means you can fix serial numbers without disabling hardwired connections. At least I now have a recipe to fix these situations, thanks. I'm still curious that if this was a QA issue on your end where two cards ended up with the same serial number? i.e. should we expect this again in the future? Thanks, Steve
  2. Hi Jon, Thanks for the info, but it looks like I'm not out of the woods yet. The serial number change command fails with "erc = 3087" on both my original JTAG-SMT2-NC boards. I'm unable to change the serial from 210308A1CB76 on either. We now have a second motherboard which does have different Serial Numbers on each of the two installed JTAG-SMT2-NC: 210308A1CB77 and 210308A1CB78 respectively. This does correctly identify in vivado lab as two different devices! So we are limited to one "broken" motherboard for the moment. --- Here's what I attempted. I first electrically shorted the USB_P/USB_N of the JTAG-SMT2-NC connected to port 3 of the hub and connected it to the Centos6.4 box. It only discovered the "1.3.3.3.3.2" device. # tail /var/log/messages Apr 6 12:08:57 labpc-18 kernel: usb 1-1.3.3.3.2: new high speed USB device number 112 using ehci_hcd Apr 6 12:08:57 labpc-18 kernel: usb 1-1.3.3.3.2: New USB device found, idVendor=0403, idProduct=6014 Apr 6 12:08:57 labpc-18 kernel: usb 1-1.3.3.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Apr 6 12:08:57 labpc-18 kernel: usb 1-1.3.3.3.2: Product: Digilent USB Device Apr 6 12:08:57 labpc-18 kernel: usb 1-1.3.3.3.2: Manufacturer: Digilent Apr 6 12:08:57 labpc-18 kernel: usb 1-1.3.3.3.2: SerialNumber: 210308A1CB76 Apr 6 12:08:57 labpc-18 kernel: usb 1-1.3.3.3.2: configuration #1 chosen from 1 choice [root@labpc-18 ~]# dadutil enum Found 1 device(s) Device: JtagSmt2NC Product Name: Digilent JTAG-SMT2NC User Name: JtagSmt2NC Serial Number: 210308A1CB76 [root@labpc-18 ~]# dadutil setsn -d JtagSmt2NC --sn 210308A1BEEF ERROR: failed to write serial number to device, erc = 3087 [root@labpc-18 ~]# dadutil enum Found 1 device(s) Device: JtagSmt2NC Product Name: Digilent JTAG-SMT2NC User Name: JtagSmt2NC Serial Number: 210308A1CB76 [root@labpc-18 ~]# Then I repeated the above exercise, shorting the other JTAG-SMT2-NC devices USB_P/N pins. [root@labpc-18 ~]# tail /var/log/messages Apr 6 12:21:23 labpc-18 kernel: usb 1-1.3.3.3.3: new high speed USB device number 8 using ehci_hcd Apr 6 12:21:23 labpc-18 kernel: usb 1-1.3.3.3.3: New USB device found, idVendor=0403, idProduct=6014 Apr 6 12:21:23 labpc-18 kernel: usb 1-1.3.3.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Apr 6 12:21:23 labpc-18 kernel: usb 1-1.3.3.3.3: Product: Digilent USB Device Apr 6 12:21:23 labpc-18 kernel: usb 1-1.3.3.3.3: Manufacturer: Digilent Apr 6 12:21:23 labpc-18 kernel: usb 1-1.3.3.3.3: SerialNumber: 210308A1CB76 Apr 6 12:21:23 labpc-18 kernel: usb 1-1.3.3.3.3: configuration #1 chosen from 1 choice [root@labpc-18 ~]# dadutil enum Found 1 device(s) Device: JtagSmt2NC Product Name: Digilent JTAG-SMT2NC User Name: JtagSmt2NC Serial Number: 210308A1CB76 [root@labpc-18 ~]# dadutil setsn -d JtagSmt2NC --sn 210308A1CB75 ERROR: failed to write serial number to device, erc = 3087 [root@labpc-18 ~]# So I know I'm talking to two different devices and neither of them work with the dadutil I installed. These were the commands I used to install the dadutil this morning. # rpm -Uvh digilent.adept.runtime_2.16.1.x86_64.rpm # rpm -Uvh digilent.adept.utilities-2.2.1.x86_64.rpm Any ideas? Does this version of dadutil actually work with JTAG-SMT2-NC? I don't really want to try it on our working board at the moment... Thanks, Steve
  3. Hi, Thanks for your help. Our ultimate system will be Linux which I have logs of the connection, but I was told we had the same matching serial numbers in Windows. I have confirmed that if only one of the JTAG-SMT2-NC is enabled, it works with the Xilinx Driver, so it's not a device driver level issue. It's purely that the Serial Numbers match for two physical devices as supplied by Digilent. I can probably fetch some windows info tomorrow, but today here's the connection info from /var/log/messages on a Centos6.4 system. Apr 5 17:35:02 labpc-18 kernel: usb 1-1.3.3.3.2: new high speed USB device number 57 using ehci_hcd Apr 5 17:35:02 labpc-18 kernel: usb 1-1.3.3.3.2: New USB device found, idVendor=0403, idProduct=6014 Apr 5 17:35:02 labpc-18 kernel: usb 1-1.3.3.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Apr 5 17:35:02 labpc-18 kernel: usb 1-1.3.3.3.2: Product: Digilent USB Device Apr 5 17:35:02 labpc-18 kernel: usb 1-1.3.3.3.2: Manufacturer: Digilent Apr 5 17:35:02 labpc-18 kernel: usb 1-1.3.3.3.2: SerialNumber: 210308A1CB76 Apr 5 17:35:02 labpc-18 kernel: usb 1-1.3.3.3.2: configuration #1 chosen from 1 choice Apr 5 17:35:02 labpc-18 kernel: usb 1-1.3.3.3.3: new high speed USB device number 58 using ehci_hcd Apr 5 17:35:02 labpc-18 kernel: usb 1-1.3.3.3.3: New USB device found, idVendor=0403, idProduct=6014 Apr 5 17:35:02 labpc-18 kernel: usb 1-1.3.3.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Apr 5 17:35:02 labpc-18 kernel: usb 1-1.3.3.3.3: Product: Digilent USB Device Apr 5 17:35:02 labpc-18 kernel: usb 1-1.3.3.3.3: Manufacturer: Digilent Apr 5 17:35:02 labpc-18 kernel: usb 1-1.3.3.3.3: SerialNumber: 210308A1CB76 Apr 5 17:35:02 labpc-18 kernel: usb 1-1.3.3.3.3: configuration #1 chosen from 1 choice If you are notfamiliar with this particular type of log, the "usb 1-1.3.3.3.2" describes the physical path to the device. i.e. The last .2, means port 2 of the last USB Hub. You can therefore see two physical devices are connected (.2 and .3), but the serial numbers are the same "210308A1CB76". I'm looking for a way to change the serials, and a range of valid numbers to use. Is there a FTDIconfig tool that will do this for JTAG-SMT2-NC? Thanks, Steve
  4. Sorry if this is in the wrong forum, I'm not 100% sure which one to use for the JTAG-SMT2-NC board. We have an application where we use two JTAG-SMT2-NC boards connected to the same host PC through a USB Hub. Unfortunately both the boards as supplied have the same Serial Number reported. So far as I can tell this means it is impossible to distinguish between the two boards in the vivado lab edition once they are connected to the same machine. They are soldered down so we actually have to disable the USB port to allow programming to succeed. We saw this on both a Windows and Linux host PC. a) Is there a way to change the serial number on one/both of the boards? Are all JTAG-SMT2-NC delivered with the same serial number? i.e. do we need to go through this process each time?