500d development - page 39 - DSLR Hack development - CHDK Forum supplierdeeply
« previous next »
Pages: 1 ... 34 35 36 37 38 [39] 40 41 42 43 44 ... 249   Go Down

500d development

  • 2487 Replies
  • 901280 Views
*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #380 on: 25 / February / 2011, 18:12:32 »
Advertisements
I started looking through the 500d firmware dump in IDA Pro today, found 17 memory addresses all pertaining to qscale and a few hdmi (and vga) settings. should I just be recording these in the stubs.s file? I guess I don't know how to implement them. Here's the settings I found today:

Code: [Select]
NSTUB( 0xFF17BCD4, mvrSetQscale)
NSTUB( 0xFF17BCFC, mvrSetQscaleYC)
NSTUB( 0xFF17BD34, mvrSetDeblockingFilter)
NSTUB( 0xFF17BD6C, mvrSetLimitQScale)
NSTUB( 0xFF17BDA4, mvrSetDefQScale)
NSTUB( 0xFF17BDC0, mvrSetTimeConst)
NSTUB( 0xFF17BDDC, mvrSetFullHDOptSize)
NSTUB( 0xFF17BF24, mvrSetHDOptSize)
NSTUB( 0xFF17BF5C, mvrSetVGAOptSize)
NSTUB( 0xFF17BF94, mvrSetGopOptSizeFULLHD)
NSTUB( 0xFF17BFDC, mvrSetGopOptSizeHD)
NSTUB( 0xFF17C024, mvrSetGopOptSizeVGA)
NSTUB( 0xFF17C06C, mvrSetD_FULLHD)
NSTUB( 0xFF17C1A8, mvrSetD_VGA)
NSTUB( 0xFF17C218, mvrFixQScale)
NSTUB( 0xFF17C1E0, mvrSetDefDBFilter)
NSTUB( 0xFF17C238, mvrSetPrintMovieLog)

This IDA stuff is pretty intense... so much to go through. I looked up the AE_MODE_MOVIE_ON andAE_MODE_MOVIE_OFF locations and there were a couple more settings / addresses I'm gonna pull out, maybe something to work with?

how do we implement these settings now? Is the stubs.s file just for our reference? I don't think any files actually access anything in them. Should I just define new prop values for ae_mode_movie_on and off in property.h and implement it from there? still a little confused on all of this.
Logged
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr
*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: 500d development
« Reply #381 on: 25 / February / 2011, 18:30:29 »
Quote
NSTUB( 0xFF17BCD4, mvrSetQscale)

Those are functions. You need to figure out which parameters does it take, and you may try call it. Do not call it until you understand what it does (some of them may be dangerous) and what parameters it takes. It can be risky.

Yes, the value you write in the stubs file is used when you reference that name. The actual code you are calling is in the original firmware (and not duplicated in autoexec.bin).

Quote
AE_MODE_MOVIE_ON and AE_MODE_MOVIE_OFF
These may be messages printed by DebugMsg in the log file, so you can use them to find out which part of code writes them. Then try to understand what that code does.

Properties are a different beast: usually you can find them with prop spy.

Start reading from here:
http://magiclantern.wikia.com/wiki/550d_dev
http://magiclantern.wikia.com/wiki/2.0.4_AJ
« Last Edit: 25 / February / 2011, 18:33:18 by a1ex »
Logged
*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #382 on: 25 / February / 2011, 18:51:16 »
Thanks man. I'm still not sure what I'm looking at but I'm just picking out strings I recognize. I ran some chdk ida file that supposedly cleaned the code up, but I'm not sure if I can tell a difference. It's all just a fun learning experience to me :)

so I need to go back and find the two values associated with each of those things I found before?
Logged
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr
*

chuchin

Re: 500d development
« Reply #383 on: 25 / February / 2011, 19:32:27 »
NSTUB( 0xFF17BDC0, mvrSetTimeConst, time const seem to away be related to fps.
Logged
*

alins

Re: 500d development
« Reply #384 on: 25 / February / 2011, 20:28:09 »
Quote from: chuchin on 25 / February / 2011, 19:32:27
NSTUB( 0xFF17BDC0, mvrSetTimeConst, time const seem to away be related to fps.

sorry chuchin, mind explaining this a little bit...are you saying by playing with this function you can change the FPS?
Logged
*

chuchin

Re: 500d development
« Reply #385 on: 25 / February / 2011, 20:55:36 »
I was looking at some gamers code the other day, and it used term like constant time when it related to frames per second. Don't know if it's the same with canon's code. I think Hudson also tried to use it to change fps. I don't have any of the files with me right now but I think it was in the early debug.c code.
Logged
*

alins

Re: 500d development
« Reply #386 on: 25 / February / 2011, 23:33:59 »
yes, i found hudson's code and played with a it a little bit with no luck. the thing is in 5d code he has a struct for movie and i don't know what's the address for it in 500d assuming the struct IS in 500d and is the same
Logged
*

Offline Coutts

  • *****
  • 538
  • www.flickr.com/couttsphotog
    • Flickr
Re: 500d development
« Reply #387 on: 26 / February / 2011, 01:37:26 »
I ran across a shooting mode address earlier today. One of the variations was for movie. Ill find it tomorrow and pdt the code. Im at a party and a little intoxicated lol can't do anything tonight. I'll post everything at that sub and hopefully someone will be able to figure it out.
Logged
Canon 5d
Canon 50mm f/1.8
Sigma 24mm f/1.8

Flickr
*

Offline silasje1

  • *
  • 39
Re: 500d development
« Reply #388 on: 26 / February / 2011, 05:18:20 »
« Last Edit: 26 / February / 2011, 05:26:27 by silasje1 »
Logged
*

Offline bjacklee

  • *
  • 35
Re: 500d development
« Reply #389 on: 26 / February / 2011, 09:33:15 »
@silasje1, any details of your post? :)
Logged
Pages: 1 ... 34 35 36 37 38 [39] 40 41 42 43 44 ... 249   Go Up
« previous next »
 

Related Topics