fi2 encoder/decoder

Hacki

359
EOS 80D

Re: fi2 encoder/decoder

« Reply #10 on: 21 / January / 2009, 15:07:46 »

Advertisements

~~I got it running under linux with some help of a friend~~ Actually he got it running - (seba-geek.de - DDoS his website a little, he'll be happy about some hits)

http://mighty-hoernsche.de/chdk/fi2encdec.tar.bz2

There ya go. Even with a makefile.

Logged

whim

2046
A495/590/620/630 ixus70/115/220/230/300/870 S95

Re: fi2 encoder/decoder

« Reply #11 on: 21 / January / 2009, 15:32:41 »

tried with attach+instructions from ewavr's Reply #7 on A590 101B, PID=0x0000315D

non-danced diskboot.bin -> pack.bat -> ps.fi2 -> "update error"
non-danced diskboot.bin -> pack.bat -> ps.fi2 -> dance -> "update error"
danced diskboot.bin -> pack.bat -> ps.fi2 -> "update error"
danced diskboot.bin -> pack.bat -> ps.fi2 -> dance -> "update error"

edit: now more understandable, i hope ...

« Last Edit: 21 / January / 2009, 15:59:24 by whim »

Logged

*Wikia FAQ *GCC Compiler Shell for Windows

ewavr

1057
A710IS

Re: fi2 encoder/decoder

« Reply #12 on: 21 / January / 2009, 15:38:17 »

Quote from: Hacki on 21 / January / 2009, 15:07:46

http://mighty-hoernsche.de/chdk/fi2encdec.tar.bz2
There ya go. Even with a makefile.

Yes, it works under Windows! (when I change in Makefile "-lz" to "libz.a"), SX100 boots.

Logged

ewavr

1057
A710IS

Re: fi2 encoder/decoder

« Reply #13 on: 21 / January / 2009, 15:44:12 »

Quote from: whim on 21 / January / 2009, 15:32:41

tried on A590 101B -> firm update error

With which version of packer?

Quote

should ps.fi2 be danced afterwards, maybe ?

Maybe no...

edit: "firm update error" means that PID or keys are invalid. If diskboot.bin is invalid, camera crashes.

« Last Edit: 21 / January / 2009, 15:56:47 by ewavr »

Logged

whim

2046
A495/590/620/630 ixus70/115/220/230/300/870 S95

Re: fi2 encoder/decoder

« Reply #14 on: 21 / January / 2009, 16:01:30 »

Quote

With which version of packer?

edit: see previous posts' edit: used archive+instructions from your post #7
edit2: used diskboot.bin freshly generated from trunk 688

wim

edit3: changes: pack.bat -> '-sys g9' to '-sys a590'
my.map -> 'HDR 0x000315A' to 'HDR 0x000315D'
then tested as per my previous post

« Last Edit: 21 / January / 2009, 16:16:36 by whim »

Logged

*Wikia FAQ *GCC Compiler Shell for Windows

whim

2046
A495/590/620/630 ixus70/115/220/230/300/870 S95

Re: fi2 encoder/decoder

« Reply #15 on: 21 / January / 2009, 16:24:22 »

@ewavr

found the solution: i stupidly assumed that the commented out PID in the makefile.inc was correct,

but dec 12662 is not 0x315D but 0x3176 ... starting new test cycle now

sorry,

wim

edit: Yes ! worked first time: unencoded diskboot.bin -> pack.bat -> ps.fi2 -> boots !!!!
looks like you can change 'probably not encoded for a590...' to 'NOT encoded for a590...'

« Last Edit: 21 / January / 2009, 16:40:27 by whim »

Logged

*Wikia FAQ *GCC Compiler Shell for Windows

ewavr

1057
A710IS

Re: fi2 encoder/decoder

« Reply #16 on: 21 / January / 2009, 16:44:37 »

Quote from: whim on 21 / January / 2009, 16:24:22

but dec 12662 is not 0x315D but 0x3176 ...

0x315D is PID for A720... Wiki says that PID for A590 is 0x3176.

Logged

whim

2046
A495/590/620/630 ixus70/115/220/230/300/870 S95

Re: fi2 encoder/decoder

« Reply #17 on: 21 / January / 2009, 16:55:02 »

@ewavr

yeah, forgot wiki page ... used calculator

Quote

(from platform/a590/sub/101b/makefile.inc)
#315D <<------------------- should be wiped
PLATFORMID=12662

PLATFORMOS=dryos
--- snip ---

again, sorry

wim

Logged

*Wikia FAQ *GCC Compiler Shell for Windows

PhyrePhoX

2254
make RAW not WAR

Re: fi2 encoder/decoder

« Reply #18 on: 22 / January / 2009, 12:51:49 »

alright, so this proves that memsets/ewavrs code is working 100% correctly.

what do you people suggest the next steps should be?
we could somehow write a dancingbits_v2 that "obfuscates" they keys...?
or we could extract & generate the keys on runtime/compilation on the autobuild. or we risk including them in svn, somehow encrypted/obfuscated (see dancing bits).
or there is a whole different idea i dont know of - all i know is, that fi2 encoding would simplify CHDK's use for dryos folks in a major way.

Logged

Flickr*
www.PhyreWorX.de
CHDK News @ Twitter

ewavr

1057
A710IS

Re: fi2 encoder/decoder

« Reply #19 on: 22 / January / 2009, 13:46:29 »

Quote from: PhyrePhoX on 22 / January / 2009, 12:51:49

alright, so this proves that memsets/ewavrs code is working 100% correctly.

memsets/~~ewavrs~~

Quote

what do you people suggest the next steps should be?

Hmm, maybe it must be included in CHDK, but in which form? Compiled executables or sources? If sources will be included, how about zlib sources, it must be also included? Someone working or planned to work on this?

Logged