ixus175_elph180_100c porting attempt - page 12 - DryOS Development - CHDK Forum
« previous next »
Pages: 1 ... 7 8 9 10 11 [12] 13 14 15 16 17 ... 21   Go Down

ixus175_elph180_100c porting attempt

  • 201 Replies
  • 102089 Views
*

Offline blackhole

  • *****
  • 940
  • A590IS 101b
    • Planetary astrophotography
Re: ixus175_elph180_100c porting attempt
« Reply #110 on: 24 / June / 2017, 12:36:43 »
Advertisements
Deleted.
« Last Edit: 24 / June / 2017, 12:52:28 by blackhole »
Logged
*

Offline axman

  • ***
  • 145
Re: ixus175_elph180_100c porting attempt
« Reply #111 on: 24 / June / 2017, 12:41:58 »
Quote from: arlan_zafian on 24 / June / 2017, 12:05:41
how can i use this chdk. please tell me, i am newbie..

after i unzip the file and put them to sd card, what the next i must do?

how i can find ps.fi2 ?

Greetings, and welcome to CHDK forums.

You may want to read about Beginner questions here;
http://chdk.wikia.com/wiki/CHDK_Links

The sd card must first be specially prepared to work with CHDK.  Read about different ways to do it here;
http://chdk.wikia.com/wiki/Prepare_your_SD_card

In this thread, we are trying to have CHDK function correctly with specific camera ixus175_elph180, having specific Canon firmware version 100c.

The code is not correct, the camera does not function properly.  Some people are trying to figure out what is wrong.  I am a noob at porting cameras..  Without help of experts, it goes very, very slowly, or maybe not at all.

And so if you have one of these cameras, it will be some time (days? weeks?) before it is useable with high chances of success.  You may want to read as much as you can about using CHDK first, and check back here to see if there is progress.  If or when something is ready for test, it will probably be posted here.
Logged
*

Offline waterwingz

  • ******
  • 12139
    • Waterwingz
Re: ixus175_elph180_100c porting attempt
« Reply #112 on: 24 / June / 2017, 12:43:23 »
Quote from: arlan_zafian on 24 / June / 2017, 12:05:41
how i can find ps.fi2 ?
Development versions of CHDK (also called unsupported builds) usually do not include ps.fi2 files. That means you cannot use the "Firmware Update" method of loading - you need to use the autoboot "SD Card Lock" method.

Being able to use unsupported builds is a common difficulty for newbies like yourself.  I think that the easiest way to do this is to use the STICK utility and follow these special instructions : STICK : Installing an unsupported build
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline arlan_zafian

  • *
  • 4
Re: ixus175_elph180_100c porting attempt
« Reply #113 on: 24 / June / 2017, 12:46:41 »
thanks for your reply..
i have ixus 175 with firmware version 100c.
Logged
*

Offline blackhole

  • *****
  • 940
  • A590IS 101b
    • Planetary astrophotography
Re: ixus175_elph180_100c porting attempt
« Reply #114 on: 24 / June / 2017, 12:57:15 »
Quote
@blackhole, the attached build fails hooktest.lua in my cam, run from chdk gui/scripts  - it fails the same way my build does.  Log attached.
Sorry for editing in the previous post.
Put this in code_gen.txt and recompile.
Code: [Select]
//-------------------------- CAPT_SEQ.C -----------------------------------------------------------

FILE capt_seq.c

>>> file=../capt_seq_hdr.c

//////////////////////////////////////////////////////////////
// capt_seq_task
//////////////////////////////////////////////////////////////
FUNC sig=task_CaptSeq name=capt_seq_task
ASM
FW 75
>>>
"    BL      shooting_expo_param_override\n"    // added
<<<
FW 1
>>>
//To do: Check if this is needed.
//"    MOV     R0, #0\n"                          // added
//"    STR     R0, [R5,#0x28]\n"                  // added, fixes overrides behavior at short shutter press (from S95)
<<<
//REM "above patch makes these three lines redundant"
//REM
//REM
FW 2
// hook fast click function for dfs and remote - not needed if using hack above
PATCHSUB ref=0
FW 2
PATCHSUB ref=1
FW $
ENDASM
ENDFUNC

//////////////////////////////////////////////////////////////
// patch for dfs + remote in quickshoot branch: capt_seq_task -> ref=0
//////////////////////////////////////////////////////////////
FUNC ref=0
ASM
FW 47
PATCHSUB
>>>
"    BL      capt_seq_hook_raw_here \n"         // added
<<<
FW $
ENDASM
ENDFUNC

//////////////////////////////////////////////////////////////
// raw hook: capt_seq_task -> ref=1
//////////////////////////////////////////////////////////////
FUNC ref=1
ASM
FW 79
//PATCHSUB ref=1
//FW 1
FW 2
PATCHSUB ref=0
->FW
ENDASM
ENDFUNC

//////////////////////////////////////////////////////////////
//
//////////////////////////////////////////////////////////////
FUNC ref=0
ASM
FW 46
>>>
"    BL      wait_until_remote_button_is_released\n" // added
"    BL      capt_seq_hook_set_nr\n"                 // added
<<<
FW 86
>>> prelabel
"    BL      capt_seq_hook_raw_here \n"         // added
<<<
FW $
>>>
"    .ltorg\n"         // added
<<<
ENDASM
ENDFUNCWhat happens with "Dark Frame Subtraction" override, does it work well?
Was the option selected applied to the first image after the restart?
Logged
*

Offline arlan_zafian

  • *
  • 4
Re: ixus175_elph180_100c porting attempt
« Reply #115 on: 24 / June / 2017, 13:25:06 »
if i locked my sd card, my camera won't turn on... how can fix it?
Logged
*

Offline axman

  • ***
  • 145
Re: ixus175_elph180_100c porting attempt
« Reply #116 on: 24 / June / 2017, 13:35:01 »
Quote from: blackhole on 24 / June / 2017, 12:57:15
What happens with "Dark Frame Subtraction" override, does it work well?
Your code gen.txt is very similar to mine.  Note that exp_drv_task is also present in my code_gen.txt..  I do not think camera will even try to override exposure value without it..  but I am not certain.  I can also try without evp_drv_task, if useful.

With yours, I test Dark Frame Subtraction. 

set exp time to 1min 10sec, take image in closet.
chdk osd shows the exp value as red numerals as overlay on LCD.
first image of dark frame subtract is taken, I can hear shutter open and close.
second image never closes the shutter, I wait 2 minutes (by chdk osd clock)
then press power off button, it retracts lens.
SD card contains the first image, nothing present for second.

from this test there is a single image that looks like a long exposure image.
this test failed when compared to working cams (ixus160, sx530hs) in that ;
    it never closes the shutter to return control to normal shooting (P) mode,
   it requires power button press to retract lens and turn off.

Quote
Was the option selected applied to the first image after the restart?
I am very sorry, I do not understand what is meant by this ^^..

edit: Results revised after seeing test image better.
« Last Edit: 24 / June / 2017, 14:12:43 by axman »
Logged
*

Offline axman

  • ***
  • 145
Re: ixus175_elph180_100c porting attempt
« Reply #117 on: 24 / June / 2017, 14:32:16 »
the raw hook addition suggestion by @blackhole here;
Code: [Select]
"    BL      capt_seq_hook_set_nr\n"                 // added
<<<
FW 86
>>> prelabel
"    BL      capt_seq_hook_raw_here \n"         // added
needed to be FW 87 for my code_gen.txt, to avoid stepping on _DebugAssert.

Re-test, slightly different results but still failing.

Enhanced Photo Ops, LongExp, 1min 10sec exposure
Dark Frame Sub = On
Disable override on startup = Off

picture taken in dark area

for the first 01:10, there is no "Busy" hands showing on osd.  LED on rear is blinking.
then the "Busy" hands appear.  Shutter does not close.  LED still blinking..
power button to stop and retract lens.
Image is taken..  exifprobe says exposure time is only 60sec.

Having a look now in exp_drv_task..
Logged
*

Offline blackhole

  • *****
  • 940
  • A590IS 101b
    • Planetary astrophotography
Re: ixus175_elph180_100c porting attempt
« Reply #118 on: 24 / June / 2017, 14:42:48 »
Quote from: axman on 24 / June / 2017, 14:32:16
the raw hook addition suggestion by @blackhole here;
Code: [Select]
"    BL      capt_seq_hook_set_nr\n"                 // added
<<<
FW 86
>>> prelabel
"    BL      capt_seq_hook_raw_here \n"         // added
needed to be FW 87 for my code_gen.txt, to avoid stepping on _DebugAssert.

Re-test, slightly different results but still failing.

Enhanced Photo Ops, LongExp, 1min 10sec exposure
Dark Frame Sub = On
Disable override on startup = Off

picture taken in dark area

for the first 01:10, there is no "Busy" hands showing on osd.  LED on rear is blinking.
then the "Busy" hands appear.  Shutter does not close.  LED still blinking..
power button to stop and retract lens.
Image is taken..  exifprobe says exposure time is only 60sec.

Having a look now in exp_drv_task..
Quote
Your code gen.txt is very similar to mine.  Note that exp_drv_task is also present in my code_gen.txt..  I do not think camera will even try to override exposure value without it..  but I am not certain.  I can also try without evp_drv_task, if useful.
You do not need exp_drv_task for now.
Comment out "#define CAM_EXT_TV_RANGE 1" in platform_camera.h and "/ *** INSTALL exp_drv_task () hook *** /" in taskhook.S file.
Quote
set exp time to 1min 10sec, take image in closet.
Set the exposure time to 10 seconds and set "Dark Frame Subtraction" to "Off" in the CHDK menu.
After the camera shoots a image, do you see the message "Busy" for next 10 seconds?
Try it several times in succession.
Can you please share your capt_seq.c file?
Logged
*

Offline axman

  • ***
  • 145
Re: ixus175_elph180_100c porting attempt
« Reply #119 on: 24 / June / 2017, 22:22:47 »
Quote from: blackhole on 24 / June / 2017, 14:42:48
You do not need exp_drv_task for now.
Comment out "#define CAM_EXT_TV_RANGE 1" in platform_camera.h and "/ *** INSTALL exp_drv_task () hook *** /" in taskhook.S file.
Done.

Quote
Set the exposure time to 10 seconds and set "Dark Frame Subtraction" to "Off" in the CHDK menu.
After the camera shoots a image, do you see the message "Busy" for next 10 seconds?
Try it several times in succession.
Can you please share your capt_seq.c file?
Since change to platform_camera.h, I cannot select LongExp from CHDK menu->EnhancedPhotoOps

I select ShortExp, and make it 9.99999
Take several images in a row, maybe 8-10.
All behave the same.

Do not see "Busy" for the 10sec the shutter is open;
See a thin white bar across bottom of osd, it goes half way across screen..
Busy flashes briefly after each exposure is done.
Cam returns to normal shooting (P) mode afterwards.

Attached capt_seq.c - it contains all the suggestions you made.  I believe I have applied all suggestions correctly, but maybe not.  code_gen.txt has many comments to help me learn where stuff is, sorry for that.

Thank you very much for looking at this.
Logged
Pages: 1 ... 7 8 9 10 11 [12] 13 14 15 16 17 ... 21   Go Up
« previous next »
 

Related Topics