40-150 f2.8 bricked by EM1mkii

Airmel wrote:

karlreed wrote:

My experience of USB connections via hubs is that they can be AWFULLY flaky. So, this needs to be kept in mind if updates must be by a direct connection to the computer, ior, internet rather than via a card.

However, best practice for this kind of update is NOT to destroy the current version until the update is complete AND the system has been re booted.

Unfortunately, most embedded systems don't have anywhere near the resources (think firmware storage space) needed to permit this duplication.

In these systems, there is usually a small portion of code designated to perform the update/re-flashing (and which is not updated in the field). That small, "update" portion of the code takes control while the main firmware package is overwritten by the new version.

The process is a lot like performing brain surgery on yourself. As with all complex things, the devil is in the details.

This can be done by booting via a pointer to the active system. The VERY LAST THING the updating s/w does is to change this pointer to point to the new systems.

Don't apply general purpose computer "PC" thinking to embedded systems, They are completely different.

I am familiar with the use of "boot" software, and, also, "boot strapping" as a means of starting systems., (and doing a few other things as well. However, Oly could quite easily have the camera copy the new system to a SD card on the camera, and, the copy that into the camera.

'tis my considered opinion that too much software is written buy vunder-kinder under 40 who seem to believe that when things god wrong, it's the user's problem.

Having said that, the s/w on the cameras and the PP apps is pretty bloody amazing!

This risk of bricking a A$1500 lens would almost be a good enough reason to avoid the system!

Karl

See

-- hide signature --

AirMel
http://www.mel-photo.com
There are 10 types of people in this world.
Those that know binary and those that don't.