Any developers interested in working on CHDK firmware for DSLRs ? - page 4 - DSLR Hack development - CHDK Forum supplierdeeply
« previous next »
Pages: 1 2 3 [4] 5 6 7 8 9 ... 21   Go Down

Any developers interested in working on CHDK firmware for DSLRs ?

  • 202 Replies
  • 104456 Views
*

Offline mx3

  • ****
  • 372
Re: Any developers interested in working on CHDK firmware for DSLRs ?
« Reply #30 on: 29 / January / 2008, 05:26:10 »
Advertisements
Quote from: RayeR on 29 / January / 2008, 05:22:52
Then I probably missed 30D decrypter. I tried all about 6 I have :) Where can I find it?

http://chdk.setepontos.com/index.php/topic,134.msg2461.html#msg2461
Logged
skype: max_dtc. ICQ: 125985663, email: win.drivers(at)gmail, eVB decompiler
*

Offline RayeR

  • *
  • 18
    • RayeR's homepage
Re: Any developers interested in working on CHDK firmware for DSLRs ?
« Reply #31 on: 29 / January / 2008, 16:15:34 »
Logged
Canon EOS 350D, PowerShot A95
*

Offline mx3

  • ****
  • 372
Re: Any developers interested in working on CHDK firmware for DSLRs ?
« Reply #32 on: 30 / January / 2008, 11:06:34 »
my friend asked one or two owners of DSLRs:
what would you want from your camera?
they said - nothing new revolutionary they do not expect from theirs cameras

so my question is - what new features do you expect?
I said - I yerstaday did 5000 shoots for timelapse movie
he said that resourse for DSLR is 20000 shots and laughed at my idea to make timelapse video
Logged
skype: max_dtc. ICQ: 125985663, email: win.drivers(at)gmail, eVB decompiler
*

Offline hoppsann

  • *
  • 12
Re: Any developers interested in working on CHDK firmware for DSLRs ?
« Reply #33 on: 30 / January / 2008, 16:20:13 »
Quote from: mx3 on 30 / January / 2008, 11:06:34
so my question is - what new features do you expect?

A bunch of posts above, I gave a wishlist.
Logged
*

Offline kwf

  • **
  • 72
Re: Any developers interested in working on CHDK firmware for DSLRs ?
« Reply #34 on: 31 / January / 2008, 11:19:06 »
Quote from: mx3 on 30 / January / 2008, 11:06:34
my friend asked one or two owners of DSLRs:
what would you want from your camera?
they said - nothing new revolutionary they do not expect from theirs cameras

so my question is - what new features do you expect?
I said - I yerstaday did 5000 shoots for timelapse movie
he said that resourse for DSLR is 20000 shots and laughed at my idea to make timelapse video

Well what is revolutionary? I would not like to install this update as the first one on my 350D, but when its stable, there are a lot of things which i might find useful:

- Enhanced bracketing e.g. +-5EV ? (e.g. for HDR)
- Auto ISO would be cool
- Focus bracketing would be cool also :)
- Focus adjustments
- DOF Calculator
- and as i forget to change ISO regulary, maybe warn me if i shot at ISO1600 in the middle of the day :)
Logged
*

Offline naplam

  • *
  • 25
  • EOS 400D
Re: Any developers interested in working on CHDK firmware for DSLRs ?
« Reply #35 on: 06 / February / 2008, 19:49:46 »
I have been trying to modify my camera firmware (EOS 400D), I made a modification -funny one, I found images that look like the sensor cleaning animation and modified it- but the firmware won't load, I guess there's a checksum somewhere, does pakwif or any tool have any info I can use to calculate the checksum and upload properly? Another issue i have: how can I be sure of the base address? right now I'm using 0xff810000 but there are lots of unreferenced strings which makes me guess the base address is wrong but on the other hand, I've seen the same results or worse with some firmwares I downloaded from here and also I've seen many absolute references in the code to FF8xxxx addresses so it's not too far off anyway. Right now the disassembly looks more or less ok but still a bit obscure to reverse-engineer for my taste. To sum up a) where is the checksum? b) any tips to make sure the base address is ok?
cheers
Logged
*

Offline naplam

  • *
  • 25
  • EOS 400D
Re: Any developers interested in working on CHDK firmware for DSLRs ?
« Reply #36 on: 06 / February / 2008, 20:07:36 »
Quote from: mx3 on 30 / January / 2008, 11:06:34
my friend asked one or two owners of DSLRs:
what would you want from your camera?
The only major thing we miss (that the firmware can fix) is a proper auto iso. The 40D introduced an autoiso mode that can still be enhanced, and its behaviour is a bit inconsistent anyway, other eos cameras simply don't have auto iso except in automatic modes, which we hardly use anyway. Something more flexible, like setting a minimum and maximum iso and maybe some more parameters would be quite nice.
Other enhancements are either unnecessary or quite minor, imho. Iso displayed on the screen would be nice, it's true you sometimes forget the iso you set until you notice the noise or high speed, but that's a minor feature. Calculators are a bit out of the question since they depend totally on the lens, you'd have to build a lens database or have the user input lens characteristics... not worth it.
Logged
*

Offline mx3

  • ****
  • 372
Re: Any developers interested in working on CHDK firmware for DSLRs ?
« Reply #37 on: 07 / February / 2008, 00:31:02 »
Quote from: naplam on 06 / February / 2008, 19:49:46
I have been trying to modify my camera firmware (EOS 400D), I made a modification -funny one, I found images that look like the sensor cleaning animation and modified it- but the firmware won't load, I guess there's a checksum somewhere, does pakwif or any tool have any info I can use to calculate the checksum and upload properly? Another issue i have: how can I be sure of the base address? right now I'm using 0xff810000 but there are lots of unreferenced strings which makes me guess the base address is wrong but on the other hand, I've seen the same results or worse with some firmwares I downloaded from here and also I've seen many absolute references in the code to FF8xxxx addresses so it's not too far off anyway. Right now the disassembly looks more or less ok but still a bit obscure to reverse-engineer for my taste. To sum up a) where is the checksum? b) any tips to make sure the base address is ok?
cheers


I analized 350D a litle and found 2 segments of code
first section must be loaded at 0x800000
second section at address ff810000

It seems you have to analize firmware update routine to be able to make modifications


attached is simple program I used to split file in case you don't have any
Logged
skype: max_dtc. ICQ: 125985663, email: win.drivers(at)gmail, eVB decompiler
*

Offline naplam

  • *
  • 25
  • EOS 400D
Re: Any developers interested in working on CHDK firmware for DSLRs ?
« Reply #38 on: 07 / February / 2008, 07:58:53 »
Quote from: mx3 on 07 / February / 2008, 00:31:02
I analized 350D a litle and found 2 segments of code
first section must be loaded at 0x800000
second section at address ff810000
Ah, great, thank you :) . I've been able to find the two sections on the 400D firmware v1.1.1 (the second section starts at 142ED0) and now that everything is loaded in the correct place I can see the strings nicely referenced. By the way, how do you "dissect" the firmwares? how do you know for sure where each section is beforehand? do you use any tools for that? i was able to determine where it is only because you told me where it was on the 350D.

Quote
It seems you have to analize firmware update routine to be able to make modifications
So you suggest that I modify the loader code to accept any firmware instead of making my firmware pass the checks? is that the way you do it for chdk? ah there's something else I'm not sure about, does the old firmware load and write the new firmware or is the new firmware loaded into the ram, called and then writes itself to flash?

Another thing, how do I find functions, events, and so on? I have names for several functions and some clues as to what they do thank to the assertions and some other strings but I'm at a loss for much of the rest of the code. And how do I find the so-called properties?

<edit> Hmm, RegisterEventProcedure and many more functions appear in "names" but not in functions and it looks like they're a bit offset from the real subroutines so they're logically not being recognised... i'll look into it. Maybe the flirt signature is not totally valid for this firmware?
« Last Edit: 07 / February / 2008, 08:37:30 by naplam »
Logged
*

Offline mx3

  • ****
  • 372
Re: Any developers interested in working on CHDK firmware for DSLRs ?
« Reply #39 on: 07 / February / 2008, 10:26:47 »
Quote from: naplam on 07 / February / 2008, 07:58:53
By the way, how do you "dissect" the firmwares? how do you know for sure where each section is beforehand? do you use any tools for that?
-I don't have information about structure of decrypted file.
-it seems firmware files for DSLR does not contain block structure (ie headers and bodies) so only way to dissect it properly ( and make it back ) is to analize firmware udpate code.
-no additional tolls were used to guess dissection process.
-All analysis was done with IDA ( several count of spliting file and loading it into IDA. of course it is not required to split it but I like to have independent sections to analyse. remember you mentioned unreferenced parts :-) )

Quote from: naplam on 07 / February / 2008, 07:58:53
Quote
It seems you have to analize firmware update routine to be able to make modifications
So you suggest that I modify the loader code to accept any firmware instead of making my firmware pass the checks?
we have to make such FW file wich will be accepted by camera. so we need to know algorithm of FW update procedure (we have it)

Quote from: naplam on 07 / February / 2008, 07:58:53
is that the way you do it for chdk?
no.
- update procedure for P&S cameras differs from DSLR one.
main difference : P&S updater code located on SD card ( while code for DSLR is stored in FLASH). actually after I have writen this I'm not so sure:-)

- I don't know how file is packed in P&S cameras.
some people have analysed it earlier (several years ago) and I don't want to analyse it. but I'm sure format is different

Quote from: naplam on 07 / February / 2008, 07:58:53
Another thing, how do I find functions, events, and so on?
IMO signature file is the best way.
« Last Edit: 07 / February / 2008, 10:32:18 by mx3 »
Logged
skype: max_dtc. ICQ: 125985663, email: win.drivers(at)gmail, eVB decompiler
Pages: 1 2 3 [4] 5 6 7 8 9 ... 21   Go Up
« previous next »
 

Related Topics