A2200 IS porting thread - page 44 - DryOS Development - CHDK Forum supplierdeeply

A2200 IS porting thread

  • 515 Replies
  • 142338 Views
Re: A2200 IS porting thread
« Reply #430 on: 03 / August / 2012, 22:10:11 »
Advertisements
It came formatted as fat32, should i reformat?
No - if you are sure its fat32 the reformatting will not change anything.

Quote
also, how do i know if it wrote BOOTDISK on that sector at 0x1E0? through a hex editor? is there any other way to verify?
Look at the screen captures here :  http://chdk.wikia.com/wiki/EOScard.  One says 0x40 beside the string BOOTDISK.  The other says 0x1E0.    You want it to say 0x1E0.

Did you click on the CHDK icon / button in the EOScard window to actually write to the card ?

Quote
I'm on PC. Yes i put it on locked.
So did the camera complaing that the card is "locked" when you start it with the SD card lock switch in the Locked position ?  (indicating that CHDK was not loaded ...)

Ported :   A1200    SD940   G10    Powershot N    G16

Re: A2200 IS porting thread
« Reply #431 on: 04 / August / 2012, 13:25:30 »
I have a 1.00d firmware version, and you?
Is it only in specific menu/operations or random or always?
Same version here. I didn't mean to imply that it is unusable or anything like that. Rev. 1984 is clearly less flickery than ever. I take it that the flickers on camera OSD updates are unfixable--or at least not fixed in other CHDK versions either. Isn't it possible to find every camera OSD update routine and add a hook to refresh the CHDK OSD as well or something? :)

Also, I traced some of my problems to overlapped OSD elements and fixed them. Other than that, the only niggle I currently have is that the splash screen is sometimes black and white and/or flickery.

*

Offline reyalp

  • ******
  • 13502
Re: A2200 IS porting thread
« Reply #432 on: 04 / August / 2012, 16:25:27 »
Isn't it possible to find every camera OSD update routine and add a hook to refresh the CHDK OSD as well or something? :)
Not really. The camera code is (mostly) executed directly from the cameras flash ROM. CHDK hooks a few tasks, by implementing the entire task up to the point we want to override in the CHDK binary (which is loaded in to RAM) We cannot arbitrarily replace all use of a specific function for the whole Canon firmware. We could do that if we actually flashed CHDK into camera ROM, but the risks of bricking cameras would be much much higher. Definitely not worth it for a cosmetic thing like this!

As I said earlier, the amount of flickering varies because the Canon firmware updates more or less frequently in different situations. It's unlikely that anything about CHDK builds actually affect it. There is a define (CAM_DETECT_SCREEN_ERASE) which helps CHDK know when it needs to redraw, but this is currently enabled for all cameras.
Don't forget what the H stands for.

Re: A2200 IS porting thread
« Reply #433 on: 05 / August / 2012, 15:41:58 »
It came formatted as fat32, should i reformat?
No - if you are sure its fat32 the reformatting will not change anything.

Quote
also, how do i know if it wrote BOOTDISK on that sector at 0x1E0? through a hex editor? is there any other way to verify?
Look at the screen captures here :  http://chdk.wikia.com/wiki/EOScard.  One says 0x40 beside the string BOOTDISK.  The other says 0x1E0.    You want it to say 0x1E0.

Did you click on the CHDK icon / button in the EOScard window to actually write to the card ?

Quote
I'm on PC. Yes i put it on locked.
So did the camera complaing that the card is "locked" when you start it with the SD card lock switch in the Locked position ?  (indicating that CHDK was not loaded ...)



ok. i think i had the wrong version of eoscard, i got CHDK loaded.

now.... how do i control the shutter speed? do i load a script from the menu?


*

Offline reyalp

  • ******
  • 13502
Re: A2200 IS porting thread
« Reply #434 on: 05 / August / 2012, 15:51:50 »
Don't forget what the H stands for.

*

Offline nafraf

  • *****
  • 1308
Re: A2200 IS porting thread
« Reply #435 on: 07 / August / 2012, 19:37:21 »
Test of the last source code posted in this forum shows problem of UI Overlay objects wrong colors.  Similar to the problem seen on a2300 porting thread.

These are the missing functions to fix this error.
Code: [Select]
//File:platform/a2200/lib.c
// Functions for PTP Live View system
int vid_get_palette_type()                      { return 3; }
int vid_get_palette_size()                      { return 256 * 4; }

void *vid_get_bitmap_active_buffer()
{
    return (void*)(*(int*)(0x560C+0x18)); //found @ loc_ff912d5c: a2200 100b
}
[\code]

Re: A2200 IS porting thread
« Reply #436 on: 11 / August / 2012, 12:58:44 »
Hello I can not find the item "curves" in the firmware.

Re: A2200 IS porting thread
« Reply #437 on: 11 / August / 2012, 13:44:45 »
Ported :   A1200    SD940   G10    Powershot N    G16


Re: A2200 IS porting thread
« Reply #438 on: 11 / August / 2012, 13:58:46 »
Test of the last source code posted in this forum shows problem of UI Overlay objects wrong colors.  Similar to the problem seen on a2300 porting thread.

These are the missing functions to fix this error.
Code: [Select]
//File:platform/a2200/lib.c
// Functions for PTP Live View system
int vid_get_palette_type()                      { return 3; }
int vid_get_palette_size()                      { return 256 * 4; }

void *vid_get_bitmap_active_buffer()
{
    return (void*)(*(int*)(0x560C+0x18)); //found @ loc_ff912d5c: a2200 100b
}

I updated the source to revision 2079 and implemented the functions above:

(CHDK 1.1.0) Dev branch rev. 2079:

* CHDK-a2200-100b-1.1.0_BETA.zip firmware version 1.00b, use the Card Lock method & copy over the CHDK folder
* CHDK-a2200-100c-1.1.0_BETA.zip firmware version 1.00c, use the Card Lock method & copy over the CHDK folder
* CHDK-a2200-100d-1.1.0_BETA.zip firmware version 1.00d, use the Card Lock method & copy over the CHDK folder

* chdk.a2200_1.1.0.zip source code

Re: A2200 IS porting thread
« Reply #439 on: 14 / August / 2012, 23:39:28 »
Test of the last source code posted in this forum shows problem of UI Overlay objects wrong colors.  Similar to the problem seen on a2300 porting thread.

These are the missing functions to fix this error.
Code: [Select]
//File:platform/a2200/lib.c
// Functions for PTP Live View system
int vid_get_palette_type()                      { return 3; }
int vid_get_palette_size()                      { return 256 * 4; }

void *vid_get_bitmap_active_buffer()
{
    return (void*)(*(int*)(0x560C+0x18)); //found @ loc_ff912d5c: a2200 100b
}

I updated the source to revision 2079 and implemented the functions above:

(CHDK 1.1.0) Dev branch rev. 2079:

* CHDK-a2200-100b-1.1.0_BETA.zip firmware version 1.00b, use the Card Lock method & copy over the CHDK folder
* CHDK-a2200-100c-1.1.0_BETA.zip firmware version 1.00c, use the Card Lock method & copy over the CHDK folder
* CHDK-a2200-100d-1.1.0_BETA.zip firmware version 1.00d, use the Card Lock method & copy over the CHDK folder

* chdk.a2200_1.1.0.zip source code

first off, i just wanna say that you're doing one hell of a job.

but i had a question....

how did you do that time lapse star thing with chdk?

 

Related Topics