From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: "Steve Simon" Date: Wed, 22 Jul 2015 17:02:35 +0100 To: 9fans@9fans.net MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: [9fans] USB serial + raspberry PI Topicbox-Message-UUID: 6180677a-ead9-11e9-9d60-3106f5b1d025 Hi, Todays problem is getting a USB serial device to work with plan9 on a ras= pberry 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 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]=3D0x0 buf[1]=3D0xe1 buf[2]=3D0x0 buf[3]=3D0x0 bu= f[4]=3D0x0 buf[5]=3D0x0 buf[6]=3D0x8=20 serial: getparam res: 7 b57600 c0 d0 e0 l8 m0 pn r0 s1 i0=20 dev(0) type(1) framing(0) overruns(0) berr(0) serr(0) serial: getparam: buf[0]=3D0x0 buf[1]=3D0xe1 buf[2]=3D0x0 buf[3]=3D0x0 bu= f[4]=3D0x0 buf[5]=3D0x0 buf[6]=3D0x8=20 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=EF=BF=BD=EF=BF=BDr=3Don mo=17n=3DnoneZ=11 hdp=3Dok se=1F]g=3D0 int-en=EF= =BF=BDn=3Dc2 in=EF=BF=BD=EF=BF=BDt-dest=3D=EF=BF=BD0 int-=EF=BF=BD=EF=BF=BD= edid=3D0=EF=BF=BD=1E edid=3Dfqinishe=1C=EF=BF=BDd trys=EF=BF=BD=EF=BF=BD=3D= 8 state=3Didle, er=EF=BF=BDQer=3Dno er=EF=BF=BDror pwr=3Don mo%rmn=3Dnone =EF=BF=BDhdp=3Dok Wseg=3D0 iNnt-en=3Dc=EF=BF=BD2 i= nt-d=EF=BF=BDest=3D0 i=EF=BF=BDnt-edid=3D0=EF=BF=BDB=3D edid=3Dfini=EF=BF= =BD&shed tr[ys=3D8 s%=EF=BF=BDtate=3Did=EF=BF=BDle, erro=3Dno errkor =1Apw=EF=BF=BD=EF=BF=BDr=3Don mon=3D=EF=BF=BDonnone hd=EF=BF=BDp=3Dok se=EF= =BF=BDg=3D0 int-en=3Dc2:=EF=BF=BDc int-dest=3D0 int-edid=3D=EF=BF=BD=EF=BF= =BDd0 edid=3Dfinishe=1C=EF=BF=BDd trys=3DX8 stat =EF=BF=BDe=3Didle*=EF=BF= =BD, err=3D")no erro9r Anyone have a EIA dongle that is known to work with the PI? anyone any ideas what might be wrong? -Steve