350d boot from cf card - page 36 - DSLR Hack development - CHDK Forum

350d boot from cf card

  • 510 Replies
  • 298271 Views
Re: 350d boot from cf card
« Reply #350 on: 02 / December / 2010, 21:10:24 »
Advertisements
fisrt, I must thank all you guys. and I have a suggestion that the hack function should be actived only in "M" mode.
I don't know if it's possible. but I think it's very helpful for me.

Re: 350d boot from cf card
« Reply #351 on: 08 / December / 2010, 13:17:05 »
There have been several people who bricked their 350Ds by running the bootflag modifier program with the wrong firmware installed.  As I understand it, they can no longer access any CF card, which means there's no way to reverse whatever damage was done - even if you could figure out what to do - because you can't get back in.

I just wondered if anyone has had experience with sending such a camera in to Canon for repair.  In theory all the camera needs is to have the firmware and flags memory and such be completely re-flashed to the original factory state.  If that's possible, it shouldn't really be an expensive repair because you wouldn't even need to disassemble the camera.

They might be able to get back in through the USB connector.  Or, if you take the battery out and look down into the well, there are two 8-pad connectors at the bottom that don't have anything to do with the battery.  Maybe that's some kind of factory access that could be used if CF isn't working.

Well, I know it wouldn't make a lot of sense to spend big repair money on a 350D, but it seems like it might be worth it to at least send it in with an explanation, and ask for a repair quote before they actually do the work.

What do you think?

Re: 350d boot from cf card
« Reply #352 on: 12 / December / 2010, 12:42:24 »
Ive got a 350D with batterygrip, FW 1.03. 32k shutter count. And I have managed to 'brick' mine a couple of times.
I used the camera with the custom firmware, perhaps taken 100 shots with it trying out all the functions.
A week or two after I went out on a boat trip and the camera died after 5 shots. I tried everything, removing the batteries, lens, battery grip, CF-card, and the tiny CR2016 battery. Dead.
Six days later i assembled the whole thing and voila! Red light on, blue light on -all ok.
Two shots later. Dead. This time I left the camera switch ON (displays were dead). 30min later I returned to pack down the camera - it was HOT. Sure I could hold it in my hand, but this was to hottest camera I've held. This time it took three weeks before it 'woke up' again. (This time I had the the tiny CR2016 battery removed.)

Sorry for the long post, but my conclusions are: If 'bricked', remove ALL batteries. Then wait. At least a week. Then reassemble and try. Dont give up, it might take a week or two before the camera is completely drained of power.
And REMOVE THE BATTERIES when not in use. (Fire hazard?)

Q: Why does this happen?

Re: 350d boot from cf card
« Reply #353 on: 12 / December / 2010, 19:06:31 »
That sounds really strange.  Does this happen with any CF card you might use?  Or if you put in a normal non-bootable card with no autoexec.bin file on it, does the camera behave normally and stay cool?

Does the heatup happen when not using the battery grip?



*

Online reyalp

  • ******
  • 12366
Re: 350d boot from cf card
« Reply #354 on: 12 / December / 2010, 19:25:24 »
Ive got a 350D with batterygrip, FW 1.03. 32k shutter count. And I have managed to 'brick' mine a couple of times.
I used the camera with the custom firmware, perhaps taken 100 shots with it trying out all the functions.
A week or two after I went out on a boat trip and the camera died after 5 shots. I tried everything, removing the batteries, lens, battery grip, CF-card, and the tiny CR2016 battery. Dead.
Six days later i assembled the whole thing and voila! Red light on, blue light on -all ok.
Two shots later. Dead. This time I left the camera switch ON (displays were dead). 30min later I returned to pack down the camera - it was HOT. Sure I could hold it in my hand, but this was to hottest camera I've held. This time it took three weeks before it 'woke up' again. (This time I had the the tiny CR2016 battery removed.)

Sorry for the long post, but my conclusions are: If 'bricked', remove ALL batteries. Then wait. At least a week. Then reassemble and try. Dont give up, it might take a week or two before the camera is completely drained of power.
And REMOVE THE BATTERIES when not in use. (Fire hazard?)

Q: Why does this happen?
I would take a wild guess that this is some kind of intermittent electrical/mechanical failure in the camera unrelated to the hack.
Don't forget what the H stands for.

Re: 350d boot from cf card
« Reply #355 on: 15 / December / 2010, 04:10:28 »
You can build your own hack

1. Download gcc346.zip
http://www.filefactory.com/file/b00a572/n/gcc346.zip

Hi, I use the firmware from the quote.

I want to reassign some of the hotkeys.
spot metering, I can not find this option in main.c

how to assign buttons metering + print = spot metering.

petition asking for my english.

2. Extract it to c:\
3. cd c:\gcc346\myproject\350d_all_in_infov2_fastcwb\
4. build.bat
5. Copy the AUTOEXEC.BIN to your CF Card

you can edit the source code before you run "build.bat"



Hi, I use the firmware from the quote.

I want to reassign some of the hotkeys.
spot metering, I can not find this option in main.c

how to assign buttons metering + print = spot metering.

sorry for my english.
« Last Edit: 15 / December / 2010, 04:14:44 by Draf »

Re: 350d boot from cf card
« Reply #356 on: 24 / December / 2010, 23:28:48 »
When updating from firmware 1.0.3 to scanled.fir, the blue LED does not come up at all. I kept the camera at "CF card containing firmware is required to update" screen for 10+min with no blue LED comming up. I checked blue LED is working on PickBridge printing. Have reset all the camera settings to default. Any idea? My camera is Rebel XT (USA ver).

Thank you in advance.
« Last Edit: 24 / December / 2010, 23:38:59 by deweb »

Re: 350d boot from cf card
« Reply #357 on: 25 / December / 2010, 23:22:09 »
If you're absolutely sure your camera has firmware v1.0.3, then you may be one of a small number of people who can't get scanled.fir to work even with the right firmware.  In earlier posts to this thread we discussed some serious shortcomings with scanled.fir, and I posted a new version called bootflg2.fir:

http://chdk.setepontos.com/index.php?topic=4202.msg57328#msg57328

But I think the first thing you should do is see if scanled succeeded in changing the boot flag even though the blue light never came on.  Go through the process of making a CF card bootable, put one of the autoexec.bin files in the boot directory, and see if the camera runs it.   If it does, then  I think you are where you want to be.

If not, then you might want to try my bootflg2.fir.   That version works on my XT, and it does check for the presence on 1.0.3 before doing anything.  I believe it is a better, safer boot flag modifier, but since I'm the author, I may be biased.  In any case, there are no guarantees with any of these programs, so you take your chances.



Re: 350d boot from cf card
« Reply #358 on: 02 / January / 2011, 15:37:39 »
Thank you for your quick response peabody.
Using bootflg2.fir produces only one blue LED flash. I am stock. Any other idea?

Re: 350d boot from cf card
« Reply #359 on: 02 / January / 2011, 16:27:23 »
No, I'm afraid I don't have any more suggestions.  Bootflg2 first checks for v1.0.3 firmware, and makes sure the initial state of the bootflag block is as expected.  Apparently that was successful because you got the first blue flash.

But then it calls the subroutine in firmware that's supposed to transfer the boot flag block to ram, and then checks to be sure that was done correctly.  If it was, it will blink blue again, but if not you should get a solid red light.  Since you get neither of these, I have to assume it's not even coming back into bootflg2 from the subroutine.

I don't know why that is happening.  It may be that there are different versions of the 350D hardware, and that the mystery subroutines originally used in scanled.fir without explanation aren't at the same place in all versions.  That would make sense if that part of the firmware isn't updated by new versions from Canon - it may be part of the boot code that never changes.

I wish I knew how to dump a range of memory to a file on the CF card.  Then I could include a test to see if that routine is where it's supposed to be, and contains what it should.  Or, just include the right subroutine in the program in the first place.  Maybe someone could suggest how to do that dump.

Anyway, if your camera still works, that's the main thing.  If it does, I wouldn't do anymore attempts at this.  That has ended badly for some.


 

Related Topics