ELPH 340 (IXUS 265)

srsa_4c

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

🙁
Have you tried holding down those buttons for longer?
If long pressing play shuts down the camera, please set the ALT key to Wifi in the CHDK menu and try again.

Caefix

srsa_4c

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

🙁
set the ALT key to Wifi in the CHDK menu.

😎Always the 1st I do.
<play> in play always shuts down, in rec closes lens.
Quality of keystroke doesn´t matter.

srsa_4c

@Caefix
Can you do this:
- enter 0xC022F48C in memory browser
- exit memory browser with MENU
- enable Miscellaneous stuff -> Debug parameters -> Show Misc values
- exit ALT mode
- shut down the camera
- press and hold ON/OFF button
- note the number(s) you see in the MEM: line
- unpress ON/OFF
- note the number(s) you see in the MEM: line, again

whim

Hi @srsa_4c,

I'm seeing MEM:0xcb640pq, where p is cycling thru 0..3,
and q is cycling thru 3 7 b f.
After unpressing(releasing) on/off result is
MEM:0xcbe40pq, same cycling for p & q
Note that lens did not extend while performing this procedure,
and starting the cam with short press "play" also produces
MEM:0xcbe40pq, same cycling for p & q

hope that helps,
wim

Caefix

😀 Yes, & starting long<play> = 0xcAe, <wifi> = 0xc9e... holding <wifi> turns on & off immediately.
// Same at srsa´s build, where <on> always opens lens.

srsa_4c

whim
I'm seeing MEM:0xcb640pq, where p is cycling thru 0..3,
and q is cycling thru 3 7 b f.
After unpressing(releasing) on/off result is
MEM:0xcbe40pq, same cycling for p & q
Note that lens did not extend while performing this procedure,
and starting the cam with short press "play" also produces
MEM:0xcbe40pq, same cycling for p & q

Thank you, also to Caefix.

It looks like the ON/OFF button is GPIO 0x47, playback is 0x48 and wifi is 0x49, as seen in sub_ff02bc5c. Buttons are active low, as usual, but sub_ff02bc5c appears to invert them. If I interpret it correctly, 0x2ad8 would be getting 0x100000 when on/off is pressed, but that contradicts what's in my RAM dump.

So, I guess, the line in boot.c would be
*(int*)(0x2ad😎 = (*(int*)0xC022F48C)&0x80000 ? 0x200000 : 0x100000;

Caefix

srsa_4c
*(int*)(0x2ad😎 = (*(int*)0xC022F48C)&0x80000 ? 0x200000 : 0x100000;

😁 Compiled in former source & working!

// core/gui_osd line 1136 has %#8x . Maybe it should be
sprintf(osd_buf, "MEM: %08x", (void*) (*(int*)conf.mem_view_addr_init));
// show value in 08 digit Hexadecimal integer

blackhole

srsa_4c

whim
I'm seeing MEM:0xcb640pq, where p is cycling thru 0..3,
and q is cycling thru 3 7 b f.
After unpressing(releasing) on/off result is
MEM:0xcbe40pq, same cycling for p & q
Note that lens did not extend while performing this procedure,
and starting the cam with short press "play" also produces
MEM:0xcbe40pq, same cycling for p & q
Thank you, also to Caefix.

It looks like the ON/OFF button is GPIO 0x47, playback is 0x48 and wifi is 0x49, as seen in sub_ff02bc5c. Buttons are active low, as usual, but sub_ff02bc5c appears to invert them. If I interpret it correctly, 0x2ad8 would be getting 0x100000 when on/off is pressed, but that contradicts what's in my RAM dump.

So, I guess, the line in boot.c would be
*(int*)(0x2ad😎 = (*(int*)0xC022F48C)&0x80000 ? 0x200000 : 0x100000;

With that we are started, except for 0xc022f48c, in the original source code it was 0xc022f484.
A modified boot.c is attached.

boot.c

16.5KB

blackhole

Is everything okay with this port now (Tv,ISO overrides,PTP..)?

Caefix

??? PTP waiting for connection.

blackhole

Caefix
??? PTP waiting for connection.

Check the USB cable and go to
CHDK settings >> Remote parameters >> Enable remote []

The USB remote option must be disabled to use the PTP Extension.
The libUSB-win32 driver is specific to the selected model. If you use more than one camera model with chdkptp client, you need to install a driver for each one.

Caefix

😁 Thx, I had a "😛" with Zadig tool.
exec require'camtests'.runbatch{bench=true,filexfer=true,shoot=true,xfersizebugs=true} =>25/0

whim

@blackhole

Tv/ISO overrides work OK, llibtst.lua passes without errors. Nothing abnormal detected during testing, feels stable (tested on trunk 5479). In short, you've got my vote for a commit - also because it needs a stubs rebuild in order to becompatible with srsa_4c's exmem updates (5480-5483) as far as I can tell (which is not very far).
cheers,
whim

blackhole

whim

Tv/ISO overrides work OK, llibtst.lua passes without errors. Nothing abnormal detected during testing, feels stable (tested on trunk 5479). In short, you've got my vote for a commit - also because it needs a stubs rebuild in order to becompatible with srsa_4c's exmem updates (5480-5483) as far as I can tell (which is not very far).
cheers,
whim

Thanks for the report.

Poslano sa mog GT-I9301I koristeći Tapatalk

Caefix

??? FW-Update opens lens.

Nutter

@blackhole: Is there a final build of the firmware available? The last one you posted is from April 13, but it looks like there were a few fixes between that build and when you submitted the patch on May 18. Unfortunately it's not in autobuild yet, as per @reyalp's reply in the patches thread ("Autobuild is disabled, as it was in the patch."), so I can't get the build there.

I'm looking for an updated build as the build posted on April 13 doesn't load in either the Firmware Update method or the bootable SD method (camera appears to just crash - no CHDK screen, just a blank screen until the battery is removed & replaced).

whim

@Nutter

Here's the latest trunk build (5577) Tested to work in both firmware update and bootable SD mode.
hope that helps,
whim

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

736.07KB

blackhole

whim
Here's the latest trunk build (5577) Tested to work in both firmware update and bootable SD mode.
hope that helps,
whim

Thanks!

@Nutter
Did you check if your camera has a 100c firmware version?
CHDK will only work on cameras with 100c firmware.

EDIT: link
https://chdk.fandom.com/wiki/FAQ#Q._How_can_I_get_the_original_firmware_version_number_of_my_camera.3F

Nutter

whim
Here's the latest trunk build (5577) Tested to work in both firmware update and bootable SD mode.

Thanks for doing that!

blackhole
Did you check if your camera has a 100c firmware version?
CHDK will only work on cameras with 100c firmware.

That was the problem - my camera's running firmware 100a unfortunately. Thanks though!

blackhole

Nutter
That was the problem - my camera's running firmware 100a unfortunately. Thanks though!

If you can obtain a firmware dump, I can take a look. It may not be necessary to create a new port.
https://chdk.fandom.com/wiki/Canon_Basic/Card_Setup
https://chdk.fandom.com/wiki/Canon_Basic/Scripts/Dumper

« Previous Page Next Page »