Magic Lantern Forum

Using Magic Lantern => Tutorials and Creative Uses => Topic started by: dfort on February 11, 2017, 02:58:02 AM

Title: Firmware Update/Downdate?
Post by: dfort on February 11, 2017, 02:58:02 AM
How to do a Canon firmware downgrade
(works for upgrade too)
Except for 5D3 1.3.6 (https://www.magiclantern.fm/forum/index.php?topic=18941.msg220980#msg220980) Only Canon has been able to downgrade one 1.3.6 is installed though not all service centers are willing to do it.
(Note that I have started a port for 5D3.136 (https://bitbucket.org/daniel_fort/magic-lantern/branch/update-to-5D.136-wip) but could not get it running--yet.)

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fc1.staticflickr.com%2F3%2F2119%2F32828449105_ee2f8d35fc_z.jpg&hash=9bdb32a4a334b1bb270b2f9acd4c2e75)

There seems to be a lot of FUD (Fear Uncertainty and Doubt) about changing the firmware on your camera, especially for uninitiated Magic Lantern users who are pointed to a website in Hungary run a guy who goes by the name of Pelican to get older firmware versions. Nothing against Hungary (I'm half-Hungarian) or Pelicans (I live at the beach) but a little anxiety is understandable.

Once you realize that it is extremely unlikely that someone created a FIR file that will cause your camera to send banking information to international cyber terrorists, download the file onto an SD card.

Firmware updates are generally posted in some sort of compressed format often along with the instructions on how to run the firmware update. If you are on a Mac and can only find a Windows version, don't panic. The *.FIR file runs on the camera so it doesn't matter which computer platform you are using. Of course you might download something that looks like this on your Mac:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fc1.staticflickr.com%2F4%2F3927%2F32757641751_ae93493402_q.jpg&hash=68625963d3d6397c986c0f9849d95d70)

Again, don't panic. This is a self extracting Windows archive and you can use Stuffit Expander which is in the Applications/Utilities folder of every Mac to expand the archive file.

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fc1.staticflickr.com%2F3%2F2637%2F32757641891_d4793f844d_z.jpg&hash=04f969a6e0ef56e65792f593b1e7be02)

I've got several cameras and like to play around with different versions of Magic Lantern so I put all of my FIR files on a single card. Make sure that the card doesn't have the boot flag enabled because if your camera also has the boot flag enabled it will just hang when you start up the camera unless you also add a ML autoexec.bin file and then it won't work on multiple platforms. In other words, this will be your dedicated firmware card.

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fc1.staticflickr.com%2F3%2F2721%2F31985719394_9f72b84d54_n.jpg&hash=5c53b505ca20378f037d1ac7f54dd659)

Those CCF14* firmware files are for the 700D/T5i, yeah I know it isn't obvious. And just in case you're thinking it, no the 5D3 firmware won't install on the EOSM. Only the valid choices will show up.

Now when you run the firmware update from the Canon menu using this card, remembering to have the camera in Manual and Still Picture mode, it will run the firmware update process--even if you are doing a firmware downdate. (Is there such a word?) The firmware update will not run if you don't have enough juice left in the battery and some external power adapters supply barely enough voltage to run the camera so it might not work. Best be safe and top off your battery first.

End of tutorial.

Not!

Firmware versions in the x.3.x series (currently only affecting 5D3) won't let you downgrade to a prior series. In other words, you can go from 1.3.4 to 1.3.3 but if there is a 1.2.3 or a 1.1.3 firmware on your card you'll get this message:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fc1.staticflickr.com%2F4%2F3785%2F32829254505_6b084888e3_z.jpg&hash=1c9102bff4d4440a4d38fd0077ada060)

It is not quite that easy with some of the latest Canon firmware updates. There are warnings about not being able to downgrade and rumors that you need some older 2.x version of Canon EOS Utility to do the downgrade but I found that is not really the case. If you happen to have one of those irrevocable firmware versions on your camera you can use whatever version of EOS Utility you have. Make sure to put a copy of the FIR file on your computer because you'll have to point to it with EOS Utility. Also make sure your camera is in Manual and Still Picture mode or EOS Utility will refuse to do the firmware update.

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fc1.staticflickr.com%2F1%2F545%2F32828853205_0749bec3a4_z.jpg&hash=ae1f0cfe2ad59da585c7ccd4152aa24b)

HA! Just noticed that "WTF Captions" item. Who says Canon engineers don't have a sense of humor?

Ok--back to doing this. You need to have a card in your camera so let's use that dedicated SD card with all the various versions. Here we go:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fc1.staticflickr.com%2F3%2F2342%2F32014345783_8000a6a2e4.jpg&hash=6b6e0a8624d7504a0afe6ced6f96e749)(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fc1.staticflickr.com%2F1%2F505%2F31985898384_f56b30c595.jpg&hash=d645790a2c5fc0b2e20937c0847048d2)(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fc1.staticflickr.com%2F4%2F3883%2F32828852675_b5042a60d5.jpg&hash=dffdb28bec5718653eb2b3b77d56d46d)(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fc1.staticflickr.com%2F3%2F2916%2F32014345443_a91be3a8b8.jpg&hash=c673f383dada41740ff58c3789d17957)(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fc1.staticflickr.com%2F1%2F391%2F32787820216_f23371cd31.jpg&hash=8c536861ca4c0f98486213f8aa8408fe)

Hey, what just happened? EOS Utility just transferred the firmware update from your computer onto the card in your camera and you can now disconnect the USB cable. The rest is exactly the same as before. In fact if you have multiple firmware versions on your card you can now have a second chance to decide which version you want to install.

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fc1.staticflickr.com%2F3%2F2827%2F32705592071_2c9799fb7d_z.jpg&hash=8158c504648603662a5189d72d703bf1)

Interestingly the firmware update will not change the status of the camera boot flag so you won't have to re-install ML. If you are curious what a new firmware version looks like, use the Portable ROM dumper (http://www.magiclantern.fm/forum/index.php?topic=16534.0) and run the ROM1.BIN file through a disassembler and...I'm getting off topic here, porting a firmware update to ML is another tutorial (https://www.magiclantern.fm/forum/index.php?topic=19417.0).

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fc1.staticflickr.com%2F3%2F2277%2F32014723493_4d4d869423_z.jpg&hash=a4203d48d1d8c6792a880d71c18365ac)
Title: Re: Firmware Update/Downdate?
Post by: ItsMeLenny on February 11, 2017, 03:57:01 AM
Whilst the opposite of 'upgrade' is 'downgrade' I think the opposite of 'update' would be 'rollback' or would it be 'outdate'. :P
Title: Re: Firmware Update/Downdate?
Post by: dfort on February 11, 2017, 04:10:21 PM
Here's an idea that is way beyond my reach but maybe possible--

How about making the 5D3.134 ML-SETUP.FIR able to live on the same card as the Canon FIR files and set it up so that the ML FIR loads first, checks to see if there are Canon FIR files on the card and give you the option to either install ML or perform a firmware update (or downdate/downgrade/rollback/outdate). Of course if it leaves the boot flag on the camera set after the update you'll get a message that the camera doesn't look like a 5D.134 but maybe the camera boot flag could be turned off before running the Canon file?

The only real reason that EOS Utility is necessary is to initiate the process. If the 5D30113.FIR and/or 5D30123.FIR is already on the card there's no need to copy it over USB.

Don't know if any of this is possible but it seems that maybe it is.

(This also assumes that the 5D3.134 ML port (https://bitbucket.org/daniel_fort/magic-lantern/pull-requests/2/update-to-5d3134-wip/diff) will someday be working.)
Title: Re: Firmware Update/Downdate?
Post by: Walter Schulz on February 12, 2017, 02:05:15 PM
Thanks for pointing out EOS Utility v3.x is doing the job, too. (I asked about 2 years ago ...)

Missing:
- "How to" for Mac users baffled by download file names indicating those files are for Windows only.
- The tutorial is useable for all cams but AFAIK only 5D3 users with firmware 1.3.3 or higher are forced to use EOS Utility. Other cams will do fine with in-cam downgrade.

If card for firmware update is formated inside cam with Q-key pressed "Format card, remove ML [Q]" card will get non-bootable and there will be no problem with cam's bootflag.
Same for formatting the card using a cardreader.
Title: Re: Firmware Update/Downdate?
Post by: Licaon_Kter on February 12, 2017, 06:29:25 PM
So looks like I'll update to M 2.0.3 after all :)
Title: Re: Firmware Update/Downdate?
Post by: dfort on February 13, 2017, 05:17:19 PM
Good points Walter. I took your suggestions and made some changes to the original post.

I suppose that most users won't be going up/down all that often except for maybe those wanting to go between 5D3.113 and 5D3.123 to get the HDMI output feature of 123 or the better performance and fewer bugs of 113. I'm messing around with trying to get a version working for 5D3.134 for those users who takes Canon's advice to always use their latest firmware and feel a little nervous rolling back in order to try out ML.

Speaking of the latest:

So looks like I'll update to M 2.0.3 after all :)

It is a very minor update and I haven't found any new bugs, though the old bugs are still there. Approve the pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/792/update-to-eosm-firmware-revision-203/diff), give it a thumbs up, smiley face, whatever to show that it is working for you. Shameless plug, I've also got a ML firmware update for the 700D (https://bitbucket.org/hudson/magic-lantern/pull-requests/813/update-to-700d115/diff). A minor firmware update isn't really very difficult to do--I can't code myself out of a paper bag and was able to do it.
Title: Re: Firmware Update/Downdate?
Post by: orhanaksan on May 07, 2018, 10:27:50 PM
hello, canon 5d mark 3 i am using.
software version 1.3.5, canon utulity program can not load the software. options not active

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fthumb.ibb.co%2FcDHUES%2FEkran_Resmi_2018_05_07_23_26_03.png&hash=b8fd843d943ab9f2c4e33f97e6aa1afd) (https://ibb.co/cDHUES)
Title: Re: Firmware Update/Downdate?
Post by: miatch on August 09, 2018, 11:50:05 PM
GREETINGS
Everyones so hasty to post link  https://www.magiclantern.fm/forum/index.php?topic=18941.0  , However, Im a 5D3 user of ML for a few years. mistakenly updated to 1.3.5, and after numerous attempts, im also unable to downgrade to 113 or 123.
I think there might be other pertinent steps not being covered, or some such issue. Some of us are still having issues. my version of eos utility will not repair either.
Any more suggestions
thanx
Title: Re: Firmware Update/Downdate?
Post by: Walter Schulz on August 10, 2018, 02:14:58 AM
http://www.catb.org/esr/faqs/smart-questions.html#beprecise
If you have problems with your EOS Utiility version it will make sense to
- mention Utility version number
- describe the problem in detail
- and the steps you have taken to make it work
Without these informations we are unable to reproduce your problem and only guessing what might have gone wrong.

I suggest to swicht cam to photo (stills) mode and mode dial M. Retry and give feedback
Title: Re: Firmware Update/Downdate?
Post by: 6D_ML on November 18, 2018, 01:14:18 AM
I'm considering purchasing 5D mkIII and installing ML. Did anyone successfully roll back firmware v1.3.5 to v1.2.3? Should I stay away from 5DmkIII running on FW 1.3.5?
Title: Re: Firmware Update/Downdate?
Post by: dfort on November 18, 2018, 06:34:54 AM
Yes, I successfully rolled back from 1.3.5 to 1.2.3 and to and from several other versions. Make sure to reset your Canon settings to factory defaults after changing the firmware. It might not be necessary but it did seem to help when I was running some tests a while back.
Title: Re: Firmware Update/Downdate?
Post by: 6D_ML on November 18, 2018, 03:42:20 PM
Yes, I successfully rolled back from 1.3.5 to 1.2.3 and to and from several other versions...
Excellent! Thanks a lot for confirmation.
Title: Re: Firmware Update/Downdate?
Post by: Kharak on April 11, 2019, 06:39:11 PM
The top post is missing pictures.
Title: Re: Firmware Update/Downdate?
Post by: Kharak on April 11, 2019, 09:01:47 PM
You are right.

Sorry about that, must be some privacy setting of mine.
Title: Re: Firmware Update/Downdate?
Post by: dfort on April 12, 2019, 02:29:00 AM
Speaking of permissions--looks like some posts are being flagged as SPAM so I missed some cries for help from a user who wanted to downgrade from 5D3.135. Basically, you need to do this via Canon EOS Utility. If the option isn't available the camera might be in Movie mode or some other mode where it doesn't allow the firmware updater to run. Put the camera in still photo, manual mode.
Title: Re: Firmware Update/Downdate?
Post by: tim.ingram3@btopenworld.c on June 04, 2019, 08:14:58 PM
Hi
I am somewhat baffled. I own a 550D and having been running ML under firmware 109 successfully for years.  Foolishly I up dated to version 110 only to find that I am now blocked from going back, downgrading. and can not run Ml any more using 109, I am even unable to run ML on an old card correctly set up.

Can some one please tell me if it is possible to downgrade and how to do it.  I am not a computer buff/geek but can follow simple instructions.
Thanks
Tim Email timingram@msn.com
Title: Re: Firmware Update/Downdate?
Post by: Walter Schulz on June 04, 2019, 08:35:02 PM
Use a spare card, format in cardreader, format in cam after and use it to downgrade.
5D3 is the only ML enabled cam affected by issue described by dfort.
Title: Re: Firmware Update/Downdate?
Post by: dfort on June 04, 2019, 10:39:11 PM
If you put both the 1.0.9 and 1.1.0 Canon firmware updaters on the same card you should be able to easily update/downdate your 550D. Note that you can get the 550D.109 Canon firmware updater from either Pelican's archive (https://pel.hu/eoscard/) or if you are nervous about getting this from a website in Hungary I also archived several updates on my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/) -- though full disclosure, I'm half-Hungarian. Look for the file named "550D Canon Firmware for Testers.zip"

Feel free to also test drive my 550D.110 port, also on the downloads page and report your findings on the pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/905/update-to-550d110/diff).
Title: Re: Firmware Update/Downdate?
Post by: Infinitymotion on September 26, 2019, 01:30:25 AM
Hello,

i did a smart thing. I installed version 1.3.6 and now i can even downdate anything if i try with the Utility there is no reaktion on the Camera/Screen. can someone help me ?

I think they dont wont me to downgrade anymore!!  :'( :'( :'( :'(
Title: Re: Firmware Update/Downdate?
Post by: Walter Schulz on September 27, 2019, 02:43:18 PM
Remove battery, remove card.
Format card using cardreader. Format again in cam.
Insert battery and cam. Connect USB and startup EOS Utility according to instruction given above.
Retry downgrade and report back.


See a1ex' reply below.
Title: Re: Firmware Update/Downdate?
Post by: Lupo on September 27, 2019, 04:12:06 PM
Hello,

i did a smart thing. I installed version 1.3.6 and now i can even downdate anything if i try with the Utility there is no reaktion on the Camera/Screen. can someone help me ?

I think they dont wont me to downgrade anymore!!  :'( :'( :'( :'(

Same problem here. I tried everything with no luck.
Title: Re: Firmware Update/Downdate?
Post by: Walter Schulz on September 27, 2019, 04:16:56 PM
If both your cams won't work with EOSUtility at all feel free to contact Canon support.
See a1ex' reply.
Title: Re: Firmware Update/Downdate?
Post by: a1ex on September 28, 2019, 10:06:29 PM
upon clicking next, the camera shows blank screen, and on the computer it shows "Press SET button to continue installing the firmware"

I believe that's a feature of the latest (1.3.6) firmware. It was introduced in response to this (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5995) recently published "Missing authorization vulnerability". I would imagine most of the camera's buttons are blocked when an USB connection is active. Don't know whether removing the cable would allow dismissing that dialog, or cause some sort of problem.

Confirmed. The firmware update can no longer be started from EOS Utility (tested with 2.14.1, but not expecting any surprises with newer versions). I can create a tool that would allow downgrading, but this would require effectively porting ML to 1.3.6 (i.e. time-consuming, but doable, and not necessarily by me).

If dfort is still around, or anyone else is willing to find the stubs and other constants for 1.3.6, I can find some time in the coming weeks in order to provide a firmware downgrading tool.

FWIW, my 5D3 is now running 1.3.6, with boot flag enabled, but without ML. Portable ROM dumper worked out of the box. My main camera (well, 2-3 pictures per month or less) is currently the 5D2, so I don't have any direct motivation to sit down and upgrade ML to latest firmware; sorry about that.
Title: Re: Firmware Update/Downdate?
Post by: dfort on September 29, 2019, 08:17:33 AM
I'm still around, though with too many projects going at the same time. I almost had 1.3.4 working properly (https://bitbucket.org/hudson/magic-lantern/pull-requests/816/update-to-5d3134/diff#comment-74839886) on the 5D3 then 1.3.5 came along and I ran into some issues (https://www.magiclantern.fm/forum/index.php?topic=18966.msg194015#msg194015). Now it looks like 1.3.6 is a one way update. Not sure I want to go there but I'd be glad to help out with some stub hunting.
Title: Re: Firmware Update/Downdate?
Post by: Danne on September 29, 2019, 08:39:52 AM
Me too, stub hunting that is...
Title: Re: Firmware Update/Downdate?
Post by: yokashin on September 29, 2019, 09:25:52 AM
https://www.slrlounge.com/canon-trying-block-magic-lantern-upcoming-5diii-firmware/
Title: Re: Firmware Update/Downdate?
Post by: Walter Schulz on September 29, 2019, 09:34:35 AM
[rant]That's the nonsensical FUD BS swept through the internet in January 2015 showing clearly people have no clue how things work and how far away from good journalistic practice most news aggregation sites are. This BS almost never got corrected.[/rant]

Quote
    Accuracy and standards for factual reporting

    • Reporters are expected to be as accurate as possible given the time allotted to story preparation and the space available and to seek reliable sources.
    • Events with a single eyewitness are reported with attribution. Events with two or more independent eyewitnesses may be reported as fact. Controversial facts are reported with attribution.
    • Independent fact-checking by another employee of the publisher is desirable.
    • Corrections are published when errors are discovered.
    • Defendants at trial are treated only as having "allegedly" committed crimes, until conviction, when their crimes are generally reported as fact (unless, that is, there is serious controversy about wrongful conviction).
    • Opinion surveys and statistical information deserve special treatment to communicate in precise terms any conclusions, to contextualize the results, and to specify accuracy, including estimated error and methodological criticism or flaws.
Source: https://en.wikipedia.org/wiki/Journalism_ethics_and_standards#Accuracy_and_standards_for_factual_reporting
Highlights by me.
Title: Re: Firmware Update/Downdate?
Post by: yokashin on September 29, 2019, 10:23:04 AM
Only now I noticed that it is news from 5 years ago ... Google found it as a novelty.
Title: Re: Firmware Update/Downdate?
Post by: Walter Schulz on September 29, 2019, 11:22:46 AM
@Danne & dfort:
Would a spare 5D3 in your hands help?
Title: Re: Firmware Update/Downdate?
Post by: Danne on September 29, 2019, 11:41:25 AM
I have a 5d3 but not moving from 1.1.3 to a locked state. I guess a rom dump from 1.3.6 is where to start. Thinking me and dfort could do this together.
Title: Re: Firmware Update/Downdate?
Post by: Walter Schulz on September 29, 2019, 11:55:15 AM
Good! A1ex has a ROM dump from a working cam.
Let us hear if there is anything to do for non-coders like me.
Title: Re: Firmware Update/Downdate?
Post by: chris_overseas on September 29, 2019, 01:19:27 PM
My time has been extremely limited for ML of late too but I'll try and help out with this as much as I can, I'm pretty familiar with stub hunting on the 5D3.
Title: Re: Firmware Update/Downdate?
Post by: Danne on September 29, 2019, 01:45:55 PM
I started out here:
https://bitbucket.org/Dannephoto/magic-lantern/commits/c4ec4869702ea1c5c086f858cf3be9624fb244e2
Title: Re: Firmware Update/Downdate?
Post by: Danne on September 29, 2019, 03:46:17 PM
A few more...
https://bitbucket.org/Dannephoto/magic-lantern/commits/dde404699bfd22f9518d33d8eaa40ff771c844ca
Title: Re: Firmware Update/Downdate?
Post by: dfort on September 29, 2019, 05:11:54 PM
Got a question via PM that's probably best answered publicly since there seems to be a few people working on this:

I disassembled firmware for both 1.1.3 and 1.3.6. I guess comparing stubs now is the way to go? Or should I dissasemble from 1.2.3 instead? hm. Guidance?

It is easier if you compare stubs with a more recent version. I've got branches for both 1.3.4 (https://bitbucket.org/daniel_fort/magic-lantern/branch/update-to-5D3.134) which is pretty much working and 1.3.5 (https://bitbucket.org/daniel_fort/magic-lantern/branch/update-to-5D.135-wip) which is pretty much finished except I don't know how to handle the change with RESTARTSTART that's required to get it working. Note that I also compared with Chris Miller's 5D3.133 branch (https://bitbucket.org/chris_miller/ml-5d3-133/branch/5D3-133) (a.k.a. chris_overseas on the forum) which is a little old but it also pretty much works.

One shortcut to finding stubs is to run contrib/stub-checker/check-stubs.py on one of the recent versions and your work in progress. Look at the offset for the stubs you found and chances are it will help get you close on the other stubs you are looking for. The hard part is looking up the constants and searching for things that need to be changed that is sprinkled all over the place. Refer to the changes in my firmware update pull requests (https://bitbucket.org/hudson/magic-lantern/pull-requests/?state=OPEN&author=%7B895de89f-cae7-4263-ac11-c167940432b1%7D) for hints.

Also note that these topics might be more appropriate for discussing porting to new firmwares:

Porting a Canon firmware update (https://www.magiclantern.fm/forum/index.php?topic=19417.0)
Canon 5D Mark III / 5D3 / Firmware 1.3.4 (https://www.magiclantern.fm/forum/index.php?topic=18966.0) (or start a new one for 1.3.6)
Title: Re: Firmware Update/Downdate?
Post by: Danne on September 29, 2019, 08:04:11 PM
Ok, I just keep going from what I began to keep momentum. I guess most of the ones I find will be valid so completed about half in stubs.S for now.
Title: Re: Firmware Update/Downdate?
Post by: Danne on September 30, 2019, 01:25:39 PM
Just finished stubs.S but there are a few TODO places that I can´t find. Hint/help needed. Following are missing atm:
Code: [Select]
NSTUB(   0x24B60,  dm_names) //todo
NSTUB(   0x25114,  task_max) //TODO
NSTUB(0xFFA02C54 - RAM_OFFSET,  post_isr_hook) // TODO (Not present in ROM1?)
NSTUB(0xFFA02C50 - RAM_OFFSET,  pre_isr_hook) // TODO (Not present in ROM1?)
NSTUB(   0x23E14,  current_task) // TODO CORRECT 0002731c?
NSTUB(     0x674,  current_interrupt) //TODO No idea what stub   
NSTUB(   0x23D00,  task_dispatch_hook) //TODO
NSTUB(0x23F4C,     terminateShutdown_save_settings) //TODO
NSTUB(0x23F50,     terminateAbort_save_settings) //TODO

Commit:
https://bitbucket.org/Dannephoto/magic-lantern/commits/de3c3c84d4ea8c9dd2893c207c5d7f11f1d86716
Title: Re: Firmware Update/Downdate?
Post by: chris_overseas on September 30, 2019, 10:14:50 PM
Here's what I found so far when comparing to 1.2.3:

NSTUB(   0x27F78,  dm_names)
NSTUB(   0x2731C,  current_task)
NSTUB(   0x27208,  task_dispatch_hook)
NSTUB(   0x2852C,  task_max)

Where did the terminateShutdown_save_settings and terminateAbort_save_settings stubs come from, 1.3.4 I guess? I don't see those in 1.2.3.
Title: Re: Firmware Update/Downdate?
Post by: Danne on September 30, 2019, 10:27:21 PM
I update from 1.1.3  8)
Anyone, feel free to join in and continue stubs and constants updating. A bit busy next couple of days.
Title: Re: Firmware Update/Downdate?
Post by: dfort on September 30, 2019, 10:38:23 PM
Where did the terminateShutdown_save_settings and terminateAbort_save_settings stubs come from, 1.3.4 I guess? I don't see those in 1.2.3.

Those are in crop_rec_4k and probably some other experimental branches.

Here's what I found for 1.3.6:

Code: [Select]
NSTUB(   0X27F78,  dm_names)
NSTUB(   0X2852C,  task_max)
NSTUB(   0x27214,  post_isr_hook)
NSTUB(   0x27210,  pre_isr_hook)
NSTUB(   0X2731C,  current_task)
NSTUB(     0x674,  current_interrupt)
NSTUB(   0x27208,  task_dispatch_hook)
NSTUB(   0x27454,  terminateShutdown_save_settings)
NSTUB(   0x27458,  terminateAbort_save_settings)
Title: Re: Firmware Update/Downdate?
Post by: Danne on September 30, 2019, 10:50:21 PM
Thanks. Added those to my stubs.S so complete now hopefully.
Title: Re: Firmware Update/Downdate?
Post by: shakenda on October 01, 2019, 01:36:50 AM
So, I had to send one of my 5d mk IIIs in for repair recently. I've been using ML for firmware 1.2.3 for years now on all three of my mk IIIs without issue. They repaired the camera, but also upgraded the firmware to 1.3.6, locking it from downgrading. So now I'm stuck with a camera that is basically useless to me for video. I'll call CPS (of which I'm a Platinum member) tomorrow to see if they will let me send it in to be downgraded, but my hopes aren't high.

It's ridiculous that they would do this. ML makes the 5D actually usable for video. I have a mk IV that I only use for stills because there's no ML for it yet. If they won't downgrade it, I'm going to have to sell this camera and I guess I'll just buy a BlackMagic Pocket 6K with EF mount instead.
Title: Re: Firmware Update/Downdate?
Post by: shakenda on October 03, 2019, 08:44:30 PM
Well, believe it or not, they did downgrade my firmware back to 1.2.3. They asked for a reason and I didn't want to say it was for ML, so I just said I've been using that version for years now on all three of my mk iii cameras bodies and feel most comfortable with it. Anyway, just FYI.
Title: Re: Firmware Update/Downdate?
Post by: Walter Schulz on October 03, 2019, 10:15:08 PM
Never heard about people getting problems with support because of ML. Most users are unaware of the bootflag (which is easily detectable by support) giving away cam being "MLed".

@a1ex: Can you add some text regarding this downgrade option into Twitter and install instructions?
Title: Re: Firmware Update/Downdate?
Post by: Lupo on October 04, 2019, 08:42:55 PM
I'm a 5D MarkIII owner/user and my knowledge ends there  :-[

Even so, if I can be helpful in anything as owner/user please let me know.
Title: Re: Firmware Update/Downdate?
Post by: Walter Schulz on October 04, 2019, 08:51:51 PM
Haven't you read? Canon CPS is able to downgrade your cam. Depending on your support status (CPS membership or not) you may be charged or not.
Title: Re: Firmware Update/Downdate?
Post by: dfort on October 16, 2019, 05:53:09 PM
Been working with Danne and critix on 5D3.136. Looks like everybody is busy lately. Same here, I really should be doing something else.

Found several stubs that were off by running the check-stubs.py script. I'm also working off my 1.3.5 port because it boots in QEMU and it shouldn't be too much of a jump going from 1.3.5 to 1.3.6. Still not working so it is probably a constant or something else that's off.

Here's the script comparing 1.2.3 against 1.3.5 and 1.3.6. Anything that looks amiss?

Code: [Select]
check-stubs.py ../../platform/5D3.123/stubs.S ~/magic-lantern_backup/platform/5D3.135/stubs.S

STUB                                   OLD           NEW     DELTA
current_interrupt                   0x00000674 -> 0x00000674 [0x000]
create_init_task                    0x00002eb8 -> 0x00002eb8 [0x000]
DryosDebugMsg                       0x00005b90 -> 0x00005be8 [0x058] [!!!]
dm_set_store_level                  0x00005ef8 -> 0x00005f50 [0x058] [!!!]
SetHPTimerAfterNow                  0x00007218 -> 0x00007270 [0x058] [!!!]
SetHPTimerNextTick                  0x00007308 -> 0x00007360 [0x058] [!!!]
create_named_semaphore              0x00008420 -> 0x00008478 [0x058] [!!!]
take_semaphore                      0x00008580 -> 0x000085d8 [0x058] [!!!]
give_semaphore                      0x0000866c -> 0x000086c4 [0x058] [!!!]
msleep                              0x00008a5c -> 0x00008ab4 [0x058] [!!!]
task_create                         0x00008b10 -> 0x00008b68 [0x058] [!!!]
GetSizeOfMaxRegion                  0x000096ec -> 0x00009744 [0x058] [!!!]
GetMemoryInformation                0x00009740 -> 0x00009798 [0x058] [!!!]
_AllocateMemory                     0x000099a0 -> 0x000099f8 [0x058] [!!!]
_FreeMemory                         0x00009d3c -> 0x00009d94 [0x058] [!!!]
CreateMemoryChunk                   0x0000a604 -> 0x0000a65c [0x058] [!!!]
GetMemoryAddressOfMemoryChunk       0x0000aba8 -> 0x0000ac00 [0x058] [!!!]
DeleteMemorySuite                   0x0000ac1c -> 0x0000ac74 [0x058] [!!!]
CreateMemorySuite                   0x0000ae24 -> 0x0000ae7c [0x058] [!!!]
AddMemoryChunk                      0x0000b100 -> 0x0000b158 [0x058] [!!!]
GetFirstChunkFromSuite              0x0000b1d0 -> 0x0000b228 [0x058] [!!!]
GetNextMemoryChunk                  0x0000b96c -> 0x0000b9c4 [0x058] [!!!]
msg_queue_create                    0x0000c1bc -> 0x0000c214 [0x058] [!!!]
CreateRecursiveLock                 0x0000c3a4 -> 0x0000c3fc [0x058] [!!!]
SetTimerAfter                       0x0000d780 -> 0x0000d7d8 [0x058] [!!!]
CancelTimer                         0x0000d980 -> 0x0000d9d8 [0x058] [!!!]
task_trampoline                     0x0000de28 -> 0x0000de80 [0x058] [!!!]
SetEDmac                            0x000125f8 -> 0x00012650 [0x058] [!!!]
ConnectWriteEDmac                   0x000126a4 -> 0x000126fc [0x058] [!!!]
ConnectReadEDmac                    0x00012768 -> 0x000127c0 [0x058] [!!!]
StartEDmac                          0x00012910 -> 0x00012968 [0x058] [!!!]
AbortEDmac                          0x00012a5c -> 0x00012ab4 [0x058] [!!!]
RegisterEDmacCompleteCBR            0x00012afc -> 0x00012b54 [0x058] [!!!]
UnregisterEDmacCompleteCBR          0x00012b38 -> 0x00012b90 [0x058] [!!!]
RegisterEDmacAbortCBR               0x00012be4 -> 0x00012c3c [0x058] [!!!]
UnregisterEDmacAbortCBR             0x00012c20 -> 0x00012c78 [0x058] [!!!]
RegisterEDmacPopCBR                 0x00012c78 -> 0x00012cd0 [0x058] [!!!]
UnregisterEDmacPopCBR               0x00012cb4 -> 0x00012d0c [0x058] [!!!]
msg_queue_receive                   0x00014680 -> 0x000146d8 [0x058] [!!!]
msg_queue_post                      0x0001486c -> 0x000148c4 [0x058] [!!!]
msg_queue_count                     0x000148ac -> 0x00014904 [0x058] [!!!]
AcquireRecursiveLock                0x000149b8 -> 0x00014a10 [0x058] [!!!]
ReleaseRecursiveLock                0x00014acc -> 0x00014b24 [0x058] [!!!]
vsnprintf                           0x00015ff4 -> 0x0001604c [0x058] [!!!]
_alloc_dma_memory                   0x00017f9c -> 0x00017ff4 [0x058] [!!!]
_free_dma_memory                    0x00017fd0 -> 0x00018028 [0x058] [!!!]
is_taskid_valid                     0x00019918 -> 0x00019970 [0x058] [!!!]
bzero32                             0x0001c448 -> 0x0001c4a0 [0x058] [!!!]
task_dispatch_hook                  0x00023d00 -> 0x00027208 [0x3508] [!!!]
pre_isr_hook                        0x00023d08 -> 0x00027210 [0x3508] [!!!]
post_isr_hook                       0x00023d0c -> 0x00027214 [0x3508] [!!!]
current_task                        0x00023e14 -> 0x0002731c [0x3508] [!!!]
gui_main_struct                     0x00024120 -> 0x00027628 [0x3508] [!!!]
dm_names                            0x00024a70 -> 0x00027f78 [0x3508] [!!!]
task_max                            0x00025024 -> 0x0002852c [0x3508] [!!!]
gui_task_list                       0x000321c8 -> 0x000356e8 [0x3520] [!!!]
cf_device_ptr                       0x00036184 -> 0x000396a4 [0x3520] [!!!]
sd_device                           0x00039960 -> 0x0003ce80 [0x3520] [!!!]
LCD_Palette                         0x00041510 -> 0x00044a30 [0x3520] [!!!]
bmp_vram_info                       0x00042d10 -> 0x00046230 [0x3520] [!!!]
additional_version                  0x00046910 -> 0x00049e30 [0x3520] [!!!]
camera_engine                       0xc0220000 -> 0xc0220000 [0x000]
cstart                              0xff0c1ca0 -> 0xff0c1ca0 [0x000] [!!!]
init_task                           0xff0c5298 -> 0xff0c5298 [0x000] [!!!]
_malloc                             0xff0c8178 -> 0xff0c8178 [0x000] [!!!]
_free                               0xff0c81d0 -> 0xff0c81d0 [0x000] [!!!]
gui_main_task                       0xff0de948 -> 0xff0de948 [0x000] [!!!]
GUI_Control                         0xff0ded1c -> 0xff0ded1c [0x000] [!!!]
gui_init_end                        0xff0df384 -> 0xff0df384 [0x000] [!!!]
SRM_AllocateMemoryResourceFor1stJob 0xff0ee3e8 -> 0xff0ee3e8 [0x000] [!!!]
SRM_FreeMemoryResourceFor1stJob     0xff0f18f8 -> 0xff0f18f8 [0x000] [!!!]
StartASIFDMAADC                     0xff10e634 -> 0xff10e634 [0x000] [!!!]
StopASIFDMAADC                      0xff10e7b0 -> 0xff10e7b0 [0x000] [!!!]
StartASIFDMADAC                     0xff10e7ec -> 0xff10e7ec [0x000] [!!!]
StopASIFDMADAC                      0xff10e8c4 -> 0xff10e8c4 [0x000] [!!!]
SetNextASIFADCBuffer                0xff10ed68 -> 0xff10ed68 [0x000] [!!!]
SetNextASIFDACBuffer                0xff10ee1c -> 0xff10ee1c [0x000] [!!!]
prop_register_slave                 0xff12301c -> 0xff12301c [0x000] [!!!]
_prop_request_change                0xff123210 -> 0xff123210 [0x000] [!!!]
prop_deliver                        0xff1237cc -> 0xff1237cc [0x000] [!!!]
_prop_cleanup                       0xff123898 -> 0xff123898 [0x000] [!!!]
LoadCalendarFromRTC                 0xff135fd4 -> 0xff135fd4 [0x000] [!!!]
_audio_ic_write                     0xff136f68 -> 0xff136f68 [0x000] [!!!]
_audio_ic_read                      0xff137020 -> 0xff137020 [0x000] [!!!]
SetAudioVolumeOut                   0xff137168 -> 0xff137168 [0x000] [!!!]
PowerAudioOutput                    0xff1379d0 -> 0xff1379d0 [0x000] [!!!]
SetSamplingRate                     0xff137a68 -> 0xff137a68 [0x000] [!!!]
call                                0xff13b750 -> 0xff13b750 [0x000] [!!!]
AllocateMemoryResource              0xff13c1f8 -> 0xff13c1f8 [0x000] [!!!]
AllocateContinuousMemoryResource    0xff13c244 -> 0xff13c244 [0x000] [!!!]
FreeMemoryResource                  0xff13c35c -> 0xff13c35c [0x000] [!!!]
SetGUIRequestMode                   0xff18b6cc -> 0xff18b6cc [0x000] [!!!]
gui_massive_event_loop              0xff1a7bbc -> 0xff1a7d18 [0x15c]
GUI_SetRollingPitchingLevelStatus   0xff2763a4 -> 0xff276500 [0x15c]
_EngDrvOut                          0xff290c80 -> 0xff290ddc [0x15c]
shamem_read                         0xff290d1c -> 0xff290e78 [0x15c]
_engio_write                        0xff290f98 -> 0xff2910f4 [0x15c]
CreateResLockEntry                  0xff294ef0 -> 0xff29504c [0x15c]
LockEngineResources                 0xff2953b8 -> 0xff295514 [0x15c]
UnLockEngineResources               0xff29555c -> 0xff2956b8 [0x15c]
_FIO_OpenFile                       0xff30e3b4 -> 0xff30e524 [0x170]
_FIO_CreateFile                     0xff30e470 -> 0xff30e5e0 [0x170]
_FIO_RemoveFile                     0xff30e51c -> 0xff30e68c [0x170]
_FIO_ReadFile                       0xff30e5c4 -> 0xff30e734 [0x170]
FIO_SeekSkipFile                    0xff30e674 -> 0xff30e7e4 [0x170]
_FIO_WriteFile                      0xff30e764 -> 0xff30e8d4 [0x170]
FIO_CloseFile                       0xff30e814 -> 0xff30e984 [0x170]
_FIO_GetFileSize                    0xff30e990 -> 0xff30eb00 [0x170]
_FIO_CreateDirectory                0xff30f070 -> 0xff30f1e0 [0x170]
_FIO_FindFirstEx                    0xff30f638 -> 0xff30f7a8 [0x170]
FIO_FindNextEx                      0xff30f72c -> 0xff30f89c [0x170]
FIO_FindClose                       0xff30f80c -> 0xff30f97c [0x170]
dialog_set_property_str             0xff35921c -> 0xff35937c [0x160]
PlayMain_handler                    0xff36deb8 -> 0xff36e018 [0x160]
ptp_register_handler                0xff3fde4c -> 0xff3fe148 [0x2fc]
dialog_redraw                       0xff456524 -> 0xff456820 [0x2fc]
FSUunMountDevice                    0xff48b788 -> 0xff48ba84 [0x2fc]
ErrForCamera_handler                0xff4a7318 -> 0xff4a7600 [0x2e8]
CancelDateTimer                     0xff4aeddc -> 0xff4af104 [0x328]
HideUnaviFeedBack_maybe             0xff4b62e0 -> 0xff4b6608 [0x328]
LiveViewApp_handler                 0xff4ba780 -> 0xff4baaa8 [0x328]
ShootOlcApp_handler                 0xff4c13a4 -> 0xff4c16cc [0x328]
PlayMovieGuideApp_handler           0xff4d6494 -> 0xff4d67c0 [0x32c]
fsuDecodePartitionTable             0xff5c5e0c -> 0xff5c6140 [0x334]
ErrCardForLVApp_handler             0xff626ea0 -> 0xff627290 [0x3f0]
LiveViewWbApp_handler               0xff62e43c -> 0xff62e82c [0x3f0]
LiveViewLevelApp_handler            0xff663ce8 -> 0xff6640e0 [0x3f8]

Code: [Select]
check-stubs.py ../../platform/5D3.123/stubs.S ../../platform/5D3.136/stubs.S

STUB                                   OLD           NEW     DELTA
current_interrupt                   0x00000674 -> 0x00000674 [0x000]
create_init_task                    0x00002eb8 -> 0x00002eb8 [0x000]
DryosDebugMsg                       0x00005b90 -> 0x00005be8 [0x058] [!!!]
dm_set_store_level                  0x00005ef8 -> 0x00005f50 [0x058] [!!!]
SetHPTimerAfterNow                  0x00007218 -> 0x00007270 [0x058] [!!!]
SetHPTimerNextTick                  0x00007308 -> 0x00007360 [0x058] [!!!]
create_named_semaphore              0x00008420 -> 0x00008478 [0x058] [!!!]
take_semaphore                      0x00008580 -> 0x000085d8 [0x058] [!!!]
give_semaphore                      0x0000866c -> 0x000086c4 [0x058] [!!!]
msleep                              0x00008a5c -> 0x00008ab4 [0x058] [!!!]
task_create                         0x00008b10 -> 0x00008b68 [0x058] [!!!]
GetSizeOfMaxRegion                  0x000096ec -> 0x00009744 [0x058] [!!!]
GetMemoryInformation                0x00009740 -> 0x00009798 [0x058] [!!!]
_AllocateMemory                     0x000099a0 -> 0x000099f8 [0x058] [!!!]
_FreeMemory                         0x00009d3c -> 0x00009d94 [0x058] [!!!]
CreateMemoryChunk                   0x0000a604 -> 0x0000a65c [0x058] [!!!]
GetMemoryAddressOfMemoryChunk       0x0000aba8 -> 0x0000ac00 [0x058] [!!!]
DeleteMemorySuite                   0x0000ac1c -> 0x0000ac74 [0x058] [!!!]
CreateMemorySuite                   0x0000ae24 -> 0x0000ae7c [0x058] [!!!]
AddMemoryChunk                      0x0000b100 -> 0x0000b158 [0x058] [!!!]
GetFirstChunkFromSuite              0x0000b1d0 -> 0x0000b228 [0x058] [!!!]
GetNextMemoryChunk                  0x0000b96c -> 0x0000b9c4 [0x058] [!!!]
msg_queue_create                    0x0000c1bc -> 0x0000c214 [0x058] [!!!]
CreateRecursiveLock                 0x0000c3a4 -> 0x0000c3fc [0x058] [!!!]
SetTimerAfter                       0x0000d780 -> 0x0000d7d8 [0x058] [!!!]
CancelTimer                         0x0000d980 -> 0x0000d9d8 [0x058] [!!!]
task_trampoline                     0x0000de28 -> 0x0000de80 [0x058] [!!!]
SetEDmac                            0x000125f8 -> 0x00012650 [0x058] [!!!]
ConnectWriteEDmac                   0x000126a4 -> 0x000126fc [0x058] [!!!]
ConnectReadEDmac                    0x00012768 -> 0x000127c0 [0x058] [!!!]
StartEDmac                          0x00012910 -> 0x00012968 [0x058] [!!!]
AbortEDmac                          0x00012a5c -> 0x00012ab4 [0x058] [!!!]
RegisterEDmacCompleteCBR            0x00012afc -> 0x00012b54 [0x058] [!!!]
UnregisterEDmacCompleteCBR          0x00012b38 -> 0x00012b90 [0x058] [!!!]
RegisterEDmacAbortCBR               0x00012be4 -> 0x00012c3c [0x058] [!!!]
UnregisterEDmacAbortCBR             0x00012c20 -> 0x00012c78 [0x058] [!!!]
RegisterEDmacPopCBR                 0x00012c78 -> 0x00012cd0 [0x058] [!!!]
UnregisterEDmacPopCBR               0x00012cb4 -> 0x00012d0c [0x058] [!!!]
msg_queue_receive                   0x00014680 -> 0x000146d8 [0x058] [!!!]
msg_queue_post                      0x0001486c -> 0x000148c4 [0x058] [!!!]
msg_queue_count                     0x000148ac -> 0x00014904 [0x058] [!!!]
AcquireRecursiveLock                0x000149b8 -> 0x00014a10 [0x058] [!!!]
ReleaseRecursiveLock                0x00014acc -> 0x00014b24 [0x058] [!!!]
vsnprintf                           0x00015ff4 -> 0x0001604c [0x058] [!!!]
_alloc_dma_memory                   0x00017f9c -> 0x00017ff4 [0x058] [!!!]
_free_dma_memory                    0x00017fd0 -> 0x00018028 [0x058] [!!!]
is_taskid_valid                     0x00019918 -> 0x00019970 [0x058] [!!!]
bzero32                             0x0001c448 -> 0x0001c4a0 [0x058] [!!!]
task_dispatch_hook                  0x00023d00 -> 0x00027208 [0x3508] [!!!]
pre_isr_hook                        0x00023d08 -> 0x00027210 [0x3508] [!!!]
post_isr_hook                       0x00023d0c -> 0x00027214 [0x3508] [!!!]
current_task                        0x00023e14 -> 0x0002731c [0x3508] [!!!]
gui_main_struct                     0x00024120 -> 0x00027628 [0x3508] [!!!]
dm_names                            0x00024a70 -> 0x00027f78 [0x3508] [!!!]
task_max                            0x00025024 -> 0x0002852c [0x3508] [!!!]
gui_task_list                       0x000321c8 -> 0x000356e8 [0x3520] [!!!]
cf_device_ptr                       0x00036184 -> 0x000396a4 [0x3520] [!!!]
sd_device                           0x00039960 -> 0x0003ce80 [0x3520] [!!!]
LCD_Palette                         0x00041510 -> 0x00044a30 [0x3520] [!!!]
bmp_vram_info                       0x00042d10 -> 0x00046230 [0x3520] [!!!]
additional_version                  0x00046910 -> 0x00049e30 [0x3520] [!!!]
camera_engine                       0xc0220000 -> 0xc0220000 [0x000]
cstart                              0xff0c1ca0 -> 0xff0c1ca0 [0x000] [!!!]
init_task                           0xff0c5298 -> 0xff0c5298 [0x000] [!!!]
_malloc                             0xff0c8178 -> 0xff0c8178 [0x000] [!!!]
_free                               0xff0c81d0 -> 0xff0c81d0 [0x000] [!!!]
gui_main_task                       0xff0de948 -> 0xff0de948 [0x000] [!!!]
GUI_Control                         0xff0ded1c -> 0xff0ded1c [0x000] [!!!]
gui_init_end                        0xff0df384 -> 0xff0df384 [0x000] [!!!]
SRM_AllocateMemoryResourceFor1stJob 0xff0ee3e8 -> 0xff0ee3e8 [0x000] [!!!]
SRM_FreeMemoryResourceFor1stJob     0xff0f18f8 -> 0xff0f18f8 [0x000] [!!!]
StartASIFDMAADC                     0xff10e634 -> 0xff10e634 [0x000] [!!!]
StopASIFDMAADC                      0xff10e7b0 -> 0xff10e7b0 [0x000] [!!!]
StartASIFDMADAC                     0xff10e7ec -> 0xff10e7ec [0x000] [!!!]
StopASIFDMADAC                      0xff10e8c4 -> 0xff10e8c4 [0x000] [!!!]
SetNextASIFADCBuffer                0xff10ed68 -> 0xff10ed68 [0x000] [!!!]
SetNextASIFDACBuffer                0xff10ee1c -> 0xff10ee1c [0x000] [!!!]
prop_register_slave                 0xff12301c -> 0xff12301c [0x000] [!!!]
_prop_request_change                0xff123210 -> 0xff123210 [0x000] [!!!]
prop_deliver                        0xff1237cc -> 0xff1237cc [0x000] [!!!]
_prop_cleanup                       0xff123898 -> 0xff123898 [0x000] [!!!]
LoadCalendarFromRTC                 0xff135fd4 -> 0xff135fd4 [0x000] [!!!]
_audio_ic_write                     0xff136f68 -> 0xff136f68 [0x000] [!!!]
_audio_ic_read                      0xff137020 -> 0xff137020 [0x000] [!!!]
SetAudioVolumeOut                   0xff137168 -> 0xff137168 [0x000] [!!!]
PowerAudioOutput                    0xff1379d0 -> 0xff1379d0 [0x000] [!!!]
SetSamplingRate                     0xff137a68 -> 0xff137a68 [0x000] [!!!]
call                                0xff13b750 -> 0xff13b750 [0x000] [!!!]
AllocateMemoryResource              0xff13c1f8 -> 0xff13c1f8 [0x000] [!!!]
AllocateContinuousMemoryResource    0xff13c244 -> 0xff13c244 [0x000] [!!!]
FreeMemoryResource                  0xff13c35c -> 0xff13c35c [0x000] [!!!]
SetGUIRequestMode                   0xff18b6cc -> 0xff18b6cc [0x000] [!!!]
gui_massive_event_loop              0xff1a7bbc -> 0xff1a7d18 [0x15c]
GUI_SetRollingPitchingLevelStatus   0xff2763a4 -> 0xff2764d0 [0x12c]
_EngDrvOut                          0xff290c80 -> 0xff290ec0 [0x240]
shamem_read                         0xff290d1c -> 0xff290f5c [0x240]
_engio_write                        0xff290f98 -> 0xff2911d8 [0x240]
CreateResLockEntry                  0xff294ef0 -> 0xff295130 [0x240]
LockEngineResources                 0xff2953b8 -> 0xff2955f8 [0x240]
UnLockEngineResources               0xff29555c -> 0xff29579c [0x240]
_FIO_OpenFile                       0xff30e3b4 -> 0xff30e608 [0x254]
_FIO_CreateFile                     0xff30e470 -> 0xff30e6c4 [0x254]
_FIO_RemoveFile                     0xff30e51c -> 0xff30e770 [0x254]
_FIO_ReadFile                       0xff30e5c4 -> 0xff30e818 [0x254]
FIO_SeekSkipFile                    0xff30e674 -> 0xff30e8c8 [0x254]
_FIO_WriteFile                      0xff30e764 -> 0xff30e9b8 [0x254]
FIO_CloseFile                       0xff30e814 -> 0xff30ea68 [0x254]
_FIO_GetFileSize                    0xff30e990 -> 0xff30ebe4 [0x254]
_FIO_CreateDirectory                0xff30f070 -> 0xff30f2c4 [0x254]
_FIO_FindFirstEx                    0xff30f638 -> 0xff30f88c [0x254]
FIO_FindNextEx                      0xff30f72c -> 0xff30f980 [0x254]
FIO_FindClose                       0xff30f80c -> 0xff30fa60 [0x254]
dialog_set_property_str             0xff35921c -> 0xff359460 [0x244]
PlayMain_handler                    0xff36deb8 -> 0xff36e0fc [0x244]
ptp_register_handler                0xff3fde4c -> 0xff3fe22c [0x3e0]
dialog_redraw                       0xff456524 -> 0xff456904 [0x3e0]
FSUunMountDevice                    0xff48b788 -> 0xff48bb68 [0x3e0]
ErrForCamera_handler                0xff4a7318 -> 0xff4a76e4 [0x3cc]
CancelDateTimer                     0xff4aeddc -> 0xff4af1e8 [0x40c]
HideUnaviFeedBack_maybe             0xff4b62e0 -> 0xff4b66ec [0x40c]
LiveViewApp_handler                 0xff4ba780 -> 0xff4bab8c [0x40c]
ShootOlcApp_handler                 0xff4c13a4 -> 0xff4c17b0 [0x40c]
PlayMovieGuideApp_handler           0xff4d6494 -> 0xff4d68a4 [0x410]
fsuDecodePartitionTable             0xff5c5e0c -> 0xff5c6224 [0x418]
ErrCardForLVApp_handler             0xff626ea0 -> 0xff627374 [0x4d4]
LiveViewWbApp_handler               0xff62e43c -> 0xff62e910 [0x4d4]
LiveViewLevelApp_handler            0xff663ce8 -> 0xff6641c4 [0x4dc]

https://bitbucket.org/daniel_fort/magic-lantern/branch/update-to-5D.136-wip
Title: Re: Firmware Update/Downdate?
Post by: dfort on October 16, 2019, 08:03:16 PM
Some progress - minimal working:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Flive.staticflickr.com%2F65535%2F48909321908_f5586c321a.jpg&hash=9836e364a31302a409cde0aa4155c5eb) (https://flic.kr/p/2hvX4qQ)

Got the firmware signature - yay!

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Flive.staticflickr.com%2F65535%2F48909321828_21844f16d8.jpg&hash=ab38cdaf322b909de257ae57f1125ac2) (https://flic.kr/p/2hvX4ps)

Still rough around the edges, haven't been able to get into the ML menus and it crashes but it is a start:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Flive.staticflickr.com%2F65535%2F48909854436_1372185815.jpg&hash=5b92a70e6872b57062a9fd9029b7ac48) (https://flic.kr/p/2hvZMJm)
Title: Re: Firmware Update/Downdate?
Post by: DeafEyeJedi on October 16, 2019, 08:42:25 PM
That’s some progress. Amazing work @dfort!
Title: Re: Firmware Update/Downdate?
Post by: GullRaDriel on October 17, 2019, 05:44:44 PM
Yes, good job !
Title: Re: Firmware Update/Downdate?
Post by: Philbo on March 01, 2020, 06:02:11 AM
Hey guys, I'm a noob here and in the 5D3/1.3.6 club.  Just seeing if there is any progress running ML on 1.3.6, I would dearly
love to run ML.
Title: Re: Firmware Update/Downdate?
Post by: dfort on March 01, 2020, 04:21:49 PM
Just seeing if there is any progress running ML on 1.3.6, I would dearly
love to run ML.

A few of us have tried. Here's my attempt:
https://bitbucket.org/daniel_fort/magic-lantern/branch/update-to-5D.136-wip

Note added to first post of this discussion (https://www.magiclantern.fm/forum/index.php?topic=18941.0) because several people have been asking this same question.
Title: Re: Firmware Update/Downdate?
Post by: Joshiewowa on March 02, 2020, 09:32:24 AM
I've got hardware with 1.3.6, anything I can help with?
Title: Re: Firmware Update/Downdate?
Post by: Danne on March 02, 2020, 10:40:14 AM
Go through this forum post from start and try to understand the difficulties around firmware upgrade then proceed.
Title: Re: Firmware Update/Downdate?
Post by: Philbo on March 02, 2020, 10:51:30 AM
I wish I could somehow contribute, I just know not one thing about coding, firmware, stubs or anything like that.  It seems that it's a complex process that will take time that people can sometimes generously donate.  Might just have to swallow the fact that I can only record 720p @ 60fps (definitely a first world problem, I get it).  :)

Thank you to anyone who has or is going to donate their time to this.