OUR NETWORK:TiVoCommunity TechLore MyOpenRouter Dijit Community MediaSmart Home See all... About UsAdvertiseContact Us

 
Learn about scoring Forum's Raw Score: 317180.0
January 9, 2010 06:25 PM

Categories: PogoPlug Development

Rating (0 votes)
  • 1
  • 2
  • 3
  • 4
  • 5
Rate This!

Member Avatar

steveo

Member
Joined: 01/08/2010

Anyone have some advice as to how I'd go about getting my usb ftdi device supported on the plug? I image the OpenPlug os would have this seeing as it's built in to most modern kernels but there seems to be alot of warnings posted on this forum about trying to use OpenPlug on the pink boxes...

Thanks for your advice in advance.

Discussion:    Add a Comment | Comments 1-14 of 14 | Latest Comment

January 9, 2010 9:24 PM

Steveo, the v2 Pink applications are almost ready to launch. You'll need a spare USB drive to install applications on.

January 10, 2010 8:43 PM

great. Let me know as soon as it's ready.

Out of curiosity do you know if it will also have ssh binaries? (not sshd, but outgoing ssh capability?). Thanks again. I will test it the moment it becomes available.

February 27, 2010 4:51 PM

I have installed OpenPogo as per the how-to s in this forum, but I am not able to recognize my FTDI device...

My understanding is that FTDI support is built into modern kernels, but clearly OpenPogo does not actually implement this. Any help?

February 27, 2010 5:16 PM

I should have looked better at the ipkg list (under 'l' instead of 'f')
ipkg install libftdi works...

February 27, 2010 5:22 PM

alright so ipkg install libftdi but the device is not detected (no /dev/ttyUSB* created). What now?

March 9, 2010 8:58 PM

The Pogoplug doesn't automatically make dev entires - this is a pain in the ass. Google around how to "mknod" manually for a serial device. Warning: it will suck trying to find an answer.

Dontcha just love the streamlined firmware on the plugs? Full of win.

November 28, 2010 5:19 PM

Did you ever get it working?

ipkg install libftdi
ipkg install libusb
mknod /dev/ttyUSB0 c 188 0

but when I run:
dmesg |grep tty

I get only:
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 ro
[ 0.900000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[ 0.910000] serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A

What am I missing?

Thanks

January 25, 2011 2:09 PM

I am almost getting the USB device recognised.
I have compiled up various usb modules and loaded them into the kernel with insmod.

I can see my arduino board under /sys/bus/usb/devices/1-1.3 and if I "cat manufacturer" and product I can see that it is recognised. The dev in that directory says that it is on device 189:16 and not the 188:16 which would be usb serial.

January 25, 2011 2:11 PM

I am almost getting there - I can see my Arduino board under /sys/bus/usb/devices/1-1.3 and the dev under there says it is on 189:16 which is not the ttyUSB.

Most frustrating

January 25, 2011 2:36 PM

I can now read messages from my Arduino. I had to compile the cdc_acm module and install that.

dmesg then said:-

[630116.930000] usb 1-1.3: new full speed USB device using ehci_marvell and address 18
[630117.030000] usb 1-1.3: configuration #1 chosen from 1 choice
[630117.030000] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device

I can see in /proc/devices that ACM is 166

so I ran:-
mknod /dev/test c 166 0

and then

cat < /dev/test

and it displayed the temperature readings coming from my arduino.

January 26, 2011 12:26 PM

Hi USBHacker,

This is very good news. I have another FTDI device on my short term list and after that I want to dive into Arduino as well.

A few messages back you say: "I am almost getting the USB device recognised. I have compiled up various usb modules and loaded them into the kernel with insmod."

Can you give an overview and some instructions of what you have been building? Maybe even upload the binaries to a file share service?

That could save me and others lots of time.

Thanks!

March 14, 2011 9:41 PM updated: March 14, 2011 9:44 PM

Ditto on the instructions, pretty please.

I picked up a pogoplug pro to serve as a data repo for stuff coming out of an arduino project. I can see the arduino on usb 189.# so the story is hanging together. Please forgive the ignorant question -- I haven't hacked around inside the kernel much since 2.2 days -- shouldn't I be able to configure adding cdc_acm and build the kernel from downloaded straight from pogo? Then can I just drop the module into the right spot under /sys and do an insmod cdc_acm followed by a mknod? I'm trying to avoid major surgery on the pogo unless I really have to. After a couple hours of having the pogo, it seems to be a cute little device.

March 15, 2011 9:40 AM

With a Pro, this will be slightly more complicated. But in theory, this model of a process should function.

May 18, 2011 2:11 AM

Hi USBHacker,
I have a device with FTDI chip and I tried to copy and compile ftdi_sio.tar with make cmd but it failed and I found ftdi_sio.o and try to insmod but the system says the ftdi_sio.o file invalid. Can you share your story about cdc_acm module compilation? and how did you install it?

If I install Plugapps with the external usb stick I got linux above 2.6.31 so the FTDI driver is already there and it does work. But Pogoplug is 2.6.22 so the driver must be installed first.
Thanks!
zhaozh

Discussion:    Add a Comment | Back to Top | Comments 1-14 of 14 | Latest Comment

Add Your Reply

(will not be displayed)

Email me when comments are added to this thread

 
 

Please log in or register to participate in this community!

Log In

Remember

Not a member? Sign up!

Did you forget your password?

You can also log in using OpenID.

close this window
close this window