Hi,

Experiencing a bit of trouble with --write-config. I'm using a file produced 
by harmony with the command:

    harmony -v --write-config harmony_config_1

but this consistently give the following.

===
Harmony Control 0.13
Copyright 2007 Kevin Timmerman and Phil Dibowitz
This software is distributed under the GPLv3.

bNumEndpoints 2
address 81 attrib 03 max_length 64
address 02 attrib 03 max_length 64
Requesting Identity: 100%                 done
data size 76222
checksum 12
size 76222
Connecting to members.harmonyremote.com:
Path: EasyZapper/New/ProcUpdate/Receive_Zaps.asp
Cookie: Monster
UserId: 0
Connected!
317 bytes sent
703 bytes sent
  done
Invalidating flash:                       done
Erasing flash:        75%          Failed to read from device: -110 (could not 
detach kernel driver from interface 0: No data available)
Failed to erase flash! Bailing out!
Failed with error -110
===

It always craps out at 75% (but is that just because it's got to 100% and just 
hasn't displayed the status line yet?). And the worst thig about this is that 
I've got to boot into Windoze to reload the config! :(

After the above command, a "-iv" gives:

===
Harmony Control 0.13
Copyright 2007 Kevin Timmerman and Phil Dibowitz
This software is distributed under the GPLv3.

bNumEndpoints 2
address 81 attrib 03 max_length 64
address 02 attrib 03 max_length 64
Requesting Identity: 100%                 done
Device Info:
  Model: Logitech Harmony 525 (Mocha Decaf)
  Skin: 22
  Firmware Version: 2.6
  Firmware Type: 0
  Hardware Version: 2.5
  External Flash: 512 KiB - FF:12 25F040
  Architecture: 9
  Protocol: 9
  Manufacturer: Harmony Remote 0-2.6.0
  Product: Harmony Remote 0-2.6.0
  IRL, ORL, FRL: 64, 64, 0
  USB VID: 046D
  USB PID: C111
  USB Ver: 0916
  Serial Number: {6A02E1FB-BE01-6802-B3D8-9DDF00018E2B}
        {6AF8D7ED-0012-6AA6-0001-8E6BBFD80BE2}
        {51220104-0100-258E-A96E-A680B0D8A8CF}
  Invalid config!
Success!
===

BTW: I've got the "Failed to read from device: -110" messages on other 
occasions. At one point it would NOT go away. I rebooted using different 
kernels - just in case as I "roll my own". But, just as suddenly as the 
condition appears, it goes away again! I've _never_ been a great believer 
of "it just fixed itself!". There's _got_ to be something going on in the 
backroom(s).

Any ideas?
Kevin

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel

Reply via email to