Eos 400d ( Rebel XTI )

0xAF

Sergei
Another variant of AUTOEXEC with ISO in Viewfinder:
http://lh.rs/kiDQ5Catx5bl
This time it uses burst counter to display ISO.
1 is 100
2 is 200
4 is 400
8 is 800
6 is 1600
3 is 3200

And it works in P, Tv, Av, M and A-DEP modes.

Very good 😀
Excellent solution 😀 and it works in Av 😀
Thanks for sharing 😀

p.s.
how you control the burst counter ? is it a ram address ? (and which if it is)

Sergei

SendToIntercom(0x6D, 1, burst_int);
I think the only way to access viewfinder lcd is through MPU. SendToIntercom is only function I could find which talks to MPU. Would be nice to find a ram address which corresponds to viewfinder lcd.

0xAF

Sergei
SendToIntercom(0x6D, 1, burst_int);
I think the only way to access viewfinder lcd is through MPU. SendToIntercom is only function I could find which talks to MPU. Would be nice to find a ram address which corresponds to viewfinder lcd.

I believe there will be NO ram address for this...
that's why i asked for it ...
and you are right about the MPU...
Alex found something about the communication, it seems to be done via ISRs (interrupt service routine) SIO3 and MREQ...
though there is some protocol which needs to be reversed, if we catch this ISRs it could be possible to proxy them and change some stuff in the communication, or even talk to MPU with our code ... but it seems there is a lot of work to be done there ....

In that matter of speaking, i think that tracing the SendToIntercom will NOT lead to anything useful for controlling the MPU in low level, though it could lead to some more commands which can be used.

p.s.
perhaps Alex could explain better what he found 😀

a1ex

Here: http://magiclantern.wikia.com/wiki/SIO3_MREQ

In digic4, viewfinder seems to be related to something named NotifyOlcInfoChanged. Didn't investigate this.

0xAF

a1ex
Here: http://magiclantern.wikia.com/wiki/SIO3_MREQ

In digic4, viewfinder seems to be related to something named NotifyOlcInfoChanged. Didn't investigate this.

I though the OLC stuff are related to the display on the back of the camera, not to the VF, but they both seems to be somehow related to each other ... I may be worth to investigate more on the OLC, thanks Alex 😀

Sergei

0xAFAlex found something about the communication, it seems to be done via ISRs (interrupt service routine) SIO3 and MREQ...
though there is some protocol which needs to be reversed, if we catch this ISRs it could be possible to proxy them and change some stuff in the communication, or even talk to MPU with our code ... but it seems there is a lot of work to be done there ....

a1ex
Here: http://magiclantern.wikia.com/wiki/SIO3_MREQ

That is interesting. I need to check it. Thanks.

repeater

sizzlincok

Sergei
Hello, everyone.
Just want to share my latest code:
http://www.filefactory.com/file/1wdg7fpyeg8z/n/400d_firmware_hack_2012-04-05_zip
Additional functionalities, which this AUTOEXEC.BIN provide, are listed in Readme.txt file.
Mainly new things are: "preset white balance" - camera can save up to 5 custom wb measurements, and EAEB script now can be started with shutter release button.

Please note this bin doesn't have all the features of 400plus firmware.

Is the ability to trigger EAEB using the shutter release something that can be added to the full 400plus firmware? If i try to shoot handheld HDR it is difficult to keep camera stable using the buttons on the back...

Great work guys by the way!

Wlad69

Hello,

In 400Plus, I do not recall the default parameter of the Color Temp. (K) and I do not know how to restore this value. 🙁

Thank you for your help.

eduperez

repeater
Is the ability to trigger EAEB using the shutter release something that can be added to the full 400plus firmware? If i try to shoot handheld HDR it is difficult to keep camera stable using the buttons on the back...

Great work guys by the way!

Yes, triggering the scripts from the shutter button is interesting; I'll try to see how Sergei's code fits into 400plus.

In the meantime, you could assign the JUMP or TRASH buttons to repeat the last script: not the real thing, but easier than fiddling with the menus each time.

eduperez

Wlad69
Hello,

In 400Plus, I do not recall the default parameter of the Color Temp. (K) and I do not know how to restore this value. 🙁

Thank you for your help.

There is no original value to restore: just set the color temperature you need in each situation, or use one of the predefined white balances (sunny, cloudy, ...).

Speedy

Well, back again with little time (still more than before). Updated german translation of Wiki.
If there are any germans here: please review it.

Speedy

Well, besides translating i'm planning to improve my C skills before they get lost 😀.
And what would be better than doing it here.
But before browsing and reading tons of src:

is there anything equal to a documentation of memory adresses or even a documentation where i should expect to find which fuction?
if not: what would you say: where's the best place to start getting into the code?

eduperez

There is "funclist.S", where we have a map with names and addresses of functions provided by the firmware; but probably not all functions are listed there, and for most functions we only know the name and address, not the parameters or what it does. The known functions are somehow documented at "firmware.h".

If you are interested to know how we start the camera and place our hooks, have a look at "entry.S", "init.c", and "gui.c". But the "core" of the hack is mostly at "main.c"; that's a good starting point to know how the hack works once the camera is up and running, and pretty much all the rest of the code is launched from there.

Hope this helps!

Speedy

Great, i'll have a look into it 😀

rhg

I have downloaded the latest patch and cannot set the max iso value beyond 1600 in the autiso settings anymore in AV mode. Switched back to the old patch (20110909) and it does not work either anymore. Any ideas (yes I have researched the 109 pages of this thread, but could not find anything).

Thanks,
Roland.

eduperez

rhg
I have downloaded the latest patch and cannot set the max iso value beyond 1600 in the autiso settings anymore in AV mode. Switched back to the old patch (20110909) and it does not work either anymore. Any ideas (yes I have researched the 109 pages of this thread, but could not find anything).

Thanks,
Roland.

"Max ISO" in AutoISO settings has always had a limit of 1600, if I recall correctly.

0xAF

Speedy
is there anything equal to a documentation of memory adresses or even a documentation where i should expect to find which fuction?
if not: what would you say: where's the best place to start getting into the code?

Edu gave you pointers to start with, once you learn how the hack is working (basics at least), you will know where to put your skills...
I would suggest investigating the main.c and leave the gui.c for later, since it is not yet fully reversed from ASM and the most things are done in the intercom_proxy (main.c) as for now. BTW scripts.c may be of interest too.

As for the documentation, take a look at the Magic Lantern documentations, they have good set of hardware (e.g. memory regions, different hardware controls) and API (e.g. structures, functions) related information.
Though ML is for DryOS cameras, most of the information is identical with our VxWorks camera.

DjD

Hi,
I really need help and I haven't found another place to post this question. I've downloaded and installed 400plus-20120415-11.bin.zip and as far as I can tell everything works great except for being able to change ISO via the Left/Right buttons and seeing ISO in the viewfinder.

So I figure there must be something I'm missing. Are there any other setting that need to be a certain way to enable this function. The manual doesn't say anything other than

Set the camera to M or Tv mode.
Look through the viewfinder, and half-press the shutter button; you should see the current measurement (shutter speed, aperture, ...).
Now press the LEFT and RIGHT buttons to change the ISO value (or UP just to display it); the new value is displayed in the viewfinder, in the same place where shutter speed is normally shown, while the button is pressed down.
In P and Av modes, ISO can also be changed, but it is not displayed.

When I follow this above instructions nothing happens. What am I doing wrong?

Thanks,
DJD

eduperez

This issue was also posted as a comment in the UserGuide page; as DJD found the cause himself, but put the answer only there, I'm copying his comment here:

"[...]But the good news is I finally figured out the problem. I had Custom Function 01 "SET button/Cross keys funct." set to "4:Cross keys:AF frame Selec." Once I changed that function back to the default "0:SET😛icture Style" I could finally set the ISO with those buttons and see ISO in the Viewfinder. There should probably be a note in the manual about this requirement. It would have helped me. Cheers, DJD"

I added a comment in the UserGuide yesterday; hope that helps to others that face the same problems.
Thanks DJD!

JoeNeptune

Greetings and thanks to you for all your hard work.

I really like how you renamed our Touchless Trigger.

Here is another Idea I hope somebody else might like and find useful in a positive way.

A stealth mode where pictures taken in this mode are auto erased if card door is opened without unlocking it with code first.
Perhaps playback could be stopped on the pictures taken in this mode by adding an error to the pic file that can be removed later?

Party on!

« Previous Page Next Page »