Mac + Analog Discovery 2 + Waveforms 2015: No device detected

[Krizzle]

Hi folks - I have a Mac running 10.10.5 and another with 10.11 both not connecting to the Analog Discovery 2 hardware over USB. What I know:

• Hardware works fine from a Windows VM on the Mac
• Plugging in the AD2 loads kext com.digilent.driver.DigilentFtdiDriver AND com.apple.driver.AppleUSBFTDI
• Neither removing com.apple.driver.AppleUSBFTDI via kextunload nor deleting the kext file helps
• Following the *awesome* steps at this post didn't help - WaveForms sees and loads the driver (no logs spit out normally; logs spit out when I rename driver) but still no dice
• Keeping AD2 unplugged while restarting: no dice
• Reinstalling WafeForms and DigilentFtdiDriver-1.0.3.pkg - no dice

Any ideas? Eager to get working on Macs. 

[attila]

Make sure to install the WaveForms SDK from the digilent.waveforms....dmg. Copy, drag and drop, the dwf.framework to Frameworks

[Naoshi]

I edited digi_enum.py as following:

 

--- digi_enum.py    2017-01-17 10:16:02.000000000 +0900

+++ digi_enum_edited.py    2017-01-18 13:01:08.000000000 +0900

@@ -6,10 +6,11 @@ if sys.platform.startswith("win"):

     dmgr = cdll.dmgr

     ftd = oledll.ftd2xx

 elif sys.platform.startswith("darwin"):

-    dwf = cdll.LoadLibrary("/Library/Frameworks/dwf.framework/dwf")

-    dmgr = cdll.LoadLibrary("/Library/Frameworks/dwf.framework/Frameworks/libdmgr.dylib")

-    ftd = cdll.LoadLibrary("/Library/Frameworks/dwf.framework/Frameworks/libftd2xx.dylib")

-    dftd = cdll.LoadLibrary("/Library/Frameworks/dwf.framework/Frameworks/libdftd2xx.dylib")

+    base = "/Applications/Waveforms.app/Contents/"

+    dwf = cdll.LoadLibrary(base+"Frameworks/dwf.framework/dwf")

+    dmgr = cdll.LoadLibrary(base+"Frameworks/dwf.framework/Frameworks/libdmgr.dylib")

+    ftd = cdll.LoadLibrary(base+"Frameworks/dwf.framework/Frameworks/libftd2xx.dylib")

+    dftd = cdll.LoadLibrary(base+"Frameworks/dwf.framework/Frameworks/libdftd2xx.dylib")

 else:

     dwf = cdll.LoadLibrary("libdwf.so")

     dmgr = cdll.LoadLibrary("libdmgr.so")

 

Then, I executed digi_enum_edited.py.

I have the following result:

(Each true serial number is replaced by (serial number).

 

$ python digi_enum_edited.py 

dyld: warning, LC_RPATH @executable_path/../Frameworks in /Applications/Waveforms.app/Contents/Frameworks/dwf.framework/dwf being ignored in restricted program because of @executable_path

 

Digilent FTDI Enumeration library loaded

Devices: 1

 1. SN:(serial number) 'Digilent USB Device' flags: 0x0 type: 0x8 id: 0x4036014 locid: 0x14060

 

FTDI Version: 0x10202

Devices: 1

 1. SN:(serial number) 'Digilent USB Device' flags: 0x2 type: 0x8 id: 0x4036014 locid: 0x1406

 

DMGR Version: 2.8.2

DmgrEnumDevices failed

 

 

 

[RCG]

I have three Macs, all running macOS Sierra: 2011 iMac, 2013 MBP, 2016 MBP. The 2013 MBP loads Waveform 2015 just fine and finds the Analog 2. Neither of the other machines will load, stating "Device Not Found." In both cases where the device is not found it can be seen in the Network tab of System Preferences as "Digilent . . . Device". Its status is "Not Configured" and the OS will not connect to it. The software seems to think it is a modem. On the 2013 MBP where everything connects just fine, it does NOT show up on the Network listing. It does show up in System Information as a Digilent USB Device under USB, but the device also shows up on System Information as a USB device on the two machines that can't find it under Waveform 2015.

FIXED: Sorry, a clean restart of the two uncooperative machines fixed them both. Waveform 2015 now sees the Analog 2 on all three Macs.

 

Edited February 5, 2017 by RCG
Problem resolved.

[Naoshi]

Hi RCG, Thank you for your important information.

But, Though I also let my mac clean restart, the condition is not changed.

WaveForms says "Device not supported" at Wavegen column in Device Manager.

The python program outputs the same messages.

[attila]

@Naoshi 
Could you run the script with the following error code print?
    print "DmgrEnumDevices failed: "+str(dmgr.DmgrGetLastError())
 

@malexander 
Do you have any thoughts why would DmgrEnum fail?

 

 

[Naoshi]

Hi attila,

The error code is the followings:

DMGR Version: 2.8.2

DmgrEnumDevices faild: 3090

On MacBookAir with macOS Sierra version 10.12.3.

[SpacedCowboy]

@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 ?

Edited February 15, 2017 by SpacedCowboy
invoking Attila

[attila]

@malexander do you have any comments for these problems?

[SpacedCowboy]

@attila, @malexander

So, it's been about a week. Has there been any progress ?

[bentwookie]

They don't care. Return your scope while you can.

[malexander]

@Naoshi

I was checking this thread regularly for a few days and then got distracted and forgot about it. Anyway, ERC 3090 means that there was an error while initializing DPCOMM. There are a number of reasons why this could happen. Thankfully there is a way to enable an error log. Can you please do the following:

1. Execute "export ADEPT_RT_LOGDETAIL=1"

2. Execute "export ADEPT_RT_LOGFILE=~/adept_erc.log"

3. Re-run your modified version of digi_enum.py and post the output of the log file here.

Thanks,

Michael

 

[bentwookie]

1 hour ago, malexander said:

@Naoshi

I was checking this thread regularly for a few days and then got distracted and forgot about it. Anyway, ERC 3090 means that there was an error while initializing DPCOMM. There are a number of reasons why this could happen. Thankfully there is a way to enable an error log. Can you please do the following:

1. Execute "export ADEPT_RT_LOGDETAIL=1"

2. Execute "export ADEPT_RT_LOGFILE=~/adept_erc.log"

3. Re-run your modified version of digi_enum.py and post the output of the log file here.

Thanks,

Michael

 

You've asked for and received a number of these. What's the plan? Is there a bug? Is there a new version? What are the "number of reasons this can happen"?

[Naoshi]

1 hour ago, malexander said:

@Naoshi

I was checking this thread regularly for a few days and then got distracted and forgot about it. Anyway, ERC 3090 means that there was an error while initializing DPCOMM. There are a number of reasons why this could happen. Thankfully there is a way to enable an error log. Can you please do the following:

1. Execute "export ADEPT_RT_LOGDETAIL=1"

2. Execute "export ADEPT_RT_LOGFILE=~/adept_erc.log"

3. Re-run your modified version of digi_enum.py and post the output of the log file here.

Thanks,

Michael

 

Hi Michael,

I have the following message in the generated log file:

 

 

System Time     Process     Thread        ERC     ERC String                  Message

1751613013      9038        1407363402352003080    ercInternalError            USBC::FInit() failed to get firmware image path

1751613013      9038        1407363402352003080    ercInternalError            DPCOMM DllInit failed to init USBC

1751613026      9038        1407363402352003090    ercDpcommInitFailed         DPCOMM library initialization failed

[malexander]

27 minutes ago, Naoshi said:

Hi Michael,

I have the following message in the generated log file:

 

 

System Time     Process     Thread        ERC     ERC String                  Message

1751613013      9038        1407363402352003080    ercInternalError            USBC::FInit() failed to get firmware image path

1751613013      9038        1407363402352003080    ercInternalError            DPCOMM DllInit failed to init USBC

1751613026      9038        1407363402352003090    ercDpcommInitFailed         DPCOMM library initialization failed

Hi Naoshi,

Can you please check to see if  this directory exists: "/Library/Frameworks/dwf.framework/Resources/digilent/adept/data/firmware" ? It should exist and contain the following files:

FTDIFW_50_00000011_00000000_010A.dylib FX2FW_01_00000001_00000000_030A.HEX    FX2FW_09_0000000D_00000000_030A.HEX
FTDIFW_51_00000001_00000000_010A.dylib FX2FW_01_00000010_00000000_030A.HEX    FX2FW_0A_0000001D_00000000_030A.HEX
FTDIFW_52_00000011_00000000_010B.dylib FX2FW_02_00000001_00000000_030A.HEX    FX2FW_0B_00000000_0000000D_030A.HEX
FTDIFW_53_00000001_00000000_010A.dylib FX2FW_02_00000004_00000000_030A.HEX    FX2FW_0C_0000000D_00000000_030A.HEX
FTDIFW_54_00000013_00000000_010B.dylib FX2FW_03_00000011_00000000_030A.HEX    FX2FW_0D_0000000D_00000000_030A.HEX
FTDIFW_55_00000811_00000000_010A.dylib FX2FW_04_00000005_00000000_030A.HEX    FX2FW_0E_0000000D_00000000_030A.HEX
FTDIFW_56_00000811_00000000_010A.dylib FX2FW_05_0000000D_00000000_030A.HEX    FX2FW_0F_00000000_0000000D_030A.HEX
FTDIFW_57_00000001_00000000_010A.dylib FX2FW_06_0000001D_00000000_030A.HEX
FTDIFW_60_00000000_00000801_010A.dylib FX2FW_08_0000000D_00000000_030A.HEX

Assuming that directory does exist one additional thing to try doing is executing "export DIGILENT_DATA_DIR=/Library/Frameworks/dwf.framework/Resources/digilent/adept/data" and then re-running the python script. It would be odd if that worked, and if it does then it would suggest that there's a bug in code that searches for the location of the data directory and for some reason or another it doesn't manifest on the Mac's that we have here.

Thanks,
Michael

 

[Naoshi]

Hi, Michael,

 

My Mac has only the directory "/Applications/Waveforms.app/Contents/Frameworks/dwf.framework/Resources/digilent/adept/data/firmware"

in stead of "/Library/Frameworks/dwf.framework/Resources/digilent/adept/data/firmware" .

It does not have the directory "/Library/Framewors/dwf.framework.

All of the listed files are contained in the directory.

[Naoshi]

2 hours ago, malexander said:

Hi Naoshi,

Can you please check to see if  this directory exists: "/Library/Frameworks/dwf.framework/Resources/digilent/adept/data/firmware" ? It should exist and contain the following files:

FTDIFW_50_00000011_00000000_010A.dylib FX2FW_01_00000001_00000000_030A.HEX    FX2FW_09_0000000D_00000000_030A.HEX
FTDIFW_51_00000001_00000000_010A.dylib FX2FW_01_00000010_00000000_030A.HEX    FX2FW_0A_0000001D_00000000_030A.HEX
FTDIFW_52_00000011_00000000_010B.dylib FX2FW_02_00000001_00000000_030A.HEX    FX2FW_0B_00000000_0000000D_030A.HEX
FTDIFW_53_00000001_00000000_010A.dylib FX2FW_02_00000004_00000000_030A.HEX    FX2FW_0C_0000000D_00000000_030A.HEX
FTDIFW_54_00000013_00000000_010B.dylib FX2FW_03_00000011_00000000_030A.HEX    FX2FW_0D_0000000D_00000000_030A.HEX
FTDIFW_55_00000811_00000000_010A.dylib FX2FW_04_00000005_00000000_030A.HEX    FX2FW_0E_0000000D_00000000_030A.HEX
FTDIFW_56_00000811_00000000_010A.dylib FX2FW_05_0000000D_00000000_030A.HEX    FX2FW_0F_00000000_0000000D_030A.HEX
FTDIFW_57_00000001_00000000_010A.dylib FX2FW_06_0000001D_00000000_030A.HEX
FTDIFW_60_00000000_00000801_010A.dylib FX2FW_08_0000000D_00000000_030A.HEX

Assuming that directory does exist one additional thing to try doing is executing "export DIGILENT_DATA_DIR=/Library/Frameworks/dwf.framework/Resources/digilent/adept/data" and then re-running the python script. It would be odd if that worked, and if it does then it would suggest that there's a bug in code that searches for the location of the data directory and for some reason or another it doesn't manifest on the Mac's that we have here.

Thanks,
Michael

 

Moreover, I executed digi_enum.py.

 

Before export "DIGILENT_DATA”:

--------------------------------------

dyld: warning, LC_RPATH @executable_path/../Frameworks in /Applications/Waveforms.app/Contents/Frameworks/dwf.framework/dwf being ignored in restricted program because of @executable_path

 

Digilent FTDI Enumeration library loaded

Devices: 1

 1. SN:(serial number) 'Digilent USB Device' flags: 0x0 type: 0x8 id: 0x4036014 locid: 0x140b0

 

FTDI Version: 0x10202

Devices: 1

 1. SN:(serial number) 'Digilent USB Device' flags: 0x2 type: 0x8 id: 0x4036014 locid: 0x140b

 

DMGR Version: 2.8.2

DmgrEnumDevices failed: 3090

-------------------------------

 

After export :

-------------------------------

dyld: warning, LC_RPATH @executable_path/../Frameworks in /Applications/Waveforms.app/Contents/Frameworks/dwf.framework/dwf being ignored in restricted program because of @executable_path

 

Digilent FTDI Enumeration library loaded

Devices: 1

 1. SN:(serial number) 'Digilent USB Device' flags: 0x0 type: 0x8 id: 0x4036014 locid: 0x140c0

 

FTDI Version: 0x10202

Devices: 1

 1. SN: '' flags: 0x1 type: 0x3 id: 0x0 locid: 0x0

 

DMGR Version: 2.8.2

DmgrEnumDevices failed: 3090

-------------------------------------

The serial number in the second part of the messages is seemed to be disappeared.

 

[malexander]

14 hours ago, Naoshi said:

Hi, Michael,

 

My Mac has only the directory "/Applications/Waveforms.app/Contents/Frameworks/dwf.framework/Resources/digilent/adept/data/firmware"

in stead of "/Library/Frameworks/dwf.framework/Resources/digilent/adept/data/firmware" .

It does not have the directory "/Library/Framewors/dwf.framework.

All of the listed files are contained in the directory.

Hi Naoshi,

It sounds like you don't have the dwf framework installed, which may explain why it can't find the Digilent data directory or the firmware images directory. Presently we perform the following search when attempt to locate the data directory:

1. Check to see if the path to the data directory was specified by the "DIGILENT_DATA_DIR" environment variable. If this path exists then it is returned as the path to the data directory.
2. Check to see if the "@executable_path/../Resources/digilent/adept/data/" directory exists. If this directory exists then assume it contains the appropriate data files.
3. Check to see if the "@executable_path/../Frameworks/dwf.framework/Resources/digilent/adept/data/" directory exists. If this directory exists then assume it contains the appropriate data files.
4. Check to see if the "/Library/Frameworks/dwf.framework/Resources/digilent/adept/data/" directory exists. If this directory exists then assume it contains the appropriate data files.
5. Check to see if the "/usr/local/share/digilent/adept/data/" directory exists. If this directory exists then assume it contains the appropriate data files.

Since this python script is not executing the WaveForms application bundle paths 2 and 3 that I listed above won't be found and the expectation is that we are going to fall back to path 4. However, if the dwf framework isn't installed then that path won't be found either. We don't expect any external users to have the software installed in their /usr/local directory and that path is a fallback used for internal testing.

Can you please mount the waveforms dmg and then drag dwf.framework into both the "Frameworks" and "SDK" folders to the right of it? After that try re-running the python script. Be sure that the environment variables for generating the log files are still set.

Thanks,
Michael

[Naoshi]

22 minutes ago, malexander said:

Hi Naoshi,

It sounds like you don't have the dwf framework installed, which may explain why it can't find the Digilent data directory or the firmware images directory. Presently we perform the following search when attempt to locate the data directory:

1. Check to see if the path to the data directory was specified by the "DIGILENT_DATA_DIR" environment variable. If this path exists then it is returned as the path to the data directory.
2. Check to see if the "@executable_path/../Resources/digilent/adept/data/" directory exists. If this directory exists then assume it contains the appropriate data files.
3. Check to see if the "@executable_path/../Frameworks/dwf.framework/Resources/digilent/adept/data/" directory exists. If this directory exists then assume it contains the appropriate data files.
4. Check to see if the "/Library/Frameworks/dwf.framework/Resources/digilent/adept/data/" directory exists. If this directory exists then assume it contains the appropriate data files.
5. Check to see if the "/usr/local/share/digilent/adept/data/" directory exists. If this directory exists then assume it contains the appropriate data files.

Since this python script is not executing the WaveForms application bundle paths 2 and 3 that I listed above won't be found and the expectation is that we are going to fall back to path 4. However, if the dwf framework isn't installed then that path won't be found either. We don't expect any external users to have the software installed in their /usr/local directory and that path is a fallback used for internal testing.

Can you please mount the waveforms dmg and then drag dwf.framework into both the "Frameworks" and "SDK" folders to the right of it? After that try re-running the python script. Be sure that the environment variables for generating the log files are still set.

Thanks,
Michael

Hi, Michael,

I executed the following steps:

1. I downloaded "digilent.waveforms_v.3.4.7.dmg"

2. I had my mac mount the file.

3. Then, the installer of waveforms2015 was popped up.

4. "To install,..." message is written in the upper side of the finder window, and "Runtime and SDK..." message is also written in the lower side.

5. I don't know where the SDK directory is. But I followed the message in the lower side. That is, I only dragged the "dwf.framework" icon into /Library/Framework folder.

6. I started the Terminal app.

7. I executed the digital_enum.py in the Terminal, then, I have the following messages:

dyld: warning, LC_RPATH @executable_path/../Frameworks in /Library/Frameworks/dwf.framework/dwf being ignored in restricted program because of @executable_path

 

Digilent FTDI Enumeration library loaded

Devices: 1

 1. SN:(serial number) 'Digilent USB Device' flags: 0x0 type: 0x8 id: 0x4036014 locid: 0x140e0

 

FTDI Version: 0x10202

Devices: 1

 1. SN:(serial number) 'Digilent USB Device' flags: 0x2 type: 0x8 id: 0x4036014 locid: 0x140e

 

DMGR Version: 2.8.2

Devices: 1

 1. SN:(serial number) 'Analog Discovery 2' PDID: 0x40300360

 

DWF Version: 3.4.7

Devices: 1

 1. SN:(serial number) 'Analog Discovery 2'

8. Hmm, It goes well??

9. I executed Waveforms2015. Then, finally it could recognize my Analog Discovery 2.

10. First of all, Scope, Wavegen, and Supplies work normally!!!!

Thank you, Michael. 

The message of the installer should still be improved.

[malexander]

12 minutes ago, Naoshi said:

Hi, Michael,

I executed the following steps:

1. I downloaded "digilent.waveforms_v.3.4.7.dmg"

2. I had my mac mount the file.

3. Then, the installer of waveforms2015 was popped up.

4. "To install,..." message is written in the upper side of the finder window, and "Runtime and SDK..." message is also written in the lower side.

5. I don't know where the SDK directory is. But I followed the message in the lower side. That is, I only dragged the "dwf.framework" icon into /Library/Framework folder.

6. I started the Terminal app.

7. I executed the digital_enum.py in the Terminal, then, I have the following messages:

dyld: warning, LC_RPATH @executable_path/../Frameworks in /Library/Frameworks/dwf.framework/dwf being ignored in restricted program because of @executable_path

 

Digilent FTDI Enumeration library loaded

Devices: 1

 1. SN:(serial number) 'Digilent USB Device' flags: 0x0 type: 0x8 id: 0x4036014 locid: 0x140e0

 

FTDI Version: 0x10202

Devices: 1

 1. SN:(serial number) 'Digilent USB Device' flags: 0x2 type: 0x8 id: 0x4036014 locid: 0x140e

 

DMGR Version: 2.8.2

Devices: 1

 1. SN:(serial number) 'Analog Discovery 2' PDID: 0x40300360

 

DWF Version: 3.4.7

Devices: 1

 1. SN:(serial number) 'Analog Discovery 2'

8. Hmm, It goes well??

9. I executed Waveforms2015. Then, finally it could recognize my Analog Discovery 2.

10. First of all, Scope, Wavegen, and Supplies work normally!!!!

Thank you, Michael. 

The message of the installer should still be improved.

Hi Naoshi,

I'm glad to hear that it's finally working. I understand why the python script wasn't previously working but I'm still not sure why the WaveForms application bundle didn't work prior to you installing the dwf.framework. The Runtime should have been able to find those data files in the application bundle without the dwf.frame being installed. It works correctly on my system. I will continue to research this problem and see why it doesn't work for some people.

Thanks,
Michael

[SpacedCowboy]

@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

 

Edited February 23, 2017 by SpacedCowboy

[malexander]

1 hour ago, SpacedCowboy said:

@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

 

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?

Thanks,
Michael

 

 

 

[SpacedCowboy]

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

Edited February 24, 2017 by SpacedCowboy

[Krizzle]

@malexander, @attila, this still isn't working on my Mac. I'm feeling swindled of $300 for a product that was advertised to work on MacOS. 

What can I do here? I've installed the latest WaveForms 2015 (3.6.8) and its FTDI driver package, but the app still says "No Device Detected"

[lstubbol]

@Krizzle Dude I had this same problem last spring. There is no fix. AD2 Will Never work on macOS. Yes it's messed up, yes they should they fix it. They will not. You need to install Windows either via Boot Camp or in a virtual machine. I would recommend Boot Camp because it is the easiest. Look it up. It's really easy, there are tons of tutorials and it works perfectly. There are a bunch of virtual machines out there but they are challenging to set up and maintain(at least for me anyway). 

If you have no idea what I am talking about, Boot Camp is an app already on your computer that enables you to partition your hard drive and install another operating system. After it is set up you just shut down your computer, hold down a button after you turn it back on (left fn maybe? not sure it's been a while) and a menu will pop up asking you which operating system you want to boot into. 

Boot Camp is totally legit native Mac software, and in my opinion it is by far the simplest method to get you back to your analog circuits course (unless you just bought it for fun). 

[attila]

Hi @Krizzle, @lstubbol

Sorry to hear that you have problems with AD2 under OS-X.
It is working on several Macbooks in our office and also on most of the client machines.

Please try the following software digilent.waveforms_v3.6.8-2.dmg
The v3.6.8 fixes an OS-X USB driver filter update issue.
The v.3.6.8-2 includes the latest USB library and Adept Runtime (fixing some compatibility issue with 3rd party libraries) supporting OS-X 10.10 and newer.

After the installation of the USB driver from the waveforms disk image please RESTART the Mac having the device DISCONNECTED !!!
Also make sure the device is not attached to any virtual machine.

Please let us know what you find.