Right, this is bootloader mode which is designed as a recovery mode to
prevent a bricked device.
> Did I brick the device when flashing it? Any ideas?
Just run colorhug-flash with the device plugged in, and it should
flash fine from the bootloader. I fixed a bug in the colorhug command
line tool that didn't allow the device enough time to re-enumerate on
some computers. If the flash fails again, then please let me know and
I'll explain how to manually recover.
Is there anything special about your PC that can give us some clues?
e.g. is it PPC/ARM or just old?
Thanks,
Richard
Yup, can you try with the LiveCD and if it fails, send me the output of:
colorhug-flash --verbose
If that still fails, just do:
/usr/libexec/colorhug boot-flash
/usr/libexec/colorhug set-flash-success 1
Richard.
> After the latest flash update, I was greeted with an error that the
> device was disconnected (which wasn't the case).
> If I connect the colorhug device to my machine, the calibration
> program loads, but communication with the colorhug seems to be borked.
> When it is plugged in, the LEDS seems to flash between red and green.
I was in the same case and compiling the version from the git repository
fixed the problem.
--
Vincent Bernat ☯ http://vincent.bernat.im
Keep it right when you make it faster.
- The Elements of Programming Style (Kernighan & Plauger)
>> After the latest flash update, I was greeted with an error that the
>> device was disconnected (which wasn't the case).
>> If I connect the colorhug device to my machine, the calibration
>> program loads, but communication with the colorhug seems to be borked.
>> When it is plugged in, the LEDS seems to flash between red and green.
> I was in the same case and compiling the version from the git repository
> fixed the problem.
However, I am still unable to use Argyll on Debian, even if the
maintainer repushed another patch. I still get:
XF86VidModeSetGammaRamp returning OK
colorhug: Sending cmd 'TakeReadingXYZ' args '40 00'
icoms: About to return usb write 3 bytes, ICOM err 0x0
colorhug: ICOM err 0x0
colorhug: Reading response
icoms: About to return usb read 0 bytes, ICOM err 0x2000
read_sample returned 'Communication protocol breakdown' (Unknown error code)
colorhug: Sending cmd 'TakeReadingXYZ' args '40 00'
icoms: About to return usb write 0 bytes, ICOM err 0x2000
colorhug: Command send failed with ICOM err 0x2000
read_sample returned 'Communications failure' (Communications failure)
I am a bit lost with which Argyll version should be used. The one here
doesn't seem to have colorhug support:
http://people.freedesktop.org/~hughsient/releases/hargyllcms-1.3.5.tar.xz
(grep -ri colorhug . doesn't return anything)
--
Vincent Bernat ☯ http://vincent.bernat.im
panic("floppy: Port bolixed.");
2.2.16 /usr/src/linux/include/asm-sparc/floppy.h
> However, I am still unable to use Argyll on Debian, even if the
> maintainer repushed another patch. I still get:
The package maintainer did issue an update today and I am now able to
use my ColorHug. Nice!
--
Vincent Bernat ☯ http://vincent.bernat.im
die_if_kernel("Whee... Hello Mr. Penguin", current->tss.kregs);
2.2.16 /usr/src/linux/arch/sparc/kernel/traps.c
Yep. We worked it out with the Debian folks.
I pushed a backported package for Ubuntu Precise (12.04) as well...
(My own package for 11.10 wasn't affected).
Regards,
Pascal de Bruijn
Are you sure you have the latest packages? colorhug-client 0.1.6?
Because that problem sounds familiar with earlier versions, but I
think it was fixed in 0.1.6?
Regards,
Pascal de Bruijn