OSTC sport DL porblem

[Anton Lundin]

Sorry for top posting, but try with a new battery in your OSTC.

I've seen such wired errors that got fixed by a fresher battery. The battery might have enough juice to run the computer but the BT chip might have problems.

//Anton

On July 12, 2016 10:34:27 AM GMT+02:00, Miika Turkia <miika.turkia at gmail.com> wrote:
>On Tue, Jul 12, 2016 at 9:54 AM, Jef Driesen <jef at libdivecomputer.org>
>wrote:
>> On 2016-07-06 10:37, Miika Turkia wrote:
>>>
>>> On Tue, Jul 5, 2016 at 5:54 PM, Jef Driesen
><jef at libdivecomputer.org>
>>> wrote:
>>>>
>>>> On 2016-07-05 14:45, Miika Turkia wrote:
>>>>>
>>>>> Something is not working properly. Trying this with rfcomm channel
>1
>>>>> and getting the following on the terminal:
>>>>>
>>>>> DATETIME 2016-07-05T12:41:54Z (1467722514)
>>>>> VERSION 0.5.0-devel-Subsurface-branch
>>>>> (8356e22e61bf80234e5a1ccc3ed0f4ea81e0245d)
>>>>> Opening the device (Heinrichs Weikamp OSTC 2, /dev/rfcomm0).
>>>>> INFO: Open: name=/dev/rfcomm0
>>>>> INFO: Configure: baudrate=115200, databits=8, parity=0,
>stopbits=1,
>>>>> flowcontrol=0
>>>>> INFO: Timeout: value=3000
>>>>> INFO: Sleep: value=300
>>>>> INFO: Flush: queue=3, input=0, output=0
>>>>> Registering the event handler.
>>>>> Registering the cancellation handler.
>>>>> Downloading the dives.
>>>>> Event: progress 0.00% (0/4194304)
>>>>> INFO: Write: size=1, data=BB
>>>>> INFO: Read: size=0, data=
>>>>> ERROR: Failed to receive the echo. [in hw_ostc3.c:211
>>>>> (hw_ostc3_transfer)]
>>>>> ERROR: Failed to send the command. [in hw_ostc3.c:444
>>>>> (hw_ostc3_device_init_download)]
>>>>> ERROR: Error downloading the dives. [in dctool_download.c:218
>>>>> (download)]
>>>>> ERROR: Input/output error (5) [in serial_posix.c:205
>(serial_close)]
>>>>> ERROR: Timeout
>>>>
>>>>
>>>>
>>>> Check whether another application is trying to use the rfcomm
>device. For
>>>> example ModemManager is known to cause this kind of communication
>>>> problems.
>>>
>>>
>>> Even after getting rid of ModemManager and several attempts, I
>didn't
>>> manage to grab the dat. I still get the same error. lsof shows the
>>> following:
>>>
>>> krfcommd  2645            root  cwd       DIR              252,1
>>> 4096          2 /
>>> krfcommd  2645            root  rtd       DIR              252,1
>>> 4096          2 /
>>> krfcommd  2645            root  txt   unknown
>>>               /proc/2645/exe
>>>
>>> Also dmesg has something related to bluetooth, but I kinda doubt
>this
>>> is the issues as dumping the memory worked fine:
>>>
>>> [   24.880646] Bluetooth: hci0: BCM: chip id 63
>>> [   24.881610] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
>>> [   24.881631] bluetooth hci0: Direct firmware load for
>>> brcm/BCM20702A1-0a5c-21e6.hcd failed with error -2
>>> [   24.881650] Bluetooth: hci0: BCM: Patch
>>> brcm/BCM20702A1-0a5c-21e6.hcd not found
>>> [   24.939965] Bluetooth: RFCOMM TTY layer initialized
>>> [   24.939974] Bluetooth: RFCOMM socket layer initialized
>>> [   24.939981] Bluetooth: RFCOMM ver 1.11
>>
>>
>> This looks good to me, so I'm not really sure why it doesn't work.
>>
>> Can you try to with a build that uses native bluetooth sockets,
>instead of
>> the serial port emulation? You can download a pre-compiled version
>here:
>>
>> http://libdivecomputer.org/builds/experimental/linux/dctool-bluetooth
>>
>> The options are the same as before, with the exception that you need
>to
>> provide the bluetooth mac address instead of /dev/rfcomm0:
>>
>> dctool-bluetooth -v -l ostc3.log -f ostc3 download -f raw -o
>dive.%n.bin
>> <ADDRESS>
>
>
>Still unable to grab you the logs :(
>
>DATETIME 2016-07-12T08:27:53Z (1468312073)
>VERSION 0.5.0-devel (7652bc61b1bbd37e32cf05d6858c53ff465880f4)
>Opening the device (Heinrichs Weikamp OSTC 2, 00:12:6F:2A:0E:E0).
>INFO: Connect: address=00:12:6F:2A:0E:E0, port=1
>Registering the event handler.
>Registering the cancellation handler.
>Downloading the dives.
>Event: progress 0.00% (0/4194304)
>INFO: Write: size=1, data=BB
>INFO: Read: size=1, data=FF
>ERROR: Unexpected echo. [in ../../source/src/hw_ostc3.c:236
>(hw_ostc3_transfer)]
>ERROR: Failed to send the command. [in ../../source/src/hw_ostc3.c:450
>(hw_ostc3_device_init_download)]
>ERROR: Error downloading the dives. [in
>../../source/examples/dctool_download.c:218 (download)]
>ERROR: Protocol error
>
>It hangs on the first write and at about the time when the OSTC Sport
>times out bluetooth mode, the INFO Read line appears.
>
>miika
>_______________________________________________
>subsurface mailing list
>subsurface at subsurface-divelog.org
>http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface