Jump to content

zaxxon

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

zaxxon's Achievements

Newbie

Newbie (1/4)

0

Reputation

  1. @malexander @attila So, the saga continues. Recent news : RMA'ed the device and got another. I bought another powered USB hub. Still not working. Dug up an old laptop, put linux on it. Device verified as working - at least in linux. Spent more time clicking in the google machine. Someone posted this as a diagnostic maneuver : export ADEPT_RT_LOGDETAIL=1 export ADEPT_RT_LOGFILE=~/adept_erc.log python digi_enum.py 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:210321A96879 'Digilent USB Device' flags: 0x0 type: 0x8 id: 0x4036014 locid: 0x140e0 FTDI Version: 0x10202 Devices: 1 1. SN:210321A96879 'Digilent USB Device' flags: 0x2 type: 0x8 id: 0x4036014 locid: 0x140e DMGR Version: 2.8.4 Devices: 1 1. SN:210321A96879 'Analog Discovery 2' PDID: 0x40300360 DWF Version: 3.10.9 Devices: 1 1. SN:210321A96879 'Analog Discovery 2' cat adept_erc.log System Time Process Thread ERC ERC String Message 2330798318 4468 4517828032 1 ercNotSupported FTDIC::FGetInfo unsupported device attribute Does that error message mean anything to anyone??
  2. Sorry for the confusion. The comment about parallels was posted by a different user. I do not have that installed. Thanks.
  3. I do not have /Library/Extensions/ DigilentFtdiDriver.kext. I do have /Library/Extensions/FTDIUSBSerialDriver.kext/ So, I deleted that - and restarted. Still not working. Thanks.
  4. I do not have any devices attached. I have in the past, and have installed drivers from FTDI on a few occasions.
  5. Thanks for the input. FWIW, I have used various development boards with FTDI chips over the years. I am sure I have installed drivers. I did install Waveforms 3.9.1 and the dwf.framework. Not the DigilentFtdiDriver.pkg. I have not tried to access the device through any other application - with the exception of the MacOS System Report to review USB devices. Here is the output from the digi_enum.py script : 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:210321AA28F7 'Digilent USB Device' flags: 0x0 type: 0x8 id: 0x4036014 locid: 0x141b0 FTDI Version: 0x10202 Devices: 1 1. SN: '' flags: 0x1 type: 0x3 id: 0x0 locid: 0x0 DMGR Version: 2.8.4 Devices: 0 DWF Version: 3.9.1 Devices: 0 Run as user or sudo - same result. I am not sure why, but with the powered USB hub the device is not seen by the OS (or the script). Those USB ports are otherwise functional. Thanks, Doug
  6. Same issue here. Same OS. Same problem. I tried a powered USB hub - no go. The device is recognized by the os FWIW. Thanks for any help.
×
×
  • Create New...