sitronix usb keychain

[gerard]

If the choice is, using a userspace program, maybe using gtkam with libgphoto (camlib) can be a good choice, some time ago i wrote to the gphoto mailinglist about this device. Some reaction was, its usb-storage so not for libgphoto.
I don't have a list with the correct reasons why usb-storage is not usable.
Reason for me to choice for libgphoto is that is included in many or all distrbutions so people can use it.

WingGnDm, if its OK with you i like to place your files on my homepage?

[WingGnDm]

That would be a good idea. I just read the email.

"No I don't think. The device is apparently a mass storage device.
Hub"

He is under the impression that these devices are actually mass storage device, but they aren't. The device that show up as a mass storage device doesn't even have a file system. It is just an interface for the device.

If you want, check out the libusb mailing list. You will see the discussion on these devices. The best thing to do is black list them as mass storage devices, and mark them as generic scsi devices, then use udev to create the standard /dev entry. Or we can go the even longer way and pretty much use libusb to access the device, but then we would basically be duplicating code thats already in the kernel.

The hardest part will be figuring out the format of the images. As of right now you can dump the images using the get_image function.
I believe i figured out how the device determines the number of pictures in the device. There is a bitmap in the map. On every line with the names of the files, there is a byte that is eigther 0 or 1, if its 1, then the image is valid, if its 0, it has been delete. The best way to handle this is run down the list of names, until you hit a null string. then use the bitmap to show which ones are valid and which have been delete. This could also allow us to recover deleted images. The images are marked invalid when you use the delete function in the device. The list is rewritten by the program.

gerard, it's fine by me if you post them on your site.

If anyone is able to figure out the image format, please post it here.

[dracohack]

I'm not aware of a function to allocate and zero an aligned area, but you could do the posix_memalign() and replace your for() loop with: memset(&get_map, 0, 512);

I'm at work right now and my keychain's at home, but if you can post a binary of a retrieved image i'd take a look at it and see what we can do to make it viewable.


edit: corrected my memset arguments

[greytortoise]

If you pull an image off of the keychain using the Mac PhotoViewer.app application, it saves the image in TIFF format. While it's possible that the image needs to be specifically formatted for the particular LCD display and is being reformatted by the app before saving it as a .tiff file, it is also quite possible that the device itself uses TIFF. TIFF is defined by Adobe in the spec: http://partners.adobe.com/public/developer/en/tiff/TIFF6.pdf, and is described as a format that describes and stores raster image data

[blooflame]

I think TIFF requires too much processing for a small MCU.

Note, I'm not a Linux person yet, but I am trying to understand the tools for hacking this device (mine came from Digital Foci, seems that they sold this design to many).

I am currently using XP and USB Snoopy, trying to determine which device in Snoopy corresponds to the device...Someone above said something about 8/1403?

On Windows, the Photo Viewer uses JPG.

One thing I am going to try (when I get Snoopy figured out): create images of 128x128 in the following: pure red, pure blue, pure green, half red half blue (top bottom), and half red half blue (left right), then move them to the device and see what the data looks like.

[aiah]

[iibm]

there is some answer here : http://picframe.spritesserver.nl/wiki/index.php/ImageEncoding

[ericm]

I had a go at writing a set image. From looking at a usb snoop I think the image gets loaded
via a sequence like:

send to block 0x31 -- 512 bytes
03 00 00 00 XX 00 00 ....

send to block 0x33 -- 0x8000 bytes 32728
the image data

send to block 0x31 -- 512 bytes
02 00 00 00 XX 00 00 ....

read from block 0x58 -- 512 bytes

I tried reading an image then writing it back with some changed bytes.
This ran okay but locked up the display and I have been unable to get it working again.
I guess this helps people in what not to do!

[NGE]

Hello every one,
I have bought a keyChain, but like some1 told on the beginning of this thread this keychain have a "trap" my wife connected to the pc, and tryed to open on the Windows Usb devices and it asked to format the unit and she pressed "YES" !!!! but it have gived an error telling that cannot format the unit, but now when i insert pictures on the device using Picture Viwer, and then i try to see the pictures on the KeyChain nothing appens... Black Screen.. Any guess how to fix this problem ?

( Maybe she have deleted any page on the "formating process " ) ? I cant enter on the "memory stick" it ask me all the time to format it..

Thanks in advance.

[Jsines]

Sorry guys. I've read all the theads but I'm really not smart enough to understand enough to even ask a question about what you wrote. The basic question is, how can a real layman that just knows how to point and click get this stupid thing to work. i.e. accept pictures from the computer and show them back. I need something easy. Or is this item destined to be filed in the circular file on tthe floor?
_________________
J. Sines

[herberto07]