« previous next »
Pages: 1 ... 3 4 [5]

Author Topic: Porting ML to XSi (450D)  (Read 108804 times)

Ant123

  • Contributor
  • Member
  • *****
  • Posts: 175
Re: Porting ML to XSi (450D)
« Reply #100 on: July 21, 2020, 10:39:09 PM »
Tried to use fast SD Card - Sandisk Extreme Pro 95MB/s (UHS-I U3 V30). CHDK benchmark on Digic6 camera writes at 70+ MB/s.

On 450D ML benchmark in playback mode writes at 19-20 MB/s. The theoretical limit is 48MHz / 2 = 24MB/s.
Can't display benchmark results in LiveView mode because canon code refreshes the bitmap buffer continiously and ML texts are flickering or disappear. How to fix it?

Now MotionJPEG recording is more stable at ~29.7FPS (dual write buffering - 2x8MB).
But frame drops still occur when the frame size exceeds 400kB for a long time.
In some very spetial situations frame size can exceed 700kB. For example: https://i.stack.imgur.com/YbUvO.gif

The experimental build is there
Logged

heder

  • Developer
  • Member
  • *****
  • Posts: 152
  • No time for caution
Re: Porting ML to XSi (450D)
« Reply #101 on: July 22, 2020, 01:34:35 PM »
Quote from: Ant123 on July 21, 2020, 10:39:09 PM
Tried to use fast SD Card - Sandisk Extreme Pro 95MB/s (UHS-I U3 V30). CHDK benchmark on Digic6 camera writes at 70+ MB/s.

On 450D ML benchmark in playback mode writes at 19-20 MB/s. The theoretical limit is 48MHz / 2 = 24MB/s.
Can't display benchmark results in LiveView mode because canon code refreshes the bitmap buffer continiously and ML texts are flickering or disappear. How to fix it?

Hi Ant123

I never any flickering on 40D, not even on the early version, but if you have flickering the buffering system is'nt working correctly, might be due to incorrect WINSYS_BMP_DIRTY_BIT_NEG address. If that one is incorrect the BMP_LOCKS in dialog_test.c will not work, and that might result in flickering. Without locking canon is free to redraw.


Quote from: Ant123 on July 21, 2020, 10:39:09 PM
Now MotionJPEG recording is more stable at ~29.7FPS (dual write buffering - 2x8MB).
But frame drops still occur when the frame size exceeds 400kB for a long time.
In some very spetial situations frame size can exceed 700kB. For example: https://i.stack.imgur.com/YbUvO.gif

That is really interessing, too bad I don't have time atm to implement your module on 40D, maybe after summer holiday.
Logged
Embedded SW engineer. Canon 20d, 40d, 350d

Ant123

  • Contributor
  • Member
  • *****
  • Posts: 175
Re: Porting ML to XSi (450D)
« Reply #102 on: July 22, 2020, 04:45:45 PM »
Quote from: heder on July 22, 2020, 01:34:35 PM
That is really interessing, too bad I don't have time atm to implement your module on 40D, maybe after summer holiday.

You need only modify lines 559, 560, 715 and 755.
Logged

MrGoodween

  • Just arrived
  • *
  • Posts: 1
Re: Porting ML to XSi (450D)
« Reply #103 on: July 22, 2020, 08:29:33 PM »
Good day. tell me on the latest version of the magic lantern is the focus peaking function implemented? moved from film and got used to manual fixes. and this function would help me. only she is needed.
Logged

Ant123

  • Contributor
  • Member
  • *****
  • Posts: 175
Re: Porting ML to XSi (450D)
« Reply #104 on: July 23, 2020, 04:48:47 PM »
Quote from: MrGoodween on July 22, 2020, 08:29:33 PM
on the latest version of the magic lantern is the focus peaking function implemented?
Not implemented on 450D.
Logged

Hellmark

  • New to the forum
  • *
  • Posts: 2
Re: Porting ML to XSi (450D)
« Reply #105 on: August 06, 2020, 09:08:46 PM »
Out of curiosity, does this port include the patch manager stuff? I'm wanting to use ML to help with trying to circumvent the SD Card write lock issue on mine (it shows as being set to lock no matter what, and not had any luck getting it to show otherwise so far), and I saw a1ex had a method for circumventing the check with ROM patching that required the patch manager.
Logged

Damiano

  • New to the forum
  • *
  • Posts: 10
Re: Porting ML to XSi (450D)
« Reply #106 on: August 10, 2020, 01:20:02 PM »
Hello,
I'm trying  to find the STATE objects of the 450D. In particular i'm trying to find the address of SCSState and SSSState.
I'm using this procedure on qemu as a1ex said : https://www.magiclantern.fm/forum/index.php?topic=17969.msg196010#msg196010
but the first part of the code doesn't return nothing.
Code: [Select]
./run_canon_fw.sh 450D,firmware="boot=0" -d calls |& grep --text EvfState
Any idea why the code doesnt't work and how can find SCSState and SSSSate for this camera?
Thank you,
Damiano
Logged

Damiano

  • New to the forum
  • *
  • Posts: 10
Re: Porting ML to XSi (450D)
« Reply #107 on: August 15, 2020, 06:43:30 PM »
I was able to redo the procedure of a1ex using FWState instead of EvfState but the SCSState and SSSState are not present in the  final result. Does anyone know what's the name of SCSState and SSSState for this camera?
Thanks.
Damiano
Logged

dopler

  • Just arrived
  • *
  • Posts: 1
Re: Porting ML to XSi (450D)
« Reply #108 on: September 11, 2020, 11:39:01 AM »
Hi all.
I am new to this forum and I appreciate the enormous work that you are all doing.
I am trying to install ML on a 450D.
When trying to download the BITBUCKER links give an error.

Could someone post a link with the latest version that works?
Thank you very much
Logged

heder

  • Developer
  • Member
  • *****
  • Posts: 152
  • No time for caution
Re: Porting ML to XSi (450D)
« Reply #109 on: October 01, 2020, 08:23:00 AM »
Logged
Embedded SW engineer. Canon 20d, 40d, 350d

stephanW91

  • New to the forum
  • *
  • Posts: 2
Re: Porting ML to XSi (450D)
« Reply #110 on: December 29, 2020, 08:57:02 PM »
Im new to this and my 450d has the 1.0.4 firmware version, does anyone have a WORKING link for 1.1.0? most of the links i found dont work or arent trustworthy
And what exactly are the features for the ML for the 450D, I dont know everything about this
Logged

Walter Schulz

  • Contributor
  • Hero Member
  • *****
  • Posts: 8124
Re: Porting ML to XSi (450D)
« Reply #111 on: December 29, 2020, 09:30:51 PM »
Logged

stephanW91

  • New to the forum
  • *
  • Posts: 2
Re: Porting ML to XSi (450D)
« Reply #112 on: December 29, 2020, 10:51:28 PM »
Logged

kitor

  • Developer
  • Senior
  • *****
  • Posts: 286
Re: Porting ML to XSi (450D)
« Reply #113 on: December 30, 2020, 07:38:45 AM »
First update to 1.1.0, then use Magic Lantern files.
Logged
EOS R, 200D, 750D, 50D...

Ant123

  • Contributor
  • Member
  • *****
  • Posts: 175
Re: Porting ML to XSi (450D)
« Reply #114 on: August 07, 2021, 08:09:55 PM »
I uploded the source code and the latest build to bitbucket.
But the modules can't be built because of missing the ".hg" folder. How to fix that?
Motion Jpeg movie recording is still experimental. It is limited to the SD controller speed.  Maybe there need to increase somehow the compression of JPEG frames.
Logged

names_are_hard

  • Developer
  • Senior
  • *****
  • Posts: 420
  • 200D idiot
Re: Porting ML to XSi (450D)
« Reply #115 on: August 07, 2021, 09:09:10 PM »
Looks interesting, but it's hard to understand because there is not much context.  This is a fork of some other repo?  Which one?  The commit history has lost everything from wherever it came from.  It's not forked from mine because platform dir doesn't have any Digic 6, 7, or 8 cams.  It would probably make more sense to have these changes on a branch of an existing repo, so that history was more meaningful.

You have a .gitignore file at top level, but official ML is hg managed - that's why you're getting these errors.  You've probably taken this source from some git managed repo?  The build process expects to use hg tools at a few places.  Personally I think making the build process dependent on the source control system is not a good idea, I removed this in my repo so you might be able to adapt those changes:
https://github.com/reticulatedpines/magiclantern_simplified/commit/4a29a347f29276d4bec0876412cec4bb12b5a28c
https://github.com/reticulatedpines/magiclantern_simplified/commit/3163d41cee35fb54b4308e1f32318ff87de53645

Those changes might not cover everything you need, it was over a year ago and I wasn't very familiar with ML code yet, changes are more likely to be messy.  Check commits around the same time.
Logged

Ant123

  • Contributor
  • Member
  • *****
  • Posts: 175
Re: Porting ML to XSi (450D)
« Reply #116 on: August 07, 2021, 10:11:08 PM »
This source code came from the official ML bitbucket repo last year before they removed all mercurial repos.
It contains my 450D related changes. Some code was taken from heder's 40D project.
But there was no changes since summer 2020. I was trying to convert mercurial to git locally but without success. Maybe I am wrong  but it's strange that bitbucket do not provide mercurial to git conversion like github doing it (AFAIK).
Logged

names_are_hard

  • Developer
  • Senior
  • *****
  • Posts: 420
  • 200D idiot
Re: Porting ML to XSi (450D)
« Reply #117 on: August 07, 2021, 11:44:55 PM »
Okay, in that case definitely look at the commits I linked.  ML does shell commands in various places that explicitly call hg CLI commands.  It is not possible to automatically convert it, the problem isn't the repo using git or hg, the problem is ML build system tries to use hg tools, and expects hg related directories to exist.  You must modify the build system if you want to manage ML code using git.

The commits I link to make those changes. 
Logged
Pages: 1 ... 3 4 [5]
« previous next »