DIGIC 6 question

pigeonhill

Both the M3 and G1X2 use DIGIC 6.

On my M3 I run scripts that require an XIMR build.

The question is, will my M3 XIMR script run on my G1X2?

chdk-assistant

Not automatically. A script that runs on the M3 isn't guaranteed on the G1 X Mark II just because both are DIGIC 6 — script behaviour and supported functions depend on the individual port, not the Digic generation, and the two cameras are otherwise unrelated ports.

What is known:

The M3 port is stable; the G1 X Mark II port is still alpha. That label means it may be less tested or have missing features, so functions your script relies on may behave differently or not work. The port notes or the porting thread for the G1X2 are the place to check what's known.
On DIGIC 6 cameras, use a 1.7 trunk build rather than 1.6.1 stable — the trunk draws the UI with a much better method on these cameras, and that applies to both models, not just one.

So: try the script on a current 1.7 trunk build for the G1X2's firmware version, and report anything that fails in the porting thread — an untested port only improves if people run it.

pigeonhill

Should have said, if I was to adapt my script to the G1X 2, I would need someone to fill in a view blanks, ie these three (these are for (bi.platform=="m3") and (bi.platsub=="101a"):

FocusSearchFar_FW = 0xfc43dfd9
FocusSearchNear_FW = 0xfc43dfff
FocusPositionWithLensCom = 0xfc5a85c7

chdk-assistant

Those three addresses are ROM function locations specific to the M3 101a firmware, so they cannot be reused: on the G1 X Mark II the same functions sit at different addresses and each one has to be found again from that camera's own firmware. I don't have G1X2 values to give you.

The way to get them is the same as it was for the M3: a firmware dump of the G1X2 version in question, then locating the equivalent focus functions in the disassembly. The wiki page on Canon Basic card setup covers making the dump, and the G1X2 porting thread here is where to ask someone to find the stubs — an alpha port only improves if people work on it.

One caution from the raw-buffer work on other Digic 6 cameras (https://chdk.setepontos.com/d/13095): function layout between Digic 6 models is similar but not identical — equivalents were at different offsets and with different struct offsets between the G7 X, SX60 HS and G16 — so identifying the G1X2 counterparts by pattern-matching the M3 disassembly is plausible, but each match needs verifying.

reyalp

pigeonhill To the first question: Yes, all 1.7 digic 6 / 7 ports use the XIMR display method, but that's probably not relevant to the script (it is relevant to the EVF issue, which I hope to work on this weekend)

For function pointers, the bot is correct that you would need to find the equivalent for your firmware. However, all the rest of its comment is irrelevant because the three functions you mention are specific to EOS M cameras and aren't present on fixed lens cams. So you need to come up with equivalent functionality rather than just finding the corresponding function.

It looks like we had a related discussion regarding these functions
https://chdk.setepontos.com/d/14597-initializeadjustmentsystem-and-exposure-control-on-m3-was-help/28
https://chdk.setepontos.com/d/14694-lens-movementfocus-control/11
In the second one, I think you were maybe trying port the same (?) script to G5 X and G7 X, so whatever the outcome of that is would likely be relevant to G1X2

If you can share the script and describe how the existing functions work, we may be able to help come up with alternatives.

pigeonhill

reyalp Thanks for the reminder ;-)

I’ll have a look and think, regarding functionality.

Cheers

Garry