Menu

Show posts

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

Show posts Menu

Messages - ty66

#1
General Development / Re: How to disable Canon errors
August 02, 2013, 11:09:19 PM
Quote from: nanomad on August 02, 2013, 05:54:45 PM
Can you take a screenshot of said error?
This is the error in movie mode. In photo mode, without live view, the error text is replaced with "Camera internal temperature is becoming too high. Can't shoot"
http://i.imgur.com/MJNb1k8.jpg

While this error is active I can't enter to ML menu, but if am already in ML menu I can see CMOS temperature value. Usually it jumps 90 to 150-160 to 240.
http://i.imgur.com/L5yVeIn.jpg
#2
General Development / How to disable Canon errors
August 02, 2013, 04:36:14 PM
Hello!

My 7D has broken cmos temperature censor which will time to time report some extreme low and high values, so I get "Camera internal temperature is becoming too high. Can't shoot" error (PS: this error does not have ERR number). Is there some known way to get around Canon errors?
#3
Quote from: dbals on July 17, 2013, 03:27:40 PM
I tried this myself- could follow this tutorial (http://www.magiclantern.fm/forum/index.php?topic=6783.0) and generate the unified (all camera version) but not the 7D- would just give me and error 2.  Still don't understand how to apply the alpha2 tag mentioned before
I'am not 100% sure but I must have used "hg clone -r ML-7D-Alpha2 https://bitbucket.org/hudson/magic-lantern" to check out code. Anyway ML-7D-Alpha2 is tag name you want to use to check out the code from server.
#4
Quote from: pfluger on July 13, 2013, 10:14:44 PM
Did you have to build the autoexec version yourself or is it somewhere available for download?
It's not available officially so I did not search. alpha2 tag is compiling without any problems but latest code had some problems few weeks ago.
There is tons of guides and even virtual machine images where everything is pre-installed, so you have to just check out the alpha2 tag code and run make 7D command.
#5
Quote from: tonybeccar on July 13, 2013, 01:07:06 AM
So, now you are working just fine with an autobootable version of ML A2 in your 7D right??? Have you experienced any kind of problems??

It's running fine. You can also use non bootable CF card to run the official alpha 2 version instead of autoexec/autoboot version.
#6
Just follow the info from Google group http://groups.google.com/group/ml-devel/browse_thread/thread/9636782a8f25bb7d

Download patch.bsdiff from google group, bsdiff program to run the patch and 1.2.3 version of Canon 7D firmware. Then apply patch.bsdiff to v1.2.3 Canon 7D firmware file. I wish there would be some MD5 sums to verify the patched file but unfortunately there is not.

Then install EOS utility 2.10.2.0 and flash the patched 1.2.3 version. As said previously it just runs hacked code which will dump the memory to CF card and enable bootflags. It will not downgrade your firmware to 1.2.3.

I don't know the internals behind this patch so I can't comment on risk factor but I suggest you to be prepared (mentally and financially) to brick your camera. I know I was, I needed autoboot just that much.
#7
There is no need to downgrade firmware to enable bootflags. Dumper firmware is just a hacked/patch version of regular/official firmware image. You need to run it just like any other firmware update/downgrade but it will not actually downgrade nor update your camera firmware. Instead it just hacked code which will dump memory to CF card and enable bootflags.
Look http://magiclantern.wikia.com/wiki/7D_support#Before_g3gg0.27s_hack

Take a note that you need to use older version of EOS utility to run older versions of firmware images or you will get firmware image not supported or something like this error. I did use EOS utility 2.10.2.0
#8
Quote from: Pelican on June 27, 2013, 12:23:42 PM
Yes.
No.
Thanks. Got it booting. Actually there is no need to downgrade firmware. Just run patched dumper firmware update on a camera with v2.0.3 firmware and that's all, you're ready to boot autoexec.bin. 7D alpha2 tag is compiling without any problems.
#9
Can't you downgrade firmware only to enable bootflags with dumper firmware and then upgrade firmware back to current version and then use ML alpha2 autoexec.bin. Or will firmware upgrade reset bootflags?
#10
autoexec.bin file should be generated by default when compiling ML. Unfortunately there is no bootdisk_enable stubs in 7d platform code.
#11
+1 for autoboot version. My 7d is half broken (without any sort of AF), so I relay heavily on ML focus aids in photo mode.

Could I enable BOOTDISK flag on 7d with magic.disable_bootdiskf = 0 "like" operation under fir version of ML and then compile my own autoexec.bin using https://bitbucket.org/hudson/magic-lantern/src code?