search

thomaschaaf / node-ftdi

FTDI bindings for Node.js
MIT License
45 stars 39 forks source link

node-ftdi module throws error: libftd2xx.so: cannot open shared object file #6

Closed sim-san closed 10 years ago

sim-san commented 10 years ago

I test node-ftdi on my raspi

pi@raspberrypi ~/dmx $ dmx-web -c /home/pi/dmx/dmx-web.conf info - socket.io started

/usr/local/lib/node_modules/dmx/node_modules/ftdi/node_modules/bindings/bindings.js:83 throw e ^ Error: libftd2xx.so: cannot open shared object file: No such file or directory at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Module.require (module.js:364:17) at require (module.js:380:17) at bindings (/usr/local/lib/node_modules/dmx/node_modules/ftdi/node_modules/bindings/bindings.js:76:44) at Object. (/usr/local/lib/node_modules/dmx/node_modules/ftdi/index.js:3:31) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12)

sim-san commented 10 years ago

some information

pi@raspberrypi ~/dmx $ sudo ldconfig -p | grep ftd libftd2xx.so (libc6) => /usr/local/lib/libftd2xx.so pi@raspberrypi ~/dmx $ ldd /usr/local/lib/libftd2xx.so not a dynamic executable pi@raspberrypi ~/dmx $ readelf -h /usr/local/lib/libftd2xx.so ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: DYN (Shared object file) Machine: ARM Version: 0x1 Entry point address: 0x666c Start of program headers: 52 (bytes into file) Start of section headers: 198900 (bytes into file) Flags: 0x5000002, has entry point, Version5 EABI Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 6 Size of section headers: 40 (bytes) Number of section headers: 30 Section header string table index: 27 pi@raspberrypi ~/dmx $

adrai commented 10 years ago

Sorry no raspi experience... :-(

mpiraux commented 10 years ago

I've been facing this exact same issue yesterday. And after a quick googling, I found a topic on the RPi forum about that (http://www.raspberrypi.org/forums/viewtopic.php?f=28&t=17009). The solution for me was to download the driver given by anat on the 12th post (http://www.mediafire.com/?7ioe9ear30yhn73). I also placed it in /usr/lib/ as well as /usr/local/lib, just because you never know ;) As I understood the problem, it was rather an incorrect driver than a missing driver problem. Anyway this fixed my issue and I hope it will fix yours!