Messages

I meant that same mechanical sound is hearable when shooting with normal shutter even in other modes than bulb.

Same mechanical movement is hearable when shooting in M (or any other) mode, yet only in bulb camera errors out

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).

This Canon Basic script enables silent shutter on RP:

Code Select Expand

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.

a1ex, is this correct way to load additional binary blob? For example, I want to load "0xFF011868 -> 0x4000     size 0x15F14    at 0xFE0A00DA":

Have you tried adding it to ML_SRC_EXTRA_OBJS in platform/200D.101/Makefile.platform.default? I mean something like this:

Code Select Expand


ML_SRC_EXTRA_OBJS = \
        log-d678.o \
        function_overrides.o \
        vram.o


Or you can try adding vram.o to ML_SRC_REBOOT_OBJ in src/Makefile.src:

Code Select Expand


ifndef ML_SRC_REBOOT_OBJ
ML_SRC_REBOOT_OBJ = reboot.o \
disp_direct.o font_direct.o vram.o \
strlen.o strcmp.o gcc-libgcc.a \
cache.o \
footer.o
endif


Yes, it works
With default "Hello, World!" text position:

Proof of concept using code from font_direct.c and disp_direct.c:

C0000000/20000000 with CONFIG_MARK_UNUSED_MEMORY_AT_STARTUP in PLAY mode with overlay - log
0x80000000/0x80000000|0xC700 with CONFIG_MARK_UNUSED_MEMORY_AT_STARTUP in PLAY mode with overlay - log

Code Select Expand

MEM(0xD2030100) = 2;  /* unsure; 2 or 6 */
MEM(0xD2030104) = 0x20077; /* meaning: we are going to change the bitmap buffer address */
MEM(0xD2030108) =  0x00019018 + offset++; /* address of new bitmap buffer, e.g. "0x00019018 + offset++", or 0x300000, or 0x280000, or 0x2AB000, or something allocated dynamically etc */
gives this when shutter is halfpressed - link to short slow motion clip

Code Select Expand

    while(1)
    {
        MEM(CARD_LED_ADDRESS) = LEDON;
        msleep(500);
        MEM(CARD_LED_ADDRESS) = LEDOFF;
        msleep(500);

        uint32_t * vram1 = (uint32_t *) 0x1901800;
        uint32_t * vram2 = (uint32_t *) 0x1785B00;
        for (int i = 0; i < 540; i++)
        {
            vram1[i + i * 960/2] = 0x46ff465e;
            vram2[i + i * 960/2] = 0x6d216d4b;
        }
    }
gives this - link to the image

Hm, with current tree there is no log when CONFIG_MARK_UNUSED_MEMORY_AT_STARTUP is defined. I double checked with fresh, clean tree.
C0000000/20000000 without CONFIG_MARK_UNUSED_MEMORY_AT_STARTUP defined - log.

I have tried logging 0xD2030108 like this:

Code Select Expand

    DryosDebugMsg(0, 15, "MEM(0xD2030108) =");
    DryosDebugMsg(0, 15, MEM(0xD2030108));
    DryosDebugMsg(0, 15, "MEM(0xD2030108) = %d", MEM(0xD2030108));
but I'm not sure if that worked.

0xC8200008 was logged with this:

Code Select Expand

static void C8200008_log(int times, int delay)
{
    for (int i = 0; i < times; i++)
    {
        DryosDebugMsg(0, 15, "MEM(0xC8200008) %d / %d = %d", i, times, MEM(0xC8200008));
        msleep(delay);
    }
}

Code Select Expand

C8200008_log(100, 20);
I think it worked - you can see C8200008 values in log.

Also I was able to make a full ROM/RAM dump (camera on -> PLAY mode with valid image -> menu) - log.

It works too
With 0x1234 LiveView (both in photo and video mode) screen flashes green with shutter pressed halfway. After that main screen's background changes from black to last LV frame when shutter is pressed halfway. Also LED blinks as it's supposed to
Edit:

It works
from 0xBFE00000, size 0x200000: regular and with exercising
from 0xC0000000, size 0x20000000: regular and with exercising
Btw. camera boots autoexec.bin a little faster than before.

Sure:
0xBFF00000, size 0x100000 - log
Fun fact - with this base and size camera doesn't lock up (i.e. I can take a photo) but main screen doesn't work at all. It's just completely black. Secondary screen still works.

After builiding with -O2 (instead of default -Os) I was able to get some partial logs:
from 0xBFE00000, size 0x200000 - log
from 0xA0000000, size 0x40000000 - camera locks up with Err60, no log is saved.

Edit:
I checked from 0xA0000000, size 0xFFFFFFF - camera doesn't lock up and MMIO log is empty (unused range?).

Few times it didn't work in regular (photo) LiveView - on-screen image was garbled and there was no log. Right now I've tried again and no problem at all, both in photo and video LV (log).

from 0xBFE00000, size 0x200000  - camera locks up with Err70, no log is saved. Edit: sometimes camera locks up with Err70 but led still blinks as it's supposed to.
from 0xEE000000, size 0x1000000 - MMIO log looks empty - log.
from 0xA0000000, size 0x40000000 - camera locks up without any error, no log is saved.

It worked out of box
mmio log without lens
mmio log with lens attached
another one - with a little exercise - took a photo, fiddled with a touchscreen, changed iso etc.

Yep, no crash, just a little longer camera start up
As for CONFIG_80D - you're right, it's defined by the Makefile.

Log made on latest (a706877) commit: log and log2. I've stressed camera a little bit - start to M mode, fiddle a bit with touchscreen, switch to LV and back, switch to movie mode -> record few secs -> back to photo mode, switch to play mode etc.
Btw. I had to define CONFIG_80D in log-d6.h - it's used in log-d6.c but it's not defined anywhere

Link
1 - without DBGDSCR
2 - with DBGDSCR
In all cases I removed disable_caches_region1_ram_d6() from reboot.c to speed up dumping process.

Edit:
3 - with latest changeset (237777f)
4 - with latest changeset and caches disabled

I guess timer has 32 bits - it wrapped shortly after 71 minutes - log. Buffer size was set to 320K, init delay to 4380000 (73 minutes).

Sure - link.
1 - no lens,
2 - with lens,
both with 0xD400000C.

Sorry, I forgot to mention - thats because I've changed init delay to 1.5 seconds.
Logs:
1 - 0xD400000C and 5 sec delay
2 - 0xC0242014 and 5 sec delay

Link
1 - 0xD400000C and %08X>
2 - 0xC0242014 and %08X>
Does it mean that old timer register work?

Edit: Link updated (now from latest changeset).