gezus
Hello,
you can read a little more on this subject to learn, everything is explained in this forum if you really need...
You can find easily how to change the SET button's mapping by reading your 350D owner's manual i think.
Otherwise go into a regular menu called "CFn" and you'll find the SET button option.
gezus
ujav
Is there option for RAW + Full-size Low quality Jpeg? I can't find it.
Hello, there is no more option for RAW + Low JPEG in the Custom Menu of this Chdk build,
because I commented out POSITION_RAWMODE in user_settings.txt file.
I post the 2014 sources here, so you can go on and modify what you want.
Last build I did (2014) is based on Zestoi's 2012 latest source code.
eduperez
ujav
Thanks for the wonderful work! It's 2014 but this camera can still make excellent shoots.
Is there option for RAW + Full-size Low quality Jpeg? I can't find it.
Btw, fine AF adjusting is impossible in software?
What I know from the 400D hack (very similar to this one):
- If I recall correctly, "RAW + low quality JPEG" does not work (camera just locks).
- AF is handled by a IC external to the ARM processor, and thus pretty much out-of-bounds for this project.
nishandh
Subject : Buttons to change number of shots for TimeLapse not working.
Hi,
Everything was working for me on the 350D, but I am unable to change the number of shots, for TimeLapse now ???.
Re-booting is not correcting the problem. All other CHDK features appear to work(not fully tested).
I have started reading this whole thread, reached 11 pages now. Would be thankful if you can direct me to the exact thread !
Using 4GB card, made bootable.
nishandh
I read the whole thread.
Is this issue known to be discussed else where in the forum 😐: ?
(Issue : unable to change number of shots using 'Menu' or 'Info' or any other buttons. It worked that way earlier.)
gezus
Hello,
i don't know if your using my 2014 version of autoexec.bin so i answer here :
- for me timelapse is working as usual you can change number of shots and interval using the 3 buttons "play/info/menu".
- i haven't changed anything in the buttons config for timelapse in my 2014 version.
Anyone has tried new 2014 version ? any suggestions ?
Sure not much people still using this old camera...
RayeR
gezus
Anyone has tried new 2014 version ? any suggestions ?
Sure not much people still using this old camera...
Hi,
I was using my 350D since 2007 and I was satisfied with it. Last I used CHDK from Zestoi 16.9.2012. But it's time to move forward and last year I have bought a new DSLR from Pentax model K-30 (I still keep my 350D). I think that for same money it offers more than similar canon or nikon models. Firmware is quite rich of features, e.g. timelapse, pixel mapping, front/back focus compenstation and more is in regular firmware so no more need a hack. But despite that there's pentax FW hacking in progress, it was done FW decrypting and modding to run simple user code on camera.
So my thanks goes to everybody who breaks the limits 😀
tzeus
Hello!
I have finally decided to mod my camera. Procedure went well, with one tiny exception.
When i did the bootflag writing procedure, the leds flashed in the correct order:
BLUE, BLUE, BOTH, BLUE. However, as someone was writing in the previous pages, switching the camera off did not work. I went on and formatted my CF card, put gezus' latest compiled AUTOEXEC.BIN, and the mod is working. I just thought i would share this, as it would prove valuable info in future development.
Now for the pressing issue, i am able to do timpelapse, but i cannot use the zoom in / out and the dp buttons. How exactly do i use them ? For example when i am in iso menu(moded one) if i press any of the three designated buttons, the value doesn't change and the buttons do what they are normally supposed to do. Note that i have compiled your latest files using gcc346, just to be sure that i have the shortcuts. Is there a step i am missing? I already changed the set button function in custom fn.
Thank you for all the support !
peabody
The program that does the boot flag setting ends by going into an endless loop using the C instruction "for ( ; ; )", and as a result you have to remove the battery to turn off the camera. That's really not a problem, and it should work normally after that.
Can't help you with the other issues.
Harry
Hi, I'm new here but CHDK on Canon 350D using for several years. I have one question. Is it possible to make CHDK in Czech language? I tried to rewrite the English entry directly in the Czech AUTOEXEC.BIN file, but it worked only partially.
fran2a
Hi all,
To save battery, I would like to set reviewtime to off when shooting en timelapse mode.
I am compiling a new CHDK in order to set that but it doesn't work. 350d doesn't fire automaticaly after first shot, but shoot instantanly when half press the the shutter button.
Here my code:
#ifdef POSITION_TLAPSE
void SwitchTimeLapse(int button) {
int i, OldLcdBrightness, OldReviewTime;
switch (button) {
#ifdef USEPLAYFORSET
case BUTTON_PLAY:
#else
case BUTTON_SET:
#endif
for (OldLcdBrightness=cameraMode.LcdBrightness, //save brightness and review time values
OldReviewTime=cameraMode.ReviewTime,
//cameraMode.ReviewTime=0xff, //set review time to hold
cameraMode.ReviewTime=0, //set review time to off
SendToIntercom(0x16,1,1), //set brightness
SendToIntercom(0x53,0,0), //release
i=1; i<TLapseFrames; i++) {
SleepTask(TLapseInterval*1000); //release
SendToIntercom(0x53,0,0);
}
cameraMode.ReviewTime=OldReviewTime; //restore brightness and review time settings when timelapse sequence is done
SendToIntercom(0x16,1,OldLcdBrightness);
SHORTCUTSIGNAL
break;
case BUTTON_LEFT:
if (TLapseInterval>1) TLapseInterval--;
break;
case BUTTON_RIGHT:
TLapseInterval++;
break;
case BUTTON_MENU:
TLapseFrames *= 2;
break;
case BUTTON_INFO:
if (TLapseFrames>1) TLapseFrames /= 2;
break;
#ifdef USEPLAYFORSET
case BUTTON_SET:
#else
case BUTTON_PLAY:
#endif
TLapseFrames++;
break;
}
}
#endif
Help welcome!
Thanks
dp297
Sorry guys,
can anyone point me to the most recent Canon 350D ML hack and perhaps a set of instructions?
The post is pretty big ..so...
peabody
I think the process is described here:
http://chdk.wikia.com/wiki/350D
reyalp
dp297
Sorry guys,
can anyone point me to the most recent Canon 350D ML hack and perhaps a set of instructions?
The post is pretty big ..so...
I would
strongly recommend that you read very carefully, since more than one person irrecoverably damaged their camera.
Also note the 350D hack is neither ML nor CHDK.
ciaoabra
hi everybody
i'm new to this forum
i've a 350d i've tried to use chdk on it, but i wasn't able to let it boot from the CF
i've read an tried different things (formatting the card, using CardTricks or HxD on it) on different cards (250MB, 2GB,4GB)
nothing seems to work.
someone can help me pointing me to the right procedure?
i'd like to do some timelapse
thanks
stamasd
I'm a little late to the party (6 years late to be exact) but I hope I will still find someone who knows anything about this firmware...
I have just tried to install it on a 350D, firmware 1.0.3 that was modified for full-spectrum and that I'm using for astrophoto with the hope that I can use its intervalometer.
I failed to have the firmware installed. No, the camera isn't bricked, it works just as well as before, but the firmware hack didn't "catch"
Here's what happens:
1. I have a CF card (an old one, 64MB "MrFlash" brand that I've been using for other firmware updates etc) that was freshly formatted to FAT16, blank otherwise, added to its root bootflg2.fir from post #342 on this thread.
2. Inserted the card into the 350D, went to the firmware menu, verified once more that I have 1.0.3, pressed "set" then selected OK to upgrade firmware
3. camera went on to display "CF card containing firmware is required to update" as expected
4. blue light flashes briefly. All good.
5. blue light flashes briefly. All good.
6 Nothing happens for a very, very long time. No LEDs are on.
7. After waiting for about 10 minutes, still nothing happens. Turned camera off, took battery out then back in, turn camera on. All works well. Firmware still shows 1.0.3, not sure if it should have changed or not...
8. Tried to boot from a card that I had previously made bootable with a hex editor, and has autoexec.bin on it. Camera displays "CF Err" on small LCD. Tried another random CF card, works well. Info menu doesn't have anything new.
9. Restarted process at 2, attempted 2 more times to have the firmware flashed (formatting the CF card each time and re-writing bootflg2.fir to it each time. The exact same thing happens.
10. Attempted the process again using the original scanled.fir from 2009 instead. This time, the blue LED flashes briefly, then the red LED briefly, then again nothing happens with the camera displaying "CF card containing firmware is required to update" for a long time with no LEDs on. Turn camera off, remove and reinsert battery, turn camera on, everything works, nothing is changed.
So it seems that toggling the boot flag on this camera fails. Any suggestions? Thanks in advance.
eduperez
I would stop fiddling with the bootflag: once it has been set, there is no need to touch it any longer, even if you want to upgrade the hack. From the message you are seeing, I would bet you are not preparing the cards properly; format them again, and be sure to edit the right bytes.
Hope this helps.
stamasd
Thanks for the reply, but I don't think this is it. The bootflag process clearly starts (thus the file is recognized, loaded and executed) but never completes as I never see the completion of the correct LED sequence. I have since tried another card, a 256MB CF that I did first a low-level format on, then formatted FAT16, edited the boot sector in the correct location (at 0x2B "EOS_DEVELOP"
at 0x40 "BOOTDISK") and placed autoexec.bin on. It doesn't boot.
stamasd
Well it looks like it's impossible to get the firmware onto this camera. What I did:
1. tried various CF cards, formatted both in the camera and on the PC, including low-level formats; Tried both FAT16 and FAT32.
2. I even flashed the camera again with the official 1.0.3 firmware
3. Tried all the available boot hacks from this thread.
None of these makes any difference, I cannot get the camera to boot from card. The LED sequence on applying the hack never finishes, and it even flashes "Err 99" on the LCD after trying. Fortunately after removing and reinserting the battery all looks fine and the camera operates properly.
Guess I'll have to live without a software intervalometer. 🙁
peabody
I wrote the bootflg2 program, the primary purpose of which was to do whatever tests are available at each stage to make sure everything is as it should be. The result is that it doesn't try to change anything in the firmware unless everything checks out. However, since the author of the original software had disappeared, I was to some extent flying blind. The problem we had was that some cameras were bricked using the original program, for no clear reason. In any case, if the correct sequence of flashes in bootflg2 does not complete, then something that bootflg2 expects to find isn't there, or isn't correct. I no longer have a 350D, but even if I did, I couldn't tell you how to solve this problem. It works for most cameras, and if it doesn't work for a camera, at least it doesn't brick it (because it doesn't try to change anything).
