ML has been ported to 5D and 40D but there seems to be lack of activity for XSi, which I believed Canon should have sold quite a lot. Yep, you are right, I have one. But I am looking at this porting thing not as an ML user but as an ML developer. For the past couple of weeks I have roamed this website and CHDK in an effort to understand what this "hacking" business is all about and to size up the development work. Well, it is big, at least to me. As someone who doesn't do video, I am wondering if it is worth the effort for me to jump in. From the information I came across it seems that firmware dump, v1.0.9 has been available (http://chdk.setepontos.com/index.php?topic=3402.0 (http://chdk.setepontos.com/index.php?topic=3402.0)) but a later thread asking for help to dump the same firmware (http://chdk.setepontos.com/index.php?topic=4973.0 (http://chdk.setepontos.com/index.php?topic=4973.0)) while using the same file I/O function pointers. Intrigued by this and as an IDA learning exercise (new tool to me), I set out to find what is going on. Well, I found the correct pointer values for those file I/O functions in Canon's flasher code and they are the same for both v1.0.9 and v1.1.0. Hmm, I wonder how one could get the firmware from apparently wrong function pointers. No, I have not dumped anything yet (need to set up the build environment in Ubuntu first, not to mention the build scripts) but I am sure mine are correct because I have cross-checked with those known working pointers in 40D firmware dump code in this thread (http://chdk.setepontos.com/index.php?topic=1651.45 (http://chdk.setepontos.com/index.php?topic=1651.45) to make sure they executes the same flasher file I/O code and they do. As a matter of fact, XS (1000D) has the exact same flasher file I/O code. They are just in different places (pointer values). I have not decided whether to continue further and certainly will not in the next two/three months but if anyone is interested in porting, I have no problem published the correct pointer values. Just want to get this porting thing move forward, albeit tortoise-wise. :)
- Rick
I got two extra weeks before my planned two month's away from home to do some more exploration. The file I/O pointer values that I found in the flasher code are correct. I have used them to dump Canon's firmware v1.1.0 successfully (from 0xFF810000 to 0xFFFFFFFF). It is not as straight as I thought. There were some more details I had to know about to actually dump the firmware without the risk of killing my XSi.
so you were able to dump the rom content?
i recommend to dump starting from 0xF8000000 btw
That (rom dump) is affirmative. I started by dumping 0xFF800000 - 0xFFFFFFFF but then discovered that IDA isn't happy about 0xFFFFFFFF being used (used by IDA?) and that 0xFF800000 - 0xFF8100000 just contains 0xFF's. I ended up just dumping 0xFF810000 - 0xFFFFFFFC so that I don't have to change file size when loading it into IDA. I am too lazy even though one only has to do it once - the first time loading.
0xF8000000 - 0xFFFFFFFF is a huge chunk (128MB). Can IDA handle that? Or would it be more advantageous to dump it in separate smaller chunks. I know 0xF8000000 - 0xF800000F is used as boot_flags and I guess it is probably in non-volatile memory. How big it may be? Also what other regions that presents interesting stuff for porting. I have taken a snapshot of the source code and am able to compile it. But I have not looked into the code yet.
By the way I think the next thing to do is to find the function pointers in the firmware to enable/disable boot-capability. I have followed the lead in a posting by Coutts (http://www.magiclantern.fm/forum/index.php?topic=1452.0 (http://www.magiclantern.fm/forum/index.php?topic=1452.0)) and found something close to the code (for 5D) in the posting but not quite the same. In 1000D (v1.0.5) I also found the same (XSi) code (in different places but very close by). Both of them are above 0xFFFF0000. I believe I have found them but until I learn ARM enough to be able to follow the code, I am not 100% sure.
After this exercise I have a better grasp of this porting business. It is not very challenged per se if one has the right knowledge (ARM assembly language for me) but requires a ton of labor to find where those equivalent pointers are in XSi, for starter. There should be more things I don't know yet.
Quote from: g3gg0 on March 03, 2013, 11:56:37 AM
ROM0: 0xF0000000 - 0xF7FFFFFF (when camera has a ROM0, then its 8 or 16M, so its 0xF0000000-0xF0FFFFFF)
ROM1: 0xF8000000 - 0xFFFFFFFF (most cameras have 16M, so its 0xF8000000-0xF8FFFFFF)
use these ranges, they are the the real base address and repeat over and over until 0xFFFFFFFF.
the processor uses the image at various addresses.
on boot, 0xFFFF0000 is executed, which is at 0xF7FF0000. later it may jump to 0xFF810000 which really is 0xFF010000 etc.
but when dumping, you best use the ranges i quoted above.
relocating in memory can be done later in IDA without any problem
for IDA: just use addresses until 0xFFFFFFFC
Thanks for the information about ROM0 and ROM1. I read about them but have not put much thought into them yet. A couple of things to clarify though.
About the memory ranges to dump. You mean to dump just the lower 16M (0xF0000000-0xF0FFFFFF for ROM0 and 0xF8000000-0xF8FFFFFF). Right?
About the address mapping. I got lost here. How can 0xFFFF0000 (ROM1 range) be mapped from 0xF7FF0000 (ROM0 range)?
haha ok you really understood what i wrote :)
yeah, i had a typo.
of course 0xFFFF0000 does map to 0xF8FF0000
Or 0xF8FF0000 maps to 0xFFFF0000. :)
Anyway I went ahead to dump 0xF0000000-0xF0FFFFFF (16M) and 0xF8000000-0xF8FFFFFF (16M)ranges. The data from the 1st range (ROM0) are all 0's. I guess there isn't ROM0 in XSi (a blank ROM should be all 0xFF's). Data in the 2nd range seems to be two copies of the same code/data with an address offset of 8M. I got the impression when searching for a couple of specific patterns that matched once in my previous dump (0xFF810000-0xFFFFFFFF) and got two matches now. That probably means the size of ROM1 is 8M for XSi. Hmm, interesting.
QuoteIDA isn't happy about 0xFFFFFFFF
You can also cut a little bit off the end with a hex editor.. Its usually garbage like F's or 0s at the end.
I'm also wondering about 400D.. would be nice to have dual ISO on that.
By the way, the first 2K bytes (0xF8000000 and 0xF8800000 too) start with 8 0x00's and then all 0xFF's. So 0xF8000000, 0xF8000004, 0xF8000008 and 0xF800000C have value of 0, 0, -1 and -1. Seems to make sense.
yep, the first sector contains startup flags
If you can write to it, it must be some kind of non-volatile memory to keep the flags across boot/power loss.
its a flash chip. commands to erase/write are simple and standardized.
Ah, good old flash chip. Must be serial type - pin count and size matter. I had dealt with them (both serial and parallel) before. I plan to convert my XSi into IR someday and will look for it when I open it up. Back to the porting thing, which model to pick as the base for XSi in your opinion?
its a parallel one, as it is mapped into memory space
Quote from: g3gg0 on September 13, 2013, 10:00:50 PM
its a parallel one, as it is mapped into memory space
You are so right.
I poked around the ML source code trying to find some details about the boot_flag thing. And I found the bootDisk flag is @0xF8000004, not what I original thought @0xF8000000! Compare these sections of firmware code, I think I found the equivalent 500D enable/diable_bookDisk code in XSi.
500D Firmware v1.1.1?:
ROM:FF066748 ; =============== S U B R O U T I N E =======================================
ROM:FF066748
ROM:FF066748
ROM:FF066748 sub_FF066748 ; CODE XREF: sub_FF013210+154p
ROM:FF066748 STMFD SP!, {R4,LR}
ROM:FF06674C ADR R2, unk_FF066718
ROM:FF066750 MOV R1, #0
ROM:FF066754 ADR R0, aEnablefirmware ; "EnableFirmware"
ROM:FF066758 BL sub_FF1A5B58
ROM:FF06675C ADR R2, sub_FF066724
ROM:FF066760 MOV R1, #0
ROM:FF066764 ADR R0, aDisablefirmwar ; "DisableFirmware"
ROM:FF066768 BL sub_FF1A5B58
ROM:FF06676C ADR R2, sub_FF066700
ROM:FF066770 MOV R1, #0
ROM:FF066774 ADR R0, aEnablebootdisk ; "EnableBootDisk"
ROM:FF066778 BL sub_FF1A5B58
ROM:FF06677C ADR R2, sub_FF06670C
ROM:FF066780 MOV R1, #0
ROM:FF066784 ADR R0, aDisablebootdis ; "DisableBootDisk"
ROM:FF066788 BL sub_FF1A5B58
ROM:FF06678C ADR R2, sub_FF066730
ROM:FF066790 MOV R1, #0
ROM:FF066794 ADR R0, aEnablemainfirm ; "EnableMainFirm"
ROM:FF066798 BL sub_FF1A5B58
ROM:FF06679C LDMFD SP!, {R4,LR}
ROM:FF0667A0 ADR R2, sub_FF06673C
ROM:FF0667A4 MOV R1, #0
ROM:FF0667A8 ADR R0, aDisablemainfir ; "DisableMainFirm"
ROM:FF0667AC B sub_FF1A5B58
ROM:FF0667AC ; End of function sub_FF066748
ROM:FF0667AC
ROM:FF0667AC ;
ROM:FF0667B0 dword_FF0667B0 DCD 0xF8000004 ; DATA XREF: sub_FF066700r
ROM:FF0667B0 ; sub_FF06670Cr
ROM:FF0667B4 dword_FF0667B4 DCD 0xF800000C ; DATA XREF: sub_FF066724r
ROM:FF0667B8 aEnablefirmware DCB "EnableFirmware",0 ; DATA XREF: sub_FF066748+Co
ROM:FF0667C7 DCB 0
ROM:FF0667C8 aDisablefirmwar DCB "DisableFirmware",0 ; DATA XREF: sub_FF066748+1Co
ROM:FF0667D8 aEnablebootdisk DCB "EnableBootDisk",0 ; DATA XREF: sub_FF066748+2Co
ROM:FF0667E7 DCB 0
ROM:FF0667E8 aDisablebootdis DCB "DisableBootDisk",0 ; DATA XREF: sub_FF066748+3Co
ROM:FF0667F8 aEnablemainfirm DCB "EnableMainFirm",0 ; DATA XREF: sub_FF066748+4Co
ROM:FF066807 DCB 0
ROM:FF066808 aDisablemainfir DCB "DisableMainFirm",0 ; DATA XREF: sub_FF066748+60o
===== bootdisk_enable =====
ROM:FF066700 ; =============== S U B R O U T I N E ================
ROM:FF066700
ROM:FF066700
ROM:FF066700 sub_FF066700 ; DATA XREF: sub_FF066748+24o
ROM:FF066700 LDR R0, =0xF8000004
ROM:FF066704 MOV R1, 0xFFFFFFFF
ROM:FF066708 B sub_FF06664C
ROM:FF066708 ; End of function sub_FF066700
===== bootdisk_disable =====
ROM:FF06670C ; =============== S U B R O U T I N E ================
ROM:FF06670C
ROM:FF06670C
ROM:FF06670C sub_FF06670C ; DATA XREF: sub_FF066748+34o
ROM:FF06670C LDR R0, =0xF8000004
ROM:FF066710 MOV R1, #0
ROM:FF066714 B sub_FF06664C
ROM:FF066714 ; End of function sub_FF06670CXSi Firmware v1.1.0
ROM:FFD184A0 ; =============== S U B R O U T I N E =======================================
ROM:FFD184A0
ROM:FFD184A0
ROM:FFD184A0 sub_FFD184A0 ; CODE XREF: sub_FF811340+164p
ROM:FFD184A0
ROM:FFD184A0 var_4 = -4
ROM:FFD184A0
ROM:FFD184A0 LDR R0, =aEnablefirmware ; "EnableFirmware"
ROM:FFD184A4 MOV R1, #0
ROM:FFD184A8 LDR R2, =sub_FFD18158
ROM:FFD184AC STR LR, [SP,#var_4]!
ROM:FFD184B0 BL sub_FFD0A128
ROM:FFD184B4 LDR R0, =aDisablefirmwar ; "DisableFirmware"
ROM:FFD184B8 MOV R1, #0
ROM:FFD184BC LDR R2, =sub_FFD1822C
ROM:FFD184C0 BL sub_FFD0A128
ROM:FFD184C4 LDR R0, =aEnablebootdisk ; "EnableBootDisk"
ROM:FFD184C8 MOV R1, #0
ROM:FFD184CC LDR R2, =unk_FFD18538
ROM:FFD184D0 BL sub_FFD0A128
ROM:FFD184D4 LDR R0, =aDisablebootdis ; "DisableBootDisk"
ROM:FFD184D8 MOV R1, #0
ROM:FFD184DC LDR R2, =unk_FFD18550
ROM:FFD184E0 BL sub_FFD0A128
ROM:FFD184E4 LDR R0, =aEnablemainfirm ; "EnableMainFirm"
ROM:FFD184E8 MOV R1, #0
ROM:FFD184EC LDR R2, =sub_FFD18300
ROM:FFD184F0 BL sub_FFD0A128
ROM:FFD184F4 LDR R0, =aDisablemainfir ; "DisableMainFirm"
ROM:FFD184F8 MOV R1, #0
ROM:FFD184FC LDR R2, =sub_FFD183D0
ROM:FFD18500 LDR LR, [SP+4+var_4],#4
ROM:FFD18504 B sub_FFD0A128
ROM:FFD18504 ; End of function sub_FFD184A0
ROM:FFD18504
ROM:FFD18504 ; ---------------------------------------------------------------------------
ROM:FFD18508 off_FFD18508 DCD aEnablefirmware ; DATA XREF: sub_FFD184A0r
ROM:FFD18508 ; "EnableFirmware"
ROM:FFD1850C off_FFD1850C DCD sub_FFD18158 ; DATA XREF: sub_FFD184A0+8r
ROM:FFD18510 off_FFD18510 DCD aDisablefirmwar ; DATA XREF: sub_FFD184A0+14r
ROM:FFD18510 ; "DisableFirmware"
ROM:FFD18514 off_FFD18514 DCD sub_FFD1822C ; DATA XREF: sub_FFD184A0+1Cr
ROM:FFD18518 off_FFD18518 DCD aEnablebootdisk ; DATA XREF: sub_FFD184A0+24r
ROM:FFD18518 ; "EnableBootDisk"
ROM:FFD1851C off_FFD1851C DCD unk_FFD18538 ; DATA XREF: sub_FFD184A0+2Cr
ROM:FFD18520 off_FFD18520 DCD aDisablebootdis ; DATA XREF: sub_FFD184A0+34r
ROM:FFD18520 ; "DisableBootDisk"
ROM:FFD18524 off_FFD18524 DCD unk_FFD18550 ; DATA XREF: sub_FFD184A0+3Cr
ROM:FFD18528 off_FFD18528 DCD aEnablemainfirm ; DATA XREF: sub_FFD184A0+44r
ROM:FFD18528 ; "EnableMainFirm"
ROM:FFD1852C off_FFD1852C DCD sub_FFD18300 ; DATA XREF: sub_FFD184A0+4Cr
ROM:FFD18530 off_FFD18530 DCD aDisablemainfir ; DATA XREF: sub_FFD184A0+54r
ROM:FFD18530 ; "DisableMainFirm"
ROM:FFD18534 off_FFD18534 DCD sub_FFD183D0 ; DATA XREF: sub_FFD184A0+5Cr
ROM:FFD18538 unk_FFD18538 DCB 0x4F ; O ; DATA XREF: sub_FFD184A0+2Co
ROM:FFD18538 ; ROM:off_FFD1851Co
ROM:FFD18538 ;
---------------------------- bootdisk_enable? ---------------
ROM:FFD18538
ROM:FFD18538 loc_FFD18538 ; DATA XREF: sub_FFD184A0+2Co
ROM:FFD18538 ; ROM:off_FFD1851Co
ROM:FFD18538 MOV R0, 0xF8000004
ROM:FFD18540 MOV R1, 0xFFFFFFFF
ROM:FFD18544 STR LR, [SP,#-4]!
ROM:FFD18548 LDR LR, [SP],#4
ROM:FFD1854C B loc_FFD18078
ROM:FFD18550 ;
---------------------------- bootdisk_disable? ---------------
ROM:FFD18550
ROM:FFD18550 loc_FFD18550 ; DATA XREF: sub_FFD184A0+3Co
ROM:FFD18550 ; ROM:off_FFD18524o
ROM:FFD18550 MOV R0, 0xF8000004
ROM:FFD18558 MOV R1, #0
ROM:FFD1855C STR LR, [SP,#-4]!
ROM:FFD18560 LDR LR, [SP],#4
ROM:FFD18564 B loc_FFD18078This similarity makes me think if 500D is a good candidate of reference for XSi porting even though these two models have different OS. Anyway, now is the time for ARM assembly language and architecture, and perhaps VxWorks. Until then, I don't think I can make any meaningful progress.
Hi all,
Any news on this topic?
I'm a 450d user (I use it mainly for astrophotography stuff) and ML would be a nice addon, I really wish to see it one day :) . I haven't moved to a newer canon model because this 450d is heavily modified (IR filter removed, peltier cooling), so I would like to stick with that camera at least for a while.
I'm afraid I cannot help with the code because I don't know the internals of Canon firmware, and I don't have experience hacking the ML code, but I can offer myself to try to test any code you generate.
I think it would be wise not to wait for a port but to use some advanced remote control device.
Some progress with converting 40D port to 450D:
(http://thumbnails116.imagebam.com/50942/4eda84509417915.jpg) (http://www.imagebam.com/image/4eda84509417915)
Quote from: Ant123 on October 14, 2016, 03:39:52 PM
Some progress with converting 40D port to 450D
Oh my, it isn't photoshopped? If not: good to see some people are not going along with planned obsolescence and try to make use of the good ol' gear!
Having said that, I personally wouldn't go below the long-running 18mp sensor for general photography nowadays, there are so many cams around with it and ML support so they should be more than affordable... I just bought a used 7d1. That's b/c I had a 450d-class cam (Nikon 3100) for some weeks on loan and wouldn't want to touch that usability and sensor iq again even with a 10-foot pole.
Quote from: Ant123 on October 14, 2016, 03:39:52 PM
Some progress with converting 40D port to 450D:
(http://thumbnails116.imagebam.com/50942/4eda84509417915.jpg) (http://www.imagebam.com/image/4eda84509417915)
Can you post a link to this test build? :)
It's not finished yet. There is no normal installer. Shooting functions not implemented. Only intervalometer works at the moment...
Quote from: Ant123 on October 18, 2016, 09:42:47 PM
It's not finished yet. There is no normal installer. Shooting functions not implemented. Only intervalometer works at the moment...
Can I help you somehow?
I compiled a modern version of ML with the changes made by rufustfirefly.
But I've got it working only when I used GCC 4.7.3
With GCC 4.8 or 4.9 I'm getting camera crash during font loading.
Is it necessarily to use GCC 4.8.3 ?
Garbage at the rightmost column was removed when I changed BMP_W_PLUS from 720 to 721 in bmp.h:
(http://thumbnails115.imagebam.com/51176/f1ffc3511751829.jpg) (http://www.imagebam.com/image/f1ffc3511751829)
Is this trick correct?
Source code: https://bitbucket.org/Ant123/magic-lantern/src (https://bitbucket.org/Ant123/magic-lantern/src)
Installer for 450D firmware 1.1.0. : https://bitbucket.org/Ant123/magic-lantern-40d/downloads/ML450D110.fir (https://bitbucket.org/Ant123/magic-lantern-40d/downloads/ML450D110.fir)
It works the same as 40D/5DC installer.
ML test build for 450D firmware 1.1.0. : https://bitbucket.org/Ant123/magic-lantern-40d/downloads/magiclantern-Nightly.2016Oct26.450D110.zip (https://bitbucket.org/Ant123/magic-lantern-40d/downloads/magiclantern-Nightly.2016Oct26.450D110.zip)
Only intervalometer can be useful at the moment...
Added the 450D and 40D changes to the vxworks branch (https://bitbucket.org/hudson/magic-lantern/branch/vxworks) in the main repo. Did some minor cleanups (compiler warnings), had some attempts at emulating it in QEMU, but didn't really check any deeper yet.
For reverse engineering, I've adapted the dm-spy-experiments (http://www.magiclantern.fm/forum/index.php?topic=2388.msg113154#msg113154) branch as vxworks-dm-spy (https://bitbucket.org/hudson/magic-lantern/branch/vxworks-dm-spy) (tested in qemu).
Hey Ant123, could you please update those download links as i would like to test this build.. They seem to be broken :( :(
was lucky enough to be given a 450d .. started doing google found this an updated 450d from 1.04 to 1.09 (arg when u can find it lol) then 1.10 (had to flash from eos util on pc) and gave your test files ago and it works! OK not much you can do but loads magic lantern menus !! .. I know this camera is so old now and be awesome to have more features but I guess like the most of magic lantern seems to be dead or lack of devs 😔
removed it from my sd card via format option and just stock canon again as lack of being able to do really anything with this so no point leaving it running.
(http://thumbnails117.imagebam.com/53699/ac9f24536988410.jpg) (http://www.imagebam.com/image/ac9f24536988410)
(http://thumbnails117.imagebam.com/53699/adee4e536988412.jpg) (http://www.imagebam.com/image/adee4e536988412)
I'm also behind porting this, as I'm also running the 450D/XSi and don't mind experimenting. Also can help by dumping and building if need be, although I don't know my way around too much code, I can at least be a guinea pig.
Tried using your files but camera only flashes LED when ML450D110.fir is the only .fir file on the card.
Also tried to put original 1.1.0 firmware on the card with your fir. I can select ML450D110.fir and confirm the update and get the error message.
I'm I missing something?
Thanks
Quote from: armedchanger on June 24, 2017, 08:31:51 PM
I'm I missing something?
Read the FAQ (http://wiki.magiclantern.fm/faq) first...
Quote from: Ant123 on June 24, 2017, 10:12:29 PM
Read the FAQ (http://wiki.magiclantern.fm/faq) first...
Couldn't get it to work but managed to get it to work with EOScard software.
I think that there is huge potential for porting ML to XSi/450d because a lot of people use it as a 2nd camera. The intervalometer works as you said.
This thread needs more exposure and more devs joining in.
I have tried it on my 450D and it doesn't seem to work. It is installed but I can't seem to be able to load the ML menu up, Also it messes up the live mode, it flashes strange text.
When I press bin buttom this is what show up, then it crash and have to remove the battery to restart. I pressed Set and nothing happened.
(http://thumb.ibb.co/j0sJ45/IMG_20170826_104255.jpg) (http://ibb.co/j0sJ45)
I do have 1.1.0 firmware installed. Is there a different region of 1.1.0 firmware?? My camera is UK Version.
Many Thanks
Mike
Managed to emulate the 450D GUI in QEMU (http://www.magiclantern.fm/forum/index.php?topic=2864.msg190254#msg190254), and also ran some tests on Ant's build:
(https://builds.magiclantern.fm/jenkins/job/QEMU-nightly-tests/208/artifact/qemu/magiclantern-Nightly.2016Oct26.450D110/2-overlay2.png) (https://builds.magiclantern.fm/jenkins/job/QEMU-nightly-tests/208/artifact/qemu/magiclantern-Nightly.2016Oct26.450D110/4-focus-peak.png) (https://builds.magiclantern.fm/jenkins/job/QEMU-nightly-tests/208/artifact/qemu/magiclantern-Nightly.2016Oct26.450D110/7-focus-patterns.png)
Animation (click to zoom):
(https://builds.magiclantern.fm/jenkins/job/QEMU-nightly-tests/208/artifact/qemu/magiclantern-Nightly.2016Oct26.450D110/thumbnails/menu.gif) (https://builds.magiclantern.fm/jenkins/job/QEMU-nightly-tests/208/artifact/qemu/magiclantern-Nightly.2016Oct26.450D110/menu.gif)
Emulation log (https://builds.magiclantern.fm/jenkins/job/QEMU-nightly-tests/208/consoleText)
Canon menu screenshots (without ML loaded):
(https://builds.magiclantern.fm/jenkins/job/QEMU-tests/208/artifact/qemu/tests/450D-menu.png)
Besides the not-so-impressive feature set, I have a few questions:
- On the actual hardware, do the fonts look as bad as in the following screenshot?
(https://builds.magiclantern.fm/jenkins/job/QEMU-nightly-tests/208/artifact/qemu/magiclantern-Nightly.2016Oct26.450D110/5-spotmeter.png)
- Do the colors in the menu customization mode really look as radioactive as these?
(https://builds.magiclantern.fm/jenkins/job/QEMU-nightly-tests/208/artifact/qemu/magiclantern-Nightly.2016Oct26.450D110/8-customize.png)
- Does the "ETTR ETTR ETTR ETTR" message show up on actual hardware as in the above screenshot?
Another surprise: if I compile ML from the vxworks branch (https://bitbucket.org/hudson/magic-lantern/branch/vxworks) (here) (https://builds.magiclantern.fm/jenkins/job/450D.110/1/), it doesn't boot correctly (https://builds.magiclantern.fm/jenkins/job/QEMU-nightly-tests/200/consoleText). When trying to compile from Ant's repository, changeset b05d7ea7f486 does not exist (https://builds.magiclantern.fm/jenkins/job/450D.110/3/consoleText) (did I misread the screenshot?) and his vxworks branch (https://bitbucket.org/Ant123/magic-lantern/commits/branch/vxworks) doesn't work either (emulation log (https://builds.magiclantern.fm/jenkins/job/QEMU-nightly-tests/209/consoleText) - it gets stuck on initial screen (https://builds.magiclantern.fm/jenkins/job/QEMU-nightly-tests/209/artifact/qemu/magiclantern-Nightly.2017Sep22.450D110/menu.gif)). Compiling from latest changeset from Ant (c700f92) gives the same result (stuck on initial screen, with LED turned on).
Unfortunately, I did not have this commit (https://bitbucket.org/hudson/magic-lantern/commits/9814dc67f327) when Ant posted his build - that would have embedded his local (uncommitted) changes in the executable file - so I'm unable to re-create his binaries from the current sources.
In any case, continuing the ML port on VxWorks models just got easier by an order of magnitude - or maybe two :)
Quote from: a1ex on September 22, 2017, 09:31:17 PM
Does the "ETTR ETTR ETTR ETTR" message show up on actual hardware as in the above screenshot?
Yes, if you are talking about ML Prefs menu.
QuoteCompiling from latest changeset from Ant (c700f92) gives the same result (stuck on initial screen, with LED turned on).
Try this patch:
diff -r 18ac6b0f9929 platform/450D.110/init.c
--- a/platform/450D.110/init.c Sun Oct 30 14:43:33 2016 +0200
+++ b/platform/450D.110/init.c Sun Sep 24 14:27:14 2017 +0300
@@ -89,7 +89,9 @@
// _mem_init();
bmp_vram_idle_ptr = malloc(360*240);
// _find_ml_card();
- msleep(550);
+ // msleep(550);
+ uint32_t size;
+ while((FIO_GetFileSize("AUTOEXEC.BIN", &size ) != 0) || (size == 0)) msleep(10);
_load_fonts();
// msleep(300);
call("DisablePowerSave");
Note: I'm using gcc-arm-none-eabi-4_7-2012q4. With GCC 4.8 it stuks.
Confirmed - works with gcc-arm-none-eabi-4_7-2012q4 (without requiring the FIO workaround).
BTW - address 0xFFD65490 doesn't seem valid for 450D - did you mean 0xFFD237F0 ?
Does that mean not all these patches from disable_cache_clearing are actually required for booting?
Quote from: a1ex on December 05, 2017, 01:55:49 AMBTW - address 0xFFD65490 doesn't seem valid for 450D - did you mean 0xFFD237F0 ?
Yes. There was wrong address 0xFFD65490.
But it doesn't help to create working binaries using modern GCC.
Only gcc-arm-none-eabi-4_7-2012q4 generates binary which doesn't stuck.
QuoteDoes that mean not all these patches from disable_cache_clearing are actually required for booting?
I don't know. I just found the same opcodes based on 40D port.
Quote from: mikeuk on August 26, 2017, 11:55:02 AM
I have tried it on my 450D and it doesn't seem to work. It is installed but I can't seem to be able to load the ML menu up, Also it messes up the live mode, it flashes strange text.
When I press bin buttom this is what show up, then it crash and have to remove the battery to restart. I pressed Set and nothing happened.
(http://thumb.ibb.co/j0sJ45/IMG_20170826_104255.jpg) (http://ibb.co/j0sJ45)
I do have 1.1.0 firmware installed. Is there a different region of 1.1.0 firmware?? My camera is UK Version.
Many Thanks
Mike
should not matter i Had 450D working with it ...i m in UK.... but have since traded in the 450D ...got as latest i could now on 77D (love it or hate it) not looked back i really like it as a huge leap forward. ye could get better but its what i wanted so :P
I have the same problem, i just put the .FIR file and was try to install it. now the camera is not booting. please help me to resolve this issue.
I guess you put the installer (ML450D110.fir) on the card but not the ML itself. The installer set the boot-flag in the camera and made the card bootable but camera is not starting, as the the ML files are missing.
You have several solutions:
- put the ML to the card; unpack the files from the following archive
https://bitbucket.org/Ant123/magic-lantern-40d/downloads/magiclantern-Nightly.2016Oct26.450D110.zip
or
- format the card in a PC or another camera to make it non-bootable again.
In both cases camera should boot again. To clear the boot-flag from your camera you have to make it boot using any of the mentioned solutions, then put the installer on a working card (ML450D110.fir file) and select "update firmware" from camera's menu again.
I'd be interested a lot in helping out. I have experience with C, but no experience with CFW of any kind. Can someone point me to resources specifically about ML?
https://www.magiclantern.fm/forum/index.php?topic=991 (https://www.magiclantern.fm/forum/index.php?topic=991)
https://bitbucket.org/hudson/magic-lantern/src/qemu/contrib/qemu/ (https://bitbucket.org/hudson/magic-lantern/src/qemu/contrib/qemu/)
https://bitbucket.org/hudson/magic-lantern/src/qemu/contrib/qemu/HACKING.rst (https://bitbucket.org/hudson/magic-lantern/src/qemu/contrib/qemu/HACKING.rst)
Hi everybody, I have a 450D and I would like tu use ML on it. I have tried to install it but is not working.
I have downloaded the files from the links given on the page 1 of this topic. I have used the installer ML450D110.fir and the files from the zip file 'magiclantern-Nightly.2016Oct26.450D110'.
My firmware version is the correct one 1.1.0 and the SDcard it has been modifided on EOScard so it is not Bootable.
When I try to install ML the screen gets black and a blue led is shinning.
May I am missing something? Or what am I doing wrong?
EDIT: Finally I could run ML on my 450D. I tought I could use video recorder function but it does not allow me. Is there any other version which I can record video with?
Thank you so much
Quote from: miguelate on May 08, 2018, 04:19:04 PM
Is there any other version which I can record video with?
EOS 450D has no video recording function out of the box. It's only theoretically possible to implement Motion JPEG(848x568px, ~22fps) recording without sound, but I abandoned the porting process in 2016 because of problems with the compiller...
Quote from: Ant123 on May 08, 2018, 10:14:16 PM
EOS 450D has no video recording function out of the box. It's only theoretically possible to implement Motion JPEG(848x568px, ~22fps) recording without sound, but I abandoned the porting process in 2016 because of problems with the compiller...
Interesting -- Can you share any code ?
I'm interested in trying to get mjpeg implementation on 5d2 & other digic4 cams .
I don't have any code.
But AFAIK this program (https://sourceforge.net/projects/eos-movrec/) captures MJPEG frames via USB. I posted the resolution and framerate from video file recorded using this program. The average bitrate was ~30-35 Mbit/s. Maybe it's limited by USB.
Thank you so much for your reply Ant123
Quote from: Ant123 on May 09, 2018, 09:36:57 AM
I don't have any code.
But AFAIK this program (https://sourceforge.net/projects/eos-movrec/) captures MJPEG frames via USB. I posted the resolution and framerate from video file recorded using this program. The average bitrate was ~30-35 Mbit/s. Maybe it's limited by USB.
Ok , I know of this already thanks.
On another note , I was wondering if you could PM me you rom files form a download link somewhere ?
I interesting in decompiling it to do some investigations in the Jpeg routines .
Quote from: reddeercity on May 10, 2018, 04:26:24 AM
if you could PM me you rom files form a download link somewhere ?
I interesting in decompiling it to do some investigations in the Jpeg routines .
If you don't want to wait you can download (http://chdk.wikia.com/wiki/1000D#Available_firmware_dumps_.26_updates) and decompile 1000D fw right now.
Or do you need exactly 450D?
Thank they could be useful , I'll check them out .
QuoteOr do you need exactly 450D?
Yes , I want to see how thinks work in this cam , but that alright @ArcziPL sent me one (thanks again)
So essentially, after I got the vxworks branch to compile, I tried to (probably in the worst way possible ;) port your patches for the 450D to the current tree, but I got really cryptic compiler errors. I will instead try to fix module compiler problems (not much better, but not as many) to get other modules working.
Also, am I the only one who has a flickering LiveView screen as long as ML is enabled?
Hi, I am an owner of the 450D.
I am interested in the idea of using this camera as a 4K video camera. I saw your discussion and have been trying to get this working for quite some time now. Can anyone do a step by step basic tutorial for me to try and get somewhere?
Thanks,
Dog101
Quote from: Dog101 on June 02, 2018, 11:52:49 PM
I am interested in the idea of using this camera as a 4K video camera.
slow image sensor * slow processor * slow storage device = bad idea :)
Quote from: miguelate on May 08, 2018, 04:19:04 PM
EDIT: Finally I could run ML on my 450D. I tought I could use video recorder function but it does not allow me. Is there any other version which I can record video with?
¿How you make it work? i was trying and i can't make it run... :(
Buenas noches Tengo una Canon Rebel XSi o conocida como la 450D y me gustaría instarlarle la versión mas reciente del Magic Lantern para este modelo agradezco el enlace de descarga y sus indicaciones. QAP
https://builds.magiclantern.fm/
Hi im new to ML, i use to use CHDK on other two Canon cameras and now i want to use my 450D with ML.
I encounter same problems. The screen goes off and the blue led lights up with working autofocus.
What i missed?
Thanks in advance.
In addition i will post some screenshots:
(https://thumb.ibb.co/g1Xuaz/20180819_193003.jpg) (https://ibb.co/g1Xuaz)
(https://thumb.ibb.co/gNRWNe/EOScard.jpg) (https://ibb.co/gNRWNe)
(https://thumb.ibb.co/j3iE8K/sd.jpg) (https://ibb.co/j3iE8K)
Have the same problem.
ML in my camera 450d dosnt work.
Eoscard 1.40 cant help either.
1. Format card
2. copy https://bitbucket.org/Ant123/magic-lantern-40d/downloads/ML450D110.fir
3. During update blue led is blinking and nothing happend.
Any one can help ?
Quote from: qendis on February 16, 2019, 12:05:05 AM
3. During update blue led is blinking and nothing happend.
Quote from: Ant123 on October 26, 2016, 10:54:53 PM
Installer for 450D firmware 1.1.0. : https://bitbucket.org/Ant123/magic-lantern-40d/downloads/ML450D110.fir (https://bitbucket.org/Ant123/magic-lantern-40d/downloads/ML450D110.fir)
It works the same as 40D/5DC installer.
From 5D Classic thread:
Quote from: coutts on June 14, 2012, 04:54:02 PM
7.) Launch the firmware update process. If you see any red led, then something went wrong. A solid blue led means that the bootdisk is now enabled. A blinking blue led means the bootdisk is now disabled (if you want to completely uninstall ML). Each time you run the firmware update it just toggles the bootdisk to the opposite of whatever it is currently. The installer FIR will make your CF card bootable for you, no further work required here.
8.) Turn the power switch off and pull your battery to turn the camera off. Just turn the camera on (make sure autoexec.bin and ML directory are on the card!) and you're all set. Press the Trash button to bring up the ML menu.
You only need to run the firmware update to enable the bootflag ONCE. Each time after that will only disable, re-enable, disable, re-enable, etc. the bootflag.
ML still does not work.
I installed the update.
After the installation, I deleted the file from the card.
I've put ML on the card.
When the camera is turned on, the red LED lights up red and nothing happens.
After turning off the boot, the camera starts normally, the trash button does not give anything.
I do not know what to do. I think I'm making a mistake somewhere.
(https://lh3.googleusercontent.com/6Hb2BQDXMD1I8PeIHWG0G6hdn4MaywLdFYbwvamhunFTOIH3amrTufYbNTMb8oq2gPN5S1rtsHn91s7igJN4AVwzyuYnI-PNTs0CgDWopBZPWx_Mlkd8facFhgUBcPCHBe7hUMO9a7-KMJow5to0-oES5SD7uVaz4kCHSS5Ms7gZbcRpdBm7S6L3YhBusi7f6hvaRGOuO1E7t7v89x4JH0if8pbgvJbUPc0OG6-hMYk1PjmlBNORT2xVuvBHWlnpHSz52BAOW8vTAaEyckhwJOAYUphQ5J_bJWFFoX8ubBuzIlGMcsRsrKb97VP9yqwocVEBOJjp7_ScwCIc9VGCVe7Z1-76SKhLlONwyR1qSwdtqg4_xPqRsIJIVUAy87fppmEydGHlZUXoGRoZVlJ60gXw-KAsvG5LbeTGozCfBQDMztISee4tgTg0CicwmerbflzxKZzIzdymMo029e1aFLN0vRQSDIDJvry4wQEXbJv72RE45KmbzXmdcYfRB7AB6ify1V0PmTkO3nHUt0GPXFw23h_9ROeBsXA9FxrsdgjrBmCuSdDhOZkRsK4v4DS4eVv7AUT47fS1WPRFppYLSZutx0rJk73wp-9BgWhaq79U4965gR0UdNnNfBGxSx3lL35EsgGeYwwPJizlwhJ4bS_fDxHUAa4=w800-h520-no)
(https://lh3.googleusercontent.com/TTMF8IQDWh8KYXIeM1EWAmPg6YPaHDz3upEVYtPTZbwRhCsxwa0aNk9ZrX7luW2OW9TbZFgEWyHuRXGVuzV4zXNrqTRO8nzEhjayJo57le_bdOOpzdGy_ALa8-ArueHtz51GPBq8rDI9AYAdBJd_z12sPR3N_i9qjHV-0Fn2lr_U8iOdsk7wTBE80FFv2rDX_Nz3MU61drNIP6SEogAFJ7TtXFWs8R9R0SGtWyDv0IaIumHpsScbqMHldIF2fXkc3aRXOuJ3zO-l7_7qh1LVhwanmF5cUWVpZuuxB6uZbhDGfJHMyVIYZUFthISD6lyLtnPp7i2fTFnZo72SoGgd1cqXTB97IY2CJ5qJGK7JWMQkdfVUdTb2S0cC8zD-5EsG2FPpWgt2mRDdPKB37-mtswNfvwN4YbV8NzXANXZjo7hrnNZ1I1mjj-XLFmwGklA_84tvDOZWG9PmZR2th94DwutH7UFFb2tLWXux2CGdCmnV9JLUTegde_Fqm-xq128e6lmMWgSDZhnidiB6V_aymLAFRQesVX1cF2SE3ySNdl3gelxEjWL1q2vJg9y7zJ1_5C_XtmjAkFKbKvzppiDwjGcnWBie2wLn6Phx3Qy30xOjVRLRUwYTvECPu43IQVFQSy8Yi9vEwoPSM_9bVbhv_WZmv9qNQKk=w600-h308-no)
Quote from: qendis on February 16, 2019, 11:07:10 AM
I've put ML on the card.
Probably ML can't find some files in ML folder on SD card.
Try to format SD card in the camera and reinstall ML.
Welcome back. I successfully installed ML on another card.It works on an old 4 GB card.On 32 GB cards, the ML does not load. I tried it on two other cards. I do astrophotography and I need to brighten the view on the display so that I can set the focus on the stars. New versions of ML have this function available. Would you be able to program it into the 450D version? It would help me considerably. If you can do it, I would be willing to pay for that, just name your price.
Quote from: qendis on February 16, 2019, 12:56:38 PM
On 32 GB cards, the ML does not load. I tried it on two other cards.
You can try this build (https://bitbucket.org/Ant123/magic-lantern-40d/downloads/magiclantern-Nightly.2019Feb16.450D110.zip)
QuoteI do astrophotography and I need to brighten the view on the display so that I can set the focus on the stars. New versions of ML have this function available. Would you be able to program it into the 450D version? It would help me considerably. If you can do it, I would be willing to pay for that, just name your price.
Which function do you need? Can you explain exactly?
Note: ML is not a commercial project, so I do not need your money...
Quote from: Ant123 on February 16, 2019, 02:39:48 PM
You can try this build (https://bitbucket.org/Ant123/magic-lantern-40d/downloads/magiclantern-Nightly.2019Feb16.450D110.zip)
Which function do you need? Can you explain exactly?
Ho aganin.
I found a description of this function here:
https://wiki.magiclantern.fm/faq (https://wiki.magiclantern.fm/faq)
Probably the name is:
Increase display gain.
(https://wiki.magiclantern.fm/_media/nightdemo.jpg?cache=&w=720&h=480&tok=7e5b04)
"Can I use LiveView in complete darkness?
Yes. Increase display gain, use a low FPS (with FPS override), or both. With a bit of tweaking, you can make the LiveView bright enough to manually focus on stars, for example.
Also check out the dark color schemes optimized for night shooting, or try disabling exposure simulation."
I've compiled ML with FEATURE_LV_DISPLAY_GAIN.
But it doesn't work out of the box.
It seems that Digic 3 has no ISO_PUSH_REGISTER (0xc0f0e0f8).
Some registers are present (0xc0f08030, 0xc0f08034) but their modification has a very short effect. Probably camera refresh their values periodically.
Another problem is the lack of shadow memory. FPS override doesn't work either, but there are signs of FPS timers:
RAM:0000A7D4 08 60 F0 C0 DCD unk_C0F06008
RAM:0000A7D8 A3 09 A3 09 DCD 0x9A309A3
RAM:0000A7DC 0C 60 F0 C0 DCD unk_C0F0600C
RAM:0000A7E0 A3 09 A3 09 DCD 0x9A309A3
RAM:0000A7E4 10 60 F0 C0 DCD unk_C0F06010
RAM:0000A7E8 A3 09 00 00 DCD unk_9A3
RAM:0000A7EC 18 60 F0 C0 DCD unk_C0F06018
RAM:0000A7F0 20 00 00 00 DCD 0x20
Got MJpeg video by inserting this code into dm-spy function:
if (lr != 0xFFAD5870)
{
return;
}
uint32_t lvsize = MEM(0x8304);
char* lvbuf = MEM(0x8308);
if (BUF_SIZE > (len + lvsize))
{
char buff[9];
uint32_t* pnum = (uint32_t*)(buff);
*pnum = (uint32_t)(0x63643030); // "00dc"
pnum = (uint32_t*)(buff + 4);
*pnum = (uint32_t)lvsize;
memcpy(buf+len, buff, 8);
len += 8;
memcpy (buf+len, lvbuf, lvsize);
len += lvsize;
if (lvsize % 2 != 0)
{
char junk = 0;
memcpy (buf+len, &junk, 1);
len += 1;
}
}
return;
https://filebin.net/f1akbgb5uprvkrxp/DM.TXT.AVI
Is there better way to get LV JPEG data than intercepting debug messages?
The JPEG buffer is is populated *and* freed in lvcdevResourceGet, so... that's pretty much the only place for a hook, if you want to reuse Canon's approach. You could place a hook (patchmgr: patch_hook_function) directly into 0xFFAD5870, but that won't solve much (the hook code will only execute when needed, so it will be a bit cleaner). You should also speed up the copying process with either dma_memcpy (HPCopy) or edmac_memcpy; that should get rid of dropped frames.
On newer models (DIGIC 5, IIRC also 60D and newer DIGIC 4), this function no longer runs automagically while in LiveView, so this approach is only valid for older models.
There is another drawback of this JPEG stream: it's not using the full LiveView resolution. On 450D, CR2 resolution is 4312x2876 (with dcraw), so I'd expect something close to 1436x958 in LiveView. On 5D2, CR2 resolution is 5634x3753, LiveView resolution is 1880x1248, LV-JPEG resolution is 1024x680. I'm pretty sure the hardware can deliver MJPEG at full LiveView resolution; "just" need to figure out how to how to request a full-size YUV buffer (most Canons do this while recording H.264) and how to call the JPEG encoder on an arbitrarily-sized YUV buffer (likely very similar to the lossless encoder).
BTW - disabling this JPEG stream on old models could be useful for reducing power consumption. Nothing measured; just theory.
QuoteI'm pretty sure the hardware can deliver MJPEG at full LiveView resolution
But which framerate?
Current LV-JPEG resolution 848x568 used by EOS utility, EOS SDK and eos_movrec. The framerate is around 20-22.
Do you think it's limited by USB throughput?
The main limiting factors are sensor readout speed, JPEG encoder speed and SD write speed.
Sensor readout speed:
- photo mode: timer A = 0x13EB, B = 0xB39 (from an older log from you), 91 microseconds / line (from 0xFFBDF2E8 VSizeSetting), so main FPS clock must be... 56 MHz x 1 channel. Yes, it's not much slower than 500D (32 MHz x 2 channels). Full-res capture at 3.82 FPS.
- LiveView: timer A = 0x9A3 (from your post), B = 0x2F7 (from your log). This gives 29.856 FPS. During initialization, LiveView runs with timer B = 0x405, i.e. at 22 FPS. See this graph:
(https://a1ex.magiclantern.fm/bleeding-edge/lv-resolution/450D.png)
Raw readout resolution: 1440x572. From this, you will have to trim some black borders. Unfortunately, this 572 smells like 5x3 binning (572*5/3=953). Guess: (AD)TG register [100C] might control this (set to 2 for 3x3 binning; default 4). FFBE168C tg_write.
24p: expecting about 1440x760 (including borders). Maybe 1440x820, if timer A can be reduced to 2298. Maybe even more if HEAD timers are also adjusted (decreased); just a guess.
JPEG encoder speed: measure the execution time of FFBF9F44 / FFBF9DF8 (whichever is used). Place a hook before and after the call, and write down the microsecond timer delta.
SD card speed: trivial to benchmark. Expecting about 20 MB/s. Continuous recording at about 800K per JPG frame.
How to avoid the flashing(flickering) of ML menu and OSD in LiveView mode?
It also changes the colors of Canon's OSD elements.
Was the lv_rec module replaced by mlv_rec? I'm trying to choose the reference for MJPEG recorder.
Menu flickering: define GUIMODE_ML_MENU as:
#define GUIMODE_ML_MENU (lv ? 28 : 2)
That's the only valid value I could find in QEMU for LiveView.
Colors: I'd expect Canon code to restore their own palette, but needs to be double-checked (whether it works in LiveView etc).
As reference code, I'd start from mlv_lite and delete a bunch of stuff specific to raw recording. You will want to look at crop_rec_4k, as that's the only version working with variable frame sizes, but it will require heavy tweaking on the memory management side. It's a bit more complicated than it needs to be, but... the alternative would be to reinvent the wheel (buffering, speed optimizations and so on).
Quote from: a1ex on February 24, 2019, 07:43:33 PM
Menu flickering: define GUIMODE_ML_MENU as:
#define GUIMODE_ML_MENU (lv ? 28 : 2)
It doesn't help.
This video was made with #define GUIMODE_ML_MENU (RECORDING ? 0 : lv ? 49 : 2)
https://filebin.net/f1akbgb5uprvkrxp/MVI_7190.MP4?t=3h26fipc (https://filebin.net/f1akbgb5uprvkrxp/MVI_7190.MP4?t=3h26fipc)
Quote
You will want to look at crop_rec_4k, as that's the only version working with variable frame sizes, but it will require heavy tweaking on the memory management side. It's a bit more complicated than it needs to be, but... the alternative would be to reinvent the wheel (buffering, speed optimizations and so on).
Unfortunately vxworks branch is too old and has no mlv_lite and crop_rec_4k modules.
SetGUIRequestMode(28) from "Don't click me" (call it after a short delay) -> I expect this to bring some transparent dialog in LiveView.
If GUIMODE_ML_MENU is actually used, it should display the same dialog "behind" ML menu, i.e. a split-second before opening it.
CURRENT_GUI_MODE should be 2C94, btw. Who knows what else is wrong, as I can barely start it in QEMU.
Quote from: a1ex on February 24, 2019, 08:24:51 PM
CURRENT_GUI_MODE should be 2C94
Already found it by myself. But it doesn't help.
Nice , thanks for starting up Mjpeg , being wanting to get in this for the last 6 months at least on d4 cams.
Great info :) This is the kick starter I've being looking for .
Quote from: Ant123 on February 16, 2019, 08:36:28 AM
From 5D Classic thread:
Thanks Ant123. At last it worked for me. I got the solid blue light when i updated the firmware with ML-SETUP.FIR. Then i've deleted the .fir file from SDcard and then put it back. Now the ML menu appears when i press Delete key. Now its time to figure it out how it works, and it'll take time. For now intervalometer works fine. Thank you guys.
I also instal sucesfull MR on my old 450D. Now i cant figure it out is there any way to shoot video with this camera?
Quote from: sliper on May 10, 2019, 12:12:24 AM
Now i cant figure it out is there any way to shoot video with this camera?
There is only one way (https://sourceforge.net/projects/eos-movrec/) which works at the moment.
Recording MJPEG video on SD-card is not ready yet. I'm not sure that this will be completed ...
Hey guys~
I successed installing the ML on my 450D which provided in the topic and i want to know is there any way to increase the ISO Value by using this ML firmware?
Thanks!
Hello I am new at magic lantern. I'm interested in features for astrophotography. I own the good old EOS 450D.
It is possible to take dark frames without wearing the shutter mechanism with long time exposure. More than 15 sec ?
I have seen the silent mode feature but there is only a max exposure of 15sec possible.
Could this function also be included in the PTP so that the dark frame can be triggered remote via usb?
If possible, my sequence should look like this and be triggerable via PTP:
Dark frame, light frame ( normal picture ), dark frame, light frame, ....
exposure time is greater than 1 minute.
For a better understanding:
I would like to activate the Canon Long Exposure Noise Reduction but do not use it in the EOS but instead save the created dark frame to the SD. So I always get a light frame and a dark frame on SD. Is that possible?
Hello to everyone!
First of all, sorry if my english is bad.. I'm spanish and I don't practice it so much..
I own a 450D and I'm interested in ML, but I have read the post and I have some doubts:
1- wich is the last file to download and install?
2- ML only is installed on SD card, or it modifies the firm?
3- Nowadays it works without bugs?
Thanks!
Hi!
1 - I don't know. But hopefully my answering will push this to the top and someone will notice and have an answer.
2 - ML runs from the card and is not permanently installed into firmware. The installer does make a small change to firmware, this enables booting from cards.
3 - Magiclantern will never be bug free, it is software. It works very reliably on some cameras, worse on others. I don't know how good it is on 450D.
There are no significant canges since reply#23 (https://www.magiclantern.fm/forum/index.php?topic=8119.msg173857#msg173857)
Runing ML GUI doesn't mean ML functionality.
So I think this topic should be removed from "Sticky Topics".
Hi!
I'm new to ML but since I just activated it in my 450D, I figured I'd explain in some more detail how it's done and what's actually achieved with ML on the 450D.
Installing:
- Check your firmware in the camera. It should be 1.1.0. If not, you need to find this firmware and upgrade the camera to it. There are links to the firmware on this site.
- Format your SD card in the camera and select "Low level format". This is done in the camera's original menus. All files on the SD will be lost.
- Remove the SD card from the camera and insert it into a card reader in your computer.
- Find the most recent ML package for the 450D. As of now, it's this one: ML test build for 450D firmware 1.1.0. : https://bitbucket.org/Ant123/magic-lantern-40d/downloads/magiclantern-Nightly.2016Oct26.450D110.zip
- Unpack the contents of the ZIP file you just downloaded to the root of the SD card (keeping the directory structure intact of course).
- Also download this small firmware file: https://bitbucket.org/Ant123/magic-lantern-40d/downloads/ML450D110.fir
- Copy the .fir file to the SD card. It should be copied to the root directory of the card.
- Unmount/eject the SD card in your PC operating system properly before removing it so you don't lose any information on it.
- Insert the SD card into the camera and power the camera on
- To make the SD card bootable, you perform a firmware upgrade in the camera menus. The trick here is that the .fir file you put on the SD is not actually a firmware for the camera but rather just a program that makes the SD card bootable.
- During the "firmware upgrade" process, the camera will (very soon) light up the blue LED by the WB button on the back of the camera. This is the verification that the card was made bootable.
- You now need to remove the battery in order to restart the camera. Just off/on will not work. Don't panic - even if this is NOT how you abort a normal firmware upgrade, this is what you need to do in this case.
- If you decide to make your SD card not bootable anymore, just perform a "firmware upgrade" again. This time, the blue LED will blink slowly. This indicates that the SD card was reverted to its original non bootable state. Again, removing the battery afterwards is the only way.
Now, fire up the ol´cam and hit the trashcan button on the back of the camera. Now, you should see the ML menus.
You can remove the .fir file if you like as that's not part of ML. I keep it on my SD so I can revert the bootable state of the SD if I like.
If you´d like to have multiple SD cards with ML, just copy all files to that SD and insert it into the camera. Then perform the "firmware upgrade" with the .fir file on the SD card and restart the camera. Every SD that you want to run ML on needs to be bootable. You can have one ML activated SD for the camera and other SDs that are not. Whenever you start the camera with the ML activated SD, you will have ML menus, otherwise not.
This is what the SD cards looks like for me:
E:\>dir
Volume in drive E is EOS_DIGITAL
2020-03-31 23:05 <DIR> DCIM
2020-03-31 23:05 <DIR> MISC
2016-10-26 22:57 260 704 autoexec.bin
2016-10-26 22:58 <DIR> ML
2020-03-31 22:29 1 247 ML450D110.fir
So, you have ML in your 450D, what can you do with it? Not much at this time (and likely not anywhere in the near or even far future). ML is designed for other platforms than the 450D and seems difficult to port to the likes of the 450D. At this time, only the intervalometer function is supposed to work. It gives you the possibility tell the camera that instead of taking one picture, it should take a number of pictures (configurable) by either pushing the trigger button half way of fully, or just wait a few seconds after leaving the menu and then start taking pics. The interval between the pics is also configurable. That's it as far as I can see. If you need this function, ML is great. If not, why bother on a 450D?
I hope this helps someone that likes to try ML on the 450D.
/Fredrik
You missed the part about cam's bootflag. It's set during first ML installation and removed if proper ML removal is performed.
A cam with bootflag set will react slightly different than without and there may be unwanted side effects.
- A cam with bootflag set will access each (!) card during startup and check if card is bootable. If card is not bootable booting into plain Canon mode will happen. If a bootable card is found it will load autoexec.bin. If autoexec.bin cannot be found cam will get stuck and you have to remove battery.
- If cam with bootflag set is in powersave mode it will access card during wake. This will cause a delay. If you can't have this because timing is critical you have to prevent cam from going to sleep.
- Because of ML's accessing procedure a cam with bootflag set may cause troubles with some cards. Some older EyeFi cards are known to be incompatible with ML and such cards are not usable with bootflag set. In cams with CF-cards CF-to-SD adapters are known to cause troubles.
Maybe I misunderstood the part with the boot flag. I was under the impression that the small .fir file was supposed to make the SD-card bootable (after performing a firmware upgrade in the camera menus) , not setting anything in the camera. Is it the camera that has some boot flag altered by the .fir file instead?
Anyone happen to have the 1.1.0 firmware? The Canon site doesn't have it any more.
https://pel.hu/eoscard
https://pel.hu/down/e5kr4110.exe
Hello all, I have an XSi and wanted to try ML, I do have Canon FW 1.1.0, and so I did the steps that fb35523 listed and after removing the battery and putting it back into the camera I saw the RED led in the bottom right is on all the time. Not feeling good about this...
So I turned off the camera and removed the battery and put the same card back in same happend's, it's been 3 minuets or more same RED led is on. I turned off the power switch and then removed the battery and removed the card and put back the battery and turned on and dead not RED led no LCD and not working. Really not good.
Just now I powered off the camera and removed the battery and then removed the card and the body was back to normal no ML...Any Ideas PLEASE??
Thank you
Christopher
Quote from: cengell on May 17, 2020, 12:05:46 AM
Any Ideas PLEASE??
It looks like your SD card is not bootable or don't contain ML files or incompatible with ML.
You can also try a newer build (https://www.magiclantern.fm/forum/index.php?topic=8119.msg212143#msg212143)
Good morning I'm a 450D canon owner. I was wondering if it is possible to install modules in this camera? I tried to install the helloworld module (this one : https://www.magiclantern.fm/forum/index.php?topic=19232). I copied and pasted the .mo file in the sd(in the module folder) but the camera can't and see it.
Thank you
Damiano
Quote from: Damiano on June 23, 2020, 01:04:57 PMI was wondering if it is possible to install modules in this camera?
It's possible if you have enough programming skills to develop(adapt) and recompile modules.
Most likely, most modules will not work on 450D because this port is slightly abandoned...
Hi to everyone ,
Is it possible to use the feature "Dump image buffers" on the EOS 450D??
Thank you,
Damiano
Quote from: Damiano on July 02, 2020, 11:35:06 AM
Is it possible to use the feature "Dump image buffers" on the EOS 450D??
Not yet.
Hello, i'm trying to use this code in a module to save a dng file with the raw_info.buffer information but the dng file that it saves in the sd is always the same and is only 38.8kb
Is that a problem of the camera or am I doing something wrong?
void* buf = malloc(raw_info.frame_size);
if (buf)
{
memcpy(buf, raw_info.buffer, raw_info.frame_size);
char filename[50];
get_numbered_file_name("bad%02d.dng", 99, filename, sizeof(filename));
struct raw_info local_raw_info = raw_info;
local_raw_info.buffer = buf;
save_dng(filename, &local_raw_info);
free(buf);
}
Thank you,
Damiano
The problem is that ML is not fully ported for 450D. Many functions are not yet implemented and therefore should not work properly.
Last year I was trying to implement "silent capture" module without success. I also stucked with raw_info.
Inorder to use raw_info, you need config_raw_liveview supported and you need to enable RAW transfers.
Is config_raw_liveview supported on this camera??
Thank you,
Damiano
I dont think it is implemented, but only Ant123 knows for sure.
Quote from: Damiano on July 12, 2020, 10:56:42 AM
Is config_raw_liveview supported on this camera??
Thank you,
Damiano
Not yet. There are no changes since 2019.
Tried to use fast SD Card - Sandisk Extreme Pro 95MB/s (UHS-I U3 V30). CHDK benchmark on Digic6 camera writes at 70+ MB/s.
On 450D ML benchmark in playback mode writes at 19-20 MB/s. The theoretical limit is 48MHz / 2 = 24MB/s.
Can't display benchmark results in LiveView mode because canon code refreshes the bitmap buffer continiously and ML texts are flickering or disappear. How to fix it?
Now MotionJPEG recording is more stable at ~29.7FPS (dual write buffering - 2x8MB).
But frame drops still occur when the frame size exceeds 400kB for a long time.
In some very spetial situations frame size can exceed 700kB. For example: https://i.stack.imgur.com/YbUvO.gif (https://i.stack.imgur.com/YbUvO.gif)
The experimental build is there (https://bitbucket.org/Ant123/magic-lantern/downloads/magiclantern-Nightly.2020Jul21.450D110.zip)
Quote from: Ant123 on July 21, 2020, 10:39:09 PM
Tried to use fast SD Card - Sandisk Extreme Pro 95MB/s (UHS-I U3 V30). CHDK benchmark on Digic6 camera writes at 70+ MB/s.
On 450D ML benchmark in playback mode writes at 19-20 MB/s. The theoretical limit is 48MHz / 2 = 24MB/s.
Can't display benchmark results in LiveView mode because canon code refreshes the bitmap buffer continiously and ML texts are flickering or disappear. How to fix it?
Hi Ant123
I never any flickering on 40D, not even on the early version, but if you have flickering the buffering system is'nt working correctly, might be due to incorrect WINSYS_BMP_DIRTY_BIT_NEG address. If that one is incorrect the BMP_LOCKS in dialog_test.c will not work, and that might result in flickering. Without locking canon is free to redraw.
Quote from: Ant123 on July 21, 2020, 10:39:09 PM
Now MotionJPEG recording is more stable at ~29.7FPS (dual write buffering - 2x8MB).
But frame drops still occur when the frame size exceeds 400kB for a long time.
In some very spetial situations frame size can exceed 700kB. For example: https://i.stack.imgur.com/YbUvO.gif (https://i.stack.imgur.com/YbUvO.gif)
That is really interessing, too bad I don't have time atm to implement your module on 40D, maybe after summer holiday.
Quote from: heder on July 22, 2020, 01:34:35 PMThat is really interessing, too bad I don't have time atm to implement your module on 40D, maybe after summer holiday.
You need only modify lines (https://bitbucket.org/Ant123/magic-lantern/src/d855737fc7cf6c101b92bb6bea162bee7e4718f6/modules/mj_rec/mj_rec.c?at=vxworks-dm-spy) 559, 560, 715 and 755.
Good day. tell me on the latest version of the magic lantern is the focus peaking function implemented? moved from film and got used to manual fixes. and this function would help me. only she is needed.
Quote from: MrGoodween on July 22, 2020, 08:29:33 PM
on the latest version of the magic lantern is the focus peaking function implemented?
Not implemented on 450D.
Out of curiosity, does this port include the patch manager stuff? I'm wanting to use ML to help with trying to circumvent the SD Card write lock issue on mine (it shows as being set to lock no matter what, and not had any luck getting it to show otherwise so far), and I saw a1ex had a method for circumventing the check with ROM patching that required the patch manager.
Hello,
I'm trying to find the STATE objects of the 450D. In particular i'm trying to find the address of SCSState and SSSState.
I'm using this procedure on qemu as a1ex said : https://www.magiclantern.fm/forum/index.php?topic=17969.msg196010#msg196010
but the first part of the code doesn't return nothing.
./run_canon_fw.sh 450D,firmware="boot=0" -d calls |& grep --text EvfState
Any idea why the code doesnt't work and how can find SCSState and SSSSate for this camera?
Thank you,
Damiano
I was able to redo the procedure of a1ex using FWState instead of EvfState but the SCSState and SSSState are not present in the final result. Does anyone know what's the name of SCSState and SSSState for this camera?
Thanks.
Damiano
Hi all.
I am new to this forum and I appreciate the enormous work that you are all doing.
I am trying to install ML on a 450D.
When trying to download the BITBUCKER links give an error.
Could someone post a link with the latest version that works?
Thank you very much
Quote from: dopler on September 11, 2020, 11:39:01 AM
Hi all.
I am new to this forum and I appreciate the enormous work that you are all doing.
I am trying to install ML on a 450D.
When trying to download the BITBUCKER links give an error.
Could someone post a link with the latest version that works?
Thank you very much
web.archive to the rescue .. for now use ..
Firmwarehttps://web.archive.org/web/20200621212226/https://bbuseruploads.s3.amazonaws.com/39131396-31da-4c59-98ed-3df70d37782d/downloads/9e0f7550-647f-4982-82be-b7eeec449aad/magiclantern-Nightly.2019Feb16.450D110.zip?Signature=DuZqzUI%2FRhpGC%2BEAtPTZXVAyXZE%3D&Expires=1592776346&AWSAccessKeyId=AKIA6KOSE3BNJRRFUUX6&versionId=4rR_PYbb_295GyYgICNVFnf4WK4NLQjV&response-content-disposition=attachment%3B%20filename%3D%22magiclantern-Nightly.2019Feb16.450D110.zip%22
Bootflag flipperhttps://web.archive.org/web/20200621212220/https://bbuseruploads.s3.amazonaws.com/39131396-31da-4c59-98ed-3df70d37782d/downloads/99b44d90-6666-4ac9-b358-5859e60ff378/ML450D110.fir?Signature=yy3eSRCThCOgnTyGPhMUGuEJPAk%3D&Expires=1592776340&AWSAccessKeyId=AKIA6KOSE3BNJRRFUUX6&versionId=24Txxkdk2Q7xoqtn.VqfpPIU2H7SUhbP&response-content-disposition=attachment%3B%20filename%3D%22ML450D110.fir%22
Im new to this and my 450d has the 1.0.4 firmware version, does anyone have a WORKING link for 1.1.0? most of the links i found dont work or arent trustworthy
And what exactly are the features for the ML for the 450D, I dont know everything about this
https://web.archive.org/web/20160306054850fw_/http://pel.hu/down/e5kr4110.exe
Quote
Firmware
https://web.archive.org/web/20200621212226/https://bbuseruploads.s3.amazonaws.com/39131396-31da-4c59-98ed-3df70d37782d/downloads/9e0f7550-647f-4982-82be-b7eeec449aad/magiclantern-Nightly.2019Feb16.450D110.zip?Signature=DuZqzUI%2FRhpGC%2BEAtPTZXVAyXZE%3D&Expires=1592776346&AWSAccessKeyId=AKIA6KOSE3BNJRRFUUX6&versionId=4rR_PYbb_295GyYgICNVFnf4WK4NLQjV&response-content-disposition=attachment%3B%20filename%3D%22magiclantern-Nightly.2019Feb16.450D110.zip%22
Bootflag flipper
https://web.archive.org/web/20200621212220/https://bbuseruploads.s3.amazonaws.com/39131396-31da-4c59-98ed-3df70d37782d/downloads/99b44d90-6666-4ac9-b358-5859e60ff378/ML450D110.fir?Signature=yy3eSRCThCOgnTyGPhMUGuEJPAk%3D&Expires=1592776340&AWSAccessKeyId=AKIA6KOSE3BNJRRFUUX6&versionId=24Txxkdk2Q7xoqtn.VqfpPIU2H7SUhbP&response-content-disposition=attachment%3B%20filename%3D%22ML450D110.fir%22
Which of these do i need to download? because i got 3 .FIR files, ML450D110, ML-setup and e5kr4110.
The last one is the firmware update for 1.1.0 and not one of the others works to get ML on my 450D, I constantly get the error
'update file error please check the memory and reload the battery and try again'
First update to 1.1.0, then use Magic Lantern files.
I uploded the source code (https://bitbucket.org/Ant123/magic-lantern-450d/src/vxworks-dm-spy/) and the latest build (https://bitbucket.org/Ant123/magic-lantern-450d/downloads/magiclantern-Nightly.2021Aug07.450D110.zip) to bitbucket.
But the modules can't be built because of missing the ".hg" folder. How to fix that?
Motion Jpeg movie recording is still experimental. It is limited to the SD controller speed. Maybe there need to increase somehow the compression of JPEG frames.
Looks interesting, but it's hard to understand because there is not much context. This is a fork of some other repo? Which one? The commit history has lost everything from wherever it came from. It's not forked from mine because platform dir doesn't have any Digic 6, 7, or 8 cams. It would probably make more sense to have these changes on a branch of an existing repo, so that history was more meaningful.
You have a .gitignore file at top level, but official ML is hg managed - that's why you're getting these errors. You've probably taken this source from some git managed repo? The build process expects to use hg tools at a few places. Personally I think making the build process dependent on the source control system is not a good idea, I removed this in my repo so you might be able to adapt those changes:
https://github.com/reticulatedpines/magiclantern_simplified/commit/4a29a347f29276d4bec0876412cec4bb12b5a28c
https://github.com/reticulatedpines/magiclantern_simplified/commit/3163d41cee35fb54b4308e1f32318ff87de53645
Those changes might not cover everything you need, it was over a year ago and I wasn't very familiar with ML code yet, changes are more likely to be messy. Check commits around the same time.
This source code came from the official ML bitbucket repo last year before they removed all mercurial repos.
It contains my 450D related changes. Some code was taken from heder's 40D project.
But there was no changes since summer 2020. I was trying to convert mercurial to git locally but without success. Maybe I am wrong but it's strange that bitbucket do not provide mercurial to git conversion like github doing it (AFAIK).
Okay, in that case definitely look at the commits I linked. ML does shell commands in various places that explicitly call hg CLI commands. It is not possible to automatically convert it, the problem isn't the repo using git or hg, the problem is ML build system tries to use hg tools, and expects hg related directories to exist. You must modify the build system if you want to manage ML code using git.
The commits I link to make those changes.
Hi, just put the 2021-Version on my 450D -fine.
I have already my other 600Da (astro) with ML so want to use this as many others as 2nd device in the night (after get rid of th LPT2-Filter).
Well - I mainly use the Intervalometer to avoid the need of an external control.
So what I really miss is the control/entension of the shutter time in bulk mode (to get 60sec or more).
Is there any chance to get this (simple?) feature into the firmware?
KR
Marcel
Hi,
First, it's not likely as simple as you expect, second, the number of developers is very small. The number of devs who own a 450D is probably 1: Ant123. Either they notice this and decide they want to spend several days (at least) trying to get intervalometer working, or you'll need to learn how to do it yourself.
No problem - if this is really the case - makes no sence :-) I'll stay with external control. Was just an idea. But anyway - thank you for the work so far!
Quote from: dl1ekm on November 07, 2022, 08:16:46 AM
Hi, just put the 2021-Version on my 450D -fine.
KR
Marcel
Hi,
You mentioned that you have the 2021 version for your 450D. From the first download link I get "magiclantern-Nightly.2019Feb16.450D110" and this bootflag flipper "ML450D110.fir"
Can you please provide a link for this 2021 version and some instructions on how to do it? I mean how do I use or when do I use Bootflag flipper? I will search the forum, but if you can links it will be much appreciated.
Thank you.
BR,
Alin
https://bitbucket.org/Ant123/magic-lantern-450d/downloads/
Quote from: Walter Schulz on February 18, 2023, 11:20:23 PM
https://bitbucket.org/Ant123/magic-lantern-450d/downloads/
Thank you so much for quick reply.
I have copied the files to the root of the card. When I go in menu for firmware upgrade WB button led start to blink or remain solid blue and the screen remains black.
Canon FW is 1.1.0.
Should I try to run firmware update only with the "Bootflag flipper" on the card? Or try to prepare a bootable card with EOSCard utility?
Thank you in advance.
Please disregard my previous post. My brain malfunctioned :)
I create a bootable SD card with EOSCard utility.
After pressing Recycle button, there it was. ML in all it's glory.
Much appreciated all the help.
BR,
Alin
Hi,
I'm having a hard time getting the mentioned version to run on my 450D (1.1.0). I keep getting the blinking blue led on the camera. @alin.cocos, sorry for asking, but what do you mean by 'pressing the Recycle button' ?
I'm on macOS Ventura and can't use the EOSCard utility, so I used the MacBoot script. Can you maybe share an image of your SD card (with the ML version you used) ?
Got it working, now figuring out how the Live View option works via my MacBook Pro....
Best regards,
Rutger
Hey guys, I'm having a hard time trying to install ML on my 450D. I've tried everything mentionned in the forums and in the instal guide, but still nothing but a blinking blue led.
I tried with 3 different versions of ML (2018, 2019 and 2021) using EOSCard to make the sd card bootable but nothing.
I also tried formating the card with the camera or with the windows formating tool but it doesnt work either.
And I used 3 different cards thinking they were just not working but no.
None of my solutions worked and what happens is this:
- Screen turns black with blue led turning on
- Screen turns on to firmware update for a split sec
- Then goes back to black with the blinking led
- Autofocus with apperture and shutter speed still work in the viewfinder
If anybody could help me that would be great. Thanks guys
I installed ML on a 450D lately.
Use a small card (SD or SDHC) and retry.
First make sure your card is properly prepared:
Run EOScard and make sure both checkboxes are enabled after start. If not: You should run EOScard as admin, enable both boxes (BOOTDISK and EOS_DEVELOP), press SAVE button.
Report back
Okay so here are the steps I used:
- Format the card from the camera with low level format enabled
- Turn off the camera, remove the card
- Plug the card in the pc, extract magiclantern-Nightly.2021Aug07.450D110 inside it.
- Run EOSCard as admin, click refresh, select ML and hit save
- Place the card in the camera, turn on, go to the update page, hit ok
Result: Instant black screen and flashing led
Sometimes this happens and other times it shows up the firmware updating screen and then turns off + blinking led
Quote from: Troncature on April 12, 2024, 11:51:39 PM- Run EOSCard as admin, click refresh, select ML and hit save
Redo from scratch but don't use "ML" icon. Select BOOTDISK and EOS_DEVELOP checkboxes and press SAVE button on top.
Nope, same thing, when I manualy select EOS_DEVELOP and BOOTDISK it selects ML by itself. And this time it has the blinking led, its not constantly on
Quote from: Troncature on April 13, 2024, 02:06:20 AMAnd this time it has the blinking led, its not constantly on
Please clarify!
"And this time" implies you have had other results after installation.
Do you get LED burning constantly in the end?
As I said in the my second post, there are two results: either the led blinks with the firmware update flashing for a sec or just an instant black screen with the blue led flashing constantly.
This time the second result happened. Sorry for not clarifying well enough.
Thanks!
Visit https://eoscard.pel.hu and download Canon firmware 1.1.0 for 450D.
Wipe card by formating inside cam.
Extract e5kr4110.fir to card and run firmware update in cam.
After that retry ML installation.
I already updated it to this version, but I tried again anyways. This time, I tried keeping the 1.1.0 firmware inside the card alongside the ML files, and it gave me the choice to update either from the original firmware or the ML one, when I choose the ML one it, for some reason tells me confirm the update from 1.1.0 to 1.0.9. I press ok nonetheless and I get a firmware update error screen and I have to remove the battery to fix it.
The error is the following: Update file error. Please check the memory card and reload the battery and try again. ; Is the build I'm using broken? Its the one I downloaded from Ant123's repo.
Also, since I started these experimentations i've been getting some color flickering in the menus, they turn green yellow and red but it goes away when I change menu.
Hmm weird, I did nothing special but now when I put the card in the camera it doesnt want to turn on (except for the viewfinder and auto stuff). I have to remove the card then the battery to make it work again.
I formated the card from the pc and now its working again.
So after some further looking in the sd card i've found that with the last method I used (keeping the two firmware files) the instalation starts but gets interrupted by something as I can see a log file getting created with some logs inside it. I can see that it usually stops at "Scanning modules" but it managed to make some progress before getting stopped once but I forgot to save the log file.
Which is actually nice.
Because it indicates cam is prepared for ML.
Now make sure to have Canon firmware 1.1.0 and not 1.0.9 installed.
If so:
Use EOScard to enable EOS_DEVELOP and BOOTDISK. Copy extracted Nightly Build content to card (wipe anything else on card before).
Insert card into cam, startup cam and wait for some time until LED calms down. Then press trashcan button to access ML menu.
Oh my god I am so stupud, I completely forgot that I had to press the recycle button to go to the ML menu, I kept trying to install it from the firmware but theres no need to do that with EOSCard why didnt I think about that earlier lol.
But its not finished yet, I managed to go to the ML menu but I still have the weird color flickering that happens everytime now and its pretty annoying, and when live view is on it just happens constantly and not just for colors but even for menus, when I'm in live view and I press the ML button, it switches between LV, ML and the WB menu very fast so I can't do anything. Also the camera just freezes sometimes and I have to remove the battery to reset it. I dont know if these issues are just for me or because its still in developpement but thanks anyways mate, at least I got it working somehow