Quote:
|
Originally Posted by ckaga2000
Reconnecting the T10 does nothing, the only way to get it to communicate with gphoto2 again is to delete files.
|
The same thing happened with the problem we ran into when the T10 had a certain numbers of files and folders on it. Couldn't use it again with gphoto2 until a file was deleted (or added). Are you sure it's an issue with the size?
Quote:
|
Originally Posted by ckaga2000
FWIW: Running detail debug on a sucessful transfer, and the same transfer when it fails only reveals the following difference:
Code:
0.142108 ptp(2): PTP: Opening session
0.142143 gphoto2-port(2): Writing 16=0x10 byte(s) to port...
0.142169 gphoto2-port(3): Hexdump of 16 = 0x10 bytes follows:
0000 10 00 00 00 01 00 02 10-00 00 00 00 01 00 00 00 ................
0.142279 gphoto2-port(2): Reading 512=0x200 bytes from port...
0.142385 gphoto2-port(2): Could only read 12 out of 512 byte(s)
0.142434 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
0000 0c 00 00 00 03 00 01 20-04 00 00 00 ....... ....
0.142482 gphoto2-port(2): Writing 12=0xc byte(s) to port...
0.142525 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
0000 0c 00 00 00 01 00 01 10-01 00 00 00 ............
0.142633 gphoto2-port(2): Reading 512=0x200 bytes from port...
0.144133 gphoto2-port(2): Could only read 12 out of 512 byte(s)
0.144156 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
0000 0c 00 00 00 03 00 04 20-01 00 00 00 ....... ....
0.144198 context(0): PTP Protocol error, data expected
|
From my limited knowledge of PTP, I think this might actually be a gphoto bug. The last read is a PTP_RC_InvalidTransa ctionID response, following a 'Get Device Info' request. Looks like the request needed a transaction id but didn't have one. (As a side note, the PTP error handling isn't the best at this point- it just tells you what it was expecting to get instead of the actual error). I'll look at this in more detail later.