Tragic Lantern for 6D

[gravitatemediagroup]

soooo....
1. download all files from bit bucket
2. put those files along with ML 2.3 in a folder (does the folder require a specific name?)
3. install just like a normal firmware update?

also, I'm guessing the .ini files DON'T go on the SD card
or do they need to stay located where the .bin is?

[gravitatemediagroup]

I attempted to load it and I get  "memory card containing firmware is required to update"

[1%]

Make sure you download the .fir from this thread after you are updated to 1.1.2, run that to set the boot flag.

ml folder from 2.3 goes in root. the .ini files go in the ML folder (yes you need them).

Its not like 5d3 where you have to run it every time.

[gravitatemediagroup]

alright, about to make the 2nd attempt, i'll let you know shortly how it goes

[gravitatemediagroup]

is EXT HDR 6D and Flashy Peaking supposed to stay in the root folder as well?

[gravitatemediagroup]

alright SUCESS lol

now what hahahaha

[gravitatemediagroup]

can't get the ML menu to pop up

[1%]

make sure of 2 things.

1. card is bootable
2. you renamed the bin to autoexec.bin

you have 2 different versions there

oh and here is a frowny browny:

LVx1_GetVramParam(W:1620 H:1080)[ff0c0fd4]

this means hdmi output is only 1620x1080. taking a lv screen shot and cropping it confirms its not CRAW buffer sized.

[gravitatemediagroup]

so I should try to install again for the 2nd time nameing autoexc with .bin

[gravitatemediagroup]

and should I use the autoexec that comes with ML or the one located on bitbucket?
or use both and add .bin to the bitbucket version?

[1%]

lol, the one that come with it is from 2.3 6D didn't even exist. 

you only have to do the firmware thing once. After that you just copy over the autoexec.bin

structure is:
/ - FOLDER
autoexec.bin
ML -FOLDER
- ini files/help/config files
DCIM -FOLDER
- pics go here

the bins are renamed because I can't upload 50 autoexec.bin files and a history of previous version is good when you need something that worked before or features that changed, etc

[gravitatemediagroup]

just curious, but why is there a autoexec on bitbucket?  they are different sizes from each other

[gravitatemediagroup]

alright, I've done it what I believe to be "the right way"
now I can't figure out how to load the ML menu

[1%]

well the first one can be named autoexec.bin so that is the first bin i compiled.

since we add/remove things the binary size changes (up to 500kb). autoexec.bin *is* ml the rest are just support files. the fir just enables the boot flag and nothing else. The reason 2.3 bin is so big is because it all of the camera autoexec.bin put together into one. since this is the 6d port its only the 6D bin.

ml menu should load on erase

[DTSET123]

I am having some exact problem. I get to the page where it says success and when I restart nothing happens. erase does not respond

[1%]

Are your cards set bootable with eoscard?

the fir set the boot flag in the camera (it will load bin from bootable cards)
eoscard sets boot + develop flag for the individual cards

when you reboot it will ONLY start if you already made the card bootable and copied all the files.

[gravitatemediagroup]

so disable bootflag at the "success" screen?

sorry for being a noob
i'm just not trying to destroy my $2000 camera
2 weeks ago I killed my $1000 nvidia geforce 690 lol

[gravitatemediagroup]

what is the process to make a card bootable?

[DTSET123]

yes, it is. I just checked. Im still confused to as what to rename to what. I put 6D-112.fir from this thread. I copied it to the rood of my card. I extracted ML 2.3 and replaced the old autoexec.bin with the one from bitbucket. Then I put all the fines (except for autoexec.bin) to ML folder. Then I updated and it says success: "BBOTDISK flag enabled AUTOEXEC.BIN found. Magic lantern Installed you may restart". But when I restart nothing happens, and erase does not work

[DTSET123]

You have to download EOScard. I got it from the original ML website

[DTSET123]

Ops, I may have lied. I just double checked and DISBOOT.BIN is not comming up in EOScard. What do I do?

[gravitatemediagroup]

ive now made it bootable, still no luck

[1%]

autoexec.bin is named exactly that, nothing after it? and its in the root folder/

http://pel.hu/eoscard/

set eos-develop and bootable

[gravitatemediagroup]

bad new folks, camera won't turn on now

even after i take battery out

[DTSET123]

o no...