code you HAVE RUN on your dslr

  • 141 Replies
  • 37014 Views
  • Publish
    Re: code you HAVE RUN on your dslr
    « Reply #70 on: 26 / May / 2008, 15:16:20 »
    Advertisements
    I have the 400D and inside the battery compartment there are a total of 16 contacts. These 16 contacts are divided into two banks of eight each. Looking at a picture of the battery grip (which I do not own) http://farm1.static.flickr.com/159/362241002_e027d93d53.jpg?v=0 there are 12 pins used. The inner row on both sides of the compartment/grip are filled, this leaves the two foremost and two rearmost outside contacts unused by the grip. Note: the grip does provide some functionality in addition to extra battery. Here's another image http://www.bhphotovideo.com/images/largeimages/458075.jpg

    So looking down into the battery compartment with the lens facing away and the lcd towards you, you get:

    ++   + -
    ++   + -
    - +    ++
    - +    ++

    Plus means used by the grip, minus means not used by the grip. So perhaps these four contacts are for debugging?

    Hope this helps.

  • Publish
    Re: code you HAVE RUN on your dslr
    « Reply #71 on: 26 / May / 2008, 15:22:28 »
    Also, I'm not sure how similar the 300D and the 400D are but here's an interesting thread with some debugging tips - all related to the 300D however:

    CANON EOS 300D Digital Rebel Firmware Hacking Forums -> The 300d debug port

  • Publish
    Re: code you HAVE RUN on your dslr
    « Reply #72 on: 26 / May / 2008, 16:37:24 »
    my problem with the above-battery pins is very simple - I tried some methods to connect to them - and nothing worked. I tried to make a fake battery with connectors - but I can't make (or buy) connectors that are on springs - like the litle connectors on top of the grip. I tried it couple days ago.

    WARNING: don't try to use hard pins or wire endings. the flat connectors on the bottom of the battery compartment are fragile - you can deform them - I tested - you don't have to.

    *

    Offline DataGhost

    • ****
    • 314
    • EOS 40D, S5IS
      • DataGhost.com
  • Publish
    Re: code you HAVE RUN on your dslr
    « Reply #73 on: 26 / May / 2008, 16:50:33 »
    Also keep in mind that (also because someone said it in that article above) the camera likely operates at TTL, which you should NOT hook up directly to your computer, either device might (will) break.


    *

    ASalina

  • Publish
    Re: code you HAVE RUN on your dslr
    « Reply #74 on: 26 / May / 2008, 17:32:19 »
    Also keep in mind that (also because someone said it in that article above) the camera likely operates at TTL, which you should NOT hook up directly to your computer, either device might (will) break.

    Yes. I've been looking at the data sheet for the MAX-232 IC. It is very simple to hook up. The hardest part is to make something that will make contact with the tabs inside of the camera. I have a small machine shop in my garage for making small parts. I'm very tempted to get a battery grip and use its pins in a plastic thing to duplicate the battery grip that I would make in the shop. That would be a last resort, though, because it would be dangerous to the camera.


  • Publish
    Re: code you HAVE RUN on your dslr
    « Reply #75 on: 26 / May / 2008, 18:10:59 »
    That why I wrote the driver. Now I'm reading what's camera is writing without connecting anything wierd to my camera in real time :-)

    I think that camera have a debug level mechanism and I think I know where. Problem is it's initialized after my code leaves. Some of the log have too small level to write out. Another target to get to.

    *

    Offline Seklth

    • **
    • 54
    • 400D
  • Publish
    Re: code you HAVE RUN on your dslr
    « Reply #76 on: 27 / May / 2008, 01:31:14 »
    you see bootloader fot find other (re)start code?)

    *

    Offline _MAG_

    • *
    • 47
  • Publish
    Re: code you HAVE RUN on your dslr
    « Reply #77 on: 27 / May / 2008, 01:33:56 »
    You can see what adress in mem writes every default value(--- Change OLC --- block)?
    i sink when OS in camera load this data maybe changed (need check this if you can)...


    ryanpg  - i post this link in EOS Lens protocol analyse - anybody intresting? topic.

    i found info - need to connect comparator, but i dont know why they need. For analyse pins need osciloscope before you connect something to you PC. If you do something wrong - you camera dead.


    « Last Edit: 27 / May / 2008, 01:48:47 by _MAG_ »


  • Publish
    Re: code you HAVE RUN on your dslr
    « Reply #78 on: 27 / May / 2008, 07:06:24 »
    you see bootloader fot find other (re)start code?)

    Actually, I didn't find any thing usefull in the bootloader, yet. I don't know what code (firmware or bootloader) is runned when the battery is closed.

    You can see what adress in mem writes every default value(--- Change OLC --- block)?
    i sink when OS in camera load this data maybe changed (need check this if you can)...

    The values printed in the OLC are properties changed and stored by "PropertyServer". It's an instance and it have interface like "GetSomething" "SetSomething" "LoadSomething" "SaveSomething" - And the last two of them are for writing and loadin it from the 3V memory I think.

    That's for answering, now for my findings. For those of you that work on 400D, I have a big present :-) Full (debug level=1) log from the loading until state 0x40, and then pressed jump, menu, trash, jump, and others. Only jump(162) and trash(165) are making any effect. based on the earlyer logs I found the place where keys are made the messages for MainControll (T=2). But I can't find why and where are the other keys blocked !? It's now the most important thing to find, becose if I could unblock them, I could do something usefull and dump the logs.

    The full log is in the attachment

    EDIT: log changed. thanks _MAG_ :-)
    « Last Edit: 27 / May / 2008, 11:09:33 by owerlord »

    *

    Offline Seklth

    • **
    • 54
    • 400D
  • Publish
    Re: code you HAVE RUN on your dslr
    « Reply #79 on: 27 / May / 2008, 10:36:58 »
    > I don't know what code (firmware or bootloader) is runned when the battery is closed.
    Of course bootloader) bootloader have jump to firmware.

     

    Related Topics