Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Slasklita

#1
Quote from: StreetShotz on May 02, 2013, 02:04:11 AM
And were up and running... Now it time to learn how to work everything :) Thanks all!!!!
How did you get it to work? If i may ask :)
#2
Quote from: nanomad on April 16, 2013, 09:13:09 PM
JUST DON'T USE THAT AUTOEXEC OR FIR
It bypasses a critical safety check so it can potentially damage your camera. For real this time
And that FIR is no good, unless you have a screwed up bootflag on your camera
How does it affect the camera? How do i know if something broke?
#3
Yeah well it didnt work for me either :(
#4
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
#5
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.
#6
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?
#7
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
#8
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?
#9
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