Failed OSTC3 fw update

[Jef Driesen]

On 2015-09-17 08:43, Paul-Erik Törrönen wrote:
> 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:
> 
> [78.817027] ERROR: Unexpected character (0x50). [in hw_ostc3.c:966
> (hw_ostc3_firmware_readline)]
> [78.817048] ERROR: Failed to parse header. [in hw_ostc3.c:1029
> (hw_ostc3_firmware_readfile)]

The first byte of a zip file is 0x50 (or ascii 'P'), so my guess is that 
you tried to flash the zip file, and not the hex file that's inside. 
Libdivecomputer expects the hex file, so that doesn't work.

> [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)]

I'm not sure what's going on here. If reading the firmware file failed, 
we shouldn't continue with the firmware upgrade. Unless I messed 
something, libdivecomputer will abort. But maybe this is just some other 
communication initiated by subsurface?

Jef