[DONE] How do I dump 5D3 firmware 1.2.3?

[chris_overseas]

I ended up just coying the modules from the last nightly build.

This is a really bad idea and you could potentially even damage your camera by doing this. Modules compiled for 1.1.3 are not compatible with 1.2.3. Once the 1.2.3 support is merged into ML outdated module code will be prevented from loading at all, but that safeguard is not yet in place:

https://bitbucket.org/hudson/magic-lantern/pull-request/354/ported-ml-over-to-5d3-firmware-123/activity#comment-1154370

[Audionut]

To encourage testing and feedback, here is a 5D3.123 build.

You should already have the bootflag enabled with the development firmware.  This implies that you are currently running firmware 1.1.3
Format the card on computer
Format the card in camera, to be safe.
Copy Canon 1.2.3 firmware to card
Update camera.
Download build below, extract contents and copy to card.
Test it and leave feedback.  No feedback slows the development process.

[pompeiisneaks]

This is a really bad idea and you could potentially even damage your camera by doing this. Modules compiled for 1.1.3 are not compatible with 1.2.3. Once the 1.2.3 support is merged into ML outdated module code will be prevented from loading at all, but that safeguard is not yet in place:

https://bitbucket.org/hudson/magic-lantern/pull-request/354/ported-ml-over-to-5d3-firmware-123/activity#comment-1154370

Okay then anyone have any ideas why my raw2dng fails to build with the errors I'm seeing?  I'll try the build just linked, but I'd love for the modules to build on my dev system.

~Phil

[Audionut]

raw2dng isn't the module, raw_rec.mo is.

raw2dng is the windows executable for converting the raw files into DNG frames.  You need to fix you gcc/mingw install and make sure you can compile 32bit on your 64bit OS.

This thread may be of some help.

[pompeiisneaks]

I got it figured out.  The libgcc.i686 version was missing on my system.  Now a ton more build just fine, but I get this error on mvl_dump which means that I can't use the mlv_rec for the new Magic Lantern video format.  Any ideas?  This def seems more like a C error:

[ GCC      ]   mlv_dump
[ GCC      ]   mlv_dump
[ GCC      ]   mlv_dump
mlv_dump.c: In function ‘lua_call_va’:
mlv_dump.c:64: warning: unused variable ‘verbose’
mlv_dump.c:63: warning: unused variable ‘nres’
mlv_dump.c:63: warning: unused variable ‘narg’
In file included from ../lv_rec/lv_rec.h:24,
                 from mlv_dump.c:305:
../../src/raw.h: At top level:
../../src/raw.h:185: warning: declaration does not declare anything
../../src/raw.h:193: warning: declaration does not declare anything
mlv_dump.c: In function ‘main’:
mlv_dump.c:2025: error: ‘struct raw_info’ has no member named ‘active_area’
mlv_dump.c:2026: error: ‘struct raw_info’ has no member named ‘active_area’
mlv_dump.c:2027: error: ‘struct raw_info’ has no member named ‘jpeg’
mlv_dump.c:2028: error: ‘struct raw_info’ has no member named ‘jpeg’
mlv_dump.c:2034: error: ‘struct raw_info’ has no member named ‘active_area’
mlv_dump.c:2035: error: ‘struct raw_info’ has no member named ‘active_area’
mlv_dump.c:2036: error: ‘struct raw_info’ has no member named ‘jpeg’
mlv_dump.c:2037: error: ‘struct raw_info’ has no member named ‘jpeg’
mlv_dump.c:2555: error: ‘struct raw_info’ has no member named ‘active_area’
mlv_dump.c:2556: error: ‘struct raw_info’ has no member named ‘active_area’
mlv_dump.c:2557: error: ‘struct raw_info’ has no member named ‘active_area’
mlv_dump.c:2558: error: ‘struct raw_info’ has no member named ‘active_area’
make[3]: *** [mlv_dump] Error 1

Any thoughts on this error? 

~Phil

[Audionut]

which means that I can't use the mlv_rec for the new Magic Lantern video format.

The windows binaries very rarely get updated, personally I would just grab the prebuilt binary from the developer.
http://www.magiclantern.fm/forum/index.php?topic=7122.0

If you really want to build it, you probably need to ping g3gg0 on that one.

[pompeiisneaks]

which would be good except that the other modules don't build when it fails there.  I guess this becomes more related to general devel instead of this 123 build though.  I'll do as you say and work on the other issues in the general devel forum area.

Thanks,

~Phil

[Audionut]

It shouldn't try and build the exe unless you specifically tell it to.  If it's dying on the linux build you could try removing it from the mlv makefile.

makefile.modules.default controls which modules get built with make, and each module has it's own makefile.

edit:  Turns out we have a sticky in the raw section for linux tools.  http://www.magiclantern.fm/forum/index.php?topic=9335.0

[pompeiisneaks]

g3ggo got me on the right track, centos has old gcc. Getting that resolved.

[DavidSh]

Thank you guys for this great update,

I am new to ml...
worked with the  tragic lantern on my old 600d

I would like to help with debugging... i own a new 5d3 1.2.3  - no ml installed.

how do i install this version of ml on a brand new 5d3?

I must downgarde to 1.1.3 to install the dev version for bootflag and then go back to 1.2.3 and install this version?

Best...
David

[VisualPursuit]

To encourage testing and feedback, here is a 5D3.123 build.

Thank you very much for that.

You should already have the bootflag enabled with the development firmware.

Is there a way to enable the bootflag without downgrading to firmware 1.1.3 before?

[Audionut]

Not at this stage, the priority is on getting the port functional rather then making it user friendly to install.

[pompeiisneaks]

Okay I've played with it a bit more, and gotten my build system working.  I've not yet tried my last working build, I'm using the one Chris linked earlier.  As was asked earlier, what should be tested?  I've tried several of the debug menu stuff like burn in tests and benchmarks and they're all seeming to crash.  I can get the logs and bmp if they're needed, but they may also not be the root of what needs testing.

[Audionut]

Best thing to do is put everything through it's paces. 

[pompeiisneaks]

I've been playing around a bit, and have the logs and bmp from crash screen,  where is the preferred landing spot for files?  I'll try to see about doing a public dropbox folder in the meantime.

I've had some really odd behavior with MLV raw recording.  This is from my own build, it all works, but sometimes the videos are extremely high noise and pinkish.  Not sure how to explain it better than that, but I'll get a few screencaps from it as well.

~Phil

[pompeiisneaks]

Nevermind, I'll just dropbox them. 

So here's the scoop.  First off I was using some of the burn in and test features and had a few crashes.  Here are the logs and BMP screenshots. The two crashes were actually with the build linked here, the odd video behavior is with my build done afterwards. 

first crash
https://www.dropbox.com/s/yo7thtsigfcc64f/LOG000.LOG
https://www.dropbox.com/s/9ovokwkiy33axrv/VRAM0.BMP

and here is the second crash

https://www.dropbox.com/s/4o1bt95flngtfa7/LOG001.LOG
https://www.dropbox.com/s/bx3v2luqtmlmw0w/VRAM1.BMP

Also I've got three images, they'll be in order a DNG file saved as png from three video recordings I did with MLV.  1 is 1080p and had horrid colors all messed up.  2 is just fine, right after the first failure, and 3 is at a lower resolution so that I could record to my slower card.  It also was all messed up.  Is this a known problem?  Do I just have something set wrong or? 
1080p bad https://www.dropbox.com/s/sekurd8e9mi7h8z/bad1080p.png
1080p good https://www.dropbox.com/s/forj472o66is0qp/good1080p.png
864p bad https://www.dropbox.com/s/ck9rl0lxgypjz0d/bad864.png

This is what I'm seeing as off so far.

otherwise focus peaking, zebras on over exposure, audio levels seem fine.  The only other thing that seems  odd is sometimes things seem to be fighting for liveview and blink on/off a lot.  My focus points in the canon firmware seems to overwrite things if they're blinking and it alternates between the two, maybe normal behavior but I"m new to the ML in a lot of ways.


~Phil

[primemultimedia]

Picking up my Ninja 2 tomorrow. This couldn't have come at a better time. Thanks so much to everyone involved. Bunch of legends!

[pompeiisneaks]

Nobody has any input on if my pics could be a problem with code or are expected?   Or should I submit this issue to a new thread about the build specifically?

~Phil

[WeekendWarrior]

I just want to say thanks for taking the time to put piece together this new version! Very thankful to have such hard workers behind all this. Props

[Audionut]

Nobody has any input on if my pics could be a problem with code or are expected?

This isn't the only WIP, and I expect this to be one of the lower priorities atm.

Back porting Tragic Lantern to get those ports functional in the ML is a major priority.

[primemultimedia]

ML working alongside hdmi out. Interesting behavior though. With mirroring off (hdmi out only, no liveview), pressing info can bring up a cropped frame with ml overlays ect. But with mirroring on (hdmi out+liveview) it is not possible to get ml overlays on either screen (ml menu asks you to press info to remove canon overlays).

Raw recording works in both modes. With mirroring off, raw recording has no effect on hdmi output!

[Grifter]

Just what Ive been waiting for...   Imagine raw to card and 1080 25p to Ninja on 1.2.3

[primemultimedia]

Just what Ive been waiting for...   Imagine raw to card and 1080 25p to Ninja on 1.2.3

That's exactly what I'm already doing! 

[Grifter]

Is it the Full Liveview screen you get onto the Ninja? And the cropped  Raw to the CF?

[primemultimedia]

The raw recording appears to have no effect on hdmi feed. I've yet to extract the raw to check it looks ok though. If you were referring to a cropped raw using 5x zoom then no, hdmi receives 5x zoom as well.