Canon 700D / T5i

[a1ex]

Some notes for fixing the boot flag code:
http://magiclantern.wikia.com/wiki/WritingBootflagsToCard

[a1ex]

State diagrams for 113: http://a1ex.bitbucket.org/ML/states/700D-alt/index.html

[mk11174]

State diagrams for 113: http://a1ex.bitbucket.io/ML/states/700D-alt/index.html

Nice! Thanks!

[topspin391]

ready to test 1.1.3 on the camera, please send a mail [email protected]

[Edmund-B]

hi, im relatively new to the forum and this is my first post.

foolishly updated my 700d to 1.1.3 and now its just sitting there. I'm no video fan how ever, the only reason why i use ML is for the different specs i can get doing time-lapse.

so if there is any thing i can do to help with the development of the 113 build i'm ready. though I'm no programmer.... and have no idea what a dump is as mentioned in a couple of posts earlier

[mk11174]

hi, im relatively new to the forum and this is my first post.

foolishly updated my 700d to 1.1.3 and now its just sitting there. I'm no video fan how ever, the only reason why i use ML is for the different specs i can get doing time-lapse.

so if there is any thing i can do to help with the development of the 113 build i'm ready. though I'm no programmer.... and have no idea what a dump is as mentioned in a couple of posts earlier

It is almost ready to go, I would like to fix one little bug though with evf-states that freezes cam while in photo mode/ live view or 1280x720@60p mode, then I feel it is just like it was, everything else is working nicely though.

[mk11174]

Ok after not getting anywhere with pretending I knew what I was doing with vsync,  I decided to keep EVF_STATE at 5 and 5. Then look closer at other things in vsync because it does have no pink frames the way it is, it just froze the cam, so I figured it had to be something else.

Well after looking through all the things that run for my camera during it, I tracked it down to digital_iso_step();

With that disabled, all is great, so now I have to see what is up with that.

But this is much less a problem because raw_rec is FAR better feature I think and the camera does not freeze at all now!

CPU% is normal now like 550D, but a little bit higher, but it probably always was, at least it does not jump right to 98% and stay there like it was doing.

[godashram]

good to hear!

[mk11174]

Ok, now inside digital_iso_step function, I tracked it down to this
call("lvae_setdispgain", 0);

So now I have to look at that one.

[mk11174]

Well looking at the similar cams 650D and EOS-M it seems the NSTUB for lvae_setdispgain is not in the 650D and it is NOT Used in EOSM.

It was in the 700D.111 and I guess working cause I never came across the freeze on it, and I just checked the address in IDA against the 700D.111, they are both at the
aEp_setdispgain ; " EP_SetDispGain >> OFF"  Subroutine.

So is this correct or should I simply just disable the stub and not use it?

[a1ex]

I would double-check the stub address for "call".

[mk11174]

I would double-check the stub address for "call".

HA! I was just going to mention that because I commented out the stub and it still crashed, so that was the only thing left! Cool, going to try now! 
HMMM, On 650, 700D.111 and 700D.113 all in same spot

Code Select Expand

---------------------------------------------------------------------------
ROM:FF12CBC0                 STMFD   SP!, {R3-R5,LR}
ROM:FF12CBC4                 LDR     R4, =0x23C20
ROM:FF12CBC8                 ADR     R0, aFa_setcrawbi_0 ; "FA_SetCRawBitNum"
ROM:FF12CBCC                 LDR     R1, [R4,#0xD8]
ROM:FF12CBD0                 BL      sub_FF138B08
ROM:FF12CBD4                 LDR     R1, [R4,#0xDC]
ROM:FF12CBD8                 ADR     R0, aFa_setobinte_0 ; "FA_SetObIntegMode"
ROM:FF12CBDC                 BL      sub_FF138B08
ROM:FF12CBE0                 ADR     R2, aRXkgvbGhrTs ; "É-ò¬âéü[âhɦÆF"
ROM:FF12CBE4                 MOV     R1, #0x16
ROM:FF12CBE8                 MOV     R0, #0x82
ROM:FF12CBEC                 BL      0x395C
ROM:FF12CBF0                 LDR     R3, [R4,#0xEC]
ROM:FF12CBF4                 ADR     R0, aFa_setobwindow ; "FA_SetObWindow"
ROM:FF12CBF8                 STR     R3, [SP]
ROM:FF12CBFC                 ADD     R3, R4, #0xE0
ROM:FF12CC00                 LDMIA   R3, {R1-R3}
ROM:FF12CC04                 BL      sub_FF138B08
ROM:FF12CC08                 LDR     R1, [R4,#0xD4]
ROM:FF12CC0C                 ADR     R0, aFa_obintegtest ; "FA_ObIntegTestImage"
ROM:FF12CC10                 BL      sub_FF138B08
ROM:FF12CC14                 ADD     R1, R4, #0xF0
ROM:FF12CC18                 ADR     R0, aFa_getobintegp ; "FA_GetObIntegPram"
ROM:FF12CC1C                 BL      sub_FF138B08
ROM:FF12CC20                 ADD     R1, R4, #0xF4
ROM:FF12CC24                 ADR     R0, aFa_getobintegp ; "FA_GetObIntegPram"
ROM:FF12CC28                 BL      sub_FF138B08
ROM:FF12CC2C                 ADD     R1, R4, #0xF8
ROM:FF12CC30                 ADR     R0, aFa_getobintegp ; "FA_GetObIntegPram"
ROM:FF12CC34                 BL      sub_FF138B08
ROM:FF12CC38                 ADD     R1, R4, #0xFC
ROM:FF12CC3C                 ADR     R0, aFa_getobintegp ; "FA_GetObIntegPram"
ROM:FF12CC40                 BL      sub_FF138B08
ROM:FF12CC44                 ADR     R2, aWhitecIcbRXkcI ; "WHITEù¦êµü@É-ò¬ù¦êµÉ¦ÆFü@ü

And this is where its SUB is

Code Select Expand

OM:FF138B08 ; =============== S U B R O U T I N E =======================================
ROM:FF138B08
ROM:FF138B08
ROM:FF138B08 sub_FF138B08                            ; CODE XREF: ROM:FF12CBD0p
ROM:FF138B08                                         ; ROM:FF12CBDCp ...
ROM:FF138B08
ROM:FF138B08 var_20          = -0x20
ROM:FF138B08 var_14          = -0x14
ROM:FF138B08 varg_r0         = -0x10
ROM:FF138B08 varg_r1         = -0xC
ROM:FF138B08 varg_r2         = -8
ROM:FF138B08 varg_r3         = -4
ROM:FF138B08
ROM:FF138B08                 STMFD   SP!, {R0-R3}
ROM:FF138B0C                 STMFD   SP!, {R3-R5,LR}
ROM:FF138B10                 LDR     R0, =0x2440C
ROM:FF138B14                 LDR     R1, [SP,#0x20+varg_r0]
ROM:FF138B18                 SUB     R4, R0, #0x1C
ROM:FF138B1C                 STR     R0, [SP,#0x20+var_20]
ROM:FF138B20                 LDR     R0, [R4,#4]
ROM:FF138B24                 ADD     R5, SP, #0x20+varg_r1
ROM:FF138B28                 MOV     R2, SP
ROM:FF138B2C                 BL      sub_FF33F948
ROM:FF138B30                 LDR     R2, [R4,#8]!
ROM:FF138B34                 LDR     R1, [SP,#0x20+varg_r0]
ROM:FF138B38                 LDR     R0, [R4,#0xC]
ROM:FF138B3C                 BLX     R2
ROM:FF138B40                 LDR     R0, [SP,#0x20+var_20]
ROM:FF138B44                 LDMIA   R0, {R1,R2}
ROM:FF138B48                 MOV     R0, R5
ROM:FF138B4C                 BLX     R2
ROM:FF138B50                 LDMFD   SP!, {R3-R5}
ROM:FF138B54                 LDR     PC, [SP+0x14+var_14],#0x14
ROM:FF138B54 ; End of function sub_FF138B08
ROM:FF138B54
ROM:FF138B58
ROM:FF138B58 ; =============== S U B R O U T I N E =======================================

[godashram]

someone is on a roll today

[mk11174]

Any way to call something else there just to see what happens, or to test call out? I took out lvae_setdispgain from the "" but I don't know if that would really work to test "call" out but it doesn't crash with that out of the call?

[mk11174]

someone is on a roll today

Maybe disabling the 2 call lines to it is just delaying the freeze, I have worked it for a few minutes with no freeze, maybe u want to test it too? AS you know, it normally only takes 15seconds of scrolling through Canon or ML menus to freeze it, only in Photomode while in Live view and Movie MOde at 1280x720x60p though, so test in those modes, that puts the cam at 60fps which is when it freezes.

But so far I cant get it too, maybe you will have differ luck?

[godashram]

sure, why not! i'll have a couple of hours tonight and tomorrow........

[mk11174]

Ok here you go, lets see what you come up with!

Anyone else with 700D, do not bother using this unless you had Firmware 111 and ran ML on it already, then by accident updated to Firmware 113 without realizing ML would not work anymore.

All users that started with Firmware 113 you will need to wait for the 700D.1113.FIR to get the bootflag on your camera first.

https://bitbucket.org/mk11174/t5i-backup/downloads/magiclantern-v2.3.NEXT.2014Mar14.700D113.zip

ALSO: Please remove ML folder and old Autoexec.bin first before unzipping this to your card.

[godashram]

15+ minutes in live view photo with no problems yet.... using various modes, especially manual and a+.

will try video later tonight.

Also, with the histogram on, it appears, flickering, in the ML menus.

with movie crop mode on, tapping the magnifying glass behaves as if you hit the info button. some items disappear, but hitting info brings them back.

beyond that, pretty solid so far.... closing in on 30 minutes with no lockups

[Edmund-B]

Anyone else with 700D, do not bother using this unless you had Firmware 111 and ran ML on it already, then by accident updated to Firmware 113 without realizing ML would not work anymore.

All users that started with Firmware 113 you will need to wait for the 700D.1113.FIR to get the bootflag on your camera first.

*cries*

[mk11174]

15+ minutes in live view photo with no problems yet.... using various modes, especially manual and a+.

will try video later tonight.

Also, with the histogram on, it appears, flickering, in the ML menus.

with movie crop mode on, tapping the magnifying glass behaves as if you hit the info button. some items disappear, but hitting info brings them back.

beyond that, pretty solid so far.... closing in on 30 minutes with no lockups

Nice!!, I like how good you test stuff, very in depth 

[mk11174]

*cries*

As soon as the bootflag is done for it, you will be able to install it, don't worry!

[Edmund-B]

As soon as the bootflag is done for it, you will be able to install it, don't worry!

meanwhile, any thing i should be reading on? i didn't really get the hang of installing unstable releases yet.

[ThankMeLater]

Even though I already have ML running on my 111 firmware I want to say thanks to mk11174 for his great work ! 

[Xtreme]

Many Thanks MK11174, i was waiting for this everyday 

Work perfecly here too. !!!!!!!!

Very good job !

[mk11174]

Really good to hear everyone!! Lets hope it stays that way with everyone!