albert

Members
  • Content Count

    20
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by albert

  1. Hi! Very late, but I finally got around to bringing my device to work to test the new driver.. It works fine now, thanks!
  2. I'm running Sierra 10.12.4 on a new 15" MacBook Pro (the new touch bar model)
  3. Hi! I tried what you proposed - no output as expected: ➜ cert syslog | grep Digilent NOTE: Most system logs have moved to a new logging system. See log(1) for more information. However, the output is the same also after attaching the Analog Discovery 2?
  4. Hi Michael, thanks for the info! I noticed both devices appear in system_profiler without unloading the driver. Does that tell you anything? Both devices have the same Vendor ID: ➜ ~ system_profiler SPUSBDataType | grep Digilent -A 7 Digilent USB Device: Product ID: 0x6014 Vendor ID: 0x0403 (Future Technology Devices International Limited) Version: 9.00 Serial Number: 210321A18D4C Speed: Up to 480 Mb/sec Manufacturer: Digilent Location ID: 0x14114000 / 32 Current Available (mA): 500 Current Required (mA): 0 Extra Operating Current (mA): 0 ➜ ~ system_profiler SPUSBDataType | grep FTDI -C 5 Product ID: 0x6010 Vendor ID: 0x0403 (Future Technology Devices International Limited) Version: 7.00 Speed: Up to 480 Mb/sec Manufacturer: FTDI Location ID: 0x14120000 / 31 Current Available (mA): 500 Current Required (mA): 500 Extra Operating Current (mA): 0
  5. Hello, I have an issue similar to this one, but not related to USB hubs: Basically, after I installed Waveforms and the USB driver, I can no longer connect to the serial USB device that I am trying to debug! I am forced to kextunload and then kextload again to make them connect: ➜ ~ ls /dev/tty.* /dev/tty.Bluetooth-Incoming-Port /dev/tty.lpss-serial1 /dev/tty.lpss-serial2 ➜ ~ sudo kextunload /Library/Extensions/DigilentFtdiDriver.kext ➜ ~ ls /dev/tty.* /dev/tty.Bluetooth-Incoming-Port /dev/tty.lpss-serial1 /dev/tty.lpss-serial2 /dev/tty.usbserial-1412A /dev/tty.usbserial-1412B ➜ ~ sudo kextload /Library/Extensions/DigilentFtdiDriver.kext ➜ ~ ls /dev/tty.* /dev/tty.Bluetooth-Incoming-Port /dev/tty.lpss-serial1 /dev/tty.lpss-serial2 /dev/tty.usbserial-1412A /dev/tty.usbserial-1412B Is there any way to fix this? The other devices are using the generic FTDI VCP driver. My computer is the latest MacBook Pro 15".
  6. I think you are right and that the changes are a good idea. I guess you thought of this already but alternatively, perhaps you can detect what version of the library you found and keep looking if it is too old? I did not try any of my other software that might be using the other driver (I guess it could be Arduino/Energia) but I guess something will probably break if I keep it renamed My /usr/local/lib/ has both 0.1.7 and 1.2.2 and uses a symlink that points to 0.1.7. Since you say 1.2.2 should work I will do some experimenting with changing the symlink to point to that version instead in case I find issues with some other software. (Before saw your latest message I was going to ask for a strategy for running Waveforms along with other software that uses that driver..) Finally, thanks a lot for guiding me Michael! You made it really difficult for me to be mad at Digilent for having to spend two weeks just to get this up and running
  7. OH THE JOY!!! I just got back home and was going to start fiddling with this again and it just worked! I did reboot last night but maybe not after changing back the name of the correct library.. Anyway, it also started working in Virtualbox. So just to be clear, the fix was renaming my extra /usr/local/lib/libftd2xx.dylib to something else (and possibly rebooting/waiting 24h ).
  8. I think I am on to something! I figured the missing log file made no sense, so what if there was another libftd2xx.dylib in my path? There was! ~ find / -name "libftd2xx.dylib" -print 2>/dev/null /Library/Frameworks/dwf.framework/Versions/A/Frameworks/libftd2xx.dylib /usr/local/lib/libftd2xx.dylib So I did some more digging: ~ diff /Library/Frameworks/dwf.framework/Versions/A/Frameworks/libftd2xx.dylib /usr/local/lib/libftd2xx.dylib Binary files /Library/Frameworks/dwf.framework/Versions/A/Frameworks/libftd2xx.dylib and /usr/local/lib/libftd2xx.dylib differ ~ ll /Library/Frameworks/dwf.framework/Versions/A/Frameworks/libftd2xx.dylib -rwxr-xr-x@ 1 albert wheel 541K 13 Nov 16:06 /Library/Frameworks/dwf.framework/Versions/A/Frameworks/libftd2xx.dylib ~ ll /usr/local/lib/libftd2xx.dylib lrwxr-xr-x 1 root admin 36B 26 Jun 2014 /usr/local/lib/libftd2xx.dylib -> /usr/local/lib/libftd2xx.0.1.7.dylib ~ ll /usr/local/lib/libftd2xx.0.1.7.dylib -rwxr-xr-x@ 1 root admin 221K 26 Jun 2014 /usr/local/lib/libftd2xx.0.1.7.dylib ~ ll /usr/local/lib/libftd2xx* -rwxr-xr-x@ 1 root admin 221K 26 Jun 2014 libftd2xx.0.1.7.dylib -rwxr-xr-x@ 1 root admin 515K 26 Jun 2014 libftd2xx.1.2.2.dylib lrwxr-xr-x 1 root admin 36B 26 Jun 2014 libftd2xx.dylib -> /usr/local/lib/libftd2xx.0.1.7.dylib Waveforms still does not find the device without this bastard, but if i rename both files, I now get the error log! ~ cat ~/adept.log System Time Process Thread ERC ERC String Message 3267427782 5777 1231453056000003080 ercInternalError FTDIC::FEnumAndUpdateCache call to ListDevices failed 3267427782 5777 1231453056000003080 ercInternalError FTDIC::FEnum FEnumAndUpdateCache() failed 3267428793 5777 1231453056000003080 ercInternalError FTDIC::FEnumAndUpdateCache call to ListDevices failed 3267428793 5777 1231453056000003080 ercInternalError FTDIC::FEnum FEnumAndUpdateCache() failed 3267430101 5777 1231453066731523080 ercInternalError FTDIC::FEnumAndUpdateCache call to ListDevices failed 3267430101 5777 1231453066731523080 ercInternalError FTDIC::FEnum FEnumAndUpdateCache() failed None of the other dylibs from the framework seem to have duplicates in /usr/local/lib and I am trying to think up a way to pipe all the filenames into find to make sure there arent any elsewhere either.
  9. Yep, tried exactly what you described but do not get a log file! In addition, I tried to run "repair permissions" (apparently in El Capitan, only way to do it is to boot in to safe mode and it will do it automatically). After that did not work I also re-installed the driver again, without success. I also spent some more time on trying to get it working in Virtualbox since the device was functional on my work PC. Apparently you need the VirtualBox Extension Pack to use USB devices. After installing that, Windows now recognizes a device has been plugged in, but the driver does not install correctly and Waveforms still does not detect it. I tried re-installing Waveforms as suggested in some other thread, but it did not help.. The status message below says "This device cannot start. (Code 10)": Edit: Just had a friend test my device on his Macbook and there it works fine..
  10. Doh! I went too quick and did not realize there was a file with such a similar name in that folder.. I went back and renamed libftd2xx.dylib instead. No errors this time but also still no log file though!?
  11. Hi Michael, Sudo did not make any difference either. I also renamed libftd2xx.dylib, just to try and confirm like you said. It did spawn a couple of extra error messages, but no log file! I find this strange since the variables seem to be in place: ~ echo $ADEPT_RT_LOGDETAIL $ADEPT_RT_LOGFILE 1 /Users/albert/adept.log This is starting to get really "interesting" now!
  12. A couple of things I tested today: The device still works on my Windows PC at work. I read somewhere that connecting the device through a USB-hub might help. It did not. Tried running the Device_Enumeration script from the SDK samples: ~ python /Applications/WaveForms.app/Contents/Resources/SDK/samples/py/Device_Enumeration.py DWF Version: 2.9.4 Number of Devices: 0
  13. Hi Michael, thanks for helping me! I am not sure what library you mean, are you are referring to this one? (it seems to be in place..) /Applications/WaveForms.app/Contents/Frameworks/dwf.framework/Versions/A/Frameworks/libftd2xx.dylib I tried running through your steps but it did not generate a log file.. I had to modify step 8 though, "/Applications/WaveForms.app" is the eqivalent of "cd /Applications/WaveForms.app" in the two terminals I tried (iTerm2 and Terminal). To run the program from the command line, I used "open /Applications/WaveForms.app" instead. I also tried starting it from Spotlight like usual. Is this correct or is there another way to launch an app from the terminal?
  14. So I tried a couple more things: Added external 5 V power supply in case my mac was not supplying enough current. No change. Tried installing Waveforms on Windows inside Virtualbox on the same machine. I expected this to work but it did not! Will bring the device back to work tomorrow to confirm it is still functional. (Is it possible to semi-brick it somehow?) Any other ideas on what to try? I was hoping for Virtualbox to be a temporary workaround while waiting for a resolution but for now I'm stuck with a paperweight..
  15. To clarify, the FTDIUSBSerialDriver appeared (in addition to the Digilent driver) after plugging in the device, then disappeared again after a few seconds. I was checking this with $ watch "kextstat | grep -i ftdi" I then tried removing the FTDIUSBSerialDriver kext (temporarily moved it to another folder) and rebooted without the device attached - still nothing
  16. Hi Michael, I get something similar, maybe I have a newer version of the driver (1 vs 1.0.3)? ~ kextstat | grep Digilent 148 0 0xffffff7f82cfe000 0x2000 0x2000 com.digilent.driver.DigilentFtdiDriver (1.0.3) 04D22EC0-C800-389F-A0FD-F0F759897EEE <41 4 3> Do you have a handy command for listing all installed FTDI drivers? From memory, I have installed the drivers included with Energia 0101E0016: EnergiaFTDIDrivers2.2.18.pkg MSP430LPCDC 1.0.3b.pkg http://energia.nu/downloads/downloadv3.php?file=energia-0101E0016-macosx.dmg I also have Arduino 1.0.5 installed, but it does not seem to come with a driver. Edit: I unplugged and plugged the device again and had another look at kextstat. This time it loaded another FTDI driver as well, could this be the issue? 151 0 0xffffff7f82d00000 0x7000 0x7000 com.FTDI.driver.FTDIUSBSerialDriver (2.3) ECC3AF36-431D-370D-86F2-5237785E9CF8 <95 41 5 4 3 1>
  17. Ok, I only tried 3.0.28 since 3.1.5 was not working.. I did several reboots with and without the device attached and also tried installing the FTDI driver again. I must have pressed the refresh button in 3.1.5 at least 100 times.. I probably have some MSP430 Launchpad and Arduino FTDI drivers installed, could they be interfering somehow? I am puzzled since system_profiler seems to indicate the device enumerates correctly and dmesg (despite some errors in the beginning) also seems to indicate the driver is loading like it should(?). Is there anything else I can try to get more information? Is there a way to get debug information from Waveforms or something? Can i run some python script with the SDK? And before anyone asks, yes, I tried it on my Windows work computer and there it works fine..
  18. Hi! Sorry to join the forum on such a sad note but I just got my Analog Discovery 2 and I have the same issue (OSX 10.11.3)! On Waveforms 3.1.5 I get "No device detected", then the list of three DEMO devices. On Waveforms 3.0.28 I get "No device detected", then the Analog Discovery 2 appears on the first line, but in the bottom box all columns are empty except "Wavegen" where it says "Device not su...". Clicking "Select" does nothing, the device explorer remains open. I tried uploading a screenshot but the forum seems broken as well ("There was a problem processing the uploaded file. Please contact us for assistance. ").. Here are a few things I have tried, not sure if Waveforms or my system is to blame (any ideas??): $ sudo kextutil -t -n /Library/Extensions/DigilentFtdiDriver.kext /Library/Extensions/DigilentFtdiDriver.kext appears to be loadable (including linkage for on-disk libraries). $ sudo kextunload -b com.apple.driver.AppleUSBFTDI (kernel) Kext com.apple.driver.AppleUSBFTDI not found for unload request. Failed to unload com.apple.driver.AppleUSBFTDI - (libkern/kext) not found. $ system_profiler SPUSBDataType | grep Digilent -A 7 2016-02-01 21:15:48.860 system_profiler[5798:47726] SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x06110000 2016-02-01 21:15:48.861 system_profiler[5798:47726] SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x06100000 2016-02-01 21:15:48.863 system_profiler[5798:47726] SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x04500000 2016-02-01 21:15:48.864 system_profiler[5798:47726] SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x04600000 Digilent USB Device: Product ID: 0x6014 Vendor ID: 0x0403 (Future Technology Devices International Limited) Version: 9.00 Serial Number: 210321A18D4C Speed: Up to 480 Mb/sec Manufacturer: Digilent Location ID: 0x24100000 / 2 Current Available (mA): 1000 Current Required (mA): 0 Extra Operating Current (mA): 0 USB 2.0 Bus: After plugging in and out a few times: $ sudo dmesg | tail Sandbox: cp(1802) System Policy: deny(1) file-write-create /usr/lib/libdjtg.dylib Sandbox: cp(1802) System Policy: deny(1) file-write-create /usr/lib/libdmgr.dylib Sandbox: cp(1802) System Policy: deny(1) file-write-create /usr/lib/libdmgt.dylib Sandbox: cp(1802) System Policy: deny(1) file-write-create /usr/lib/libdpcomm.dylib Sandbox: cp(1802) System Policy: deny(1) file-write-create /usr/lib/libdpcutil.dylib Sandbox: cp(1802) System Policy: deny(1) file-write-create /usr/lib/libdpio.dylib Sandbox: cp(1802) System Policy: deny(1) file-write-create /usr/lib/libdpti.dylib Sandbox: cp(1802) System Policy: deny(1) file-write-create /usr/lib/libdspi.dylib Sandbox: cp(1802) System Policy: deny(1) file-write-create /usr/lib/libdstm.dylib Sandbox: cp(1802) System Policy: deny(1) file-write-create /usr/lib/libdtwi.dylib Sandbox: cp(1802) System Policy: deny(1) file-write-create /usr/lib/libdwf.dylib Sandbox: cp(1802) System Policy: deny(1) file-write-create /usr/lib/libftd2xx.dylib Sandbox: cp(1802) System Policy: deny(1) file-write-create /usr/lib/libjtsc.dylib Sandbox: cp(1802) System Policy: deny(1) file-write-create /usr/lib/libusb-1.0.0.dylib Sandbox: mkdir(1804) System Policy: deny(1) file-write-create /usr/share/digilent Sandbox: cp(1806) System Policy: deny(1) file-write-create /usr/share/digilent Sandbox: cp(1806) System Policy: deny(1) file-write-create /usr/share/digilent Sandbox: cp(1926) System Policy: deny(1) file-write-create /usr/lib/libdmgr.dylib Sandbox: cp(1926) System Policy: deny(1) file-write-create /usr/lib/libdmgt.dylib Sandbox: cp(1926) System Policy: deny(1) file-write-create /usr/lib/libdpcomm.dylib Sandbox: cp(1926) System Policy: deny(1) file-write-create /usr/lib/libdpcutil.dylib Sandbox: cp(1926) System Policy: deny(1) file-write-create /usr/lib/libdpio.dylib Sandbox: cp(1926) System Policy: deny(1) file-write-create /usr/lib/libdpti.dylib Sandbox: cp(1926) System Policy: deny(1) file-write-create /usr/lib/libdspi.dylib Sandbox: cp(1926) System Policy: deny(1) file-write-create /usr/lib/libdstm.dylib Sandbox: cp(1926) System Policy: deny(1) file-write-create /usr/lib/libdtwi.dylib Sandbox: cp(1926) System Policy: deny(1) file-write-create /usr/lib/libdwf.dylib Sandbox: cp(1926) System Policy: deny(1) file-write-create /usr/lib/libftd2xx.dylib Sandbox: cp(1926) System Policy: deny(1) file-write-create /usr/lib/libjtsc.dylib Sandbox: cp(1926) System Policy: deny(1) file-write-create /usr/lib/libusb-1.0.0.dylib Sandbox: mkdir(1928) System Policy: deny(1) file-write-create /usr/share/digilent Sandbox: cp(1930) System Policy: deny(1) file-write-create /usr/share/digilent Sandbox: cp(1930) System Policy: deny(1) file-write-create /usr/share/digilent hfs: mounted WaveForms on device disk2s1 ignored is_io_service_close(0x100000398,IOHIDParamUserClient) Digilent Stopping Digilent USB Device: not registry member at registerService() 001690.596267 AppleUSBLegacyRoot@: AppleUSBLegacyRoot::usbServiceCallback: unable to notify matching done for usbService <ptr> (Digilent USB Device) Digilent probe8: initial probe score = 100000 Digilent probe: Manufacturer Name = Digilent Digilent probe8: final probe score = 100001 Digilent Starting Digilent Stopping Digilent probe8: initial probe score = 100000 Digilent probe: Manufacturer Name = Digilent Digilent probe8: final probe score = 100001 Digilent Starting I am confused - half of this seems quite correct, still other stuff seems badly wrong. Unsure where to proceed from here, would really appreciate any guidance..