A495 porting thread

fvdk

146
Ixus 70 1.01b / 1.02a & Powershot A590is 1.01b

« on: 18 / August / 2010, 11:37:56 »

Advertisements

I just went to a camera shop and made a dump of the A495

http://drop.io/CANON_A495

I had no time to check the firmware version but I think it is 1.00a

Can someone confirm if this dump is OK?

Frans

Logged

c10ud

245

Re: A495 porting thread

« Reply #1 on: 18 / August / 2010, 11:51:59 »

seems fine, DRYOS version 2.3, release #0043

Logged

whoever

280
IXUS950

Re: A495 porting thread

« Reply #2 on: 18 / August / 2010, 12:01:42 »

Quote from: fvdk on 18 / August / 2010, 11:37:56

I had no time to check the firmware version but I think it is 1.00a

Quote from: your dump A495.BIN

Firmware Ver GM1.00D

Edit: Dump starting at 0xFFC00000, I trust.

« Last Edit: 18 / August / 2010, 12:17:31 by whoever »

Logged

fe50

3152
IXUS50 & 860, SX10 Star WARs-Star RAWs

Re: A495 porting thread

« Reply #3 on: 20 / August / 2010, 02:15:47 »

Quote from: fvdk on 18 / August / 2010, 11:37:56

I just went to a camera shop and made a dump of the A495

Quote from: c10ud on 18 / August / 2010, 11:51:59

seems fine, DRYOS version 2.3, release #0043

Quote from: whoever on 18 / August / 2010, 12:01:42

Firmware Ver GM1.00D
Edit: Dump starting at 0xFFC00000, I trust.

--> A495 1.00D dump added to the chdkdumps backup repository ([1]) and updated the wikia.

Logged

-->FIRMWARE DUMPS<-- * Manual * Lua * me

syahmixp

13

Re: A495 porting thread

« Reply #4 on: 20 / October / 2010, 11:59:44 »

Hi, I been porting A495 100d based on A480 for the past few days, now I got the camera and dump the firmware but I found that my firmware version is 100f, so I start porting it again from beginning and got the CHDK bootloader to work.

Next task is to get CHDK splash logo, but I got a few problems with hooking task...
Is there any others who works on this model?

Here firmware dump of my A495 100f: http://www.fileserve.com/file/4ve8Jyj

« Last Edit: 20 / October / 2010, 12:03:25 by syahmixp »

Logged

syahmixp

13

Re: A495 porting thread

« Reply #5 on: 21 / October / 2010, 00:47:47 »

Update, now it display CHDK version but without logo and some keys aren't responding. Going to fix keymap.

Logged

syahmixp

13

Re: A495 porting thread

« Reply #6 on: 21 / October / 2010, 12:56:44 »

Quote from: Johndk

Hiya!

I am so happy that you started on the A495 port. I have the same camera and same firmware version as you.

Tell if there is anything i can help you with, like tedious trail and error work,etc. I dont think it would be a problem for me to set up a build enviroment for this camera.

Hi John,
glad to hear that

the build environment is easy to setup, you just need CHDK-Shell if you are on windows.

For now, all I have done:
loader\
platform\sub\boot.c
platform\sub\capt_seq.c
platform\sub\lib.c
platform\sub\movie_rec.c
platform\sub\stubs_entry_2.S
platform\sub\stubs_min.c
platform\lib.c

Update, CHDK now display logo. After the logo disappear, nothing from CHDK appear like battery indicator, etc... (or does it needed to be enable first?)
I don't know about keymap and have been read entire discussion and posts here: http://chdk.setepontos.com/index.php/topic,4727.0.html

Below is my current keymap and keymask

Code: [Select]

#define KEYS_MASK0 (0x00000000)
#define KEYS_MASK1 (0x00000000)
#define KEYS_MASK2 (0x017005f4)

	//{ 2, KEY_DISPLAY	, 0x00000400 }, // Doesnt exist's?
	{ 2, KEY_RIGHT		, 0x00000004 }, 
	{ 2, KEY_SHOOT_FULL	, 0x00000010 }, 
	{ 2, KEY_SHOOT_HALF	, 0x00000020 }, 
	{ 2, KEY_ZOOM_IN	, 0x00000080 }, 
	{ 2, KEY_ZOOM_OUT	, 0x00000040 },
	{ 2, KEY_SET		, 0x00000100 }, 
	{ 2, KEY_UP			, 0x00100000 }, 
	{ 2, KEY_DOWN		, 0x00200000 }, 
	{ 2, KEY_LEFT		, 0x00400000 }, 
	{ 2, KEY_MENU		, 0x01000000 }, 
    { 0, 0, 0 }

Code: [Select]

DEF(physw_status, 0x2E7F4)

initial val
0:88de0180
1:040000c2
2:0405x1f4

2:xx1xxxxx up
2:xx2xxxxx dn
2:xx4xxxxx left
2:xxxxxxx0 right
2:xxxxx1xx func/set
2:xxxxxxEx full
2:xxxxxxCx half
2:x5xxxxxx menu
2:xxxxxx7x zoom in
2:xxxxxxbx zoom out
playback, cannot retrive yet

I don't know if I set up keymap correctly, need experts to check this. But with this keymap, all keys are responding,
and I still don't know how to call CHDK menu either...? and how CHDK process input key. Also there is no print button in this model...

« Last Edit: 21 / October / 2010, 13:42:28 by syahmixp »

Logged

c10ud

245

Re: A495 porting thread

« Reply #7 on: 21 / October / 2010, 13:08:43 »

i think chdk by default uses KEY_PRINT for changing modes (OSD-ALT), in ixus105 i defined the DISP. key as the print one, i see a495 has a few keys.. maybe KEY_PRINT can be defined as a combination of two different keys? or you should sacrifice the pic/movie mode button..

Logged

syahmixp

13

Re: A495 porting thread

« Reply #8 on: 21 / October / 2010, 13:31:39 »

Hi c10ud, thanks for suggestion, I already tried to assign KEY_PRINT to another key such as up/down/zoom/menu, but doing this makes all button non responsive and splash "busy" text, however the camera still running and didn't freeze. I'll try to do this again.

My idea is to make CHDK menu appear after long press menu button, but need to figure out how to do that...

Logged

syahmixp

13

Re: A495 porting thread

« Reply #9 on: 21 / October / 2010, 20:59:04 »

Update progress:
Now I got everything on display like battery status, time, some bar at the bottom, etc...

I mapped the PRINT button to PLAYBACK button to open CHDK menu, but the menu doesn't appear, instead the exposure(up button) shows and then all the button will be non responsive. Pressing all buttons doesn't do anything except power and mode button. The camera still fine and working and can be turn on/off normally.

There must be something I missed.

« Last Edit: 21 / October / 2010, 22:00:33 by syahmixp »

Logged