Messages

No, was working with what Alex provided to me. While I have *some* background in hw hacking (was working on jlime linux port to bsquare power handheld... 10 years ago), that's my first entry into Canon's world (only messed with ML 5d2 audio code before).
Printing things over serial seems to be safer too (considering still have 4/5 of loan to pay and disassembled camera already  )

[e]
sht_memoryread2 is missing

https://www.magiclantern.fm/forum/index.php?topic=22770.0

Will there be a Magic Lantern that would have the option for the Canon EOS R/RP family of camera to record both Full Frame 4K, and Super35MM 4K video?

If you know people willing to help and have all the needed low level knowledge, maybe. So far we cannot even execute code on camera without hardware hacking.

In case of R, UART is hidden under thumb rubber, next to Trash button (there's a hole to access connector). Pinout:

MPU RX IS WRONG. Scroll to post 38-43 on this thread for proper R/RP/... pinout.

Code Select Expand

1. 0V (not GND)
2. RXDICU (1v8)
3. TXDICU (1v8)
4. GND
5. RXDMPU (3v3)  #EDIT: WRONG! Unknown, (3v3)
6. TXDMPU (3v3)
7. ? (3v3)       #EDIT: WRONG! RXDMPU, (3v3)!
8. ? (3v3)



For upcoming RP I expect the same.
Note that R (and RP on mentioned photo) has 2nd similar connector next to this one. No communication was visible, something tells me this may be JTAG. However not accessible without disassembling camera.

Initial notes:

I'll add here
- LV is taking so many resources, that it's loosing input on UART. Going into menu makes it reliable + camera output is a few times faster.

For adventurous (as it need's 1v8 UART or 3v3 with voltage divider on TX), simple bootloader dumper:

Code Select Expand

import serial
import sys

start = int('0xE0000000',16)
end = int('0xE0040000',16)
step = int('0x1000',16)
current = start

with serial.Serial('/dev/ttyS6', 115200, timeout=1) as ser, open("dump2.log", 'w', encoding='utf-8') as logfile:
  while True:
    line = ser.readline()
    if line is not b'':     #skip timeouts
      decoded = line.replace(b'\r\n',b'').decode("UTF-8") #bytes to string
      print(decoded)
      logfile.write(decoded + '\n')

    if b"Mode ON" in line:       #enter interactive shell
      ser.write(b'akashimorino\r\n')
    elif b"K424[1]>" in line:    #prompt, start data dump
      if current > end:
        sys.exit(0)
      ser.write(str.encode("d " + hex(current) + " " + hex(step) + "\r\n"))
      current += step

Of course you need to reassemble this data into binary form yourself.

UART location/pinout is here.

And I didn't have to hold any needle on the UART connector

Yup. Fortunately with bootflag enabled, now RX is sufficient.

If you missed the news:
https://twitter.com/_kitor/status/1095807058358796290

However executed via bootloader CLI, and took a lot of pain to debug this for Alex and me. Would be much easier if I had proper FPC for this debug connector; had to hold needle to TX pad all the time by hand.

Oh hello!

Code Select Expand

Dry[WarpPUX]> sysvers
SystemIF 1.01
DRYOS version 2.3, release #0060+p4
MACH 0.51

Grip communication was my mistake, this pin is used by grip itself unfortunately.
Anyway,

Code Select Expand

Battery close!
RSTFLG : 0010
E1ON
openBattery
/USB_DET undetected
setCCSnkRst

MON>>>All task Initialize
================SD send recode 0 0
WakeupReason from ICU: 0x67,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x02,
Hello from MPU 

[N]

Interesting quirks:
- Battery grip has ability to upgrade it's firmware (additional option in firmware update menu).
- Toshiba M4EBF10XBG inside (may be wrong about F). Google gives no results, but A1ex found another uC with very similar name.
- Shutter and AF pins are directly available on grip connector. Ground them for action.
- There's a single (unused in grip) pin that shows some digital communication on camera start, photo shots and sometimes random "messages" on idle. Signal is active-low 3.3v, around 50kHz, but no luck trying to treat is as 57600 serial communication. Will borrow logical analyzer and try to dump this.



USB-C in grip seems to be used only for charging grip batteries. USB-C in body is used for communication and charge of internal battery when no grip is attached.
Both work only with LP-E6N (won't charge E6) and with USB-PD adapters only. No luck with standard 5V chargers and QC/PE ones.

After some time spent with R I have some more conclusions:

- AF works great with EF lenses (I use 100-400 atm)
- Grip is expensive as hell, but worth it - since it will charge both batteries inside
- quirks: grip has separate USB-C for charging, will charge only with LP-E6N, won't charge any with both E6 and E6N inserted.
- where's back dial ?! ( )

Yesterday I (finally!) bought 5DIII as spare body... with respectable 258k shutter count Yep, it was so cheap I can replace shutter twice before hit "usual" price, and it has so signs of failing.
Anyway, to the point. When I was shooting with 5D2 and 100-400 (had a7 16-35, r 24-105 and 5d2 100-400 on last trip to cover all scenarios) I noticed i somehow like R grip better. Now I confirmed this - due to it's grip depth, R with 100-400 on adapter seems more comfortable to me. Feels more secure in my hands, and that's an interesting observation as I was looking to jump to 1 series for bigger body while I had my first 5D2...

As I finally got my hands on R (arrived just yesterday), some photos comparing to 5D2 and A7s1: https://imgur.com/a/8rHgjoI

First impressions:
- grip ergonomy is wonderful. It's smaller than 5D2, but due to a bit different shape it's similar in comfort of holding it.
- where's back dial ?!
- touch bar is a joke. Was disabled factory default and I kept it disabled.
- control ring is interesting feature. Not sure why was also factory default disabled.
- mode dial is not that bad (how often do you switch modes?). However there's so much wasted space in power switch location.
- AF is fast AF ( ). I was amazed after using A7s for last two years.
- 24-105 is quite heavy lens.
- LP-E6N! Took two spare LP-E6 from mum's 5D2 (btw, 10 years anniversary!) and now I have three. Eat this, Sony!
- I'm amazed so far with EVF quality. Much better than A7s1, which was the first EVF that convinced me that mirrorless may substitute DSLR.
- A few more programmable buttons wouldn't hurt.

Nice to see that something is going on!
This green screen is a problem with graphics runtime, or it hanged in this state? Just wonder, as graphics is not really needed to have a rom dump...

Theoretically speaking:

We don't have any ideas about internals, and you're asking questions.

Nobody from dev team have it, and what's worse it's not just an iteration of DSLR, some things for sure had changed.
The best expectation is no expectations.

Depends on what you want. I'll probably add 70-200 2.8L IS II + something wide like mentioned 16-35 on EF and leave 24-105 for trips where I don't have time/want to play with lenses.
Yup, I'm not shooting much video, and just before my 5d2 hit the floor (in accident) I worked mostly as photojournalist. After two years break (done only ~3000 shoots on a7s during those 2 years, half of them on two visits in the Zone) i'm getting back into it, and lastly most shots are either on 16-35 or on 100+mm.

With all the 'paradoxes' that R presents, I still decided to buy it. For Canon skintones, EF lenses and body ergonomics (waited for a7sIII but I consider even a9 too small for my hands).
Many people talk about single SD card and IBIS - I don't consider them a problem, but to be fair - none of my previous cameras had those. And would probably buy again 5dc as backup body.
After you go mirrorless, seems there's no going back. I still borrow 5D2 and Nikon D7000 from mum, but after I got used to EVF I always missed exposure on first few shots as on EVF WYSIWYG

I just pre-ordered R + 24-105. So @a1ex if you have any ideas for rom dumping feel free to contact me.

Hope to get it on time as I'm going for a week to Chernobyl Exclusion Zone just day after release. So either new toy (and opportunity to compare it against A7s) for this trip, or will have to wait until I'm back.

I'm looking forward to see it in person, at the moment I really think about going back to Canon from A7s1. Body seems to win in terms of ergonomic with both Nikon Z and A7/A9. ISO performance (at least on photos I saw, unfortunately jpegs only) is not too bad, and I think up to 40k after Lightroom it will be comparable with a7s in 1080/2.5k resolution that I usually export my photos.

I will miss rear dial. However with new ring on lenses (set this to aperture control) and using camera dials for ISO/exposure seems to be a good idea.

As for 4K, IIRC Kai tried with 10-18mm EF-S on adapter and it worked perfectly. So there are some workarounds to this crop factor other than on 5d4.

No third party lenses for R mount,

I missed that info, where they stated it? Remember there are not too many third party lenses for Sony FE too. AFAIR Sigma announced first E-mounts this year...

In terms of lenses with my a7s I use 16-35/4 and 24-240 which is perfect (but heavy) all-around lens. Here will probably go back for 70-200 on adapter and native 24-105, sadly there was no wide zoom like 16-35 or 17-40 announced...

If it's 30p fps wouldn't that be video mode? Maybe it limited to Video only , there no manual to read yet so it's a mystery

"Time lapse". No regular movie.

They purposefully put SD on it, so people buy MKIII.

Even dual SD would be nice.

Single SD slot, no 4k. Canon, why?

Standard IDE-SATA adapter inside. I have similar one, identical from-factor.
And yes, it's definitely CF card -> CFast (SATA) adapter.

How to remove bootflag? When I run firmware update again (running Magic Lantern), it shows "Update file cannot be found", even when I unpack fresh copy of Magic Lantern files to this card.

When I used a new, fresh formatted card (so ML will not start), procedure worked - got "blue blinking light", but after inserting first card it booted again to ML...

1080p 60fps

Does this counts?
http://www.magiclantern.fm/forum/index.php?topic=18808.msg148003;topicseen#new

Shot on 5D Classic with 28-135 1:3.5-5.6 IS USM @44mm f/5.6
ISO 800, 2s exposure.
Colors corrected a bit in Lightroom, then exif-based time overlay added using some magic in ImageMagick ( )*
Unfortunately not 4K as Sony Movie Studio 12 can't go above 1080p.

Proves that 5D classic is still capable for this kind of usage 

*code if anyone would like to use it:

Code Select Expand

for f in *.tif; do
date=$(identify -format "%[EXIF:DateTimeOriginal]" $f 2>/dev/null)
echo $date
convert -size 500x56 xc:none -font DejaVu-Sans-Mono-Book -pointsize 44 -gravity southeast \
-stroke black -strokewidth 1 -annotate 0 "$date" \
-stroke none -fill \#999 -annotate 0 "$date" \
$f +swap -geometry +9+9 \
-composite comp/$f
done

Since when RPi has USB 3.0? And no, you can't do it.

I'm looking for a ROM dump for QEMU experiments (mine is incomplete). You may get one from the Debug menu; please send it to me by PM.
If there is still interest, I can try to fix compilation on the latest codebase, then let you continue the port.

My 5D2 recently meet the floor, and I'm using 5Dc since then. I can make dump if you still need it

Side note: there is a small chance to get LiveView with the full-res silent pic backend, but the front-end functions are not present, so it will require some low-level research along these

That would be interesting!

I written this already: CBOX is nothing more than overpriced two connectors and nice case. CFast is just SATA in different form-factor. They won't help you as they designed nothing, and all they are writing about possibilities and costs is just PR.

What you need here is somehow bridge CF IDE implementation with SATA drive, that requires creating some custom circuits.

And isn't it sensor itself that gets hot during recording?