Messages

So you'd have to solder to those pins, they are there in my grip making contact.

Hmm. Moreover this RX-TX signals go to the battery slot from main board, so may be soldering to the mainboard (e.g. near the appropriate connector) would be easier. But I don't want to solder to the cameras pcb.

Please correct me if I'm wrong, you write that you have the grip that has the middle contacts missed in the original Canon grip?

the 5D repair manual says its pins are those:

(middle two rows, maybe meant for grip)
BATDOOR
AFSEL
LGSEL
SW1
SW2
DIAL1
DIAL2
VCHKON
AELOCK
BATSEL1
BATSEL0

(outer rows, maybe debug)
TXDMPU RXDICU
TXDICU RXDMPU
MON1 MON3
MON0 MON2

Thanks a lot! Now I see that 5D middle row pins are used by the grip, and outer rows (with smaller contact point) are unused by the grip.

hehe, 4 pins only? USB I hope?

50D has extra pins the grip doesn't go to.

Hmm, camera body already has one USB connector.
More over USB uses point-to-point channels, so you can't easely duplicate the USB connector pins in the battery slot.

Moreover in this situation there is no need of 4 pins for USB as there is no need to use USB interface for power supply.

wow, very cool.
i am not sure how we would merge this into Magic Lantern, but i like the idea a lot.

the only VERY practical thing i can think about is building an abstraction level to select the ML version to boot.
depending on the camera model and firmware version it loads the specific ML version.

We already actually merged some stuff from barebox into ML

There are many things that can be imported from barebox into ML, but not only the code running on camera. E.g. barebox uses scripts for incoming inspection of patches. This scripts decrease the number of errors in souce code and make the developer's life easier. Just now I'm working on incoming inspection scripts for ML.

Nice job.   
Please correct me if I'm wrong, is it for using the ARM as a "bare metal" platform?

Yes, you are right.

Barebox is something like busybox, but for bare-metal

I have seen some materials in the ML wiki, and in the CHDK wiki about camera' hardware. Appearence of barebox on DIGIC can make hardware investigation more comfortable. IMHO it is possible to use barebox for easy uploading ML/CHDK image into the camera without memory card manipulations.

Here is the image of Canon EOS 600D battery slot and the image of top part of Canon BG-E8:



You can see that camera body has 16 connection points for grip pins, but battery grip has  only 12 pins. The 4 central connection points are unused by grip.

Does anybody know how this 4 central connection points on the camera body can be used?

I have examinied Canon EOS 1100D camera, the situation is the same --- the camera body has the connection points unused by the grip.

Subject: barebox bootloader for Canon cameras announcement

Barebox (formerly known as U-Boot v2) is a awesome
bootloader for the ARM-based boards (see http://www.barebox.org).

There is a very initial support for Canon cameras in barebox.

Supported cameras:

* Canon PowerShot A1100;
* Canon EOS 600D;
* Canon EOS Magic Lantern qemu-based emulator.

Just now barebox for Canon cameras is a demo
but after some improvements it can become very
handy tool for CHDK and Magic Lantern development.

Announcement and instructions in the Barebox maillist:
    http://lists.infradead.org/pipermail/barebox/2013-August/015820.html

Barebox with Canon DIGIC support sources:
    http://github.com/frantony/barebox/tree/next.digic

Your comments and questions are welcome!

The ML is not trivial software.
Adding a new feature for one platform
can break build for another camera.

To prevent the problems like this some techniques
are developed.

E.g. here is a quote from U-Boot's General Patch Submission Rules
  http://www.denx.de/wiki/U-Boot/Patches

Before sending the patch, you __must__ run
the MAKEALL script on your patched source tree
and make sure that no errors or warnings are
reported for any of the boards. Well, at least
not any more warnings than without your patch.

I have just made a relatively small and simple
script make-all.sh. It just builds
ML for all platforms. Also it quickly builds
documentation. At the final the script prints out
the statistics so it's easy to find a broken platforms
(if any): see the 'target failed to compile' field.

The script on bitbucket:

https://bitbucket.org/frantony/magic-lantern.makeall/commits/52a7be8070fbc52e73d0c2536467c648a201df6d


USAGE:

Code Select Expand


$ cd magic-lantern
$ make allsupported

...

make[2]: *** [shoot.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [100D] Error 2
FAILED
Compiled in    2s
Building  docq
OK
Compiled in    7s

===================== SUMMARY ============================

compiled in   50s
targets with warnings or errors: 18 ( 40D 50D 5D2 5DC 60D 7D 1100D 500D 550D 5D3 600D 650D 6D 7D_MASTER EOSM 700D 100D docq)
target failed to compile: 4 ( 40D 5DC 700D 100D)
make: *** [allsupported] Error 4


Please reply to this request!