colorhug-flash problem

37 views
Skip to first unread message

Yuri D'Elia

unread,
Apr 8, 2015, 2:35:09 PM4/8/15
to colorhu...@googlegroups.com
I remember I had this issue before, but I didn't report it.

I'm using colorhug-client 0.2.1 from debian unstable.

First issue: colorhug-flash (and colorhug-ccmx by the way) require me to
unplug/replug to detect the device. This is annoying.

Second issue:

colorhug-flash -f colorhug-1.2.3.bin

returns the following error:

Failed to write the firmware
usb:00:04: Invalid read: retval=0x0a [Invalid value] cmd=0x28 (expected
0x28 [set-flash-success]) len=64 (expected 2 or 64)

however the main dialog reads 'Device successfully updated' and a
further invocation of colorhug-flash says my device is at 1.2.3.
Was it flashed correctly, or not?

Richard Hughes

unread,
Apr 12, 2015, 2:17:25 PM4/12/15
to colorhu...@googlegroups.com
On 8 April 2015 at 19:35, Yuri D'Elia <wav...@thregr.org> wrote:
> I'm using colorhug-client 0.2.1 from debian unstable.

Does this happen with something newer?

> First issue: colorhug-flash (and colorhug-ccmx by the way) require me to
> unplug/replug to detect the device. This is annoying.

I've not heard of this before.

> however the main dialog reads 'Device successfully updated' and a
> further invocation of colorhug-flash says my device is at 1.2.3.
> Was it flashed correctly, or not?

You can trust the output of colorhug-cmd get-firmware-version or what
the colorhug-flash tool uses. There have been a lot of fixes since
0.2.1 so I assume that fixed it. I assume it doesn't happen with the
LiveCD as well?

Richard.

Richard Hughes

unread,
Apr 12, 2015, 2:23:44 PM4/12/15
to colorhu...@googlegroups.com
On 8 April 2015 at 19:35, Yuri D'Elia <wav...@thregr.org> wrote:
> I'm using colorhug-client 0.2.1 from debian unstable.

Does this happen with something newer?

> First issue: colorhug-flash (and colorhug-ccmx by the way) require me to
> unplug/replug to detect the device. This is annoying.

I've not heard of this before.

> however the main dialog reads 'Device successfully updated' and a
> further invocation of colorhug-flash says my device is at 1.2.3.
> Was it flashed correctly, or not?

Yuri D'Elia

unread,
Apr 12, 2015, 4:19:08 PM4/12/15
to colorhu...@googlegroups.com
On 04/12/2015 08:23 PM, Richard Hughes wrote:
> On 8 April 2015 at 19:35, Yuri D'Elia <wav...@thregr.org> wrote:
>> I'm using colorhug-client 0.2.1 from debian unstable.
>
> Does this happen with something newer?

I'll try (need to rebuilt the client before).

>> First issue: colorhug-flash (and colorhug-ccmx by the way) require me to
>> unplug/replug to detect the device. This is annoying.
>
> I've not heard of this before.

Probably related to the above.

Yuri D'Elia

unread,
Apr 12, 2015, 4:57:18 PM4/12/15
to colorhu...@googlegroups.com
On 04/12/2015 08:23 PM, Richard Hughes wrote:
> On 8 April 2015 at 19:35, Yuri D'Elia <wav...@thregr.org> wrote:
>> I'm using colorhug-client 0.2.1 from debian unstable.
>
> Does this happen with something newer?

I tried briefly to compile the latest client (0.2.6 from github,
right?), but even the latest colord on debian is old.

I've submitted a couple of bug reports about that, hoping to move things
a bit forward.

Meanwhile, the latest downloadable livecd is from 2013/02.
Looks equally old.

Richard Hughes

unread,
Apr 18, 2015, 11:03:37 AM4/18/15
to colorhu...@googlegroups.com
On 12 April 2015 at 21:57, Yuri D'Elia <wav...@thregr.org> wrote:
> Meanwhile, the latest downloadable livecd is from 2013/02.
> Looks equally old.

I'm going to work on this tonight, and make the new CD compatible with
ColorHug2 as well.

Richard.
Reply all
Reply to author
Forward
0 new messages