SD980 port

[RaduP]

Ok, I am thinking to start the SD980 port.
I won't have a lot of time to work at it, maybe 10 hours a week or so, and will probably need a lot of help and advice, but I hope to get something working this year.
Anyway, I was wondering, which camera do you think I should use as a reference model thing?

[reyalp]

I'll just repeat my comments at http://chdk.setepontos.com/index.php/topic,3977.0.html

[RaduP]

Great, thanks!

[RaduP]

Ok, now it seems that I hit a dead end.

I have the following values in the makefile.inc:
MEMBASEADDR=0x1900
RESTARTSTART=0x50000
MEMISOSTART=0x153E84
ROMBASEADDR=0xFF810000

I am not sure that MEMISOSTART is right, the documentation on how to find this value is very ambiguous, but I looked at the SX10 firmware, found where it is, then looked at my firmware and found a similar code, so I used the value that I found. If someone else can confirm that, it would be nice.

The my_restart() function looks like this:

Code: [Select]

void __attribute__((noreturn)) my_restart()
{
    void __attribute__((noreturn)) (*copy_and_restart)(char *dst, char *src, long length);
    int i;

*((volatile int *) 0xc0223030) = 0x46; // Turn on LED
for (i=0; i<10000000; i++) // Wait a while
{
    asm volatile ( "nop\n" );
}

    for (i=0; i<(blob_copy_and_reset_size/sizeof(long)); i++){
((long*)(RESTARTSTART))[i] = blob_copy_and_reset[i];
    }

*((volatile int *) 0xc0223030) = 0x46; // Turn on LED
for (i=0; i<100000; i++) // Wait a while
{
    asm volatile ( "nop\n" );
}

    copy_and_restart = (void*)RESTARTSTART;
    copy_and_restart((void*)MEMISOSTART, (char*)blob_chdk_core, blob_chdk_core_size);
}

No LED blinking, camera freezes. I tried both the boot and firmware update methods, same result. Any ideas?

[reyalp]

You can try turning on your LED earlier, in entry.S. Most cameras turn of the SD card (using an MMIO address that must be determined from the firmware dump) and a delay loop there.

You've already built a blinker that works, so it might be productive to compare that with the early stages of the loader.

You can look at the disassembly of your CHDK image, which will appear in loader/<camera>/main.dump
You should be able to clearly see the entry.S code and my_restart. If you have toolchain problems, they may be visible here. You can also look at main.bin, which should be your CHDK image exactly as it will be loaded.

[RaduP]

The problem is, the entry.S of CHDK is totally different than the entry.S of the blinker (which is much bigger).
I did already look at main.bin and I can clearly see the LED blinking code, which is very near the beginning, and I can't see why the code wouldn't get there if the camera starts to actually execute it. There are no conditional jumps or anything, so the execution SHOULD get there.
What exactly is the purpose of turning off the card power? If it's just to support the restart, it shouldn't matter, as my LED blinking code is before the restart thing.

Could it be that for some reason the diskboot.bin and the ps.fi2 are not encoded properly by the toolchain? Would the camera still attempt to run the ps.fi2 if the encoding is not right?

[reyalp]

The problem is, the entry.S of CHDK is totally different than the entry.S of the blinker (which is much bigger).

The MMIO address poked in entry.S could be wrong (and almost certainly is, if you haven't corrected it). As I said before, try turning on the LED in entry.S, or try skipping that code. You say the entry.S of the blinker is much bigger... OK, what does it do ?

Could it be that for some reason the diskboot.bin and the ps.fi2 are not encoded properly by the toolchain? Would the camera still attempt to run the ps.fi2 if the encoding is not right?

I'm fairly sure that the camera won't load an incorrectly encoded FI2, but not 100% certain.

You know how your blinker is encoded right ? Figure out if your CHDK image is encoded in the same way.

For diskboot, setting NEED_ENCODED_DISKBOOT=3 in your makefile.inc should use the right diskboot encoding for your camera (assuming you are working from the latest SVN) but obviously I haven't tested that.

[RaduP]

Ok, got the SOB to work
So.. NEED_ENCODED_DISKBOOT needs to be removed.
The the diskboot.bin needs to be transformed into a ps.fi2 with the fi2encdec tool.
Afterwards, I can use the firmware update method and it works (previously it didn't, if I had NEED_ENCODED_DISKBOOT set as 1 or 2). However, the diskboot.bin method does not work, as expected.

I use a 3 weeks old SVN, and the only valid methods for NEED_ENCODED_DISKBOOT are 1 and 2.

[reyalp]

Ok, got the SOB to work
So.. NEED_ENCODED_DISKBOOT needs to be removed.
The the diskboot.bin needs to be transformed into a ps.fi2 with the fi2encdec tool.
Afterwards, I can use the firmware update method and it works (previously it didn't, if I had NEED_ENCODED_DISKBOOT set as 1 or 2). However, the diskboot.bin method does not work, as expected.

You've broken something horribly in the makefiles then, since the FI2 is normally made from the unencoded main.bin, not the encoded diskboot.bin.

I use a 3 weeks old SVN, and the only valid methods for NEED_ENCODED_DISKBOOT are 1 and 2.

[RaduP]

From looking at the makefile, you have to explicitly enable the FI2, and you need some keys that I didn't understand how to get (yes, I did read the thread, but maybe I am too tired).
And I am not making the FI2 with the makefile, I am making it with a bat that I also used with the blinker. But it is made from the diskboot.bin

[reyalp]

From looking at the makefile, you have to explicitly enable the FI2, and you need some keys that I didn't understand how to get (yes, I did read the thread, but maybe I am too tired).

Then how are you building your FI2

If you are using some other program after the fact, built it from main.bin (in loader/<camera>) rather than diskboot.

I would BTW suggest keeping your SVN up to date. It will make merging much easier. Also, it would be nice to know if the new encoding is correct for diskboot.

[RaduP]

I am using ewavr's program from here: http://chdk.setepontos.com/index.php/topic,2995.msg28164.html#msg28164
It converts unencoded diskboot.bins to ps.fi2
I will go to bed now, and will update the code from the latest svn tarball. I don't think keeping the code up to date is an issue so far, so long as there are not many hacks such as defining camera specific stuff in kbd.c
Will also test the new encryption and will let you know how it works.

[fe50]

And I am not making the FI2 with the makefile, I am making it with a bat that I also used with the blinker. But it is made from the diskboot.bin

So i guess you also use an old version of encoder, without support for the new NEED_ENCODED_DISKBOOT=3 option...e.g. based upon my old SX10 blinker archive which is from december 2008, with the old encoder ...

[RaduP]

So i guess you also use an old version of encoder, without support for the new NEED_ENCODED_DISKBOOT=3 option...e.g. based upon my old SX10 blinker archive which is from december 2008, with the old encoder ...

Ok, now I am totally confused :/
If my SVN is 3 weeks old, then why isn't something that was made in December last year in there?

[RaduP]

The bootdisk.bin encoded with the new tool, NEED_ENCODED_DISKBOOT=3 works, firmware starts. Thanks!