ELPH 340 (IXUS 265)

Caefix

srsa_4c

Caefix
😀 Cam arrived with fw 100c.

blackhole

@Caefix
Test build, ixus265_elph340hs-100c

The modemap is completely wrong so all shooting modes should be checked as described here: https://chdk.setepontos.com/d/13151/38

For this camera,set "Propcase / Param data page" to [4].
The numeric ID of current shooting mode is displayed after 49:

ixus265_elph340hs-100c-1.5.0-5456-full.zip

725.25KB

Caefix

🙁 No Entry. CHDK ignored.

blackhole

Caefix
🙁 No Entry. CHDK ignored.

You have to use the autoboot method, with a locked SD card to load CHDK.
See here how to configure an SD card: https://chdk.fandom.com/wiki/Prepare_your_SD_card

Caefix

Apparently I peeked the maybe only not bootable SD- Card from my collection. ( ( ( ( ( ( ( ( ( :lol

Hybrid Auto-------------- 33296
Creative Shot------------ 33297

Auto -------------------- 32768
P------------------------ 32772
Portrait----------------- 32788

Smart Shutter------------ 
Smile-------------------- 33328
Wink Self-Timer---------- 33329
FaceSelf-Timer----------- 33327

HIGHSPEED_BURST---------- 32776
Handheld Night Scene----- 33332
Low Light---------------- 32888
Fish-eye Effect---------- 33330
Miniature Effect--------- 33331
Toy Camera Effect-------- 33334
Monochrome--------------- 33338
Super Vivid-------------- 33325
Poster Effect------------ 33326
Snow--------------------- 32796
Fireworks---------------- 32798
Long Shutter------------- 32774

~~Cam says : MemCardError.~~ <-- SPOOKY ??? Now it works or not, ... looking deeper... ???

Edit1: nd_test, mf_test, ubtest: passed, Zebra fine...
Edit2: Filebrowser is often only after booting in Rec Mode available. // There´s a connecion to deleting testshots...

2B continued...
keep on breathing, should be healthy... 😁

FirstLox.zip

3.06KB

blackhole

Caefix
Cam says : MemCardError. ?? Now it works, ... looking deeper... ???

Edit1: nd_test, mf_test, ubtest: passed, Zebra fine...
Edit2: Filebrowser is only after booting in Rec Mode available. // There´s a connecion to deleting testshots...

Do you see "Memory card error!" on the display after you try to take a picture?

whim

Hi,
Seems I'm too late to report the mode numbers, but another thing I noticed:

- cam* always starts in "rec" mode (w/ either on/off or play button)

stay safe,
whim

* = ixus 265 with your test build, so must be 100c

blackhole

Test version with fix_writable_media_flag in boot.c

whim
Hi,
Seems I'm too late to report the mode numbers, but another thing I noticed:

- cam* always starts in "rec" mode (w/ either on/off or play button)

stay safe,
whim

* = ixus 265 with your test build, so must be 100c

Thanks for the report.
I don't know what to say about the problem with starting in rec mode.
sub_FF06E0EC looks suspicious, but I can't follow it too deep.

 STMFD   SP!, {R4,LR}
 LDR     R3, =0x2AD8
 LDR     R4, [SP,#8+arg_0]
 MOV     R12, #0
 CMP     R4, #0
 STR     R12, [R3]
 MOVNE   R12, #0x80000
 STRNE   R12, [R3]
 CMP     R2, #0
 ORRNE   R2, R12, #0x400000
 STRNE   R2, [R3]
 CMP     R0, #0
 LDRNE   R0, [R3]
 ORRNE   R0, R0, #0x100000
 STRNE   R0, [R3]
 CMP     R1, #0
 LDRNE   R0, [R3]
 ORRNE   R0, R0, #0x200000
 STRNE   R0, [R3]
 LDMFD   SP!, {R4,PC}

In boot.c we currently have:

   // Replacement of sub_ for correct power-on.
   // (short press = playback mode, long press = record mode)
   // value and pointer from sub_FF06E0EC ixus265_elph340hs-100c
   *(int*)(0x2ad😎 = (*(int*)0xC022F484)&0x80000 ? 0x200000 : 0x100000;

ixus265_elph340hs-100c-1.5.0-5456-full-fix_writable_media_flag.zip

802.2KB

ixus265_elph340hs-100c-src.zip

69.17KB

whim

@blackhole

Thanks for your efforts on this port !

This is getting quite weird: for a short while, the cam booted as it should,
"play" -> play, "on/off" -> rec, then reverted to previous behaviour.

Will play with your new build (got some time while under 'intelligent lockdown').

stay safe,whim

P.S Just realised it's been 5 years (!) since I last compiled a build ...

Caefix

blackhole

whim
- cam* always starts in "rec" mode (w/ either on/off or play button)

😐: My play button started in playmode.

When Memory Card is in Error state, it is not even readable, browser | lua.flt can´t be loaded.

// new build commented soon...
The card issue seems gone, fw-update works now,
play button starts in 'random' mode.

😁 Very nice so far...

srsa_4c

@blackhole, Caefix
Can you do an experiment for me?
I'm curious whether switching off the card helps with the card error Caefix is experiencing.
Please put these in task_Startup_my at the place where the diskboot-related function is commented out.

mov r0, #0
bl sub_FF06C4F4

I'm not sure if the above does what I think it does, but it does seem to be the equivalent of what DIGIC 6 cameras do.
Please comment out the fix_writable_media_flag workaround for this experiment.

I'll take a look at the startup issue.

blackhole

srsa_4c
@blackhole, Caefix
Can you do an experiment for me?
I'm curious whether switching off the card helps with the card error Caefix is experiencing.
Please put these in task_Startup_my at the place where the diskboot-related function is commented out.
[code]mov r0, #0
bl sub_FF06C4F4[/code]
I'm not sure if the above does what I think it does, but it does seem to be the equivalent of what DIGIC 6 cameras do.
Please comment out the fix_writable_media_flag workaround for this experiment.

I'll take a look at the startup issue.

Done.
Test build attached.

ixus265_elph340hs-100c-1.5.0-srsa_test-full.zip

802.62KB

srsa_4c

blackhole
Done.

Thanks.

Now, about startup.

I have an old RAM dump from this model. It was made from Canon Basic, playback mode. The word at 0x2ad8 is 0x100000. I'd guess rec mode would be 0x200000.
sub_FF02BC5C evaluates 3 GPIOs (playback button, on/off button, and something else).
I think the playback button's state is *(int*)0xc022f48c & 0x80000. If I'm correct with the above guess, on/off is *(int*)0xc022f48c & 0x100000.
Since I don't know what the third startup possibility is, I'd probably evaluate the on/off button.

reyalp

srsa_4c
Since I don't know what the third startup possibility is, I'd probably evaluate the on/off button.

I'd guess third is probably the wifi / mobile connect button.

blackhole

srsa_4c

I have an old RAM dump from this model. It was made from Canon Basic, playback mode. The word at 0x2ad8 is 0x100000. I'd guess rec mode would be 0x200000.
sub_FF02BC5C evaluates 3 GPIOs (playback button, on/off button, and something else).
I think the playback button's state is *(int*)0xc022f48c & 0x80000. If I'm correct with the above guess, on/off is *(int*)0xc022f48c & 0x100000.
Since I don't know what the third startup possibility is, I'd probably evaluate the on/off button.

I suppose then * (int *) (0x2ad😎 = (* (int *) 0xC022F48C) & 0x100000? 0x200000: 0x100000; should be fine.

One more question.
How did you get to 0xC022F48C, the first entry in the table @ 0xFF5F82DC is 0xCO22F484, I can't find any index,offset or pointer to C022F48C ?

Caefix

HuHU... 🧑‍🎄 Ghost catched I guess.
Very short press <play|wifi> opens lens, longer keeps it closed.
Same at Sx610 & 620.

Edit:
Ix170 short <on> keeps closed, longer opens.
Ix275 <on|wifi|play> allways closed.

Edit2: compared both builds, no diff. Browser, scripts, deleting, RAW... all good.
? fw-Update opens lens.

srsa_4c

reyalpI'd guess third is probably the wifi / mobile connect button.

Yes, very likely. I missed that part of the manual at first.

blackhole
I suppose then * (int *) (0x2ad😎 = (* (int *) 0xC022F48C) & 0x100000? 0x200000: 0x100000; should be fine.

I think so, we'll find out soon.

How did you get to 0xC022F48C, the first entry in the table @ 0xFF5F82DC is 0xCO22F484, I can't find any index,offset or pointer to C022F48C ?

sub_FF06BE70 aka sub_FF06E918 takes a single argument, in r0.
That argument is multiplied by 8 ([tt]lsl #3[/tt] shifts bits to the left, 3 times). So, the GPIO address is taken from 0xFF5F82DC + 8 * r0, the mask is the word after that.

Caefix
Edit2: compared both builds, no diff. Browser, scripts, deleting, RAW... all good.

If that remains so, I'd vote for keeping the later version of the code that switches off the card.

If I understand correctly, the startup workaround for sx610, 620, ixus275 will need to be revisited. After the correct startup on this cam is confirmed.

blackhole

srsa_4c
sub_FF06BE70 aka sub_FF06E918 takes a single argument, in r0.
That argument is multiplied by 8 ([tt]lsl #3[/tt] shifts bits to the left, 3 times). So, the GPIO address is taken from 0xFF5F82DC + 8 * r0, the mask is the word after that.

Thank you for the explanation.

blackhole

Replacement of sub_ for correct power-on.
Expected behavior:
POWER (on / off) button: short press = playback mode, long press = record mode
PLAY button: always playback mode
*(int*)(0x2ad😎 = (*(int*)0xC022F48C)&0x100000 ? 0x200000 : 0x100000;

ixus265_elph340hs-100c-1.5.0-pwr_on-full.zip

802.59KB

Caefix

<on> = play 😖 <play> = play.
(Same as Ix275 now)

« Previous Page Next Page »