Topics

It appears that Canon XF605's firmware shares many (non-)features found in EOS R5/R6/..., such as Canon Basic being locked by default
(If you are unhappy about that, please speak to your local Canon representative and explain to them why full access to your camera would motivate you to buy again a Canon. You are invited to share your story within the "General Chat" section https://www.magiclantern.fm/forum/index.php?board=26.0, or if it is specific to XF605 in the following thread: https://www.magiclantern.fm/forum/index.php?topic=26794.0).

Maybe most notably, the Device section of the MMU tables starts at BF000000, too (and unlike previous Digic generations):

Code Select Expand

$ magiclantern_simplified/contrib/firmware_tools/decode_armv7_mmu_tables.py XF605/ROM0.BIN
CPU0
TTBR0: E0004800
===============
00001000-00001FFF -> 00000000-00000FFF (-1000) O:NCACH I:WB,WA  P:RW
TTBR1: E0000000
===============
00002000-3FFFFFFF -> 00002000-3FFFFFFF (   +0) O:NCACH I:WB,WA  P:RW
40000000-BEFFFFFF -> 40000000-BEFFFFFF (   +0) O:NCACH I:NCACH  P:RW
BF000000-DEFFFFFF -> BF000000-DEFFFFFF (   +0) Device           P:RW XN
DF000000-DFFFFFFF -> DF000000-DFFFFFFF (   +0) O:NCACH I:WB,WA  P:RW
E0000000-E7FFFFFF -> E0000000-E7FFFFFF (   +0) O:WB,WA I:WB,WA  P:R
E8000000-EFFFFFFF -> E8000000-EFFFFFFF (   +0) Strongly-ordered P:RW XN
F0000000-F7FFFFFF -> F0000000-F7FFFFFF (   +0) O:WB,WA I:WB,WA  P:R
F8000000-FFFFFFFF -> F8000000-FFFFFFFF (   +0) Strongly-ordered P:R  XN

CPU1
TTBR0: E0004880
===============
TTBR1: E0000000
===============
00001000-3FFFFFFF -> 00001000-3FFFFFFF (   +0) O:NCACH I:WB,WA  P:RW
40000000-BEFFFFFF -> 40000000-BEFFFFFF (   +0) O:NCACH I:NCACH  P:RW
BF000000-DEFFFFFF -> BF000000-DEFFFFFF (   +0) Device           P:RW XN
DF000000-DFFFFFFF -> DF000000-DFFFFFFF (   +0) O:NCACH I:WB,WA  P:RW
E0000000-E7FFFFFF -> E0000000-E7FFFFFF (   +0) O:WB,WA I:WB,WA  P:R
E8000000-EFFFFFFF -> E8000000-EFFFFFFF (   +0) Strongly-ordered P:RW XN
F0000000-F7FFFFFF -> F0000000-F7FFFFFF (   +0) O:WB,WA I:WB,WA  P:R 
F8000000-FFFFFFFF -> F8000000-FFFFFFFF (   +0) Strongly-ordered P:R  XN

$

This indicates, that "Digic DV 7" is very similar (if not fully equivalent) to Digic X.

Are there any other notable similarities between Digic DV 7 and Digic X known?
Or even more important: were any (remarkable) differences observed (yet), i.e. besides the different name?

XF605's UART (see https://www.magiclantern.fm/forum/index.php?topic=26807.msg242477#msg242477) provides, inter alia, the EnableBootDisk and DisableBootDisk commands in an eventproc shell.

From first inspection, Canon XF605's bootloader appears to support booting via autoexec.bin, if the "bootflag" is set.
on XF605, bootflag resides at 0xE3FF8004 in ROM (and 0xDFFE2084 in TCM).

This thread shall be about building a "ML style" autoexec.bin that will facilitate development of custom code for XF605.

The unused 50 pin header below the bottom cover, https://www.magiclantern.fm/forum/index.php?topic=26795.msg242476#msg242476, provides access to an 1.8 V UART:
115200 baud, 8 bits, 1 stop, no parity, LSb first, non-inverted

Use the akashimorino-equivalent common to EOS cinema cameras for starting the shell, as on other EOS Cinema cameras.

Use ? to get a list of supported commands of this D214 shell (D214 is how XF605 is apparently referred to internally).

Use drysh to start another shell (on Diva) with less but different commands. Again, ? is your friend if you aren't familiar with this Dry[DivaPUX] shell.

Within D214 shell, SaveAllRomImageToFile can be used to save the content of the ROMs residing at 0xE0000000-0xE3FFFFFF and 0xF0000000-0xF0FFFFFF to your SD card in the bottom slot, slot B.

[As always: never use force for separating things.]

If you happen to have a (spare?) XF605 you do not mind taking apart, please do so (carefully!) and document (or at least link) your findings here!

In other words: This thread shall receive all the images taken from inside your camcorder.
If you don't have a camera at hand when disassembling your camcorder, documenting any IC markings and linking datasheets is probably just as good

WARNING: many screws on XF605 are secured using threadlocker.
Double check that you are always using a perfectly fitting screwdriver and alway apply sufficient axial force when (un-)screwing, otherwise the screw heads are very(!) easily damaged beyond repair.

As always: never use force for separating things.
If something doesn't come off very easily, you very very likely missed either at least one screw, connector with extremely thin wires on it or a very delicate flexible flat cable!
I haven't encountered any plastic clips on XF605 so far.

The good news: you can get incredibly far with just a suitable crosshead screwdriver and/or bit.
My J00 bit worked somewhat, yet I have definitely seen better fits, so take this information with a big grain of salt.
Theoretically (or rather: mechanically) the XF605 seems to be an almost perfect positive example of how to build repair-friendly electronics — if there only was easy access to spare parts 

Our images and details will follow...

This thread is meant for the general discussion targeting Canon XF605, i.e. everything that does not clearly belong into another section of this forum.

Always bear in mind, that XF605 is a camcorder and not a target DSLR/DSLM of ML!
So any requests, especially feature requests should be carefully assessed before posting them here, especially whether they rather ought to be addressed (and sent) to Santa Claus.
Rule of thumb: High profile features and requests like "raw video, plz!!" -> Santa Claus (unless you provide a proof of concept of course  ).

Remarks about bugs in the official firmware are welcome here, although chances are negligibly small that someone besides Canon can fix them.
So do not forget to talk to your Canon representative (unless you do not care about your bug).

Shortcomings that are very unlikely to be related to pricing policy, however, might be of interest and are welcome in this thread.

E.g., the direction of the zoom ring could be inverted from Canon's first HD(V) camcorders in the same category as XF605 onwards (XH A1/G1/A1s/G1s/...).
This is not the case anymore on XF605, which is extremely annoying, and nothing that you could get from Canon by throwing money on the problem (buying XF705) either.
While it is absolutely unknown whether this shortcoming could be theoretically overcome via an firmware update or a ML like firmware extension, investigating whether that seems possible (i.e. the zoom ring's position is forwarded by the ICU to the electromechanical system) or not (i.e. the zoom ring's position is directly coupled with the electromechanical system without the ICU being able to interfere) might be a very interesting research question.

Last but not least, discussion about possibly relevant old/other threads for XF605 can go here as well.
If it turns out that something is indeed the same on XF605, the link can/will be later added to another thread, dedicated to summarizing progress on XF605, with a detailed description explaining the findings (including possibly observed minor differences).