Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - walta

Pages: 1 2 [3] 4
51
Camera-specific Development / Re: Canon 5D Classic Firmware ** Beta 4 **
« on: October 28, 2012, 09:17:07 PM »
i 've just installed  new FW follow your guide,  but blue led blink .. then after reset , press Trash button, but nothing happen??  did something wrong?  .. You say BLink led mean bootdisk is disable ,so how to enable .. thanks

Help I gave to an earlier poster who was having the same problem as you.


==========================================================
The instructions aren't too clear.

On your first install you need to do the firmware update with the file named "5dc.111.card bootable.fir" in the root of the card
This makes your card bootable
next you have to do the firmware update with the "5dc.111.ML install.fir" file (as well as all the other ones needed for ML)
This installs the ML bootflag.

There is no message that it was successful. The blue light should come on steady - like the instructions say. Then you have to remove the battery to re-boot the camera.

Blinking light means something wasn't installed properly.

I'm not sure what the camera does if you do the upgrade firmware process with 2 fir files in the root of the card.
after copying all the files over there, I made sure there was only 1 fir file each time when I did the firmware upgrade process and it worked for me.
 

52
Camera-specific Development / Re: Canon 5D Classic Firmware ** Beta 4 **
« on: October 27, 2012, 05:42:40 PM »
Hi,
I have 5D, with SN#252xxxxxx. will this work on my 5D Canon 5D Classic Firmware  ** Beta 4 **?

thanks

Earlier problems with different serial numbers are now solved. Works with all 5Dc cameras


53
Camera-specific Development / Re: Canon 5D Classic Firmware ** Beta 4 **
« on: October 24, 2012, 05:13:01 PM »
Okay, that makes sense - I will give a try later today. Indeed I did this with two files on the card. I thought I might want to do that one by one, but wasn't sure about the order so I didn't do that. Thanks for pointing that out! Perhaps the first post needs to be edited a bit? :)

Cheers!

I think the camera will probably read the file names in alphabetical order - so will only load the "make card bootable" one and never do the "ML bootflag" one.


Coutts said he was making changes to the boot sequence and other bug fixes so I suspect he won't worry too much about installation instructions being accurate until the first non-beta version is released.

I guess us "beta testers" just have to figure it out for ourselves.   :'(


 

54
Camera-specific Development / Re: Canon 5D Classic Firmware ** Beta 4 **
« on: October 22, 2012, 10:28:44 PM »
Thanks, already tried that with formatting card in camera and in windows. Tried with two batteries. Do I supposed to get any message that firmware update was successful? It just shows Firmware loading, screen goes blank and blue led starts blinking every couple seconds.

The instructions aren't too clear.

On your first install you need to do the firmware update with the file named "5dc.111.card bootable.fir" in the root of the card
This makes your card bootable
next you have to do the firmware update with the "5dc.111.ML install.fir" file (as well as all the other ones needed for ML)
This installs the ML bootflag.

There is no message that it was successful. The blue light should come on steady - like the instructions say. Then you have to remove the battery to re-boot the camera.

Blinking light means something wasn't installed properly.

I'm not sure what the camera does if you do the upgrade firmware process with 2 fir files in the root of the card.
after copying all the files over there, I made sure there was only 1 fir file each time when I did the firmware upgrade process and it worked for me.
 

 

 


55
Camera-specific Development / Re: Canon 5D Classic Firmware ** Beta 3 **
« on: October 05, 2012, 05:52:27 PM »
Does 400plus run on the 5D? Don't think so.
So why is it that you think Auto ISO is irrelevant for ML on the 5D?

Auto ISO is the single one thing I will run ML on my 5D for.

I'm only suggesting that it was of importance to the 400plus developers but is not to the ML developers.

I never said that 400plus would run on the 5D. I was using it as an example of how auto exposure (that works well) could be accomplished on Canon cameras by a third party developer.



56
Camera-specific Development / Re: Canon 5D Classic Firmware ** Beta 3 **
« on: October 05, 2012, 04:29:52 PM »
Sorry for my ignorance, but what is your point here? While you might not be happy with auto exposure, others might still like it. (like me). But must of all, what do you mean by "Good auto ISO can be done in LiveView, based on histogram"? There is LiveView in the 5D? Why would LiveView help with AutoISO? If I have the time for the histogram, I also have time to change the ISO. Sorry, that I don't get it! Please explain.
Thanks a lot for your answer,
Bests,
Christoph

Yeah, I'm confused as well. My xTi does a a great job of auto-ISO with the 400plus hack.  Sounds like its not a priority in the ML list of things to do.





58
Camera-specific Development / Re: Canon 5D Classic Firmware ** Beta 3 **
« on: October 04, 2012, 09:52:34 PM »
Be patient  ::)

Alex posted that we could compile it ourselves if we wanted - I just wondered if newer downloads with source are stored in a different place than page 1 of this thread.


 

59
Camera-specific Development / Re: Canon 5D Classic Firmware ** Beta 3 **
« on: October 04, 2012, 07:23:43 PM »
OK, so where is Beta 4 for us to enjoy?

60
Camera-specific Development / Re: Canon 5D classic || ** Beta 2 **
« on: October 02, 2012, 09:51:14 PM »
I'm getting the same message; how did you fix it?

Edit: Figured it out.  I decrypted all of the files and then moved them out of the subdirectories.  Not sure which change, or both, made the difference though.

Everything thats in the "5dc.ml23.beta3" folder needs to be unzipped and copied into the root of your CF card.

From the instructions: 5.) Download the zip file from the link below, unzip all of the files to your CF card.



61
Camera-specific Development / Re: Canon 5D Classic Firmware ** Beta 2 **
« on: September 29, 2012, 04:58:37 PM »
5DC with serial number 133080xxxx doesn't work. Long RED at startup.
Waiting for new versions.
Thanks!

New version won't help. According to the instructions long red means something didn't work right - either enabling the bootflag or making the card bootable.

I would try installing again making sure you have the right firmware version to start with.

Walt

 

62
Camera-specific Development / Re: Canon 5D Classic Firmware ** Beta 2 **
« on: September 27, 2012, 04:54:38 PM »
So, Andrew it looks like you've checked off your short term goals (from page 1) and now you've got the software running beside the Canon software.

Whats your priority list for implementing the rest of the ML features - so we get some kind of idea in what order things will be coming?

Great work BTW.

Walt


63
Camera-specific Development / Re: Canon 5D Classic Firmware ** Beta 2 **
« on: September 26, 2012, 08:25:09 PM »
Thank you very much! All donations greatly appreciated :)

Sorry it's a little confusing, but the installer fir should only be run once to enable the camera bootflag, once this is enabled it will stay enabled until you run that FIR again to disable it. The new second FIR file will **only** make your card bootable, it won't touch the camera bootflag. so, this just makes it easier to set up a card for ML.

Great - Thanks.  That second FIR makes life easier for people that struggled with making cards bootbale before.

Walt
 

64
Camera-specific Development / Re: Canon 5D Classic Firmware ** Beta 2 **
« on: September 26, 2012, 07:40:03 PM »
Andrew, now that there are 2 FIR files is this line still valid in the installation instructions.

"Download the zip file from the link below, unzip all of the files to your CF card."

It loads both FIR files together?

Walt




65
my SN is 0430103136, it's a newer version?

Ones that start with 0 should work OK. But there is pretty much no functionality as this version is just a very preliminary beta-test.

Serial numbers that start with something other than 0 (like mine starts with a 3) it locks up my camera and the back buttons don't work any more.

So it looks like it works on yours (I assume the back buttons work OK) but theres not much in the menu right now.

You'll have to wait until they develop the functionality more and figure out why it doesn't work on the newer models.

Walt
 
 

66
Hi

in my 5Dc I'have only this menu: Shot, Prefes, Debug, Help and I'can't understanding the cause.
You can help me?

Ciao
A.

ps: sorry for my very bad english

Whats the first 4 numbers in your serial number?

This firmware doesn't work on newer versions of the 5Dc. You should probably uninstall it. Its only in beta test right now.

Walt





67
http://chdk.setepontos.com/index.php?topic=8550.msg89435;topicseen#new
Does anybody else have firmware 4.1.0?

Never heard of it.
The instructions say you need to be running 1.1.1 - 3 times!!

68
Hi guys!

Before I do it - anybody know how to do if my firstfive will turn to brick?  :)

Just remove the battery and card from your camera, format the CF card, put battery back in, put card back in and boot it.


69
Andrew needs to answer your question but I think having multiple ML versions on a card that moves between cameras will cause problems - not the least of which is a difficulty in troubleshooting anything.

Especially a beta-version.

Walt

70
Just tested and same issue here as well:
1. Installing and Solid blue light
2. no rear inputs would work, no info in viewfinder. Buttons WB/AF/ISO working but shutter didn't
3. Removed battery put in regular card (ML 50D installed on it) didn't work
3. Removed battery put in regular card (without ML installed), worked fine. RELIEF! I thought the cam died!!!!

However,
- CF-Card with ML 50D installed still works in 50D but not on 5D
- CF-card without ML works on 5D (big relief) and on 50D
- CF-Card I used to install ML 5D seems dead on both camera's :-(
My question is how I can reboot it and make it work again or is it destroyed? Please help :-)


Serial: DS126901 3431300439

I'm confused as to why the ML 50D is part of the discussion. Did you think it would work with the 5D?

To answer your question, I formatted the card I used to install the ML 5D (with my PC) and all works fine now.


 

71
Just downloaded the latest version of the SDK (ver 2.11) and I see that only models after the 40D are now supported. For the 5D and XTi (the ones I use) it says "Remote Control may work but not supported".

I've got all the earlier versions stored away (that do support the 5d) and I'll dig them out and see if there are any differences where you have to handle the older and newer versions of the 5d differently. There are a couple of sample programs that may provide a clue.

Walt

72
What can you do with the EOS SDK?

Its the "official" Canon authorized way to write software for the EOS cameras. You can write software that controls the camera and downloads images - like Zoombrowser and EOS Utility.

But you can't add new/hidden features like ML can.

 

73
It looks like if your serial number starts with something less than 093, then it will work for you. I just don't get what could be different between 5d classics to make ML not work, if they all use the same firmware version / updates :|

talk about a headache..

Heres a thought. I use the Canon SDK to write EOS apps and don't quite understand the difference between how that works and how the ML software works. But heres an idea.

If we could write something using the SDK that queries some camera settings and writes to the logfile. We could run it on the old models and the newer models and see what the difference is.

I could write the app but I have no idea what camera configuration settings to look for.


Make any sense? At lease the app could run and connect to the camera and not hang up. Just not sure what we could look for.

Walt


74
the problem is this isn't an issue on any other camera, so nobody knows how to fix it (basically how it's been the entire time porting to the 5dc...)

I like your earlier thought

" I need to figure out where the boot process is being held up at in newer models."

Maybe build a version with debugging output for all the boot process actions to a file on the CF card and one of us with the newer model can run it.




75
Alex/Coutts - if you want any more testing done - let me know.

Pages: 1 2 [3] 4