IXUS145/ELPH135 Porting attempt - page 9 - DryOS Development - CHDK Forum  

IXUS145/ELPH135 Porting attempt

  • 126 Replies
  • 52459 Views
Re: IXUS145/ELPH135 Porting attempt
« Reply #80 on: 22 / November / 2016, 22:03:34 »
Advertisements
So it seems that EOScard doesn't work well.
For My Testing of a bunch of Ixus145-100c I used different "BULK" method for "Preparing" the requred number of multiple Sd-Cards:-

a/ Using a newish camera that supports "Bootable" Sd-Cards i.e. an Ixus 115.

b/  With the SD-card lock off I use Canon's  Ixus 115 Low Level Format.

c/  With the SD-card lock off use the Ixus 115 alternate Fir Up-Date boot method.

d/ Use the CHDK Ixus 115 to set the SD-Card to "Bootable"

e/ I my case the CHDK versions Ixus 115 and CHDK Ixus 145 were the same.

f/ Delete the Ixus 115's DISKBOOT.BIN (Or just Re-Named to DISKBOOT!BIN)

g/ Then copy Ixus 145's DISKBOOT.BIN

h/ With the SD-card lock on test the Ixus 145's DISKBOOT.BIN

H-H

See Attached Files (EOScard 1V40) Examples for Ixus 125 and EOS M3

Note #1.
When Using the SD-Card Reader/Writer in my Asus Laptop (Windows 10) a number
of "Un-Wanted" and "Hidden" files are also written to the Sd-Card of a fixed size (aprox 50k)
but with variable names dependent upon what software happens to be running at the time.

I just Delete them, but next time I use my Asus Laptop SD-card reader a new, but un-wanted, lot will be added.
« Last Edit: 22 / November / 2016, 22:37:29 by Hardware_Hacker »

Re: IXUS145/ELPH135 Porting attempt
« Reply #81 on: 22 / November / 2016, 22:38:53 »
So it seems that EOScard doesn't work well.
For My Testing of a bunch of Ixus145-100c I used different "BULK" method for "Preparing" the requred number of multiple Sd-Cards:-

a/ Using a newish camera that supports "Bootable" Sd-Cards i.e. an Ixus 115.

b/  With the SD-card lock off I use Canon's  Ixus 115 Low Level Format.

c/  With the SD-card lock off use the Ixus 115 alternate Fir Up-Date boot method.

d/ Use the CHDK Ixus 115 to set the SD-Card to "Bootable"

e/ I my case the CHDK versions Ixus 115 and CHDK Ixus 145 were the same.

f/ Delete the Ixus 115's DISKBOOT.BIN (Or just Re-Named to DISKBOOT!BIN)

g/ Then copy Ixus 145's DISKBOOT.BIN

h/ With the SD-card lock on test the Ixus 145's DISKBOOT.BIN

H-H

See Attached Files (EOScard 1V40) Examples for Ixus 125 and EOS M3

Note #1.
When Using the SD-Card Reader/Writer in my Asus Laptop (Windows 10) a number
of "Un-Wanted" and "Hidden" files are also written to the Sd-Card of a fixed size (aprox 50k)
but with variable names dependent upon what software happens to be running at the time.

I just Delete them, but next time I use my Asus Laptop SD-card reader a new lot will be added.
For the benefit of anyone who finds this post by accident, please just use STICK.  Normal SD card preparation for CHDK usage is really not as complicated as described above.

Edit :  I posted earlier about why zoomx had issues with EOScard.
« Last Edit: 22 / November / 2016, 22:40:48 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: IXUS145/ELPH135 Porting attempt
« Reply #82 on: 26 / November / 2016, 19:41:12 »
I have a chance to get an elph135 cheap...open box.  $35. I want to use it mainly as reference for my digic6  port of the sx60hs because I have no previous experience using a camera with a fully functional chdk .  I realize it could possibly be a different firmware version, but is chdk mostly working for this camera? Like histogram, zebra?
Thx in advance for your advice.  :)
« Last Edit: 26 / November / 2016, 20:23:49 by 62ndidiot »

*

Offline nafraf

  • *****
  • 1308
Re: IXUS145/ELPH135 Porting attempt
« Reply #83 on: 27 / November / 2016, 11:07:36 »
@62ndidiot: blinkythebear tested, see his report here


Re: IXUS145/ELPH135 Porting attempt
« Reply #84 on: 27 / November / 2016, 13:14:44 »
Thanks...
I am wondering why its not in the trunk svn version 4737 yet? I see IXUS 140/Elph 130 and IXUS150/Elph 140. I see the repository of nafraf version 777, here:
http://subversion.assembla.com/svn/nafraf/chdk/platform/ixus145_elph135/
 looks old.  Would like to look at recent source if possible.


edit:
Well I picked it up. Installed ixus145_elph135-100c-1.5.0-4711-3.zip
It boots and works..is seems that DNG is corrupt, not supported yet?
Really would like someone to point me to the most recent source.
« Last Edit: 27 / November / 2016, 20:18:50 by 62ndidiot »

Re: IXUS145/ELPH135 Porting attempt
« Reply #85 on: 30 / November / 2016, 19:53:15 »
I compiled and built and installed @nafraf version that is here;

http://subversion.assembla.com/svn/nafraf/chdk/platform/ixus145_elph135/ :) version 777

Code: [Select]
creating bin_compat.h
boot.o stubs_min.o stubs_auto.o stubs_entry.o stubs_entry_2.o capt_seq.o movie_rec.o filewrite.o main.thm.o gui_draw.thm.o memmgmt.thm.o gui.thm.o kbd_process.thm.o kbd_common.thm.o conf.thm.o gui_osd.thm.o raw.thm.o usb_sync.thm.o shooting.thm.o camera_info.thm.o remotecap.thm.o lib_thumb.thm.o lang_str.thm.o bin_compat.h -> libplatformsub.a
../../../../core/entry.S -> entry.o
-> main.elf
   text    data     bss     dec     hex filename
  87616   40364    6900 134880   20ee0 main.elf
main.elf -> main.bin
<< Leaving ./platform/ixus145_elph135/sub/100c
>> Entering to ./loader/ixus145_elph135
blobs.S -> blobs.o
-> main.elf
main.elf -> main.bin
<< Leaving ./loader/ixus145_elph135
dance -> DISKBOOT.BIN ver 12
copy modules
**** Firmware creation completed successfully

However, the camera enters an infinite loop, no led blinks nothing (battery removal necessary). :(
@nafraf: am I using the correct source code?


Edit: got it working....I am an idiot.


« Last Edit: 30 / November / 2016, 20:43:45 by 62ndidiot »

Re: IXUS145/ELPH135 Porting attempt
« Reply #86 on: 30 / November / 2016, 19:57:25 »
However, the camera enters an infinite loop, no led blinks nothing (battery removal necessary).
Might not have actually been an infinite loop. I think the technical term you are looking for is "hangs".  Which means that it could have been just executing random instructions and wandering around forever while stressing and wearing out parts of your camera.

On not.   Welcome to CHDK  8)
« Last Edit: 30 / November / 2016, 20:00:50 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: IXUS145/ELPH135 Porting attempt
« Reply #87 on: 30 / November / 2016, 20:44:23 »
Got it working now....


Re: IXUS145/ELPH135 Porting attempt
« Reply #88 on: 01 / December / 2016, 18:19:46 »
This is a great little camera! Thanks for doing such a good job on the port. Finally, I can see what CHDK is capable of pre-digic6.  My previous comment about corrupt Dng does not apply, somehow some of my thumbnails are corrupted, but the actual image files are ok when opened for viewing in rawtherapee.  I think I'm noticing the same thing others have noticed regarding underexposure of Jpegs at least in auto mode.

Compiles fine in the standard CHDK environment, only needed loader make file adjustment.

This will be a much appreciated reference camera for me!

Re: IXUS145/ELPH135 Porting attempt
« Reply #89 on: 04 / December / 2016, 19:45:29 »
I found that my build using nafraf's svn version 777 had the wrong addresss for apexus (I think).   I just commented it out in stubs_entry_2.S, and sigfinder did the rest.  Comparing with ixus150 it looks correct. I also uncommented in capt_seq.c
"    BL      shooting_expo_param_override\n"    // added


I tried to manipulate exposure times, and it seems that as long as I am in LONG SHUTTER mode (for night pictures), CHDK is able to set the shutter speed both short and long...it's not clear that this always works. Seems like you need a particular order of doing things. 

I also looked for additional modes by modifying shooting.c
It seems that you can set AV, TV and M modes (at least as long as the camera is in LONG SHUTTER mode first). 
Code: [Select]
    { MODE_AUTO,                32768 },
    { MODE_M,                   32769 },
    { MODE_AV,                  32770 },
    { MODE_TV,                  32771 },
    { MODE_P,                   32772 },
    { MODE_LONG_SHUTTER,        32774 },

Here are some extracts using exiftool:
Code: [Select]
Shooting Mode                   : Long Shutter
Shutter Speed                   : 30

Shooting Mode                   : Long Shutter
Shutter Speed                   : 1/2000

Shooting Mode                   : Manual
Shutter Speed                   : 2

Shooting Mode                   : Shutter speed priority AE
Shutter Speed                   : 2

Aperture                        : 3.2
Shooting Mode                   : Aperture-priority AE
Shutter Speed                   : 1

Aperture                        : 3.2
Shooting Mode                   : Long Shutter
Shutter Speed                   : 1/640

So it looks like you could control much more than the Canon menu allows, but you need to use chdkptp (or gui version to change mode) to enter the correct propcases etc. Is there a standard way to implement things like this?  Just scripts on the camera?



 

Related Topics