interested in a 50D initial port of Magic Lantern ?

  • 1148 Replies
  • 132959 Views
  • Publish
    Re: interested in a 50D initial port of Magic Lantern ?
    « Reply #10 on: 06 / March / 2011, 15:47:05 »
    Advertisements
    Pel,
    do you have 'orange box' ?

    Indy

  • Publish
    Re: interested in a 50D initial port of Magic Lantern ?
    « Reply #11 on: 06 / March / 2011, 15:53:55 »
    Yep.

    Update file
    cannot be found.
    Please check the memory
    card and reload the
    battery and try again.
    « Last Edit: 14 / March / 2011, 16:25:15 by Pelican »

  • Publish
    Re: interested in a 50D initial port of Magic Lantern ?
    « Reply #12 on: 06 / March / 2011, 16:06:03 »
    Pel,

    Try this, using 'update'.

    Indy
    « Last Edit: 06 / March / 2011, 16:20:14 by arm.indiana »

  • Publish
    Re: interested in a 50D initial port of Magic Lantern ?
    « Reply #13 on: 06 / March / 2011, 16:06:58 »
    double check your firmware version is 1.0.7 !


  • Publish
    Re: interested in a 50D initial port of Magic Lantern ?
    « Reply #14 on: 06 / March / 2011, 16:18:45 »
    If this not work, try this one, it should be better.

    Indy

  • Publish
    Re: interested in a 50D initial port of Magic Lantern ?
    « Reply #15 on: 06 / March / 2011, 16:25:15 »
    The first magiclantern worked, camera rebooted and a white on purple text showed on the LCD for a tenth second then CF led turn on, camera freezed.
    Reboot, sensor cleaning, white text on purple background 3 lines, empty line, 1 purple line for a tenth second.
    Camera works normally until the first expo, then ERR80

    Edit:
    Second autoexec.bin boots normally, nothing happens
    In the Canon menu there are two extra lines.

    Camera frozen.

    Reboot, sensor cleaning, some purple lines (still to fast to read).
    Menu sometimes start, sometimes not and camera freezes.
    Expo makes ERR80

    No .log (or .bin) file created with nor the first .fir. neither the second one.

    Edit:
    If I press the menu before ML starts I can see the purple lines:


    « Last Edit: 06 / March / 2011, 17:03:33 by Pelican »

  • Publish
    Re: interested in a 50D initial port of Magic Lantern ?
    « Reply #16 on: 06 / March / 2011, 16:34:28 »
    remove the battery and try the 2nd one.
    do you have a log file and a bin file created ? could you send me log file ?

    menu won't work as gui_main_task() code must be like 5dm2:
     https://bitbucket.org/hudson/magic-lantern/src/fecb7a724424/gui.c
    and not 550d / 60d style:
     https://bitbucket.org/hudson/magic-lantern/src/79feec857621/gui.c

    Indy

  • Publish
    Re: interested in a 50D initial port of Magic Lantern ?
    « Reply #17 on: 06 / March / 2011, 17:18:33 »
    I wish I can do this test with my 7D... :)
    « Last Edit: 06 / March / 2011, 18:17:54 by Pelican »


  • Publish
    Re: interested in a 50D initial port of Magic Lantern ?
    « Reply #18 on: 07 / March / 2011, 01:27:08 »
    The bootflag is now set since autoboot is launched. Did you try the 2nd fir ?  I'll compile another version tonight.
    Indy

  • Publish
    Re: interested in a 50D initial port of Magic Lantern ?
    « Reply #19 on: 07 / March / 2011, 10:34:47 »
    Yes, I tried both .fir files and none of them made any log or bin file...
    I've made more test with the second autoexec.bin:
    The camera starts, during the sensor cleaning the ML text shows for a very short time then disappears.
    The camera works until I fully press the shutter button -> ERR80 (remove battery helps only)
    If I press the menu button -> menu shows and ML text on the top of the menu (see the screenshots), the LCD freezes (menu, info, play, pict modes, func not responds) but the front and rear wheel, the WB, AF, ISO, half shutter buttons work.
    If I press the play it shows the last picture and the ML texts and same happens when the menu button press. Same happens with Function, Picture Style, Info: once a display shows something then the LCD freezes.
    If I change a mode (like Av to Tv) the camera freezes temporarily but after the metering timer finish then works again.

     

    Related Topics