08-10-2017 01:54 PM - edited 08-10-2017 02:08 PM
Hello my frends,
I have EOS 1000D and big problem with DSLR.
Cant boot on power on. When I put fully charged battery, close batt. door, RED LED blink fast 1-2 sec and thats all. LCD display is black and stay black. When I press shutter to half or full, I can see tru viewfinder buSY message , ISO change value on light and thats all. When I put LOCKED SD Card, tru viewfinder I can see Err. , when I put unlocked SD Card ..still buSY. Shutter have no responde
USB to PC = not detected!
08-10-2017 02:46 PM
08-10-2017 02:54 PM
08-10-2017 03:11 PM
We found that often what caused this was not updating to the most recent firmware.
If your camera became affected by this phenomenon, while the camera was still in service life (up until 2015), our Factory Service Centers here in the United States could still manually upate the firmware. Unfortunately the camera is now out of service life, so our facilities here in the US are no longer making repairs or updates to the EOS 1000D, or Rebel XS as it is known here in the US.
08-10-2017 03:16 PM
08-10-2017 03:51 PM
If your camera can be recognized by your compuer, then you should be able to update the firmware. If your camera can't be seen by the computer, then unfortunately you'll want to see if Canon in your region has options. Head to http://global.canon/en/support and select your region for support options.
08-11-2017 06:34 AM
Ha. I'm going to start using the word "phenomenon" when I totally screw something up at work. Like the curious phenomenon where it appears I do not show up, and instead I am actually at home sleeping.
Seems warranty or no, he should at least get loyalty credits towards a refurb or something because it didn't wear out, it is a known defect.
08-11-2017 07:17 AM - edited 08-11-2017 07:19 AM
I know, it's all clear to me for a guarantee.
But ...
I am interested in how the factory enters the new firmware on a bricked board. There must be a way, rather than throwing a plate off and putting another. I wonder if anyone knows in what way they flash new firmware? Is it possible that VxWorks is forced to enter new firmware via specially formatted SD card? Or the special pins on the board that work through the serial cable? MPU is working, and its EEPROM works. It is a controller for AF, batt and SD card door, display through a viewfinder, servo, flash, buttons, shutter, ... ect. For example, when I remove a flat cable from the shutter, it reports error 99 .... That's all. It is also the primary boot, and after its boot, it should continue DIGIC III with F-ROM to boot firmware. This is the end, he has nothing to boot, or the firmware is damaged and the buSY is released. DIGIC III is the basis for LCD, photo sensor, USB, ... and that's what does not work. Not to prolong the writing, does anyone know the way to write to F-ROM that is bricked with damaged firmware? It's probably a bug that just put the firmware in the lock position.
08-11-2017 07:26 AM
I know, it's all clear to me for a guarantee.
But ...
I am interested in how the factory enters the new firmware on a bricked board. There must be a way, rather than throwing a plate off and putting another. I wonder if anyone knows in what way they flash new firmware? Is it possible that VxWorks is forced to enter new firmware via specially formatted SD card? Or the special pins on the board that work through the serial cable? MPU is working, and its EEPROM works. It is a controller for AF, batt and SD card door, display through a viewfinder, servo, flash, buttons, shutter, ... ect. For example, when I remove a flat cable from the shutter, it reports error 99 .... That's all. It is also the primary boot, and after its boot, it should continue DIGIC III with F-ROM to boot firmware. This is the end, he has nothing to boot, or the firmware is damaged and the buSY is released. DIGIC III is the basis for LCD, photo sensor, USB, ... and that's what does not work. Not to prolong the writing, does anyone know the way to write to F-ROM that is bricked with damaged firmware? It's probably a bug that just put the firmware in the lock position.
08-11-2017 08:50 AM
When a camera gets bricked like that, it's usually because the camera lost power during a firmware upgrade. Apparently there isn't enough firmware memory to install the new before removing the old, so it has to do it on the fly. If the camera loses power, the part of the firmware that boots up the camera may not be there. So there's every reason to suppose that Canon has to apply some rather heroic measures to get things working again, such as temporarily wiring in a working chip to resuscitate the one in the camera. It's not the sort of electronic surgery that you're likely to be able to do at home.
09/26/2024: New firmware updates are available.
EOS R5 Mark II - Version 1.0.1
EOS R6 Mark II - Version 1.5.0
07/01/2024: New firmware updates are available.
04/16/2024: New firmware updates are available.
RF100-300mm F2.8 L IS USM - Version 1.0.6
RF400mm F2.8 L IS USM - Version 1.0.6
RF600mm F4 L IS USM - Version 1.0.6
RF800mm F5.6 L IS USM - Version 1.0.4
RF1200mm F8 L IS USM - Version 1.0.4
Canon U.S.A Inc. All Rights Reserved. Reproduction in whole or part without permission is prohibited.