Messages

I think there was a method to update the AUTOEXEC.BIN file in the card, without having to remove the card from the camera, but it was no longer functional;

Upload to the camera is functional, at least under Linux. And I made download also functional again with A1ex's help.
Wiki page

The write speeds are detailed in their press release for the µSD pendants.

SanDisk upped their Extreme range to 80/50 MB/s read/write:



They plan to ship this month.

Nice comparison!

how to use those

?? it doesn't work when I paste my video link in the middle of it.

You have to use HTTP, not HTTPS.

0 props need to be blocked out or it won't change, just give you the red square. Then you need to change mode to apply it.

I commented out

Code Select Expand


        if (should_run_polling_action(20000, &aux))
        {
set_pic_quality(PICQ_SRAW);
            guess_mem_running = 1;
            guess_free_mem();
//set_pic_quality(PICQ_RAW);
        }

void set_pic_quality(int q)
{
    if (q == -1) return;
    prop_request_change(PROP_PIC_QUALITY, &q, 4);
//    prop_request_change(PROP_PIC_QUALITY2, &q, 4);
//    prop_request_change(PROP_PIC_QUALITY3, &q, 4);
}


and switched between Movie/Night Portrait and P/LV, but always 75 MB.

Ah really, permanant error 70, interesting, that is scary

I just thought "what the heck" and tried

Code Select Expand

        if (should_run_polling_action(20000, &aux))
        {
set_pic_quality(PICQ_SRAW);
            guess_mem_running = 1;
            guess_free_mem();
set_pic_quality(PICQ_RAW);
        }
in debug.c
but still only 75 MB.

Now we need to try to get more Buffer Memory like the other cams, even the 500D has 95, I just tried Raw on my 500D and I get high res then on 550D with no skip.

I already tried to find sourcecode for the sRAW experiments from the past, but couldn't find anything yet. I'm also afraid of the permanent Err70 this seems to provoke.

If you know how to get it on there or pull it or whatever its called, lol

It's actually quite simple and fun (as long as the VCS doesn't start fighting with you ):

• Fork
• hg clone https://bitbucket.org/mk11174/magic-lantern


• Make your changes
• hg commit path/file.c
• Enter commit message
• hg push
• Press Pull request on bitbucket website
• Voilà

I added the Stub for SeekFile to get it going.

Is this available on bitbucket?

Testing 128K...

Wow:

Code Select Expand


sonic@sonic-VGN-Z41WD-B:~/ML/sonic74/magic-lantern/platform/550D.109$ ls -lh autoexec.bin
-rwxrwxr-x 1 sonic sonic 523K Jun  3 12:41 autoexec.bin
sonic@sonic-VGN-Z41WD-B:~/ML/sonic74/magic-lantern/platform/550D.109$ time cat ../../src/ptpcam.txt | ptpcam --chdk
real    0m1.257s


You may need to allocate the buffers with alloc_dma_memory / free_dma_memory, this should fix it.

It works I also thought about this, but saw that only the filename was allocated this way in PTP_CHDK_UploadFile.
Pull requested.

Make them larger too.

Testing 128K...

Never mind, got it

...at least the upload. The download has strange difference patterns. I already tried to shrink BUF_SIZE to 32 bytes, FIO_WriteFile() at the same time (works correct) and msleep(10) after send_data(). Strange things going on with the latter. I wonder what the difference from the current repository to the correctly working version magiclantern-2011Mar11.550d.fw109.AudioMon.PTP.alex.zip is...

Do you have found the disassembly start address of both ROM files ? And what they are ?
Do you have found what is the rom file where there is the stuff we are searching for ? ROM0.BIN or ROM1.BIN ?

Neither of them, I think. I modified debug.dump_rom_task() to dump another ROM2.BIN
Then do

Code Select Expand

./disassemble.pl 0xFF000000 ROM1.BIN

But I didn't investigate further, since xaint has already solved it, hasn't he?

ok: good news: the cache hack is seems to be working, checking now...

Just when I found out how to dump the ROM from the correct address 0xFF010000 X-)

Where might be the source code for it?

Never mind, got it

I actually figured out the dump a few days ago, but could nopt figure out the dissasemble part, I have IDA but looking through that was no help because much of it was garble because I did not have and scripts

I tried the demo version, too (the free version doesn't do ARM). But I missed the map file for remake-elf (the demo does only ELF).

Oh, and to clarify, I know the script is not for IDA, I will look use it with ipython if I am correct?

No, it's just a perl script using the gcc cross compiler tools.

Are you also working on this problem on 550D ?

Yes, but first I want to be able (again) to install my (supposedly many) test builds via USB. I'll have to find Alex's source code for his ptp-ml.c implementation.

are you sure it's an offset (relative address) or perhaps it's an absolute address ?

Each .BIN is 0x0100 0000 = 16 MB long, so:
ROM0.BIN: 0xF000 0000..0xF0FF FFFF
ROM1.BIN: 0xF800 0000..0xF8FF FFFF
I think the #define is absolute.

Where to find the 550D rom disassembled, or where to find the rom dump and how to disassemble it ?

When you run 550D-109.fir, the following happens:

Code Select Expand


    f = FIO_CreateFileEx(CARD_DRIVE "ML/LOGS/ROM0.BIN");
    if (f != (void*) -1)
    {
        bmp_printf(FONT_LARGE, 0, 60, "Writing ROM0");
        FIO_WriteFile(f, (void*) 0xF0000000, 0x01000000);
        FIO_CloseFile(f);
    }
    msleep(200);

    f = FIO_CreateFileEx(CARD_DRIVE "ML/LOGS/ROM1.BIN");
    if (f != (void*) -1)
    {
        bmp_printf(FONT_LARGE, 0, 60, "Writing ROM1");
        FIO_WriteFile(f, (void*) 0xF8000000, 0x01000000);
        FIO_CloseFile(f);
    }


You can disassemle them with disassemble.pl
What I don't understand yet: 1% does for the 600D:

Code Select Expand

#define HIJACK_CACHE_HACK_ALLOCMEM_SIZE_ADDR 0xFF0123E8
But with the offsets from above, I dont't have such high addresses in my ROM?.BIN.dis
It's mirrored.

It was tried months ago... would fail transferring. Loading different bins off the card worked at one point.

Oh, it was already done
And it actually works:

Code Select Expand


sonic@sonic-VGN-Z41WD-B:~/ptp-dir/mweerden-CHDK-5273d12/tools/ptpcam$ ls -lh autoexec.bin
-rwxr-xr-x 1 sonic sonic 453K Mai 31 13:14 autoexec.bin
sonic@sonic-VGN-Z41WD-B:~/ptp-dir/mweerden-CHDK-5273d12/tools/ptpcam$ time echo "upload autoexec.bin B:/ULTEST.BIN" | ./ptpcam --chdk
real    0m18.585s
sonic@sonic-VGN-Z41WD-B:~/ptp-dir/mweerden-CHDK-5273d12/tools/ptpcam$ time echo "download B:/ULTEST.BIN ULTEST.BIN" | ./ptpcam --chdk
real    0m4.162s
sonic@sonic-VGN-Z41WD-B:~/ptp-dir/mweerden-CHDK-5273d12/tools/ptpcam$ diff ULTEST.BIN autoexec.bin
sonic@sonic-VGN-Z41WD-B:~/ptp-dir/mweerden-CHDK-5273d12/tools/ptpcam$


...but only with this autoexec.bin binary from Alex. Where might be the source code for it?

Hello!

Do you developers remove the memory card each time you install your autoexec.bin build?

I want to try to implement the HIJACK_CACHE_HACK_*_SIZE_* boot hack to free memory on the 550D. Since this is still quite obscure to me, I'm afraid I have to install many builds until it works. And since I'm too lazy to remove the SD Card each time, I was wondering if anyone else would be interested in something like

Code Select Expand

ruby contrib/mlusb/write2card.rb platform/550D.109/autoexec.bin autoexec.bin

to transfer a new build via USB to the memory card.
If so, I'd try to implement this. Or are there other ways already?