Messages

1

Camera-specific Development / Re: Canon 500D / T1i

« on: August 13, 2018, 04:54:05 AM »

Hi @dfort

about the api_test.lua tests, really hangs the 500D. Not related to these Stubs.

But...check this script. It runs same functions that hangs on api_test. (Setting ISO and Enabling LiveView)
Runs fine....no hangs !! Tested on 500D fw111:

Code: [Select]

-- Simple 500d test script.

require("keys")

--printf
function printf(...)
    io.write(string.format(...))
end

function main()
    menu.close()
    console.show()

    printf("Camera    : %s (%s) %s\n", camera.model, camera.model_short, camera.firmware)
    printf("Lens      : %s\n", lens.name)
    printf("Shoot mode: %s\n", camera.mode)
    printf("ISO       : %s (raw %s, %s, apex %s)\n", camera.iso, camera.iso.raw, camera.iso.value, camera.iso.apex)

    printf("Setting ISO 800\n")
    camera.iso.value = 800
    printf("ISO       : %s (raw %s, %s, apex %s)\n", camera.iso, camera.iso.raw, camera.iso.value, camera.iso.apex)

    printf("Press any key to test LiveView...\n")
    key.wait()

    if lv.enabled then
        printf("LiveView is running; stopping...\n")
        lv.stop()
        msleep(2000)
    end

    printf("Starting LiveView...\n")
    lv.start()

    msleep(5000)
    printf("Stopping LiveView...\n")
    lv.stop()
    msleep(1000)

    printf("Test complete. Press any key to exit...\n")
    key.wait()

    console.hide()
end

keymenu = menu.new
{
    name   = "500D tests",
    help   = "Some tests on 500D",
    select = function(this) task.create(main) end,
}






I have no idea why the api_test.lua hangs, and this script works.
Successfully sets ISO to 800 and enabled LiveView.

So, I think the 500D is ready for version 112.
Please not forget to update these new Stubs. They aren't related to these tests, but present in version 112.

And, If possible check my patch about "SoundDevice\SoundDevice_CODEC.c" crash. 
Now My 500D is stable, no more crash while recording movies:

Code: [Select]

--- src/audio-common.orig.c 2018-06-01 17:50:30.343132126 -0300
+++ src/audio-common.c 2018-06-01 18:08:03.743893154 -0300
@@ -308,11 +308,15 @@
     {
         return is_menu_active("Audio");
     }
     else
     {
+        #if defined(CONFIG_500D)
+        return 0;
+        #else
         return is_movie_mode() && do_draw_meters && zebra_should_run() && !get_halfshutter_pressed();
+        #endif
     }
 #else
     return 0;
 #endif
 }
@@ -503,17 +507,20 @@
     int meters_slept_times = 0;
 
     TASK_LOOP
     {
         msleep(MIN_MSLEEP);
-        int meters_sleep_cycles = (DISPLAY_IS_ON ? (50/MIN_MSLEEP) : (500/MIN_MSLEEP));
-        meters_slept_times++;
-        compute_audio_levels(0);
-        compute_audio_levels(1);
-        if(meters_slept_times >= meters_sleep_cycles) {
-            reconfig_audio = audio_meters_step(reconfig_audio);
-            meters_slept_times = 0;
+        if (audio_meters_are_drawn())
+        {
+           int meters_sleep_cycles = (DISPLAY_IS_ON ? (50/MIN_MSLEEP) : (500/MIN_MSLEEP));
+           meters_slept_times++;
+           compute_audio_levels(0);
+           compute_audio_levels(1);
+           if(meters_slept_times >= meters_sleep_cycles) {
+               reconfig_audio = audio_meters_step(reconfig_audio);
+               meters_slept_times = 0;
+           }
         }
     }
 
 }


thanks

2

Camera-specific Development / Re: Canon 500D / T1i

« on: July 16, 2018, 03:51:10 AM »

How did you come up with those addresses?

@dfort
opening 2 simultaneous IDA sessions and comparing each Stub address in 111 and 112
"mvr_config" is not an address, I've noticed a change in old value.

3

Camera-specific Development / Re: Canon 500D / T1i

« on: June 13, 2018, 01:01:08 AM »

Hi @dfort

Thanks for your tip about 500D dumping. I was also searching for new stubs and noticed some changes not present in your stubs.S

update-to-500d112

Code: [Select]

NSTUB(0xFF0234B4,  gui_init_end)
NSTUB(    0x1E8C,  mvr_config)               // please re-check
NSTUB(0xFF33030C,  fsuDecodePartitionTable)

Not sure, I have little experience with this. Can you check please?
Maybe this help your API_TEST.LUA tests.
thanks

4

General Development / Re: Portable ROM dumper

« on: June 01, 2018, 04:50:44 AM »

Got my hands on a 500D and thought I'd try dumping the 1.1.2 firmware but ran into this:

Same issue with 1.1.1. I have used the portable dumper a few times and have never seen this before.

Hi dfort,

sorry for the late reply... I've tried Portable Dumper on my 500D, same screen on booth firmware, even with low capacity card.

5

General Development / Re: A guide to dumping image buffers / VRAM dumps in all modes

« on: April 01, 2018, 05:59:31 PM »

Missing data:
- 500D

Here is:
https://drive.google.com/open?id=1xXMdcUwSyhqKHGIaNTvJUw_1bS3TsQyp
Nightly.2017Dec07.500D111