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

I have a proof-of-concept app similar to Slugterm that will read a USB keyboard directly and render on the picframe using libst2205. I'll release it once it gets a bit further along.

If you can figure out how to push images in real-time out to an AX20X or other device you might be able to adapt it for that as well.

-PG

Peter
Cool. I just checked slugterm page and that is exactly what I'm interested in and it shows root access.

Is there a way to make it so the lcd only would have 4 or 8 lines on it so we could have much bigger font size.

The font size on the picture frame where it shows the menu I can see no problems and is 8 lines and probably can hold 10-12 characters each line.

Here we go - an alpha release for testing/feedback is attached. Its written in C with minimal bloat and supports color, curses, etc. The keyboard mappings are configured in a text file that can be modified to support different keyboards.

To compile you need libst2205, libgd and librote. You should already have the first two installed as they are required for LCD4Linux but you may need to install librote (which doesn't seem to be in the debian repos).

cd /root
wget http://downloads.sourceforge.net/project/rote/rote/rote-0.2.8/rote-0.2.8.tar.gz
tar xvfz rote-0.2.8.tar.gz
cd rote-0.2.8/
./configure && make && make install

Then compile st2205term...

cd /root
tar xvfz st2205term-alpha-0.01.tgz
cd st2205term-alpha-0.01
./mak

Then try running it...

LD_LIBRARY_PATH=/usr/local/lib ./st2205term --font=small --picframe=/dev/sdb --keyboard=/dev/input/event0 --keymap=./us.kmap

Font options are tiny, small and large. There may be missing key defintions for things like keypads, function keys, etc. and the codes that are there may have to be remapped for non-US keyboards.

Let me know how it goes.

-PG



Edited 1 time(s). Last edit at 11/24/2010 12:48PM by petergunn.

Here is a slightly revised version with a better keymap file (spacebar should now work :-)

Jeff has kindly provided some web space so you can download from
http://jeff.doozan.com/debian/lcd/st2205term-alpha-0.02.tgz

-PG

Here is a picture of the picframe running lynx within st2205term...

http://jeff.doozan.com/debian/lcd/IMG_3670_640x480.JPG

http://jeff.doozan.com/debian/lcd/IMG_3667_640x480.JPG

-PG

Got my Shift3 today and having a bit of trouble with it.

1) Pictures lie. The USB plug is "backwards" like the others. (Coby) but also centered on the bottom... hardware revision. ;(
2) Came with CD, has "corrupted" single 2MB flash partition, so not a hidden CDROM partition version. (Have one of those as well from a while back)

dmesg:

[431274.460401] scsi 9:0:0:0: Direct-Access SITRONIX MULTIMEDIA 0.09 PQ: 0 ANSI: 0 CCS
[431274.461481] sd 9:0:0:0: Attached scsi generic sg1 type 0
[431274.471341] sd 9:0:0:0: [sdb] 4096 512-byte logical blocks: (2.09 MB/2.00 MiB)
[431274.474302] sd 9:0:0:0: [sdb] Write Protect is off
[431274.474312] sd 9:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[431274.474318] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[431274.486299] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[431274.486339] sdb: unknown partition table
[431274.522343] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[431274.522385] sd 9:0:0:0: [sdb] Attached SCSI removable disk

rat@pipsqueak:~/st2205tool$ ls -al /dev/disk/by-id/
lrwxrwxrwx 1 root root 9 2010-11-24 14:40 usb-SITRONIX_MULTIMEDIA-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 9 2010-11-20 18:26 usb-SITRONIX_MULTIMEDIA_50443984483BC810-0:0 -> ../../sdb

rat@pipsqueak:~/st2205tool$ ./hackfw.sh /dev/sdb
Interactive script to hack the firmware of your keychain photo
player.
No photoframe found there.
Sorry, there doesn't seem to be a device using the ST2205U chipset
at /dev/sdb.

rat@pipsqueak:~/st2205tool$ strings -a -8 whole-memory.bin | grep SITRONIX
SITRONIX CORP.
SITRONIXMULTIMEDIA 0.09
SITRONIX CORP.
SITRONIXMULTIMEDIA 0.09
SITRONIX CORP.
...
SITRONIXMULTIMEDIA 0.09
SITRONIX CORP.
SITRONIXMULTIMEDIA 0.09
rat@pipsqueak:~/st2205tool$

rat@pipsqueak:~/st2205tool$ ./phack -m /dev/sdb
No photoframe found there.

rat@pipsqueak:~/st2205tool$ sudo cat /dev/sdb > whole-memory.bin
rat@pipsqueak:~/st2205tool$ ls -la whole-memory.bin
-rw-r--r-- 1 rat rat 2097152 2010-11-24 15:16 whole-memory.bin
rat@pipsqueak:~/st2205tool$

rat@pipsqueak:~/st2205tool$ sudo ./phack -df original-fwimage.bin /dev/sdb
..
Firmware dumped.

rat@pipsqueak:~/st2205tool$ ls -la original-fwimage.bin
-rw-r--r-- 1 root root 65536 2010-11-24 15:18 original-fwimage.bin
rat@pipsqueak:~/st2205tool$


This one's frustrating. Anyone got any ideas?

Salt in the wound: The "relevant file" link is not just 404'ed, but the domain is offline. http://picframe.spritesserver.nl/wiki/index.php/Innovage-shift3

On that page: "phack -m does send text successfully."

rat@pipsqueak:~/st2205tool$ ./phack -m /dev/sdb
No photoframe found there.

Nope.

And....

"The script hackfw.sh does not recognize the device as m_innovage or m_innovage2 so it won't modify the firmware, but is able to back it up and display the message "baks r ok" on the LCD. "

Nope.

Hardware info: Board has a date: 2007.12.21
DG015
A-3B

Epoxy blob. No other identifying marks. Board is in two parts. Second part is the side control buttons.

Why not give the hack generating script a try?

You may also need to make the one line code change to main.c and recompile phack.

-PG

petergunn Wrote:
-------------------------------------------------------
> Why not give the hack generating script a try?

Whoops. Thought I had that in there.

rat@pipsqueak:~/st2205tool$ ./generate-hack.pl /dev/sdb hack/m_my_new_hack
Creating hack/m_my_new_hack...
using DA65=/home/rat/st2205tool/cc65/src/da65/da65
using PHACK=/home/rat/st2205tool/phack
Dumping firmware: /home/rat/st2205tool/phack -df fwimage.bin /dev/sdb
Expected response 8 on cmd 1, got 0x0!
Splitting firmware into 16k segments...
0+0 records in
0+0 records out
0 bytes (0 B) copied, 3.8284e-05 s, 0.0 kB/s
dd: `fwimage.bin': cannot skip to specified offset
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000415642 s, 0.0 kB/s
dd: `fwimage.bin': cannot skip to specified offset
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000422012 s, 0.0 kB/s
dd: `fwimage.bin': cannot skip to specified offset
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000447016 s, 0.0 kB/s
Error: Nothing to read from input file `fwimage-seg0.bin'
Locating CMP_VAR1 & CMP_VAR2...
Eeek! expected single match but found 0 - dont know what to do!

> You may also need to make the one line code change
> to main.c and recompile phack.

Fixed that, thanks... And unfortunately the Coby download link is broken right now. ;( I'm pretty sure now that's what this is...

rat@pipsqueak:~/st2205tool$ lsusb
Bus 004 Device 007: ID 1403:0001 Sitronix Digital Photo Frame

Same exact ID.

Garrgh! Heh...

Thanks for making me feel like I'm just ONE step away from getting this working, though. Better than I was about a half hour ago. ;)

Try running generate-hack.pl as root. I think its failing to dump the firmware due to permissions.

-PG

petergunn Wrote:
-------------------------------------------------------
> Try running generate-hack.pl as root. I think its
> failing to dump the firmware due to permissions.
>
> -PG

*le sigh* That was part of the problem.

So used to just jumping into SU mode I forget to sudo on this other box. (No SU/Root PW) and for some reason I never remember sudo -i when I need to ;)

rat@pipsqueak:~/st2205tool$ sudo ./phack -m /dev/sdb
Expected response 8 on cmd 1, got 0xff!

Screen: baks r ok

I definitely have the Shift3.

Trying your hack script since I have no chance in downloading the files they had in the wiki. "Eeeek!" on the screen. Device reset. Replugged.

Ok, just a sec...
libst2205: detected device, 128x128, 24 bpp.
Found device: 128x128, 24 bpp

Unplugged, got prompt. Device behaving as normal. Trying to get LCD4Linux to run now.

Grabbed your sample, edited html out, fixed the port... and now I'm stuck on this:

rat@pipsqueak:~/lcd4linux-0.11.0-SVN$ sudo ./lcd4linux -F -v -f lcd4linux.conf
Version 0.11.0-SVN-965 starting
security error: owner and/or group of 'lcd4linux.conf' don't match
security error: group or other have access to 'lcd4linux.conf'

rat@pipsqueak:~/lcd4linux-0.11.0-SVN$ ./lcd4linux -F -v -f lcd4linux.conf
Version 0.11.0-SVN-965 starting
security error: group or other have access to 'lcd4linux.conf'

I'm a bit baffled.

rat@pipsqueak:~/lcd4linux-0.11.0-SVN$ ls -la lcd4linux.*
-rw-r--r-- 1 rat rat 10413 2009-01-12 22:54 lcd4linux.c
-rw-r--r-- 1 rat rat 3190 2010-11-24 16:22 lcd4linux.conf
-rw-r--r-- 1 rat rat 23163 2009-01-13 07:15 lcd4linux.conf.sample
-rw-r--r-- 1 rat rat 285 2000-04-03 12:31 lcd4linux.kdelnk
-rw-r--r-- 1 rat rat 543 2008-12-31 01:05 lcd4linux.lsm
-rw-r--r-- 1 rat rat 26652 2010-11-20 17:42 lcd4linux.o
-rw-r--r-- 1 rat rat 2306 2008-12-31 01:05 lcd4linux.xpm

Ran as persistent root:

root@pipsqueak:/home/rat/lcd4linux-0.11.0-SVN# ./lcd4linux -F -v -f lcd4linux.conf
Version 0.11.0-SVN-965 starting
security error: owner and/or group of 'lcd4linux.conf' don't match
security error: group or other have access to 'lcd4linux.conf'

Totally lost now.

As root try:

chmod 600 lcd4linux.conf

Also, I see you have a 24-bit device. You will probably have to edit the spec file and change it from 16-bit color. Then reflash specifying your original un-hacked firmware.

I would...

sudo -s # to become root
./phack -uf original-fwimage.bin /dev/sdb # back to original firmware
vi generate-hack.pl # change CONF_BPP=16 to CONF_BPP=24

Then run generate-hack.pl again.

-PG



Edited 3 time(s). Last edit at 11/24/2010 05:06PM by petergunn.

Peter
I'm stuck at this, can you check to make sure it's the right tar command?

Then compile st2205term...

cd /root
tar xvfz st2205term-alpha-0.01.tgz

Would this be the right way to download that file

wget http://forum.doozan.com/file.php?2,file=40,filename=st2205term-alpha-0.01.tgz,download=1 >st2205term-alpha-0.01.tgz

Download the alpha2 version: http://jeff.doozan.com/debian/lcd/st2205term-alpha-0.02.tgz

wget http://jeff.doozan.com/debian/lcd/st2205term-alpha-0.02.tgz
tar xvfz st2205term-alpha-0.02.tgz
cd st2205term-alpha-0.02
./mak

-PG



Edited 2 time(s). Last edit at 11/24/2010 05:20PM by petergunn.

root@pipsqueak:/home/rat/lcd4linux-0.11.0-SVN# chmod 600 lcd4linux.conf
root@pipsqueak:/home/rat/lcd4linux-0.11.0-SVN# ls -la lcd4linux.conf
-rw------- 1 rat rat 3190 2010-11-24 16:22 lcd4linux.conf
root@pipsqueak:/home/rat/lcd4linux-0.11.0-SVN# ./lcd4linux -F -v -f lcd4linux.conf
Version 0.11.0-SVN-965 starting
security error: owner and/or group of 'lcd4linux.conf' don't match
root@pipsqueak:/home/rat/lcd4linux-0.11.0-SVN#

I decide to try to remake it again as root.

root@pipsqueak:/home/rat/lcd4linux-0.11.0-SVN/lcd4linux-0.11.0-SVN# ./lcd4linux -F -v -f lcd4linux.conf Version 0.11.0-SVN-965 starting
security error: group or other have access to 'lcd4linux.conf'

Chmod as above.

root@pipsqueak:/home/rat/lcd4linux-0.11.0-SVN/lcd4linux-0.11.0-SVN# chmod 600 lcd4linux.conf
root@pipsqueak:/home/rat/lcd4linux-0.11.0-SVN/lcd4linux-0.11.0-SVN# ./lcd4linux -F -v -f lcd4linux.conf
Version 0.11.0-SVN-965 starting
libst2205: detected device, 128x128, 24 bpp.


Device doesn't do anything but hang and garbage spews. Gonna try your firmware fix.

(Following new instructions now.)



Edited 1 time(s). Last edit at 11/24/2010 05:26PM by rat.

rat, I think you are pretty close to hacking it. Its probably hanging because the screen depth is wrong in the hack.

Try reverting to the original firmware, modify generate-hack.pl and generate a new 24-bit hack.

-PG

Peter
You are amazing!
You did it!
Very cool.
You , Jeff and Gorgone have turned our dockstars into an amazing device. Thanks guys.

What is the way to get this program to start on start up?

This is my current rc.local what would be the line to add in this so I get root access like this.
#!/bin/bash
rdate ptbtime1.ptb.de >/dev/null &
echo 2 > /proc/cpu/alignment
echo default-on > /sys/class/leds/dockstar\:orange\:health/trigger
echo none > /sys/class/leds/dockstar\:orange\:misc/trigger
mount -a
/usr/local/bin/camstart &
/usr/bin/startx < /dev/null > /dev/null 2>&1 &
/install/lcd4linux-0.11.0-SVN/lcd4linux -f /root/lcd4linux-0.11.0-SVN/lcd4linux.conf
exit 0



Edited 2 time(s). Last edit at 11/24/2010 05:52PM by rgtaa.

Generated a new hack...

Got a new message on the screen this time.

"Yay! \o/"

Still hung when it asked me to reconnect the device. Disconnecting gives me a flood of readline errors.

Making sure I got the original firmware on the device, reflashed it to backup, tried to run lcd4linux:

root@pipsqueak:/home/rat/lcd4linux-0.11.0-SVN/lcd4linux-0.11.0-SVN# ./lcd4linux -F -v -f lcd4linux.conf
Version 0.11.0-SVN-965 starting
Unable to get parm_block
st2205: cannot open st2205 device /dev/sdb

Looks about right.

Starting over after nuking everything but a couple of firmware images just in case. Permissions have been a constant problem all along so I'm just redoing it as root.

my dmesg output is *identical* to yours, which makes this even more frustrating. Can't hack, "baks r ok"... Next step.

Did svn checkout, grabbed generate-hack, chmod'ed it, ran it... got a different set of errors this time.

root@pipsqueak:/home/rat/lcd/st2205tool# ./generate-hack.pl /dev/sdb hack/m_shift3
Creating hack/m_shift3...
using DA65=/home/rat/lcd/cc65/src/da65/da65
using PHACK=/home/rat/lcd/st2205tool/phack
Dumping firmware: /home/rat/lcd/st2205tool/phack -df fwimage.bin /dev/sdb
..
Firmware dumped.
Splitting firmware into 16k segments...
1+0 records in
1+0 records out
16384 bytes (16 kB) copied, 0.00011883 s, 138 MB/s
1+0 records in
1+0 records out
16384 bytes (16 kB) copied, 0.000142721 s, 115 MB/s
1+0 records in
1+0 records out
16384 bytes (16 kB) copied, 0.00016007 s, 102 MB/s
1+0 records in
1+0 records out
16384 bytes (16 kB) copied, 0.000138533 s, 118 MB/s
ERROR: dissessembly of fwimage-seg0.bin failed!

Moving on to Coby DP152 Modifications... Changed return value, make install, downloaded Coby files from here, extracted, edited generate-hack to change CONF_BPP=16 value to 24, nuked m_shift3 folder, trying again.

Same messages as before.

I think I'm just gonna have to give up and get one of those Coby clips...

Ugh.

> ERROR: dissessembly of fwimage-seg0.bin failed!

Did you remember to compile the da65 disassembler? This error means the following command failed...

cd /home/rat/lcd/st2205tool/hack/m_shift3 
/home/rat/lcd/cc65/src/da65/da65 -S 0x4000 --cpu 65C02 fwimage-seg0.bin

Might be worth trying to run that directly and see if you get more info.

-PG

rgtaa Wrote:
-------------------------------------------------------

> What is the way to get this program to start on
> start up?

If you want to hack it into /etc/rc.local then it would be something like:

LD_LIBRARY_PATH=/usr/local/lib ./st2205term --font=tiny --picframe=/dev/sdb --keyboard=/dev/input/event0 --keymap=./us.kmap </dev/null >/dev/null 2>&1 &

Add it somewhere between "mount -a" and "exit 0".

You might also set the prompt to be shorter "PS1='# ' LD_LIBRAR..." on the same line if you want.

You will need the picframe connected at boot for it to work, but you can plug in and remove the keyboard whenever you want.

-PG



Edited 1 time(s). Last edit at 11/24/2010 06:15PM by petergunn.

petergunn Wrote:
-------------------------------------------------------
> Might be worth trying to run that directly and see
> if you get more info.

Hrmmm...

Gave me a file not found error. Could have sworn I compiled it all. And wow. It's in my history, but I guess the compile got interrupted somehow.

Deleted m_shift3 and trying again.

Massive errorspam like before. Attached as file.

Peter
I still can't get it to work, I would like the shorter prompt, not sure what to add exactly, could you look at my rc.local and just add the line to it so I will just cut and paste.
I wasn't sure if it needs to have added the directory thing, since I have to use the libary line from this directory:
cd st2205term-alpha-0.02

I don't need this line anymore ,right?
/install/lcd4linux-0.11.0-SVN/lcd4linux -f /root/lcd4linux-0.11.0-SVN/lcd4linux.conf

I see it has tiny font is there a way to make font a little bigger?


this is my current rc.local

#!/bin/bash
rdate ptbtime1.ptb.de >/dev/null &
echo 2 > /proc/cpu/alignment
echo default-on > /sys/class/leds/dockstar\:orange\:health/trigger
echo none > /sys/class/leds/dockstar\:orange\:misc/trigger
mount -a
/usr/local/bin/camstart &
#/usr/bin/startx < /dev/null > /dev/null 2>&1 &
#/install/lcd4linux-0.11.0-SVN/lcd4linux -f /root/lcd4linux-0.11.0-SVN/lcd4linux.conf
LD_LIBRARY_PATH=/usr/local/lib ./st2205term --font=tiny --picframe=/dev/sdb --keyboard=/dev/input/event0 --keymap=./us.kmap </dev/null >/dev/null 2>&1 &

exit 0



Edited 3 time(s). Last edit at 11/24/2010 06:39PM by rgtaa.

Went ahead and tried it despite the errorspam. Hung just like before. Gah...

This is basically what happens when LCD4Linux is executed:

root@pipsqueak:/home/rat/lcd/lcd4linux-0.11.0-SVN# ./lcd4linux -F -v -f lcd4linux.conf
Version 0.11.0-SVN-965 starting
libst2205: detected device, 128x128, 24 bpp.

(hangs here, both in term and via battery charging indicator on screen)

Disconnecting cable results in this:

initializing layout 'mylayout'
widget 'Uname': Class 'text', Parent '<root>', Layer 1, Row 0, Col 0
widget 'Uptime': Class 'text', Parent '<root>', Layer 1, Row 1, Col 0
widget 'Temp1': Class 'text', Parent '<root>', Layer 1, Row 2, Col 0
widget 'Temp2': Class 'text', Parent '<root>', Layer 1, Row 3, Col 0
widget 'Temp3': Class 'text', Parent '<root>', Layer 1, Row 4, Col 0
widget 'Busy': Class 'text', Parent '<root>', Layer 1, Row 5, Col 0
widget 'BusyBar': Class 'bar', Parent '<root>', Layer 1, Row 5, Col 5
widget 'RAID': Class 'text', Parent '<root>', Layer 1, Row 7, Col 0
widget 'md0': Class 'text', Parent '<root>', Layer 1, Row 8, Col 0
widget 'md1': Class 'text', Parent '<root>', Layer 1, Row 9, Col 0
widget 'md2': Class 'text', Parent '<root>', Layer 1, Row 10, Col 0
widget 'UPS': Class 'text', Parent '<root>', Layer 1, Row 12, Col 0
widget 'LOADPCT': Class 'text', Parent '<root>', Layer 1, Row 13, Col 0
widget 'TIMELEFT': Class 'text', Parent '<root>', Layer 1, Row 14, Col 0
widget 'ITEMP': Class 'text', Parent '<root>', Layer 1, Row 15, Col 0
i2c_sensors: unable to autodetect i2c sensors!
readline requested line 8 but file only had 2 lines
readline requested line 9 but file only had 2 lines
readline requested line 5 but file only had 2 lines
readline requested line 6 but file only had 2 lines
readline requested line 3 but file only had 2 lines
readline couldn't open file '/var/log/apcupsd.status'
readline couldn't open file '/var/log/apcupsd.status'
readline couldn't open file '/var/log/apcupsd.status'
readline requested line 8 but file only had 2 lines
readline requested line 9 but file only had 2 lines
readline requested line 5 but file only had 2 lines
readline requested line 6 but file only had 2 lines
readline requested line 3 but file only had 2 lines
readline couldn't open file '/var/log/apcupsd.status'
readline couldn't open file '/var/log/apcupsd.status'
readline couldn't open file '/var/log/apcupsd.status'


Wanna call it, PG? :) Verdict: Don't buy the Shift3?

rat Wrote:
-------------------------------------------------------

> Deleted m_shift3 and trying again.
>
> Massive errorspam like before. Attached as file.

Looks like generate-hack.pl succeeds in creating a hack, then it cd's to the hack directly and runs the 'assembleme' script to compile the hack which generates all the errors. The assembleme script tries to compile all the m_* hacks and not just he new one and all the errors you see are actually for the m_coby_dp152 hack where the creator probably used a different assembler thats not compatible with crasm.

I dont see assembleme trying to compile m_shift003 at all? You might want to verify the directory has been created and then compile manually to see more output...

cd hack
mv m_coby_dp152 xxx_m_coby_dp152 # disable coby 152 hack
./assembleme

I still think this unit is probably hackable :-)

-PG

rgtaa Wrote:
-------------------------------------------------------

> I don't need this line anymore ,right?
> /install/lcd4linux-0.11.0-SVN/lcd4linux -f
> /root/lcd4linux-0.11.0-SVN/lcd4linux.conf

nope - that can go or be commented out

> I see it has tiny font is there a way to make
> font a little bigger?

--font=small or --font=large

> LD_LIBRARY_PATH=/usr/local/lib ./st2205term
> --font=tiny --picframe=/dev/sdb
> --keyboard=/dev/input/event0 --keymap=./us.kmap
> /dev/null 2>&1 &

Where is the st2205term-alpha-0.02 directory? You need full paths - if its in /root...

PS1='# ' LD_LIBRARY_PATH=/usr/local/lib /root/st2205term-alpha-0.02/st2205term --font=small --picframe=/dev/sdb --keyboard=/dev/input/event0 --keymap=/root/st2205term-alpha-0.02/us.kmap </dev/null >/dev/null 2>&1 &

-PG

Peter!

Oh YEAH! :)
Thanks bro!

petergunn Wrote:
-------------------------------------------------------
> rat Wrote:
> --------------------------------------------------
> -----
>
> > Deleted m_shift3 and trying again.
> >
> > Massive errorspam like before. Attached as
> file.
>
> Looks like generate-hack.pl succeeds in creating a
> hack, then it cd's to the hack directly and runs
> the 'assembleme' script to compile the hack which
> generates all the errors. The assembleme script
> tries to compile all the m_* hacks and not just he
> new one and all the errors you see are actually
> for the m_coby_dp152 hack where the creator
> probably used a different assembler thats not
> compatible with crasm.
>
> I dont see assembleme trying to compile m_shift003
> at all? You might want to verify the directory has
> been created and then compile manually to see more
> output...
> I still think this unit is probably hackable :-)
>
> -PG


Dir was created, files were dumped and it had something for hackfw to flash onto the lcd. Renamed the dir, generated different files to flash to the lcd after the original was reapplied... same issues as before: Screen and terminal hangs, LCD4linux hangs exactly the same as before.

I'm starting to think this is a case of the Shift3 being a kissing cousin of the Coby DP152 but has enough differences to create problems.

If you think all the DP152's are still hackable, I'm probably just going to give up and order one of those now. (shudder) Pink... ugh. (I much prefer the look of the original DP151SX's but those aren't guaranteed to be hackable now.)

rat Wrote:
-------------------------------------------------------
> Dir was created, files were dumped and it had
> something for hackfw to flash onto the lcd.
> Renamed the dir, generated different files to
> flash to the lcd after the original was
> reapplied... same issues as before: Screen and
> terminal hangs, LCD4linux hangs exactly the same
> as before.

Did you modify generate-hack.pl so that spec file ends up with 24bpp rather than 16bpp?

When I created the script my picframe kept hanging as well and it was because I was setting 24bpp when my frame was a 16bpp one.

> I'm starting to think this is a case of the Shift3
> being a kissing cousin of the Coby DP152 but has
> enough differences to create problems.

Its possible but lets double check the config - can you attach the generate-hack.log and spec file from the m_ directory?

> If you think all the DP152's are still hackable,
> I'm probably just going to give up and order one
> of those now. (shudder) Pink... ugh. (I much
> prefer the look of the original DP151SX's but
> those aren't guaranteed to be hackable now.)

No idea. I bought a DP151 off amazon and it turned out to be a DP151BW that appears as a CDROM and in not hackable - thats going to be an Xmas present for someone. I got all my DP152s and an Innovage generic off ebay.

Amazon has blue, red and pink DP152. The price varies but I think I remember blue as the cheapest (~$10 shipped). If you order the blue one you can tell from the box if its hackable if it has UPC code 7-16829-61152-4 like mine. Or get one off ebay where you can ask the seller before purchasing.

I wouldn't give up on the shift3 yet tho. It just has to work once.

-PG

Peter

I tried large font but small seems to work and it didn't hang when I did apt-get update.



Edited 1 time(s). Last edit at 11/24/2010 07:34PM by rgtaa.

rgtaa Wrote:
-------------------------------------------------------
> Peter
>
> I tried large font but small seems to work and it
> didn't hang when I did apt-get update.

So all good now?

-PG

petergunn Wrote:
-------------------------------------------------------
> Did you modify generate-hack.pl so that spec file
> ends up with 24bpp rather than 16bpp?

Yep. ;(

> Its possible but lets double check the config -
> can you attach the generate-hack.log and spec file
> from the m_ directory?

Attached. I see the process was interrupted on yet another model type. I'll try disabling that one too later.

> No idea. I bought a DP151 off amazon and it turned
> out to be a DP151BW that appears as a CDROM and in
> not hackable - thats going to be an Xmas present
> for someone. I got all my DP152s and an Innovage
> generic off ebay.

Funny that once I had given up and just decided to do some random image searches, I found a listing on eBay for a DP151 with the package clearly indicating that it was a DP151SX model pre v7. (Extended image support and supported OS lists) And in white to match the dock. I'll keep working on the Shift3 though.

> I wouldn't give up on the shift3 yet tho. It just
> has to work once.

Funny thing is, even when the original firmware is applied, phack works just fine. Too bad it's got a 9 character one line limit on what it can display of text via that method.

If anything, this thread's gonna be probably the only source of reliable info for anyone planning to do the Shift3 LCD hack. ;)