Messages

btw: is there some kind of Magic Lantern test suite / runbook that allows to verify all functionality to ensure completeness / hunt bugs or gaps on 100D.100B?

Walter: doesn't work the issue is with the NVRAM.
a1ex: hey man sorry for disappearing so long; after getting stuck with the task handling/scheduling I allowed the rest of my life to take over ...

I guess I first need to get back on the horse again - how do I sync up with 100D development?

The code doesn't seem to be in the mainline repo (yet), so I guess you're working off https://bitbucket.org/niklastisk/magic-lantern, correct?

how do I get the right ARM gcc etc?

doesn't make any difference, "MAIN_FIRMWARE flag is DISABLED!" keeps showing even on new card (where I have to set EOS_DEVELOP and BOOTDISK for it to work).

perhaps this wasn't clear: ML works in both cases, I just can't get (back) to a state where I can use a card without ML

I got the bootflag set during some experiments a few years ago, and don't know how to reset it (anymore).

You've seen https://www.amazon.com/Fotga-power-adapter-ACK-E15-coupler/dp/B00F5VMIQS? Maybe using some other power source with that adapter would work.

Oh wow awesome.

Had to put porting to 100D aside for a while after getting completely stuck, only to come back to see someone else suceeded! \o/

a Hero Member indeed!

Testing it on 100D.100B, Firmware Update says "MAIN_FIRMWARE flag is DISABLED!", whatever that means. "Please contact ML developers for a fix." ... hereby doing that

(Firmware -1, Bootdisk -1, RAM_EXE -1, Update -1)

Some time in the past I seem to have enable the boot flag (with the help of Alex), now I can't use the camera without an ML SD at all, I'd love a fix for that, too

Great work, we'll test more!

   count

Hi,

sorry for dropping the ball on this one in the past ...

The main problem isn't that there are two different firmware versions (the differences are small enough), but rather the fact that they changed the task structures and the scheduler quite a bit. I kinda gave up when debugging turned unreasonably painful because of the inability to debug that easily using the qemu port. That situation might have improved noticeably.

I'm not sure I'll find time to hack away at this anytime soon, but the differing firmware are less of an issue than the necessity of a lot of try & error to find out how scheduling works now; and what structures need to be access / piggy-backed to make ML work as expected.

   count

Hi,

please contact me (count on freenode IRC, also on #magiclantern) to see whether it's of any use just now. We'd do a blind dump of your firmware image to see whether yours got the same checksum mine has. So far, I've seen two different 1.00 versions, but only one user with the same firmware I'm developing against).

Task management code has changed noticeably compare to other cameras, so it might still take some more time until we even got the ML menu. I can only invest a few evenings a month, so progress is slow.

   count

did anything further come from this? i.e. do we know how to talk to an EOS via JTAG?

   count

What Marsu said.

Rolling up sleeves for another night of hacking now ...

   count

Speaking of good news:





   count

P.S: For those interested - the code is at https://bitbucket.org/berlincount/magic-lantern/commits/all

Hello,

some updates: with help from alexML and FoolsTP I was able to gather what I need, so something is going on here. LED location is the same as on 5D3, and we might be seeing "Hello World" or more some time this week, pending identification of more function entry points for the 100D (found a few thousands, identified only a could dozen so far). slow work, but there's some movement at least.

   count

Well, the current progress I'm seeing doesn't pass my build chain (compared to other platforms), as several maps and defines and #ifdefs are missing; but nothing catastrophic there. Judging from what I'm seeing there it doesn't feel like there really was a firmware at hand; and I'd love to be able to have a look at the objdump myself, and see how I can help.

Knowing other firmwares would of course help finding commonalities to identify entry points, but I know my C and my Linux and have a camera at hand, so I'm definitely willing to try ... considering that the 70D is showing "hello world" & more is giving me a certain amount of hope in either case. Guess I'll have to look for the code for that, too; it's not in the main repo (yet).

Any specific person to talk to on IRC, anyway? I'm "count" on Freenode.

Cheers,

   count

I try to :-) ... it's just that if you read the thread you should have a clear understanding what is required to get a port working, if still in doubt look at the neighboring 70d thread that recently has found a maintainer.

it's just that if you'd just read my actual post you'd be aware of me asking specific questions to (help) continue exactly along those lines

to repeat: somebody managed to dump the firmware using a non-standard approach, but apparently the files never made it somewhere; no was I able to find documentation for that process. if somebody explains the process I'd dump the firmware myself; so it should be possible to continue from there.

I'll have a look at the 70D thread now, too.

   count

Don't pray, code!

funny man. I've offered to help, and would already have invested a few hours if somebody got back to me.

   count

Hi Glen! Did any one manage to send you the files by any chance?

If not, or if additional firmware images are wanted, I can (try to) provide dumps for my (german) 100D.

I'd need to know what dumper tool to use, and where / how to drop the file(s)

   count