Failed OSTC3 fw update

[Anton Lundin]

On 17 September, 2015 - "Paul-Erik Törrönen" wrote:

> 
> This is with the latest from git.
> 
> Subsurface v4.4.96-135-ge5caca8f4901, built with libdivecomputer
> v0.5.0-devel-Subsurface-branch (8932b2a936a237284e0bffcea562c406551ab433)
> 
> Using the following to build:
> 
> rm -rf install-root grantlee subsurface libdivecomputer libgit2 && git
> clone git://subsurface-divelog.org/subsurface &&
> ./subsurface/scripts/build.sh
> 
> Start up Subsurface:
> 
> LD_LIBRARY_PATH=install-root/lib subsurface/build/subsurface
> 
> So, I do the following:
> 
> 1. Click File -> Configure dive computer
> 2. Click Connect via Bluetooth
> 3. Put the OSTC3 in Bt-mode
> 4. In Subsurface Bt-dialog click Scan, select OSTC3, click Save
> 5. Click Retrieve available details, making sure the connection works as
> the fields are populated, fw is 1.87
> 6. Click Update firmware, select the 1.88 fw hex-file in the file-dialog,
> click Open
> 
> As a result I get 'Error: Firmware update failed!' on the bottom of the
> Configure dive computer-dialog.
> 
> In the terminal, from which I started Subsurface:
> 
> $ LD_LIBRARY_PATH=install-root/lib subsurface/build/subsurface
> Map theme file does not exist: ""
> QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No
> such file or directory
> qt.bluetooth.bluez: Bluez 5 detected.
> qt.bluetooth.bluez: Creating QtBluezDiscoveryManager
> qt.bluetooth.bluez: Discovered:  "00:80:25:49:F9:29" "OSTC3#04460" Num
> UUIDs 2 total device 0 cached RSSI 0 Class 7936
> qt.bluetooth.bluez: Discovered:  "A8:54:B2:5E:B3:6B" "TVBluetooth" Num
> UUIDs 0 total device 1 cached RSSI -77 Class 525372
> qt.bluetooth.bluez: Updating RSSI for "00:80:25:49:F9:29" QVariant(short,
> -72)
> qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
> [78.817027] ERROR: Unexpected character (0x50). [in hw_ostc3.c:966
> (hw_ostc3_firmware_readline)]

Looks like somethings b0rken with your firmware file.

> [78.817048] ERROR: Failed to parse header. [in hw_ostc3.c:1029
> (hw_ostc3_firmware_readfile)]
> qt.bluetooth.bluez: void QBluetoothSocketPrivate::_q_readNotify() 17
> error: -1 "Connection timed out"
> QIODevice::write (QBluetoothSocket): device not open
> [128.673783] ERROR: Failed to send the command. [in hw_ostc3.c:418
> (hw_ostc3_device_init_service)]
> QIODevice::write (QBluetoothSocket): device not open
> [152.701132] ERROR: Failed to send the command. [in hw_ostc3.c:192
> (hw_ostc3_transfer)]
> [152.701138] ERROR: Failed to send the command. [in hw_ostc3.c:395
> (hw_ostc3_device_init_download)]
> qt.bluetooth.bluez: Discovered:  "00:80:25:49:F9:29" "OSTC3#04460" Num
> UUIDs 2 total device 0 cached RSSI 0 Class 7936
> qt.bluetooth.bluez: Discovered:  "A8:54:B2:5E:B3:6B" "TVBluetooth" Num
> UUIDs 4 total device 1 cached RSSI 0 Class 525372
> qt.bluetooth.bluez: Updating RSSI for "00:80:25:49:F9:29" QVariant(short,
> -73)
> qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
> QSocketNotifier: Socket notifiers cannot be enabled or disabled from
> another thread
> qt.bluetooth.bluez: void QBluetoothSocketPrivate::_q_readNotify() 16
> error: -1 "Connection timed out"
> 
> (I tried this twice).
> 

I should probably tinker some with the ui there. If you click Retrieve
available details the device is put into download mode, and thus not
accepting firmware-upgrade command any longer. 

So, unless your firmware file is damaged which the stray "P" above
suggests, try connecting and then doing firmware update straight away.


This reminds me that there are some settings which the OSTC Sport
doesn't accept yet, which makes the qtbluetooth code behave badly, and
thus makes the configure code behave even worse. That should be fixed
before we release.


//Anton


-- 
Anton Lundin	+46702-161604