For me the bug is still present:
owserver —link ftdi:s:0x0403:0x6001:xxxxxx —debug
^C
owserver -d ftdi:s:0x0403:0x6001:xxxxxx --debug
remains stuck in an endless loop:
DEBUG: ow_ds9097U.c:(471) Attempt 0 of 3 to initialize the DS9097U
DEBUG: ow_ds9097U.c:(565) Send the initial reset to the bus master.
DEBUG: ow_ds9097U.c:(643) wrong response (E7 not 00)
DEBUG: ow_ds9097U.c:(660) Failed first attempt at resetting baud rate of bus
master ftdi:s:0x0403:0x6001:xxx
DEBUG: ow_ds9097U.c:(643) wrong response (E7 not 00)
DEBUG: ow_ds9097U.c:(665) Failed second attempt at resetting baud rate of bus
master ftdi:s:0x0403:0x6001:xxx
DEBUG: ow_ds9097U.c:(643) wrong response (E7 not 00)
DEBUG: ow_ds9097U.c:(660) Failed first attempt at resetting baud rate of bus
master ftdi:s:0x0403:0x6001:xxx
DEBUG: ow_ds9097U.c:(643) wrong response (E7 not 00)
DEBUG: ow_ds9097U.c:(665) Failed second attempt at resetting baud rate of bus
master ftdi:s:0x0403:0x6001:xxx
DEBUG: ow_ds9097U.c:(627) wrong response (F7 not 44)
DEBUG: ow_ds9097U.c:(565) Send the initial reset to the bus master.
and here its starts over again…
If I now retry with —link I get
DEFAULT: ow_link.c:(364) LINK detection error, trying powercycle
DEFAULT: ow_link.c:(373) LINK detection error, giving up
but then everything seems OK.
At this point the only way out for using the -d driver is to unplug and replug
the LinkUSB.
S.
> On 15 Feb 2016, at 22:45, Johan Ström <jo...@stromnet.se> wrote:
>
> On 10/02/16 08:25, Stefano Miccoli wrote:
>>
>>> On 10 Feb 2016, at 07:55, Johan Ström <
>>> <mailto:jo...@stromnet.se>jo...@stromnet.se <mailto:jo...@stromnet.se>>
>>> wrote:
>>>
>>>>
>>>> Basic functionality seems OK, but there is a sequence that breaks the
>>>> server.
>>>>
>>>> $ owserver --link ftdi:i:0x0403:0x6001 --foreground
>>>> ^C
>>>> $ owserver -d ftdi:i:0x0403:0x6001 --debug
>>>>
>>>
>>> Interesting. When you shut down owsserver --link, does it mention
>>> successfully resetting baudrate, or does that fail too?
>>> When a link is detected, it switches to 19200bps instead of 9600 (double
>>> the speed), and when it shuts down it tries to change back into 9600bps.
>>>
>>
>> Yes, you can restart —link, but I says something like, LINK not found,
>> resetting. Please let me know if you cannot reproduce: I can post a gist
>> with the complete debug output.
>>
> Hi,
>
> tested now, and I cannot reproduce.
>
> owserver --debug --foreground --link ftdi:s:0x0403:0x6001:xxxxxxxx
> owserver --debug --foreground -d ftdi:s:0x0403:0x6001:xxxxxxxx
>
> In both cases it inits fine, and owdir works fine too.
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140_______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
