350d boot from cf card

au_courant777

crazyklaus
and, I forgot to ask, in what order do you want the menu entries to be?

Ohh, thanks crazyklaus. I tried again to do it but im really stuck, (hahaha i dont know what Im doing) I indeed need the shortcuts orders are ISO, Spot metering, safety shift, shutter count display and extended AEB and as you suggested the color temp white balance and focus assist beam the 'no flash' option too. Thanks again in advance and very much appreciated crazyklaus.

crazyklaus

ok, this is your file:
http://www.mediafire.com/file/qa1vswkjceo5a2l/350D-au_courant.zip

just take the autoexec.bin out of it.

the menu is in the order 1 iso 2 metering (with spot option) 3 safety shift 4 flash on/off 5 counter 6 colortemp 7 white balance 8 aeb

so if you want the aeb or WB just go the other way round and you're right there.
also note that there are shortcuts for activating spot metering, safety shift, flash and colortemp white balance (look in the thread I explained the shortcuts somewhere) so you don't need to go over the menu eg if you want spot metering

crazyklaus

new version with automatic flash exposure bracketing via INFO menu

it always takes three shots: underexposed first, then normal and overexposed last.
adjust the flash exposure difference with LEFT/RIGHT, adjust the waiting time between the shots with MENU/INFO (minimum is 3 seconds), start the sequence with SET

don't press any keys during the sequence or you will confuse the code 😉

you need to increase the waiting time between the shots manually if you want to take long exposures.
please report if the 3 second waiting time doesn't work for you (I have the suspicion that it won't work with big files (ie RAW+L) and slow cards). longer delays should though.

http://www.mediafire.com/file/uiw46q26dq9ddmm/350D-20101011.zip

degra

Hi to all!
I'm new here andm as first thingm I want to thank you all for these great hacks.

I tried and succeded to install the "firmware" on my 350D, and everything works fine. Except the timelapse function: when I press "SET" the camera take the first shot, but the second one is never taken. Sometimes it takes 2 or 3 shots but not the number I set on the menu, nor the right interval. I tried to set different time and frames, but nothing changed. Anybody succeeded to make the timelapse work?

I use the version of Cyrustam from this https://chdk.setepontos.com/d/4202/275

Thanks

au_courant777

Thn

crazyklaus
ok, this is your file:
http://www.mediafire.com/file/qa1vswkjceo5a2l/350D-au_courant.zip

just take the autoexec.bin out of it.

the menu is in the order 1 iso 2 metering (with spot option) 3 safety shift 4 flash on/off 5 counter 6 colortemp 7 white balance 8 aeb

so if you want the aeb or WB just go the other way round and you're right there.
also note that there are shortcuts for activating spot metering, safety shift, flash and colortemp white balance (look in the thread I explained the shortcuts somewhere) so you don't need to go over the menu eg if you want spot metering

Thanks for this. It is awesome....

annuges

A question to whoever wrote the eAEB feature (Cyrustam i assume?)

in your code you use a fixed delay of 5 secs between pictures, am i right to assume your busyflag idea doesnt work?


SendToIntercom(0x53,0,0);
 SleepTask(5000); //delay for system to save picture
                                //while (cameraMode.BusyFlag != 0 )
                                //{
                                //   SleepTask(1000); 
                                //}

Im asking because while this works fine under pretty much all circumstances,
its stops working as soon as you get Tv values > 5secs (eg. nighttime photography).
Now, I could just set the delay to 10000, but that sucks for normal exposure times.

If it doesnt work, would you mind doing a little sanity check on something i thought about?

temp=camera.Mode.TvVal;

tv=HexToMilsecs(temp);

SendToIntercom(0x53,0,0);        //shoot

SleepTask(500+tv);                 //well,  SleepTask(500+HexToMilsecs(camera.Mode.TvVal)); is probably more elegant

To me this looks like it could provide a delay closer to what is actually needed to account for writing to the card.

The real work is probably in the function translating the hex values to at least somewhat accurate durations for the sleep command so i would appreciate some feedback before i start working on some dumb idea that easier to archive some other way... 😀

thanks to anyone who's been working on this so far!!

pepponeskie

hi...im new in the forum and tried CHDK in my 350D and now I am having a great problem.

i just followed the instructions in this link below

http://chdk.wikia.com/wiki/350D

but now when I want to use a normal CF CARD, my camera cannot read it anymore and says "ERR CF"

what am i going to do now? Please help me. I want to revert back all the settings in my camera before...please help.

annuges

pepponeskie,

in this post:
https://chdk.setepontos.com/d/4202/5
the guy who posted the scanled.fir links to a bootflag.fir that's supposed to revert the changes the 2nd time its run

if that doesnt work, id assume using the official canon firmware update would reset everything.
(try to put the files on the modified cf if a normal one doesn't work)

hope that helps

edit:

i worked out how cameraMode.TvVal is mapped to the shutterspeed.
time to watch Tv now, i'll might continue on the other stuff tomorrow

pepponeskie

@annuges:

my situation is similar to this post
https://chdk.setepontos.com/d/4202/178

but, i didn't find a solution to his post.

RebelKeith

I'm trying to install chdk on my 350d but I'm stuck at:

"2. Insert CF to camera and run firmware update from the bottom choice of the 5th Menu setup screen. Screen will show "CF card containing firmware is required to update". Wait for blue LED to light steady. Wait another 30 seconds."

No blue light ever comes on, I waited for 5 minutes and nothing happened. Am I missing something?

pepponeskie

RebelKeith
I'm trying to install chdk on my 350d but I'm stuck at:

"2. Insert CF to camera and run firmware update from the bottom choice of the 5th Menu setup screen. Screen will show "CF card containing firmware is required to update". Wait for blue LED to light steady. Wait another 30 seconds."

No blue light ever comes on, I waited for 5 minutes and nothing happened. Am I missing something?

the same happened to me when I followed that step...then when I place my other CF in, it says "ERR CF"...no matter what I do still the same error. It only works as normal when there is no CF card inside.

Please experts help.

peabody

Over the weekend I bought my first DSLR - a used 350D. I would love to implement these improvements, but after reading the entire thread, I see a number of people have effectively bricked their cameras trying to do the bootflag changes. A couple involved the wrong firmware version, but not all. Does anyone have an idea of what may be going wrong for these guys? Could we be dealing with different hardware versions?

Is it possible to make scanled.fir, or I guess bootflag.fir, look first for things it expects to find at specific locations, including the firware version number, before actually changing anything?

Well, in any case, I really appreciate the work of those who made this all happen.

peabody

I'm curious about the shutter actuations count reported here. Has anyone checked the EXIF data of a raw file to see if the same value appears anywhere in there?

Would it be possible for a "count.fir" file to write the count value to a file on the CF card, or display it, but NOT make any changes to the bootflags?

pepponeskie

im still waiting for the reply of the experts...maybe they can help me

peabody

Pepponeskie, unless you didn't have firmware v1.0.3 when you began this operation, it's hard to see that you've done anything wrong. The problem has to be in the original bootflag change using scanled.fir, and not in any later step. We know that because when you now insert a newly-formatted, non-bootable CF card, your camera is supposed to operate normally, as if no change has been made. But instead, yours produces a CF error message. And if I understand correctly, the same error message occurs even when you insert a bootable CF card with a correct autoexec.bin file on it. So basically you are now unable to do anything with any CF card, which makes it impossible to make any further modifications. If that's correct, it's hard to see how you can recover from that. I hope I'm wrong. If so, the experts will say so.

I think the point just needs to be made that while most people have done the bootflag mod successfully, there appears to be a small but very real chance that it will instead brick your camera even if you follow the instructions exactly and have the right firmware version to start with.

pepponeskie

@peabody:

you are correct. the thing that is happening now is that, I cant access my cf card, i cannot update firmware for it says "cannot update. stop", and there is no way I can access the CF card, and the camera wont take photos anymore. I think, the only way is to access the camera from the USB and reset the firmware. Or to make a bootable card that is loaded with a software that automatically reset or restore the firmware or the settings back into normal one.

crazyklaus

ok, there is a very small chance that you will kill your camera with firmware version 1.0.3
but there is a near 100% chance that you will your camera if it's not firmware 1.0.3

IF YOU WANT TO TRY THIS HACK, PLEASE CHECK YOUR CAMERA'S FIRMWARE VERSION FIRST!

SEVERAL PEOPLE KILLED THEIR CAMERAS BECAUSE THEY THOUGHT THEY HAD THE RIGHT FIRMWARE BUT ACTUALLY HAD NOT.

posting this here in a really huge font trying to prevent it happening again.

peabody

Thanks crazyklaus. But wouldn't it be even better if bootflag.fir could check for the presence of the v1.0.3 firmware before proceeding to change the flags? I mean, just in case someone doesn't see your post.

Anybody know how to do that?

Still leaves the issue of how you end up with a bricked camera when you DO have v1.0.3.

peabody

Pepponeskie, have you looked at the pins at the bottom of the CF slot to make sure none is bent or broken. I know, it's unlikely in the extreme, but just to be sure.

pepponeskie

peabody, in the camera side, all pins are ok.

« Previous Page Next Page »