i'm using ftdi232 without problems on arm
2012/11/6 Peter Hollenbeck <[email protected]>
> I run a Raspberry Pi with Raspbian, a Prolific PL2303 USB to
> serial adapter and a Hobby Boards serial master. Works fine.
> Peter
>
> On Tue, Nov 6, 2012 at 2:42 PM, Gregg Levine <[email protected]>wrote:
>
>> On Tue, Nov 6, 2012 at 5:37 PM, Thomas Parvais <[email protected]>
>> wrote:
>> > Hello Paul,
>> >
>> > I just installed digitemp on this sheevaplug
>> >
>> > There is, I think a strange behaviour with PL2303:
>> >
>> > 1. I plug the usb adapter. Correctly detected by kernet in ttyUSB0
>> > 2. digitemp_DS9097U -s /dev/ttyUSB0 -w -v gives correct 1-wire
>> detection
>> > 3. i I redo again digitemp_DS9097U -s /dev/ttyUSB0 -w -v, I obtain:
>> >
>> > DigiTemp v3.5.0 Copyright 1996-2007 by Brian C. Lane
>> > GNU Public License v2.0 - http://www.digitemp.com
>> > Error 5: DS2480B Adapter Not Detected
>> > Error 7: DS2480B: Bad Response
>> > Error 7: DS2480B: Bad Response
>> > Error 7: DS2480B: Bad Response
>> > Error 7: DS2480B: Bad Response
>> > Error 7: DS2480B: Bad Response
>> > Error 7: DS2480B: Bad Response
>> > Error 7: DS2480B: Bad Response
>> > Error 7: DS2480B: Bad Response
>> > Error 7: DS2480B: Bad Response
>> >
>> > I have to unplug the usb adapter and put it in again to have digitemp
>> > working (once)
>> >
>> > dmesg gives:
>> >
>> > unplug
>> >
>> > [ 787.871868] usb 1-1: USB disconnect, address 6
>> > [ 787.878234] pl2303 ttyUSB0: pl2303 converter now disconnected from
>> > ttyUSB0
>> > [ 787.886008] pl2303 1-1:1.0: device disconnected
>> >
>> > re-plug usb:
>> >
>> > [ 791.916586] usb 1-1: new full speed USB device using orion-ehci and
>> > address 7
>> > [ 792.072503] usb 1-1: New USB device found, idVendor=067b,
>> idProduct=2303
>> > [ 792.079258] usb 1-1: New USB device strings: Mfr=1, Product=2,
>> > SerialNumber=0
>> > [ 792.086431] usb 1-1: Product: USB 2.0 To COM Device
>> > [ 792.091348] usb 1-1: Manufacturer: Prolific Technology Inc.
>> > [ 792.099425] usb 1-1: configuration #1 chosen from 1 choice
>> > [ 792.108767] pl2303 1-1:1.0: pl2303 converter detected
>> > [ 792.125013] usb 1-1: pl2303 converter now attached to ttyUSB0
>> >
>> > aie aie aie... I'm restarting a complex problem out of my knowledge....
>> > After trying getting OWFS working on my synology and now on my sheeva I
>> > wonder how to manage finnaly...
>> >
>> > Any idea of good serial-usb stable adapter I can buy ?
>> >
>> > Thomas
>> >
>> >
>> > Le 6/11/2012 23:22, Paul Alfille a écrit :
>> >
>> > I was worried that a serial mode bug had crept into the program, so I
>> just
>> > tested the current owfs version with a pl2303 and serial adapter on x-64
>> > architecture (i.e. a desktop system). It works perfectly, both for the
>> > DS9097U and the passive adapter.
>> >
>> > So assuming your USB/serial adpter and DS9097U are fine, the problem is
>> with
>> > the two different architectures. Could there be bugs in the ARM version
>> of
>> > the pl2303 kernel module?
>> >
>> > I'm not exactly how to procede, except that maybe trying another program
>> > (like digitemp) for comparison might be illuminating.
>> >
>> > Paul
>> >
>> >
>> > On Tue, Nov 6, 2012 at 12:21 PM, Thomas Parvais <[email protected]>
>> wrote:
>> >>
>> >> Hello
>> >>
>> >> I finally succeed to compile last owfs on my SheevaPlug (Debian
>> Squeeze)
>> >> by following the next sequences below thanx
>> >> http://archive.pfb.no/2010/04/01/owfs-on-debian-squeeze/#) .
>> >>
>> >> (as root)
>> >>
>> >> 1. libusb
>> >>
>> >> tar -xvzf libusb-0.1.12.tar.gz
>> >> cd libusb-0.1.12
>> >> libusb-0.1.12$ ./configure --without-x
>> >>
>> >> make
>> >> make install
>> >>
>> >> 2. owfs
>> >>
>> >> cd owfs
>> >> ./configure --enable-debian
>> >>
>> >> make
>> >> make install
>> >>
>> >> vi /etc/udev/rules.d/56-owfs.rules
>> >>
>> >> Paste the code below.
>> >>
>> >> ##########################################################
>> >> SUBSYSTEM!="usb_device", ACTION!="add", GOTO="owfs_rules_end"
>> >>
>> >> # DS2490 1-Wire adapter
>> >> SYSFS{idVendor}=="04fa", SYSFS{idProduct}=="2490", MODE="0666",
>> >> GROUP="owfs"
>> >>
>> >> LABEL="owfs_rules_end"
>> >> ##########################################################
>> >>
>> >> addgroup owfs
>> >> usermod -a -G owfs root
>> >> mkdir /mnt/1-wire
>> >>
>> >> voilà,
>> >>
>> >>
>> >> However, when I launch owserver , I have problems:
>> >>
>> >>
>> >>> root@sheeva:~/libusb-0.1.12# owhttpd -d /dev/ttyUSB0 --debug -p 3001
>> >>> DEBUG MODE
>> >>> libow version:
>> >>> 2.8p20
>> >>> DEBUG: ow_daemon.c:(167) main thread id = 1076887552
>> >>> CONNECT: ow_avahi_link.c:(72) No Avahi support. Library
>> libavahi-client
>> >>> couldn't be loaded
>> >>> CONNECT: ow_dnssd.c:(82) Zeroconf/Bonjour is disabled since dnssd
>> library
>> >>> isn't found
>> >>> CALL: ow_parsename.c:(98) path=[]
>> >>> DEBUG: owlib.c:(82) Globals temp limits 0C 100C (for simulated
>> >>> adapters)
>> >>> DEBUG: ow_ds9097U.c:(285) Attempt 0 of 3 to initialize the DS9097U
>> >>> DEBUG: ow_ds9097U.c:(376) Send the initial reset to the bus master.
>> >>> DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
>> >>> DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
>> >>> DEBUG: ow_ds9097U.c:(454) wrong response (0F not 00)
>> >>> DEBUG: ow_ds9097U.c:(471) Failed first attempt at resetting baud
>> rate
>> >>> of bus master /dev/ttyUSB0
>> >>> DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
>> >>> DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
>> >>> DEBUG: ow_ds9097U.c:(454) wrong response (0F not 00)
>> >>> DEBUG: ow_ds9097U.c:(476) Failed second attempt at resetting baud
>> rate
>> >>> of bus master /dev/ttyUSB0
>> >>> DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
>> >>> DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
>> >>> DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
>> >>> DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
>> >>> DEBUG: ow_ds9097U.c:(454) wrong response (0F not 00)
>> >>> DEBUG: ow_ds9097U.c:(471) Failed first attempt at resetting baud
>> rate
>> >>> of bus master /dev/ttyUSB0
>> >>> DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
>> >>> DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
>> >>> DEBUG: ow_ds9097U.c:(454) wrong response (0F not 00)
>> >>> DEBUG: ow_ds9097U.c:(476) Failed second attempt at resetting baud
>> rate
>> >>> of bus master /dev/ttyUSB0
>> >>> DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
>> >>> DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
>> >>> DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
>> >>> DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
>> >>> DEBUG: ow_ds9097U.c:(438) wrong response (45 not 44)
>> >>> DEBUG: ow_ds9097U.c:(376) Send the initial reset to the bus master.
>> >>> DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
>> >>> DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
>> >>> DEBUG: ow_ds9097U.c:(454) wrong response (0F not 00)
>> >>> DEBUG: ow_ds9097U.c:(471) Failed first attempt at resetting baud
>> rate
>> >>> of bus master /dev/ttyUSB0
>> >>> DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
>> >>> DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
>> >>> DEBUG: ow_ds9097U.c:(454) wrong response (0F not 00)
>> >>> DEBUG: ow_ds9097U.c:(476) Failed second attempt at resetting baud
>> rate
>> >>> of bus master /dev/ttyUSB0
>> >>> DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
>> >>> DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
>> >>> DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
>> >>> DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
>> >>> DEBUG: ow_ds9097U.c:(454) wrong response (0F not 00)
>> >>> DEBUG: ow_ds9097U.c:(471) Failed first attempt at resetting baud
>> rate
>> >>> of bus master /dev/ttyUSB0
>> >>> DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
>> >>> DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
>> >>> DEBUG: ow_ds9097U.c:(454) wrong response (0F not 00)
>> >>> DEBUG: ow_ds9097U.c:(476) Failed second attempt at resetting baud
>> rate
>> >>> of bus master /dev/ttyUSB0
>> >>> DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
>> >>> DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
>> >>> DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
>> >>> DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
>> >>> DEBUG: ow_ds9097U.c:(438) wrong response (45 not 44)
>> >>> DEBUG: ow_ds9097U.c:(376) Send the initial reset to the bus master.
>> >>
>> >>
>> >> same kind of results if I launch owserver -d /dev/ttyUSB0 etc...
>> >>
>> >> Very strange because it worked the first time, but now, this is not
>> >> working anymore. I also tried to reboot the plug.
>> >>
>> >> Don't know really what to do. I tried googling without success till
>> now.
>> >> I'm litle bit disappointed as my 1-wire network is fully installed and
>> I
>> >> want to use sheevaplug instead of Windows from now.
>> >>
>> >>
>> >>
>> >> some more info saying (according to my very basic knowledge) things
>> seems
>> >> okay for the usb-adapter driver (PL2303)
>> >>
>> >>> uname -a
>> >>> Linux sheeva 2.6.32-5-kirkwood #1 Sun Sep 23 22:53:30 UTC 2012
>> armv5tel
>> >>> GNU/Linux
>> >>
>> >>
>> >>> root@sheeva:~/libusb-0.1.12# lsusb
>> >>> Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303
>> Serial
>> >>> Port
>> >>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> >>
>> >>
>> >>> root@sheeva:~/libusb-0.1.12# libusb-config --version
>> >>> 0.1.12
>> >>
>> >>
>> >>> dmesg
>> >>> [ 2.296697] usb 1-1: new full speed USB device using orion-ehci and
>> >>> address 2
>> >>> [ 2.462694] usb 1-1: New USB device found, idVendor=067b,
>> >>> idProduct=2303
>> >>> [ 2.469460] usb 1-1: New USB device strings: Mfr=1, Product=2,
>> >>> SerialNumber=0
>> >>> [ 2.476641] usb 1-1: Product: USB 2.0 To COM Device
>> >>> [ 2.481547] usb 1-1: Manufacturer: Prolific Technology Inc.
>> >>> [ 2.487779] usb 1-1: configuration #1 chosen from 1 choice
>> >>> [ 2.995785] udev[151]: starting version 164
>> >>> [ 3.539919] usbcore: registered new interface driver usbserial
>> >>> [ 3.551690] USB Serial support registered for generic
>> >>> [ 3.559387] usbcore: registered new interface driver
>> usbserial_generic
>> >>> [ 3.565963] usbserial: USB Serial Driver core
>> >>> [ 3.583986] USB Serial support registered for pl2303
>> >>> [ 3.589649] pl2303 1-1:1.0: pl2303 converter detected
>> >>> [ 3.607210] usb 1-1: pl2303 converter now attached to ttyUSB0
>> >>> [ 3.613038] usbcore: registered new interface driver pl2303
>> >>> [ 3.618658] pl2303: Prolific PL2303 USB to serial adaptor driver
>> >>
>> >>
>> >>
>> >> Thank you
>> >>
>> >> Thomas
>>
>> Hello!
>> You should have asked me first.
>> The FTDI Chip ones work much better then those. The PL2303 one
>> suffers from not being properly introduced to Linux. Whereas the FTDI
>> one has been. Sadly they do not have an open source directly driver,
>> but the one that's in the kernel works. Incidentally their webpages
>> should show you the way regarding everything and they even sell direct
>> if you can't find a local vendor.
>> -----
>> Gregg C Levine [email protected]
>> "This signature fought the Time Wars, time and again."
>>
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Central: Instant, anywhere, Remote PC access and management.
>> Stay in control, update software, and manage PCs from one command center
>> Diagnose problems and improve visibility into emerging IT issues
>> Automate, monitor and manage. Do more in less time with Central
>> http://p.sf.net/sfu/logmein12331_d2d
>> _______________________________________________
>> Owfs-developers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>
>
>
> ------------------------------------------------------------------------------
> LogMeIn Central: Instant, anywhere, Remote PC access and management.
> Stay in control, update software, and manage PCs from one command center
> Diagnose problems and improve visibility into emerging IT issues
> Automate, monitor and manage. Do more in less time with Central
> http://p.sf.net/sfu/logmein12331_d2d
> _______________________________________________
> Owfs-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
--
Roberto Spadim
Spadim Technology / SPAEmpresarial
------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
