A590IS porting...

  • 968 Replies
  • 248266 Views
*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: First boot: a failure!
« Reply #20 on: 02 / October / 2008, 04:05:59 »
Advertisements
@brake

congrats, great work !

the 'qemu-encoded' and the 'brake-encoded' versions show small differences at the end of the file though:

Quote
26540: D7 00 00 51 7D 00 F9 FF-1C (eof)                         <-- 'brake-encoded'

26540: D7 00 00 FF FF 00 FF FF-00 00 00 00 00 00 00 00    <-- 'qemu-encoded'
..... more trailing zeroes

does this mean that the non-identical bytes are spurious (like the trailing zeroes in 'qemu-encoded')
and can be chopped off ? 
could you - or anybody else who owns a NewDryOs cam (ma_jk ?) - please check this ?

wim

*

Offline brake

  • *
  • 23
  • IXUS90IS / SD790IS
Re: First boot: a failure!
« Reply #21 on: 02 / October / 2008, 04:44:00 »
I cut them off and it still works. That example you gave is interesting actually because it looks like my code is actually acting on data (15x encoding of 00 00 00 00 00 00 00 00 should give some permutation of the following:

Code: [Select]
0x3000: 0xffffff00      0xffffa0a0      0x00ffffff      0xa000ffff
0x3010: 0xff00a0ff      0xffffffff      0xffffff00      0xffffa0a0
0x3020: 0x00ffffff      0xa000ffff      0xff00a0ff      0xffffffff

unless there's other data there).

What does the unencoded image look like at that line?

« Last Edit: 02 / October / 2008, 04:45:49 by brake »

*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: First boot: a failure!
« Reply #22 on: 02 / October / 2008, 05:37:42 »
@brake

last line in hexedit of unencoded diskboot.bin (that you supplied):
Quote
26540: FF FF FF FF

i hope that's what you meant, I only used the bins that you supplied

besides in your cam, did you also check DEcoding in the qemu emulation ?


wim

*

Offline brake

  • *
  • 23
  • IXUS90IS / SD790IS
Re: First boot: a failure!
« Reply #23 on: 02 / October / 2008, 05:59:53 »
Yeah I have. Decoding is just removing the 00 from the front and applying the encryption once, so yeah, I restored one the firmware I created with my app and decoded using qemu and it worked.

I just fixed up the code so that it shouldn't leave any trailing stuff in the encode or decode now.

[files removed - get update in last reply]
« Last Edit: 03 / October / 2008, 00:47:10 by brake »


*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: First boot: a failure!
« Reply #24 on: 02 / October / 2008, 06:26:16 »
@brake

excellent ! i'll now test your stuff by compiling/encoding/padding a modified udumper for NewDryOS
which dumps not just 4 Meg, but the entire firmware.
I'll attach it here when done.

wim

edit: attached nudumper.zip contains diskboot.bin & empty.dum - put both on empty, CHDK-bootable disk
       changes vs. chr's udump08:
       - removed led blinking
       - dumps entire firmware (begin of firmware to FFFF FFFF)
       - sources (+ .bat to compile under Win32) included in archive
« Last Edit: 02 / October / 2008, 06:52:17 by whim »

*

Offline ma_jk

  • **
  • 60
Re: First boot: a failure!
« Reply #25 on: 02 / October / 2008, 07:46:57 »
A quick compile, just in case someone would like to give a try encoding their builds.

*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: First boot: a failure!
« Reply #26 on: 02 / October / 2008, 08:08:32 »
thanks ma_jk !

could you test the new udumper in the post before yours? TIA

BTW did you use gcc for that ? my compile with Borland C++ 5.5 is 27K, even after upx --ultra-brute !

wim

edit: never mind, i see: VisualStudio 2005
« Last Edit: 02 / October / 2008, 08:11:17 by whim »

*

Offline ma_jk

  • **
  • 60
Re: First boot: a failure!
« Reply #27 on: 02 / October / 2008, 08:21:38 »
this is what i got.  :)

ive VS2005 installed on this comp...
« Last Edit: 02 / October / 2008, 09:53:13 by ma_jk »


*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: First boot: a failure!
« Reply #28 on: 02 / October / 2008, 09:27:54 »
@ma_jk

your dump looks pretty peculiar, it seems to miss the first part, but does contain
(part of) a readable dump  ???
Are you sure you copied empty.dum and diskboot.bin to an EMPTY bootable card ?
Udumper is really 'primitive', you see, it doesn't know anything about filesystems
(which is not surprising considering it's effectively only 175 bytes 'big' )
it just starts dumping from sector 2048 on the card; that's about 1 mb from the
beginning of the card. So if there's more than 1mb on the card when your copying
empty.dum on it it will overwrite (part of) already existing data ...

on the other hand, if your card WAS empty, then this udumper is no good ...

wim

*

Offline ma_jk

  • **
  • 60
Re: First boot: a failure!
« Reply #29 on: 02 / October / 2008, 09:30:44 »
try now.  :)
« Last Edit: 02 / October / 2008, 09:53:25 by ma_jk »

 

Related Topics