Author Topic: Canon 650D [OLD] (Read 1267701 times)

nanomad · « **Reply #900 on:** April 16, 2013, 12:17:40 PM »

Yep, not the safe ones I handed out though (requires props)

Lucas_W · « **Reply #901 on:** April 16, 2013, 12:35:47 PM »

I tried to compile the latest version of autoexec.bin and I re-did the EOScard but when I booted up my LED flashes and camera doesn't boot, it's fine without the card though. Is it because I'm using an outdated nightly of Magiclantern or did I do something wrong.

nanomad · « **Reply #902 on:** April 16, 2013, 12:38:14 PM »

Uhmm..interesting. Did the old alpha work for you? The only thing I can think of is the new CRC check I added to prevent booting with a wrong fw version. (I'll sit on IRC if you want to do a couple of tests)

Lucas_W · « **Reply #903 on:** April 16, 2013, 12:39:56 PM »

~~I never got to try the old alpha. The version I was using before was a autoexec.bin I compiled myself on March 13th with the .fir from the 650D downloads section.~~

nanomad and I have been testing things on IRC and he thinks there might be a bug with his signature checking or that I was just using an old firmware or similar.

On the plus-side, here's an image of one of Magic Lantern's "features" [It's a joke btw, my camera is perfectly safe!]

https://imageshack.us/scaled/large/820/20130416215724.jpg

faern · « **Reply #904 on:** April 16, 2013, 02:28:27 PM »

Taking timelapses with cameras with moving mirrors is dangerous since they get worn out after a limited number of shots. Of course it depend on the interval and everything else. Taking 1 pic each 10 sec will produce >8000 images per day.

I know some people who did this and broke the camera completely after a few days.

Watch out guys!

Lucas_W · « **Reply #905 on:** April 16, 2013, 02:50:19 PM »

Plants don't really grow that fast (I hope?), so I don't think he'd be taking a photo every 10 seconds. Maybe he could take 1 an hour and have 1 day = 1 second which would produce 14 seconds of time lapse footage at 24 fps.

Phillips321 · « **Reply #906 on:** April 16, 2013, 02:52:59 PM »

Lucas, that was the plan 2 weeks lasting 14 seconds.

24 shots per day * 14 days = 336 photos, surely not enought to wear the shutter out!

faern · « **Reply #907 on:** April 16, 2013, 03:12:14 PM »

Of course not. I just wanted to warn for potential mistakes.

Well available builds would be awesome. Please carry on.

Slasklita · « **Reply #908 on:** April 16, 2013, 04:05:37 PM »

Hey guys! Just want to hop in and give a big thanks to everyone working on this release.

Im also wondering how to compile ML? Not that i cant wait for the official release. No stress bro!
But i love living on the edge, experimenting with shit

FYI; I have no experience in programming

loplo · « **Reply #909 on:** April 16, 2013, 04:15:29 PM »

Then stand back and relax.
Compiling and installing it's not resuming to "next -> next -> finish", so better be safe and wait.

Slasklita · « **Reply #910 on:** April 16, 2013, 04:36:39 PM »

Quote from: loplo on April 16, 2013, 04:15:29 PM

Then stand back and relax.
Compiling and installing it's not resuming to "next -> next -> finish", so better be safe and wait.

Yeah.. Thats what i thought.
What could go wrong when compiling it yourself?

Lucas_W · « **Reply #911 on:** April 16, 2013, 04:50:50 PM »

Funnily enough, compiling Magic Lantern sort of is "next -> next -> finish" except Command Line style instead of GUI.

If you do want to compile Magic Lantern I 110% recommend getting the Virtual Machine made for it.

http://nanomad.magiclantern.fm/Development%20Box/VirtualBox/MagicLantern.zip

You'll need virtualbox for it. From then on you just need to make a make.user file and do 'make 650D' in the terminal and get your autoexec.bin off your VM.

loplo · « **Reply #912 on:** April 16, 2013, 04:57:26 PM »

Lucas_W, "except".

Lucas_W · « **Reply #913 on:** April 16, 2013, 05:00:34 PM »

Heh. Yep, it's as simple as pressing a button..... and then doing this, and then doing that, and then writing this here and that there.

1ricca · « **Reply #914 on:** April 16, 2013, 05:01:21 PM »

Quote from: Lucas_W on April 16, 2013, 04:50:50 PM

Funnily enough, compiling Magic Lantern sort of is "next -> next -> finish" except Command Line style instead of GUI.

If you do want to compile Magic Lantern I 110% recommend getting the Virtual Machine made for it.

http://nanomad.magiclantern.fm/Development%20Box/VirtualBox/MagicLantern.zip

You'll need virtualbox for it. From then on you just need to make a make.user file and do 'make 650D' in the terminal and get your autoexec.bin off your VM.

It's always much simpler when you've done it before. I find myself making similar justifications to people about other programmer stuff where, to me, it seems like such a quick and easy task. It's like reformatting a PC. So easy to me, but there really is a ton of particulars and steps that a smart someone who's never done it before could easily screw it up. Being so busy, I know I wouldn't have any problems doing it myself. Just no time what so ever for me right now. Yet, I would absolutely love to test some more out and report on bugs. That I do have time for

Therefor... anyone that would be generous enough to compile a 650d build and PM me with it would be a champion and ultimately be helping out the community just a little more, not just for me

blade · « **Reply #915 on:** April 16, 2013, 05:16:58 PM »

If I could compile a version for you ( and I can't) I would not give it to you. Any bugs you run in to you will report back here. And as it would be a costum build the developers would have a hard time figuring out what may have coused the bug.

Wait for the build from nanomad, it will not have every option activated, but it will be testable. So fare the code is very stable ( far more stable then some comersial final software I have to work with) and that takes time.

Aldo I have a pre alpha running, I to look forward to a alpha version. And when it is there I will test and report back.

Slasklita · « **Reply #916 on:** April 16, 2013, 05:35:52 PM »

Quote from: Lucas_W on April 16, 2013, 04:50:50 PM

Funnily enough, compiling Magic Lantern sort of is "next -> next -> finish" except Command Line style instead of GUI.

If you do want to compile Magic Lantern I 110% recommend getting the Virtual Machine made for it.

http://nanomad.magiclantern.fm/Development%20Box/VirtualBox/MagicLantern.zip

You'll need virtualbox for it. From then on you just need to make a make.user file and do 'make 650D' in the terminal and get your autoexec.bin off your VM.

Oh, really?
This is the correct download for the ML build, right? https://bitbucket.org/hudson/magic-lantern/overview

Lucas_W · « **Reply #917 on:** April 16, 2013, 05:40:57 PM »

That's the source-code that you compile from, yes.

I'm not sure if I should do this, but I've attached my autoexec.bin and the .fir file for the 650D from the ftp space of the site.

I take no responsibility for what happens if you brick your camera, and I have no idea how to help in such event. I'm not even 100% sure this works.

You'll need to place both into the root of your card and then download the magic-lantern nightly and place the ML folder in the root. Then you'll need to download EOScard and check all threes boxes and click 'save'. Pop the card into your camera and then run the firmware updater and that should work, I have no idea as it's a different process to what I originally did.

Link removed by Nanomad: The bootfix does not enable the bootflag, it fixes it...and the FIR bypasses a crucial safety check
As always, the safest and officially recommended method is to wait until the official Alpha release.

Slasklita · « **Reply #918 on:** April 16, 2013, 06:05:16 PM »

Quote from: Lucas_W on April 16, 2013, 05:40:57 PM

That's the source-code that you compile from, yes.

I'm not sure if I should do this, but I've attached my autoexec.bin and the .fir file for the 650D from the ftp space of the site.

I take no responsibility for what happens if you brick your camera, and I have no idea how to help in such event. I'm not even 100% sure this works.

You'll need to place both into the root of your card and then download the magic-lantern nightly and place the ML folder in the root. Then you'll need to download EOScard and check all threes boxes and click 'save'. Pop the card into your camera and then run the firmware updater and that should work, I have no idea as it's a different process to what I originally did.

*********** - autoexec.bin

*********** - 650D-bootifx.fir

As always, the safest and officially recommended method is to wait until the official Alpha release.

Ok now Im almost shitting my pants

What revision is this?

Lucas_W · « **Reply #919 on:** April 16, 2013, 06:07:14 PM »

The latest as of writing, but with a slight modification to bypass the sig check as that wasn't working right.

EDIT: Funnily enough, Bitbucket is also down as of writing...

Slasklita · « **Reply #920 on:** April 16, 2013, 06:19:24 PM »

Quote from: Lucas_W on April 16, 2013, 06:07:14 PM

The latest as of writing.

EDIT: Funnily enough, Bitbucket is also down as of writing...

It didn't work. Just said that i needed "All the ML files on the card" or something like that when i tried the Firmware update tool inside the camera.

Lucas_W · « **Reply #921 on:** April 16, 2013, 06:23:26 PM »

Ah, okay. Try this instead:

Wipe the root of your card (Except the DCIM folder if you have anything stored there).

Then extract removed onto it.
Edit by nanomad: Nope, the bootfix won't work..it's a fix, not a proper bootflag enabler
Do the firmware update.

Replace the ML folder and autoexec.bin with the nightly and file I linked to, respectively. Do the EOScard step.

and it should just boot up into ML [Press trashcan on the normal operation display to bring up the ML menu].

Slasklita · « **Reply #922 on:** April 16, 2013, 06:30:22 PM »

Quote from: Lucas_W on April 16, 2013, 06:23:26 PM

Ah, okay. Try this instead:

Wipe the root of your card (Except the DCIM folder if you have anything stored there).

Then extract http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Feb02.650D.BOOTFIX.zip onto it.

Do the firmware update.

Replace the ML folder and autoexec.bin with the nightly and file I linked to, respectively. Do the EOScard step.

and it should just boot up into ML [Press trashcan on the normal operation display to bring up the ML menu].

That last part was a litte fuzzy. I want to get this 100% correct.
After i do the firmware update with the ML folder and 650D-bootfix.fir, i replace them both with the two files you linked earlier and the bitbucket folder?

EDIT: I dont have a autoexec.bin after i did the firmware update on the memory card

Lucas_W · « **Reply #923 on:** April 16, 2013, 06:35:09 PM »

after you do the firmware update:

Download the nightly: http://nanomad.magiclantern.fm/nightly/ (The .zip)

Copy the 'ML' folder in that nightly package into your card (And overwrite when it says if you want to)

Then download the autoexec.bin I originally posted in my first post (The Google drive thing). Put that onto the root of the card and overwrite the old one.

Then run EOScard and check all three boxes and click 'save' (I press it a couple of times because someone suggested that 10's of pages ago and because OCD). Then put the card into the camera and turn it on (You probably shouldn't have to do another firmware update).

Shadeena · « **Reply #924 on:** April 16, 2013, 06:47:45 PM »

What response is one meant to get after the firmware upgrade? I'm following the steps and ML isn't loading (camera is fine tho). When I do the firmware upgrade step I get 'EnableMainFirm

' on the camera's LCD. That's the only feedback the process generated.

Thanks for taking the time Lucas_W and big thank you to the ML team for their work.

News:

Author Topic: Canon 650D [OLD] (Read 1267701 times)