ST2205 Sitronix Digital Photo Frame not recognised

[cu-kai]

Describe the bug I am trying to upload to an old ST2205 based photo frame which I've never been able to interface with. I don't have the original software for it any more (which I believe was windows XP based anyway).

Name the camera If this is camera specific, include the camera name as shown by gphoto2 --auto-detect or USB IDs

The device is shown in lsusb:

Bus 003 Device 017: ID 1403:0001 Sitronix Digital Photo Frame

& in gphoto2 --auto-detect:

$ ./gphoto2 --auto-detect
Model                          Port                                            
----------------------------------------------------------
ST2205 USB picture frame       usbdiskdirect:/dev/sda

libgphoto2 and gphoto2 version output of: gphoto2 --version

This version of gphoto2 is using the following software versions and options:
gphoto2         2.5.28.1       gcc, popt(m), exif, no cdk, no aa, jpeg, readline
libgphoto2      2.5.30         standard camlibs, gcc, no ltdl, EXIF
libgphoto2_port 0.12.1         iolibs: disk ptpip serial usb1 usbdiskdirect usbscsi, gcc, no ltdl, EXIF, USB, serial without locking

To Reproduce Attempting to upload a jpg (a few kb) to the device using gphoto2 -u file.jpg produces the following:

*** Error ***              
An error occurred in the io-library ('Unknown error'): No error description available
*** Error (-105: 'Unknown model') ***   

I can also provide the debug log on request.

What's interesting is that this device shows up as a 2MiB un-formatted filesystem in gparted. Unsure if that's supposed to be the case however without the right software or further advice I'm hesitant to touch this as it's such an old frame and I'd rather not break it. There are currently no photos on the frame.

[ndim]

We do have a specific st2205 camlib in libgphoto2 which is even part of the standard set of camlibs to be built, so I am not sure why usbdiskdirect is happening here.

[msmeissn]

usbdiskdirect is the access method. (ioctls backchannelling over scsi disk)

debuglog would be good, it might be a permissons issue perhaps.

[cu-kai]

I'll post the debug log when I next have access to the device. Thanks for getting back to me so quickly.

[cu-kai]

I have attached the log.

my-logfile.txt

[cu-kai]

I came across this library, it seems to be able to dump the firmware and write text to the display but no other features are supported. Would a firmware dump help? It looks like I've got something that's almost non-existent / unsupported everywhere. https://github.com/neophob/libst2205

[cu-kai]

I found the original software for this and it turns out there were already photos on it (despite the device staying: No Photo, the software can sync to it but the photos never appear on the screen. Perhaps it's corrupted, I'm not sure at this point.