[argyllcms] Re: ColorHug with Argyll 1.5.1

  • From: Richard Hughes <hughsient@xxxxxxxxx>
  • To: argyllcms@xxxxxxxxxxxxx
  • Date: Mon, 18 Mar 2013 14:51:47 +0000

On 18 March 2013 14:04, Richard Hughes <hughsient@xxxxxxxxx> wrote:
> Yes, the issue is I didn't want to release a version of the firmware
> that would not work with older versions of ArgyllCMS -- I've not
> looked in a while, will 1.4.0 accept the 64 fixed return packet?

It appears not:

colorhug: Sending cmd 'SetLeds' args '00 00 00 00'
icoms: About to return usb write 5 bytes, ICOM err 0x0
colorhug: ICOM err 0x0
colorhug: Reading response
icoms: About to return usb read 0 bytes, ICOM err 0x100
Instrument initialisation failed with 'Communication protocol
breakdown' (Unknown error code)!

And it works fine with any 1.1.x firmware. You can test this by doing:

wget http://hughski.com/downloads/colorhug/firmware/colorhug-1.1.8.bin
colorhug-cmd flash-firmware colorhug-1.1.8.bin
-- This is the latest released firmware that does the incomplete
writes that does not work on Windows.

wget http://hughski.com/downloads/colorhug/firmware/colorhug-1.2.0.bin
colorhug-cmd flash-firmware colorhug-1.2.0.bin
-- This is the latest *test* firmware that returns the full 64 byte
buffer which fixes it on Windows.

Richard

Other related posts: