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 - EVVK

#1
Camera-specific Development / Re: Canon EOS M
December 04, 2014, 10:24:30 PM
feureau, if factory reset doesn't work. Try re-flashing the official firmware update (again) even if you already are on that version.

http://www.canon-europe.com/Support/Consumer_Products/products/cameras/Digital_SLR/EOS_M.aspx?type=firmware
#2
@arcadio: Your above shutter bug doesn't seem to work 100%.

For me it indeed works first time straight after install. But this is nothing new, I've had luck to get it working 25times in the row, where I thought I had something. But then suddenly the bug was back again. It's random.

Anyway, add to your procedure that you take take two photos and then Press the power-button. Wait few seconds then press on again.  The bug is back. Almost always for me. (11-22 lens and sensor cleaning off). However If I wait 2 minutes my luck is better and it usually works.

Maybe there is a soft shutdown pattern.
#3
Quote from: kosmarnik on August 01, 2014, 05:56:14 PM
...just focuses but won't fire with a full press.
Any ideas?
Using a sdcard without ML it works fine.
I can post dumps/logs later when I get home.
Hey, welcome!

It's called shutter-bug, just browse in previous posts. It appears with EF-M zoom lenses, not fixed (22mm) primes or with EF-adapter. There are atleast two known? work-arounds when it appears, either quickly reboot your camera by pressing powerbutton twice, or just twist the lens and reseat it again while the camera is on.

I'm not sure if we still have any clues what triggers this bug, as it appears mostly to be random. Sometimes it wierdly seems to work fine for a while in a row.
#4
Ok , Sorry  :-[
No idea on the actual code calling those, but those few that were marked with questionmarks in the  were empty in EOSM.202/stubs.S . Just tried to help out.
#5
Tried to figure out some new stubs for EOSM.202 . However I would advice someone checks/verifys them as I haven't had any prior experience on this.


NSTUB(FF555B80,  StartPlayProtectGuideApp)
NSTUB(FF5557BC,  StopPlayProtectGuideApp)

NSTUB(FF4E5E2C,  MirrorDisplay)
NSTUB(FF4E5E8C,  NormalDisplay)
NSTUB(FF4E5E5C,  ReverseDisplay)

NSTUB(FF2C17B8,  EngDrvOut)

NSTUB(FF0D7918,  gui_change_shoot_type_post)    ; or is it FF0D7904 ?
NSTUB(FF0D7830,  gui_change_mode)

NSTUB(FF1B524C,  GUI_SetLvMode)
NSTUB(FF134A8C,  SetAudioVolumeIn)

NSTUB(FF2C0474,  mvrSetFullHDOptSize)
NSTUB(FF2C0658,  mvrSetGopOptSizeFULLHD)
#6
Reverse Engineering / Re: Tutorial: finding stubs
June 06, 2014, 12:45:42 AM
Great guide! Thanks. Maybe it should be wikified as well? :)

Is there anyway to extract ROM1.BIN from vendors firmware update (FIR) file?
data_body from dissect_fw3 seems different/wrong.

I'd really want to compare the .dis file for other models to get some confidence if I've got this right.
#7
Crap, seems like so, just had a good luck the first 5 runs, it's been a while when I last tried the nightlys. Anyway, I now get the shutter bug more frequently again, if not every time.

Has anyone been doing any analysis of the lenses? Similar to this:
http://pickandplace.wordpress.com/2011/10/05/canon-ef-s-protocol-and-electronic-follow-focus/
Maybe it could reveal what differs the zoom lenses. :-\
#8
With older nightlys the shutter bug appeared also after warm boots, which seems to be fixed now, it seems to be a lot better.

However, it still appears with cold boots (re-seat battery and press power). After that I needed to re-seat the lens to get the shutter working again. (11-22 and 18-55 behaves the same). But like I mentioned it now persists warm-boots, so it's a lot better, and seems like we are headed in the right direction.

Needs more testing...
#9
Tragic Lantern / Re: EOS M Alpha shutter-bug discussion
October 27, 2013, 09:31:01 PM
Yes, the bootflag was left Enabled on the camera when this occured.

And yes, we could it low-level format, (as the camera does). I'm not so used to that term cause when talking about low-level formating on harddrives that is on a totally other level which allows settings sector sizes and stuff, the true term in my ears is even lower. ;) This is just about erasing the whole memorycard, partitions and filesystems. (including the flags that for example EOSCard sets)
#10
Tragic Lantern / Re: EOS M Alpha shutter-bug discussion
October 27, 2013, 08:35:24 PM
Quote from: Malakai on October 21, 2013, 11:51:51 AM
It only occurs when ML/TL is installed or running.

FALSE
I've was about to miss one of lifes most important moments at the hospital due the shutter bug. My card was totally overwriten with DD /RAW.  I thought I was ready to go with plain Canon firmware but no.. Shutter bug apperead! Luckily it was just to re-seat the lens but still missed few seconds of one important moment.

I did not have any ML files left on the memory card nor the special partitiontables . The memorycard was 100% clean and totally re-partitioned with new filesystem.

The only way I was able to get rid of shutter bug was to flash Canons firmware and do a reset of of all camera settings like I wrote here:
http://www.magiclantern.fm/forum/index.php?topic=8347.msg82215#msg82215

The question is is it enough to just disable the bootflag or to do a reset of the settings? If it's the bootflag or some other leftover from previous use of  ML.
#11
Tragic Lantern / Re: EOS M Alpha shutter-bug discussion
October 21, 2013, 10:05:37 PM
Just thinking...Is there any room for anything that could be tried with the FIR installer? If the bootflag could be set in some other way?
#12
Tragic Lantern / Re: EOS M Alpha shutter-bug discussion
October 11, 2013, 08:23:04 AM
Quote from: maxotics on October 10, 2013, 11:14:59 PM
Hi EVVK, can you give some specific step-by-step instructions, thanks!  (there are so many places one could misunderstand).

Sure, I'm mostly written this from memory.. but it should be almost correct:

Uninstall/reverting back to known working state:
1) Put camera in M-mode and flash the the FIR file that was included with ML.
2) Disable bootflag with the jog dial as instructed.
3) Do a low-level format in the camera.
4) Download Windows version of the firmware from Canons site:
http://www.canon.co.uk/Support/Consumer_Products/products/cameras/Digital_SLR/EOS_M.aspx
5) Put EOSM1202.FIR from the ZIP in the clean memorycard and flash it the same way in M mode.
4) Go to menu (Still in M-mode) and "Clear settings", all camera settings should be enough (c.fn not needed).
5) Done.

Install ML and re-producing the shutter bug:
1) Use EOSCard or other methods which you prefer to set the bootflags to the card. (I use Ubuntu so can't really give any guidance here)
2) Download EOSM labeled ML from http://ml.bot-fly.com/ and extract the files to card.
2) Put the card back in the camera and flash the ML FIR file in M mode, like FW update
3) Reboot the camera, (auto)load all the ML modules. No modules needed with Oct 10 build to reproduce the issue.
4) Shut down the camera, and remove the battery
5) Insert either EF-M 11-22mm or 18-55mm lens if you are not using those already and start up the camera again.
6) Get focus and press the shutter button. Either it's working or not. Repeat few times again from step 4.
7) have a coffee
8.) You could also try from step 4 with the EF-M 22mm or EF to EF-M adapter with other lenses just to see that it's still working from cold boot, any lens will work with a how-swap.
#13
Tragic Lantern / Re: EOS M Alpha shutter-bug discussion
October 10, 2013, 10:58:23 PM
Malakai and a1ex, I've mentioned it few times now in both threads. But I had to re-flash Canons original firmware to get rid of the shutter bug. Also factory reset settings to get rid of some wierd colors in liveview during bursts.

My memorycard was totally formatted and clean when I still had the bug. So don't just blindly look at what is currently on your card.
#14
Tragic Lantern / Re: EOS M Alpha shutter-bug discussion
October 06, 2013, 05:45:35 PM
Quote from: Malakai on October 06, 2013, 02:17:55 PM
The point of this thread is to discuss and possibly find the cause of the shutter bug while ML/TL is installed and running. The bug comes with ML/TL and by removing it you remove the bug.
If you just re-read everything, I had the bug with a clean memory card, it's a left over from ML. The pure Canon firmware doesn't produce the shutter bug so it's related to ML, I just had to back off everything back to stock to get it all clean of the issues that were from use of ML, why complain, I'm just trying to feed information here! Which could determine hints of which wrong addresses are altered by ML.
#15
Tragic Lantern / Re: EOS M Alpha shutter-bug discussion
October 06, 2013, 12:42:45 PM
No, the point was to get rid of the shutter bug and restore the whole camera like it came from factory.

Anyway, made the memory card bootable once again, and only put that autoexec.bin in the root, still works like it should. But how can I tell if it really executed that file?
#16
Tragic Lantern / Re: EOS M Alpha shutter-bug discussion
October 04, 2013, 08:47:39 PM
No shutter bug after even more testing...

However I shot something with the 11-22mm lens I get some weird color distortion, randomly about 2/10 times it shows green or pinkish in LiveView between bursts in M-mode, I don't think it should be there, it is more like something that could appear with ML.

The images that were saved were OK, only appeared in LiveView for split seconds...

EDIT: Restored(?) "all camera settings" or whatever it's called, have Swedish language here so the actual words could differ. (Did NOT restore C.Fn) , and after this I do NOT get any weird colors in LiveView anymore. So everything seems to be back normal, like it came from the factory. :)
#17
Tragic Lantern / Re: EOS M Alpha shutter-bug discussion
October 04, 2013, 08:33:56 PM
I went in in the upgrade mode and Disabled Bootflag with ML FIR files. Booted and did a low-level/slow format on the camera. Put the official firmware update there and flashed firmware. Seems to work alright now, but it probably needs deeper testing to verify that the bug is totally gone.

Next step would probably be to completly restore all camera settings to factory I guess. But it seems to be working for me at the moment.
#18
Tragic Lantern / Re: EOS M Alpha shutter-bug discussion
October 04, 2013, 08:15:00 PM
Yes, but I got the shutter bug without any files at all on the memory card. Totally formated and repartitioned the card. So I wonder If it's something else bootflags or something that has been poking in wrong addresses in earlier versions.

What I haven't tried yet is to re-flash the official canon firmware once again.
#19
Tragic Lantern / Re: Tragic Lantern for EOS M
September 27, 2013, 02:42:39 PM
I didn't uninstall or unset any bootflags. I had the flashing green LED in some point also but was desperate to get the camera working, I believe here I used GParted in Ubuntu to completely do a new partition table on the card, then I was able to boot the camera correctly without ML and do the quick format.
#20
Tragic Lantern / Re: Tragic Lantern for EOS M
September 27, 2013, 11:47:28 AM
Not so updated on the shutter bug, but I observed something new. I was running Sept22 version for quite some time. Then I had to wipe my memory card to rescue a laptop, wrote over the memorycard with a dd/raw image, so ML and all partition tables were wiped. Later on I just created a MBR/MSDOS partition with GParted and used the camera to quick format the partition.

So I should not have ML left on the card anymore? But I still have the the shutter bug and have to re-seat the lens to get it working.
#21
Tragic Lantern / Re: Tragic Lantern for EOS M
September 15, 2013, 09:45:18 AM
I guess it is too much free time?  ;)

Reminds me of a small company that had 4 project leaders/managers and 1 developer. The 4 had meetings every day what the developer could do, without letting the developer into the meetings to say his word.
So you can imagine the board meetings all day long: - Wish he could implement this new .... feature if he only had time.
So 4 barely technical people trying to come up with plans how to take over the world with the company. The ratio between planning and implementing wasn't obviously working, it was only slowing down but they where to blind to see that. That company would have crashed if the developer decided to quit his job.

Anyway with the above story in mind, I wouldn't imagine anyone wants something bad to this project, everyone want to help. Maybe Gary has good insight enough and could maintain like the EOSM wiki page/documentation for example. This thread would have been a lot smaller if the documentation was up to date, since this thread is the only source for up to date information.

It is too easy to bounce (stupid & already answered) questions here, I'm not referring to anyone personally here just my personal general observations of this thread.
#22
Tragic Lantern / Re: Tragic Lantern for EOS M
September 09, 2013, 09:17:07 PM
Disabling IS in the menu does not seem to make any difference to me att all.
Even if it's left off and the camera is cold booted the bug is still there.
#23
Tragic Lantern / Re: Tragic Lantern for EOS M
September 09, 2013, 06:55:42 PM
For me.. the shutter bug only appears with the two EF-M lenses 18-55 and 11-22.

EF 70-200 IS F4 and few and cheaper EF lenses with the adapter works perfect on first try with IS on.
#24
Tragic Lantern / Re: Tragic Lantern for EOS M
August 09, 2013, 10:56:14 PM
@ wuxiekeji I was on the same boat too.

Found solution under "Installing Magic Lantern on other cards" subject here:
http://magiclantern.wikia.com/wiki/Unified/Install
make_bootable.sh

ExFAT is completly broken and at least Ubuntus fuse based exFAT refuses to even mount the card after trying so FATxx is the way to go.