Magic Lantern Forum

Magic Lantern Releases => Camera-specific discussion => Topic started by: SpenceM on September 05, 2018, 03:09:27 PM

Title: Canon EOS R / RP
Post by: SpenceM on September 05, 2018, 03:09:27 PM
Today Canon showed us the new EOS R. Unfortunately, they’re crippling it. 4k video is heavily cropped, and can’t even get 120fps @ 1080p. Also only 1 SD card slot.

So it’s up to the awesome people of MagicLantern to unlock this camera’s true potential!  ;)
Title: Re: Canon EOS R
Post by: a1ex on September 07, 2018, 01:31:20 PM
If you've got one and don't mind running a couple of tests, just ask.

Expecting to get blank screen with M50 code, i.e. hopefully able to run a while(1). Maybe also LED blinks if lucky.
Title: Re: Canon EOS R
Post by: Walter Schulz on September 07, 2018, 01:53:57 PM
Also only 1 SD card slot.
UHS-II interface, though. First time in consumer/prosumer line-up.
Lens interface protocol redesigned. Means work for devs.
No third party lenses for RF mount, only EF/EF-S with adapter. Seriously, Canon?
Menu control redesign.
New HDMI modes.

Sounds like lot of fun and navigation towards HC SVNT DRACONES.
Full code ahead, argh!



Seriously, a1ex: Your twitter account sounds like you'r not absolutely against sending you a specimen. It's nonetheless twitter. So: Where are we heading, cap'n?
Title: Re: Canon EOS R
Post by: kitor on September 07, 2018, 02:09:25 PM
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.

Quote
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...
Title: Re: Canon EOS R
Post by: Walter Schulz on September 07, 2018, 02:42:22 PM
[RF mount and third party]
I missed that info, where they stated it?

No quote from Canon itself. Problem seems to exist because of a (at least one) Canon patent covering RF mount and no word given about licensing to third parties.
Nothing heard from Sigma, Tamron, Tokina (to name the most usual suspects) about it.

I think/hope there will be some interviews at Photokina trying to get a solid statement about this.
Title: Re: Canon EOS R
Post by: a1ex on September 07, 2018, 04:19:39 PM
Seriously, a1ex: Your twitter account sounds like you'r not absolutely against sending you a specimen. It's nonetheless twitter. So: Where are we heading, cap'n?

Well, since the other DIGIC 6/7 ports appear to be a little different from what we are used to (DIGIC 4/5), and simply waiting for others to jump in apparently wasn't exactly the best idea for these models, I've considered getting a recent camera and making a reference port, that others could easily adapt to other "new" cameras. Was thinking at M50, as it seems close enough to all other DIGIC 7 models, yet different enough to be challenging (its firmware is a strange mix between EOS and PowerShot codebases, and the sensor looks a bit faster than on older Canons).

Then noticed the giveaway and got tempted by the full-frame dual pixel RAW (some unfinished notes I've started to write a while ago here (https://a1ex.magiclantern.fm/bleeding-edge/5D4/5d4-dual-pixel.html)). Didn't expect anything to come up from that, but looks like some folks took it (maybe a bit too) seriously.

EOS R is also DIGIC 8. No idea what's inside, but expecting its firmware to be similar to M50. Whether we'll be able to run code on it, remains to be seen.
Title: Re: Canon EOS R
Post by: dfort on September 07, 2018, 04:28:47 PM
Your twitter account...

You mean we should be following someone other than just @autoexec_bin for the latest ML news?
Title: Re: Canon EOS R
Post by: Walter Schulz on September 07, 2018, 05:34:31 PM
Didn't expect anything to come up from that, but looks like some folks took it (maybe a bit too) seriously.

Friendly forces may be among the hardest to endure. (Source: Fortune cookie of the day)

With that thought in mind:
I think there are some people happy to hear about your change of heart and willing to express their happiness through donations. If you drop a word I'm convinced there will be no troubles getting you a EOS R (+ RF lens + EF/EF-S-Adapter) or a M50.

Title: Re: Canon EOS R
Post by: kitor on September 15, 2018, 07:14:43 PM
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.
Title: Re: Canon EOS R
Post by: KelvinK on September 18, 2018, 11:34:13 AM
Price tag for RF lenses is non adequate (you get body and 28-70 5.5k$) making whole system kinda strange. And for this price you have 50mm in 4k.
Title: Re: Canon EOS R
Post by: kitor on September 18, 2018, 09:38:39 PM
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 ;)
Title: Re: Canon EOS R
Post by: lovelybead on October 01, 2018, 03:26:08 AM
I ordered one too. I work in tech and am happy to help with however I can once it arrives!

Theoretically speaking: Would it possible with ML to shoot 120fps in 1080p or would the limit still be 720p? That's the main gripe I have with this camera. The 4k crop I don't mind so much.
Title: Re: Canon EOS R
Post by: kitor on October 01, 2018, 12:27:21 PM
Quote
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.
Title: Re: Canon EOS R
Post by: a1ex on October 01, 2018, 07:10:18 PM
If it's like 5D4, it's very unlikely, as 1080p60 appears to be pushed to the limit (https://www.magiclantern.fm/forum/index.php?topic=17695.msg206730#msg206730). That's an unexpected limitation, since on both models, the sensor appears to be fast enough (https://twitter.com/autoexec_bin/status/1037487068870520833) for 1080p120, assuming no readout overhead for lower resolutions.

5D3:

5936x3950x7.65 = 179 Mp/s (full size, including black bars, in photo mode)
5796x3870x7.65 = 171 Mp/s (active area size)

3744x1382x31.5 = 163 Mp/s (full size, including black bars, 1:1 crop x5)
3596x1320x31.5 = 149 Mp/s (active area size)

2080x1320x40 = 109 Mp/s (full size, including black bars, 3x3 binning 1080p FPS override)
1936x1280x40 = 99 Mp/s (active area size)

2080x1040x48 = 104 Mp/s (active size, 3x3 binning crop_rec)
1936x1040x48 = 97 Mp/s (active size)

700D (LiveView figures from the bleeding-edge crop_rec (https://www.magiclantern.fm/forum/index.php?topic=19300.msg205546#msg205546)):

5280x3529x6.45 = 120 Mp/s (full size)
5208x3476x6.45 = 117 Mp/s (active size)

2592x1107x33.3 = 95 Mp/s (full size, 1:1 crop x5)
2520x1080x33.3 = 91 Mp/s (active size)

1808x1189x43.3 = 109 Mp/s (full size, including black bars)
1736x1160x43.3 = 98 Mp/s (active size)

In other words:
- 5D3 1080p (1936x1280) was pushed to 40 FPS, i.e. about 100 Mp/s out of 170 in photo mode (what limits it? no idea)
- 700D 1080p (1736x1160) was pushed to 43 FPS with a slower sensor, i.e. about 100 Mp/s out of 120

Take it with a grain of salt, i.e. as pure speculation or CR0 if you prefer; I did not see the EOS R firmware.
Title: Re: Canon EOS R
Post by: a1ex on October 16, 2018, 08:48:32 PM
Tried to run some initial tests on the EOS R; unfortunately, this is all we've got:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fa1ex.magiclantern.fm%2Fbleeding-edge%2FR%2Fr.jpg&hash=94380fc020e2b71807adeaf9c08f5d41)

The error screen looks just like on previous models, which is encouraging. The camera recognized there was a FIR file on the card, for the correct model, otherwise it would have printed "Update file cannot be found". The error message means it could not verify the checksum; Canon might have changed the FIR file format, or maybe also the encryption.



Edit: progress - apparently it doesn't like tiny FIR files, but otherwise it accepts them:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fa1ex.magiclantern.fm%2Fbleeding-edge%2FR%2Fprogres.jpg&hash=ca755ea2cfeb71c418ad02fea6ae8233)

Edit (February 2019): turns out it was just the decryption code locking up with some FIR files.
Encryption changed - we can no longer create FIR files for this camera.
Title: Re: Canon EOS R
Post by: kitor on October 21, 2018, 09:06:00 AM
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...
Title: Re: Canon EOS R
Post by: a1ex on October 21, 2018, 03:56:45 PM
Every single accepted FIR file (that did not print an error) hanged in the green screen state.

Otherwise, the error message was always the one from the screenshot.

My hypothesis:
- Canon does some more checks to decide whether the file format is valid or not (possibly some data structure where the old FIR files had executable code)
- that green screen might be the result of some incomplete display shutdown from the bootloader:
   - test video:
   - while loading a FIR, Canon bootloader prints "Loading..."
   - after that, on previous models it turns off the display and the SD card, then it runs the firmware update program
   - that firmware update will turn on the display again; that means, you would see a short flicker (https://youtu.be/WzMTZr_Zef0?t=280) (display turning off and on for a split second)
   - in the test video, I do not see the display turning off, which is why I believe the bootloader maybe "forgot" to turn it off before running the FIR code
   - maybe just the image stream was turned off, and the display controller (which is likely "smarter" than in previous models) timed out and displayed some green screen.

The above is just speculation.

Easiest way to figure it out: wait for a firmware update.
Harder way: perform some more blind tests, hoping to get some different outcome (other than green screen or error message).

I'm not 100% sure we actually executed code on the camera, but the lack of error message hopefully means the FIR file was accepted (i.e. encryption was not changed).
Title: Re: Canon EOS R
Post by: kitor on October 31, 2018, 01:05:49 PM
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.
Title: Re: Canon EOS R
Post by: a1ex on November 17, 2018, 10:53:12 PM
EOS R users might be interested in the following numbers (thanks @kitor for test images):

Silent still: 17.47 μs/line, 78.25 ms full readout at 6720x4480 => 385 MPix/second readout speed?
4K24/23.98/25/30: 14.45 +/- 0.019 μs/line, 31.2 ms at 3840x2160
1080p24/25/30/50/60: 14.12 +/- 0.067 μs/line, 15.3 ms at 1920x1080
720p25/30/50/60: 21.20 +/- 0.087 μs/line, 15.3 ms at 1280x720
720p100/120: 9.47 +/- 0.204 μs/line, 6.8 ms at 1280x720
Title: Re: Canon EOS R
Post by: Walter Schulz on December 13, 2018, 10:15:44 AM
Most readers may be aware of Lensrental's tear-down/disssembly of an RF 50/1.2:
https://www.lensrentals.com/blog/2018/12/disassembly-of-the-canon-rf-50mm-f1-2l/

Well, R system really seems to be a hard nut to crack ...
Title: Re: Canon EOS R
Post by: kitor on December 17, 2018, 08:41:44 AM
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 :P 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...
Title: Re: Canon EOS R
Post by: Dmytro_ua on December 17, 2018, 10:34:47 AM
This question is directed more to ML developers then to R owners.
Is R have any potential advantages for ML video possibilities over 5d4, except eye tracking?
Title: Re: Canon EOS R
Post by: KelvinK on December 17, 2018, 01:23:06 PM
This question is directed more to ML developers then to R owners.
Is R have any potential advantages for ML video possibilities over 5d4, except eye tracking?

No. But image quality can differ. For some reason, 4K on 5D4 is sharper then on R.
Title: Re: Canon EOS R
Post by: Dmytro_ua on December 17, 2018, 03:49:55 PM
No.

What about DIGIC 6+ vs DIGIC 8,  CF bus vs SDXC UHS-II bus?
Title: Re: Canon EOS R
Post by: kitor on January 10, 2019, 08:13:25 AM
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.

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FFgnmgJ1%2F49759127-1882742475181896-2832192286425612288-n.jpg&hash=6f399e16708fcb2fe39374f561ff2e81) (https://ibb.co/FgnmgJ1)

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.
Title: Re: Canon EOS R
Post by: a1ex on January 10, 2019, 08:57:57 AM
- 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.

Here's my attempt at manually identifying the message format and timings. It appears to be UART (https://tutorial.cytron.io/2012/02/16/uart-universal-asynchronous-receiver-and-transmitter/), bit time about 18.5-19 microseconds, so about 52000-54000 baud. Couldn't identify any plain text in these short fragments, though.

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fa1ex.magiclantern.fm%2Fbleeding-edge%2FR%2Fr-uart2.jpg&hash=456321b4da1694d43b6fa5062a13b260) (https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fa1ex.magiclantern.fm%2Fbleeding-edge%2FR%2Fr-uart4.jpg&hash=cd5b012e48683e3204982c8bdf575209)
Title: Re: Canon EOS R
Post by: TiagoSilva1987 on January 28, 2019, 06:55:29 PM
Hello, Where can i download the Magic lantern firmware update for EOS R?
Title: Re: Canon EOS R
Post by: Walter Schulz on January 28, 2019, 07:58:57 PM
You have to find the tree ... (https://www.magiclantern.fm/forum/index.php?topic=17695.msg207023#msg207023)
Title: Re: Canon EOS R
Post by: TiagoSilva1987 on January 29, 2019, 10:19:51 AM
It´s under development?
Title: Re: Canon EOS R
Post by: Walter Schulz on January 29, 2019, 10:26:40 AM
What difference does it make? ML development follows no schedule.
2 years ago a generous offer was made: A 750D (free of charge) for anyone willing and able to port it. Nobody claimed it ...

My advice:
If there is no ML for your cam act like there will be no ML for your cam ever.
Title: Re: Canon EOS R
Post by: TiagoSilva1987 on January 29, 2019, 02:32:44 PM
Where can i download RLEDID14.FIR  ?
Title: Canon EOS R Firmware
Post by: jga on February 12, 2019, 07:23:45 AM
Firmware 1.1 has been released: https://www.canon-europe.com/support/consumer_products/products/cameras/digital_slr/eos-r.aspx?type=firmware
Title: Re: Canon EOS R
Post by: civita on February 12, 2019, 08:43:03 AM
A new firmware regarding EOS R was released!

https://www.canon-europe.com/support/consumer_products/products/cameras/digital_slr/eos-r.aspx?type=firmware
 (https://www.canon-europe.com/support/consumer_products/products/cameras/digital_slr/eos-r.aspx?type=firmware)
Canon EOS R Firmware v.1.1.0 changes:
Title: Re: Canon EOS R
Post by: Sapporo on February 12, 2019, 11:32:06 AM
Firmware 1.1.0 is release from Canon now https://www.canon-europe.com/support/consumer_products/products/cameras/digital_slr/eos-r.aspx?type=firmware&firmwaredetailid=tcm:13-1776855
Title: Re: Canon EOS R
Post by: kitor on February 12, 2019, 05:47:18 PM
Grip communication was my mistake, this pin is used by grip itself unfortunately.
Anyway,
Code: [Select]
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  8)
Title: Re: Canon EOS R
Post by: a1ex on February 12, 2019, 10:17:56 PM
... the "behind the scenes" picture:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fa1ex.magiclantern.fm%2Fbleeding-edge%2FR%2Frr.jpg&hash=b546b0bd6f634188a1885aeb7fb2a3e8)

The firmware update... unfortunately wasn't helpful. None of my previous tricks worked with it. I'm still wondering why some of my previous test FIRs resulted in green screen, but I'm now 100% sure we did not execute any code on the camera. The green screen was likely a bug in Canon's FIR loading routine, or something like that.

The good news - kitor identified two UART ports: one at 3.3V, used by the MPU (outputs the log from above) and another at 1.8V, likely used by the main CPU (same voltage level on DIGIC 6 (https://www.magiclantern.fm/forum/index.php?topic=7531.msg200763#msg200763)). The latter needs some level shifting (https://electronics.stackexchange.com/questions/333229/1-8v-uart-with-3-3v-uart), but - at least on previous models - it has everything we need to enable the boot flag and explore around.

Worst case - ML on EOS R may require some hardware hacking in order to install it (like in the above picture). No big deal, right? I mean, you need a lot more knowledge to be able to use it (https://www.eoshd.com/comments/topic/28683-how-do-i-get-ml-crop-recording-going-on-my-5d3/?tab=comments#comment-273299) ;)

Also forgot to mention - I've got high-res PCB pictures from the Lensrentals teardown (https://www.lensrentals.com/blog/2018/10/teardown-of-the-canon-eos-r-mirrorless-camera/). If any of you can identify anything from here, please write it down.

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fa1ex.magiclantern.fm%2Fbleeding-edge%2FR%2F1S7A7943-small.JPG&hash=57284664b6f9d20a1bd68834f92ec363) (https://a1ex.magiclantern.fm/bleeding-edge/R/1S7A7943.JPG) (https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fa1ex.magiclantern.fm%2Fbleeding-edge%2FR%2F1S7A7944-small.JPG&hash=1a54f11521f7fdfda3d67c0e27ff1ff6) (https://a1ex.magiclantern.fm/bleeding-edge/R/1S7A7944.JPG)
Title: Re: Canon EOS R
Post by: kitor on February 13, 2019, 05:24:04 PM
Oh hello!

Code: [Select]
Dry[WarpPUX]> sysvers
SystemIF 1.01
DRYOS version 2.3, release #0060+p4
 MACH 0.51
Title: Re: Canon EOS R
Post by: kitor on February 14, 2019, 08:03:51 AM
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.
Title: Re: Canon EOS R
Post by: Danne on February 14, 2019, 08:12:18 AM
Geniuses.
Title: Re: Canon EOS R
Post by: a1ex on February 14, 2019, 06:21:17 PM
Initial notes:

- Encryption changed. Wasn't able to look inside the firmware update. Unable to create FIR files for this camera.
- Other than that, bootloader and overall code structure look familiar.
- Portable ROM dumper worked (https://bitbucket.org/hudson/magic-lantern/commits/b6ec71d104dcb66f48802707467fd7e8036816ac?at=recovery) after (https://bitbucket.org/hudson/magic-lantern/commits/230b4fdd1ad3f31c3e4c93155e4504d83cc1c657?at=recovery) some (https://bitbucket.org/hudson/magic-lantern/commits/5b87791d9c225bb6c7a2feefed570f8b955317db?at=recovery) minor (https://bitbucket.org/hudson/magic-lantern/commits/1ff7677fcababfbbebd44d386aa5f312656e404a?at=recovery) tweaking (https://bitbucket.org/hudson/magic-lantern/commits/19f18f0492eaa4ea86c4550e33f24733aeb54fe5?at=recovery).
- Display buffer in bootloader context: 1024x682, otherwise like M50 (UYVY).
- LED address: 0xD01300D4 (0xD01300D8/DC maybe also valid).
- CPU info: identical to M50/SX70.
- Early startup: identical to M50 (yes, this entire block (https://bitbucket.org/hudson/magic-lantern/src/digic6-dumper/platform/M50.101/consts.h?fileviewer=file-view-default#consts.h-9) is identical, same stub addresses).
- Can jump to main firmware (with this trick (https://bitbucket.org/hudson/magic-lantern/commits/7d4d8bbd3b0257eb7cc893777f6e47d7684b3970?at=digic6-dumper)). Autoexec.bin is loaded on both CPU cores (https://bitbucket.org/hudson/magic-lantern/commits/0f8fc984f719c52d3be1749be20133e643f0bdd6?at=digic6-dumper) (maybe there are more?)
- Can save log files and dump ROM from main firmware.
- Overall, very similar to M50, but closer to "classic" EOS firmware (i.e. less of a PowerShot). Also has a MPU.
- Most of the code runs from ROM, very much like M50.
- Source code committed to digic6-dumper (https://bitbucket.org/hudson/magic-lantern/branch/digic6-dumper) branch (initial platform directory) and recovery (https://bitbucket.org/hudson/magic-lantern/branch/recovery) branch (portable ROM dumper, CPU info).

... and took a lot of pain to debug this for Alex and me.

It's true, it took us many hours of debugging, but compared to other models, this was quite easy. It definitely wasn't a matter of staring at the code for hours or days with no idea what to do next (cough 7D, EOSM shutter bug, 80D io_trace and many others). Yes, the camera was stubborn, but there was visible progress every few dozens of minutes (except during our breaks).

That was partly because most of the hard work was already done for M50 and all other earlier models, so it was mostly a matter of identifying what to tweak. And because Canon didn't change *that* much (except for the FIR encryption). And I didn't have to hold any needle on the UART connector :D
Title: Re: Canon EOS R
Post by: Walter Schulz on February 14, 2019, 06:39:23 PM
- Encryption changed.

Boy, really hate to read that!
Title: Re: Canon EOS R
Post by: Indy on February 14, 2019, 11:34:15 PM
Boy, really hate to read that!
Working on it with Alex :-)
Title: Re: Canon EOS R
Post by: kitor on February 15, 2019, 07:31:14 AM
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]
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 (https://www.magiclantern.fm/forum/index.php?topic=7531.msg212071#msg212071).


Quote
And I didn't have to hold any needle on the UART connector
Yup. Fortunately with bootflag enabled, now RX is sufficient.
Title: Re: Canon EOS R
Post by: a1ex on February 15, 2019, 05:05:15 PM
This camera has 2 GiB (https://www.magiclantern.fm/forum/index.php?topic=5071.msg212085#msg212085) of RAM 8)

Canon already struggled to pack this amount of RAM into the 32-bit address space: only the first GiB is visible as regular ("cacheable") memory. The second GiB is only visible as "uncacheable", and - just a guess - probably used exclusively by DMAs (image processing etc). Then, there are 512 MiB reserved from peripherals (addresses starting with C and D), 256 for the main ROM (starting with E), 256 for the slow (serial?) flash (starting with F, but apparently unused on R), and a couple of small regions overlapped here and there (DF - probably some sort of TCM; BFE - something with special meaning, etc).

MMU configuration is very similar to DIGIC 7:
Code: [Select]
00001000-00001FFF -> 00000000-00000FFF (-1000) O:NCACH I:WB,WA  P:RW       [ CPU0 only ]
00001000-00001FFF -> 00001000-00001FFF (   +0) O:NCACH I:WB,WA  P:RW       [ CPU1 only ]
00002000-3FFFFFFF -> 00002000-3FFFFFFF (   +0) O:NCACH I:WB,WA  P:RW       [ cacheable RAM - only the first GiB ]
40000000-BFFFFFFF -> 40000000-BFFFFFFF (   +0) O:NCACH I:NCACH  P:RW       [ uncacheable RAM - 2 GiB ]
C0000000-C2FFFFFF -> C0000000-C2FFFFFF (   +0) Device           P:RW XN    [ MMIO area ]
C4000000-C4FFFFFF -> C4000000-C4FFFFFF (   +0) Device           P:RW XN
C8000000-CAFFFFFF -> C8000000-CAFFFFFF (   +0) Device           P:RW XN
CC000000-CDFFFFFF -> CC000000-CDFFFFFF (   +0) Device           P:RW XN
D0000000-D0FFFFFF -> D0000000-D0FFFFFF (   +0) Device           P:RW XN
D2000000-D2FFFFFF -> D2000000-D2FFFFFF (   +0) Device           P:RW XN
D4000000-D5FFFFFF -> D4000000-D5FFFFFF (   +0) Device           P:RW XN
D7000000-D9FFFFFF -> D7000000-D9FFFFFF (   +0) Device           P:RW XN
DE000000-DEFFFFFF -> DE000000-DEFFFFFF (   +0) Device           P:RW XN
DF000000-DFFFFFFF -> DF000000-DFFFFFFF (   +0) O:NCACH I:WB,WA  P:RW       [ TCM? ]
E0000000-E7FFFFFF -> E0000000-E7FFFFFF (   +0) O:WB,WA I:WB,WA  P:R        [ main ROM ]
E8000000-EFFFFFFF -> E8000000-EFFFFFFF (   +0) Strongly-ordered P:R  XN    [ ? ]
F0000000-F7FFFFFF -> F0000000-F7FFFFFF (   +0) O:WB,WA I:WB,WA  P:R        [ only used on M50; at least on DIGIC 7, it's much slower than main ROM ]
F8000000-FFFFFFFF -> F8000000-FFFFFFFF (   +0) Strongly-ordered P:R  XN    [ ? ]

i.e.
- 00000000-00000FFF virtual: unavailable (likely used to catch null pointer errors)
- 00001000-00001FFF virtual: private page for each of the two cores (mapped to either 00000000-00000FFF or 00001000-00001FFF physical)
- other than that, flat mapping everywhere (with different permissions and attributes)
- some regions in the MMIO (Device) areas are unavailable; minor differences from DIGIC 7 in the C0000000 - DEFFFFFF range.
- anything above 0x40000000 (until BFDFFFFF) is uncacheable; this is the main RAM
- the first GiB of RAM is also visible as cacheable: 00002000-3FFFFFFF
Title: Re: Canon EOS R
Post by: Mike Tornado on February 15, 2019, 07:00:54 PM
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]
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 (https://www.magiclantern.fm/forum/index.php?topic=7531.msg212071#msg212071).

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

Did you try sht_memoryread2 B:/K424_00.bin 0xE0000000 0x00040000 ?
Title: Re: Canon EOS R
Post by: kitor on February 15, 2019, 07:11:48 PM
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 :(
Title: Re: Canon EOS R
Post by: civita on March 08, 2019, 05:40:16 PM
A new firmware regarding EOS R was released!

https://www.canon-europe.com/support/consumer_products/products/cameras/digital_slr/eos-r.aspx?type=firmware
 (https://www.canon-europe.com/support/consumer_products/products/cameras/digital_slr/eos-r.aspx?type=firmware)
Canon EOS R Firmware v.1.1.0 changes:
  • Support for "continuous shooting" is available when "silent shutter" has been enabled.
  • Corrects a phenomenon in which an error may occur if there is a large number of files in a specific format on the memory card.
  • Corrects a phenomenon in which an error may occur when silent shutter has been enabled.
  • Corrects a phenomenon in which horizontal linear noise may occur when using specific lenses together with certain recording image quality settings.
  • Corrects a phenomenon in which the information displayed in the viewfinder may become abnormal.

Not sure is it helpful or not: Canon has already updated the firmware for the RP. Ver. 1.1.0  for windows and MAC
 
1. Support for Camera Control API (CCAPI)* function, for software developers, has been added.


https://www.usa.canon.com/internet/portal/us/home/support/details/cameras/eos-dslr-and-mirrorless-cameras/mirrorless/eos-rp?subtab=downloads-firmware (https://www.usa.canon.com/internet/portal/us/home/support/details/cameras/eos-dslr-and-mirrorless-cameras/mirrorless/eos-rp?subtab=downloads-firmware)
Title: Re: Canon EOS R / RP
Post by: kitor on March 09, 2019, 10:36:43 PM
If anyone already had his hands on RP and have USB UART that's able to work with 1v8 levels, you may try to dump the bootloader using my previous code.
https://twitter.com/_kitor/status/1095956664287555584
UART will be probably hidden under thumb rubber, as it has same style connector and very similar location to R.

So far I had no time to play more with R unfortunately.
BTW - if anyone knows where I can get my hands on 0.4mm pitch FFC cable (8 pin is needed for R and probably RP UART), please send me PM. Other devices that may use this internally are also a valid option (to harvest from dead / get spare parts).
Title: Re: Canon EOS R / RP
Post by: Walter Schulz on March 10, 2019, 01:07:06 AM
Are you sure about 0.4mm?
Title: Re: Canon EOS R / RP
Post by: kitor on March 10, 2019, 01:55:15 PM
Almost. Standard 0.5mm is too wide, I wasn't able to connect both TX and RX without shorting one of them to next pin (GND). I measured piece of FPC cut to fit into connector and divided into 8 pins, got roughly this 0.4mm pitch.
Title: Re: Canon EOS R / RP
Post by: paulleavitt on April 13, 2019, 11:49:05 PM
Hey all! I have a GH5 now so I've been out of the ML world for a while, but I'm glad you guys are still at it!

My business partner has an EOS R that he's said he's willing to run some tests on if that's helpful for y'all (and if the likelihood of bricking is reasonably low). If that would be helpful, just let me know!

Paul

Title: Re: Canon EOS R / RP
Post by: kitor on April 14, 2019, 02:21:17 PM
At the moment it's impossible to run anything without enabling bootflag via UART first. Something like this:
https://twitter.com/_kitor/status/1095729715284008960
Title: Re: Canon EOS R / RP
Post by: aprofiti on April 18, 2019, 01:35:17 PM
Canon released a new 1.2.0 firmware (https://www.canonwatch.com/canon-eos-r-firmware-ver-1-2-0-available-to-download/amp/) update for Eos R.
Title: Re: Canon EOS R / RP
Post by: kitor on April 26, 2019, 06:29:44 PM
Can someone with working toolchain checkout this repo/branch: https://bitbucket.org/kitorPL/magic-lantern/branch/kitor/eosr_120
and compile for me minimal hello world?

Code: [Select]
cd minimal/hello-world
make MODEL=R

On 1.1.0 hello_world gave me LV crashes instead of text printed, but at least it worked.
Between updating, dumping 1.2.0 and updating stubs I updated my WSL distro (Ubuntu 16.04 to 19.04) and linker stopped working:
Code: [Select]
Using /usr/bin/arm-none-eabi-gcc (from PATH).
[ VERSION  ]   ../../platform/R.120/version.bin
[ CPP      ]   magiclantern.lds
(...)
[ LD       ]   magiclantern
arm-none-eabi-ld:magiclantern.lds:1: syntax error
make: *** [../../src/Makefile.src:224: magiclantern] Error 1
indeed magiclantern.lds is generated broken :( https://i.imgur.com/iLLqR2B.png

So i setup toolchain on another machine (this time Debian testing), built it and camera lockups completely, even before any print from ICU on UART:
Code: [Select]
BootLoadNow jump to AUTOEXEC.BIN(0x00800000)!!
//and dead...

ML Rescue as autoexec.bin still works from the same card...

Not sure if that's my toolchain problem or what. For new stubs I even compared them against M50 ROM and I'm sure they are right.
Title: Re: Canon EOS R / RP
Post by: dfort on April 27, 2019, 01:03:21 AM
Compiled fine here in Costa Rica -- no errors but no testing either.

On my downloads page. (https://bitbucket.org/daniel_fort/magic-lantern/downloads/)
Title: Re: Canon EOS R / RP
Post by: kitor on April 27, 2019, 08:44:42 AM
Thanks. Same behavior unfortunately  :(
Time to dig into ML code then.
Title: Re: Canon EOS R / RP
Post by: aprofiti on April 27, 2019, 12:08:24 PM
It probably locked due to firmware signature (https://www.magiclantern.fm/forum/index.php?topic=23296.msg215053#msg215053) not corresponding.
I saw you didn't updated (https://bitbucket.org/kitorPL/magic-lantern/commits/248f71a0c267956894cc9c23747f1b804933d856) it yet in your repo.

You can also replace qprintf messages to print using uart if you prefer to not use qemu
Title: Re: Canon EOS R / RP
Post by: kitor on April 27, 2019, 01:59:06 PM
Hmm, I was sure that digic6 branch had no signature testing. At least it was the case at some moment just when 1.1.0 update arrived ;)

Then I'll remove signature check as I don't have qemu working for R yet (got path from Alex for m50, however this needs mods for R), and on-camera computation won't work at the moment (guess why :) )
Title: Re: Canon EOS R / RP
Post by: dfort on April 27, 2019, 03:14:49 PM
Just saw this article (https://www.thephoblographer.com/2019/04/25/canon-eos-rp-is-capable-of-being-controlled-by-user-generated-apps/) about Canon's CCAPI (Camera Control Application Program Interface) software developer's kit. Don't know anything about it or if the R is one of the supported cameras but the RP is.

[EDIT] Looks like the cameras supported at this time are the RP, Canon 200D II / SL3 and Powershot SX70 HS.
Title: Re: Canon EOS R / RP
Post by: kitor on April 27, 2019, 08:13:30 PM
It probably locked due to firmware signature (https://www.magiclantern.fm/forum/index.php?topic=23296.msg215053#msg215053) not corresponding.
And bingo! After skipping check it runs like before (crashes LV). Added some blinking, LV crashes on bmp_vram_raw() as I have 4 blinks and then crash :)
Code: [Select]
static void hello_world()
{
    blink_led(1000);
    blink_led(1000);
    blink_led(1000);
    blink_led(1000);

    while (!bmp_vram_raw())
    {
        blink_led(200);
    }

    while(1)
    {
        blink_led(500);
        font_draw(100, 75, COLOR_WHITE, 3, "Hello, World!");
    }
}

Unfortunately when tracing bmp_vram_raw() i saw dark magic :(
Title: Re: Canon EOS R / RP
Post by: kitor on April 27, 2019, 09:04:02 PM
At least I was able to get firmware signature updated and collect stack dump for Alex when he's back.

Would create MR, however I don't have rights for official repo...

Is there any built-in way to send some prints to log on card? Without qemu and still no display, UART using needle (literally as I still don't have proper cable) is quite annoying...
Title: Re: Canon EOS R / RP
Post by: histor on April 27, 2019, 09:25:17 PM
Simple registering here - https://developers.canon-europe.com/developers/s/login/SelfRegister
gives you enough information.
Latest CCAPI supports EOS 250D, EOS RP (firmware 1.1.0 is required), PowerShot SX70 HS (firmware 1.1.0). Usual SDK support Eos R from version EDSDK v3.9.0, EOS RP – from EDSDK v13.10.0, EOS 250D – from EDSDK v13.10.20. These are consequent releases.
There were rumors that you can complete registration, fill the profile and get access to it after awhile.
If somebody needs version 2.14 (models up to EOS Kiss X70 / EOS 1200D / EOS REBEL T5 / EOS Hi / EOS M2) – it’s available in the net.
Title: Re: Canon EOS R / RP
Post by: srsa on April 27, 2019, 09:54:36 PM
Simple registering here (...)
gives you enough information.
Those who wish to work on ML in the future may want to read the terms & conditions, especially the section "Confidentiality". Their stuff is not open source.
Title: Re: Canon EOS R / RP
Post by: dfort on April 27, 2019, 11:06:22 PM
Would create MR, however I don't have rights for official repo...

Anyone can create a pull request on the main repo. I'm good with merging it as long as it doesn't disturb the other platforms.
Title: Re: Canon EOS R / RP
Post by: kitor on April 27, 2019, 11:22:50 PM
Nevermind, tried to create PR from master repo instead of mine  :'( But I'll wait a bit, since...

In the meantime I traced the problem to bmp_vram_info. I was able to hand-draw some lines on display using code from here:

https://www.magiclantern.fm/forum/index.php?topic=17360.510
and display buffers from RAM dump: 1100100 12ffc00

No related picture as I was too lazy to make one, however now I understand mostly that this structure holds addresses of both buffers
Code: [Select]
struct bmp_vram_info
{   
    struct MARV * vram1;        /* one of the two bitmap buffers - statically allocated? */
    struct MARV * vram2;        /* the other bitmap buffer */
    struct MARV * back_vram;    /* we need to write to the other one */
};

but I still don't know how to find this pointer from stubs.C / how Alex got one:
Code: [Select]
/** Bitmap **/
DATA_PTR(    0xFB1C,  bmp_vram_info)
Funny enough, when set to exactly the same value as on M50 LV won't crash, but drawing won't work either.
DATA_PTR is relative to RAM?
Title: Re: Canon EOS R / RP
Post by: aprofiti on April 27, 2019, 11:50:43 PM
Don't know if it's a valid way to find bump buffer without a ram dump or MMIO logs, but found the "SetDrawWait" (https://bitbucket.org/aprofiti/magic-lantern/commits/d9d813cf507eb4f4858336c2f422331da4fce5db) reference while looking for 6d2 and 800d stubs.

Pointer inside the function's body appears to match the 200D and 77D dumps. Maybe you can try with EOS R?
Title: Re: Canon EOS R / RP
Post by: kitor on April 28, 2019, 12:00:03 AM
Got another RAM dump and this makes sense, those are buffers I drawn into myself (dump starts from 0x40000000):

Code: [Select]
kitor@kitor-pc:Desktop$ xxd -e -s 0x0000FB1C -l 0x0C RAM.BIN     #bmp_vram_info
0000fb1c: 412ff900 414ff400 414ff400           ../A..OA..OA      #vram1, vram2, back_vram

kitor@kitor-pc:Desktop$ xxd -e -s 0x002ff900 -l 0x2C RAM.BIN    #MARV for 2ff900
002ff900: 5652414d 41100100 00000000 11060200  MARV...A........
002ff910: 00000400 000002aa 412ff91c 4d454d50  ........../APMEM
002ff920: 00000010 00000000 41100000           ...........A

kitor@kitor-pc:Desktop$ xxd -e -s 0x004ff400 -l 0x2C RAM.BIN    #MARV for 4ff400
004ff400: 5652414d 412ffc00 00000000 11060200  MARV../A........
004ff410: 00000400 000002aa 414ff41c 4d454d50  ..........OAPMEM
004ff420: 00000010 00000000 412ffadc           ........../A

So the problem seems to be somewhere deeper, as LV hangs (and ML throws exception) directly on bmp_vram_raw() call

[e] I don't understand something:

Code: [Select]
  uart_printf("bmp_vram_info %p \n", bmp_vram_info);
    uart_printf("bmp_vram_info[0] %p \n", bmp_vram_info[0]);
    uart_printf("vram1 %p \n", bmp_vram_info[0].vram1);
    uart_printf("vram2 %p \n", bmp_vram_info[0].vram2);
    uart_printf("back_vram %p \n", bmp_vram_info[0].back_vram);
    uart_printf("bmp_marv, should match above %p \n", bmp_marv());

Code: [Select]
bmp_vram_info 0xfb1c
bmp_vram_info[0] 0x1
vram1 0x1
vram2 0x4fc0278
back_vram 0x41100000
bmp_marv, should match above 0x1
Title: Re: Canon EOS R / RP
Post by: kitor on April 28, 2019, 12:55:12 PM
Oh, Hai!

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.imgur.com%2FsyCi8Nx.jpg&hash=5de184a634891627ac21e0a474ce9a1c)
https://twitter.com/_kitor/status/1122454369235079169

I don't understand this at all. Seems that dump_file shifts down ram offsets by 0X10?! explanation below
bmp_vram_info sits at 0xFB2C, not 0xFB1C. How I found this?

Code: [Select]
for(uint32_t * i = 0x40000000; i < 0x80000000; i+=1){
        if(*i == 0x412ff900) uart_printf("vram1 %p \n", i);
        if(*i == 0x414ff400 ) uart_printf("vram2 %p \n", i);
    }

and a few moments later
Code: [Select]
vram1 0x4000fb2c
vram2 0x4000fb30
vram2 0x4000fb34

But what's werid MARV structures sits exactly where I found them in a dump:

Code: [Select]
bmp_vram_info 0xfb2c
bmp_vram_info[0] 0x412ff900
vram1 0x412ff900
vram2 0x414ff400
back_vram 0x414ff400

yup, that's shows my desperation  8)

@dfort - new MR coming in a moment :)

[edit]
OK, now I know what happened. Our initial dump on 1.1.0 has been shifted. I got MARVs from new dump, bmp_vram_info I was checking on old one all the time... working on pointers at 2AM is a bad idea.
Title: Re: Canon EOS R / RP
Post by: dfort on April 28, 2019, 01:37:03 PM
Great work @kitor -- PR merged.
Title: Re: Canon EOS R / RP : new FIR version
Post by: Indy on May 04, 2019, 01:20:19 PM
Hi,

FYI, Canon has changed the way signature and encryption is done for EOS R and EOS RP (FIR version 5).

Previous versions were:
https://magiclantern.fandom.com/wiki/Firmware_file
https://magiclantern.fandom.com/wiki/Fir_Security

As soon as debugging EOS R or RP will be possible within QEmu, I'll continue my investigations started with Alex. He owns holidays after giving years of time to ML.

Kind regards
Indy
Title: Re: Canon EOS R / RP
Post by: kitor on May 04, 2019, 02:15:42 PM
A bit of ML offtopic:

1.2.0 seems to remove banding issues:
https://www.canonrumors.com/firmware-v1-2-0-seems-to-have-solved-a-banding-issue-that-was-present-in-the-canon-eos-r/
Quote
Ladies and Gentlemen! WE HAVE DONE IT!! Thank you so much to the many of you who gave feedback, shared my videos, posted in forums and relayed the information you received from Canon, I can confirm that Firmware update 1.2.0 resolves the banding issue I reported back in November on the Canon EOS R!

Tamron 70-200 G2 works great with R
Tired of waiting for RF 70-200 (and in need for one soon) I wanted to pick used 2.8L IS II USM. But found that Tamron presented not so long ago 2nd gen of their lineup (and new SP 70-200mm F/2.8 Di VC USD G2 is roughly the same price as used 2.8L IS II). As I have good contact with one camera store, I played a little with this lens via basic EF-RF adapter and it worked flawlessly, AF was fast and accurate, no problems with VR (shots like 1/30 on 200mm).
Interesting (and not found in manual) feature is that tripod mount will mount directly to Arca Swiss compatibile Quick Releases, what I found by accident.

Sample full-res jpeg (from raw, without LR lens corrections; 200mm/2.8 ISO 100): https://kitor.pl/eos_r/tamron.jpg
This is how this combo looks:
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fkitor.pl%2Feos_r%2Ftamron_r.jpg&hash=cae02e2274b1909495b9de1c06a586f9)

As for missing control ring on EF lenses, I'm using back-button focus, thus I have exposure lock on half-shutter. So i set exp-lock button + upper dial as ISO change. Works much better than fighting with touch bar and saves a lot of money on adapter with control ring.
Title: Re: Canon EOS R / RP : new FIR version
Post by: kitor on May 04, 2019, 02:39:32 PM
As soon as debugging EOS R or RP will be possible within QEmu, I'll continue my investigations started with Alex. He owns holidays after giving years of time to ML.

https://www.magiclantern.fm/forum/index.php?topic=2864.msg215604#msg215604
There is a patch for M50 here (https://www.magiclantern.fm/forum/index.php?topic=23296.msg210088#msg210088); IIRC it worked on R with minimal changes. Will clean them up for committing, but I think it will happen after bringing the current state into mainline.

I'm not competent enough to do those 'minimal changes' myself unfortunately, at least not without any hints where to look.
Title: Re: Canon EOS R / RP
Post by: oc_masta on May 05, 2019, 06:29:29 PM
Can someone with far more intelligence than me, explain the high level concept of what needs doing and how it works.

Is it a hunt for the memory addresses than respond to the things we need. LED at address xxxxxxx, memory for sensor data at xxxxxx ??

I'm genuinely very curious and would love to learn more if someone can break it down just a little.
Cool Stuff!
Title: Re: Canon EOS R / RP
Post by: kitor on May 05, 2019, 07:26:20 PM
Up to now, mostly like you described.
Quote
Is it a hunt for the memory addresses than respond to the things we need. LED at address xxxxxxx, memory for sensor data at xxxxxx ??

But not only for hardware memory addresses, but also for location of needed DryOS functions that we need to call. In 'normal' programming you just include headers for some library and use it. Here you need to find that stuff in disassembled ROM first, understand how it works, what parameters it can take (and thus how to call it). This is already mostly done with previous cameras, so you just need to find proper memory location that holds your needed function. Later also find how to 'hook' into Canon tasks to get data from them, etc.

And DryOS (and low level stuff - new Digic processors) changes with time. That's why Alex did 'fishy' M50 port that allows ML menu access, but it breaks things for older devices so he decided not to push code until he sorts this out.
Title: Re: Canon EOS R / RP
Post by: sast on May 18, 2019, 08:52:46 PM
Hello,
is there somebody, who is still working on ML for Canon EOS R?  >:(

Before I was using ML on the Canon 5D III. ML gave me an perfectin handling of the camera.
I don't now how to do all the things on the EOS R without ML (f. e. Intervalometer, Motion detection, the modules). 

Best regards from Germany
Title: Re: Canon EOS R / RP
Post by: Walter Schulz on May 18, 2019, 09:10:34 PM
It's mantra time again ...

If there is no ML for your cam act like there will be no ML for your cam ever.
Title: Re: Canon EOS R / RP
Post by: kitor on May 18, 2019, 11:17:17 PM
Hello,
is there somebody, who is still working on ML for Canon EOS R?  >:(

Refer to this (https://www.magiclantern.fm/forum/index.php?topic=19737.msg216007#msg216007). No posts = no news.

Quote
f. e. Intervalometer, Motion detection,
So we have something in common (had to bring notebook with me last time I suddenly needed intervalometer). However I risked a lot to my camera (as seen in this thread) to at least try to make it happen.
Title: Re: Canon EOS R / RP
Post by: sast on May 24, 2019, 07:06:44 PM
Hello kitor,
thanx for your work to make it happen.
Everyday I take a look in this forum to see the development.
Best regards from Germany
Title: Re: Canon EOS R / RP
Post by: DaGentooBoy on June 25, 2019, 03:38:39 PM
I have been using/watching ML for years on several different cameras. I love the flexibility that ML provides and I am really excited about the 4k options that ML has brought to the newer cameras.

I recently upgraded to an EOS R and I was trying to find the version of QEMU that works with the R as well as the current progress mapping functions. I have a background in embedded programming and hardware design. If someone can help me get caught up I can try to lend a hand.
Title: Re: Canon EOS R / RP
Post by: johannjr2 on July 13, 2019, 04:05:16 PM
Is there a patreon page where we can support the development of certain cameras like the EOS R/ RP or even 5d mark IV (any newer canon with dual pixel autofocus). Thanks in advance!
Title: Re: Canon EOS R / RP
Post by: Walter Schulz on July 14, 2019, 08:07:56 PM
No
Title: Re: Canon EOS R / RP
Post by: sast on July 16, 2019, 10:14:25 PM
Warum so eine unfreundliche Antwort auf eine gute Frage?
Title: Re: Canon EOS R / RP
Post by: kitor on July 17, 2019, 07:45:04 AM
Warum so eine unfreundliche Antwort auf eine gute Frage?
Która odpowiedź jest niegrzeczna?*

English, please.  ::)

Sorry, had to.
Title: Re: Canon EOS R / RP
Post by: reddeercity on July 17, 2019, 07:56:00 AM
Warum so eine unfreundliche Antwort auf eine gute Frage?
Google say it's German -  the translation  "why such a rude answer to a good question"
not sue what there are referring to thou
Title: Re: Canon EOS R / RP
Post by: kitor on July 17, 2019, 09:18:35 AM
Thats why I asked my question - in Polish :) (I understand German enough for his post)
For 'when' question (https://www.magiclantern.fm/forum/index.php?topic=23927.0) no wonder answer was rude. For donations, it was short but not rude.
Maybe it's better to remove those posts asking for dates, instead of replying like this every time...
Title: Re: Canon EOS R / RP
Post by: Ant123 on July 17, 2019, 12:14:00 PM
2 Walter Schulz and other moderators

Why don't you oblige new users to read the FAQ before they can post? And then delete dumb messages / ban them.
There is no advertising on this forum. So why do we need to see their useless posts?
Title: Re: Canon EOS R / RP
Post by: Walter Schulz on July 17, 2019, 08:51:18 PM
First: I'm not a moderator (and have no intention to be one, better for the forum and me).

I cannot imagine a foolproof system to avoid such messages. You will always have an amount of people not reading FAQs or unable to grab the concepts of ML development or just feeling entitled (list not complete) or really, really believing they are helping. And such issues are not exclusive to newbies.

Noise by such users is bearable IMO. In "slow" forum times like this it may appear like an increase. No need for drastic measures (again: IMO).
Title: Re: Canon EOS R / RP
Post by: vlasena on August 05, 2019, 11:24:20 AM
Also would love to see ML for EOS R. Any info on signature and decryption of these cameras?

Thanks!
Title: Re: Canon EOS R / RP
Post by: 71m363nd3r on August 07, 2019, 12:00:07 AM
Also would love to see ML for EOS R. Any info on signature and decryption of these cameras?

Thanks!

How much bucks would you donate for ML contribution for EOS R?
Title: Re: Canon EOS R / RP
Post by: sast on August 13, 2019, 06:31:19 AM
150 € - 200 €
Title: Re: Canon EOS R / RP
Post by: jga on August 16, 2019, 05:21:48 PM
150 € - 200 €

Me too.
Title: Re: Canon EOS R / RP
Post by: 71m363nd3r on August 17, 2019, 08:34:06 PM
150 € - 200 €
Me too.

You can start with 50€ the link is here https://magiclantern.fm/donate.html
when you see progress you can pay another 50€
And when is finally out you can use it first, before others by donating the rest.
And now show it that you meant it for real with donating.
Title: Re: Canon EOS R / RP
Post by: Travis on August 20, 2019, 11:44:17 PM
It would be absolutely incredible ML came to the RP. It'd be a game changer in terms of price / performance for a full frame. They seem very protective of their cinema line though.

Too bad you can't fork the firmware and charge money for it without running into issues
Title: Re: Canon EOS R / RP
Post by: kitor on August 23, 2019, 12:12:22 PM
R firmware 1.3: https://www.canon.co.uk/support/consumer_products/products/cameras/digital_slr/eos-r.html?type=firmware
Quote
Firmware Version 1.3.0 incorporates the following enhancement:
1. Support for the RF24-240mm F4-6.3 IS USM lens has been added.

RP firmware 1.2: https://www.canon.co.uk/support/consumer_products/products/cameras/digital_slr/eos-rp.html?type=firmware
Quote
Firmware Version 1.2.0 incorporates the following enhancement and fix:
1. Support for the RF24-240mm F4-6.3 IS USM lens has been added.
2. Corrects a phenomenon in which the top of some captured images may be dark during high-speed sync shooting with an external flash.

No mentions about fixes for recent vulnerabilities.
Title: Re: Canon EOS R / RP
Post by: Sapporo on August 24, 2019, 10:07:12 AM
R firmware 1.3: https://www.canon.co.uk/support/consumer_products/products/cameras/digital_slr/eos-r.html?type=firmware
RP firmware 1.2: https://www.canon.co.uk/support/consumer_products/products/cameras/digital_slr/eos-rp.html?type=firmware
No mentions about fixes for recent vulnerabilities.
Not fixed. https://www.magiclantern.fm/forum/index.php?topic=24385.msg219582#msg219582
"EOS R firmware version 1.3.0 and earlier, EOS RP firmware version 1.2.0 and earlier, EOS RP GOLD firmware version 1.2.0 and earlier"
Title: Re: Canon EOS R / RP
Post by: kitor on August 24, 2019, 11:41:15 PM
This info was published before those firmware were even mentioned elsewhere, so I assumed it was an error.
But yes, that makes sense.
Title: Re: Canon EOS R / RP
Post by: Sapporo on August 25, 2019, 08:23:37 AM
This info was published before those firmware were even mentioned elsewhere, so I assumed it was an error.
But yes, that makes sense.
CVE-2019-6001 published 6 August, firmware 1.3.0 published 7 August. 1.3.0 was already ready.
Title: Re: Canon EOS R / RP
Post by: DeafEyeJedi on September 01, 2019, 07:15:10 PM
Just a heads up... I currently have an EOS R kit in my hands. It's a loaner. Good thing this came with an adapter to go from R to EF mount.

Let me know if there's anything I can contribute while we're at it. Will probably have access to this for a week or so.

That 4K crop is a joke but doable w Tokina 11-20mm 2.8 from what I've seen so far. Such a weird animal though.  :o
Title: Re: Canon EOS R / RP
Post by: gtemp on October 01, 2019, 08:56:12 PM
Hi, I really only need one single feature from ML for the EOS R, and that's the ability to auto-restart video when it reaches the file size/time limit (30 mins, as I understand it.) Can ML currently allow this on the EOS R? My 5DMkII can do this with ML, and I'd love to upgrade but I need continuous video without having to return to the camera. Multiple files is A-OK. Any insight appreciated!
Title: Re: Canon EOS R / RP
Post by: Walter Schulz on October 04, 2019, 08:15:09 AM
Get yourself a cam suitable for your needs.
Title: Re: Canon EOS R / RP
Post by: kitor on October 04, 2019, 11:57:30 AM
Quote
Can ML currently allow this on the EOS R?

Is ML for R mentioned anywhere?

I need to upgrade (and dump) 1.3 and 1.4 and hopefully update stubs for 1.4. Yup, I'm still on 1.2.
Title: Re: Canon EOS R / RP
Post by: vlasena on November 09, 2019, 11:45:12 PM
How much bucks would you donate for ML contribution for EOS R?
100 bucks
Title: Re: Canon EOS R / RP
Post by: kotik on November 21, 2019, 04:21:00 PM
Hi, I really only need one single feature from ML for the EOS R, and that's the ability to auto-restart video when it reaches the file size/time limit (30 mins, as I understand it.) Can ML currently allow this on the EOS R? My 5DMkII can do this with ML, and I'd love to upgrade but I need continuous video without having to return to the camera. Multiple files is A-OK. Any insight appreciated!

With an external recorder like the Atoms Ninja V, you can do 10-bit continues recording through the HDMI output port.
Title: Re: Canon EOS R
Post by: Ireversible on December 05, 2019, 02:53:52 PM
Tried to run some initial tests on the EOS R; unfortunately, this is all we've got:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fa1ex.magiclantern.fm%2Fbleeding-edge%2FR%2Fr.jpg&hash=94380fc020e2b71807adeaf9c08f5d41)

The error screen looks just like on previous models, which is encouraging. The camera recognized there was a FIR file on the card, for the correct model, otherwise it would have printed "Update file cannot be found". The error message means it could not verify the checksum; Canon might have changed the FIR file format, or maybe also the encryption.



Edit: progress - apparently it doesn't like tiny FIR files, but otherwise it accepts them:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fa1ex.magiclantern.fm%2Fbleeding-edge%2FR%2Fprogres.jpg&hash=ca755ea2cfeb71c418ad02fea6ae8233)

Edit (February 2019): turns out it was just the decryption code locking up with some FIR files.
Encryption changed - we can no longer create FIR files for this camera.

Hi
I just bought a Canon R and I hope in the future to install a magic lantern firmware on it, but what wrote A1ex is not very encouraging...Is there still hope or will we never see ML on canon r?
Thanks

Title: Re: Canon EOS R / RP
Post by: Mariiiik on December 05, 2019, 06:38:30 PM
Is it possible to create another way of donations besides bitcoin? It may be to make a separate account for the team that is working on EOS R, it seems to me that this will greatly accelerate the collection of donations. Sorry for my english
Title: Re: Canon EOS R / RP
Post by: DoctorJones on December 08, 2019, 11:00:08 AM
I know it’s a faux pas asking annoying questions about ML release features, so firstly; thank you so much to all ML developers. If I ever get the pleasure of using ML on one of my cameras I will certainly donate anything I can.

Does anyone know if ML for EOS R is expected to enable 10bit recording in 1080p over HDMI? I love the look of 10bit in C-log, but I don’t have the hardware for 4K.
Title: Re: Canon EOS R / RP
Post by: kitor on December 16, 2019, 06:23:04 PM
Does anyone know if ML for EOS R is expected to enable 10bit recording in 1080p over HDMI? I love the look of 10bit in C-log, but I don’t have the hardware for 4K.

ML for R (or anything Digic 7+ (https://www.magiclantern.fm/forum/index.php?topic=19737.275)) is not expected to exist any time soon (https://www.magiclantern.fm/forum/index.php?topic=22770.msg216715#msg216715), and you're asking about specific features...

So far we have only proven that it's possible to run custom code.
I guess @a1ex that  "Magic lantern rescue" is misleading and should be replaced with another name for early development ports. Just a string swap may keep people a little less excited.
Title: Re: Canon EOS R / RP
Post by: IDA_ML on December 16, 2019, 07:31:17 PM
If I ever get the pleasure of using ML on one of my cameras ...

Indeed, ML is a lot of pleasure and fun to use.  If you don't have a camera that supports it, please don't wait forever.  Just consider spending 100-200 US$ for a used EOS-M or 100D body.  Both cameras are ML capable and work miracles with the entire lens arsenal of Canon and with almost any lens that you can imagine using cheap adapters.  Soon you will realize that these are the best 100-200 $ that you have spent in your life.  Good luck!     
Title: Re: Canon EOS R / RP
Post by: Lbs26 on February 25, 2020, 02:06:29 PM
Hi to all,i am new in this forum...i wanted to ask a question about Canon Eos R - banding stripes problems.
I have Eos R with the latest 1.6 firmware update,the banding is fixed in the faster shutter speeds at 100%,but in the longer shutter speeds it is till a big issue....
it occurs from 2-3 sec above in the darkest underexposed shadows,where in the shoter shutter speed even if i bring the exposure in post to +5 stops there is no banding.
Title: Re: Canon EOS R / RP
Post by: jo.meatloaf on March 15, 2020, 06:07:00 PM
Такая же проблема и на моем m6 mk ii. Похоже что жто проблема прошивки
Title: Re: Canon EOS R / RP
Post by: kitor on May 08, 2020, 12:15:11 PM
https://www.canonrumors.com/canon-announces-100-firmware-update-for-stop-motion-photography/

Wow, $100 for increase in LV resolution. With no HDMI output, and no focus peaking in many scenarios, so camera is basically useless for other things than stop-motion.
Title: Re: Canon EOS R / RP
Post by: coon on August 13, 2020, 11:10:31 PM
Hi,
I just got an EOS RP as my first camera recently. After watching some youtube videos about photography I've found out about magic lantern as a way to hack canon cameras. I have some experience with embedded software development (Arduino / AVR and STM32F4 / ARM) and I've also some knowledge about reverse engineering (x86/x64 on Windows). I've good knowledge in C / C++.

With the help of names_are_hard on discord I am already able to compile ML and qemu for the 50D, which meight help me getting familiar with ML development. Luckily a friend of mine has a 50D laying around which I can use for playing around, since he has a newer camera and doesn't need it right now.

Is there a way I can help? Is it possible to dump the firmware of the RP so I can take a look with Ghidra on it?
Title: Re: Canon EOS R / RP
Post by: Walter Schulz on August 16, 2020, 10:12:12 PM
Canon changed encryption/signature in RP. There is no Portable ROM Dumper (https://www.magiclantern.fm/forum/index.php?topic=16534.0) available ATM.
See https://www.magiclantern.fm/forum/index.php?topic=22770.msg215961#msg215961

Looks a little bit hackish: https://twitter.com/autoexec_bin/status/1095731428388716546
Title: Re: Canon EOS R / RP
Post by: a1ex on August 17, 2020, 11:29:41 AM
Actually, the portable ROM dumper (autoexec.bin version) worked on EOS R, but only after enabling the boot flag via UART.
Title: Re: Canon EOS R / RP
Post by: kitor on September 01, 2020, 11:05:46 PM
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.imgur.com%2F5RvCuUd.png&hash=9e5790b03e8dcc6d0a80b9ff103864b2)

Nothing to be excited about, just (finally) upgraded from 1.2.0 to 1.7.0 and checked that bootflag is still there, and dumper still works.
I have no plans for updating stubs in near future, as I tend to take to many projects at once.
Title: Re: Canon EOS R / RP
Post by: kitor on September 02, 2020, 10:28:19 AM
Cross-post from R5/R6 thread:

Canon basic dumper works on R! Not sure if without bootflag enabled too.

I created the files with Unix line endings (LF only). I made card by using EOScard, with only option "script" selected.
Both files (extend.m and script.req) you can download here: https://kitor.pl/eos_r/cbasic_dumper.zip

Of course credits for dumper goes to @srsa as I took his code directly from this post (https://www.magiclantern.fm/forum/index.php?topic=23296.msg227190#msg227190)

After I put card into camera, I went into playback mode, pressed Q/Set button and red light turned on. A minute later it was done, ROM.txt was saved to card root!
Title: Re: Canon EOS R / RP
Post by: coon on September 04, 2020, 06:07:17 PM
I can confirm that the Canon Basic dumper also works on the EOS RP.

ROM size is 32MB. Dumping takes about ~2 hours and 15 minutes so you better have your battery charged before dumping :).
You don't have to set the bootflag for that so this can be done without opening the case at all.
Title: Re: Canon EOS R / RP
Post by: Walter Schulz on September 04, 2020, 06:20:53 PM
Coon, can you retry with the code supplied by srsa? And compare time required?
https://www.magiclantern.fm/forum/index.php?topic=25305.msg230434#msg230434
Title: Re: Canon EOS R / RP
Post by: coon on September 04, 2020, 06:32:15 PM
Just tried that. It also worked out of the box and only took about 10 seconds.

Got two files: gang100.bin and gang200.bin which both have a size of 32MB.
This dump looks more reliable so this is the way to go I guess :)
Title: Re: Canon EOS R / RP
Post by: Walter Schulz on September 04, 2020, 06:34:59 PM
Thanks! This is really fast!
Title: Re: Canon EOS R / RP
Post by: coon on September 05, 2020, 11:11:59 AM
I can also confirm that enabling the bootflag via

Code: [Select]
private sub Initialize()
  EnableBootDisk()
end sub

does work aswell.

I've tried booting the portable ROM dumper (https://www.magiclantern.fm/forum/index.php?topic=16534.0) on the RP.
As soon as I close the battery lid, it loads in a glitchy way and crashes or aborts with an error message, since there is some text written in red.

Title: Re: Canon EOS R / RP
Post by: coon on September 05, 2020, 01:35:25 PM
After I've done some little adjustments in the display source code of the portable dumper, I am now able to see a clear picture :).

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.imgur.com%2FVm45eFr.jpg&hash=8b28291b226790dcfdfe29f2e9ff2d5d)

LCD of EOS RP has a resolution of 736x480. Next step is finding the stubs in the firmware.
Title: Re: Canon EOS R / RP
Post by: yourboylloyd on September 05, 2020, 07:21:45 PM
After I've done some little adjustments in the display source code of the portable dumper...

Can you create an image of the card? Or share the autoexec.bin file?

Nevermind. That won't do anything for me.
Title: Re: Canon EOS R / RP
Post by: coon on September 05, 2020, 08:49:26 PM
I could upload my autoexec.bin but the code it is based on is a bit behind. Better wait until a1ex merges it into the official build.
It doesen't do anything useful anyways beside displaying the error message more nicely on the RP :).
Title: Re: Canon EOS R / RP
Post by: coon on September 07, 2020, 01:01:51 AM
names_are_hard and I did some first research on the RP. With his help I am now able to run its firmware in QEMU partially.

I've added the RP into models_list.c file of qemu by just copying 200D definitions and renaming to EOSRP. I've also added a EOSRP rom folder and renamed gang100.bin -> ROM0.BIN, gang200.bin -> ROM1.BIN.
Then started emulation with:

Code: [Select]
./run_canon_fw.sh EOSRP,firmware="boot=0" -d romcpy
It runs but locks up early.

QEMU log:

Code: [Select]
00000000 - 1FFFFFFF: eos.ram
40000000 - 5FFFFFFF: eos.ram_uncached
DF000000 - DFFFFFFF: eos.ram_extra
E0000000 - E1FFFFFF: eos.rom0
E2000000 - E3FFFFFF: eos.rom0_mirror
E4000000 - E5FFFFFF: eos.rom0_mirror
E6000000 - E7FFFFFF: eos.rom0_mirror
E8000000 - E9FFFFFF: eos.rom0_mirror
EA000000 - EBFFFFFF: eos.rom0_mirror
EC000000 - EDFFFFFF: eos.rom0_mirror
EE000000 - EFFFFFFF: eos.rom0_mirror
F0000000 - F0FFFFFF: eos.rom1
F1000000 - F1FFFFFF: eos.rom1_mirror
F2000000 - F2FFFFFF: eos.rom1_mirror
F3000000 - F3FFFFFF: eos.rom1_mirror
F4000000 - F4FFFFFF: eos.rom1_mirror
F5000000 - F5FFFFFF: eos.rom1_mirror
F6000000 - F6FFFFFF: eos.rom1_mirror
F7000000 - F7FFFFFF: eos.rom1_mirror
F8000000 - F8FFFFFF: eos.rom1_mirror
F9000000 - F9FFFFFF: eos.rom1_mirror
FA000000 - FAFFFFFF: eos.rom1_mirror
FB000000 - FBFFFFFF: eos.rom1_mirror
FC000000 - FCFFFFFF: eos.rom1_mirror
FD000000 - FDFFFFFF: eos.rom1_mirror
FE000000 - FEFFFFFF: eos.rom1_mirror
FF000000 - FFFFFFFF: eos.rom1_mirror
BFE00000 - DEFFFFFF: eos.mmio
[EOS] enabling memory access logging (RW).
[EOS] loading './EOSRP/ROM0.BIN' to 0xE0000000-0xE1FFFFFF
[EOS] loading './EOSRP/ROM1.BIN' (expected size 0x01000000, got 0x02000000) to 0xF0000000-0xF0FFFFFF
[MPU] FIXME: using generic MPU spells for EOSRP.
[MPU] FIXME: no MPU button codes for EOSRP.
Start address: 0xE0000000
Setting BOOTDISK flag to FFFFFFFF
[CPU0] E0008450: MRC p15,0,Rd,cr0,cr0,5:      MPIDR -> 0x80000000
[CPU0] E0008460: MCR p15,0,Rd,cr12,cr0,0:       VBAR <- 0xE000001D
[CPU0] E000848C: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x8C50078
[CPU0] E0008482: MCR p15, ...          : CACHEMAINT x1 (omitted)
[CPU0] E000848C: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C50878
[CPU0] E0004B62: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C50878
[CPU0] E0004B62: MCR p15, ...          : CACHEMAINT x2 (omitted)
[CPU0] E0004B62: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C51878
[ROMCPY] 0xE0008634 -> 0xDF001000 size 0x600      at 0xE000699C
Logging ROM-copied blocks to EOSRP/romcpy.sh.
 
[CPU0] E00084D8: MRC p15,0,Rd,cr0,cr0,5:      MPIDR -> 0x80000000
[CPU0] E0004B86: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C51878
[CPU0] E0004C50: MCR p15, ...          : CACHEMAINT x512 (omitted)
[CPU0] E0004B86: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C50878
[CPU0] E0004B96: MCR p15, ...          : CACHEMAINT x1 (omitted)
[CPU0] E0004AE2: MCR p15,0,Rd,cr3,cr0,0:       DACR <- 0x55555555
[CPU0] E0004AEA: MCR p15,0,Rd,cr2,cr0,0:  TTBR0_EL1 <- 0xE0004800
[CPU0] E0004AEE: MCR p15,0,Rd,cr2,cr0,1:  TTBR1_EL1 <- 0xE0000080
[CPU0] E0004AF2: MCR p15,0,Rd,cr13,cr0,1: CONTEXTIDR(S) <- 0x0       
[CPU0] E0004AF6: MCR p15,0,Rd,cr2,cr0,2:      TTBCR <- 0x7       
[CPU0] E0004AFE: MCR p15,0,Rd,cr8,cr7,0:    TLBIALL <- 0x0       
[CPU0] E0004B06: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C50878
[CPU0] E0004B06: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C50879
[CPU0] E0008546: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C50879
[CPU0] E0008546: MCR p15, ...          : CACHEMAINT x1 (omitted)
[CPU0] E0008546: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C51879
[CPU0] E000855E: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C51879
[CPU0] E000855E: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C5187D
[CPU0] E000856A: MRC p15,0,Rd,cr1,cr0,1:  ACTLR_EL1 -> 0x45
[CPU0] E000856A: MCR p15,0,Rd,cr1,cr0,1:  ACTLR_EL1 <- 0x45     
[CPU0] E000856A: MRC p15,0,Rd,cr15,cr0,0:  A9_PWRCTL -> 0x0
[CPU0] E000856A: MCR p15,0,Rd,cr15,cr0,0:  A9_PWRCTL <- 0x1       
[CPU0] E000858A: MRC p15,0,Rd,cr15,cr0,1:    A9_DIAG -> 0x0
[CPU0] E000858A: MCR p15,0,Rd,cr15,cr0,1:    A9_DIAG <- 0x400000 
[CPU0] E0004900: MRC p15,0,Rd,cr0,cr0,5:      MPIDR -> 0x80000000
[CPU0] E00049A6: MCR p15,0,Rd,cr12,cr0,0:       VBAR <- 0xDF000000
[ROMCPY] 0xE0008C34 -> 0xDF000000 size 0x100      at 0xE0004966
BootL[ROMCPY] 0xE0008D50 -> 0x40100000 size 0x116D4    at 0xE0007F4C
[ROMCPY] 0xE0000000 -> 0x40700000 size 0x4900     at 0x10F46C 

romcpy.sh contains:

Code: [Select]
dd if=ROM0.BIN of=EOSRP.0xDF001000.bin bs=1 skip=$((0x8634)) count=$((0x600))
dd if=ROM0.BIN of=EOSRP.0xDF000000.bin bs=1 skip=$((0x8C34)) count=$((0x100))
dd if=ROM0.BIN of=EOSRP.0x40100000.bin bs=1 skip=$((0x8D50)) count=$((0x116D4))
dd if=ROM0.BIN of=EOSRP.0x40700000.bin bs=1 skip=$((0x0)) count=$((0x4900))

But it seems to be incomplete. Boot process seems to lock up here.
When running QEMU like this:

Code: [Select]
./run_canon_fw.sh EOSRP,firmware="boot=1"
I will get the following message in red color before it locks up:

Code: [Select]
BootLoadCard Read Error!!!
e
Title: Re: Canon EOS R / RP
Post by: coon on September 07, 2020, 08:45:48 PM
I've applied the M50 DIGIC8 QEMU draft patch by alex (https://www.magiclantern.fm/forum/index.php?topic=23296.msg210088#msg210088) and used the M50 instead of 200D as a template for the RP.
It immediately crashed on the first try with the following error:

Code: [Select]
qemu-system-arm: /home/nimble-test/ML/qemu-eos/qemu-2.5.0/hw/arm/../eos/eos.c:2568: eos_handle_card_led: Assertion `s->card_led' failed.

After changing the RPs LED Address in model_list.c from M50 to 200D it is now booting even further. It is now booting the second core of the CPU and locks up a little bit later then before:

Code: [Select]
00000000 - 3FFFFFFF: eos.ram
40000000 - 7FFFFFFF: eos.ram_uncached
DF000000 - DFFFFFFF: eos.ram_extra
E0000000 - E1FFFFFF: eos.rom0
E2000000 - E3FFFFFF: eos.rom0_mirror
E4000000 - E5FFFFFF: eos.rom0_mirror
E6000000 - E7FFFFFF: eos.rom0_mirror
E8000000 - E9FFFFFF: eos.rom0_mirror
EA000000 - EBFFFFFF: eos.rom0_mirror
EC000000 - EDFFFFFF: eos.rom0_mirror
EE000000 - EFFFFFFF: eos.rom0_mirror
F0000000 - F1FFFFFF: eos.rom1
F2000000 - F3FFFFFF: eos.rom1_mirror
F4000000 - F5FFFFFF: eos.rom1_mirror
F6000000 - F7FFFFFF: eos.rom1_mirror
F8000000 - F9FFFFFF: eos.rom1_mirror
FA000000 - FBFFFFFF: eos.rom1_mirror
FC000000 - FDFFFFFF: eos.rom1_mirror
FE000000 - FFFFFFFF: eos.rom1_mirror
BFE00000 - DEFFFFFF: eos.mmio
[EOS] enabling memory access logging (RW).
[EOS] loading './EOSRP/ROM0.BIN' to 0xE0000000-0xE1FFFFFF
[EOS] loading './EOSRP/ROM1.BIN' to 0xF0000000-0xF1FFFFFF
[MPU] FIXME: using generic MPU spells for EOSRP.
[MPU] FIXME: no MPU button codes for EOSRP.
Start address: 0xE0000000
Setting BOOTDISK flag to 0
[CPU0] E0008450: MRC p15,0,Rd,cr0,cr0,5:      MPIDR -> 0x80000000
[CPU0] E0008460: MCR p15,0,Rd,cr12,cr0,0:       VBAR <- 0xE000001D
[CPU0] E000848C: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x8C50078
[CPU0] E0008482: MCR p15, ...          : CACHEMAINT x1 (omitted)
[CPU0] E000848C: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C50878
[CPU0] E0004B62: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C50878
[CPU0] E0004B62: MCR p15, ...          : CACHEMAINT x2 (omitted)
[CPU0] E0004B62: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C51878
[ROMCPY] 0xE0008634 -> 0xDF001000 size 0x600      at 0xE000699C
Logging ROM-copied blocks to EOSRP/romcpy.sh.

[CPU0] E00084D8: MRC p15,0,Rd,cr0,cr0,5:      MPIDR -> 0x80000000
[CPU0] E0004B86: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C51878
[CPU0] E0004C50: MCR p15, ...          : CACHEMAINT x512 (omitted)
[CPU0] E0004B86: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C50878
[CPU0] E0004B96: MCR p15, ...          : CACHEMAINT x1 (omitted)
[CPU0] E0004AE2: MCR p15,0,Rd,cr3,cr0,0:       DACR <- 0x55555555
[CPU0] E0004AEA: MCR p15,0,Rd,cr2,cr0,0:  TTBR0_EL1 <- 0xE0004800
[CPU0] E0004AEE: MCR p15,0,Rd,cr2,cr0,1:  TTBR1_EL1 <- 0xE0000080
[CPU0] E0004AF2: MCR p15,0,Rd,cr13,cr0,1: CONTEXTIDR(S) <- 0x0       
[CPU0] E0004AF6: MCR p15,0,Rd,cr2,cr0,2:      TTBCR <- 0x7       
[CPU0] E0004AFE: MCR p15,0,Rd,cr8,cr7,0:    TLBIALL <- 0x0       
[CPU0] E0004B06: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C50878
[CPU0] E0004B06: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C50879
[CPU0] E0008546: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C50879
[CPU0] E0008546: MCR p15, ...          : CACHEMAINT x1 (omitted)
[CPU0] E0008546: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C51879
[CPU0] E000855E: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C51879
[CPU0] E000855E: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C5187D
[CPU0] E000856A: MRC p15,0,Rd,cr1,cr0,1:  ACTLR_EL1 -> 0x45
[CPU0] E000856A: MCR p15,0,Rd,cr1,cr0,1:  ACTLR_EL1 <- 0x45       
[CPU0] E000856A: MRC p15,0,Rd,cr15,cr0,0:  A9_PWRCTL -> 0x0
[CPU0] E000856A: MCR p15,0,Rd,cr15,cr0,0:  A9_PWRCTL <- 0x1       
[CPU0] E000858A: MRC p15,0,Rd,cr15,cr0,1:    A9_DIAG -> 0x0
[CPU0] E000858A: MCR p15,0,Rd,cr15,cr0,1:    A9_DIAG <- 0x400000   
[CPU0] E0004900: MRC p15,0,Rd,cr0,cr0,5:      MPIDR -> 0x80000000
[CPU0] E00049A6: MCR p15,0,Rd,cr12,cr0,0:       VBAR <- 0xDF000000
[ROMCPY] 0xE0008C34 -> 0xDF000000 size 0x100      at 0xE0004966
BootL[ROMCPY] 0xE0008D50 -> 0x40100000 size 0x116D4    at 0xE0007F4C
[ROMCPY] 0xE0000000 -> 0x40700000 size 0x4900     at 0x10F46C 
oade[CPU0] 001008F6: MCR p15, ...          : CACHEMAINT x584 (omitted)
[CPU0] E0040000: MCR p15,0,Rd,cr12,cr0,0:       VBAR <- 0xE073A000
[CPU0] E004000A: MRC p15,0,Rd,cr0,cr0,5:      MPIDR -> 0x80000000
Wake up CPU1
Wake up CPU1
[ROMCPY] 0xE12F43EC -> 0x4000     size 0x247CC    at 0xE004003C
[CPU1] E0008450: MRC p15,0,Rd,cr0,cr0,5:      MPIDR -> 0x80000001
[CPU1] E0008460: MCR p15,0,Rd,cr12,cr0,0:       VBAR <- 0xE000001D
[CPU1] E000848C: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x8C50078
[CPU1] E0008482: MCR p15, ...          : CACHEMAINT x1 (omitted)
[CPU1] E000848C: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C50878
[CPU1] E0004B62: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C50878
[CPU1] E0004B62: MCR p15, ...          : CACHEMAINT x2 (omitted)
[CPU1] E0004B62: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C51878
[CPU1] E0004B86: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C51878
[CPU1] E0004C40: MCR p15, ...          : CACHEMAINT x512 (omitted)
[CPU1] E0004B86: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C50878
[CPU1] E0004B96: MCR p15, ...          : CACHEMAINT x1 (omitted)
[CPU1] E0004AE2: MCR p15,0,Rd,cr3,cr0,0:       DACR <- 0x55555555
[CPU1] E0004AEA: MCR p15,0,Rd,cr2,cr0,0:  TTBR0_EL1 <- 0xE0004880
[CPU1] E0004AEE: MCR p15,0,Rd,cr2,cr0,1:  TTBR1_EL1 <- 0xE0000080
[CPU1] E0004AF2: MCR p15,0,Rd,cr13,cr0,1: CONTEXTIDR(S) <- 0x1       
[CPU1] E0004AF6: MCR p15,0,Rd,cr2,cr0,2:      TTBCR <- 0x7       
[CPU1] E0004AFE: MCR p15,0,Rd,cr8,cr7,0:    TLBIALL <- 0x0       
[CPU1] E0004B06: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C50878
[CPU1] E0004B06: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C50879
[CPU1] E0008546: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C50879
[CPU1] E0008546: MCR p15, ...          : CACHEMAINT x1 (omitted)
[CPU1] E0008546: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C51879
[CPU1] E000855E: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C51879
[CPU1] E000855E: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C5187D
[CPU1] E000856A: MRC p15,0,Rd,cr1,cr0,1:  ACTLR_EL1 -> 0x45
[CPU1] E000856A: MCR p15,0,Rd,cr1,cr0,1:  ACTLR_EL1 <- 0x45       
[CPU1] E000856A: MRC p15,0,Rd,cr15,cr0,0:  A9_PWRCTL -> 0x0
[CPU1] E000856A: MCR p15,0,Rd,cr15,cr0,0:  A9_PWRCTL <- 0x1       
[CPU1] E000858A: MRC p15,0,Rd,cr15,cr0,1:    A9_DIAG -> 0x0
[CPU1] E000858A: MCR p15,0,Rd,cr15,cr0,1:    A9_DIAG <- 0x400000   
[CPU1] E0004AA2: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C5187D
[CPU1] E0004AA2: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C5107D
[ROMCPY] 0xE1318BB8 -> 0x223B000  size 0xD1748    at 0xE0040050
[CPU0] E0040104: MRC p15,0,Rd,cr0,cr0,5:      MPIDR -> 0x80000000
[ROMCPY] 0xE13EA300 -> 0xDF002800 size 0xB94      at 0xE0040088
K433 READY
        4:4294966.271 [EEP] InstEEP: Rng_MDS(0x0 != 0x8000)
        5:4294966.271 [EEP] InstEEP: Srvc_MDS(0x0 != 0x100)
        8:4294966.271 [EEP] Rng_EEPH_RDS Invalid:0x0
        9:4294966.271 [EEP] Srvc_EEPH_RDS Invalid:0x0
       12:4294966.271 [STARTUP] K433 ICU Firmware Version 1.5.0 ( 3.8.7 )

romcpy does now generate a few more address:

Code: [Select]
dd if=ROM0.BIN of=EOSRP.0xDF001000.bin bs=1 skip=$((0x8634)) count=$((0x600))
dd if=ROM0.BIN of=EOSRP.0xDF000000.bin bs=1 skip=$((0x8C34)) count=$((0x100))
dd if=ROM0.BIN of=EOSRP.0x40100000.bin bs=1 skip=$((0x8D50)) count=$((0x116D4))
dd if=ROM0.BIN of=EOSRP.0x40700000.bin bs=1 skip=$((0x0)) count=$((0x4900))
dd if=ROM0.BIN of=EOSRP.0x4000.bin bs=1 skip=$((0x12F43EC)) count=$((0x247CC))
dd if=ROM0.BIN of=EOSRP.0x223B000.bin bs=1 skip=$((0x1318BB8)) count=$((0xD1748))
dd if=ROM0.BIN of=EOSRP.0xDF002800.bin bs=1 skip=$((0x13EA300)) count=$((0xB94))

This is my current EOSRP definition in models_list.c:

Code: [Select]
{
        .name                   = "EOSRP",
        .digic_version          = 8,
        .ram_size               = 0x40000000,   /* 1GB */
        .card_led_address       = 0xD208016C,   // 200D /* WLAN LED 0xD2080190 */
        .current_task_addr      = 0x28,         /* fixme: read from virtual memory */
        .uart_rx_interrupt      = 0x15D,
        .uart_tx_interrupt      = 0x16D,
        .rom0_size              = 0x02000000,   /* 32MB (main ROM) */
        .rom1_size              = 0x02000000,   /* 32MB (secondary ROM) */
        .dedicated_movie_mode   = 0, // camera has support for it. Set to 1 later.
    },
Title: Re: Canon EOS R / RP
Post by: coon on September 07, 2020, 10:39:27 PM
Not sure if it helps, but when executing qemu with firmware="boot=1" with a bootflag enabled sd card image with Magic Lantern on it, I get some SDIO errors and I can see that it is trying to execute AUTOEXEC.BIN before it locks up:

Code: [Select]
00000000 - 3FFFFFFF: eos.ram
40000000 - 7FFFFFFF: eos.ram_uncached
DF000000 - DFFFFFFF: eos.ram_extra
E0000000 - E1FFFFFF: eos.rom0
E2000000 - E3FFFFFF: eos.rom0_mirror
E4000000 - E5FFFFFF: eos.rom0_mirror
E6000000 - E7FFFFFF: eos.rom0_mirror
E8000000 - E9FFFFFF: eos.rom0_mirror
EA000000 - EBFFFFFF: eos.rom0_mirror
EC000000 - EDFFFFFF: eos.rom0_mirror
EE000000 - EFFFFFFF: eos.rom0_mirror
F0000000 - F1FFFFFF: eos.rom1
F2000000 - F3FFFFFF: eos.rom1_mirror
F4000000 - F5FFFFFF: eos.rom1_mirror
F6000000 - F7FFFFFF: eos.rom1_mirror
F8000000 - F9FFFFFF: eos.rom1_mirror
FA000000 - FBFFFFFF: eos.rom1_mirror
FC000000 - FDFFFFFF: eos.rom1_mirror
FE000000 - FFFFFFFF: eos.rom1_mirror
BFE00000 - DEFFFFFF: eos.mmio
[EOS] loading './EOSRP/ROM0.BIN' to 0xE0000000-0xE1FFFFFF
[EOS] loading './EOSRP/ROM1.BIN' to 0xF0000000-0xF1FFFFFF
[MPU] FIXME: using generic MPU spells for EOSRP.
[MPU] FIXME: no MPU button codes for EOSRP.
Start address: 0xE0000000
Setting BOOTDISK flag to FFFFFFFF
[CPU0] E0008450: MRC p15,0,Rd,cr0,cr0,5:      MPIDR -> 0x80000000
[CPU0] E0008460: MCR p15,0,Rd,cr12,cr0,0:       VBAR <- 0xE000001D
[CPU0] E000848C: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x8C50078
[CPU0] E0008482: MCR p15, ...          : CACHEMAINT x1 (omitted)
[CPU0] E000848C: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C50878
[CPU0] E0004B62: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C50878
[CPU0] E0004B62: MCR p15, ...          : CACHEMAINT x2 (omitted)
[CPU0] E0004B62: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C51878

[CPU0] E00084D8: MRC p15,0,Rd,cr0,cr0,5:      MPIDR -> 0x80000000
[CPU0] E0004B86: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C51878
[CPU0] E0004C50: MCR p15, ...          : CACHEMAINT x512 (omitted)
[CPU0] E0004B86: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C50878
[CPU0] E0004B96: MCR p15, ...          : CACHEMAINT x1 (omitted)
[CPU0] E0004AE2: MCR p15,0,Rd,cr3,cr0,0:       DACR <- 0x55555555
[CPU0] E0004AEA: MCR p15,0,Rd,cr2,cr0,0:  TTBR0_EL1 <- 0xE0004800
[CPU0] E0004AEE: MCR p15,0,Rd,cr2,cr0,1:  TTBR1_EL1 <- 0xE0000080
[CPU0] E0004AF2: MCR p15,0,Rd,cr13,cr0,1: CONTEXTIDR(S) <- 0x0       
[CPU0] E0004AF6: MCR p15,0,Rd,cr2,cr0,2:      TTBCR <- 0x7       
[CPU0] E0004AFE: MCR p15,0,Rd,cr8,cr7,0:    TLBIALL <- 0x0       
[CPU0] E0004B06: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C50878
[CPU0] E0004B06: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C50879
[CPU0] E0008546: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C50879
[CPU0] E0008546: MCR p15, ...          : CACHEMAINT x1 (omitted)
[CPU0] E0008546: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C51879
[CPU0] E000855E: MRC p15,0,Rd,cr1,cr0,0:      SCTLR -> 0x48C51879
[CPU0] E000855E: MCR p15,0,Rd,cr1,cr0,0:      SCTLR <- 0x48C5187D
[CPU0] E000856A: MRC p15,0,Rd,cr1,cr0,1:  ACTLR_EL1 -> 0x45
[CPU0] E000856A: MCR p15,0,Rd,cr1,cr0,1:  ACTLR_EL1 <- 0x45       
[CPU0] E000856A: MRC p15,0,Rd,cr15,cr0,0:  A9_PWRCTL -> 0x0
[CPU0] E000856A: MCR p15,0,Rd,cr15,cr0,0:  A9_PWRCTL <- 0x1       
[CPU0] E000858A: MRC p15,0,Rd,cr15,cr0,1:    A9_DIAG -> 0x0
[CPU0] E000858A: MCR p15,0,Rd,cr15,cr0,1:    A9_DIAG <- 0x400000   
[CPU0] E0004900: MRC p15,0,Rd,cr0,cr0,5:      MPIDR -> 0x80000000
[CPU0] E00049A6: MCR p15,0,Rd,cr12,cr0,0:       VBAR <- 0xDF000000
BootLoad[SDIO] Error
[SDIO] Error
Now jump to AUTOEXEC.BIN(0x00800000)!!

I think I am now at a point where I have to dive deeper into how the initialization process works and how to find out the proper device addresses / RAM size etc. to get even further on the boot process.
Title: Re: Canon EOS R / RP
Post by: aprofiti on September 08, 2020, 04:26:30 PM
I suggest you to start reading posts from Digic 7 (https://www.magiclantern.fm/forum/index.php?topic=19737.0) development thread, it has very useful information on how progress was made by other users to make digic6-dumper branch to work on D7 cameras and will help you to have an idea on what to do to start porting ML for EOS RP.

Starting from here (https://www.magiclantern.fm/forum/index.php?topic=19737.msg206736#msg206736) there are some of my previous posts of me understanding how to port code to 77D using only emulator as I don't have a real camera, also looks for posts from calle2010 who kept progressing the work.

After that you will like to print an Hello World on EOS RP and share a picture!

I think I am now at a point where I have to dive deeper into how the initialization process works and how to find out the proper device addresses / RAM size etc. to get even further on the boot process.
Does the emulation looks like it keep running or instead it hangs up?

You can also try to improve emulation for Digic X camera to have Canon GUI to render and navigate from QEMU, here you would certainly like some hints from a1ex to address you into the right direction :)
Title: Re: Canon EOS R / RP
Post by: coon on September 08, 2020, 08:01:41 PM
Will check the Digic 7 thread out, thanks for that advice!
Actually I am already able to print hello world on the physical RP since ML recovery already boots. It just doesen't run in the emulator yet.

QEMU doesn't segfault but seems to wait for something after it has passed the bootloader and gets stuck when executing the actual firmware:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FRNVysmJ%2Fqemu-ml.png&hash=a069b20fa49d4f4b4c2d9dd1b44a2fae) (https://i.ibb.co/RNVysmJ/qemu-ml.png)

Maybe I should do a dump of both UART interfaces of the physical RP to have an idea what should happen next. But for that I need a 0.4mm 8pin FPC cable first. It is like impossible getting such... At least in an affordable way. :/.
Title: Re: Canon EOS R / RP
Post by: coon on September 09, 2020, 09:30:31 PM
Just found out that AUTOEXEC.BIN is actually executed and Magic Lantern Rescue code does already run on RP firmware within QEMU.
Emulated display does work, which meight help in finding stubs. :)

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2Fgj9dn4G%2Frp-qemu.png&hash=153337dc06a7efb495c74f7f8ca23159) (https://i.ibb.co/gj9dn4G/rp-qemu.png)

A first milestone I want to achieve is getting the portable dumper running. Even if technically not necessary due to the possibility of dumping via canon basic it will give me some practice in finding stubs hopefully.
After that I'll try getting the cpuinfo code running, do a dump of it on the real hardware and post its output here.
Title: Re: Canon EOS R / RP
Post by: srsa on September 09, 2020, 10:26:16 PM
After that I'll try getting the cpuinfo code running, do a dump of it on the real hardware and post its output here.
If you do that, please use the updated code from CHDK svn. The old Cortex R4 specific code is not very useful on Cortex A9.
Title: Re: Canon EOS R / RP
Post by: nikfreak on September 09, 2020, 10:30:02 PM
some auto-method to find / extract stubs would be handy now
Title: Re: Canon EOS R / RP
Post by: coon on September 09, 2020, 11:05:22 PM
If you do that, please use the updated code from CHDK svn. The old Cortex R4 specific code is not very useful on Cortex A9.

Good to know, I will do that, thx!

some auto-method to find / extract stubs would be handy now

Back in the days when I have written some Gametrainers I have used a simple pattern matching algorithm for an almost game version independent way to apply a code injection to a specific code location. Maybe I can modify and use that for ML as an automated way to find stubs. However, the found stubs should always be reviewed by a developer before running them on real HW since pattern matching meight not always work 100% correct.
Title: Re: Canon EOS R / RP
Post by: names_are_hard on September 09, 2020, 11:19:33 PM
For automating stub hunting...  Ghidra has a Python scripting engine (well, Jython.  Or native Java).  That gives you access not just to the disassembly, but the decompiled forms.  I believe you can also access Ghidra's IL, Pcode.  So you can in theory do some pretty cool searches and comparisons.  You can do this from the CLI, you can spin up Ghidra without needing to start the frontend.
Title: Re: Canon EOS R / RP
Post by: coon on September 14, 2020, 07:55:28 PM
Got CPU info of RP dumped via Canon Basic Dumper script (https://www.magiclantern.fm/forum/index.php?topic=25305.msg230668#msg230668) and parsed via x86 port of CHDK cpuinfo tool (https://www.magiclantern.fm/forum/index.php?topic=25305.msg230850#msg230850):

Code: [Select]
ID         0x414FC091
  Revision             0x1 1
  Part                 0xC09 3081
  ARM Arch             0xF 15
  Variant              0x4 4
  Implementor          0x41 65
Cache type 0x83338003
  Icache min words/line 0x3 3 [8]
  (zero)               0x0 0
  L1 Icache policy     0x2 2
  Dcache min words/line 0x3 3 [8]
  Exclusives Reservation Granule 0x3 3 [8]
  Cache Writeback Granule 0x3 3 [8]
  (zero)               0x0 0
  (register format)    0x4 4
TCM type   0x00000000
  (raw value)          0x0 0
TLB type   0x00000404
  TLB                  0x0 0 [Unified TLB]
  TLB entries          0x2 2 [256]
  -                    0x0 0
  Lockable unified or data entries 0x4 4
  Lockable instruction entries 0x0 0
  (zero)               0x0 0
TTBCR      0x00000007
  N                    0x7 7 [TTBR0 table size 128 bytes]
  (zero)               0x0 0
  TTBR0 walks disabled 0x0 0
  TTBR1 walks disabled 0x0 0
  (zero)               0x0 0
  Long descriptors     0x0 0
TTBR0      0xE0004800
  IRGN[1]              0x0 0
  Shareable            0x0 0
  (impl. defined)      0x0 0
  RGN (Outer cacheability) 0x0 0
  NOS (Inner shareable) 0x0 0
  IRGN[0]              0x0 0
  Table address        0x1C00090 29360272 [0xe0004800]
TTBR1      0xE0000000
  IRGN[1]              0x0 0
  Shareable            0x0 0
  (impl. defined)      0x0 0
  RGN (Outer cacheability) 0x0 0
  NOS (Inner shareable) 0x0 0
  IRGN[0]              0x0 0
  Table address        0x1C00000 29360128 [0xe0000000]
Multiprocessor ID 0x80000000
  (raw value)          0x80000000 -2147483648
Revision ID 0x00000000
  (raw value)          0x0 0
Processor feature 0 0x00001231
  ARM inst set         0x1 1
  Thumb inst set       0x3 3
  Jazelle inst set     0x2 2
  ThumbEE inst set     0x1 1
  -                    0x0 0
Processor feature 1 0x00000011
  Programmers' model   0x1 1
  Security extensions  0x1 1
  Microcontr. prog model 0x0 0
  Virt. extensions     0x0 0
  Generic timer ext.   0x0 0
  -                    0x0 0
Debug feature 0x00010444
  Coproc. dbg model    0x4 4
  Coproc. secure dbg model 0x4 4
  Memory-mapped dbg model 0x4 4
  Coproc. trace model  0x0 0
  Memory-mapped trace model 0x1 1
  Debug model M        0x0 0
  Perf. monitors       0x0 0
  -                    0x0 0
Aux feature 0x00000000
  (raw value)          0x0 0
Mem model feature 0 0x00100103
  VMSA support         0x3 3
  PMSA support         0x0 0
  Cache coherence      0x1 1
  Outer shareable      0x0 0
  TCM support          0x0 0
  Auxiliary registers  0x1 1
  FCSE support         0x0 0
  -                    0x0 0
Mem model feature 1 0x20000000
  L1 Harvard cache VA  0x0 0
  L1 unified cache VA  0x0 0
  L1 Harvard cache s/w 0x0 0
  L1 unified cache s/w 0x0 0
  L1 Harvard cache     0x0 0
  L1 unified cache     0x0 0
  L1 cache test & clean 0x0 0
  Branch predictor     0x2 2
Mem model feature 2 0x01230000
  L1 Harvard fg prefetch 0x0 0
  L1 Harvard bg prefetch 0x0 0
  L1 Harvard range     0x0 0
  Harvard TLB          0x0 0
  Unified TLB          0x3 3
  Mem barrier          0x2 2
  WFI stall            0x1 1
  HW access flag       0x0 0
Mem model feature 3 0x00102111
  Cache maintain MVA   0x1 1 [Supported]
  Cache maintain set/way 0x1 1 [Supported]
  Branch predictor maintenance 0x1 1 [Invalidate all]
  Maintenance broadcast 0x2 2
  -                    0x0 0
  Transl. table coherent walk 0x1 1
  Cached memory size   0x0 0 [4 GByte]
  Supersection support 0x0 0 [Supported]
ISA feature 0 0x00101111
  Swap instrs          0x1 1
  Bitcount instrs      0x1 1
  Bitfield instrs      0x1 1
  CmpBranch instrs     0x1 1
  Coproc instrs        0x0 0
  Debug instrs         0x1 1
  Divide instrs        0x0 0
  -                    0x0 0
ISA feature 1 0x13112111
  Endian instrs        0x1 1
  Exception instrs     0x1 1
  Exception AR instrs  0x1 1
  Extend instrs        0x2 2
  IfThen instrs        0x1 1
  Immediate instrs     0x1 1
  Interwork instrs     0x3 3
  Jazelle instrs       0x1 1
ISA feature 2 0x21232041
  LoadStore instrs     0x1 1
  Memhint instrs       0x4 4
  MultiAccess Interruptible instructions 0x0 0
  Mult instrs          0x2 2
  MultS instrs         0x3 3
  MultU instrs         0x2 2
  PSR AR instrs        0x1 1
  Reversal instrs      0x2 2
ISA feature 3 0x11112131
  Saturate instrs      0x1 1
  SIMD instrs          0x3 3
  SVC instrs           0x1 1
  SynchPrim instrs     0x2 2
  TabBranch instrs     0x1 1
  ThumbCopy instrs     0x1 1
  TrueNOP instrs       0x1 1
  T2 Exec Env instrs   0x1 1
ISA feature 4 0x00011142
  Unprivileged instrs  0x2 2
  WithShifts instrs    0x4 4
  Writeback instrs     0x1 1
  SMC instrs           0x1 1
  Barrier instrs       0x1 1
  SynchPrim_instrs_frac 0x0 0
  PSR_M instrs         0x0 0
  -                    0x0 0
ISA feature 5 0x00000000
  -                    0x0 0
Cache level ID 0x09200003
  Cache type, level1   0x3 3 [Separate Icache, Dcache]
  Cache type, level2   0x0 0 [no cache]
  Cache type, level3   0x0 0 [no cache]
  Cache type, level4   0x0 0 [no cache]
  Cache type, level5   0x0 0 [no cache]
  Cache type, level6   0x0 0 [no cache]
  Cache type, level7   0x0 0 [no cache]
  Level of unification Inner Shareable 0x1 1
  Level of coherency   0x1 1
  Level of unification 0x1 1
  (zero)               0x0 0
Cache size ID reg (data, level0) 0x700FE019
  Line size in words   0x1 1 [8]
  Associativity        0x3 3 [4]
  Number of sets       0x7F 127 [128]
  Write allocation     0x1 1
  Read allocation      0x1 1
  Write back           0x1 1
  Write through        0x0 0
Cache size ID reg (inst, level0) 0x200FE019
  Line size in words   0x1 1 [8]
  Associativity        0x3 3 [4]
  Number of sets       0x7F 127 [128]
  Write allocation     0x0 0
  Read allocation      0x1 1
  Write back           0x0 0
  Write through        0x0 0
SCTLR      0x40C5187D
  MMU Enable           0x1 1
  Strict Align         0x0 0
  Data or Unified Cache Enable 0x1 1
  CP15 Barrier Enable  0x1 1
  - (SBO)              0x7 7
  - (SBZ)              0x0 0
  SWP/SWPB Enable      0x0 0
  Branch Pred Enable   0x1 1
  ICache Enable        0x1 1
  High Vector          0x0 0
  Round Robin          0x0 0
  - (SBZ)              0x0 0
  - (SBO)              0x1 1
  HA flag              0x0 0
  - (SBO)              0x1 1
  WXN (virt. ext. only) 0x0 0
  UWXN (virt. ext. only) 0x0 0
  FIQ Enable           0x0 0
  - (SBO)              0x3 3
  VE                   0x0 0
  CPSR E               0x0 0
  - (SBZ)              0x0 0
  NMFI                 0x0 0
  TRE                  0x0 0
  AFE                  0x0 0
  Thumb exceptions     0x1 1
  - (SBZ)              0x0 0
ACTLR      0x00000045
  Cache & TLB maint. broadcast 0x1 1
  L2 prefetch enable   0x0 0
  L1 prefetch enable   0x1 1
  Write full line of zeroes 0x0 0
  (zero)               0x0 0
  SMP                  0x1 1
  Exclusive cache      0x0 0
  Alloc in one way     0x0 0
  Parity on            0x0 0
  -                    0x0 0
ACTLR2     0x00000701
  (raw value)          0x701 1793
CPACR      0xC0000000
  (zero)               0x0 0
  CP10 access permission 0x0 0
  CP11 access permission 0x0 0
  (zero)               0x0 0
  D32DIS               0x1 1
  ASEDIS               0x1 1
DACR       0x0000C000
  (raw value)          0xC000 49152
NSACR (sec. ext. only) 0x55555555
  (raw value)          0x55555555 1431655765
DBGDIDR    0x35137041
  Revision             0x1 1
  Variant              0x4 4
  - (RAZ)              0x70 112
  Version              0x3 3 [v7 full]
  Context              0x1 1 [2]
  BRP                  0x5 5 [6]
  WRP                  0x3 3 [4]
DBGDRAR    0x00000000
  Valid                0x0 0
  - (UNK)              0x0 0
  Address              0x0 0 [0x00000000]
DBGDSAR    0x00030000
  Valid                0x0 0
  - (UNK)              0x0 0
  Address              0x30 48 [0x00030000]
DBGDSCR    0x03000002
  HALTED               0x0 0
  RESTARTED            0x1 1
  MOE                  0x0 0
  SDABORT_l            0x0 0
  ADABORT_l            0x0 0
  UND_l                0x0 0
  FS                   0x0 0
  DBGack               0x0 0
  INTdis               0x0 0
  UDCCdis              0x0 0
  ITRen                0x0 0
  HDBGen               0x0 0
  MDBGen               0x0 0
  SPIDdis              0x0 0
  SPNIDdis             0x0 0
  NS                   0x0 0
  ADAdiscard           0x0 0
  ExtDCCmode           0x0 0
  - (SBZ)              0x0 0
  InstrCompl_l         0x1 1
  PipeAdv              0x1 1
  TXfull_l             0x0 0
  RXfull_l             0x0 0
  - (SBZ)              0x0 0
  TXfull               0x0 0
  RXfull               0x0 0
  - (SBZ)              0x0 0
Config base addr reg 0xC1000000
  (raw value)          0xC1000000 -1056964608
PLEIDR     0x00000000
  (raw value)          0x0 0
TLB lockdown reg 0x00000000
  (raw value)          0x0 0
PRRR       0x00098AA4
  (raw value)          0x98AA4 625316
NMRR       0x44E048E0
  (raw value)          0x44E048E0 1155549408

Title: Re: Canon EOS R / RP
Post by: Corallaro on September 16, 2020, 01:13:12 PM
Great work!! Wonderful!!
I also have an EOS RP and I am available to test.
I've been using ML on EOS M for a while
Thank you
Giovanni
Title: Re: Canon EOS R / RP
Post by: coon on September 18, 2020, 11:07:39 AM
Like already mentioned here: https://www.magiclantern.fm/forum/index.php?topic=25305.msg231013#msg231013

I've ran this Canon Basic script on my RP:

Code: [Select]
private sub Initialize()
    System.Create()
    CamInfo_Debug(1)
end sub

Which has generated a CAM_INFO.XML file with the following content:

Code: [Select]
<?xml version="1.0"?>
<Canon>
    <CameraInfo>
        <Serial>xxxxxxxxxxxx</Serial>
        <FirmwareVer>
            <Internal>0.3.8.7</Internal>
            <Major>1.5.0</Major>
        </FirmwareVer>
        <ErrorList></ErrorList>
        <TotalShoot>1780</TotalShoot>
        <TotalShutter>1086948659</TotalShutter>
        <PowerOnCount>229</PowerOnCount>
        <TotalRunningTime>148394</TotalRunningTime>
    </CameraInfo>
</Canon>

TotalShutter value seems to be invalid here. Could someone else with an RP run that script too and post the results here?
Title: Re: Canon EOS R / RP
Post by: kitor on September 18, 2020, 12:43:50 PM
Unless it counts every movie frame as one shot  8)
Suspicious is that looks like just signed 32 bit integer.
Using only half MSB gives 8393 base 10, which is more realistic, but still huge compared to total shots.
I'll try later on R.
Title: Re: Canon EOS R / RP
Post by: Corallaro on September 18, 2020, 01:49:01 PM
Hi
if you tell me step by step instruction how to execute script with my EOS RP, i can make the test.
Ciao
Giovanni
Title: Re: Canon EOS R / RP
Post by: kitor on September 18, 2020, 01:53:40 PM
Code: [Select]
<?xml version="1.0" encoding="UTF-8"?>
<Canon>
   <CameraInfo>
      <Serial>xxxxxxx</Serial>
      <FirmwareVer>
         <Internal>0.7.3.5</Internal>
         <Major>1.7.0</Major>
      </FirmwareVer>
      <ErrorList>
         <Kind>
            <ID>E01</ID>
            <Count>4</Count>
            <ErrorLog>
               <BatTemperature>max:0 min:0</BatTemperature>
               <FirstOccurTime>2019.07.26 19:26:06</FirstOccurTime>
               <LastOccurTime>2019.07.27 08:52:14</LastOccurTime>
               <Log>
                  <DateTime>2019.07.27 08:52:14</DateTime>
                  <Reason>DS-EID:061</Reason>
                  <BatTemperature>0</BatTemperature>
                  <LensID>000000a0</LensID>
                  <ReleaseCount>2228</ReleaseCount>
               </Log>
               <Log>
                  <DateTime>2019.07.27 08:51:47</DateTime>
                  <Reason>DS-EID:061</Reason>
                  <BatTemperature>0</BatTemperature>
                  <LensID>000000a0</LensID>
                  <ReleaseCount>2224</ReleaseCount>
               </Log>
               <Log>
                  <DateTime>2019.07.26 19:26:19</DateTime>
                  <Reason>DS-EID:064</Reason>
                  <BatTemperature>0</BatTemperature>
                  <LensID>000000a0</LensID>
                  <ReleaseCount>2204</ReleaseCount>
               </Log>
               <Log>
                  <DateTime>2019.07.26 19:26:06</DateTime>
                  <Reason>DS-EID:063</Reason>
                  <BatTemperature>0</BatTemperature>
                  <LensID>000000a0</LensID>
                  <ReleaseCount>2204</ReleaseCount>
               </Log>
            </ErrorLog>
         </Kind>
         <Kind>
            <ID>E70</ID>
            <Count>1</Count>
            <ErrorLog>
               <BatTemperature>max:0 min:0</BatTemperature>
               <FirstOccurTime>2020.09.02 15:03:04</FirstOccurTime>
               <LastOccurTime>2020.09.02 15:03:04</LastOccurTime>
               <Log>
                  <DateTime>2020.09.02 15:03:04</DateTime>
                  <Reason>DS-EID:101</Reason>
                  <BatTemperature>0</BatTemperature>
                  <LensID>0102eefe</LensID>
                  <ReleaseCount>3018</ReleaseCount>
               </Log>
            </ErrorLog>
         </Kind>
      </ErrorList>
      <TotalShoot>3019</TotalShoot>
      <TotalShutter>2845</TotalShutter>
      <PowerOnCount>890</PowerOnCount>
      <TotalRunningTime>115710</TotalRunningTime>
   </CameraInfo>
</Canon>

There are some interesting logs here :D

Hi
if you tell me step by step instruction how to execute script with my EOS RP, i can make the test.
Ciao
Giovanni

Look at linked topic. There's everything explained in first post.
Title: Re: Canon EOS R / RP
Post by: c_joerg on September 18, 2020, 01:53:47 PM
https://www.magiclantern.fm/forum/index.php?topic=25305.0

TotalShutter value seems to be invalid here. Could someone else with an RP run that script too and post the results here?
Have you tried to make one shoot and  a second dump?     
Title: Re: Canon EOS R / RP
Post by: c_joerg on September 18, 2020, 01:57:19 PM
There are some interesting logs here :D
Du you use original Batterie?
BatTemperature is always 0.
Title: Re: Canon EOS R / RP
Post by: kitor on September 18, 2020, 02:00:11 PM
Yes and no. I have two 100% original LP-E6N, and two LP-E6 that looks original but were bought in China a few years ago. Still holds charge properly and I never had problems with those in 5D2, 5D3 and now in R.

But IIRC I fixed some old non-Canon battery that had cold solder joints inside, this may be it. I can't put it exactly in time, but this was for sure not when I played with ML.
ERR70 was a result of my broken Basic script.
Title: Re: Canon EOS R / RP
Post by: c_joerg on September 18, 2020, 02:04:34 PM
ERR70 was a result of my broken Basic script.
Then try it again with original LP-E6N, ;)
Title: Re: Canon EOS R / RP
Post by: kitor on September 18, 2020, 02:11:53 PM
No, it was an actual error in script code. I made a rom dump just before that (and on those LP-E6's as N were discharged so bad I had to charge them externally), and started experimenting with calling some functions :)
Title: Re: Canon EOS R / RP
Post by: coon on September 18, 2020, 03:11:30 PM
https://www.magiclantern.fm/forum/index.php?topic=25305.0
Have you tried to make one shoot and  a second dump?     

I'll give it a shot (pun intended).
Title: Re: Canon EOS R / RP
Post by: coon on September 18, 2020, 03:18:33 PM
Code: [Select]
<?xml version="1.0"?>
<Canon>
    <CameraInfo>
        <Serial>xxxxxxxxxxxx</Serial>
        <FirmwareVer>
            <Internal>0.3.8.7</Internal>
            <Major>1.5.0</Major>
        </FirmwareVer>
        <ErrorList></ErrorList>
        <TotalShoot>1781</TotalShoot>
        <TotalShutter>1086948660</TotalShutter>
        <PowerOnCount>232</PowerOnCount>
        <TotalRunningTime>148548</TotalRunningTime>
    </CameraInfo>
</Canon>

Counter increased by one but is still invalid.
It should be below 1781 since I have done some bracketing shots which are taken by electronic shutter.
Title: Re: Canon EOS R / RP
Post by: c_joerg on September 18, 2020, 03:37:30 PM
Counter increased by one but is still invalid.
Intresting...
Maybe the memory is brocken.
Would be intresting to see a dump from an other RP.
Title: Re: Canon EOS R / RP
Post by: coon on September 18, 2020, 03:40:18 PM
Unless it counts every movie frame as one shot  8)
...

I have recorded a video for a few seconds, just to be sure. ShutterCount stays the same here.
Title: Re: Canon EOS R / RP
Post by: Corallaro on September 18, 2020, 06:59:22 PM
Hi
this is the CAM_INFO.XML of my RP

Code: [Select]
<?xml version="1.0"?><Canon>
<CameraInfo>
<Serial>xxxxxxxxxxxx</Serial>
<FirmwareVer>
<Internal>0.3.8.7</Internal>
<Major>1.5.0</Major>
</FirmwareVer>
<ErrorList><Kind><ID>E60</ID><Count>1</Count><ErrorLog><BatTemperature>max:0 min:0</BatTemperature><FirstOccurTime>2020.02.02 17:40:00</FirstOccurTime><LastOccurTime>2020.02.02 17:40:00</LastOccurTime><Log><DateTime>2020.02.02 17:40:00</DateTime><Reason>DS-EID:067</Reason><BatTemperature>0</BatTemperature><LensID>010aeefe</LensID><ReleaseCount>7759</ReleaseCount></Log></ErrorLog></Kind></ErrorList>
<TotalShoot>12292</TotalShoot>
<TotalShutter>1086959388</TotalShutter>
<PowerOnCount>1127</PowerOnCount>
<TotalRunningTime>441761</TotalRunningTime>
</CameraInfo>
</Canon>
Title: Re: Canon EOS R / RP
Post by: coon on September 18, 2020, 07:21:02 PM
Interesting. Shutter count also broken here or has some encoding scheme.
Thanks for providing this!

Could you edit your post and wrap the XML output into code blocks like this?

[code]
<xml code here>
[/code]

It's easier to read like this.

It meight be interesting getting a dump of a fresh RP with 0 shots taken to find out the origin value. But it will be very hard to find such I guess...
Title: Re: Canon EOS R / RP
Post by: c_joerg on September 18, 2020, 07:41:48 PM
Interesting. Shutter count also broken here or has some encoding scheme.
Looks like this...
But only on RP.


It meight be interesting getting a dump of a fresh RP with 0 shots taken to find out the origin value.
Yes, would be intresting...
All my M's and 6D had 0 on the biginning.
Title: Re: Canon EOS R / RP
Post by: coon on September 19, 2020, 07:57:31 PM
Executed the following Canon Basic script from srsa on EOS RP (https://www.magiclantern.fm/forum/index.php?topic=25305.msg231075#msg231075):

Code: [Select]
private sub Initialize()
  ExecuteEventProcedure("smemShowFix")
  dumpf()
end sub

Got the following memory map:

Code: [Select]
[RSC] --- Common Lower ----
[RSC] LIME_HEAP                0x00000000 0x00000000         0 [Cacheable!
[RSC] MOVIE_CFILTER_SEED       0x00000000 0x00000000         0 [Cacheable!
[RSC] OMAR COM                 0x00000000 0x00000000         0 [Cacheable!
[RSC] ENGINE_MIRROR            0x00000000 0x00000000         0 [Cacheable!
[RSC] SITTERVCODEC WORK        0x4048C000 0x00207000   2125824
[RSC] DCFNO                    0x40693000 0x00004000     16384
[RSC] FILE HEADER              0x40698400 0x00100000   1048576
[RSC] DAF_WORK                 0x40798400 0x00051000    331776
[RSC] FACTORY/TVAFDEBUG        0x41585000 0x00080000    524288
[RSC] VSHADING_COMP_WORK       0x41682000 0x0002CC00    183296
[RSC] DARKCUR_COMP_WORK        0x416AEC00 0x00025400    152576
[RSC] LIME                     0x41800000 0x00500000   5242880
[RSC] NETWORK_HEAP             0x41D00000 0x00300000   3145728
[RSC] ZICO                     0x42000000 0x00180000   1572864
[RSC] APROC                    0x42180000 0x00021000    135168
[RSC] ARIMA                    0x421A1000 0x0006C000    442368
[RSC] SHIRAHAMA                0x4220D000 0x0002E000    188416
[RSC] RENDERING WORK           0x4233B000 0x00D00000  13631488
[RSC] JOB OBJECT               0x430D1000 0x00320000   3276800
[RSC] FIX                      0x43D18400 0x00200000   2097152
[RSC] TUNE                     0x43F18400 0x00200000   2097152
[RSC] TUNE2                    0x44118400 0x00600000   6291456
[RSC] FANCING_WORK             0x44718400 0x001C2000   1843200
[RSC] CAPTURE_WORK             0x449DA400 0x056E0000  91095040
[RSC] DAF_RAW                  0x7F4BB000 0x0083B800   8632320
[RSC] DANCING                  0x7FCF6800 0x00309800   3184640

[RSC] --- Normal ----
[RSC] LV_SERVO_WORK            0x00000000 0x00000000         0 [Cacheable!
[RSC] LV_AE_WORK               0x41605000 0x0007D000    512000
[RSC] EXMEM3_AREA              0x4A0BA400 0x04455C00  71654400
[RSC] TWAIN_AREA_L             0x5B710000 0x00300000   3145728
[RSC] YUV 2nd_L                0x5BA10000 0x04520000  72482816
[RSC] SS_U                     0x60000000 0x077B0000 125501440
[RSC] YUV 1st_U                0x677B0000 0x03D40000  64225280
[RSC] YUV 2nd_U                0x6B4F0000 0x04520000  72482816
[RSC] SUSANYUV                 0x6FA10000 0x048C0000  76283904
[RSC] YUV Thumb                0x742D0000 0x02B93000  45690880
[RSC] DECMEM1_AREA_U           0x76E63000 0x03480000  55050240
[RSC] EXMEM3_AREA_2            0x7A2E3000 0x051D8000  85819392
[RSC] TWAIN_AREA_U             0x80000000 0x00300000   3145728
[RSC] CAPMEM1_AREA_U           0x80300000 0x03480000  55050240
[RSC] ALGS_AREA_1U             0x83780000 0x03480000  55050240
[RSC] ALGS_AREA_2U             0x86C00000 0x03480000  55050240
[RSC] EXALGS_AREA_U            0x9A700000 0x032A0000  53084160
[RSC] SS_L                     0xA0000000 0x077B0000 125501440
[RSC] YUV 1st_L                0xA77B0000 0x03D40000  64225280
[RSC] CAPMEM1_AREA_L           0xAB4F0000 0x03480000  55050240
[RSC] DECMEM1_AREA_L           0xAE970000 0x03480000  55050240
[RSC] EXALGS_AREA_L            0xB5270000 0x032A0000  53084160
[RSC] ALGS_AREA_2L             0xB8510000 0x03480000  55050240
[RSC] ALGS_AREA_1L             0xBB990000 0x03480000  55050240

[RSC] --- Movie ----
[RSC] CINEMA_FILTER_WORK       0x00000000 0x00000000         0 [Cacheable!
[RSC] MOVIE_RECYUV             0x00000000 0x00000000         0 [Cacheable!
[RSC] AUDIO WORK               0x435C0400 0x00258000   2457600
[RSC] MOVIE_STREAM             0x4E510000 0x0FC00000 264241152
[RSC] LV_WORK_L                0x5E150000 0x01EB0000  32178176
[RSC] LV_WORK_U                0x60000000 0x04F00000  82837504
[RSC] MOVIE_RECWORK_U          0x64F00000 0x01A00000  27262976
[RSC] MOVIE_RECWORK_L          0xAB4F0000 0x0FC40000 264503296

[RSC] --- Play ----
[RSC] SLIDE_SHOW_WORK          0x5DEDA800 0x01FA4000  33177600
[RSC] IMGPLAY_WORK             0x60000000 0x05400000  88080384
[RSC] MOVIE_PLAYWORK           0xA0000000 0x176D0000 393019392

[RSC] --- Multishot ----
[RSC] HDR/GIS_MOVIE_RECWORK    0x00000000 0x00000000         0 [Cacheable!
[RSC] HDR/GIS_MOVIE_RECYUV     0x00000000 0x00000000         0 [Cacheable!
[RSC] HDR/GIS_KAITO_YUV        0x00000000 0x00000000         0 [Cacheable!
[RSC] HDR/GIS_LV_SERVO_WORK    0x00000000 0x00000000         0 [Cacheable!
[RSC] HDR/GIS_FLEXIBLE_MEM3_1  0x00000000 0x00000000         0 [Cacheable!
[RSC] HDR/GIS_FLEXIBLE_MEM3_2  0x00000000 0x00000000         0 [Cacheable!
[RSC] HDR/GIS_AUDIO WORK       0x435C0400 0x00258000   2457600
[RSC] HDR/GIS_EXMEM3_AREA      0x4A0BA400 0x04455C00  71654400
[RSC] HDR/GIS_MOVIE_STREAM     0x4E510000 0x0FC00000 264241152
[RSC] HDR/GIS_COMP_WORK        0x505F0000 0x28A00000 681574400
[RSC] HDR/GIS_YUV 2nd-1        0x5BAE0000 0x04520000  72482816
[RSC] HDR/GIS_SLIDE_SHOW_WORK  0x5DEDA800 0x01FA4000  33177600
[RSC] HDR/GIS_LV_WORK_L        0x5E150000 0x01EB0000  32178176
[RSC] HDR/GIS_LV_WORK_U        0x60000000 0x04F00000  82837504
[RSC] HDR/GIS_SS-2             0x60000000 0x077B0000 125501440
[RSC] HDR/GIS_IMGPLAY_WORK     0x60000000 0x05400000  88080384
[RSC] HDR/GIS_YUV 1st-2        0x677B0000 0x03D40000  64225280
[RSC] HDR/GIS_YUV 2nd-2        0x6B4F0000 0x04520000  72482816
[RSC] HDR/GIS_SUSAN_YUV        0x6FA10000 0x048C0000  76283904
[RSC] HDR/GIS_YUV Thumb        0x742D0000 0x02B93000  45690880
[RSC] HDR/GIS_EXMEM3_2         0x7A2E3000 0x051D8000  85819392
[RSC] HDR/GIS_WORK4            0x80300000 0x03480000  55050240
[RSC] HDR/GIS_WORK2            0x80300000 0x03480000  55050240
[RSC] HDR/GIS_MOVIE_PLAYWORK   0xA0000000 0x176D0000 393019392
[RSC] HDR/GIS_SS-1             0xA0000000 0x077B0000 125501440
[RSC] HDR/GIS_YUV 1st-1        0xA77B0000 0x03D40000  64225280
[RSC] HDR/GIS_WORK3            0xAB4F0000 0x03480000  55050240
[RSC] HDR/GIS_WORK1            0xAB4F0000 0x03480000  55050240

[RSC] --- Indev ----
[RSC] INDEV_SS-1               0x00000000 0x00000000         0 [Cacheable!
[RSC] INDEV_YUV 1st-1          0x00000000 0x00000000         0 [Cacheable!
[RSC] INDEV_YUV 2nd-1          0x00000000 0x00000000         0 [Cacheable!
[RSC] INDEV_BASIC              0x00000000 0x00000000         0 [Cacheable!
[RSC] INDEV_SS-2               0x00000000 0x00000000         0 [Cacheable!
[RSC] INDEV_YUV 1st-2          0x00000000 0x00000000         0 [Cacheable!
[RSC] INDEV_YUV 2nd-2          0x00000000 0x00000000         0 [Cacheable!
[RSC] INDEV_YUV Thumb          0x00000000 0x00000000         0 [Cacheable!
[RSC] INDEV_SUSAN_YUV          0x00000000 0x00000000         0 [Cacheable!
[RSC] INDEV_KAITO_YUV          0x00000000 0x00000000         0 [Cacheable!
[RSC] INDEV_MOVIE_REC_YUV      0x00000000 0x00000000         0 [Cacheable!
[RSC] INDEV_EXMEM3_AREA        0x4A0BA400 0x04455C00  71654400
[RSC] INDEV_YUV_OUT            0x51486000 0x047C7000  75264000
[RSC] INDEV_TRIMING_VIEW_WORK  0x56550000 0x02200000  35651584
[RSC] INDEV_YUV_IN             0x58750000 0x05780000  91750400
[RSC] INDEV_SLIDE_SHOW_WORK    0x5DEDA800 0x01FA4000  33177600
[RSC] INDEV_IMGPLAYWORK        0x60000000 0x05400000  88080384
[RSC] INDEV_WORK               0x65400000 0x10B00000 279969792
[RSC] INDEV_EXMEM3_AREA        0x7A2E3000 0x051D8000  85819392

[RSC] --- DP ----
[RSC] DP_SS-1                  0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_YUV 1st-1             0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_YUV 2nd-1             0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_YUV_IN                0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_YUV_OUT               0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_MULTI_CHUNK           0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_WORK                  0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_SINGLE_CHUNK          0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_SS-2                  0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_YUV 1st-2             0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_YUV 2nd-2             0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_YUV Thumb             0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_SLIDE_SHOW_WORK       0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_SUSAN_YUV             0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_KAITO_YUV             0x00000000 0x00000000         0 [Cacheable!
[RSC] DP_MOVIE_REC_YUV         0x00000000 0x00000000         0 [Cacheable!

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FSc4gW4J%2FRP.png&hash=26e494fbf14046d2a897914a46d6ab5d)

RP has 2GB of RAM.
Title: Re: Canon EOS R / RP
Post by: coon on September 22, 2020, 12:48:48 AM
Got portable dumper working on RP by finding the card init stub (thx to names_are_hard for some help!):

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fcdn.discordapp.com%2Fattachments%2F754146111987646464%2F757722386576441414%2Funknown.png&hash=3f83ed932b8903ab73c5897b16971c24)

Interestingly the firmware file sizes compared to Canon Basic dumper are different.

Portable Dumper:
ROM0.bin: 32MB
ROM1.bin: 16MB

Canon Basic Dumper:
gang100.bin: 32MB
gang200.bin: 32MB

However, both firmware dumps are binary equal. (ROM0.bin == gang100.bin, ROM1.bin == gang200.bin), while ROM0.bin / gang100.bin have some usual noise in the last section of the files.

File content of gang200.bin from 16MB on does only consist of 0xFF values so the real size of it seems to be 16MB.
Title: Re: Canon EOS R / RP
Post by: coon on October 01, 2020, 10:06:07 PM
I am now able to blink the SD card LED of RP v1.5.0 via Canon Basic:

Code: [Select]
private sub Initialize()
    System.Create()

    ExportToEventProcedure("LedOn",0xE0587BC5)
    ExportToEventProcedure("LedOff",0xE0587BE5)

    For i = 1 To 3
      LedOn(1)
      SleepTask(500)
      LedOff(1)
      SleepTask(500)
    Next
end sub


However, if I try to use LedOn and LedOff stubs on the portable dumper like this:

Code: [Select]
void (*LedOn)(int unknown)  = 0xE0587BC5;
void (*LedOff)(int unknown) = 0xE0587BE5;

while (true) {
  LedOn(1);
  busy_wait(500);
  LedOff(1);
  busy_wait(500);
}

It will crash on LedOn() call. It seems these functions do need some initialization before they can be used.
Title: Re: Canon EOS R / RP
Post by: Walter Schulz on October 01, 2020, 10:24:59 PM
IANAP but are you able to run Canon Basic scripts in QEMU?
Title: Re: Canon EOS R / RP
Post by: coon on October 01, 2020, 10:29:40 PM
I don't know how. Canon basic may be initialized as well before. We are not very far with qemu yet. We are only able to run the portable dumper and we can run the dump_task of digic6 dumper. d6 dumper does not run on real hw yet.
Title: Re: Canon EOS R / RP
Post by: coon on October 01, 2020, 11:43:10 PM
We just had a breakthrough. Digic 6 dumper does work on RP! We can now start tasks and run our own code side by side to canon gui:


The code I am executing:

Code: [Select]
static void DUMP_ASM dump_task()
{
  void (*LedOn)(int unknown)  = 0xE0587BC5;
  void (*LedOff)(int unknown) = 0xE0587BE5;

  while (true) {
    LedOn(1);
    msleep(500);
    LedOff(1);
    msleep(500);
  }
}
Title: Re: Canon EOS R / RP
Post by: IDA_ML on October 02, 2020, 07:42:16 AM
This is very exciting news.  Congratulations!
Title: Re: Canon EOS R / RP
Post by: kitor on October 02, 2020, 09:53:17 AM
We have a blink. I repeat, we have a blink!

Hello world coming soon confirmed?  ;)
Title: Re: Canon EOS R / RP
Post by: coon on October 02, 2020, 08:34:57 PM
Of course. :) Next task is getting control over the display. Shouldn't be too hard, since portable dumper already guesses the required addresses correctly.
Title: Re: Canon EOS R / RP
Post by: Nigel95 on October 02, 2020, 08:54:42 PM
Amazing keep up the good work!!
Title: Re: Canon EOS R / RP
Post by: reddeercity on October 03, 2020, 01:44:23 AM
I haven't bought a camera yet but the EOS R with this break though is looking tempting to bought one , great job !
Title: Re: Canon EOS R / RP
Post by: kitor on October 03, 2020, 10:43:55 AM
I haven't bought a camera yet but the EOS R with this break though is looking tempting to bought one , great job !

Not that I had Hello World running on R a year ago ;)
https://www.magiclantern.fm/forum/index.php?topic=22770.msg215750#msg215750

Just porting it further is 'above my paygrade'.

However, if there's a progress made on RP (and I have high hopes in @coon work, considering his experience as listed on twitter), I will attempt to port his work to R.
Title: Re: Canon EOS R / RP
Post by: coon on October 04, 2020, 01:28:11 PM
I have also some issues on finding the vram_info struct location at the moment. I have found the location where it *should* be, based on the code of 200D but I cannot see valid pointers to MARV structs there so I am still investigating...

[...] explanation below bmp_vram_info sits at 0xFB2C, not 0xFB1C. How I found this?

Code: [Select]
for(uint32_t* i = 0x40000000; i < 0x80000000; i+=1) {
  if(*i == 0x412ff900) uart_printf("vram1 %p \n", i);
  if(*i == 0x414ff400 ) uart_printf("vram2 %p \n", i);
}

Wow, now that's an aggressive method :). Dereferencing thousands of invalid pointers didn't crash your cam?
If nothing helps and if I should lose all of my hope I also meight doing it that way. Just want to mention that calling

Code: [Select]
dump_file("RAM41.BIN", 0x80000000, 0x40000000);

Didnt started to dump and made my led blink in a different pattern suddenly, so it brought my camera in some glitched state which was fixed after a battery pull.
Title: Re: Canon EOS R / RP
Post by: srsa on October 04, 2020, 01:54:04 PM
Code: [Select]
dump_file("RAM41.BIN", 0x80000000, 0x40000000);

Didnt started to dump and made my led blink in a different pattern suddenly, so it brought my camera in some glitched state which was fixed after a battery pull.
Try dumping it in a buffered way, not directly.
Title: Re: Canon EOS R / RP
Post by: coon on October 05, 2020, 12:56:42 AM
Dereferencing thousands of invalid pointers didn't crash your cam?

Nevermind, I read your code wrong. You are basically scanning the whole memory for the MARV pointers. I've also done that but "offline" on a 1GB RAM dump and found a structure which meight be the vram_info struct. However, the backbuffer pointer does always seem to be zero!? I need to do some deeper investigation here.

Addresses in this struct seem always to be the same, even after battery pull:
Code: [Select]
0x41100100
0x41340400

By inspecting the buffers at that place I have verified, that I am on the right track. Both buffers contain the same images and have a resolution of 736x480, which matches the resolution of the LCD screen. names_are_hard did some analysis on the image format and found out that it is UYVYAA with JFIF colourspace:

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fcdn.discordapp.com%2Fattachments%2F754146111987646464%2F762441266335711262%2Ftest.jpg&hash=9689193b7aa9fe4e7e9d5017a42ad404)


By searching the memory for more MARV signatures I have found two other buffers with a resolution of 960x540, which matches the resolution of the EVF. For some reason the image format is BGRA here:

Code: [Select]
0x2C1E100
0x2E18600

The first buffer is for menu and general overlays:
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fcdn.discordapp.com%2Fattachments%2F754146111987646464%2F762443301369675806%2Ftest.png&hash=5fa97c5b47c4dc7695e62baf9fbd0ccb)

The second buffer holds the focus point overlay:
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fcdn.discordapp.com%2Fattachments%2F754146111987646464%2F762445638469943356%2Ftest.png&hash=26ef8b039f43a8350f4963f60f659f10)

names_are_hard has written some python scripts to decode the different vram buffer format. I will merge them into some auto vram image finder / extractor tool and publish it somewhere. Probably here.

There is still a 736x480 buffer left at
Code: [Select]
0x9F624800

Which I haven't dumped yet, because lack of time. I will let you know what's inside soon.
Title: Re: Canon EOS R / RP
Post by: coon on October 06, 2020, 12:30:25 AM
I don't get the colors right yet, but I can draw proper shapes on the screen. We have debug output now. :)

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FK9C1j12%2Fdebug-output2.jpg&hash=ac78f7c74dbbd199ca9731ef57df154a)
Title: Re: Canon EOS R / RP
Post by: nikfreak on October 06, 2020, 08:17:38 PM
Keep up the good work.
Title: Re: Canon EOS R / RP
Post by: garry23 on October 06, 2020, 08:33:02 PM
I’ve been watching these developments with interest and much ignorance, but with high hopes.

What I think I see is a ‘quick’ way to get a scripting environment running, ie before, hopefully, we have a rich/full ML environment up and running, ie with menus etc.

Assuming, once again in ignorance, a Basic scripting API can access/control, ie set/get, key functions, eg shutter, aperture, ISO and, ideally, focus distance etc, such a scripting environment will be very handy for photographers.

I could imagine converting major parts of my DOFIS Lua script to a Basic script, ie giving focus DoF and focus bracketing feedback. Crude, but, I suggest, useful low hanging fruit.

But, as I say, I may be talking in ignorance of what is achievable via a Basic scripting feature.
Title: Re: Canon EOS R / RP
Post by: Walter Schulz on October 06, 2020, 08:54:07 PM
Huh? I thought coon and his supporters left scripting and going towards full scale ML coding right now ...
Clarification, please!
Title: Re: Canon EOS R / RP
Post by: garry23 on October 06, 2020, 08:58:24 PM
Yes, I get that, but I have no idea of the time/effort to get a useful Basic scripting API up and running, vs a ‘stable’ full ML environment.

I was only thinking out loud.
Title: Re: Canon EOS R / RP
Post by: names_are_hard on October 06, 2020, 10:17:50 PM
You could certainly get Basic to do pretty much anything, but for anything complicated it's harder than C (anything where Basic doesn't have a function already given to you).  For simple stuff, if you don't want menus, or maybe even keys, possibly Basic would be easier.  But which tasks are simpler?  That's not easy to tell in advance.

Additionally, time spent making things work in Basic doesn't progress ML at all.  And, it's a different language, that most of the ML devs won't have used before, so they have to learn it first.  If it's the same devs working on it, it takes time away from ML dev, so it's a tradeoff.  If you want to learn Canon Basic and work on it, that would be great!  There's a lot you can do with it and CHDK documents some of it, with examples.
Title: Re: Canon EOS R / RP
Post by: garry23 on October 06, 2020, 11:09:38 PM
@names_are_hard

I didn’t make myself clear enough.

I was suggesting that maybe having access to Basic might ‘satisfy’ those of us that script, rather than waiting for a Lua implementation.

As I say, I was thinking out load and will now stop thinking  ;) :)
Title: Re: Canon EOS R / RP
Post by: srsa on October 06, 2020, 11:30:16 PM
I was suggesting that maybe having access to Basic might ‘satisfy’ those of us that script, rather than waiting for a Lua implementation.
I don't think so.
A Basic script can only be started once.
It locks the Canon UI while it runs.
I tried making a shooting script on PowerShots with some tricks (multi-threading, basically), but those tricks crash dual core cameras. The language (its interpreter) is most likely not thread-safe.
Canon Basic scripting is a great tool for early development, dumping memory, setting bootflag, trying things out while running native code isn't working yet on a camera. That's all.
Title: Re: Canon EOS R / RP
Post by: garry23 on October 06, 2020, 11:35:17 PM
@srsa

Thanks for the insight.

BTW I looked over on the CHDK site and now understand the limitations of Canon Basic.

Cheers

Garry
Title: Re: Canon EOS R / RP
Post by: Nigel95 on October 06, 2020, 11:38:08 PM
I don't get the colors right yet, but I can draw proper shapes on the screen. We have debug output now. :)

(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fi.ibb.co%2FK9C1j12%2Fdebug-output2.jpg&hash=ac78f7c74dbbd199ca9731ef57df154a)
Great to see progress. As a noob I am wondering. In terms of any basic first version that requires testing. Is the current stage at something like 5% progress, 20%?
Is it possible at all to tell?

In no way I'm trying to push just curious how to interpret some posts over here as a noob. I will just think like there will never be a ML on this cams :) Thanks for the hard work.
Title: Re: Canon EOS R / RP
Post by: names_are_hard on October 07, 2020, 01:03:17 AM
Early, 1% perhaps.  There is no real way to tell.  This is a puzzle game, you don't know how many levels there are, and you don't know if one of the levels will be a puzzle that is too hard for you to solve.
Title: Re: Canon EOS R / RP
Post by: coon on October 07, 2020, 11:14:18 AM
All what we have done so far (and are still doing) is preparatory work so we will have a fundament for beginning the actual ML port.

What happened until now:
- FIR encryption on newer models has changed so we had no easy option anymore (only UART) to set the boot flag, which is required for ML to boot. Luckily Canon Basic support has been added which allowed it again, so we used it.

- Portable dumper was bootable after finding some required routines in the original firmware and after a little fix in the display code. This showed that we can execute arbitrary code in general. However, portable dumper starts before the firmware has booted and all hardware is initialized. Most of the cameras functions cannot be used at this stage. Therefore our next goal was to boot digic6-dumper, which is a minimal version of ML.

- After finding some more routines in the firmware we were able to boot digic6-dumper and let the SD card access LED blink. We can now execute arbitrary code while hardware is initialized. We can also use the LED to give us some feedback of what our code does.

- We found out where the frame buffers are and what their image format is. We are now able to draw on the screen and can use it for a very convenient debug output.

What happens next:
- Find out how the buttons work, so we can interact with our code and don't have to compile a new firmware every time if we want to test something. Maybe implementing some interactive RAM dumper where target address and dump size can be set by user for example. We could also use that to write to specific RAM addresses, to test if we found correct hardware addresses.
- Get stock firmware of RP run in QEMU.


Great to see progress. As a noob I am wondering. In terms of any basic first version that requires testing. Is the current stage at something like 5% progress, 20%?
Is it possible at all to tell?

In no way I'm trying to push just curious how to interpret some posts over here as a noob. I will just think like there will never be a ML on this cams :) Thanks for the hard work.

I don't expect anything usable before mid 2021.
Title: Re: Canon EOS R / RP
Post by: Walter Schulz on October 07, 2020, 11:30:57 AM
What you wrote:

I don't expect anything usable before mid 2021.

What average user reads
Quote
You have the right to go ballistic if there isn't a full working ML at 01.07.2021 00:00:01.
Title: Re: Canon EOS R / RP
Post by: coon on October 07, 2020, 11:59:03 AM
And then what? I am doing this in my free time. I am doing this to make my fancy camera even more fancy. Other people may profit from that as well. Nobody pays me so I don't owe someone something.

What I have meant: An unstable ML with minimal features, which I wouldn't recommend for daily use, could be available at the earliest mid 2021 for alpha testing, if we are very very lucky.
Title: Re: Canon EOS R / RP
Post by: theBilalFakhouri on October 07, 2020, 12:34:59 PM
I don't owe someone something.

Of course, some users might build their dreams in that date you gave, like We will have 4K RAW capability on EOS RP in mid 2021! or something like that, they would think you gave a promise at that date, be prepared for some aggressive users :P

Otherwise the most users understand what porting ML is, and they understand what you mean.

Nice work by the way! :D
Title: Re: Canon EOS R / RP
Post by: Nigel95 on October 07, 2020, 01:40:38 PM
Good to clarify this up indeed. Work on the project whenever you want and try to enjoy it as much as possible. If you and others ever succeed to put ML on this camera that would be amazing! And if it doesn't get to that stage. Well at least you had fun in it if you work on it when you want and you also learned something along the way.

BTW is there a reason why ML is free? Has this something to do with Canon to avoid any law suits?

If it takes so much work for developers I think it would be fair to compensate them for firmware that works properly. (if it's stable and sort of reliable). Maybe people don't like to donate in advance in the hope there ever will be ML on a cam. Although for 'stable firmware' I think people would like to pay some money? This would be nice for developers to earn a bit of money by doing their hobby. It's probably not enough for all the hours that go into it. But it's always nice to gain a little bit of money by doing what you love.
Title: Re: Canon EOS R / RP
Post by: Walter Schulz on October 07, 2020, 01:49:43 PM
If it takes so much work for developers I think it would be fair to compensate them for firmware that works properly. (if it's stable and sort of reliable). Maybe people don't like to donate in advance in the hope there ever will be ML on a cam. Although for 'stable firmware' I think people would like to pay some money?

Lookup your fallacy here (https://en.wikipedia.org/wiki/List_of_fallacies). Poll result: https://mobile.twitter.com/autoexec_bin/status/1182941915337150464
Title: Re: Canon EOS R / RP
Post by: Nigel95 on October 07, 2020, 03:09:12 PM
Lookup your fallacy here (https://en.wikipedia.org/wiki/List_of_fallacies). Poll result: https://mobile.twitter.com/autoexec_bin/status/1182941915337150464

To lazy to read it all. Based on what I know about fallacies. I would assume you mean faulty generalization. Good one, it was my own opinion and shouldn't sell it as the opinion of a larger sample :)

Your comments make me laugh sometimes on the forum here. To the point although a bit cocky. Maybe it's the result of all the noob questions here. Maybe it's the way you are as a person. Or both?
Title: Re: Canon EOS R / RP
Post by: coon on October 11, 2020, 06:21:01 PM
Finding button states in RAM is not an easy task (at least for me) so after hours of searching I have given up that route for now and did some research on the MPU instead.
I have used this post from a1ex as a reference: https://magiclantern.fm/forum/index.php?topic=2864.msg169517#msg169517

By reading mpu_recv_ring_buffer and using the LCD to display all received mpu messages I have retreived almost all button codes of RP:

Code: [Select]
Power Switch:               0x00 => params: on: 0x01, off: 0x00
half shutter:               0x05
shutter:                    0x06
* AE-Lock/FE-Lock           0x07
AF-ON:                      0x08
AF Point/Index/Magnify:     0x0B
M-Fn:                       0x0C
Q/set:                      0x0D
menu:                       0x0E
Playback:                   0x0F
info:                       0x10
Trashcan:                   0x11
movie shooting:             0x14
up:                         0x15
down:                       0x16
right:                      0x17
left:                       0x18
Main dial:                  0x19 => params: clockwise: 0x01, anti clockwise: 0xFF
Quick control dial:         0x1A => params: clockwise: 0xFF, anti clockwise: 0x01
multi-function lock switch: 0x1B
Mode dial:                  0x23 => params:
  0x01: C3
  0x02: Tv
  0x05: Movie
  0x06: P
  0x07: SCN
  0x08: Manual
  0x09: C2
  0x0A: Av
  0x0C: Bulb
  0x0D: C1
  0x0E: Fv
  0x0F: Auto

Reading mpu ring buffer via polling should make simple helper menus for convenient developing possible now.
Title: Re: Canon EOS R / RP
Post by: 71m363nd3r on October 12, 2020, 05:24:04 AM
nice work coon!  8)
Title: Re: Canon EOS R / RP
Post by: coon on October 22, 2020, 12:11:57 AM
As already mentioned in Battery grip pins / UART (https://www.magiclantern.fm/forum/index.php?topic=7531.msg232097#msg232097) Thread, I've managed to get access to physical UART on RP without the need of disassembling the camera. I have found out the following pinout so far:

Code: [Select]
1: (Unknown traffic on boot) (1v8)
2: Maybe RXICU (1v8)
3: TXICU (1v8)
4: GND
5: Maybe RXMPU (3v3)
6: TXMPU (3v3)
7: Unknown (3v3)
8: Unknown (3v3)

Here is some UART traffic I have received:

MPU output when switching on camera:
Code: [Select]
RSTFLG : 0010
E0ON
E1ON
openBattery

MON>>>sw task Initialize Complete
/USB_DET undetected
batt task Initialize Complete
adapter task Initialize Complete
temp_task.c:356 I2C Comm Error ret=1
disp task Initialize Complete
acc task Initialize Complete
setCCSnkRst
temp task Initialize Complete
Main Task receive from ICU ptr(0x20003940) size=0x04 cmmand=0x01 dataId=0x00
================SD send recode 0 0
Main Task receive from ICU ptr(0x20003940) size=0x0A cmmand=0x02 dataId=0x10
temp_task.c:421 I2C Comm Error ret=1
Main Task receive from ICU ptr(0x20003940) size=0x0B cmmand=0x0C dataId=0x00
Main Task receive from ICU ptr(0x20003940) size=0x0B cmmand=0x0C dataId=0x00
temp_task.c:421 I2C Comm Error ret=1
temp_task.c:421 I2C Comm Error ret=1
temp_task.c:421 I2C Comm Error ret=1
temp_task.c:421 I2C Comm Error ret=1
temp_task.c:421 I2C Comm Error ret=1
temp_task.c:421 I2C Comm Error ret=1

I don't know why there are so many I2C errors. Maybe because I didn't had any lens attached.

ICU output when switching on camera:
Code: [Select]
BootLoade[00]K433 READY
       31:      8.828 [STARTUP] K433 ICU Firmware Version 1.5.0 ( 3.8.7 )
      169:    116.237 [BATCHK] ERROR PROP_ACTIVE_SWEEP_STATUS : 0
      178:    116.696 [BATCHK] ERROR PROP_ACTIVE_SWEEP_STATUS : 0
      570:    155.915 [PA] WARN EventDispatch Current=1,dwEventID=3,dwParam=0x0
      980:    250.283 [PROPAD] ERROR GetPropertyData ID (0) = 0x0E090000
      981:    250.289 [PRP] ERROR NotFoundID:0x0E090000,Func:0xE0447AA4
     2002:    497.515 [GUI] ERROR m_hThisBDialog NULL !!
     2003:    497.645 [GUI] ERROR RefreshAfFrameSelectDialog NULL !!
     2083:    634.894 [FM] EV_INSERTION_COMPLETE : ID = 1(0), stat = 8192
     2337:    853.225 ------------------------------
     2338:    853.233 Camera Flag Current Setting
     2339:    853.238 ------------------------------
     2340:    853.242       14 Mode ON
     2341:    853.266 ------------------------------
     2427:    900.955 [GUI] ERROR RefreshAfFrameSelectDialog NULL !!
     2514:    948.596 ERROR [MEM] Over Permanet Memory cache 48 18100

Now this is a bit disappointing. I was expecting a more detailed output here. When using QEMU with gdb attached I can see some NotifyComplete messages. These would be interesting to see on real HW. Is there a way to enable those?
Title: Re: Canon EOS R / RP
Post by: deviousfusion on October 30, 2020, 12:41:13 PM
Interesting. Shutter count also broken here or has some encoding scheme.
Thanks for providing this!

Could you edit your post and wrap the XML output into code blocks like this?

[code]
<xml code here>
[/code]

It's easier to read like this.

It meight be interesting getting a dump of a fresh RP with 0 shots taken to find out the origin value. But it will be very hard to find such I guess...

Not sure if this is still applicable or needed, but I just bought a RP and have taken a single shot. Here is my XML:
Code: [Select]
<?xml version="1.0"?>
  <Canon>
    <CameraInfo>
      <Serial>XXXXX</Serial>
      <FirmwareVer>
        <Internal>0.3.8.7</Internal>
        <Major>1.5.0</Major>
      </FirmwareVer>
      <ErrorList></ErrorList>
      <TotalShoot>1</TotalShoot>
      <TotalShutter>1086947310</TotalShutter>
      <PowerOnCount>16</PowerOnCount>
      <TotalRunningTime>1829</TotalRunningTime>
    </CameraInfo>
  </Canon>

Based on this the origin value appears to be 1086947309
Title: Re: Canon EOS R / RP
Post by: coon on November 20, 2020, 08:58:09 PM
Canon has released Firmware Update 1.6.0 (https://www.canon-europe.com/support/consumer_products/products/cameras/digital_slr/eos-rp.html?type=firmware&firmwaredetailid=tcm:13-2038522&os=windows%2010%20%2864-bit%29&language=en) for RP recently which I have applied today. Canon Basic does still work. I have taken a dump already.

I also got some E70 errors in the error log, which I have triggered in the past by my code accidentally:

Code: [Select]
<ErrorList>
  <Kind>
  <ID>E70</ID>
  <Count>4</Count>
  <ErrorLog>
    <BatTemperature>max:0 min:0</BatTemperature>
    <FirstOccurTime>2020.10.03 00:28:07</FirstOccurTime>
    <LastOccurTime>2020.11.20 21:05:14</LastOccurTime>
    <Log>
      <DateTime>2020.11.20 21:05:14</DateTime>
      <Reason>DS-EID:101</Reason>
      <BatTemperature>0</BatTemperature>
      <LensID>00000000</LensID>
      <ReleaseCount>1844</ReleaseCount>
    </Log>
    <Log>
      <DateTime>2020.10.24 00:47:12</DateTime>
      <Reason>DS-EID:101</Reason>
      <BatTemperature>0</BatTemperature>
      <LensID>00000000</LensID>
      <ReleaseCount>1833</ReleaseCount>
    </Log>
    <Log>
      <DateTime>2020.10.24 00:46:04</DateTime>
      <Reason>DS-EID:101</Reason>
      <BatTemperature>0</BatTemperature>
      <LensID>00000000</LensID>
      <ReleaseCount>1833</ReleaseCount>
    </Log>
    <Log>
      <DateTime>2020.10.03 00:28:07</DateTime>
      <Reason>DS-EID:101</Reason>
      <BatTemperature>0</BatTemperature>
      <LensID>00000000</LensID>
      <ReleaseCount>1830</ReleaseCount>
    </Log>
  </ErrorLog>
  </Kind>
</ErrorList>

I have triggered them when trying to read from memory >= 0x8000000 via DMA access. I think these memory regions may be read via buffered reads.

Downgrade back to 1.5.0 was possible out of the box. No battery door trick or similiar was needed.
Title: Re: Canon EOS R / RP
Post by: coon on November 27, 2020, 08:49:11 PM
Not sure if this is still applicable or needed, but I just bought a RP and have taken a single shot. Here is my XML:
Code: [Select]
<?xml version="1.0"?>
  <Canon>
    <CameraInfo>
      <Serial>XXXXX</Serial>
      <FirmwareVer>
        <Internal>0.3.8.7</Internal>
        <Major>1.5.0</Major>
      </FirmwareVer>
      <ErrorList></ErrorList>
      <TotalShoot>1</TotalShoot>
      <TotalShutter>1086947310</TotalShutter>
      <PowerOnCount>16</PowerOnCount>
      <TotalRunningTime>1829</TotalRunningTime>
    </CameraInfo>
  </Canon>

Based on this the origin value appears to be 1086947309

Sorry, I have overlooked your answer until now. Thanks for that interesting information! Yes, it seems the shutter count starts at 1086947309 for some reason.
Title: Re: Canon EOS R / RP
Post by: kitor on December 15, 2020, 08:48:56 PM
If you were wondering where the missing posts went:

DIGIC 8 DryOS Shell (drysh) investigation (https://www.magiclantern.fm/forum/index.php?topic=25662.0)
DIGIC 8 MPU investigation (https://www.magiclantern.fm/forum/index.php?topic=25661.0)
Title: Re: Canon EOS R / RP
Post by: DeafEyeJedi on December 18, 2020, 09:01:57 AM
Damn @coon, Great work and Keep it up!  ;D
Title: Re: Canon EOS R / RP
Post by: coon on December 22, 2020, 04:11:04 PM
All information in this post do refer to EOS RP with firmware 1.6.0.

I have done some further investigations on VRAM handling and it seems that Canon has changed it on newer models. On my initial investigations (https://www.magiclantern.fm/forum/index.php?topic=22770.msg231637#msg231637) I have done a full RAM dump and searched for the MARV signatures manually to find the VRAM buffers. This worked fine as a first entry point to draw simple things on the LCD but drawing in EVF or HDMI output did not work properly with this method. Therefore I have analysed the SaveVRAM event procedure to find out some more information about the buffer handling.

In the past the structure of struct bmp_vram_info was like this:

Code: [Select]
struct bmp_vram_info
{   
    struct MARV * vram1;        /* one of the two bitmap buffers - statically allocated? */
    struct MARV * vram2;        /* the other bitmap buffer */
    struct MARV * back_vram;    /* we need to write to the other one */
};

vram1 and vram2 are two buffers which are written in an alternating way to prevent flicker.
back_vram points to the back buffer.

On RP Canon has changed it to this:

Code: [Select]
struct bmp_vram_info
{   
    struct MARV * vram1;        /* one of the two bitmap buffers - statically allocated? */
    struct MARV * vram2;        /* the other bitmap buffer */
};

Plus now there is a global buffer index at 0xFF6C with the index of the current back buffer. It is either 0 or 1.

There are 3 YUV (UYVYAA) buffer pairs in total. One back and one front buffer each. Only one of the three buffer pairs seems to used:

Code: [Select]
vramBufferPairNo = 0: Final image displayed on LCD or EVF without sensor image
vramBufferPairNo = 1: Nullptr (Unknown)
vramBufferPairNo = 2: Nullptr (Unknown)

I don't know if buffer pairs 1 and 2 are ever used.

Formular for getting YUV buffers:

Code: [Select]
DAT_e0255238 + vramBufferPairNo * 0x28 + (1 - vram_current_buffer) * 4 - 0x5c

DAT_e0255238 is the dereferenced value on address 0xE0255238 which is 0x722B0.
vramBufferPairNo selects the buffer pair. Valid values are 0 to 2. It seems that buffer 1 and 2 are unused.
vram_current_buffer is the dereferenced value of 0xFF6C and is either 0 or 1.

There are 6 BGRA buffers in total. They are not double buffered and only two them are used in practice:

Code: [Select]
vramBufferNo = 0: Menu and Live View Overlays
vramBufferNo = 1: Focus point overlay
vramBufferNo = 2: Nullptr (Unknown)
vramBufferNo = 3: Nullptr (Unknown)
vramBufferNo = 4: Nullptr (Unknown)
vramBufferNo = 5: Nullptr (Unknown)

Formular for getting BGRA buffers:
Code: [Select]
DAT_e0331888 + vramBufferNo * 0xc


With this information I am now able to draw proper images on LCD, EVF and HDMI output. However, due to the pixel wise "software" rendering via CPU the current rendering performance with about 3 fps is quite bad.
I assume that actual rendering by Canon code is done in the BGRA buffers and are then composited and converted to YUV by some coprocessor. I don't know how to trigger that conversion in Canon firmware. Once I have found that out rendering speed should increase significantly. Until full ML does not run on RP, speed is not in focus so I will keep it like that for now.

Bad news are, that the new VRAM handling does require some adjustment in ML code. Good news are that R5 and R6 do also seem to use this new rendering method so they will profit from these changes as well. EOS R does still use the old method.
Title: Re: Canon EOS R / RP
Post by: sombree on December 27, 2020, 07:32:03 PM
This Canon Basic script enables silent shutter on RP:
Code: [Select]
private sub Initialize()
    ExecuteEventProcedure("sht_EnableManualSilent")
end sub
Works in M, Av, Tv and P both in single and continuous modes. Works fine with interval timer. Fails with ERR70 in bulb.
Title: Re: Canon EOS R / RP
Post by: c_joerg on December 27, 2020, 08:26:55 PM
Would be interesting to know whether you could also switch off the crop mode for EFS lenses.
Title: Re: Canon EOS R / RP
Post by: coon on December 28, 2020, 06:56:59 PM
This Canon Basic script enables silent shutter on RP:
Code: [Select]
private sub Initialize()
    ExecuteEventProcedure("sht_EnableManualSilent")
end sub
Works in M, Av, Tv and P both in single and continuous modes. Works fine with interval timer. Fails with ERR70 in bulb.

Nice finding! It seems we have a first feature for RP :). Usually silent shutter is only possible in SCN mode or when performing a focus bracketing shoot but not in any other modes.
When do you get ERR70 in bulb? Directly after shutter press or when it tries to close the shutter?
Title: Re: Canon EOS R / RP
Post by: coon on December 28, 2020, 08:24:25 PM
I have found a firmware version independent and read only method to find LED GPIO addresses of newer camera models and created a little Canon Basic script for that.
Sample usage for RP:

Code: [Select]
'LED GPIO dumper for EOS RP
dim gpio_base      = 0xD0130000
dim led_obj_ptr    = 0x4E28
dim led_obj_offset = 0x28
dim led_count_max  = 15

private sub save_led_gpio_addresses(fileName)
  RemoveFile(fileName)

  f = OpenFileCREAT(fileName)
  CloseFile(f)

  f = OpenFileWR(fileName)
  pLedObjectBase = *led_obj_ptr

  ledKind = 0

  do while ledKind < led_count_max
    pLedObject = pLedObjectBase + ledKind * led_obj_offset
    ledGpioOffset = pLedObject + 8

    WriteFileString(f, "[0x%08X] LED %d: 0x%08X\n", pLedObject, ledKind, gpio_base + *ledGpioOffset)
    ledKind = ledKind + 1
  loop

  CloseFile(f)
end sub

private sub Initialize()
  save_led_gpio_addresses("B:/LED_GPIOS.TXT")
end sub

The script saves the following content:

Code: [Select]
[0x00D2DE8C] LED 0: 0xD01300D4
[0x00D2DEB4] LED 1: 0xD0130000
[0x00D2DEDC] LED 2: 0xD01300D8
[0x00D2DF04] LED 3: 0xD0130000
[0x00D2DF2C] LED 4: 0xD0130000
[0x00D2DF54] LED 5: 0xD0130000
[0x00D2DF7C] LED 6: 0xD01300DC
[0x00D2DFA4] LED 7: 0xD0130000
[0x00D2DFCC] LED 8: 0xD0130000
[0x00D2DFF4] LED 9: 0xD0130000
[0x00D2E01C] LED 10: 0xD0130000
[0x00D2E044] LED 11: 0xD0130000
[0x00D2E06C] LED 12: 0xD0130000
[0x00D2E094] LED 13: 0xD0130000
[0x00D2E0BC] LED 14: 0xD0130000

The output suggests that there are three LEDs on RP (four LEDs if you also count the addresses ending with 0).

Code: [Select]
LED 0: 0xD01300D4 - Card LED
LED 2: 0xD01300D8 - Auto Focus Assist LED
LED 6: 0xD01300DC - Unknown / Nothing happens
Other LEDs: 0xD0130000 - Unknown / Nothing happens

Writing to these addresses will toggle the LEDs.
Values to toggle GPIOs on RP are:

Code: [Select]
LED_ON_BITMASK:  0x4D0002
LED_OFF_BITMASK: 0x4C0003

The script can also be run on other newer models. One has to find and set the following parameters for their camera model:

Code: [Select]
gpio_base
led_obj_ptr
led_obj_offset
led_count_max

The parameters can be found by inspecting led.set.directly function which can be found at 0xE0697DAA on RP 1.6.0 firmware. The function may also be named LEDDrv_SetLEDDirectly on other models.

Function signature is:

Code: [Select]
int led_set_directly(uint ledKind, int controlId)

Parameters for EOS R are:

Code: [Select]
'LED GPIO dumper for EOS R
dim gpio_base      = 0xD0130000
dim led_obj_ptr    = 0x4DDC
dim led_obj_offset = 0x24
dim led_count_max  = 13

Script from above with these values produces:

Code: [Select]
[0x00D7D7B4] LED 0: 0xD01300D4
[0x00D7D7D8] LED 1: 0xD0130000
[0x00D7D7FC] LED 2: 0xD01300D8
[0x00D7D820] LED 3: 0xD0130000
[0x00D7D844] LED 4: 0xD0130000
[0x00D7D868] LED 5: 0xD0130000
[0x00D7D88C] LED 6: 0xD0130000
[0x00D7D8B0] LED 7: 0xD0130000
[0x00D7D8D4] LED 8: 0xD0130000
[0x00D7D8F8] LED 9: 0xD0130000
[0x00D7D91C] LED 10: 0xD0130000
[0x00D7D940] LED 11: 0xD0130000
[0x00D7D964] LED 12: 0xD0130000

GPIO addresses are similiar to RP but LED 6 does also end with 0 here.

However, it's not trivial to get the values for R6 since the value for gpio_base is stored in RAM.
Could someone with an R6 execute this and tell me the result?

Code: [Select]
'Get R6 LED base

private sub save_led_base(fileName)
  RemoveFile(fileName)

  f = OpenFileCREAT(fileName)
  CloseFile(f)

  f = OpenFileWR(fileName)

  pLedBase = 0x4F54
  WriteFileString(f, "LED base 1: [0x%08X]: 0x%08X\n", pLedBase, *pLedBase)

  pLedBase = 0x4F5C
  WriteFileString(f, "LED base 2: [0x%08X]: 0x%08X\n", pLedBase, *pLedBase)

  CloseFile(f)
end sub

private sub Initialize()
  save_led_base("B:/LED_BASE.TXT")
end sub

Title: Re: Canon EOS R / RP
Post by: sombree on December 28, 2020, 10:11:54 PM
Nice finding! It seems we have a first feature for RP :). Usually silent shutter is only possible in SCN mode or when performing a focus bracketing shoot but not in any other modes.
When do you get ERR70 in bulb? Directly after shutter press or when it tries to close the shutter?

Directly after shutter button press although it seems that camera starts taking picture - I can hear lens iris moving and card LED lights up (but no image saved on the card).
Title: Re: Canon EOS R / RP
Post by: coon on December 28, 2020, 10:15:22 PM
I have found a function which is used to set some GPIO pins at 0xE03B4FDC.

Signature is:

Code: [Select]
void gpioSet(int gpioOffset, int onOffBitmask)

gpioOffset is added to the fixed address 0xD0130000.
onOffBitmask is mostly 0x4D0002 to set the GPIO and 0x4C0003 to reset the GPIO. Bitmasks are different on some addresses.

The function is used to toggle GPIO pins, and some chip enable pins. It is also used to toggle some GPIO pin to low at the end of send_mpu which meight be an interrupt pin for MPU. This function may be used to identify several GPIOs.
Title: Re: Canon EOS R / RP
Post by: coon on December 29, 2020, 12:09:30 AM
Executing sht_EnableManualSilent on UART gives the following output:

Code: [Select]
K433[1]>sht_EnableManualSilent
 Enable Names
    "SHOOT"
    "LV"
    "MECHA"
    "LENS"
    "EF"
    "APEX"
    "DC_MECHA"
    "FA"
    "IS"
    "LVAF"
    "EOSAF"
    "EOSAE"
    "EDET"
    "ALL"

 Stab Status
    SHOOT : respect
    LV : respect
    MECHA : ignore
    LENS : respect
    EF : respect
    APEX : respect
    DC_MECHA : ignore
    FA : ignore
    IS : ignore
    LVAF : respect
    EOSAF : ignore
    EOSAE : ignore
    EDET : respect

 sht_EnableManualSilent returned 0(0x0)

When pressing the shutter button in manual mode an image is taken but shutter does not close. Camera is in electronic shutter mode.

Executing sht_DisableManualSilent on UART gives the following output:

Code: [Select]
K433[1]>sht_DisableManualSilent
 Enable Names
    "SHOOT"
    "LV"
    "MECHA"
    "LENS"
    "EF"
    "APEX"
    "DC_MECHA"
    "FA"
    "IS"
    "LVAF"
    "EOSAF"
    "EOSAE"
    "EDET"
    "ALL"

 Stab Status
    SHOOT : respect
    LV : respect
    MECHA : respect
    LENS : respect
    EF : respect
    APEX : respect
    DC_MECHA : ignore
    FA : ignore
    IS : ignore
    LVAF : respect
    EOSAF : ignore
    EOSAE : ignore
    EDET : respect

 sht_DisableManualSilent returned 0(0x0)

Shutter does close again in manual mode.

When pressung shutter button in Bulb mode while beeing in Silent Shutter mode camera crashes with Err70 and asserts on UART:

Code: [Select]
K433[1]>    45024: 711030.598 [STARTUP] ERROR <7>ASSERT : ImageController::ImageControllerShootCommon.c
    45025: 711030.621 [STARTUP] <7>ASSERT : Task = ShootCapture
    45026: 711030.626 [STARTUP] <7>ASSERT : Core 0
    45027: 711030.633 [STARTUP] <7>ASSERT : Line 813
    45028: 711030.640 [STARTUP] < StackDump >
    45029: 711030.644 [STARTUP] SP: 0x00245174
    45030: 711030.674 [STARTUP] 0xFFFFFFFF
    45031: 711030.679 [STARTUP] 0x00000064
    45032: 711030.682 [STARTUP] 0x00000000
    45033: 711030.693 [STARTUP] 0x40D65130
...

When pressing the shutter button in Bulb mode while in normal shutter mode you can hear some mechanical movement inside the camera before the image capturing starts, even when having the lens on the widest possible aperture and also when not having a lens attached at all. I don't know what is exactly happing here but I assume that the camera cannot move the required part for bulb mode when beeing in silent shutter mode. It does detect that and does crash.
Title: Re: Canon EOS R / RP
Post by: sombree on December 29, 2020, 09:52:12 AM
Same mechanical movement is hearable when shooting in M (or any other) mode, yet only in bulb camera errors out :)
Title: Re: Canon EOS R / RP
Post by: coon on December 29, 2020, 03:22:02 PM
If I don't have a lens attached or when lens is at widest possible aperture I don't hear anything when pressing the shutter button.
Title: Re: Canon EOS R / RP
Post by: sombree on December 29, 2020, 03:36:35 PM
I meant that same mechanical sound is hearable when shooting with normal shutter even in other modes than bulb.
Title: Re: Canon EOS R / RP
Post by: coon on January 09, 2021, 10:56:08 PM
I have found some debug function which prints the whole interrupt vector table of the RPs ICU to UART (firmware version 1.6.0):

Code: [Select]
0xe0136920: void printInterruptVectorTable(void)

It produces the following output:

Code: [Select]
<=-=-=- Vector Start -=-=-=>
0,-noise-
1,EDOMAIN_OPERA_OPEKICK0
2,EDOMAIN_EDMAC_5_WR_S1
3,EDOMAIN_EDMAC_1_RD_L0
4,EDOMAIN_VITON
5,EDOMAIN_OPERA0
6,SYNC_irq_intb60v
7,SYNC_vi_out7
8,TMU_int_SWA
9,TMU_int_pulc
10,INTC_XINT *IRQEXT
11,TCU_T0OUT *IRQEXT
12,postman_RCVINT0
13,postman_FIFOINT0
14,Eeko_TIMER_OC0_INT*ASYMMETRIC
15,Eeko_TIMER_IC0_INT*ASYMMETRIC
16,EDOMAIN_SYNGEN_1
17,EDOMAIN_OPERA_OPEKICK1
18,EDOMAIN_EDMAC_6_WR_S0
19,EDOMAIN_EDMAC_1_RD_M0
20,EDOMAIN_AFFINE
21,EDOMAIN_OPERA_ERR0
22,SYNC_irq_intb59v
23,SYNC_vi_out8
24,TMU_int_SWB
25,TMU_int_occh0SP
26,INTC_XINT *IRQEXT
27,TCU_T1OUT *IRQEXT
28,postman_RCVINT1
29,postman_FIFOINT1
30,Eeko_TIMER_OC1_INT*ASYMMETRIC
31,Eeko_TIMER_IC1_INT*ASYMMETRIC
32,EDOMAIN_SYNGEN_2
33,EDOMAIN_OPERA_OPEKICK2
34,EDOMAIN_EDMAC_6_WR_SS0
35,EDOMAIN_EDMAC_1_RD_S0
36,EDOMAIN_AFFINE_OVR_ERR
37,EDOMAIN_OPERA_ABORT0
38,SYNC_irq_intb50v
39,SYNC_vi_out9
40,TMU_int_ocall
41,TMU_int_occh0EP
42,INTC_XINT *IRQEXT
43,TCU_T2OUT *IRQEXT
44,postman_RCVINT2
45,postman_FIFOINT2
46,Eeko_TIMER_OC2_INT*ASYMMETRIC
47,Eeko_TIMER_IC2_INT*ASYMMETRIC
48,EDOMAIN_SYNGEN_3
49,EDOMAIN_OPERA_OPEKICK3
50,EDOMAIN_EDMAC_6_WR_SS1
51,EDOMAIN_EDMAC_1_RD_S1
52,EDOMAIN_SARIDON
53,EDOMAIN_OPERA1
54,SYNC_irq_intb49v
55,SYNC_vi_out10
56,TMU_int_pulgenCEI
57,TMU_int_occh1SP
58,INTC_XINT *IRQEXT
59,TCU_T3OUT *IRQEXT
60,postman_RCVINT3
61,postman_FIFOINT3
62,Eeko_TIMER_OC3_INT*ASYMMETRIC
63,Eeko_TIMER_IC3_INT*ASYMMETRIC
64,EDOMAIN_SYNGEN_4
65,EDOMAIN_OPERA_OPEKICK4
66,EDOMAIN_EDMAC_6_WR_SS2
67,EDOMAIN_EDMAC_1_RD_SS0
68,EDOMAIN_KURABO
69,EDOMAIN_OPERA_ERR1
70,SYNC_irq_intl60v
71,SYNC_vi_out11
72,TMU_int_icapCE1
73,TMU_int_occh1EP
74,INTC_XINT *IRQEXT
75,TCU_T4OUT *IRQEXT
76,postman_RCVINT4
77,postman_FIFOINT4
78,Eeko_TIMER_OC4_INT*ASYMMETRIC
79,Eeko_TIMER_IC4_INT*ASYMMETRIC
80,EDOMAIN_SYNGEN_STP
81,EDOMAIN_OPERA_OPEKICK5
82,EDOMAIN_EDMAC_6_WR_SS3
83,EDOMAIN_EDMAC_1_RD_SS1
84,EDOMAIN_MESSI
85,EDOMAIN_OPERA_ABORT1
86,SYNC_irq_intl60v_st1
87,SYNC_irq_intvi4
88,TMU_pulc_ch0
89,TMU_int_occh2SP
90,INTC_XINT *IRQEXT
91,TCU_T5OUT *IRQEXT
92,postman_RCVINT5
93,postman_FIFOINT5
94,Eeko_TIMER_OC5_INT*ASYMMETRIC
95,Eeko_TIMER_IC5_INT*ASYMMETRIC
96,EDOMAIN_SYNGEN_FRM
97,EDOMAIN_OPERA_OPEKICK6
98,EDOMAIN_EDMAC_6_WR_SS4
99,EDOMAIN_EDMAC_1_RD_SS2
100,EDOMAIN_DANCING_FEN
101,EDOMAIN_HAIDI_PNL_WR
102,SYNC_irq_intl59v
103,SYNC_irq_vi4_set_1
104,TMU_pulc_ch1
105,TMU_int_occh2EP
106,INTC_XINT *IRQEXT
107,TCU_IPCOUT4
108,postman_RCVINT6
109,postman_FIFOINT6
110,Eeko_TIMER_OC6_INT*ASYMMETRIC
111,Eeko_TIMER_IC6_INT*ASYMMETRIC
112,EDOMAIN_SYNGEN_1_A
113,EDOMAIN_EDMAC_1_WR_L0
114,EDOMAIN_EDMAC_DAN_WR
115,EDOMAIN_EDMAC_1_RD_SS3
116,EDOMAIN_DANCING_SURF
117,EDOMAIN_HAIDI_LINE_WR
118,SYNC_irq_intl59v_st1
119,SYNC_irq_vi4_set_2
120,TMU_pulc_ch2
121,TMU_int_occh3SP
122,INTC_XINT *IRQEXT
123,TCU_T4F_INT
124,postman_RCVINT7
125,postman_FIFOINT7
126,Eeko_TIMER_OC7_INT*ASYMMETRIC
127,Eeko_TIMER_IC7_INT*ASYMMETRIC
128,EDOMAIN_SYNGEN_2_A
129,EDOMAIN_EDMAC_1_WR_M0
130,EDOMAIN_EDMAC_7_WR_S0
131,EDOMAIN_EDMAC_2_RD_M0
132,EDOMAIN_DANCING_RACI
133,EDOMAIN_SHREK
134,SYNC_irq_intl50v
135,SYNC_irq_vi4_set_3
136,TMU_pulc_ch3
137,TMU_int_occh3EP
138,INTC_XINT *IRQEXT
139,TCU_IPCOUT5
140,postman_DIRECTINT0
141,postman_Semaphore0
142,Eeko_TIMER_ICOC_OC0INT*ASYMMETRIC
143,Eeko_TIMER_ICOC_IC0INT*ASYMMETRIC
144,EDOMAIN_SYNGEN_3_A
145,EDOMAIN_EDMAC_1_WR_M1
146,EDOMAIN_EDMAC_7_WR_S1
147,EDOMAIN_EDMAC_2_RD_S0
148,EDOMAIN_WOMBAT_INTEG
149,EDOMAIN_SUSAN
150,SYNC_irq_intl50v_st1
151,SYNC_irq_intvi4b
152,Camif
153,TMU_int_occh4SP
154,INTC_XINT *IRQEXT
155,TCU_T5F_INT
156,postman_DIRECTINT1
157,postman_Semaphore1
158,Eeko_TIMER_ICOC_OC1INT*ASYMMETRIC
159,Eeko_TIMER_ICOC_IC1INT*ASYMMETRIC
160,EDOMAIN_SYNGEN_4_A
161,EDOMAIN_EDMAC_1_WR_M2
162,EDOMAIN_EDMAC_7_WR_SS0
163,EDOMAIN_EDMAC_2_RD_SS0
164,EDOMAIN_WOMBAT_BLOCK
165,EDOMAIN_OHYITG
166,SYNC_irq_intlssdv
167,SYNC_irq_vi4b_set_1
168,Camif
169,TMU_int_occh4EP
170,INTC_XINT *IRQEXT
171,Aproc_irq_aproc
172,postman_DIRECTINT2
173,postman_Semaphore2
174,rem_REM_INT
175,zico_timer_irq
176,EDOMAIN_SYNGEN_STP_A
177,EDOMAIN_EDMAC_1_WR_M3
178,EDOMAIN_EDMAC_ATO_WR_SS0
179,EDOMAIN_EDMAC_3_RD_M0
180,EDOMAIN_WOMBAT_AE
181,EDOMAIN_HIP
182,SYNC_irq_intlssdv_st1
183,SYNC_irq_vi4b_set_2
184,Camif
185,TMU_int_occh5SP
186,INTC_XINT *IRQEXT
187,Aproc_irq_aproc
188,postman_DIRECTINT3
189,postman_Semaphore3
190,SDDomain_ADMAC0
191,HDMAC0_IntrReq1
192,EDOMAIN_SYNGEN_FRM_A
193,EDOMAIN_EDMAC_1_WR_M4
194,EDOMAIN_EDMAC_ATO_WR_SS1
195,EDOMAIN_EDMAC_3_RD_OPT_RICH
196,EDOMAIN_COMBAT_INTEG
197,EDOMAIN_RASH
198,SYNC_irq_intp
199,SYNC_irq_vi4b_set_3
200,Camif
201,TMU_int_occh5EP
202,INTC_XINT *IRQEXT
203,Aproc_irq_aproc
204,postman_DIRECTINT4
205,postman_fifi_err0
206,SDDomain_ADMAC1
207,HDMAC0_IntrReq2
208,EDOMAIN_SYNGEN_1_B
209,EDOMAIN_EDMAC_1_WR_S0
210,EDOMAIN_EDMAC_ATO_WR_SS2
211,EDOMAIN_EDMAC_3_RD_OPT_LITE
212,EDOMAIN_COMBAT_BLOCK
213,EDOMAIN_RSHD
214,SYNC_irq_intp_st1
215,SYNC_vi_out12
216,Camif
217,TMU_int_icapch0
218,INTC_XINT *IRQEXT
219,Aproc_irq_aproc
220,postman_DIRECTINT5
221,SATA_irq_sata
222,SDDomain_ADMAC2
223,HDMAC0_IntrReq3
224,EDOMAIN_SYNGEN_2_B
225,EDOMAIN_EDMAC_1_WR_SS0
226,EDOMAIN_ORCA_1
227,EDOMAIN_EDMAC_DAF_RD_M0
228,EDOMAIN_WEABER1
229,(reserved)
230,SYNC_irq_inte
231,Camif
232,Camif
233,TMU_int_icapch1
234,INTC_XINT *IRQEXT
235,Aproc_irq_aproc
236,postman_DIRECTINT6
237,PCIe_irq_pcie
238,SDDomain_SDCON0
239,HDMAC0_IntrReq4
240,EDOMAIN_SYNGEN_3_B
241,EDOMAIN_EDMAC_1_WR_SS1
242,EDOMAIN_ORCA_2
243,EDOMAIN_EDMAC_DAF_RD_S0
244,EDOMAIN_WEABER2
245,(reserved)
246,SYNC_irq_inte_st1
247,Camif
248,Camif
249,TMU_int_icapch2
250,INTC_XINT *IRQEXT
251,Aproc_irq_aproc
252,postman_DIRECTINT7
253,PCIe_irq_pcie
254,SDDomain_SDCON1
255,HDMAC0_IntrReq5
256,EDOMAIN_SYNGEN_4_B
257,EDOMAIN_EDMAC_1_WR_SS2
258,EDOMAIN_ORCA_3
259,EDOMAIN_EDMAC_DAF_RD_S1
260,EDOMAIN_HISTORY
261,(reserved)
262,SYNC_-
263,SSIO_SSIOINT
264,Camif
265,TMU_int_icapch3
266,INTC_XINT *IRQEXT
267,Aproc_irq_aproc
268,cclime_msgcom_int0
269,PCIe_irq_pcie
270,SDDomain_SDCON2
271,HDMAC0_IntrReq6
272,EDOMAIN_SYNGEN_STP_B
273,EDOMAIN_EDMAC_1_WR_SS3
274,EDOMAIN_ORCA_4
275,EDOMAIN_EDMAC_MAP_RD_S0
276,EDOMAIN_HISTORY2_1
277,(reserved)
278,SYNC_-
279,SIO0_SIO0INT
280,Camif
281,TMU_int_icapch4
282,INTC_XINT *IRQEXT
283,Aproc_irq_aproc
284,cclime_msgcom_int1
285,UHS2_irq_uhs2
286,XDMAC_XDMAC_0
287,HDMAC0_IntrReq7
288,EDOMAIN_SYNGEN_FRM_B
289,EDOMAIN_EDMAC_1_WR_SS4
290,EDOMAIN_ORCA_5
291,EDOMAIN_EDMAC_5_RD_M0
292,EDOMAIN_HISTORY2_2
293,(reserved)
294,SYNC_-
295,SIO1_SIO1INT
296,Camif
297,TMU_int_icapch5
298,INTC_XINT *IRQEXT
299,Aproc_irq_aproc
300,cclime_msgcom_int2
301,UHS2_irq_uhs2
302,XDMAC_XDMAC_1
303,irq_mdomain_i2i_0
304,EDOMAIN_HEAD_ERR/ATOMIC_ERR
305,EDOMAIN_EDMAC_1_WR_SS5
306,EDOMAIN_ORCA_6
307,EDOMAIN_EDMAC_5_RD_M1
308,EDOMAIN_HISTORY2_3
309,(reserved)
310,SYNC_-
311,SIO2_SIO2INT
312,Camif
313,TMU_int_icapch6
314,INTC_XINT *IRQEXT
315,Aproc_irq_aproc
316,cclime_msgcom_int3
317,USB_hibiki_h
318,XDMAC_XDMAC_2
319,irq_mdomain_i2i_1
320,EDOMAIN_HEAD_ERR2
321,EDOMAIN_EDMAC_2_WR_M0
322,EDOMAIN_ORCA_7
323,EDOMAIN_EDMAC_5_RD_S0
324,EDOMAIN_HISTORY2_4
325,(reserved)
326,SYNC_irq_lss
327,SIO3_SIO3INT
328,Camif
329,TMU_int_icapch7
330,INTC_XINT *IRQEXT
331,adomain_xmon0
332,cclime_msgcom_int4
333,USB_hibiki_d
334,XDMAC_XDMAC_3
335,irq_mdomain_i2i_2
336,EDOMAIN_HEAD_ERR3
337,EDOMAIN_EDMAC_2_WR_S0
338,EDOMAIN_ORCA_8
339,EDOMAIN_EDMAC_5_RD_SS0
340,EDOMAIN_BIKING
341,TSENS_irq_tsens
342,SYNC_irq_lss_st1
343,SIO4_SIO4INT
344,Camif
345,TMU_int_icapch8
346,INTC_XINT *IRQEXT
347,adomain_xmon1
348,cclime_msgcom_int5
349,UART0 RX_IntReqRx
350,DSI_irq_dsi
351,irq_mdomain_a2i_cclime
352,EDOMAIN_HEAD_ERR4
353,EDOMAIN_EDMAC_2_WR_SS0
354,EDOMAIN_ORCA_9
355,EDOMAIN_EDMAC_5_RD_SS1
356,EDOMAIN_CAPTAIN
357,XDMAC_XDMAC_ABORT
358,SYNC_vi_out0
359,SIO5_SIO5INT
360,Camif
361,TMU_int_icapch9
362,INCT_XINT *IRQEXT
363,adomain_xmon2
364,cclime_msgcom_int6
365,UART0 TX_IntReqTx
366,HDMI_irq_hdmi
367,SROMC0_oIRQ_TX
368,EDOMAIN_HEAD_ERR5
369,EDOMAIN_EDMAC_3_WR_M0
370,EDOMAIN_SWAN_GV_END
371,EDOMAIN_EDMAC_5_RD_SS2
372,EDOMAIN_OPTI0
373,SYNC_vi_out13
374,SYNC_vi_out1
375,SIO6_SIO6INT
376,mario_mario
377,TMU_int_icapch10
378,INTC_XINT *IRQEXT
379,adomain_xmon3
380,cclime_msgcom_int7
381,UART1 RX_IntReqRx
382,HDMI_irq_hdmi
383,SROMC0_oIRQ_RX
384,EDOMAIN_HEAD_ERR6
385,EDOMAIN_EDMAC_3_WR_S0
386,EDOMAIN_PLANET_WR_0
387,EDOMAIN_EDMAC_6_RD_S0
388,EDOMAIN_OPTI1
389,SYNC_vi_out14
390,SYNC_vi_out2
391,SIO7_SIO7INT
392,mario_mario
393,TMU_int_icapch11
394,INTC_XINT *IRQEXT
395,cclime_citron_int
396,cclime_sdcon_int
397,UART1 TX_IntReqTx
398,PMU_irq_pmu
399,SROMC0_oIRQ_FAULT
400,EDOMAIN_SAP1
401,EDOMAIN_EDMAC_3_WR_SS0
402,EDOMAIN_PLANET_WR_1
403,EDOMAIN_EDMAC_6_RD_S1
404,EDOMAIN_DAFIGARO
405,SYNC_vi_out15
406,SYNC_vi_out3
407,swimmy_irq_sitter
408,mario_mario
409,TMU_INT_SWA_ONLY
410,INTC_XINT *IRQEXT
411,cclime_tdmac0_int
412,cclime_others_int
413,UART2 RX_IntReqRx
414,HARB_harbInt
415,SROMC0_oERR_COLLECT
416,EDOMAIN_SAP2
417,EDOMAIN_EDMAC_DAF_WR_S0
418,EDOMAIN_PLANET_RD_0
419,EDOMAIN_EDMAC_6_RD_SS0
420,EDOMAIN_EDMAC_6_RD_SS5
421,SYNC_irq_intvi5
422,SYNC_vi_out4
423,swimmy_irq_endev
424,mario_mario
425,TMU_INT_SWB_ONLY
426,INCT_XINT *IRQEXT
427,cclime_tdmac1_int
428,cclime_slotb_sddat1_int *IRQEXT
429,UART2 TX_IntReqTx
430,RSTGEN_WDTINT
431,SROMC1_oIRQ_TX
432,EDOMAIN_SAP3
433,EDOMAIN_EDMAC_MAP_WR_SS0
434,EDOMAIN_PLANET_RD_1
435,EDOMAIN_EDMAC_6_RD_SS1
436,EDOMAIN_EDMAC_6_RD_SS6
437,dolphin
438,SYNC_vi_out5
439,swimmy_irq_sven
440,mario_mario
441,TMU_INT_SWC_ONLY
442,INTC_XINT *IRQEXT
443,cclime_tdmac2_int
444,cclime_slotd_sddat1_int *IRQEXT
445,I2C0_TIRQ
446,I2C1_TIRQ
447,SROMC1_oIRQ_RX
448,EDOMAIN_ATOMIC_LIP
449,EDOMAIN_EDMAC_MAP_WR_SS1
450,EDOMAIN_JP52
451,EDOMAIN_EDMAC_6_RD_SS2
452,EDOMAIN_EDMAC_6_RD_SS7
453,dolphin
454,SYNC_vi_out6
455,ALGS_irq_algs
456,mario_mario
457,TMU_INT_SWD_ONLY
458,INTC_IRQ_soft_out*ASYMMETRIC
459,cclime_tdmac3_int
460,(reserved)
461,I2C0_RIRQ
462,I2C1_RIRQ
463,SROMC1_oIRQ_FAULT
464,EDOMAIN_PENTA
465,EDOMAIN_EDMAC_5_WR_M0
466,EDOMAIN_EDMAC_OPERA_WR
467,EDOMAIN_EDMAC_6_RD_SS3
468,EDOMAIN_EDMAC_DAN_RD
469,dolphin
470,int_tm_misc_cpu_handshake0*ASYMMETRIC
471,ALGS_irq_algs
472,mario_mario
473,irq_mcpu_SCUEVABORT *IRQEXT
474,irq_mcpu_SLVERRINTR
475,irq_mcpu
476,(reserved)
477,I2C0_SIRQ
478,I2C1_SIRQ
479,SROMC1_oERR_COLLECT
480,EDOMAIN_SANTA
481,EDOMAIN_EDMAC_5_WR_S0
482,EDOMAIN_EDMAC_OPERA_RD
483,EDOMAIN_EDMAC_6_RD_SS4
484,EDOMAIN_EDMAC_7_RD_S0
485,dolphin
486,int_tm_misc_cpu_handshake1*ASYMMETRIC
487,GLDA_irq_glda
488,mario_mario
489,irq_mcpu_DECERRINTR
490,irq_mcpu_L2CCINTR
491,irq_mcpu
492,MONI_moniout(0)*IRQEXT
493,MONI_moniout(1)*IRQEXT
494,MONI_moniout(2)*IRQEXT
495,MONI_moniout(3)*IRQEXT
496,INTC_ANDINT(0)*ASYMMETRIC
497,INTC_ANDINT(1)*ASYMMETRIC
498,INTC_ANDINT(2)*ASYMMETRIC
499,INTC_ANDINT(3)*ASYMMETRIC
500,INTC_ANDINT(4)*ASYMMETRIC
501,INTC_ANDINT(5)*ASYMMETRIC
502,DEBSIO
503,XIMR_irq_ximr
504,mario_mario
505,irq_mcpu_ECNTRINTR
506,INTC_ANDINT(0)*ASYMMETRIC
507,INTC_ANDINT(1)*ASYMMETRIC
508,INTC_ANDINT(2)*ASYMMETRIC
509,INTC_ANDINT(3)*ASYMMETRIC
510,INTC_ANDINT(4)*ASYMMETRIC
511,INTC_ANDINT(5)*ASYMMETRIC
512,GIC_SGI(0)
513,GIC_SGI(1)
514,GIC_SGI(2)
515,GIC_SGI(3)
516,GIC_SGI(4)
517,GIC_SGI(5)
518,GIC_SGI(6)
519,GIC_SGI(7)
520,GIC_SGI(8)
521,GIC_SGI(9)
522,GIC_scheduling
523,GIC_timer
524,GIC_suspend
525,GIC_SGI(13)
526,GIC_SGI(14)
527,GIC_SGI(15)
528,GIC_PPI(16)
529,GIC_PPI(17)
530,GIC_PPI(18)
531,GIC_PPI(19)
532,GIC_PPI(20)
533,GIC_PPI(21)
534,GIC_PPI(22)
535,GIC_PPI(23)
536,GIC_PPI(24)
537,GIC_PPI(25)
538,GIC_PPI(26)
539,GIC_GlobalTimer
540,GIC_LegacyFiq
541,GIC_PrivateTimer
542,GIC_WatchdogTimer
543,GIC_LegacyIrq
544,GIC_MariusIntc
545,GIC_OmarIntc
546,GIC_SPI(34)
547,GIC_SPI(35)
548,GIC_SPI(36)
549,GIC_SPI(37)
550,GIC_SPI(38)
551,GIC_SPI(39)
552,GIC_SPI(40)
553,GIC_SPI(41)
554,GIC_SPI(42)
555,GIC_SPI(43)
556,GIC_SPI(44)
557,GIC_SPI(45)
558,GIC_SPI(46)
559,GIC_SPI(47)
560,GIC_SPI(48)
561,GIC_SPI(49)
562,GIC_SPI(50)
563,GIC_SPI(51)
564,GIC_SPI(52)
565,GIC_SPI(53)
566,GIC_SPI(54)
567,GIC_SPI(55)
568,GIC_SPI(56)
569,GIC_SPI(57)
570,GIC_SPI(58)
571,GIC_SPI(59)
572,GIC_SPI(60)
573,GIC_SPI(61)
574,GIC_SPI(62)
575,GIC_SPI(63)
<=-=-=- Vector End -=-=-=>

We do now know the meaning of all interrupt sources. This should help to improve qemu support. Vector table is the same on R and M50 so I assue that this table is valid for all DIGIC 8 models.

I have created a canon basic script which saves the interrupt names to SD card and can easily be adjusted for other models. Vectors are stored as hex instead of decimal here:

Code: [Select]
'Get RP Interrupt Vector Table

dim pIvt_table_1 = 0x1ba48
dim vector1_len = 0x200

dim pIvt_table_2 = 0x1c3ec
dim vector2_len = 0x40

private sub write_table(hFile, pVectorTable, startVector, numElements)
  isrVector = startVector

  do while isrVector < numElements
    ppIrqName = pVectorTable + isrVector * 4
    WriteFileString(hFile, "0x%03X: %s\n", isrVector, *ppIrqName)

    isrVector = isrVector + 1
  loop
end sub

private sub save_ivt(fileName)
  RemoveFile(fileName)

  hFile = OpenFileCREAT(fileName)
  CloseFile(hFile)

  hFile = OpenFileWR(fileName)

  write_table(hFile, pIvt_table_1, 0, vector1_len)
  write_table(hFile, pIvt_table_2, vector1_len, vector2_len)

  CloseFile(hFile)
end sub

private sub Initialize()
  save_ivt("B:/RP_IVT.TXT")
end sub

Output on RP is:
Code: [Select]
0x000: -noise-
0x001: EDOMAIN_OPERA_OPEKICK0
0x002: EDOMAIN_EDMAC_5_WR_S1
0x003: EDOMAIN_EDMAC_1_RD_L0
0x004: EDOMAIN_VITON
0x005: EDOMAIN_OPERA0
0x006: SYNC_irq_intb60v
0x007: SYNC_vi_out7
0x008: TMU_int_SWA
0x009: TMU_int_pulc
0x00A: INTC_XINT *IRQEXT
0x00B: TCU_T0OUT *IRQEXT
0x00C: postman_RCVINT0
0x00D: postman_FIFOINT0
0x00E: Eeko_TIMER_OC0_INT*ASYMMETRIC
0x00F: Eeko_TIMER_IC0_INT*ASYMMETRIC
0x010: EDOMAIN_SYNGEN_1
0x011: EDOMAIN_OPERA_OPEKICK1
0x012: EDOMAIN_EDMAC_6_WR_S0
0x013: EDOMAIN_EDMAC_1_RD_M0
0x014: EDOMAIN_AFFINE
0x015: EDOMAIN_OPERA_ERR0
0x016: SYNC_irq_intb59v
0x017: SYNC_vi_out8
0x018: TMU_int_SWB
0x019: TMU_int_occh0SP
0x01A: INTC_XINT *IRQEXT
0x01B: TCU_T1OUT *IRQEXT
0x01C: postman_RCVINT1
0x01D: postman_FIFOINT1
0x01E: Eeko_TIMER_OC1_INT*ASYMMETRIC
0x01F: Eeko_TIMER_IC1_INT*ASYMMETRIC
0x020: EDOMAIN_SYNGEN_2
0x021: EDOMAIN_OPERA_OPEKICK2
0x022: EDOMAIN_EDMAC_6_WR_SS0
0x023: EDOMAIN_EDMAC_1_RD_S0
0x024: EDOMAIN_AFFINE_OVR_ERR
0x025: EDOMAIN_OPERA_ABORT0
0x026: SYNC_irq_intb50v
0x027: SYNC_vi_out9
0x028: TMU_int_ocall
0x029: TMU_int_occh0EP
0x02A: INTC_XINT *IRQEXT
0x02B: TCU_T2OUT *IRQEXT
0x02C: postman_RCVINT2
0x02D: postman_FIFOINT2
0x02E: Eeko_TIMER_OC2_INT*ASYMMETRIC
0x02F: Eeko_TIMER_IC2_INT*ASYMMETRIC
0x030: EDOMAIN_SYNGEN_3
0x031: EDOMAIN_OPERA_OPEKICK3
0x032: EDOMAIN_EDMAC_6_WR_SS1
0x033: EDOMAIN_EDMAC_1_RD_S1
0x034: EDOMAIN_SARIDON
0x035: EDOMAIN_OPERA1
0x036: SYNC_irq_intb49v
0x037: SYNC_vi_out10
0x038: TMU_int_pulgenCEI
0x039: TMU_int_occh1SP
0x03A: INTC_XINT *IRQEXT
0x03B: TCU_T3OUT *IRQEXT
0x03C: postman_RCVINT3
0x03D: postman_FIFOINT3
0x03E: Eeko_TIMER_OC3_INT*ASYMMETRIC
0x03F: Eeko_TIMER_IC3_INT*ASYMMETRIC
0x040: EDOMAIN_SYNGEN_4
0x041: EDOMAIN_OPERA_OPEKICK4
0x042: EDOMAIN_EDMAC_6_WR_SS2
0x043: EDOMAIN_EDMAC_1_RD_SS0
0x044: EDOMAIN_KURABO
0x045: EDOMAIN_OPERA_ERR1
0x046: SYNC_irq_intl60v
0x047: SYNC_vi_out11
0x048: TMU_int_icapCE1
0x049: TMU_int_occh1EP
0x04A: INTC_XINT *IRQEXT
0x04B: TCU_T4OUT *IRQEXT
0x04C: postman_RCVINT4
0x04D: postman_FIFOINT4
0x04E: Eeko_TIMER_OC4_INT*ASYMMETRIC
0x04F: Eeko_TIMER_IC4_INT*ASYMMETRIC
0x050: EDOMAIN_SYNGEN_STP
0x051: EDOMAIN_OPERA_OPEKICK5
0x052: EDOMAIN_EDMAC_6_WR_SS3
0x053: EDOMAIN_EDMAC_1_RD_SS1
0x054: EDOMAIN_MESSI
0x055: EDOMAIN_OPERA_ABORT1
0x056: SYNC_irq_intl60v_st1
0x057: SYNC_irq_intvi4
0x058: TMU_pulc_ch0
0x059: TMU_int_occh2SP
0x05A: INTC_XINT *IRQEXT
0x05B: TCU_T5OUT *IRQEXT
0x05C: postman_RCVINT5
0x05D: postman_FIFOINT5
0x05E: Eeko_TIMER_OC5_INT*ASYMMETRIC
0x05F: Eeko_TIMER_IC5_INT*ASYMMETRIC
0x060: EDOMAIN_SYNGEN_FRM
0x061: EDOMAIN_OPERA_OPEKICK6
0x062: EDOMAIN_EDMAC_6_WR_SS4
0x063: EDOMAIN_EDMAC_1_RD_SS2
0x064: EDOMAIN_DANCING_FEN
0x065: EDOMAIN_HAIDI_PNL_WR
0x066: SYNC_irq_intl59v
0x067: SYNC_irq_vi4_set_1
0x068: TMU_pulc_ch1
0x069: TMU_int_occh2EP
0x06A: INTC_XINT *IRQEXT
0x06B: TCU_IPCOUT4
0x06C: postman_RCVINT6
0x06D: postman_FIFOINT6
0x06E: Eeko_TIMER_OC6_INT*ASYMMETRIC
0x06F: Eeko_TIMER_IC6_INT*ASYMMETRIC
0x070: EDOMAIN_SYNGEN_1_A
0x071: EDOMAIN_EDMAC_1_WR_L0
0x072: EDOMAIN_EDMAC_DAN_WR
0x073: EDOMAIN_EDMAC_1_RD_SS3
0x074: EDOMAIN_DANCING_SURF
0x075: EDOMAIN_HAIDI_LINE_WR
0x076: SYNC_irq_intl59v_st1
0x077: SYNC_irq_vi4_set_2
0x078: TMU_pulc_ch2
0x079: TMU_int_occh3SP
0x07A: INTC_XINT *IRQEXT
0x07B: TCU_T4F_INT
0x07C: postman_RCVINT7
0x07D: postman_FIFOINT7
0x07E: Eeko_TIMER_OC7_INT*ASYMMETRIC
0x07F: Eeko_TIMER_IC7_INT*ASYMMETRIC
0x080: EDOMAIN_SYNGEN_2_A
0x081: EDOMAIN_EDMAC_1_WR_M0
0x082: EDOMAIN_EDMAC_7_WR_S0
0x083: EDOMAIN_EDMAC_2_RD_M0
0x084: EDOMAIN_DANCING_RACI
0x085: EDOMAIN_SHREK
0x086: SYNC_irq_intl50v
0x087: SYNC_irq_vi4_set_3
0x088: TMU_pulc_ch3
0x089: TMU_int_occh3EP
0x08A: INTC_XINT *IRQEXT
0x08B: TCU_IPCOUT5
0x08C: postman_DIRECTINT0
0x08D: postman_Semaphore0
0x08E: Eeko_TIMER_ICOC_OC0INT*ASYMMETRIC
0x08F: Eeko_TIMER_ICOC_IC0INT*ASYMMETRIC
0x090: EDOMAIN_SYNGEN_3_A
0x091: EDOMAIN_EDMAC_1_WR_M1
0x092: EDOMAIN_EDMAC_7_WR_S1
0x093: EDOMAIN_EDMAC_2_RD_S0
0x094: EDOMAIN_WOMBAT_INTEG
0x095: EDOMAIN_SUSAN
0x096: SYNC_irq_intl50v_st1
0x097: SYNC_irq_intvi4b
0x098: Camif
0x099: TMU_int_occh4SP
0x09A: INTC_XINT *IRQEXT
0x09B: TCU_T5F_INT
0x09C: postman_DIRECTINT1
0x09D: postman_Semaphore1
0x09E: Eeko_TIMER_ICOC_OC1INT*ASYMMETRIC
0x09F: Eeko_TIMER_ICOC_IC1INT*ASYMMETRIC
0x0A0: EDOMAIN_SYNGEN_4_A
0x0A1: EDOMAIN_EDMAC_1_WR_M2
0x0A2: EDOMAIN_EDMAC_7_WR_SS0
0x0A3: EDOMAIN_EDMAC_2_RD_SS0
0x0A4: EDOMAIN_WOMBAT_BLOCK
0x0A5: EDOMAIN_OHYITG
0x0A6: SYNC_irq_intlssdv
0x0A7: SYNC_irq_vi4b_set_1
0x0A8: Camif
0x0A9: TMU_int_occh4EP
0x0AA: INTC_XINT *IRQEXT
0x0AB: Aproc_irq_aproc
0x0AC: postman_DIRECTINT2
0x0AD: postman_Semaphore2
0x0AE: rem_REM_INT
0x0AF: zico_timer_irq
0x0B0: EDOMAIN_SYNGEN_STP_A
0x0B1: EDOMAIN_EDMAC_1_WR_M3
0x0B2: EDOMAIN_EDMAC_ATO_WR_SS0
0x0B3: EDOMAIN_EDMAC_3_RD_M0
0x0B4: EDOMAIN_WOMBAT_AE
0x0B5: EDOMAIN_HIP
0x0B6: SYNC_irq_intlssdv_st1
0x0B7: SYNC_irq_vi4b_set_2
0x0B8: Camif
0x0B9: TMU_int_occh5SP
0x0BA: INTC_XINT *IRQEXT
0x0BB: Aproc_irq_aproc
0x0BC: postman_DIRECTINT3
0x0BD: postman_Semaphore3
0x0BE: SDDomain_ADMAC0
0x0BF: HDMAC0_IntrReq1
0x0C0: EDOMAIN_SYNGEN_FRM_A
0x0C1: EDOMAIN_EDMAC_1_WR_M4
0x0C2: EDOMAIN_EDMAC_ATO_WR_SS1
0x0C3: EDOMAIN_EDMAC_3_RD_OPT_RICH
0x0C4: EDOMAIN_COMBAT_INTEG
0x0C5: EDOMAIN_RASH
0x0C6: SYNC_irq_intp
0x0C7: SYNC_irq_vi4b_set_3
0x0C8: Camif
0x0C9: TMU_int_occh5EP
0x0CA: INTC_XINT *IRQEXT
0x0CB: Aproc_irq_aproc
0x0CC: postman_DIRECTINT4
0x0CD: postman_fifi_err0
0x0CE: SDDomain_ADMAC1
0x0CF: HDMAC0_IntrReq2
0x0D0: EDOMAIN_SYNGEN_1_B
0x0D1: EDOMAIN_EDMAC_1_WR_S0
0x0D2: EDOMAIN_EDMAC_ATO_WR_SS2
0x0D3: EDOMAIN_EDMAC_3_RD_OPT_LITE
0x0D4: EDOMAIN_COMBAT_BLOCK
0x0D5: EDOMAIN_RSHD
0x0D6: SYNC_irq_intp_st1
0x0D7: SYNC_vi_out12
0x0D8: Camif
0x0D9: TMU_int_icapch0
0x0DA: INTC_XINT *IRQEXT
0x0DB: Aproc_irq_aproc
0x0DC: postman_DIRECTINT5
0x0DD: SATA_irq_sata
0x0DE: SDDomain_ADMAC2
0x0DF: HDMAC0_IntrReq3
0x0E0: EDOMAIN_SYNGEN_2_B
0x0E1: EDOMAIN_EDMAC_1_WR_SS0
0x0E2: EDOMAIN_ORCA_1
0x0E3: EDOMAIN_EDMAC_DAF_RD_M0
0x0E4: EDOMAIN_WEABER1
0x0E5: (reserved)
0x0E6: SYNC_irq_inte
0x0E7: Camif
0x0E8: Camif
0x0E9: TMU_int_icapch1
0x0EA: INTC_XINT *IRQEXT
0x0EB: Aproc_irq_aproc
0x0EC: postman_DIRECTINT6
0x0ED: PCIe_irq_pcie
0x0EE: SDDomain_SDCON0
0x0EF: HDMAC0_IntrReq4
0x0F0: EDOMAIN_SYNGEN_3_B
0x0F1: EDOMAIN_EDMAC_1_WR_SS1
0x0F2: EDOMAIN_ORCA_2
0x0F3: EDOMAIN_EDMAC_DAF_RD_S0
0x0F4: EDOMAIN_WEABER2
0x0F5: (reserved)
0x0F6: SYNC_irq_inte_st1
0x0F7: Camif
0x0F8: Camif
0x0F9: TMU_int_icapch2
0x0FA: INTC_XINT *IRQEXT
0x0FB: Aproc_irq_aproc
0x0FC: postman_DIRECTINT7
0x0FD: PCIe_irq_pcie
0x0FE: SDDomain_SDCON1
0x0FF: HDMAC0_IntrReq5
0x100: EDOMAIN_SYNGEN_4_B
0x101: EDOMAIN_EDMAC_1_WR_SS2
0x102: EDOMAIN_ORCA_3
0x103: EDOMAIN_EDMAC_DAF_RD_S1
0x104: EDOMAIN_HISTORY
0x105: (reserved)
0x106: SYNC_-
0x107: SSIO_SSIOINT
0x108: Camif
0x109: TMU_int_icapch3
0x10A: INTC_XINT *IRQEXT
0x10B: Aproc_irq_aproc
0x10C: cclime_msgcom_int0
0x10D: PCIe_irq_pcie
0x10E: SDDomain_SDCON2
0x10F: HDMAC0_IntrReq6
0x110: EDOMAIN_SYNGEN_STP_B
0x111: EDOMAIN_EDMAC_1_WR_SS3
0x112: EDOMAIN_ORCA_4
0x113: EDOMAIN_EDMAC_MAP_RD_S0
0x114: EDOMAIN_HISTORY2_1
0x115: (reserved)
0x116: SYNC_-
0x117: SIO0_SIO0INT
0x118: Camif
0x119: TMU_int_icapch4
0x11A: INTC_XINT *IRQEXT
0x11B: Aproc_irq_aproc
0x11C: cclime_msgcom_int1
0x11D: UHS2_irq_uhs2
0x11E: XDMAC_XDMAC_0
0x11F: HDMAC0_IntrReq7
0x120: EDOMAIN_SYNGEN_FRM_B
0x121: EDOMAIN_EDMAC_1_WR_SS4
0x122: EDOMAIN_ORCA_5
0x123: EDOMAIN_EDMAC_5_RD_M0
0x124: EDOMAIN_HISTORY2_2
0x125: (reserved)
0x126: SYNC_-
0x127: SIO1_SIO1INT
0x128: Camif
0x129: TMU_int_icapch5
0x12A: INTC_XINT *IRQEXT
0x12B: Aproc_irq_aproc
0x12C: cclime_msgcom_int2
0x12D: UHS2_irq_uhs2
0x12E: XDMAC_XDMAC_1
0x12F: irq_mdomain_i2i_0
0x130: EDOMAIN_HEAD_ERR/ATOMIC_ERR
0x131: EDOMAIN_EDMAC_1_WR_SS5
0x132: EDOMAIN_ORCA_6
0x133: EDOMAIN_EDMAC_5_RD_M1
0x134: EDOMAIN_HISTORY2_3
0x135: (reserved)
0x136: SYNC_-
0x137: SIO2_SIO2INT
0x138: Camif
0x139: TMU_int_icapch6
0x13A: INTC_XINT *IRQEXT
0x13B: Aproc_irq_aproc
0x13C: cclime_msgcom_int3
0x13D: USB_hibiki_h
0x13E: XDMAC_XDMAC_2
0x13F: irq_mdomain_i2i_1
0x140: EDOMAIN_HEAD_ERR2
0x141: EDOMAIN_EDMAC_2_WR_M0
0x142: EDOMAIN_ORCA_7
0x143: EDOMAIN_EDMAC_5_RD_S0
0x144: EDOMAIN_HISTORY2_4
0x145: (reserved)
0x146: SYNC_irq_lss
0x147: SIO3_SIO3INT
0x148: Camif
0x149: TMU_int_icapch7
0x14A: INTC_XINT *IRQEXT
0x14B: adomain_xmon0
0x14C: cclime_msgcom_int4
0x14D: USB_hibiki_d
0x14E: XDMAC_XDMAC_3
0x14F: irq_mdomain_i2i_2
0x150: EDOMAIN_HEAD_ERR3
0x151: EDOMAIN_EDMAC_2_WR_S0
0x152: EDOMAIN_ORCA_8
0x153: EDOMAIN_EDMAC_5_RD_SS0
0x154: EDOMAIN_BIKING
0x155: TSENS_irq_tsens
0x156: SYNC_irq_lss_st1
0x157: SIO4_SIO4INT
0x158: Camif
0x159: TMU_int_icapch8
0x15A: INTC_XINT *IRQEXT
0x15B: adomain_xmon1
0x15C: cclime_msgcom_int5
0x15D: UART0 RX_IntReqRx
0x15E: DSI_irq_dsi
0x15F: irq_mdomain_a2i_cclime
0x160: EDOMAIN_HEAD_ERR4
0x161: EDOMAIN_EDMAC_2_WR_SS0
0x162: EDOMAIN_ORCA_9
0x163: EDOMAIN_EDMAC_5_RD_SS1
0x164: EDOMAIN_CAPTAIN
0x165: XDMAC_XDMAC_ABORT
0x166: SYNC_vi_out0
0x167: SIO5_SIO5INT
0x168: Camif
0x169: TMU_int_icapch9
0x16A: INCT_XINT *IRQEXT
0x16B: adomain_xmon2
0x16C: cclime_msgcom_int6
0x16D: UART0 TX_IntReqTx
0x16E: HDMI_irq_hdmi
0x16F: SROMC0_oIRQ_TX
0x170: EDOMAIN_HEAD_ERR5
0x171: EDOMAIN_EDMAC_3_WR_M0
0x172: EDOMAIN_SWAN_GV_END
0x173: EDOMAIN_EDMAC_5_RD_SS2
0x174: EDOMAIN_OPTI0
0x175: SYNC_vi_out13
0x176: SYNC_vi_out1
0x177: SIO6_SIO6INT
0x178: mario_mario
0x179: TMU_int_icapch10
0x17A: INTC_XINT *IRQEXT
0x17B: adomain_xmon3
0x17C: cclime_msgcom_int7
0x17D: UART1 RX_IntReqRx
0x17E: HDMI_irq_hdmi
0x17F: SROMC0_oIRQ_RX
0x180: EDOMAIN_HEAD_ERR6
0x181: EDOMAIN_EDMAC_3_WR_S0
0x182: EDOMAIN_PLANET_WR_0
0x183: EDOMAIN_EDMAC_6_RD_S0
0x184: EDOMAIN_OPTI1
0x185: SYNC_vi_out14
0x186: SYNC_vi_out2
0x187: SIO7_SIO7INT
0x188: mario_mario
0x189: TMU_int_icapch11
0x18A: INTC_XINT *IRQEXT
0x18B: cclime_citron_int
0x18C: cclime_sdcon_int
0x18D: UART1 TX_IntReqTx
0x18E: PMU_irq_pmu
0x18F: SROMC0_oIRQ_FAULT
0x190: EDOMAIN_SAP1
0x191: EDOMAIN_EDMAC_3_WR_SS0
0x192: EDOMAIN_PLANET_WR_1
0x193: EDOMAIN_EDMAC_6_RD_S1
0x194: EDOMAIN_DAFIGARO
0x195: SYNC_vi_out15
0x196: SYNC_vi_out3
0x197: swimmy_irq_sitter
0x198: mario_mario
0x199: TMU_INT_SWA_ONLY
0x19A: INTC_XINT *IRQEXT
0x19B: cclime_tdmac0_int
0x19C: cclime_others_int
0x19D: UART2 RX_IntReqRx
0x19E: HARB_harbInt
0x19F: SROMC0_oERR_COLLECT
0x1A0: EDOMAIN_SAP2
0x1A1: EDOMAIN_EDMAC_DAF_WR_S0
0x1A2: EDOMAIN_PLANET_RD_0
0x1A3: EDOMAIN_EDMAC_6_RD_SS0
0x1A4: EDOMAIN_EDMAC_6_RD_SS5
0x1A5: SYNC_irq_intvi5
0x1A6: SYNC_vi_out4
0x1A7: swimmy_irq_endev
0x1A8: mario_mario
0x1A9: TMU_INT_SWB_ONLY
0x1AA: INCT_XINT *IRQEXT
0x1AB: cclime_tdmac1_int
0x1AC: cclime_slotb_sddat1_int *IRQEXT
0x1AD: UART2 TX_IntReqTx
0x1AE: RSTGEN_WDTINT
0x1AF: SROMC1_oIRQ_TX
0x1B0: EDOMAIN_SAP3
0x1B1: EDOMAIN_EDMAC_MAP_WR_SS0
0x1B2: EDOMAIN_PLANET_RD_1
0x1B3: EDOMAIN_EDMAC_6_RD_SS1
0x1B4: EDOMAIN_EDMAC_6_RD_SS6
0x1B5: dolphin
0x1B6: SYNC_vi_out5
0x1B7: swimmy_irq_sven
0x1B8: mario_mario
0x1B9: TMU_INT_SWC_ONLY
0x1BA: INTC_XINT *IRQEXT
0x1BB: cclime_tdmac2_int
0x1BC: cclime_slotd_sddat1_int *IRQEXT
0x1BD: I2C0_TIRQ
0x1BE: I2C1_TIRQ
0x1BF: SROMC1_oIRQ_RX
0x1C0: EDOMAIN_ATOMIC_LIP
0x1C1: EDOMAIN_EDMAC_MAP_WR_SS1
0x1C2: EDOMAIN_JP52
0x1C3: EDOMAIN_EDMAC_6_RD_SS2
0x1C4: EDOMAIN_EDMAC_6_RD_SS7
0x1C5: dolphin
0x1C6: SYNC_vi_out6
0x1C7: ALGS_irq_algs
0x1C8: mario_mario
0x1C9: TMU_INT_SWD_ONLY
0x1CA: INTC_IRQ_soft_out*ASYMMETRIC
0x1CB: cclime_tdmac3_int
0x1CC: (reserved)
0x1CD: I2C0_RIRQ
0x1CE: I2C1_RIRQ
0x1CF: SROMC1_oIRQ_FAULT
0x1D0: EDOMAIN_PENTA
0x1D1: EDOMAIN_EDMAC_5_WR_M0
0x1D2: EDOMAIN_EDMAC_OPERA_WR
0x1D3: EDOMAIN_EDMAC_6_RD_SS3
0x1D4: EDOMAIN_EDMAC_DAN_RD
0x1D5: dolphin
0x1D6: int_tm_misc_cpu_handshake0*ASYMMETRIC
0x1D7: ALGS_irq_algs
0x1D8: mario_mario
0x1D9: irq_mcpu_SCUEVABORT *IRQEXT
0x1DA: irq_mcpu_SLVERRINTR
0x1DB: irq_mcpu
0x1DC: (reserved)
0x1DD: I2C0_SIRQ
0x1DE: I2C1_SIRQ
0x1DF: SROMC1_oERR_COLLECT
0x1E0: EDOMAIN_SANTA
0x1E1: EDOMAIN_EDMAC_5_WR_S0
0x1E2: EDOMAIN_EDMAC_OPERA_RD
0x1E3: EDOMAIN_EDMAC_6_RD_SS4
0x1E4: EDOMAIN_EDMAC_7_RD_S0
0x1E5: dolphin
0x1E6: int_tm_misc_cpu_handshake1*ASYMMETRIC
0x1E7: GLDA_irq_glda
0x1E8: mario_mario
0x1E9: irq_mcpu_DECERRINTR
0x1EA: irq_mcpu_L2CCINTR
0x1EB: irq_mcpu
0x1EC: MONI_moniout(0)*IRQEXT
0x1ED: MONI_moniout(1)*IRQEXT
0x1EE: MONI_moniout(2)*IRQEXT
0x1EF: MONI_moniout(3)*IRQEXT
0x1F0: INTC_ANDINT(0)*ASYMMETRIC
0x1F1: INTC_ANDINT(1)*ASYMMETRIC
0x1F2: INTC_ANDINT(2)*ASYMMETRIC
0x1F3: INTC_ANDINT(3)*ASYMMETRIC
0x1F4: INTC_ANDINT(4)*ASYMMETRIC
0x1F5: INTC_ANDINT(5)*ASYMMETRIC
0x1F6: DEBSIO
0x1F7: XIMR_irq_ximr
0x1F8: mario_mario
0x1F9: irq_mcpu_ECNTRINTR
0x1FA: INTC_ANDINT(0)*ASYMMETRIC
0x1FB: INTC_ANDINT(1)*ASYMMETRIC
0x1FC: INTC_ANDINT(2)*ASYMMETRIC
0x1FD: INTC_ANDINT(3)*ASYMMETRIC
0x1FE: INTC_ANDINT(4)*ASYMMETRIC
0x1FF: INTC_ANDINT(5)*ASYMMETRIC
Title: Re: Canon EOS R / RP
Post by: Corallaro on January 13, 2021, 01:21:58 PM
This Canon Basic script enables silent shutter on RP:
Code: [Select]
private sub Initialize()
    ExecuteEventProcedure("sht_EnableManualSilent")
end sub
Works in M, Av, Tv and P both in single and continuous modes. Works fine with interval timer. Fails with ERR70 in bulb.

Hi sombree
where did you find this command? (sht_EnableManualSilent)
I couldn't find any documentation.
Thanks
Giovanni
Title: Re: Canon EOS R / RP
Post by: kitor on January 13, 2021, 03:30:29 PM
Quote
This Canon Basic script enables silent shutter on RP:

You quoted all the keywords you need to find proper thread on this forum ;)
Title: Re: Canon EOS R / RP
Post by: Corallaro on January 13, 2021, 04:23:23 PM
You quoted all the keywords you need to find proper thread on this forum ;)
Hi
FOUND
Many thanks!