Firmware Version 1.2.0 addresses the following phenomenon.

• If pressure is applied to the lens barrel while the lens is mounted to the camera (pressure can be applied even while attaching the lens cap or while carrying the camera with the lens attached in a bag), the autofocusing function of the lens may stop working.

Little bit annoyed that my 7D with v2.0 can't do this while a T4i can. They are still shipping new 7Ds after all. That- and the new Group function on the 600EX-RT Speedlites. I wonder if the EOS-M will support all these 2012 camera functions.

+2

I just trashed my 40mm f/2.8 trying to do the firmware update with my 5D3. I followed the instructions by the letter. The update failed and rendered the lens inoperable. Now the lens has to go back to Canon and it scared the hell out of me because I thought it might have also damaged the 5D3. Save yourself the grief I have been through today and send it back to Canon for the update or don't do it at all.

Matt Howell wrote:
I just trashed my 40mm f/2.8 trying to do the firmware update with my 5D3. I followed the instructions by the letter. The update failed and rendered the lens inoperable. Now the lens has to go back to Canon and it scared the hell out of me because I thought it might have also damaged the 5D3. Save yourself the grief I have been through today and send it back to Canon for the update or don't do it at all.

Did your 5D Mark III have firmware v1.1.3 or later?

Maybe that explains why Canon didn't give us the option to do the update ourselves with the Mk II superteles.

Yes, I had loaded firmware v1.1.3 on my camera back in June. As I said, I literally followed the instructions to the letter and even went further by clearing all settings and custom functions before attempting the update. I am really disappointed in Canon that this could happen. I believe this first ever user applied lens update was poorly tested.


More detail:

The camera recognized the update and started applying it when I clicked ok. When the progress bar reached 29% it suddenly jumped to a full bar and said 2978% complete. I swear this is the craziest thing I have ever seen and I knew at that point that I was screwed. I quickly got Canon on the phone and we waited an additional 10 minutes but never got to update complete. The camera was locked up and I had to remove the battery to get it to turn off. A second attempt with a different memory card while on the phone with Canon came to the same result. The lens will be sent out to Canon tomorrow for repair.

Huh!

This is nucking futs. Guess I'll have to refrain from getting the 40. Pity...

I was about to take this thread down but decided to try it for myself.
For me it worked without any problems. It was a very fast update and my 40mm f/2.8 is now v1.2.0.
Post your success stories as well.

Matt,
Was your battery low in charge? Did you have anything else on the memory card or just the firmware file?

Just updated with no problems using a 5D Mk3 with latest f/w... CF card Lexar 1000x 16GB formatted in camera. Unpacked the zip on XP-32bit machine. Just dropped the EF005120.lfu in root of CF.

Some peaople say using Mac may cause problems with the file... not sure how or why

There doesn't seem to be any particular reason for the failure I experienced. I did the download and unpacking on a Windows 7 x64 system. The file properties were showing the correct size for the firmware file on the card after I copied it over. I used a nearly new Canon battery that was showing 97% full. I used a sandisk extreme 8gb SD card the first time and a sandisk ultra 4gb CF card the second try. How can I possibly explain a 2978% complete message? I saw it, it happened, is all I can say. It probably ruined the lens or at least some of the electronics in the lens and now sadly my lens is out of commission.

I would wait since above ...

Snopchenko wrote: Guess I'll have to refrain from getting the 40. Pity...

That would be the wrong conclusion to draw. Any new 40 mm you are likely to buy from here on out will almost certainly have the most up to date firmware already in place.

I may get one myself in a few weeks.

Fred Miranda wrote: Firmware Version 1.2.0 is for lenses with Firmware Version 1.1.0. If the lens' firmware is already Version 1.2.0, it is not necessary to update the firmware.

The lenses with the following serial numbers are equipped with Firmware Version 1.1.0:
The third digit in the serial number is either 0, 1, or 2 (xx0xxxxxxx, xx1xxxxxxx, or xx2xxxxxxx).
Lenses with serial numbers other than those listed above are equipped with Firmware Version 1.2.0.

WebDog wrote:
Just updated with no problems using a 5D Mk3 with latest f/w... CF card Lexar 1000x 16GB formatted in camera. Unpacked the zip on XP-32bit machine. Just dropped the EF005120.lfu in root of CF.

Some peaople say using Mac may cause problems with the file... not sure how or why

I forgot to mention that I used a Mac when successfully updating my lens firmware.

Fred, which OSX version were you running? I have seen at least one report that Mountain Lion may cause a problem. Thanks.

Howard

Well, I still recommend this lens. New ones will already have the update. It is simply very good by any standard and one of my favorites.

http://imgur.com/UYBWR

Snopchenko wrote:
This is nucking futs. Guess I'll have to refrain from getting the 40. Pity...

Updated fine here.... 650D - Mac OSX 10.6

Firmware update worked for me. MacBook Pro 2.2GHz, OS X Lion 10.7.4. Canon 5D MkIII firmware version 1.1.3.

Mine failed and the lens went back to Canon.

Windows 7, 5D3 with firmware V1.1.3