9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
* [9fans] USB serial + raspberry PI
@ 2015-07-22 16:02 Steve Simon
  0 siblings, 0 replies; only message in thread
From: Steve Simon @ 2015-07-22 16:02 UTC (permalink / raw)
  To: 9fans

Hi,

Todays problem is getting a USB serial device to work with plan9 on a raspberry PI.

I have several dongles which seem to reprisent two chipsets.

One is recognised by the USB driver and it starts usb/serial for me,
sadly It just seems to receive a single character constantly.

The other is not recognised, but I start usb/serial manually and I
get quite a bit of life from it:

usb debug gives me:

usb/serial: startdevs: opening #0 /dev/usb/ep9.0
usb/serial: opendev 0x5d060 /dev/usb/ep9.0
usb/serial: /dev/usb/ep9.0 csp 255.0.0 vid 0x67b did 0x2303 refs 1
	none <nil> <nil>
	conf: cval 1 attrib a0 100 mA
		iface csp 255.0.0
		  alt 0 attr 2 ival 0
		  ep id 1 addr 129 dir in type intr itype 0 maxpkt 10 ntds 1
		  ep id 2 addr 2 dir out type bulk itype 0 maxpkt 64 ntds 1
		  ep id 3 addr 131 dir in type bulk itype 0 maxpkt 64 ntds 1
serial: vid 0x067b did 0x2303 vid 0x067b did 0x2303
serial[0]: ep ids: in 3 out 2 intr 1
usb/serial: /dev/usb/ep9.3 already exists; trying to open
usb/serial: opendev 0x5d680 /dev/usb/ep9.3
usb/serial: /dev/usb/ep9.2 already exists; trying to open
usb/serial: opendev 0x5d6c0 /dev/usb/ep9.2
usb/serial: /dev/usb/ep9.1 already exists; trying to open
usb/serial: opendev 0x50360 /dev/usb/ep9.1
serial: ep in /dev/usb/ep9.3 out /dev/usb/ep9.2
serial: ep intr /dev/usb/ep9.1
serial: valid interface, calling serinit
plinit
serial: type 1
serial: vendorread val: 0x8484 idx:0 buf:50480
serial: vendorread res:1
serial: vendorwrite val: 0x404 idx:0
serial: vendorwrite res:8
serial: vendorread val: 0x8484 idx:0 buf:50480
serial: vendorread res:1
serial: vendorread val: 0x8383 idx:0 buf:50480
serial: vendorread res:1
serial: vendorread val: 0x8484 idx:0 buf:50480
serial: vendorread res:1
serial: vendorwrite val: 0x404 idx:1
serial: vendorwrite res:8
serial: vendorread val: 0x8484 idx:0 buf:50480
serial: vendorread res:1
serial: vendorread val: 0x8383 idx:0 buf:50480
serial: vendorread res:1
serial: vendorwrite val: 0x0 idx:1
serial: vendorwrite res:8
serial: vendorwrite val: 0x1 idx:0
serial: vendorwrite res:8
serial: vendorwrite val: 0x2 idx:68
serial: vendorwrite res:8
serial: getparam: buf[0]=0x0 buf[1]=0xe1 buf[2]=0x0 buf[3]=0x0 buf[4]=0x0 buf[5]=0x0 buf[6]=0x8 
serial: getparam res: 7
b57600 c0 d0 e0 l8 m0 pn r0 s1 i0 
dev(0) type(1)  framing(0) overruns(0) berr(0)  serr(0)
serial: getparam: buf[0]=0x0 buf[1]=0xe1 buf[2]=0x0 buf[3]=0x0 buf[4]=0x0 buf[5]=0x0 buf[6]=0x8 
serial: getparam res: 7
serial: adding interface 0, 5d824
eiaU9...usb/serial: fsadd eiaU9
serial: reading from interrupt

and cat /dev/usb/ctl gives

ep9.3 enabled bulk r speed full maxpkt 256 pollival 0 samplesz 0 hz 0 hub 2 port 2 busy
ep9.2 enabled bulk w speed full maxpkt 256 pollival 0 samplesz 0 hz 0 hub 2 port 2 busy
ep9.1 enabled interrupt r speed full maxpkt 10 pollival 10 samplesz 0 hz 0 hub 2 port 2 busy


sadly though, the data is corrupted:

pw��r=on mo\x17n=noneZ\x11 hdp=ok se\x1f]g=0 int-en�n=c2 in��t-dest=�0 int-��edid=0�\x1e edid=fqinishe\x1c�d trys��=8 state=idle, er�Qer=no er�ror
pwr=on mo%rmn=none �hdp=ok Wseg=0 iNnt-en=c�2 int-d�est=0 i�nt-edid=0�B= edid=fini�&shed tr[ys=8 s%�tate=id�le, erro=no errkor
\x1apw��r=on mon=�onnone hd�p=ok se�g=0 int-en=c2:�c int-dest=0 int-edid=��d0 edid=finishe\x1c�d trys=X8 stat	�e=idle*�, err=")no erro9r

Anyone have a EIA dongle that is known to work with the PI?
anyone any ideas what might be wrong?

-Steve



^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2015-07-22 16:02 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-22 16:02 [9fans] USB serial + raspberry PI Steve Simon

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).