Magic Lantern Firmware Wiki - Recent changes [en]

User:Henkamill

2012-05-16T13:10:27Z

New user account

User:Wcchopper

2012-05-16T09:11:39Z

New user account

Build instructions

2012-05-16T07:39:33Z

Detailed build instructions (Unified branch):

← Older revision		Revision as of 07:39, May 16, 2012
(3 intermediate revisions not shown)
Line 5:		Line 5:
	hg clone <nowiki>https://bitbucket.org/hudson/magic-lantern/</nowiki>		hg clone <nowiki>https://bitbucket.org/hudson/magic-lantern/</nowiki>

-	* after the clone, enter the magic-latern directory and call "hg update" to choose the branch to work on (e.g. "hg update unified" for the unified branch); a list of branches can be found on the bitbucket.org site; currently: unified 550d 60d default 500d.	+	* after the clone, enter the magic-latern directory and call "hg update" to choose the branch to work on (e.g. '''hg update unified''' for the unified branch).
-	* Install or build the arm-elf cross compile environment (gcc 4.3.2) and perl.

-	* Update the Makefile <tt>$(ARM_PATH)</tt> to point to your arm-elf-gcc (arm-linux-gcc will work as well).	+	* Install or build the arm-elf cross compile environment (gcc 4.6.2) and perl.
		+
		+	* Update the Makefile.inc <tt>$(ARM_PATH)</tt> to point to your arm-elf-gcc (arm-linux-gcc will work as well).

	* Run <tt>make</tt>. There are more warnings than there should be; a good janitor project would be to clean up all of the warnings with explicit typecasts or fixes.		* Run <tt>make</tt>. There are more warnings than there should be; a good janitor project would be to clean up all of the warnings with explicit typecasts or fixes.
Line 15:		Line 15:
	* If you are building under Cygwin rather than Linux or OS X, [http://tomayko.com/writings/that-dilbert-cartoon here's a nickel...]		* If you are building under Cygwin rather than Linux or OS X, [http://tomayko.com/writings/that-dilbert-cartoon here's a nickel...]

-	= Camera-specific build instructions =	+	= [[Build instructions/Unified\|Detailed build instructions (Unified branch)]] =

-	* [[Build instructions/5D]]	+	Click the link above to find out how to setup the compiler, how to solve common problems etc.
-	* [[Build instructions/7D]]
-	* [[Build instructions/550D]]

-	= magiclantern ELF image =	+	=Some juicy details=
		+	== magiclantern ELF image ==

	The build process for the firmware involves a few non-traditional steps compared to a normal compilation. This section tries to walk through the process with emphasis on how it differs from a regular executable Makefile.		The build process for the firmware involves a few non-traditional steps compared to a normal compilation. This section tries to walk through the process with emphasis on how it differs from a regular executable Makefile.

Build instructions/Unified

2012-05-16T07:37:15Z

Fixing common compiling problems:

← Older revision		Revision as of 07:37, May 16, 2012
(9 intermediate revisions not shown)
Line 1:		Line 1:
-	These are build instructions for the 550D branch of Magic Lantern. They may work on the 5D branch, too, with minor changes. Credits goto [http://groups.google.com/group/ml-devel/browse_thread/thread/ba6a0d550c80f33c/b49acdfa4fc2a698#msg_c53ffeb56d19bf7a Arm.Indy and Phil].	+	These are build instructions for the Unified branch of Magic Lantern. Credits goto [http://groups.google.com/group/ml-devel/browse_thread/thread/ba6a0d550c80f33c/b49acdfa4fc2a698#msg_c53ffeb56d19bf7a Arm.Indy, Phil] and [https://bitbucket.org/hudson/magic-lantern/changeset/4c01cf16265d Sztupy].

	=Installing arm-elf-gcc 4.6.2=		=Installing arm-elf-gcc 4.6.2=
Line 60:		Line 60:
	hg clone -r unified https://bitbucket.org/hudson/magic-lantern/ && cd magic-lantern		hg clone -r unified https://bitbucket.org/hudson/magic-lantern/ && cd magic-lantern

-	Check the gcc version number in the Makefile:	+	Check the gcc version number in the Makefile.inc:

	GCC_VERSION=4.4.2 # or whatever you have installed		GCC_VERSION=4.4.2 # or whatever you have installed
Line 76:		Line 76:
	=Building the documentation=		=Building the documentation=

-	==User guides (PDF & Wiki)==	+	==User guides (PDF & BMP)==

-	cd doc	+	make docs
-	python mkdoc.py

	==Source code docs (Doxygen)==		==Source code docs (Doxygen)==
Line 96:		Line 96:
	=Fixing common compiling problems=		=Fixing common compiling problems=
	Magic Lantern is not easy to compile, and this section attempts to provide a little guidance if some problems appear. Please feel free to improve this if you succeed in compiling Magic Lantern.		Magic Lantern is not easy to compile, and this section attempts to provide a little guidance if some problems appear. Please feel free to improve this if you succeed in compiling Magic Lantern.
-
-	===Missing a few letters from ML menu===
-
-	Straightforward solution:
-
-	make clean
-	make

	===arm-elf-gcc not found===		===arm-elf-gcc not found===

-	Check the paths and version number in the Makefile. It should look like this:	+	Check the paths and version number in the Makefile.inc. It should look like this:

-	ARM_PATH=~/arm-toolchain # you might have installed arm-elf-gcc somewhere else...	+	ARM_PATH=~/arm-toolchain462 # you might have installed arm-elf-gcc somewhere else...
	ARM_BINPATH=$(ARM_PATH)/bin		ARM_BINPATH=$(ARM_PATH)/bin
-	GCC_VERSION=4.4.2 # or what gcc version you have installed...	+	GCC_VERSION=4.6.2 # or what gcc version you have installed...
	CC=$(ARM_BINPATH)/arm-elf-gcc-$(GCC_VERSION)		CC=$(ARM_BINPATH)/arm-elf-gcc-$(GCC_VERSION)
	...		...

-	The arm-elf directory, ~/arm-toolchain/bin, is not required to be in PATH. You should be able to invoke arm-elf-gcc from the terminal with this command: (Check your version number)	+	The arm-elf directory, ~/arm-toolchain462/bin, is not required to be in PATH. You should be able to invoke arm-elf-gcc from the terminal with this command: (Check your version number)
-	$ ~/arm-toolchain/bin/arm-elf-gcc-4.3.2	+	$ ~/arm-toolchain462/bin/arm-elf-gcc

	Make sure you install arm-elf-gcc with the summon-arm-toolchain script. I've tested 5 other builds of arm-elf-gcc, and none of them was able to compile Magic Lantern.		Make sure you install arm-elf-gcc with the summon-arm-toolchain script. I've tested 5 other builds of arm-elf-gcc, and none of them was able to compile Magic Lantern.
Line 135:		Line 128:
	===make: No rule to make target `lua-glue.o'.===		===make: No rule to make target `lua-glue.o'.===

-	This appears if you try to build the 5D branch with these instructions. You have to turn it off in the Makefile:	+	This appears if you try to build the old 5D branch with these instructions. You have to turn it off in the Makefile:
	CONFIG_LUA = n		CONFIG_LUA = n

Line 143:		Line 136:

	Sometimes, running <tt>make clean</tt> fixes strange compiling problems... and sometimes not.		Sometimes, running <tt>make clean</tt> fixes strange compiling problems... and sometimes not.
-

	===relocation truncated to fit: R_ARM_PC24...===		===relocation truncated to fit: R_ARM_PC24...===
		+
		+	'''Fix: use a 32-bit compiler.'''

	What does this error mean?		What does this error mean?
Line 152:		Line 146:

	*Long answer: [http://rowley.zendesk.com/entries/46203-relocation-truncated-to-fit-r-arm-pc24-against-symbol-error-message] [http://www.motherboardpoint.com/relocation-truncated-fit-error-means-t94967.html] [http://newsgroups.derkeiler.com/Archive/Comp/comp.os.vxworks/2006-02/msg00192.html]		*Long answer: [http://rowley.zendesk.com/entries/46203-relocation-truncated-to-fit-r-arm-pc24-against-symbol-error-message] [http://www.motherboardpoint.com/relocation-truncated-fit-error-means-t94967.html] [http://newsgroups.derkeiler.com/Archive/Comp/comp.os.vxworks/2006-02/msg00192.html]
-

	Workaround from [http://groups.google.com/group/ml-devel/browse_thread/thread/8c02917ef7360b95\| L0RE]: add -mlong-calls to the CFLAGS in the Makefile		Workaround from [http://groups.google.com/group/ml-devel/browse_thread/thread/8c02917ef7360b95\| L0RE]: add -mlong-calls to the CFLAGS in the Makefile
Line 165:		Line 158:
	-D__ARM__ \		-D__ARM__ \
	'''-mlong-calls\'''		'''-mlong-calls\'''
		+
		+	Warning: this will make the binary larger (bug in 64-bit gcc?)

	===Link problems with the LDS file===		===Link problems with the LDS file===
Line 171:		Line 166:

	link problems – zero-byte .lds file causing trouble. deleted it. got rebuilt		link problems – zero-byte .lds file causing trouble. deleted it. got rebuilt
-
-
-	===Camera hangs after being switched off and on===
-
-	See [http://groups.google.com/group/ml-devel/browse_thread/thread/f232bcb55243519d/87b96d3cb43b4bec?#87b96d3cb43b4bec].
-
-	This seems to be caused by the compiler. Use a GCC version which is known to work (like GCC 4.4.2).
-
-	GCC 4.3.2 causes this bug and also other instabilities (looks like an invalid pointer issue).
-
-	This problem may also appear when ML is started without a config file on FAT32 cards. See [http://groups.google.com/group/ml-devel/browse_thread/thread/070af004c449cdb1].

Talk:Build instructions/550D

2012-05-16T07:23:11Z

moved [[Talk:Build instructions/550D]] to [[Talk:Build instructions/Unified]]

Build instructions/550D

2012-05-16T07:23:11Z

moved [[Build instructions/550D]] to [[Build instructions/Unified]]

Build instructions/550D

2012-05-16T07:22:53Z

Compiling Magic Lantern / 550D:

← Older revision		Revision as of 07:22, May 16, 2012
Line 1:		Line 1:
	These are build instructions for the 550D branch of Magic Lantern. They may work on the 5D branch, too, with minor changes. Credits goto [http://groups.google.com/group/ml-devel/browse_thread/thread/ba6a0d550c80f33c/b49acdfa4fc2a698#msg_c53ffeb56d19bf7a Arm.Indy and Phil].		These are build instructions for the 550D branch of Magic Lantern. They may work on the 5D branch, too, with minor changes. Credits goto [http://groups.google.com/group/ml-devel/browse_thread/thread/ba6a0d550c80f33c/b49acdfa4fc2a698#msg_c53ffeb56d19bf7a Arm.Indy and Phil].

-	=Installing arm-elf-gcc 4.6.0=	+	=Installing arm-elf-gcc 4.6.2=

-	'''Step 1. '''Download [http://groups.google.com/group/ml-devel/browse_thread/thread/1992d0d91e0f37e4 summon-arm] script and save it in your Home folder: <tt>/home/yourusername/</tt>	+	'''Step 1. '''Download [https://bitbucket.org/hudson/magic-lantern/src/tip/toolchain summon-arm] script and save it in your Home folder: <tt>/home/yourusername/</tt>

	'''Step 2. '''Get the dependencies, as described in summon-arm's [http://github.com/esden/summon-arm-toolchain/ README].		'''Step 2. '''Get the dependencies, as described in summon-arm's [http://github.com/esden/summon-arm-toolchain/ README].

-	*For '''Debian/Ubuntu''', they are:	+	*For '''Debian/Ubuntu''', run [https://bitbucket.org/hudson/magic-lantern/src/a28afc13b7ea/toolchain/prepare.ubuntu.sh prepare.ubuntu.sh].

-	''sudo apt-get install'' flex bison libgmp3-dev libmpfr-dev libncurses5-dev libmpc-dev autoconf texinfo build-essential git-core mercurial zlibc zlib1g-dev	+	*For '''Fedora''' users, the dependencies are:
-	*For '''Fedora''' users, they are:
	yum install wget gmp-devel mpfr-devel ncurses-devel libmpc-devel mercurial zlib-devel		yum install wget gmp-devel mpfr-devel ncurses-devel libmpc-devel mercurial zlib-devel
	*For '''Mac OS X''', you need to install ''gmp'', ''mpfr'', ''libmpc'', ''libiconv'' and ''wget'' packages using MacPorts:		*For '''Mac OS X''', you need to install ''gmp'', ''mpfr'', ''libmpc'', ''libiconv'' and ''wget'' packages using MacPorts:
Line 17:		Line 17:
	For Mac details, check Coutts' guide [[Magic_Lantern_Development_on_Mac]], AJ's [[2.0.4_Building_ML]] page and/or Piers' [http://pdaddy.wordpress.com/2010/11/07/quick-notes-on-magic-lantern-for-550d/ blog entry].		For Mac details, check Coutts' guide [[Magic_Lantern_Development_on_Mac]], AJ's [[2.0.4_Building_ML]] page and/or Piers' [http://pdaddy.wordpress.com/2010/11/07/quick-notes-on-magic-lantern-for-550d/ blog entry].

-	You will also need gnutar and mercurial (can they be installed with port install?! I don't use a Mac...)	+	You will also need gnutar and mercurial.

	*For '''other''' Linux distros, use the package management system (yum, zypper etc.) and be careful, since the packages may have a slightly different name.		*For '''other''' Linux distros, use the package management system (yum, zypper etc.) and be careful, since the packages may have a slightly different name.
Line 26:		Line 26:
	''bash summon-arm''		''bash summon-arm''

-	This will install arm-elf-gcc under ~/arm-toolchain/bin.	+	This will install arm-elf-gcc under ~/arm-toolchain462/bin.

	If the script fails to download newlib, try changing the FTP transfer mode to "no-passive":		If the script fails to download newlib, try changing the FTP transfer mode to "no-passive":
Line 35:		Line 35:
	'''Step 4. '''Add the arm-elf-gcc binaries to your PATH. This is ''not'' required for building Magic Lantern, but is required for [[GPL Tools/ARM console\|ARM console]] and other related tools.		'''Step 4. '''Add the arm-elf-gcc binaries to your PATH. This is ''not'' required for building Magic Lantern, but is required for [[GPL Tools/ARM console\|ARM console]] and other related tools.

-	''PATH=~/arm-toolchain/bin:$PATH''	+	''PATH=~/arm-toolchain462/bin:$PATH''
	''which arm-elf-gcc''		''which arm-elf-gcc''
-	/home/.../arm-toolchain/bin/arm-elf-gcc	+	/home/.../arm-toolchain462/bin/arm-elf-gcc

	'''Step 5. '''Test the installation by compiling a Hello World program:		'''Step 5. '''Test the installation by compiling a Hello World program:
Line 54:		Line 54:
	You should get a file named ''hello.o'' . When compiling without "-c", it may complain about missing _exit and _sbrk, but this is OK according to [http://embdev.net/topic/183043 this forum post].		You should get a file named ''hello.o'' . When compiling without "-c", it may complain about missing _exit and _sbrk, but this is OK according to [http://embdev.net/topic/183043 this forum post].

-	=Compiling Magic Lantern / 550D=	+	=Compiling Magic Lantern / Unified=

-	Next, get the source code (550D branch) and the precompiled magiclantern.fir:	+	Next, get the source code (Unified branch):

-	hg clone -r 550d https://bitbucket.org/hudson/magic-lantern/ && cd magic-lantern	+	hg clone -r unified https://bitbucket.org/hudson/magic-lantern/ && cd magic-lantern
-	wget http://bitbucket.org/hudson/magic-lantern/downloads/magiclantern-0.2.0.rc1.550d.fw109.zip
-	unzip magiclantern-0.2.0.rc1.550d.fw109.zip magiclantern.fir

	Check the gcc version number in the Makefile:		Check the gcc version number in the Makefile:

User:Jhon indra31

2012-05-15T23:33:11Z

New user account

User:Johnidol

2012-05-15T22:51:01Z

New user account

User:Caimai86

2012-05-15T22:15:07Z

New user account

User:Studioman2

2012-05-15T15:16:01Z

New user account

User:Focusnumerique

2012-05-15T13:16:18Z

New user account

User:Dude303

2012-05-15T09:04:35Z

New user account

User:Охуевший Фотограф

2012-05-15T08:00:28Z

New user account

User:Coliciste

2012-05-14T20:35:00Z

New user account

User:PasiiHasi

2012-05-14T18:30:53Z

New user account

User:Alicanabaci

2012-05-14T18:11:22Z

New user account

User:Batto271

2012-05-14T17:31:38Z

New user account

User:Northernlight

2012-05-14T11:01:09Z

New user account

1100D Magic Lantern??

2012-05-14T10:38:23Z

https://bitbucket.org/nanomad/magic-lantern-for-1100d/src

New page

[[File:Placeholder|right|300px]]
I know you guys (ML team) has been working on 1100d last month (march) and while surfing, i kinda saw this post from bitbucket: https://bitbucket.org/nanomad/magic-lantern-for-1100d/src

May I ask, is this a working one or still a test version. Please reply. Thanks ML team, awesome as always :)

User:Effifly

2012-05-14T09:32:45Z

New user account

User:Philip1978

2012-05-14T05:28:42Z

New user account

User:Franzy972

2012-05-13T16:47:27Z

New user account

User:Aram Sardar

2012-05-13T11:07:13Z

New user account

User:Chokchen

2012-05-13T06:18:37Z

New user account

User:BigGee537

2012-05-13T05:53:22Z

New user account

User:TheDanish

2012-05-12T23:31:49Z

New user account

User:Ryanp777

2012-05-12T17:54:24Z

New user account

User:Francescodb

2012-05-12T15:51:55Z

New user account

User:Gluap

2012-05-12T11:37:34Z

New user account

User:Brittapotthoff

2012-05-12T08:36:22Z

New user account

User:Srubino89

2012-05-12T04:06:41Z

New user account

User:Toddterry

2012-05-12T03:56:30Z

New user account

Unbricking

2012-05-11T21:04:55Z

ERR70 at every startup:

← Older revision		Revision as of 21:04, May 11, 2012
(One intermediate revision not shown)
Line 20:		Line 20:
	* PROP_PIC_QUALITY (0x80000031 on 550D)		* PROP_PIC_QUALITY (0x80000031 on 550D)
	* PROP_MOVIE_SOUND_RECORD* (0x2050013-0x2050015 on 5D Mark II 2.1.1)		* PROP_MOVIE_SOUND_RECORD* (0x2050013-0x2050015 on 5D Mark II 2.1.1)
		+	* PROP_VIDEO_MODE (0x80000039 on 5D Mark III 1.1.2)
		+
		+	==='''Solution 0'''===
		+	'''Simply reboot the camera without a card and clear the settings.'''

	===Solution 1===		===Solution 1===

Talk:New feature requests

2012-05-11T20:13:34Z

ISO/WB/VOL/LCD control change in t2i, possibly other models:

← Older revision		Revision as of 20:13, May 11, 2012
(One intermediate revision not shown)
Line 70:		Line 70:

	'''[[Special:Contributions/86.163.57.32\|86.163.57.32]] 07:07, May 11, 2012 (UTC)'''		'''[[Special:Contributions/86.163.57.32\|86.163.57.32]] 07:07, May 11, 2012 (UTC)'''
		+
		+	== ISO/WB/VOL/LCD control change in t2i, possibly other models ==
		+
		+	In movie mode Id like to see the the controls for these four items to be adjustable with the wheel. I think the best way to approach this is press and hold flash, with left or right buttons, select ISO/WB/VOL/LCD. Once selected, use wheel to adjust value up or down. If there is another value youd like to change, the menu is open as long as the flash button in pressed.
		+
		+
		+
		+	This leaves the sensor free since vol and lcd are moved. Could that be a hands free shutter release through motion detetion.
		+
		+	[[User:AttilaGyulaBalazs\|AttilaGyulaBalazs]] 20:13, May 11, 2012 (UTC)