Topics

It runs for a few minutes then the camera seems to shut off. Afterwards I see some photos and movies were written to the SD card, but I am not sure if it passed or failed. Any suggestions?

I got this from the FAQ: "You can generate the ROM images from your own camera by compiling with CONFIG_DEBUGMSG=1 and then selecting Dump ROM from Debug menu." So I made the change in Makefile.inc and built ML as follows:

make clean; make;
// I get these build errors
zebra.o: In function `card_benchmark_wr':
zebra.c:(.text+0x354c): undefined reference to `console_printf'
zebra.c:(.text+0x365c): undefined reference to `console_printf'
zebra.c:(.text+0x366c): undefined reference to `console_printf'
zebra.o: In function `card_benchmark':
zebra.c:(.text+0x36c4): undefined reference to `console_printf'
zebra.c:(.text+0x36fc): undefined reference to `console_printf'
zebra.c:(.text+0x3704): undefined reference to `console_show'
vram.o: In function `vram_toggle':
vram.c:(.text+0xf0): undefined reference to `menu_show_only_selected'
collect2: ld returned 1 exit status
make[1]: *** [magiclantern] Error 1
make[1]: Leaving directory `/home/vtrandal/magic-lantern/platform/60D.111'
make: *** [60D] Error 2

Having been away from firmware development for a while I could use some help getting this to build. Thanks.

I'm mostly interested in landscape photography at the moment. I believe focus peaking at x5 and x10 magnification will result in better manual focus results for me. As a simple test, reading a street sign a block away is not easily done without this.

In a previous thread in the support area for early downloads Alex explained there's a global flag that blocks all LiveView overlays in x5 (and I also assume x10) modes.

So then showing peaking in x5 modes can be done? But there's a global flag that blocks all LiveView overlays in such modes. Hmmm ... Focus Peak is in the overlay menu. So then I don't understand how it can be done.

Anyway, I want to do this and I would appreciate any help or pointers that I could get as I begin experimenting with a 600D/T3i. It appears that most or all the Focus Peak feature is implemented in zebra.c file, but I really have no idea where to begin at the moment.

To get started experimenting with Magic Lantern development I went to http://www.magiclantern.fm/develop and downloaded the source code as follows:

hg clone -r unified https://bitbucket.org/hudson/magic-lantern

Since I don't have a camera at the moment I am not able to test it, but I think the firmware version in the source code is still at 2.3.RC5 because of the following grep command and it's results:

cd magic-lantern
grep -r --include=*.[ch] "v2\.3" .

./platform/5D2.212/version.c:const char build_version[] = "v2.3.RC5.2012Aug18.5D2212";
./platform/550D.109/version.c:const char build_version[] = "v2.3.RC5.2012Aug18.550D109";
./platform/50D.109/version.c:const char build_version[] = "v2.3.RC5.2012Aug18.50D109";
./platform/60D.111/version.c:const char build_version[] = "v2.3.RC5.2012Aug18.60D111";
./platform/500D.111/version.c:const char build_version[] = "v2.3.RC5.2012Aug18.500D111";
./platform/600D.102/version.c:const char build_version[] = "v2.3.RC5.2012Aug18.600D102";

When I had a camera I seem to recall it reporting the firmware version as 2.3 without RC5 appended, but now I am a little confused.

The primary reason I want to use Magic Lantern is for features that assist with manual focus like Focus Peak and Increase SharpContrast. But neither one seems to do anything in x5/x10 zoom as far as I can tell. I don't find Magic Zoom at x3 zoom useful and here's why:

As a simple manual focus test I sometimes take a photo of a street sign a block a way. In the resulting photo I can read the street sign if taken with a Sony NEX that has Focus Peaking at x10 zoom. I cannot do this with a Canon with or without Magic Lantern.

Any suggestions? Please don't say buy a Sony NEX

First, Magic Lantern is great. I am grateful to everyone who has contributed to it's development. Thank you!

This post is about the "Increase SharpContrast" feature in the Prefs menu that Alex pointed to me in July. Maybe I am expecting too much from this feature in that I would like it to work a lot like Focus Peak but in x5/x10 zoom.

On page 42 of the ML User Guide "Increase SharpContrast" is listed as a feature for customizing Canon's x5/x10 zoom in LiveView i.e. sharpness and contrast are maximized when zoom is active. The User Guide also says increased sharpness works somewhat like focus peaking.

So then the User Guide says it "works somewhat like focus peaking" but not exactly like it. Then what should I see? I don't think I see anything. If anyone could try it on their camera and give a reply I would greatly appreciate that.

Thank you!

I have read through the FAQ, looked over the current posts, and searched for solutions to problems I am having with some Magic Lantern manual focus features. But I have not found any posts that address the manual focus features I am having problems with (Focus Peak, Magic Zoom, and SharpContrast) on my Canon T3i (600D). So I will describe the problems in reference to how they should work according to the Magic Lantern v2.3 User Guide.

Problem: The User Guide regarding Focus Peak says "High-contrast lines will be marked by blinking dots showing which part of the image is in focus." In my case on my Canon T3i (600D) lots of blinking dots do appear around high-contrast lines as I adjust the manual focus ring on the lens, but the dots appear only briefly and then most of them disappear leaving a relatively small number of blinking dots around high-contrast lines. I've tried adjusting Focus Peak settings in the Overlay menu, but I have not found settings that make the Focus Peak feature consistently mark high-contrast lines with lots of blinking dots that persist around the portion of the image that is in fact in focus after I have stopped adjusting the manual focus on the lens.

Problem: The User Guide regarding Magic Zoom says "Displays a zoom box for focus assist ... When ML believes you have achieved perfect focus, Magic Zoom will display a focus confirmation (customizable)." I use Magic Zoom in the Zoom In (+) trigger mode with "Green Bars" as focus confirmation. In my case on my Canon T3i (600D) focus confirmation (Green Bars) often illuminates at the top and bottom of the zoom window when the portion of the image being focused on is *not* actually in focus. And when the Green Bars do appear when "perfect" focus is achieved they often appear only briefly and then disappear even if my hand is not touching the focus ring on the lens and the portion of the image in the Magic Zoom window is in fact still in focus.

Problem: The User Guide regarding "Increase SharpContrast" says "when zoom is active, sharpness and contrast are maximized. Increased sharpness works somewhat like focus peaking." This is the most important Magic Lantern focus feature to me. It's enabled by selecting "Increase SharpContrast" in "LiveView zoom settings" of the Prefs menu. This feature has worked only once for me - and it was AMAZING! Specifically, after enabling it, I'm sure I pressed Zoom In (+) and I thought the Magic Zoom window popped up and I could see Focus Peak like behavior occurring within the zoom window (with magnification) as I adjusted the manual focus ring on the lens. But now no matter what I try I can't get any Focus Peak like activity when zoom is active either through pressing Zoom In (+) or by holding the shutter button halfway down.

If anyone cares to comment on how I may be misusing any of these features and how I might use them correctly I would be very grateful. Shortly here I will begin to split these problems into separate posts so anyone who is interested can focus on a specific problem. And for any problem that remains unresolved I will open a bug report as appropriate.

Thanks!

I'm really sorry if this is in an FAQ somewhere but I can't find it.

This is based on the instructions provided at http://www.magiclantern.fm/develop
When I refer to the instructions I mean the instructions at the above page and it's subpages.

Step 1. Get the source code. I got it just like it says below so I don't have to do ""hg update unified" later.
hg clone -r unified https://bitbucket.org/hudson/magic-lantern

Step 2. Setup up the compiler. Here I did things a little differently
- I skipped downloading summon-arm because it's in the ML source code toolchain folder.
- I downloaded and executed prepare.ubuntu.sh (but this is also in the ML source code toolchain folder )
- In ~/magic-lantern/toolchain I edited summon-arm and added the --no-passive-ftp parameter to the wget line per the instructions.
- I ran summon-arm as follows: ./summon-arm SUDO=sudo (when it needed root privileges I gave it the root password)
- I tested the toolchain by building the hello.c per the instructions.
- I added ~/arm-toolchain462/bin to my PATH
- I tried running make in the ~/magic-lantern folder as follows: make, make clean, make (but make encountered errors and failed each time)
- I also tried running make 600D as follows: make 600D, make clean, make 600D (but again make encountered errors and failed each time)

At this point I'm not sure my ML toolchain build is valid because it should just build ML with no problem right?

But... I did only glance through the summon-arm README without making any changes because I thought all that would be covered by downloading and running prepare.ubuntu.sh ... I have little idea what or where to set all those things to in the README

Here's the entire output with errors that I get with running make:
vtrandal@vtrandal-android:~/magic-lantern$ make
make -C /home/vtrandal/magic-lantern/platform/60D.111
make[1]: Entering directory `/home/vtrandal/magic-lantern/platform/60D.111'
[ CPP      ]   magiclantern.lds
[ AS       ]   ../../src/entry.o
[ CC       ]   boot-hack.o
[ AS       ]   stubs.o
[ VERSION  ]   ../../platform/60D.111/version.c
[ CC       ]   version.o
[ CC       ]   bmp.o
[ CC       ]   font-dyn.o
[ CC       ]   config.o
[ CC       ]   menu.o
[ CC       ]   debug.o
[ CC       ]   stdio.o
[ CC       ]   audio.o
[ CC       ]   bitrate.o
[ CC       ]   tweaks.o
../../src/tweaks.c: In function 'handle_arrow_keys':
../../src/tweaks.c:1566:17: warning: passing argument 1 of 'aperture_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:228:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1580:17: warning: passing argument 1 of 'aperture_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:228:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1593:17: warning: passing argument 1 of 'iso_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:226:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1594:17: warning: passing argument 1 of 'shutter_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:227:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1607:17: warning: passing argument 1 of 'iso_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:226:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1608:17: warning: passing argument 1 of 'shutter_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:227:6: note: expected 'void *' but argument is of type 'int'
[ CC       ]   lens.o
[ CC       ]   property.o
[ CC       ]   propvalues.o
[ CC       ]   gui.o
[ CC       ]   gui-common.o
[ CC       ]   misc.o
[ CC       ]   picstyle.o
[ CC       ]   cfn.o
[ CC       ]   zebra.o
[ CC       ]   shoot.o
[ CC       ]   chdk-gui_draw.o
[ CC       ]   movtweaks.o
[ CC       ]   my_memset.o
[ CC       ]   menuhelp.o
cd ../../doc; python menuindex.py
Could not open menuindex.txt
mkdir: cannot create directory `cam': File exists
[ CC       ]   menuindex.o
[ CC       ]   af_patterns.o
[ CC       ]   focus.o
[ CC       ]   notify_box.o
[ CC       ]   bootflags.o
[ CC       ]   dialog_test.o
[ CC       ]   vram.o
[ CC       ]   morse.o
[ CC       ]   liveview.o
[ CC       ]   reloc.o
[ CC       ]   aj_port.o
[ CC       ]   fps-engio.o
[ CC       ]   cartridge.o
[ CC       ]   hdr.o
[ CC       ]   lv-img-engio.o
[ CC       ]   state-object.o
[ CC       ]   tasks.o
[ AR       ]   lib_a-setjmp.o
[ AR       ]   libstdio.a
[ LD       ]   magiclantern
boot-hack.o: In function `my_init_task':
boot-hack.c:(.text+0x14): relocation truncated to fit: R_ARM_PC24 against symbol `get_current_task' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x4c): relocation truncated to fit: R_ARM_PC24 against symbol `init_task' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x100): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x128): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x138): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x154): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x16c): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x1e8): relocation truncated to fit: R_ARM_PC24 against symbol `task_create' defined in *ABS* section in magiclantern
boot-hack.o: In function `my_assert_handler':
boot-hack.c:(.text+0x234): relocation truncated to fit: R_ARM_PC24 against symbol `get_current_task' defined in *ABS* section in magiclantern
boot-hack.o: In function `my_big_init_task':
boot-hack.c:(.text+0x2b8): relocation truncated to fit: R_ARM_PC24 against symbol `call' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x2e8): additional relocation overflows omitted from the output
collect2: ld returned 1 exit status
make[1]: *** [magiclantern] Error 1
make[1]: Leaving directory `/home/vtrandal/magic-lantern/platform/60D.111'
make: *** [60D] Error 2
vtrandal@vtrandal-android:~/magic-lantern$

Here's the entire output with errors that I get with running make 600D:
vtrandal@vtrandal-android:~/magic-lantern$ make 600D
make -C /home/vtrandal/magic-lantern/platform/600D.102
make[1]: Entering directory `/home/vtrandal/magic-lantern/platform/600D.102'
[ CPP      ]   magiclantern.lds
[ AS       ]   ../../src/entry.o
[ CC       ]   boot-hack.o
[ AS       ]   stubs.o
[ VERSION  ]   ../../platform/600D.102/version.c
[ CC       ]   version.o
[ CC       ]   bmp.o
[ CC       ]   font-dyn.o
[ CC       ]   config.o
[ CC       ]   menu.o
[ CC       ]   debug.o
[ CC       ]   stdio.o
[ CC       ]   audio.o
[ CC       ]   bitrate.o
[ CC       ]   tweaks.o
../../src/tweaks.c: In function 'handle_arrow_keys':
../../src/tweaks.c:1566:17: warning: passing argument 1 of 'aperture_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:228:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1580:17: warning: passing argument 1 of 'aperture_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:228:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1593:17: warning: passing argument 1 of 'iso_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:226:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1594:17: warning: passing argument 1 of 'shutter_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:227:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1607:17: warning: passing argument 1 of 'iso_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:226:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1608:17: warning: passing argument 1 of 'shutter_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:227:6: note: expected 'void *' but argument is of type 'int'
[ CC       ]   lens.o
[ CC       ]   property.o
[ CC       ]   propvalues.o
[ CC       ]   gui.o
[ CC       ]   gui-common.o
[ CC       ]   misc.o
[ CC       ]   picstyle.o
[ CC       ]   cfn.o
[ CC       ]   zebra.o
[ CC       ]   shoot.o
[ CC       ]   chdk-gui_draw.o
[ CC       ]   movtweaks.o
[ CC       ]   my_memset.o
[ CC       ]   menuhelp.o
cd ../../doc; python menuindex.py
Could not open menuindex.txt
mkdir: cannot create directory `cam': File exists
[ CC       ]   menuindex.o
[ CC       ]   af_patterns.o
[ CC       ]   focus.o
[ CC       ]   notify_box.o
[ CC       ]   bootflags.o
[ CC       ]   dialog_test.o
[ CC       ]   vram.o
[ CC       ]   morse.o
[ CC       ]   liveview.o
[ CC       ]   reloc.o
[ CC       ]   aj_port.o
[ CC       ]   fps-engio.o
[ CC       ]   cartridge.o
[ CC       ]   hdr.o
[ CC       ]   lv-img-engio.o
[ CC       ]   state-object.o
[ CC       ]   tasks.o
[ AR       ]   lib_a-setjmp.o
[ AR       ]   libstdio.a
[ LD       ]   magiclantern
boot-hack.o: In function `my_assert_handler':
boot-hack.c:(.text+0x18): relocation truncated to fit: R_ARM_PC24 against symbol `get_current_task' defined in *ABS* section in magiclantern
boot-hack.o: In function `my_big_init_task':
boot-hack.c:(.text+0x9c): relocation truncated to fit: R_ARM_PC24 against symbol `call' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0xcc): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x10c): relocation truncated to fit: R_ARM_PC24 against symbol `task_create' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x120): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.o: In function `my_dump_task':
boot-hack.c:(.text+0x31c): relocation truncated to fit: R_ARM_PC24 against symbol `call' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x324): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x32c): relocation truncated to fit: R_ARM_PC24 against symbol `call' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x334): relocation truncated to fit: R_ARM_PC24 against symbol `call' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x340): relocation truncated to fit: R_ARM_PC24 against symbol `call' defined in *ABS* section in magiclantern
boot-hack.o: In function `hold_your_horses':
boot-hack.c:(.text+0x37c): additional relocation overflows omitted from the output
collect2: ld returned 1 exit status
make[1]: *** [magiclantern] Error 1
make[1]: Leaving directory `/home/vtrandal/magic-lantern/platform/600D.102'
make: *** [600D] Error 2
vtrandal@vtrandal-android:~/magic-lantern$