Messages

Good indeed. Thank you!

That's weird.
From what I remember from 400D, you can delete the autoexec.bin and the camera boots it's Original Firmware w/o problems. But I could be wrong.

I guess it wont get out of beta.
Anyway, from what you described, it seems that the camera (software) really is locked up, and you had to pull out the batteries to reset it.
I wonder what could be the reason for that.
I don't think there are different hardware versions of this camera, but who knows. This could be the reason.

Can you try enabling the bootflag, then put the autoexec.bin (i'm using the same from the first post) and see if it works with it?
I never tried to start the camera w/o autoexec.bin.
This could be the problem? The camera is old enough, that it could not turn on w/o the autoexec.bin and bootflag enabled (though I doubt it).
Never tried to start the camera w/o the autoexec.bin, but if this is the problem, then the disabling of the hack should be done with turning of the bootflag, instead of formating the card (as I suggested earlier).

This is just out of curiosity, you dont have to try this if you are worried about the camera.

BTW, Alex or other dev could have more info on this.

It was a different problem there, not like what you've experienced, though I never had problems with 5Dc.
Anyway, the point is that you can use the hack relatively safe. In case of a problem (like your's, though I suppose there were more factors for this), you can always replace/format the CF card.

As I said, I do not know of bricks and I do not see a way of bricking the camera with the hack.

but beta version seems a bit risky, and it's my only motivation to install ML...

Just to clarify this a bit.
The version is beta, since it never came to fully ported ML.
But what's in there (thanks to Alex and Coutts) works as expected and AFAIK there are no reports of any brick by this hack.
And to say the truth, I do not see how can this hack damage your camera.

I have it installed from the moment it was released.
It is true that I do not take photos with the camera, but my wife shoots with it at least once per week and it takes few hours of shooting a photo session in studio.
I believe it's something like 150-200 photos per session (week)

So far the camera works as it should.

I was supposed to continue the port long time ago.
Sorry to disappoint, but it wont receive attention from me, at least anytime soon.

I haven't took a photo for almost 2 years. You can guess how much time for hacking I have
Besides the camera is VxWorks based and ML is for DryOS cameras mostly, not that it's impossible to port some of the goodies, but 5Dc wont have much of ML anyway.
I'm not sure how much interest receives this camera either.

If I have the time for ML (which I dream of), I would probably move to some newer camera, thought they are already full of goodies (most of them).

If you want to deactivate the hack, just delete or rename the autoexec.bin file ...
It's not a good idea to reflash the original firmware again, since you're already running the very same firmware...
It's not a good idea to deactivate the bootflag and activate it all the time, either.
Just rename or remove the autoexec.bin, or format your cf card and the hack will be gone.

This sounds like the brainchild of a person begging for work, and the admin should probably delete this thread.

Keeping it here will do better, for any further attempts to make money from ML.

[(expressing my opinion only, as usual, this may or may not cover with opinions of other ML members)]

(expressing my opinion only, as usual, this may or may not cover with opinions of other ML members)

First I should say, krashnik has some points about licensing IMO. But that's all of it.
Everything else sounds like an attempt to commercialize the project.
And some of us remember the last talk about this.

I didn't look through the code thoroughly ...

They have done a great job up until this point, though it is still an amateur piece of code with inadequate licensing and maintenance to really hold standard in a larger marketplace.

So you haven't done your homework to check the source, but still consider it as an amateur piece of code ? Inadequate maintenance ? Marketplace ?
First you should checkout the code, if you're developer, then we would be interested in hearing your opinion. If you are not, then probably you're not the one to give such definitions.
I'm not saying that the code cannot be better than this (different devs, different approaches). But you're telling me that the salt is sweet, only because you do not know what salt is.

If we treat it similar to the Android system, we could theoretically have a platform for future chipsets to run only on MagicLantern Firmware.  This would allow a complete different open-source camera system to adopt ML into it's hardware for a truly 100% open-source platform.  This can't happen on the random hours the current coders are putting into this software.

Why do you compare Android - an Open Source project, based on other Open Source projects (Driven by a huge corporation and advertised) with ML - Open Source project based on proprietary work, which is undocumented and reverse engeneered. A totally hostile environment for new devs, unless they have the courage to stick for it long enough. To me this is not real comparation.
To make ML work on a different hardware (other than Canon's) would not be possible ATM, since it's all based on their hardware and their OS and APIs. Not sure ML will ever be something else, but who knows.

Whether we like it or not, writing code takes money.

I totaly disagree with this. Whenever I can, I help other open source projects. This costs nothing to them, neither to their users.
To me it's like a hobby or more like an religion, but that's me.
All the devs here are not doing it for money, neither users pay for it.
The code might cost in business, yes, but this is something diffrent and you should have realized it so far, since you said you worked with open source projects.
Most open source projects are driven by ppl wanting to give to others, not to take from them. Even these that sells support after that. Enterprise linux distributions, OpenERP, Kolab, Proxmox, etc... All they give, not take. If you are not able to go by yourself, then you can pay for support, but you're not forced to.

Dedicated Servers to host ML website: $2,000/year
Redesign responsive website: $4,000
How-To Tutorials for beginners: $10,000
Funding for 5 programmers to treat this as part-time job: $50,000 = $10k/year per programmer. 
Distribute the $50k to the top 5 programmers who work on this code which will allow them to buy cameras and completely take them apart, completely obliterate CF/SSD controllers, etc.

I'm not sure how much costs ML's Dedicated per year, but the other prices seems a bit high to me ?!?
I'm living and working in Bulgaria. In my "free" time, I work my ass for extra.
If I could ask $4k for redesign, I would work 2 hours a day in total.
I'm not saying this is unreasonable price whereever you live, but believe me, there are much cheaper experts around the world.
Documentation and tutoruals are written by ppl wanting to share their free time, just like the devs. As it was mentioned in some post above, this makes these ppl feel themselves significant, because they are significant!
Paying someone $10k will do some good documents for few months, then you will have outdated documents for years (because the volunteers are not around anymore), unless you keep spending $10k for documentation.
This is more than acceptable in every business mode, since there are no volunteers there, but here it's different.

The most harmful thing for this project is to start paying to any dev !
This was discussed already. Once you give someone money to work on this project, all the other devs will leave you. No new devs will be available, since it's hard to enter this environment. The project will slowly (or not so slowly) die!

We need to step away from the mindset that ML is a garage/basement project and realize that it is currently ranked at 59,000 on Alexa, has global coverage with top magazines and reviewers, and is being used by filmmakers worldwide in commercial productions.

We're essentially sitting on a multi-million nonprofit educational open-source platform that just needs the right management to standardize how it works. 

The project is that BIG only because it is not commercial ! Once you make it commercial it will be ruined.

Yes, I am a businessman who enjoys helping charities & philanthropic efforts.

To me you look more like a businessman, who seeks oppotunities. Nothing wrong in that, but this project should not be comercialized IMO !

I haven't seen other contributors here who are programmers in the Silicon Valley area.  Maybe that is why everyone thinks it has to be garage style to still be "for the people."

I'm not sure I'm getting this right, but this sounds offending to me.
If you're looking for programmers which you can enslave and squeeze for few years, perhaps you should really go to Sillicon Valley. We already know few "good" companies comming from there, should I point them ?

If you look at other large & successful open-source projects, they handle their work slightly differently. Think wordpress, eclipse, kaltura, android, chrome OS, etc. These are all open-source yet still bring in funds to help their beloved programmers & their vast communities grow.

I already mentioned few open source projects above, as I mentioned that ML is quite different from other OS projects and if you want to compare it with other projects, you should find some worthy for that.

#1: magiclantern.com - not .fm - this will be the for-profit side of the business where people can hire programmers to help them install magic lantern in all of their corporation's cameras, etc. 

Hire programmers ?? Go to freelancer.com.
Profit ? I do not need troubles with Canon. Count me out of this as soon as you start taking profit of this.

#2: Get a board of directors & rectify a nonprofit.   anyone on the board will not be allowed to accept any money - they simply oversee decisions & stand behind the mission of the nonprofit.  elect a board who has ML's best interest in mind who have diverse talents such as programmers, filmmakers, marketers, and businessman.

And loose all the devs and kill the project.
ML is not business, neither a profession. It's a hobby and education project.
We learn by ML, then we monetize our knowledge in business.

#3: Do outreach with ML and partner with Canon.  Once ML becomes a 501c3 nonprofit, Canon can make tax-deductible donations to the ML crew.
Also, I'm sure Canon would be happy to hire programmers from the ML crew & can create a happy cohesive environment between ML + Canon.  ML can be a training-ground where anyone can learn Canon firmware & if they really excel, they get picked up by the R&D department of Canon.  With $500k funding, non profit status, and a board of directors that sets this structure up better - Canon will happily start doing business with & welcoming the ML community a lot more.

I see another ending of this movie, we all know what it is. There is no reason for Canon to cooperate with us, is there ?




Before I finish the post, here is a quote from hirethestache, which express my opinion in short, which I couldn't say better.

Or dont change what isnt broken. Please quit trying to monetize ML. As soon as you bring money into the game, you introduce power struggles and inequality.

Tutorials are already being made on a daily basis from the users, for free.
The website is already perfectly (albeit slightly clunky) functional.
The general public feels like it is a part of something big, because it is free and completely open-source.

One more thing you should consider before your reply. I'm not a businessman (at least not like you). My point of view is different and it does not include ML as business.

[1ds mark2]

Does anybody know or has tried to run ML 5dc on a 1ds mark2... I really love this camera for its files, they look so 3 dimensional, to me offcourse.. But the menu on this piece of machinery absolutely stinks, also the lcd wich is is tiny, much tiny-erer then the 5dc, so being able to check focus with on press on a button would be sooo welcome. So could I try running ML 5dc on my 1 ds or would it not work for sure. After all they are made practically at the same date and the menu looks so a like. Any help would be appreciated!

ML for 5Dc is for ..... 5Dc !

I would say that there is a risk of bricking the camera if you try to activate it with .fir file for different camera, or try to execute AUTOEXEC.BIN from a different model.

AFAIK, 1Ds mk2 is not in the ML targets, I think no camera from 1D line is in ML targets.

There are beta versions already, read the first post in this thread. Scrax is preparing the next beta5 version, which will be available soon I guess.

Off-topic, sorry for posting this, call me superstitious or naive, but I do not like my post count staying on 66.

Export the hg diff, we can pull his repo to the main via bitbucket anyway

If you want me, I can merge scrax's diff and sync to latest ML, before you pull. Though it's not worth pulling my repo may be, the job is not finished.


EDIT: I see scrax is going to handle it.

I've just tried to pull from source repo to your repo and merged them, added those dummy things and now it can load and I'm enjoying the new menu layout

Nice, would you pull-request so I can merge it into my repo. It can save me some time when I get back to it.

The beta4 was compiled from Unified by Alex, but way too many things changed since then... One of the first changes was the boot procedure. This is the reason, which prevents you from booting it correctly right now...
I were trying to fix the booting, but it still needs work. In my repo you can find the local_entry.S which is the old entry.S from 5DC (made by Coutts), but I had made some modifications to it (cant remember what and where).
Basically 5Dc will not boot normally in the current ML source, even if you compile it. Not in this shape at least.

I will have few free days after Tuesday, since we are Orthodox Christians, and we have 1 week calibrations now.
I will try to sync my repo with the main-stream ML.
So if anyone is interested, it will be easier to take over from there (and try to finish the cache-hacks boot method)

EDIT:
Just read the last post from scrax, how you booted it with cache-hacks or with your local entry.S ?

EDIT2:
Sorry, just saw in the ML repo that the entry.S is still there, I dont know why I were thinking that it were removed long time ago...
But still IIRC (which I doubt already), there will be problems with booting it, because of the CPU initialization, I had to modify some parts in entry.S to fix this (but again, I may be wrong).

Thanks for doing this!  I notice that when I format my card in my 5D, it erases the ML stuff as well, so I have to re-upload the files to my card each time.  Is this how it works?  I also use Magic Lantern on my 5DII and can format in camera, so I worry I'll be constantly erasing my ML install on my 5D cards.

Yes on 5DC format is erasing all stuff on the card. This may change in future, but no guarantees.
Better use "Erase All" when you want to empty your card.

Hi.
I'm currently busy with other projects @ my job. No work is done for 5Dc from me ATM.
I have plans to return to 5Dc, but cant say when. Hopefully in the summer.
The progress in ML is far from this port now and there is a lot to be done.
The porting of the boot method is almost finished, but still has some problems.
Once it's done I guess the port will be easier to be maintained.

I do not know of other dev working on 5Dc ATM. Please feel free to take over.
Here is my work on porting the boot method (cache-hacks): https://bitbucket.org/0xAF/magic-lantern-5dc-port-wip
If anyone is interested, please contact me and i will explain in depths where i got stuck.

If you want to use ML on 5Dc please use the latest beta4 from Alex. It is stable for daily usage. My wife is happily using it on my 5D for long time now.

Unfortunately no references about this errors... could you share a log of yours?

I do not have the camera with me ATM, but I'm sure there should be no errors on a working camera.

Thanks 0xAF, A1ex!!!

So now, just wondering how should i proceed after booting with new autoexec.bin on card...

1) Take Pictures until buffer fulls, and then, while on busy mode, go to ML menu and execute -> don't click me
or
2) don't click me -> Take pictures -> wait for dump

How big should i expect the file from a dumpf? how much time aprox to write it?
by the way, on benchmarking card, how it behaves to other members of the board? everyone with the same results as me with unfinished 4th phase?

I dont know how should you proceed, just do few experiments and read the log. Try to find what's wrong from the log.
The log  will be few tenths of kilobytes i think... but cant remember exactly.
Writing it to the card should take no more than 2-3 seconds i believe.

btw forgot to say:
when you click the "dont' click me" it will wait 10 seconds (as Alex suggested), then it should beep to indicate the starting of the log dump, then beep again when it finishes. Basically you should hear 2 beeps.

pd2: So I should compile an autoexec.bin with the code you wrote in "don't click me" class... but i don't find how to on windows... any chance you could pm the autoexec?

https://www.dropbox.com/s/5xxgrbytppf3xk3/autoexec.bin

I did not tested it (camera not with me ATM), but should do what you need.

Right, that's why so many people were hiding things by mistake

(and customizing menu is more like "set and forget", no?)

count me in, when i first took ML in my hands (i think it were when Alex handed it to me), i clicked here and there ...
then later when i was @home, i was wondering where the heck is that thing that i saw before ...
took me some minutes to find out that i can hide/show stuff from the menu...

i think it should be harder to do that, not as easy as it was with me

@0xAF I think you have to add me (600Dplus) permissions for pushing to your fork, I have no writing permission on the main tree, but I can submit pull request to you fork I suppose like on the main tree so it's not a problem for me and maybe is better so you could check what I did also.

Yeah. Perhaps it's better to fork it from me and send pull requests...

Had tomale some changes to compile the tree version don't boot, the 0xAF fork boots but with few different things from beta 4, now I'll try to enable some recent features to see if they works, first of all GUI event
?

The 5DC in the master repo is broken. Even the old boot method wont work. I suspect it's a problem in the initialization of the CPU, that's why I still have problems with the cache boot method. The CPU hangs after specific amount of time, whatever I do...
I made changes in the old boot method (the original init code) to make it boot. These days I will try to find what were changed that prevents the original init procedure... I hope if I fix this, the cache boot method will work too, as it seems the cache hacks are working, but the camera still hangs somewhere... strange enough.

In the meanwhile, use my repo, until these problems are fixed. I will push the the master once it's ok.

BTW, just updated with the master, please pull again.


EDIT: if you need to push to my repo, please go ahead, I think my repo is inheriting the master's repo user permissions, you should be able to commit to my repo too...

One more thing, we should distinguish between features not done and features impossible.
And perhaps put different icons for impossible and not done in the table...
If 5Dc had all that it can it will still look poor on features compared to other cameras. So the rest features should be marked as impossible.