Jump to content

SpacedCowboy

Members
  • Posts

    4
  • Joined

  • Last visited

Posts posted by SpacedCowboy

  1. 23 hours ago, malexander said:


    There appears to be a different issue on your system. Our internal library that enumerates FTDI devices directly using libusb appears to see the AD2 but for some reason FTDI's D2XX library does not. I don't recall ever encountering this situation before. Normally both don't work. Can you please execute "ioreg -c IOUSBInterface -l -w 0 > usbdevices.txt" and then send me the txt file?

    @malexander Done :)

  2. @malexander Still not working over here, though :(

    I am still seeing:

    sh-3.2$ python ~simon/Downloads/digi_enum.py 
    
    Digilent FTDI Enumeration library loaded
    Devices: 1
     1. SN:210321A195D5 'Digilent USB Device' flags: 0x0 type: 0x8 id: 0x4036014 locid: 0x110
     2. SN:210299A1818C 'Digilent USB Device' flags: 0x0 type: 0x8 id: 0x4036014 locid: 0x1b0
    
    FTDI Version: 0x10202
    Devices: 0
    
    DMGR Version: 2.8.2
    Devices: 0
    
    DWF Version: 3.4.7
    Devices: 0

    (one of these is the Analog discovery, the other is an HS3) ... and I have:

    sh-3.2$ ls /Library/Frameworks/dwf.framework/Resources/digilent/adept/data/firmware
    FTDIFW_50_00000011_00000000_010A.dylib	FX2FW_03_00000011_00000000_030A.HEX
    FTDIFW_51_00000001_00000000_010A.dylib	FX2FW_04_00000005_00000000_030A.HEX
    FTDIFW_52_00000011_00000000_010B.dylib	FX2FW_05_0000000D_00000000_030A.HEX
    FTDIFW_53_00000001_00000000_010A.dylib	FX2FW_06_0000001D_00000000_030A.HEX
    FTDIFW_54_00000013_00000000_010B.dylib	FX2FW_08_0000000D_00000000_030A.HEX
    FTDIFW_55_00000811_00000000_010A.dylib	FX2FW_09_0000000D_00000000_030A.HEX
    FTDIFW_56_00000811_00000000_010A.dylib	FX2FW_0A_0000001D_00000000_030A.HEX
    FTDIFW_57_00000001_00000000_010A.dylib	FX2FW_0B_00000000_0000000D_030A.HEX
    FTDIFW_60_00000000_00000801_010A.dylib	FX2FW_0C_0000000D_00000000_030A.HEX
    FX2FW_01_00000001_00000000_030A.HEX	FX2FW_0D_0000000D_00000000_030A.HEX
    FX2FW_01_00000010_00000000_030A.HEX	FX2FW_0E_0000000D_00000000_030A.HEX
    FX2FW_02_00000001_00000000_030A.HEX	FX2FW_0F_00000000_0000000D_030A.HEX
    FX2FW_02_00000004_00000000_030A.HEX

     

  3. @attila

    So I have the same problem on my Mac Pro. I plug in the Analog Discovery 2 directly to my Mac, nothing happens (no LEDs or anything light up, don't know if they're supposed to)

    If I run 'Enumerate.py', I see:

    sh-3.2# python ~simon/Downloads/Enumerate.py 
    
    FTDI Version: 0x10202
    Devices: 0
    
    DMGR Version: 2.8.2
    Devices: 0
    
    DWF Version: 3.4.7
    Devices: 0

    And if I run 'digi_enum.py' I get:

    sh-3.2# python ~simon/Downloads/digi_enum.py 
    
    Digilent FTDI Enumeration library loaded
    Devices: 1
     1. SN:210321A195D5 'Digilent USB Device' flags: 0x0 type: 0x8 id: 0x4036014 locid: 0x1f0
    
    FTDI Version: 0x10202
    Devices: 0
    
    DMGR Version: 2.8.2
    Devices: 0
    
    DWF Version: 3.4.7
    Devices: 0

    ... so that sees *something* ... 

    kextstat reports:

    sh-3.2# kextstat | grep -i ftdi
      156    0 0xffffff7f83d6f000 0x2000     0x2000     com.digilent.driver.DigilentFtdiDriver (1.0.3) 04D22EC0-C800-389F-A0FD-F0F759897EEE <42 4 3>

    And both 'dmesg' and 'syslog', after plugging in the device, report at the end:

    Feb 15 08:40:45 atlantis kernel[0] <Notice>: Digilent probe8: initial probe score = 100000
    Feb 15 08:40:45 atlantis kernel[0] <Notice>: Digilent probe: Manufacturer Name = Digilent
    Feb 15 08:40:45 atlantis kernel[0] <Notice>: Digilent probe8: final probe score = 100001
    Feb 15 08:40:45 atlantis kernel[0] <Notice>: Digilent Starting

    ... but no matter what I do, running Waveforms 2015 (version 3.4.7) on the Mac (running El Capitan, 10.11.6) doesn't detect any device :(

    If it helps, there is no /dev/tty.usbserial<anything> device file either. I've unplugged all my other FTDI devices (mainly JTAG-HS3's :) in case things were getting confused. Any ideas ?

×
×
  • Create New...