LCD screen for your dockstar (cheap! <$5)

Hi, All

I have a Sytronix device which I bought specifically for the hack, and was pleased to find it has the same identifier as expected. From lsusb...
Bus 001 Device 018: ID 1403:0001 Sitronix Digital Photo Frame

I found it had showed up at /dev/sdb and the hack script resulted in a screen showing 'baks r ok', but I was surprised to find, that it reported...
$ ./hackfw.sh /dev/sdb
...
"Sorry, I couldn't find a matching device profile"

I then followed the instructions at...
http://forum.doozan.com/read.php?2,2435,2439#msg-2439
...using the latest .deb for the cc65 tools which no longer seem to be available via public subversion.

It seems to be talking to the device. However, the script also reports failure, finishing with the lines...
Locating CMP_VAR1 & CMP_VAR2...
Eeek! expected single match but found 0 - dont know what to do!

Any ideas what I can do now to try and proceed? I'm pretty sure it's from the right family of displays, but the default approach doesn't seem to be cutting it and the steps for a new hack are failing too.

The original firmware backup generated by the hackfw.sh script is attached to this post.

superelchi has uploaded a version of dpf-ax that added support for Coby DP-151 (white color) ax206 frames.

dpf-ax v0.3 with new alternative 'display' firmware, changelog

Now with two different alternative firmware versions:
- 'Developer' version: firmware with same features and look
as pre-0.3 versions ("Blue Screen of Hack").
- 'Display' version: firmware for use as a status display (lcdlinux, vdr, etc.)
* New, bigger font
* New menus
* User selectabel & dowloadable splashscreen
* User config saved to flash.

Thanks superelchi

Thanks superelchi, great news.

You tested if it works with the DX21334?

Thanks to all.

FYI: new dpf-ax version 0.3 in svn.

Its now possible to build 2 different firmware versions:
- 'Developer' version: firmware with same features and look as pre-0.3 versions ("Blue Screen of Hack").
- 'Display' version: firmware for use as a status display (lcd4linux, vdr, etc.) with bigger font, new menu and selectable splashscreen.

superelchi



Edited 1 time(s). Last edit at 05/18/2012 11:48AM by superelchi.

root@YAVDR:/home/gaby/dpf-ax/fw# python identify.py
Usage: python identify.py dumpfile|dpf-devicenode
root@YAVDR:/home/gaby/dpf-ax/fw# python identify.py full.bin
Looking for firmware.............: Found (buildwin, 320x240 px).
Looking for known version info...: None.
Looking for Openwin..............: Found.
Looking for LcdIniTbl............: Found.
Looking for known signatures.....: Found.

Your dpf seems to be compatible with currently unsupported model dx21334.
Sorry, this dpf in NOT supported by dpf-ax at the moment.
Work in progress. Check back later.

Thanks Superelchi

@petergunn

I would like to report a problem I am facing with st2205term/ax206term. For the 5x8 font defined in fonts.txt, the last column of # (column 5) along the width isn't used hence it is behaving more like 4x8. This results in truncated capital letter Y and letter w among the character set. I edited fonts.txt manually for these 2 characters to use 4x8. Fonts.txt is created by makefonts.c. I'm using a 128x128 frame.

What is the best way to fix this problem? Thanks in advance.

My findings sofar:

- Bought DX #27893
- Dump made with ax20dump.exe can be restored with SPI Programmer
- Dump made with python identify.py /dev/sg2 can be restored with restore.py

ubuntu:~/dpf-ax/trunk/fw# python identify.py /dev/sg2
Detecting & reading dpf flash...
Opening generic SCSI device '/dev/sg2'
Manufacturer: Winbond
Size        : 1 MB
Reading 100000 bytes...
Flash written to file 'full.bin'.

Looking for firmware.............: Found (buildwin, 128x128 px).
Looking for known version info...: None.
Looking for Openwin..............: Found.
Looking for LcdIniTbl............: Found.
Looking for known signatures.....: None.

Sorry, no matching dpf found.
But following models have a partial signature match: ['agk_violet']

- Flashed with python restore.py ../src/fw_disp_agk_violet.bin -f
- lcd4linux could not find USB0; had to change the .conf to use 'usbmon0' (?)
lcd4linux then run but there was nothing on the display; just a white screen.

ubuntu:~/dpf-ax/trunk/lcd4linux# ./lcd4linux -f ../dpf.conf -F
Found AX206 DPF
Got LCD dimensions: 128x128
Warning: Image Bgnd: fopen(bgnd.png) failed: No such file or directory
Warning: Image Bgnd: fopen(bgnd.png) failed: No such file or directory
Warning: Image Bgnd: fopen(bgnd.png) failed: No such.....etc

The dpf dims a little when lcd4linux starts, but thats it. No info or whatever....
Also, the dpf can no longer put put off, is that 'normal' ?

Did I forget something or maybe did something wrong?

termuser Wrote:
-------------------------------------------------------
> What is the best way to fix this problem? Thanks
> in advance.
I fixed the problem with a strategic placement of fseek

fseek(fd,7,SEEK_CUR);
if (fread(d->data,1,sz,fd)!=sz)

in load_font function. And for fonts.txt, between z and { characters, I added empty lines. I will wait for petergunn to comment on this.

Little further:

after flashing with "fw_disp_linkdelight.bin" it almost worked. For a moment I could read something like "LCD4LINUX" and then the screen filled with text and bars (Yeahhhh...) but it was all mirrored. Even the menu kind of worked but also mirrored :(
I've read a topic that this happened to others and the advice was to use an older dpflib. I tried that but can't get it compiled.


The original FW: DX 27893 dump

Bought at: DX.com

As far as I know it is an 1.5 inch 128x128 and the SPI tells me:

Cmd-9f: ID:0xef401400
Cmd-ab: ID:0x13131313
Cmd-90: ID:0xef13ef13
flash ID Winbond 25q80

If anyone has this dpf working I would be glad to hear how you got it going.

Ed

Edit:
Wow! Don't know why, but it works!
Again I compiled and tried to flash but now the restore.py gave me trouble. But because the bin's compiled OK I copied them to Windows (ohoh) and started to try them all with "SPI Programmer". The second one was a hit: "fw_disp_blue.bin" gave me "the eyes", great! Tried the menu-button and got a readable menu. Then started lcd4linux (hehe, back at Linux, pff) and lots of info readable on the display.
Thanks for this very nice hack!



Edited 1 time(s). Last edit at 05/22/2012 07:28AM by C4Vette.

@C4Vette

Try the attached file. It uses lcdblit.s from agk_violet and lcdinit.s which I created from lcdinitbl_tmp.txt. I modified dev_mode to 2 to enable identify.py's devel mode.
EDIT: Ok this is not needed anymore.

python identify.py ../../../dx27893.bin 
Looking for firmware.............: Found (buildwin, 128x128 px).
Looking for known version info...: None.
Looking for Openwin..............:
OpenWin        at 0x1280 (0x00069c), len 0x61, CRC = 0xd5efd5d9
Written to openwin_tmp.bin.
Looking for LcdIniTbl............:
Module 37:
LcdInit (Tbl)   at 0x14b1 (0x048181)
Module 52:
LcdScheduleTbl  at 0x14c9 (0x04978b), len 0x00
LcdContrastTbl  at 0x14ca (0x04978c), len 0x09
LcdContrastTb2  at 0x14d4 (0x049796), len 0x0b
LcdBacklightTbl at 0x14e0 (0x0497a2), len 0x16
LcdIniTbl       at 0x14f9 (0x0497bb), len 0x86, CRC = 0x4d507697
Written to lcdinitbl_tmp.txt.
Looking for known signatures.....:
OpenWin:   match at model agk_violet
None.

Sorry, no matching dpf found.
But following models have a partial signature match: ['agk_violet']

Edited 1 time(s). Last edit at 05/22/2012 08:03AM by ax206geek.

Hi,

thanks for the dx27893. I have one of these myself but forgot to add it. :-o
Will be available as new model "dx27893" in the next svn commit.

Just finished adding a new feature for those, who want to connect more than one display at the same time: USB iSerial Number adjustable in dpfs menu. Now its possible to identify each dpf by a unique serial number, e.g. in a udev rule. Will need a little more testing - but I hope to upload it in the next days...

BTW: works also with dealextreme model # 27894 (blue).

superelchi



Edited 1 time(s). Last edit at 05/22/2012 11:43AM by superelchi.

Thanks ax206geek for your help and trouble.

New display to toy around with!

Bought at: DX.com

FirmWare dump: full.bin

It's a 2.4" AX206 320x240
I've first made a dump and then tried all available FW's. The dpf seems to run because linux recognizes a "USB-display" when plugged-in.

In USB-mode lsusb shows: Bus 002 Device 023: ID 1908:0102 GEMBIRD
and in flashmode: Bus 002 Device 024: ID 1908:3318 GEMBIRD

SPI Programmer shows:
Cmd-9f: ID:0xc84014c8
Cmd-ab: ID:0x13131313
Cmd-90: ID:0xc813c813
flash ID in channel 1 is Apple 25Q80

FW fw_disp_focal.bin almost works: it uses 1/4 of the screen and all the lines are in reversed order; from bottom to top that is.
Even the menu kinda worked but has black bars between the items. That was a lot better than the original menu because that one was in Chinese!

Via linux:

python restore.py ../src/fw_disp_focal.bin -f

ubuntu:~/dpf-ax/trunk/fw# ./hiddetach
Detaching dpf at 2-2.1:1.0... done.
root@ubuntu:~/dpf-ax/trunk/fw# python restore.py ../src/fw_disp_focal.bin -f
Found AX206 DPF (bootloader)
Manufacturer: Apple
Size        : 1 MB
Erase full flash...
Flashing sector 0...
Flashing sector 1...
Flashing sector 2...
Flashing sector 3...
Flashing sector 4...
Flashing sector 5...
Executing applet..

Same result and after a reset of the dpf it doesn't start anymore.

Has anyone had more luck with this one?

Ed



Edited 1 time(s). Last edit at 05/23/2012 02:14AM by C4Vette.

Please read the earlier posts. dx21334 is being worked on.

C4Vette Wrote:
>
> Same result and after a reset of the dpf it
> doesn't start anymore.
>
> Has anyone had more luck with this one?
>
> Ed

Download my Dump file here and restore. is the same.

gabychan Wrote:
-------------------------------------------------------

>
> Download my Dump file
> here and restore. is the same.

Hi, thanks,

Do you mean with "is the same" that it is an original FW dump?
Then that won't change much because I made a dump myself as you can see above via "FirmWare dump: full.bin".
Or is your dump a hacked one and working with lcd4linux?

If the original dump, I can not help you over the DX does not work with lcd4linux.

Sorry

@C4Vette: Your dx21334 firmware seems to differ from other dx21334 firmware after running a diff with gabychan's firmware. Investigating with identify.py:

Looking for firmware.............: Found (buildwin, 320x240 px).
Looking for known version info...: None.
Looking for Openwin..............:
OpenWin        at 0x1280 (0x00064c), len 0x73, CRC = 0xf4729795
Written to openwin_tmp.bin.
Looking for LcdIniTbl............:
Module 35:
LcdInit !NOTBL! at 0x14a1 (0x048171)
Module 48:
LcdScheduleTbl  at 0x14dc (0x04968a), len 0x00
LcdContrastTbl  at 0x14dd (0x04968b), len 0x09
LcdContrastTb2  at 0x14e7 (0x049695), len 0x0b
LcdBacklightTbl at 0x14f3 (0x0496a1), len 0x16
LcdBacklightTb2 at 0x150a (0x0496b8), len 0x16
LcdIniTbl       at 0x1523 (0x0496d1), len 0xaa, CRC = 0xc70ac3d2
Written to lcdinitbl_tmp.txt.
Looking for known signatures.....:
None.

Sorry, no matching dpf found.

gabychan's dx21334 with identify.py:

Looking for firmware.............: Found (buildwin, 320x240 px).
Looking for known version info...: None.
Looking for Openwin..............:
OpenWin        at 0x1280 (0x00064c), len 0x6a, CRC = 0xe7bb71fc
Written to openwin_tmp.bin.
Looking for LcdIniTbl............:
Module 35:
LcdInit !NOTBL! at 0x14a1 (0x030971)
Module 48:
LcdScheduleTbl  at 0x1330 (0x031ce0), len 0x00
LcdContrastTbl  at 0x1331 (0x031ce1), len 0x09
LcdContrastTb2  at 0x133b (0x031ceb), len 0x0b
LcdBacklightTbl at 0x1347 (0x031cf7), len 0x16
LcdBacklightTb2 at 0x135e (0x031d0e), len 0x16
LcdIniTbl       at 0x1377 (0x031d27), len 0x183, CRC = 0x53c2379b
Written to lcdinitbl_tmp.txt.
Looking for known signatures.....:

Your dpf seems to be compatible with currently unsupported model dx21334.
Sorry, this dpf in NOT supported by dpf-ax at the moment.
Work in progress. Check back later.

Edited 2 time(s). Last edit at 05/24/2012 09:31AM by ax206geek.

ax206geek Wrote:
-------------------------------------------------------
> @C4Vette: Your dx21334 firmware seems to differ
> from other dx21334 firmware after running a diff
> with gabychan's firmware.

Right. Both are DX #21334 but have different firmware. AND: tried to flash C4Vette's dump to my 21334 (= same firmware as gabychan's). Not working. :-(

superelchi

C4Vette Wrote:
-------------------------------------------------------
>
>
> FW fw_disp_focal.bin almost works: it uses 1/4 of
> the screen and all the lines are in reversed
> order; from bottom to top that is.
> Even the menu kinda worked but has black bars
> between the items. That was a lot better than the
> original menu because that one was in Chinese!
>
> Same result and after a reset of the dpf it
> doesn't start anymore.
>
> Has anyone had more luck with this one?
>
> Ed

Did you try the pearl or pearl_landscape fw? I'm asking, because your original fw-dump at https://www.dropbox.com/s/mt6hfwyucnbxxbh/full.bin works on my pearl dpf...

superelchi

@superelchi

Thanks. I will try that next week when I'm back home and let you know.

FYI:

New version in SVN
- USB serial number adjustable in menu.
- New model dx27893.

superelchi

Hi all

Last week I received this dpf
http://dx.com/p/1-5-lcd-rechargeable-digital-usb-photo-frame-keychain-with-8m-memory-for-140-photos-silver-33624
http://dx.com/p/2-4-lcd-desktop-digital-photo-frame-and-calendar-27-picture-memory-storage-21334

Only want to share with you that sku 33624 (first one) works with last svn

Thank you for the job

Sergio (bcn too)

gabychan Wrote:
-------------------------------------------------------
> root@YAVDR:/home/gaby/dpf-ax/fw# python
> identify.py
> Usage: python identify.py dumpfile|dpf-devicenode
> root@YAVDR:/home/gaby/dpf-ax/fw# python
> identify.py full.bin
> Looking for firmware.............: Found
> (buildwin, 320x240 px).
> Looking for known version info...: None.
> Looking for Openwin..............: Found.
> Looking for LcdIniTbl............: Found.
> Looking for known signatures.....: Found.
>
> Your dpf seems to be compatible with currently
> unsupported model dx21334.
> Sorry, this dpf in NOT supported by dpf-ax at the
> moment.
> Work in progress. Check back later.
>
> Thanks Superelchi

Hi Sergio read this

Por el momento no es soportado el DX21334.

Saludos

@gabychan

Ok, thank you!

sergiosmail Wrote:
-------------------------------------------------------
> Hi all
>
> Last week I received this dpf
> http://dx.com/p/1-5-lcd-rechargeable-digital-usb-p
> hoto-frame-keychain-with-8m-memory-for-140-photos-
> silver-33624
> http://dx.com/p/2-4-lcd-desktop-digital-photo-fram
> e-and-calendar-27-picture-memory-storage-21334
>
> Only want to share with you that sku 33624 (first
> one) works with last svn
>
> Thank you for the job
>
> Sergio (bcn too)

Hi Sergio,

What fw-type did work for the 33624? if you send me the CRCs or a dump of the original fw I will add it to the list of known dpfs.

superelchi

Hi superelchi
if the file full.bin is the firmware you can find both files attached

BR,
Sergio

sergiosmail Wrote:
-------------------------------------------------------
> Hi superelchi
> if the file full.bin is the firmware you can find
> both files attached
>
> BR,
> Sergio
Hi Sergio, both files are identical. But it matches dx27893.



Edited 1 time(s). Last edit at 05/29/2012 07:23AM by ax206geek.

superelchi Wrote:
-------------------------------------------------------
> FYI:
>
> New version in SVN
> - USB serial number adjustable in menu.
How do we use this? Are we supposed to create a udev rule to name each device uniquely and then run the appropriate userland programs?



Edited 1 time(s). Last edit at 05/29/2012 07:24AM by ax206geek.

ax206geek Wrote:
-------------------------------------------------------
> How do we use this? Are we supposed to create a
> udev rule to name each device uniquely and then
> run the appropriate userland programs?

Exactly. Its only useful if you want to connect more than one display at a time. If all dpfs have same serial, they are detected in random order. For example: my ax206dpf graphlcd driver for VDR supports up to 4 displays which can be logically arranged to simulate a bigger display. Say: 2 hor landscape x 2 vert landscape = 640 x 480 pixel or 4 hor portrait = 320 x 960 pixel. By assigning different serials and an udev rule you can make sure first display ist upper left, second upper right, or whatever.

BTW: got dx21334 working. Needs some polishing, but will be ready in a couple of days (I hope).

superelchi