Installation:
1) Format the card from the camera.
2) Make sure you are running Canon firmware 1.1.1 (http://www.usa.canon.com/cusa/support/consumer?pageKeyCode=prdAdvDetail&docId=0901e024805866b7).
3) Copy ML files (http://builds.magiclantern.fm/) on the card and run Firmware Update.
Uninstallation:
1) Run Firmware Update from your ML card.
2) Follow the instructions.
(http://a1ex.magiclantern.fm/bleeding-edge/new-installer.png)
Discussion thread for the 60D. I don't own this camera, so if there is anything you feel is important for this camera and should be in this opening post, please let me know.
Right, So far so good, but I'm kinda stuck on the Firmware Update instruction. How does one do this? I can find nothing in any of the software or on the camera and my users manual has long since bitten the dust (drowned, actually, but that's a whole other story).
Please ... (http://lmgtfy.com/?q=canon+eos+60d+user+manual+download)
There's no need to be so snarky. Some of us just aren't part of the IT generation.
But thanks anyway. Now I just have to work out how to make the ML stuff work.
Which would be easier if I could get all the files to unzip. But they won't. I've run into this before on the Mac but what worked for that item doesn't work here. I knew this would be too good to be true.
You're not trying to extract the autoexec.bin file are you (OSX may think this is some sort of compressed file based on the file extension, but it is not, it is the ML binary code that is loaded by the camera)?
Only extract the actual zip file you download (which extracts just fine on my Mac), and copy those files to an SD card as is (preserving the exact folder structure).
@cybercretin,
I've found that sometimes when I download an ml build it only downloads partially (probably just a slow connection on my end), so the zip file looks like it's there but it won't open. So then I download it again.
Thanks, fellas.
I've downloaded it three times, same result. Tried extracting just the downloaded file, installed as directed, nothing happens. It goes onto the card, along with the firmware update, but when I turn the camera back on, there's no change.
I must be doing something wrong, but I don't know enough about what's supposed to be happening to spot what it is. Pity, ML has some very useful functions.
Have you tried to press trashcan button some seconds after camera starts up?
@cybercretin
Snarky? Your first post here is: "I don't know how to find the firmware/manual for a Canon 60D."
Every hear of Canon USA?
http://www.usa.canon.com/cusa/consumer/products/cameras/slr_cameras/eos_60d
You know, where you can download the firmware and manual super easy for FREE even?
Not part of the IT generation or just lazy?
Ever think ML just isn't for you? You can BRICK your camera, you know?
Is there any chance to add AF Microadjustment to 60D, if it is even possible?
Uh.. it cannot be done. Saw this thread after posting:
http://www.magiclantern.fm/forum/index.php?topic=950.0
Ronsky
I understand I need 1.1.3 firmware but I cannot find instruction on how downgrade from 1.1.4 to 1.1.3
Please let me know how downgrade. Many thanks
First post of this thread and RTFM. Downgrade firmware = Upgrade.
And you are wrong about the version.
I hate to sound like a newbie and that's probably because I am. I want to install ML on my 60D but can't find the download on the download page. I find only nightly builds. Is that suitable for someone who had nothing related to ML on his camera. They sound like updates to me and I have nothing to update. If I download and install the latest nightly build is that the same as downloading and installing a stable build?
Thank.
Stable is really old, the nightly is the new stable and the way to go: http://builds.magiclantern.fm
Have been shooting raw video on the 50D for a while and decided to finally do the same on my 60D. I thought I had set everything up the way I usually do with the ML menus (I went through them both together with both cameras, just to be sure), but with the 60D it doesn't seem the same. I don't get the usual framing for 2.39:1 aspect ratio that I have chosen (it seems more like 16:9), and I can't see the live RAW histogram to judge exposure though I have set it on in the menus.
Thanks for all the advice.
Took three downloads and umpty-dozen attempts at the update process but it's finally in. Now I just have to work out how to use the functions I want - but there is a User Guide so a little patience and a lot of studying and experimentation . . .
Hey there,
Just to thanks the whole dev team to provide a tool like ML. I'm an open source enthusiast (using and working with GNU/Linux & Unix systems for many years) and I just discovered the project, replace my old Nikon D3100 with a 60D. Fabulous.
Thanks again. :))
Quote from: maatunix on April 18, 2015, 09:58:54 PM
Just to thanks the whole dev team to provide a tool like ML. I'm an open source enthusiast (using and working with GNU/Linux & Unix systems for many years) and I just discovered the project, replace my old Nikon D3100 with a 60D. Fabulous.
If you plan to use Darktable and RAW MLV video or Full-res silent pics/MLV see this tip too: http://www.magiclantern.fm/forum/index.php?topic=9560.msg142928#msg142928 (http://www.magiclantern.fm/forum/index.php?topic=9560.msg142928#msg142928) ;)
Hey thanks, that would help me. ;D
I want to shoot continuous 1080p Raw with my 60d running magic lantern. Currently, it stops recording in about 10 secs max. is there any way out? Is it possible by capturing it in the laptop through an HDMI cable, using the laptop as an external recorder? is there ANY way out?
I think the only way that could happen is if you use a low frame rate.
24 fps? If not then how much?
According to my math, about 6 fps. Not really video.
I recently did a test with the 15th April nightly build. Using a 16 GB SanDisk Extreme Pro 95 Class 10 card, shooting 2.39:1 (to help reduce datarate a bit more) and at max res of 1728 x 724, I got the following:
25 fps = 270 frames (for 10 seconds).
20 fps = 327 frames (for 13 seconds).
16 fps = 440 frames (for 17 seconds).
I didn't think there was much point in going lower than 16 fps.
Hi there!
First post, so bear with me if I ask silly things.
But I searched the forum and did not find anything about this. I want to know if anyone has experience with using ML on a Canon 60Da. As the 60D and the 60Da cameras are nearly identical I don' think there should be any negative impact of the difference, but I want to make sure before I do something wrong.
Thanks!
Alex
I use a 60Da. It works fine. The only difference between the two is the optical filter in front of the sensor. Electronically/internally they are identical.
Thanks for the reply... looks like i know what i'm doing this weekend! :)
Ok, so I've noticed quite a few people around asking specifically how to install ML who aren't able to do it, and the step that most are missing is actually updating the firmware once the files are on your SD card which is performed as follows. (If you've never updated your camera's firmware, you probably don't know how to install custom firmware, right?)
1) Make sure camera is in Manual mode (M)
2) Go to the third settings menu (Wrench icon w/ 3 dots)
3) Highlight the last line, which lists your firmware version (Should be 1.1.1 currently)
4) Click set, this will bring you to the firmware update screen
5) Click "OK"
6) Magic Lantern will install
7) Restart your camera.
I hope this has helped some folks!
Hi,
I installed the nigtly build 2015-05-03 01:15:02 +0300 on my 60D, but I cannot find the raw mode. Is it there?
Module tab ...
My question is twofold.
I was trying to use ML on multiple cards and went through the process as outlined. However, I was only able to get it to work on the original card. After an hour of trying to figure it out, in my frustration, I accidentally did a deep format on the original card. Now ML does not work on any card. The real problem is that now the firmware update menu option has disappeared. So now I can't uninstall/reinstall ML from ANY card.
Any idea what I should do? And possibly why I couldn't use multiple cards?
Thanks
Dial M for ... Redo installation for all cards
Hi there,
when filming with the 60D I always used the VAF-60D Anti Moiré Filter by Mosaic Engineering. It really extinguishes the unwanted aliasing/moiré from the footage and gives it a professional look (see http://mosaicengineering.com/products/vaf/60d/main.html (http://mosaicengineering.com/products/vaf/60d/main.html)). Now I am changing to the Blackmagic Design Pocket Cinema Camera and don't need it anymore. I payed € 323,96 for it and I would like to sell it for € 200 incl. free shipping.
Regards,
Robert
No, there is no proof or guarantee your camera will not get harmed and if it breaks you can keep both parts.
There is however no report about ML nightly build actually killing a single camera. You can be the first, though.
If you can't live without your cam and will be unable to get a replacement ... well, think it over.
I have had ML installed for awhile. I use it for HDR mostly. Playing more with it now. Want to shoot lightning. Photo not video. Tips?
Anyways.... i have version v2.3.60d.111
Built on 2012-07-23
Any benefits to updating? What to download to update?
I do not see any secure / approved / builds.... just nightly builds.
Any help / suggestions appreciated.
And yes, I am shooting a 60D. Thanks
"Stable" v2.3 is considered to be unstable/outdated. Nightly build is the new black.
Devs using something close to "rolling release" (look it up at wikipedia) for some time now. So don't expect to see something like 2.4 or else in near future.
With nightly there is a module at hand: http://www.magiclantern.fm/forum/index.php?topic=6303.msg48426#msg48426
1.) Top of page -> User Guide -> FAQ
2.) Dito and Top of page -> User Guide -> Installation Guide
3.) Sorry, no ML 101 available right now.
http://www.magiclantern.fm/forum/index.php?topic=11269.0
Do you try to understand exposure modes used by "native" Canon firmware?
- Center-weighted average, spot metering, partial metering, evaluative metering
- Flash ETTL-2 modes "Evaluative", "Average"?
Canon does not publish their source code. If you simply want to understand what the various modes are for and when to use them, I would refer you to p119 in your manual.
Hi Installed ML on my 60d today,
there is no bulb ramping?
I used ML a few years ago and loved the bulb ramping intervalometer combo, but I can see it in the menu anywhere?
Gone for good.
Top of page, a little way down
Home - Help - Search - Profile - My ...
I downloaded this because my camera keeps shutting off. Which it didn't fix but also, when recording it seems to record at 2x speed? Any thoughts? This is on a 60d
@dfort has a build for the 60D to fix the mv640crop mode video. He needs a someone with a 60D to help him test it.
http://www.magiclantern.fm/forum/index.php?topic=12608.msg165718#msg165718
installed on my 60D last week. afew video settings in ML caused 60D to crash : ERROR 70
didnt save log files due to me going into panic mode thinking that 60D was about to get bricked.......shutdown camera and started up, still error 70....
shutdown and pulled battery out and restarted and ML presented with camera didnt shutdown properly and last config files didnt save and gave the option to delete the last config.....hit that yes button super fast and default ML settings took place......phewww
Battery definitely drains ALOT faster with ML, there are some really nifty tweaks that im not familiar with...luckily google and Youtube is my friend.
is there a complete list to what each setting or module does as that would be super helpful as half of the help files are not complete or exists on ML when intalled.
Quote from: tolga1970 on April 14, 2016, 10:32:09 AM
Battery definitely drains ALOT faster with ML,
Each and every time someone comes up with this one and we are trying to nail it down the issue is no longer reproducable. If your incident is we will be more than happy to hunt it down.
Please give steps to reproduce and measurements/battery uptime with/w.o. ML.
Quote from: tolga1970 on April 14, 2016, 10:32:09 AM
is there a complete list to what each setting or module does as that would be super helpful as half of the help files are not complete or exists on ML when intalled.
Top of page -> User Guide
Top of page -> Downloads -> Download Nightly Builds -> Features
I'm still working on the mv640crop issue. Looking for testers:
http://magiclantern.fm/forum/index.php?topic=12608.msg165718#msg165718
I've installed ML on my 60D with no issues. Now, how do I make it work with additional SD cards?
Top of page -> User Guide -> Install Guide
Hello,
I'm trying to uninstall magic lantern (ML version : Nightly.2016Apr19.60D111) from my camera but the "firmware version" menu has disappeared.
I don't know what to do. Any help?
Manual page 278. Last line.
Which manual?
Firmware details appears only in P/Tv/Av/M/B/C modes. In other modes it wont appear.
Currently the download page for the nightly's is down. I guess they are re configuring it for something. They aren't sure when its going to be back up. I guess it depends on the volunteers. But I guess its my bad luck, because I need to download ML for my 60D. Would any of you who already have a recent or last stable nightly be able to send it to me? Not sure the size of it, but it might be able to be emailed if its not too big. Or google drive or something like that would work.
http://magiclantern.fm/forum/index.php?topic=17924.msg172418;topicseen#msg172418
Awesome! Thanks
My good ol' 60d recently made a motor sound at shill shooting it definitely shouldn't make and then died ... well, it has 330k shutter cycles. Now it doesn't do anything when turned on and I wonder if anyone knows how to diag what's wrong with it.
Does "doesn't turn display on" mean it's completely dead, like damaged a circuit board? Or could have a broken shutter or shutter motor have the same effect'?
I'm asking b/c there are rather cheap parts available for the 60d from China (either just the shutter blades or the shutter assembly), and I wonder if trying to fix it with the help of a friend of mine is worth it. With a new shutter, the one moving part would be replaced, everything else is fine.
What does the display test (http://www.magiclantern.fm/forum/index.php?topic=14732.0) say?
If there's no sign of life, it's most likely a hardware issue. Probably it's best to check the fuses first.
My Vertion 2016-10-09 10:20
I loaded the Raw_Rec.mo Moduel for shooting raw and when I got my footage back it was all good. I took the RAW and converted it to a DNG. If I open it with Photoshoop and look at it there is nothing wrong I can color grade it fine and make it into a video.
The problem now is when I load it up into Davinci Resolv and look at the video it has these tiny random black dots. It looks like dead pixles. They are fixed in place and basically look like bits of dust on your monitor but it is acctualy the video.
All Information on the topic
Immage sequences are fine
Only Problem while in Davinci Resolv
I used a RAW to DNG Converter
http://www.phreekz.de/wordpress/2014/04/magiclantern-raw2cdng-1-5-0/
Picture of a frame from davinci resolv You can see the random black dots. (Also yes thats my food I was testing it)
https://www.dropbox.com/s/jesjo05e6fg1kl8/Untitled_1.4.1.jpg?dl=0
I'm running magiclantern-Nightly.2016Sep16.60D111.zip on a 60D.
Has anyone seen this?
The camera just started booting to the info screen on power-up. Usually it presents a 'cleaning sensor' message. No more. All buttons are dead except for the shutter button. The exposure and f-stop dials work. One can take a picture. It is stored on the SD Card. The camera auto-focus function is dead. The view finder focus points are absent. One cannot view the picture, call up magic lantern by pressing DELETE, or access the Canon menu by pressing MENU.
Since the camera was fine until yesterday, something changed. Do I have a broken (damaged) camera or a magic lantern S/W problem?
Nothing changed after removing the battery and card, followed by installing the battery only. Same probem.
Remove battery, remove card.
Insert battery, do not insert card.
Startup cam and post results.
Hallo every body,
I can't install with ESO utility (last version) the Cinestyle or any other picture style on C (Camera) section but only on M (Manual).
I have last firmware 1.1.1 and Naughtly 2016Aug24
What is wrong?
Please help, thanks!
anybody is there :(
please help!
Sorry, not clear what the error is.
1. You were able to install a picture style.
2. It shows up in M mode but not in any other mode.
3. Does it work in photo/stills and movie mode?
Have you tried an older EOS Utility Version (v2.x)?
Hi Walter,
1 - I never had problem to install Picturestyle before.
2 - I don't have a old EOS utility version (maybe you?)
3 - With last EOS I can install Cinestyle (and any other desired picture style) only on M (manual). When I switch to Camera this set up is disabled.
So, When I fire up the camera on M (manual , EXPO, I can see (or choose) : Picturestyle > Cinestyle... but if I switch to Camera mode, EXPO, I can see UserDef1...
Sorry, we have a communication problem.
There are different modes (for example P, M, Tv, Av, B, C (Camera User Setting), Movie)).
I have no idea what you are trying to tell me with "Camera mode" because I assume every mode available on your cam is a camera mode.
So please clarify *what* happens *where/when*.
Does the error occur without ML running, too?
http://www.magiclantern.fm/forum/index.php?topic=17808.0
Sorry Walter,
alex gave a link right to my very recent post... sorry everybody, maybe i seriously have to visit a doctor... ::)
60D boots into info menu at power up, all buttons dead except for shutter, aperture and exposure dial work, af dead, af pont display dead.
Nothing changed after removing the battery and card, followed by installing the battery only. Same probem.
CaptGreg: Perhaps it's totally no the same problem but I had an issue one time when doing stack focusing. Camera hang, and I had to remove battery. But when I restarted the camera, it behave strangely like also as you said no autofocus was working ans some other issues.
Then I find that pressing the joystick button in AF mode change the focus ... so the camera was setted by ML and has the camera hang (due to t° certainly), it doesn't restore the "normal parameters".
My solution was to go to canon menu and then use the "Clear all camera settings".
But if you cannot access canon menu, I really don't know how to help :(
Yes, it would be sweet if the menu button worked. I could then navigate to the reset menu and reset the camera. That just might solve the problem.
I tried running the camera tethered over a USB cable to a computer using the 'gphoto2 library' program 'entangle'. All read-back status info such as ISO, aperture, shutter speed, copyright, color temperature, etc worked. Setting camera parameters failed. The error message was 'PTP failed: camera busy'.
What did you do before the crash?
Please send me a good copy of your ROM (in ML/LOGS on some old card) and a bad copy (delete ML/LOGS/ROM*.BIN, start the camera and let ML re-create these files). If the ROM files are not re-created when starting with a ML card, use this dumper (http://www.magiclantern.fm/forum/index.php?topic=16534.0).
I have loaded ML onto my 60D specifically to use the in camera intervalometer. All is working fine except I cannot activate the 'start after' function. I can set the number of seconds but it doesn't activate. The 'stop after', 'take a picture every' and 'start trigger all work'. Can anyone help?
I need some help!! My camera keeps saying "Incorrect firmware version. Expecting firmware version 1.1.1" I have 1.1.2. Will it not work with 1.1.2? And if it does still work, can you give me help with how to install it properly as I'm not sure if I'm doing it correctly XD
XD!
Quote from: OwenGuerin on January 10, 2017, 12:39:11 AM
I need some help!! My camera keeps saying "Incorrect firmware version. Expecting firmware version 1.1.1" I have 1.1.2. Will it not work with 1.1.2? And if it does still work, can you give me help with how to install it properly as I'm not sure if I'm doing it correctly XD
You need 1.1.1. You can just put it on the SD card and run firmware update to downgrade to 1.1.1.
Found working 1.1.1 link on google: http://support-nz.canon.co.nz/contents/NZ/EN/0400055002.html
I have used ML for years, but to day I tried to update to the newest firmware fc3ec35: marts 30 2017, but got a message on the camera update screen "Update not possible file 1.1.1. must be present" or something like this, update was not possible, firmware 1.1.1. was present, tried several times, finely I decided to update to an earlier version, no problem.
Fixed, rebuilding the nightlies.
Can anyone be kind enough to tell me how [ step by step ] to go back to firmware 1.1.1 as my 60D is at 1.1.2 and I would like to run under ML. I have downloaded 1.1.1 from the net. Thanking you in advance. Jeff.
Unzip file and follow instructions located in dir "update-procedure-pdf".
G'day Walter, Thank you for your prompt answer, May I ask where do I find this file, [dir/update-procedure-pdf] I have searched MF and the forum, but am unable to find it, Thank you. Jeff.
Link to Canon's firmware file 1.1.1 is included in install instructions on Nightly Build download page for your cam. Or use http://pel.hu/eoscard
If you are on OS X/macOS: Just unzip.
Here what i found on the web:
https://www.dropbox.com/s/gz50t04h4chxvhv/EOS%2060D%20Parts%20catalog.pdf?dl=0
60D part catalog! I got also for 7D, 5DII, 5DIII and 600D.
Might be some help for retroengineering?!
Cheers.
Quote from: Exo on November 20, 2017, 01:52:47 AM
Here what i found on the web:
https://www.dropbox.com/s/gz50t04h4chxvhv/EOS%2060D%20Parts%20catalog.pdf?dl=0
60D part catalog! I got also for 7D, 5DII, 5DIII and 600D.
Might be some help for retroengineering?!
Cheers.
It just goes down to "printed circuit board" level, it does not even list the integrated circuits in that board... I do not think it can be used for reverse-engineering, unfortunately. However, service manuals do have that information (and more); those could be useful.
Okay, this is the closest i got: 40D
http://cholla.mmto.org/photography/gear/repair/eos_40d_service_manual.pdf
Otherwise:
http://pdfwhiz.org/lp4/?title=canon%2060d%20service%20manual%20pdf
But don't count on me putting any credit card infos in that king of a website.
Quote from: Exo on November 20, 2017, 11:48:09 PM
Okay, this is the closest i got: 40D
http://cholla.mmto.org/photography/gear/repair/eos_40d_service_manual.pdf
Otherwise:
http://pdfwhiz.org/lp4/?title=canon%2060d%20service%20manual%20pdf
But don't count on me putting any credit card infos in that king of a website.
Yes, the "2. BLOCK DIAGRAM > 2-1 GENERAL" on page 151 could be interesting, if there is something there that developers still do not know.
I have a Canon 60D which has 1.1.2 firmware installed. I would like to use Magic Lantern ... I have looked for a 1.1.1 firmware and find that it has been removed from Canon's web site. I've searched elsewhere and it appears one can not just downgrade to an earlier firmware on this camera. Unless that is untrue, can you let me know the correct steps for getting back to version 1.1.1. I think once I have accomplished that, I should be able to install Magic Lantern.
Is there a link somewhere, -anywhere-, to get this?
Thank you!
Hello Everyone,
I wanted to install Magic Lantern on my Canon EOS 60d, however, I can't find the Canon Firmware 1.1.1. They only have latest firmware 1.1.2. Would you be able to share the download link or dropbox link to canon 1.1.1 firmware for Canon 60d?
Thanks
sixb
Quote from: sixb on November 29, 2017, 05:58:46 AM
Hello Everyone,
I wanted to install Magic Lantern on my Canon EOS 60d, however, I can't find the Canon Firmware 1.1.1. They only have latest firmware 1.1.2. Would you be able to share the download link or dropbox link to canon 1.1.1 firmware for Canon 60d?
Thanks
sixb
In the thread I found this link:
http://pel.hu/eoscard
Nice to know pelican's site is recovering.
Hello, I seem to have a problem with live audio playback. Using a mini-usb to 3.5mm jack adapter and the newest version of ML installed (2017-12-19) I get absolutely no audio through my headphones. Do I need the sescom cable or the cable that came with my camera instead? Or is it something with ML? Thanks in advance.
I was able to update my 60D with the ML firmware, I'm having 2 issues and I was hoping you guys might have some ideas.
1. When I am focusing to shoot video, there is plenty of light as it adjusts, but as it locks in focus, it becomes very dim. It's odd. I feel like there is some setting that is off - it was doing this before I downloaded ML, I was hoping this might affect or resolve. Only for video.
2. When I start to record, it only lasts a few seconds, sometimes a little longer, and then stops recording automatically. Empty card, plenty of storage, I cannot figure it out. Again happened before ML install.
I am hoping there is some setting or something I have accidentally adjusted wrong. Any tips or advice on how to troubleshoot is greatly appreciated. Thanks!
It's been many years since I installed Magic Lantern on my 60D. The version I have is v2.3.60D.111 from July 2012. The camera menu shows firmware version 1.1.1-ml-v2.3. What's the best way to upgrade to the current version? Can it just be directly upgraded by copying the files to the memory card and doing the firmware update in the camera? Or is it best to uninstall the old version and then install the new version from scratch?
Use a non-ML card (can be a small and slow one). Format card in cardreader, format card in cam.
Update cam with Canon firmware 1.1.6 using this card.
Now back to your ML card: Remove/rename *.fir, autoexec.bin and ML directory before copying nightly build files to card.
Insert ML card and enjoy.
Thanks for the info. Now, if I upgrade and it doesn't work right or I don't like it, is it equally straightforward to downgrade back to the old version I have?
Ok, I'm confused here. You said to update with Canon firmware 1.1.6. If you mean firmware from the Canon website, the only firmware they offer is v11.2.
If you're talking about ML firmware, what's listed for the 60D is version 1.1.1.
If you did specifically mean ML firmware 1.1.6, the only one that shows that version number is for the Canon 6D (not the 60D).
Please advise, thanks! (I'll admit, I'm stupid when it comes to figuring this stuff out. I'm the kind of person that needs detailed step-by-step instructions.)
Quote from: Walter Schulz on February 26, 2018, 04:41:58 PM
Use a non-ML card (can be a small and slow one). Format card in cardreader, format card in cam.
Update cam with Canon firmware 1.1.6 using this card.
Now back to your ML card: Remove/rename *.fir, autoexec.bin and ML directory before copying nightly build files to card.
Insert ML card and enjoy.
Looks like there's some confusion over firmware on the 60D. Current working Magic Lantern version is for 1.1.1 and latest Canon firmware is at 1.1.2. If anyone has a 60D.112 firmware dump please PM me. Thanks!
Quote from: dfort on April 13, 2018, 07:14:22 AM
Looks like there's some confusion over firmware on the 60D. Current working Magic Lantern version is for 1.1.1 and latest Canon firmware is at 1.1.2. If anyone has a 60D.112 firmware dump please PM me. Thanks!
i can help you dump the 1.1.2 firmware but the method from CHDK doesnt seem to work
the portable rom dumper needs signed firmware right?
@jai554 - Great!
Steps:
- Make sure you have ML working on your 60D, prepare a few cards with ML. Sometimes the card gets corrupted and usually smaller capacity cards cards work better than the large ones. The important part is that your camera and card bootflags are set. The ML installation does that.
- Download the 60D Canon Firmware for Testers.zip from my downloads page: https://bitbucket.org/daniel_fort/magic-lantern/downloads/ in there you'll find the Canon firmware updaters to get you to 112 and back to 111.
- Put both firmware updaters on either an SD card formatted without the bootflag set -or- on a ML prepared card with the bootflag set but remove the ML-SETUP.FIR file from the card.
- Download the Portable firmware dumper from here: http://a1ex.magiclantern.fm/debug/portable-rom-dumper/autoexec.bin
- Put the Portable firmware dumper (just an autoexec.bin file) on a card that has the bootflag set. It should dump the 1.1.2 firmware when you run it in camera. It might not work the first time or you might need to run it on a few different cards. You can read more about it here: http://www.magiclantern.fm/forum/index.php?topic=16534.0
- Zip up the files and PM me. Don't share openly on the forum!
In case that doesn't work, try the blind dumper: https://a1ex.magiclantern.fm/bleeding-edge/blind-dumper/autoexec.bin
- You'll need to have a valid image on your card so when you press the playback button it has something to playback.
- Again, on a card with the bootflag set and a valid in the proper directory, put the blind dumper autoexec.bin file on the card and start the camera.
- Press the Playback button.
- You should get a new file in the root directory of your card, on the 500D it was named "As" and that should be the firmware dump.
If you're interested in how to port ML to a Canon firmware update you check out my tutorial (https://www.magiclantern.fm/forum/index.php?topic=19417.0).
Quote from: dfort on April 14, 2018, 12:31:19 AM
@jai554 - Great!
Steps:
- Make sure you have ML working on your 60D, prepare a few cards with ML. Sometimes the card gets corrupted and usually smaller capacity cards cards work better than the large ones. The important part is that your camera and card bootflags are set. The ML installation does that.
- Download the 60D Canon Firmware for Testers.zip from my downloads page: https://bitbucket.org/daniel_fort/magic-lantern/downloads/ in there you'll find the Canon firmware updaters to get you to 112 and back to 111.
- Put both firmware updaters on either an SD card formatted without the bootflag set -or- on a ML prepared card with the bootflag set but remove the ML-SETUP.FIR file from the card.
- Download the Portable firmware dumper from here: http://a1ex.magiclantern.fm/debug/portable-rom-dumper/autoexec.bin
- Put the Portable firmware dumper (just an autoexec.bin file) on a card that has the bootflag set. It should dump the 1.1.2 firmware when you run it in camera. It might not work the first time or you might need to run it on a few different cards. You can read more about it here: http://www.magiclantern.fm/forum/index.php?topic=16534.0
- Zip up the files and PM me. Don't share openly on the forum!
In case that doesn't work, try the blind dumper: https://a1ex.magiclantern.fm/bleeding-edge/blind-dumper/autoexec.bin
- You'll need to have a valid image on your card so when you press the playback button it has something to playback.
- Again, on a card with the bootflag set and a valid in the proper directory, put the blind dumper autoexec.bin file on the card and start the camera.
- Press the Playback button.
- You should get a new file in the root directory of your card, on the 500D it was named "As" and that should be the firmware dump.
If you're interested in how to port ML to a Canon firmware update you check out my tutorial (https://www.magiclantern.fm/forum/index.php?topic=19417.0).
Sorry i got a bit confused
i need to install firmware 1.1.2 first right?
then insert the card with ML working with the modified autoexec.bin?
Edit:
Nvm, i got it working now
dumping the rom :)
wish me luck haha XD
It worked perfectly. Thanks!
(https://farm1.staticflickr.com/874/26570893247_1e68f0751b.jpg) (https://flic.kr/p/GtYLR6)
Got it:
(https://farm1.staticflickr.com/789/39636531210_6205b6b75e.jpg) (https://flic.kr/p/23oxzP9)
Here's a behind the scenes look:
(https://farm1.staticflickr.com/820/40731141874_f405429d9b.jpg) (https://flic.kr/p/254gKqN)
Test build on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). [EDIT] This is an early test build without a .FIR file so if you want to try it out make sure ML is running on your 60D.111 before doing the Canon firmware update to 1.1.2. ML-SETUP.FIR updated so you can install ML using the test build.
Quote from: dfort on April 14, 2018, 09:30:01 AM
Got it:
(https://farm1.staticflickr.com/789/39636531210_6205b6b75e.jpg) (https://flic.kr/p/23oxzP9)
Here's a behind the scenes look:
(https://farm1.staticflickr.com/820/40731141874_f405429d9b.jpg) (https://flic.kr/p/254gKqN)
Test build on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). This is an early test build without a .FIR file so if you want to try it out make sure ML is running on your 60D.111 before doing the Canon firmware update to 1.1.2.
tested and running just fine on my 60d 1.1.2
i tested on 2 different memory card. 1 with ML preinstalled 1 without ML.
one without ML i made it work using EOScard
Quote from: jai554 on April 14, 2018, 05:28:42 PM
...i made it work using EOScard
a1ex made a ML-SETUP.FIR for 1.1.2 so with the latest test build you should be able to install ML -- which basically sets the bootflag on both the camera and card.
Quote from: dfort on April 14, 2018, 06:09:38 PM
a1ex made a ML-SETUP.FIR for 1.1.2 so with the latest test build you should be able to install ML -- which basically sets the bootflag on both the camera and card.
removed ML from my camera, formatted the card
reinstalled using the latest build
all working perfectly!
thanks!
Great -- pull request posted (https://bitbucket.org/hudson/magic-lantern/pull-requests/917/update-to-60d112/diff).
@dfort
Been using the latest FIR 1.1.2 build quite a bit
Passes all STUBTEST but in LUATEST the camera turn off by itself when "Setting ISO to random values..."
Let's try the newer tests that are in the lua_fix branch. Uploaded a test build to my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
@dfort
===============================================================================
ML/SCRIPTS/api_test.lua - 2018-4-19 13:20:38
===============================================================================
Strict mode tests...
Strict mode tests passed.
Generic tests...
arg = table:
[0] = "api_test.lua"
camera = table:
shutter = table:
raw = 99
apex = 5.375
ms = 24
value = 0.024097
aperture = table:
raw = 22
apex = 1.75
value = 1.8
min = table:
raw = 22
apex = 1.75
value = 1.8
max = table:
raw = 80
apex = 9.
value = 22.6
iso = table:
raw = 80
apex = 6.
value = 200
ec = table:
raw = 0
value = 0
flash = true
flash_ec = table:
raw = 0
value = 0
kelvin = 5200
mode = 3
metering_mode = 1
drive_mode = 0
model = "Canon EOS 60D"
model_short = "60D"
firmware = "1.1.2"
temperature = 163
gui = table:
menu = false
play = false
play_photo = false
play_movie = false
qr = false
idle = true
bulb = function: p
wait = function: p
burst = function: p
reboot = function: p
shoot = function: p
event = table:
pre_shoot = nil
post_shoot = nil
shoot_task = nil
seconds_clock = nil
keypress = nil
custom_picture_taking = nil
intervalometer = nil
config_save = nil
console = table:
write = function: p
clear = function: p
hide = function: p
show = function: p
lv = table:
enabled = false
paused = false
running = false
zoom = 1
overlays = false
stop = function: p
pause = function: p
resume = function: p
wait = function: p
info = function: p
start = function: p
lens = table:
name = "EF50mm f/1.8 II"
focal_length = 50
focus_distance = 0
hyperfocal = 73199
dof_near = -109905601
dof_far = 1000000
af = true
af_mode = 0
autofocus = function: p
focus = function: p
display = table:
idle = nil
height = 480
width = 720
notify_box = function: p
print = function: p
load = function: p
draw = function: p
off = function: p
rect = function: p
on = function: p
clear = function: p
pixel = function: p
circle = function: p
screenshot = function: p
line = function: p
key = table:
last = 10
wait = function: p
press = function: p
menu = table:
visible = false
open = function: p
get = function: p
close = function: p
select = function: p
block = function: p
set = function: p
new = function: p
movie = table:
recording = false
stop = function: p
start = function: p
dryos = table:
clock = 42
ms_clock = 42554
image_prefix = "IMG_"
dcim_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
config_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "ML/"
path = "ML/SETTINGS/"
ml_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 2208
folder_number = 100
free_space = 31119808
type = "SD"
path = "B:/"
_card_ptr = userdata
shooting_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 2208
folder_number = 100
free_space = 31119808
type = "SD"
path = "B:/"
_card_ptr = userdata
date = table:
sec = 39
min = 20
hour = 13
wday = 6
isdst = false
day = 19
yday = 1
year = 2018
month = 4
call = function: p
rename = function: p
directory = function: p
remove = function: p
interval = table:
time = 10
count = 0
running = false
stop = function: p
battery = table:
level = 35
id = 1
performance = 2
time = nil
drain_rate = 33
task = table:
create = function: p
yield = function: p
property = table:
Generic tests completed.
Module tests...
Testing file I/O...
Copy test: autoexec.bin -> tmp.bin
Copy test OK
Append test: tmp.txt
Append test OK
Rename test: apple.txt -> banana.txt
Rename test OK
Rename test: apple.txt -> ML/banana.txt
Rename test OK
File I/O tests completed.
Testing Canon GUI functions...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Start LiveView...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Resume LiveView...
Pause LiveView...
Enter PLAY mode...
Exit PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Stop LiveView...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Start LiveView...
Enter PLAY mode...
Exit PLAY mode...
Pause LiveView...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Resume LiveView...
Enter MENU mode...
Enter PLAY mode...
Exit PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Pause LiveView...
Resume LiveView...
Pause LiveView...
Enter PLAY mode...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Stop LiveView...
Start LiveView...
Enter PLAY mode...
Enter PLAY mode...
Enter MENU mode...
Exit MENU mode...
Enter MENU mode...
Enter MENU mode...
Enter MENU mode...
Enter PLAY mode...
Enter PLAY mode...
Exit PLAY mode...
Stop LiveView...
Start LiveView...
Enter MENU mode...
Enter PLAY mode...
Enter MENU mode...
Canon GUI tests completed.
Testing ML menu API...
Menu tests completed.
Testing picture taking functions...
Snap simulation test...
Single picture...
B:/DCIM/100CANON/IMG_2209.CR2 not found.
B:/DCIM/100CANON/IMG_2209.JPG: 5662879
Two burst pictures...
Ideally, the camera should be in some continuous shooting mode (not checked).
B:/DCIM/100CANON/ABC_2210.CR2 not found.
B:/DCIM/100CANON/ABC_2210.JPG: 5729078
B:/DCIM/100CANON/ABC_2211.CR2 not found.
B:/DCIM/100CANON/ABC_2211.JPG: 5664187
Bracketed pictures...
B:/DCIM/100CANON/IMG_2212.CR2 not found.
B:/DCIM/100CANON/IMG_2212.JPG: 5934052
B:/DCIM/100CANON/IMG_2213.CR2 not found.
B:/DCIM/100CANON/IMG_2213.JPG: 5712465
B:/DCIM/100CANON/IMG_2214.CR2 not found.
B:/DCIM/100CANON/IMG_2214.JPG: 754961
Bulb picture...
Elapsed time: 13157
B:/DCIM/100CANON/IMG_2215.CR2 not found.
B:/DCIM/100CANON/IMG_2215.JPG: 363953
Picture taking tests completed.
Testing multitasking...
Only one task allowed to interrupt...
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Main task yielding.
Task C started.
Task C finished.
Main task back.
Multitasking tests completed.
Testing half-shutter...
Half-shutter test OK.
Testing module 'lv'...
LiveView is running; stopping...
Starting LiveView...
Overlays: Canon
Overlays: Canon
Overlays: ML
Overlays: ML
Overlays: disabled
Overlays: Canon
Overlays: Canon
Overlays: Canon
Overlays: disabled
Overlays: ML
Overlays: disabled
Overlays: Canon
Overlays: Canon
Overlays: Canon
Overlays: Canon
Setting zoom to x1...
Setting zoom to x5...
Setting zoom to x10...
Setting zoom to x5...
Setting zoom to x1...
Setting zoom to x10...
Setting zoom to x1...
Pausing LiveView...
Resuming LiveView...
Stopping LiveView...
LiveView tests completed.
Testing lens focus functionality...
Autofocus outside LiveView...
Focus distance: 0
Autofocus in LiveView...
The test stops after finishing the autofocus test
Edit:
The test completes if i remove the lens but the screen is blank when it asks to switch to Av mode then Movie mode (im just guessing what to do hehe)
We had similar issues running the test on the 650D. So you got to the end of the test?
Quote from: dfort on April 19, 2018, 07:47:23 AM
We had similar issues running the test on the 650D. So you got to the end of the test?
I can get to the end only if i remove the lens.
I tried with 2 different lens.
Something doesn't look quite right here:
lens = table:
name = "EF50mm f/1.8 II"
focal_length = 50
focus_distance = 0
hyperfocal = 73199
dof_near = -109905601
dof_far = 1000000
af = true
af_mode = 0
Note the difference with a successful run on the 700D:
lens = table:
name = "EF28-105mm f/3.5-4.5 USM"
focal_length = 30
focus_distance = 1410
hyperfocal = 8518
dof_near = 1224
dof_far = 1666
af = true
af_mode = 0
Now the question is if the same issue is present in the 1.1.1 firmware. Could you try a regression test?
Does EF 50/1.8 II report focus distance to cam?
EDIT: Checked, it does not.
I also tried with tamron 17-50 vc. Same result
I will retest using the kit lens
Edit:
@dfort i forgot that my kitlens AF is broken
cant complete the test
Can anyone help test the latest build?
I can't test it :(
There's also issues completing the lens tests on the 650D. I'll post scripts to help us see what's going on with that. Just give me some time to get to it.
Ok--let's try to isolate that problem area. Let's start by running only the test that is failing. On your card under ML/scripts you'll see something like this:
(https://farm1.staticflickr.com/929/41632365321_98180b6519.jpg) (https://flic.kr/p/26qUKL6)
Open up the api_test.lua file with a text editor and scroll down to the end, you'll see this:
function api_tests()
menu.close()
console.clear()
console.show()
test_log = logger("LUATEST.LOG")
-- note: each test routine must print a blank line at the end
strict_tests()
generic_tests()
printf("Module tests...\n")
test_io()
test_camera_gui()
test_menu()
test_camera_take_pics()
sleep(1)
test_multitasking()
test_keys()
test_lv()
test_lens_focus()
test_camera_exposure()
test_movie()
printf("Done!\n")
test_log:close()
key.wait()
console.hide()
end
Comment out all the tests that you don't want to run. In our case we only want the test_lens_focus() so put a "--" in front of all the other tests:
function api_tests()
menu.close()
console.clear()
console.show()
test_log = logger("LUATEST.LOG")
-- note: each test routine must print a blank line at the end
-- strict_tests()
-- generic_tests()
printf("Module tests...\n")
-- test_io()
-- test_camera_gui()
-- test_menu()
-- test_camera_take_pics()
-- sleep(1)
-- test_multitasking()
-- test_keys()
-- test_lv()
test_lens_focus()
-- test_camera_exposure()
-- test_movie()
printf("Done!\n")
test_log:close()
key.wait()
console.hide()
end
Make sure you do a shutter half-press when the test asks for it.
Here's how a couple of lenses did on the 700D. First one is the 28-105mm and the second is the 50mm 1.8 STM lens.
===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2018-4-22 14:35:43
===============================================================================
Module tests...
Testing lens focus functionality...
Autofocus outside LiveView...
Focus distance: 1860
Autofocus in LiveView...
Please trigger autofocus (half-shutter / AF-ON / * ).
19...18...17...16...15...Autofocus triggered.
Autofocus completed.
Focus distance: 2590
Focusing backward...
Focus distance: 1860
Focus motor position: 0
Focusing forward with step size 3, wait=true...
...
Focus distance: 470
Focus motor position: 0
Focusing backward with step size 3, wait=true...
........
Focus distance: 655350
Focus motor position: 0
Focus range: 3 steps forward, 8 steps backward.
Motor steps: 0 forward, 0 backward, 0 lost.
Focusing forward with step size 3, wait=false...
.....................................
Focus distance: 470
Focus motor position: 0
Focusing backward with step size 3, wait=false...
..................................
Focus distance: 655350
Focus motor position: 0
Focus range: 37 steps forward, 34 steps backward.
Motor steps: 0 forward, 0 backward, 0 lost.
Focusing forward with step size 2, wait=true...
.....................................................
Focus distance: 470
Focus motor position: 0
Focusing backward with step size 2, wait=true...
...................................................
Focus distance: 655350
Focus motor position: 0
Focus range: 53 steps forward, 51 steps backward.
Motor steps: 0 forward, 0 backward, 0 lost.
Focusing forward with step size 2, wait=false...
...
Focus distance: 470
Focus motor position: 0
Focusing backward with step size 2, wait=false...
...
Focus distance: 655350
Focus motor position: 0
Focus range: 126 steps forward, 124 steps backward.
Motor steps: 0 forward, 0 backward, 0 lost.
Focusing forward with step size 1, wait=true...
...
Focus distance: 470
Focus motor position: 0
Focusing backward with step size 1, wait=true...
...
Focus distance: 655350
Focus motor position: 0
Focus range: 212 steps forward, 212 steps backward.
Motor steps: 0 forward, 0 backward, 0 lost.
Focusing forward with step size 1, wait=false...
...
Focus distance: 470
Focus motor position: 0
Focusing backward with step size 1, wait=false...
...
Focus distance: 655350
Focus motor position: 0
Focus range: 303 steps forward, 310 steps backward.
Motor steps: 0 forward, 0 backward, 0 lost.
Focus test completed.
Done!
===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2018-4-22 14:38:10
===============================================================================
Module tests...
Testing lens focus functionality...
Autofocus outside LiveView...
Focus distance: 3500
Autofocus in LiveView...
Please trigger autofocus (half-shutter / AF-ON / * ).
19...18...17...Autofocus triggered.
Autofocus completed.
Focus distance: 3500
Focusing backward...
Focus distance: 655350
Focus motor position: 0
Focusing forward with step size 3, wait=true...
.........................
Focus distance: 340
Focus motor position: 0
Focusing backward with step size 3, wait=true...
.........................
Focus distance: 655350
Focus motor position: 0
Focus range: 25 steps forward, 25 steps backward.
Motor steps: 0 forward, 0 backward, 0 lost.
Focusing forward with step size 3, wait=false...
...
Focus distance: 1100
Focus motor position: 0
Focusing backward with step size 3, wait=false...
...
Focus distance: 1100
Focus motor position: 0
Focus range: 162 steps forward, 163 steps backward.
Motor steps: 0 forward, 0 backward, 0 lost.
Focusing forward with step size 2, wait=true...
...
Focus distance: 1100
Focus motor position: 0
Focusing backward with step size 2, wait=true...
...
Focus distance: 1100
Focus motor position: 0
Focus range: 164 steps forward, 164 steps backward.
Motor steps: 0 forward, 0 backward, 0 lost.
Focusing forward with step size 2, wait=false...
...
Focus distance: 1100
Focus motor position: 0
Focusing backward with step size 2, wait=false...
...
Focus distance: 1100
Focus motor position: 0
Focus range: 419 steps forward, 421 steps backward.
Motor steps: 0 forward, 0 backward, 0 lost.
Focusing forward with step size 1, wait=true...
...
Focus distance: 1100
Focus motor position: 0
Focusing backward with step size 1, wait=true...
...
Focus distance: 1100
Focus motor position: 0
Focus range: 1055 steps forward, 1055 steps backward.
Motor steps: 0 forward, 0 backward, 0 lost.
Focusing forward with step size 1, wait=false...
...
Focus distance: 1100
Focus motor position: 0
Focusing backward with step size 1, wait=false...
...
Focus distance: 1100
Focus motor position: 0
Focus range: 1057 steps forward, 1058 steps backward.
Motor steps: 0 forward, 0 backward, 0 lost.
Focus test completed.
Done!
I get error everytime im trying to test "test_lens_focus()" function
ML/SCRIPTS/API_TEST.LUA:1175: assertion failed!
stack traceback:
[C]: in function 'assert'
ML/SCRIPTS/API_TEST.LUA:1175: in function 'test_lens_focus'
ML/SCRIPTS/API_TEST.LUA:1349: in function 'api_tests'
ML/SCRIPTS/API_TEST.LUA:1364: in main chunk
[API_TEST.LUA] script finished.
Get yourself a lens reporting focus distance.
(https://img3.picload.org/image/dorgaddw/vram3.png)
Focus dist, DOF Near and Far must contain valid entries.
i am using tamron 17-50 2.8 vc
(https://thumb.ibb.co/n5mHRx/Untitled.jpg) (https://ibb.co/n5mHRx)
Set cam to factory defaults. Don't forget Custom Functions (C.Fn) settings!
Remove battery after each test run.
Try different focus modes.
Report back.
All lenses should be able to complete the focus test or at least not crash the test. It looks like lua couldn't put the camera into LiveView. Try running the test in photo mode with and without LiveView. Also do a regression test--are you getting the same results with 1.1.1 as you are with 1.1.2?
[EDIT] Maybe worth mentioning we're using lua_fix experimental builds when running these tests. The lua tests in the nightly builds use a different API (application program interface).
Quote from: dfort on April 23, 2018, 04:37:07 PM
All lenses should be able to complete the focus test or at least not crash the test. It looks like lua couldn't put the camera into LiveView. Try running the test in photo mode with and without LiveView. Also do a regression test--are you getting the same results with 1.1.1 as you are with 1.1.2?
[EDIT] Maybe worth mentioning we're using lua_fix experimental builds when running these tests. The lua tests in the nightly builds use a different API (application program interface).
Already tested both in liveview and outside liveview still getting the same error
only running the test_lens_focus() function
@jai554 - Could you please post the "lens = table:" block from the log file using the Tamron lens you used to make this screenshot?
(https://farm1.staticflickr.com/971/26803660957_625b16bef1.jpg) (https://flic.kr/p/GQxLzt)
Are you using photo mode? Are you starting the test in LiveView or outside of LiveView? Have you tried running test_lv() by itself? The reason I'm asking these questions is because just before the assert error you're getting is this:
-- note: some lenses may be able to AF only in LiveView
-- so let's check each mode regardless of the other
The tests should be able to switch to the various modes but I have found that it is best to have the camera in photo mode with LiveView off and in manual mode before running the tests. The error might be a problem getting into and out of LiveView because the lens information seems to be fine on your screenshot.
Looks like we're stuck on the lua_fix branch lua API tests. The 60D can't get past the lens tests but I'm not sure if we're getting the same results with 1.1.1 and 1.1.2. Check out some of the testing that has been going on with the 650D and note how a possible stub issue was tracked down. We should be able to do something similar here to track down the issue with the focus test.
Start reading from here:
https://www.magiclantern.fm/forum/index.php?topic=7473.msg200606#msg200606
Quote from: dfort on April 24, 2018, 04:50:26 PM
@jai554 - Could you please post the "lens = table:" block from the log file using the Tamron lens you used to make this screenshot?
sorry for the late :D
here you go
lens = table:
name = "17-50mm"
focal_length = 18
focus_distance = 570
hyperfocal = 2167
dof_near = 462
dof_far = 748
af = true
af_mode = 0
focus = function: p
autofocus = function: p
@jai554 - looks good. Have you tried running just the lens focus test by itself? Review Reply #116 (https://www.magiclantern.fm/forum/index.php?topic=14739.msg200395#msg200395) for instructions. If that passes, run test_camera_exposure and test_movie so we can see if it passes those tests. Some cameras seem to have a hard time running all of the tests in one run yet they can pass each test when run individually.
Quote from: dfort on May 15, 2018, 05:36:27 AM
@jai554 - looks good. Have you tried running just the lens focus test by itself? Review Reply #116 (https://www.magiclantern.fm/forum/index.php?topic=14739.msg200395#msg200395) for instructions. If that passes, run test_camera_exposure and test_movie so we can see if it passes those tests. Some cameras seem to have a hard time running all of the tests in one run yet they can pass each test when run individually.
yes it passes all tests except test_lens_focus
The 17-50mm Tamron lens might be one of the lenses that isn't passing the focus test. Refer to the
lua test_lens_focus() (https://www.magiclantern.fm/forum/index.php?topic=22053.0) topic for some other lens/camera combinations that aren't passing the test.
Something you can do if you want to help figure out exactly where the test is failing is to add some printf statements to the lua script like saulbass did on the 650D for the movie test (https://www.magiclantern.fm/forum/index.php?topic=7473.msg200625#msg200625).
As far as the firmware update, it does look like all the issues that have turned up on 1.1.2 are also on 1.1.1 so (in my opinion) it should be ready to merge. Here is a list of the various firmware updates in progress (https://www.magiclantern.fm/forum/index.php?topic=19417.msg184578#msg184578).
Hi,
i have already installed the 1.0.3 Firmware. What should i do, to install ML?
Follow the steps outlined in the first post of this thread.
Hello Lantern Corps,
Trying to get ML setup on my 60Da (1.1.1) with a 64 GB SCT Card. Watched several videos (varying degrees of credibility) and read this thread plus other websites. Should be pretty easy so I must be doing something stupid.
My understanding: I need to use macboot since card size is > 32GB (something to do with filesystem...don't quite understand 64GB limitation).
1. Didn't format card.
2. Successfully installed macboot and prepared 64GB card with bootable flag.
3. Downloaded nightly (magiclantern-Nightly.2018Jul03.60D111) and copied ML files tree to card root (autoexec.bin, ML-SETUP.FIR, ML/*)
From videos it looks like putting card in camera and press garbage can should go to ML. Does not.
Is it as simple as the first post in the thread? I.e. Format card in camera, copy files to root, click "Firmware" in menu to upgrade? If I do that, do I need to worry about the bootable flag being set? Is there any special concern about 64GB cards?
Many thanks for your help.
Forget that outdated info.
Follow instructions in post 1 or go to top of page -> User Guide -> Install Guide
Worked like a charm. Many thanks for the help. Was just a little hesitant given the minor conflicts in instructions over the last few years.
Anyone here could tell me if there is any improvement since 2014 as far as raw capabilities of 60D? in terms of countineus shooting resolution and other features? i could not find any detail /change log regarding improvements.
Thanks
Hey all.
I am wondering if someone might point me to some information on how best to use gradual exposure?
Is it somewhat automatic? Does it step in both directions or only up/down? Can you get it to go both ways?
For example if you were to film 24hrs you would need to have the EV go up and down with the light conditions.
I have tried searching the forums and the web but found very little.
Thanks in advance,
Andrew.
Another question if I may,
Does anyone have experience recording RAW video with the 60D?
Is it possible to do so and for how long? The preference would be to do so via the HDMI port so as to extend the recording tine and the write speed however reading up gives me the impression this is not possible?
Perhaps a swath of large capacity high write speed SD cards?
Does anyone have some advice?
Is there anyway to enable lossless compression in 12 Bit raw video?
60D main processor is DIGIC 4 and therefore not able to use it. Reddeercity is working on porting this feature set to D4. See here (https://www.magiclantern.fm/forum/index.php?topic=19336.msg209477;topicseen#msg209477).
Don't hold your breath waiting to make it into 60D. Nobody around owning a 60D working on it.
If you are into RAW recording on Canon bodies you might want to take a look into 100D. Just under 200€ for a cam in mint condition. Yes, no swivel display and battery life sucks IMO. But memory interface good for about 40 MByte/s (without overclocking) ...
I know this is somewhat of a dead thread but I was hoping I could get some assistance. My 60D with 1.1.1 nightly build from July 3rd keeps booting off my video recording. It'll record for no more than 4 seconds before it says "movie recording has been stopped automatically."
The kicker is, I can record longer footage using the MLV recording. I've been using this same class 10 64gb card for a few years and have had numerous videos exceeding 10 minutes in length(not MLV). I've cleared all the buffers, ram, rom, done a couple of low level reformats, disabled modules, disabled anything that might get in the way of recording but it still tops out at 4 seconds. I would record in MLV regularly but 6 seconds in MLV is hardly more helpful than 4 seconds in h264.
Its a sudden issue. I recorded some timelapses the other day using the autoexposure module and wondered if maybe I just exhausted my SD card or something? I'm at my wits end and really wish I could just record a 60 second video without infuriating me beyond belief.
This camera has been used and abused over the years but its reliability has kept it in my camera bag, I even did a shutter replacement by myself a few years back. I'm worried it hit its limits.
Before going into analysis: May I suggest to get another card and retry? 60D's limit is about 25 MByte/s (without overclocking) and such cards are affordable. Get your pick from cameramemoryspeed.com -> Reviews -> SD-cards and Micro SD-cards or any other reliable source offering write rate benchmarks.
Quote from: Walter Schulz on January 09, 2019, 04:42:42 PM
Before going into analysis: May I suggest to get another card and retry? 60D's limit is about 25 MByte/s (without overclocking) and such cards are affordable. Get your pick from cameramemoryspeed.com -> Reviews -> SD-cards and Micro SD-cards or any other reliable source offering write rate benchmarks.
I tried another class 10 card that I have, exact same behavior; just under 4 seconds of footage. I tried MLV recording and got up to 7 seconds of footage(170 frames) before it skipped and stopped. It doesn't make any sense to me. Short of a factory reset/reinstall of ML, I'm not sure what to do next.
I thought I would include some details in case it says something I'm not seeing.
Free memory 322k + 1509k
- allocated ram 401kb, peak 712kb
- malloc 322kb, 138kb used
- allocatedmemory 1.5mb, 264kb used
- shoot_malloc 32mb, 0 used
- shoot space 502kb
- shoot contig 31mb, (sets to 0 then back to 31 every 15 seconds)
- shoot total 187mb, (same behavior as shoot contig)
- srm job total 6x31mb
- autoexec.bin 512kb of 1.5mb
image buffers 720x480, 1056x704
shutter count 173k = 157800+15135
internal temp 44c, 111F, 172 raw
battery level 100% (fails to recognize battery, problem started after rebuilding the camera)
Module tab -> bench.mo OK -> Restart (photo mode) -> Debug tab -> Benchmarks -> Card Benchmarks -> Quick R/W benchmark (1 min).
Open card's root directory and convert bench0.ppm to png or jpeg. Upload it to a file/pic like picload.org and link image here.
And retry H.264 recording with Global Draw OFF.
does anybody have the autoexe.bin file that allows you to clear all settings for a 60d that has the err 70 and only boots when you have the dial on "C"?
ASSERT: FALSE
at DevelopCombination.c:108, task RscMgr
lv:0 mode:0
RscMgr stack: 115e68 [115f90-114f90]
0xUNKNOWN @ ff07b8cc:115f88
0xUNKNOWN @ ff1dcb80:115f60
0xFF1DC5DC @ ff02c3fc:115f28
0xUNKNOWN @ ff1dc60c:115f18
0xUNKNOWN @ ff1dc694:115ef8
0xFF0CAE58 @ ff0c9858:115ec0
0xFF013EC0 @ ff0caf18:115ea0
0x1FE00378 @ 1fe006d8:115e68
Magic Lantern version : Nightly.2018Jul03.60D111
Mercurial changeset : 7a3b5fa3f4c6 (unified) tip
Built on 2018-07-02 22:19:47 UTC by jenkins@nightly.
Free Memory : 392K + 1920K
*****a1ex took care of me!*****
Does the 60d have the automatic recording restart feature with ML?
If it does, does the dual pixel AF work with this camera and ML as well?
Automatic restart works with 60D.
But there is no DPAF inside 60D! The only ML supported camera with DPAF is 70D.
Hi, recently bought a used version, I wanted to know if by chance there is a workaround to remote control it like the 70D does via the app? I know 60D don't have WiFi, only have RC6 and switches.
If your phone has an IR blaster, you can use an app which sends the correct signal via IR to the cam to trigger it remotely (emulating the RC6).
Here an example:
https://play.google.com/store/apps/details?id=com.haui.camerainfraredremote
I am using irplus
https://play.google.com/store/apps/details?id=net.binarymode.android.irplus
which is configurable. I control a TV, an EOS camera, an audio amplifier and Christmas lights with one app on my phone.
Disregard that, sorry
Thank you for theses infos
Quote from: ArcziPL on June 29, 2022, 08:02:33 PM
If your phone has an IR blaster, you can use an app which sends the correct signal via IR to the cam to trigger it remotely (emulating the RC6).
Here an example:
https://play.google.com/store/apps/details?id=com.haui.camerainfraredremote
I am using irplus
https://play.google.com/store/apps/details?id=net.binarymode.android.irplus
which is configurable. I control a TV, an EOS camera, an audio amplifier and Christmas lights with one app on my phone.
Wow its been a while since I've been on these forums, glad to see this project is still kicking around.
Just got my partner a 60D to mess around with, figured some of the features of ML would be of use to her. Trying to find the 1.1.1 firmware in 2023 has proven difficult, can I update her to 1.1.2 and will magic lantern install or does it absolutely NEED 1.1.1? It looks like there is some work being done on 1.1.2 but forgive me I am not a programmer, does this mean 1.1.2 support is coming soon(tm) or has there been roadblocks and I should continue searching for 1.1.1?
I've tried the eoscard program and it keeps stalling out trying to download firmware. Could be the program, could be my crappy internet. Should I keep trying with that or follow another path?
Thanks and I really appreciate the work you guys are doing.
ML checks the existing firmware version and will refuse to run on a non-matching version: you must use 1.1.1.
Links to Canon firmware 1.1.1 found in
Top of page -> Downloads -> Download Nightly Builds -> Main Builds -> 60D, 60Da -> Installation
also in "Useful Links".
Also in https://eoscard.pel.hu -> Scroll down.