D20 porting thread - page 2 - DryOS Development - CHDK Forum supplierdeeply
« previous next »
Pages: 1 [2] 3 4 5   Go Down

D20 porting thread

  • 45 Replies
  • 16083 Views
*

Offline jedaker

  • *
  • 2
Re: D20 porting thread
« Reply #10 on: 21 / May / 2013, 16:42:08 »
Advertisements
Here's what I get running the script outside in bright light:

Aperture          PROPCASE_AV        Zoom
-----------          ------------------        -------
8                      570-582                 0-62
9                      583-614                 63-116
10                    615-622                 117-129

I haven't figured out what lighting conditions will give me intermediate aperture values like 6 or 7 yet.
Logged
*

Offline nafraf

  • *****
  • 1308
Re: D20 porting thread
« Reply #11 on: 21 / May / 2013, 22:42:47 »
Thanks, I'll update aperture table.

Have you tested photo related overrides?  Have you detected any bug?
Logged
*

Offline Jeffreydonaldnelson

  • *
  • 4
Re: D20 porting thread
« Reply #12 on: 25 / June / 2013, 18:55:10 »
Hello Rdumont99,

I have a powershot D20 and have really been trying to make CHDK work. I successfully loaded the 100b firmware on a 32g Sandisk.  Unfortunately, I cannot get any downloaded scripts to run.  In fact, I am not even able to open the script menu.  Do you have any ideas?  One thread mentioned partions on my memory... I really don't know.

Thank you.
Jeff@fundavida.org
Logged
*

Offline waterwingz

  • ******
  • 12128
    • Waterwingz
Re: D20 porting thread
« Reply #13 on: 25 / June / 2013, 19:15:02 »
Quote from: Jeffreydonaldnelson on 25 / June / 2013, 18:55:10
I have a powershot D20 and have really been trying to make CHDK work. I successfully loaded the 100b firmware on a 32g Sandisk.  Unfortunately, I cannot get any downloaded scripts to run.  In fact, I am not even able to open the script menu.  Do you have any ideas?  One thread mentioned partions on my memory... I really don't know.
The D20 was released in 2012 and thus does not require partitioning of the SD card. 

I assume from your comments that you are getting CHDK to load?  Do you see the CHDK logo at startup and can enter <ALT> mode and see the CHDK menus ?

I'm curious how you know that you cannot get any downloaded scripts to run if you are unable to open the script menu? 

So the most likely scenerio is that you did not completely install CHDK to your SD card correctly.   Full installation instructions are here : http://chdk.wikia.com/wiki/Prepare_your_SD_card but I recommend simply using the STICK utility listed at the top of that page.

Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline Jeffreydonaldnelson

  • *
  • 4
Re: D20 porting thread
« Reply #14 on: 27 / June / 2013, 22:23:24 »
Hello Waterwingz,
Thank you for your prompt response. 

I have been able to load CHDK correctly, but the screen flickers. 

I tried using STICK a couple days ago but got the response that my camera is not supported yet (I don't remember the exact wording).   I will try to walk through the Card Preparation process again and get back to you this weekend.

As far as the scripts, my card shows when connected to the computer, that I have downloaded the correct scripts, but I cannot access the script menu when back in my camera.

Thanks again for all of your help, I will remove the "Talk" tab on the D20 page.
Jeff
Logged
*

Offline waterwingz

  • ******
  • 12128
    • Waterwingz
Re: D20 porting thread
« Reply #15 on: 27 / June / 2013, 23:09:44 »
Quote from: Jeffreydonaldnelson on 27 / June / 2013, 22:23:24
I have been able to load CHDK correctly, but the screen flickers. 
Unfortunately, its a limitation of CHDK running on top of the Canon firmware.
http://chdk.setepontos.com/index.php?topic=8450.msg96390#msg96390
Does it flicker in playback mode or just in shooting mode?

Quote
I tried using STICK a couple days ago but got the response that my camera is not supported yet (I don't remember the exact wording).   I will try to walk through the Card Preparation process again and get back to you this weekend.
The D20 is only available from the 1.2.0 CHDK trunk (aka unstable or dev).  I  believe there is a way to change the config file for STICK to make it use that version.

Quote
As far as the scripts, my card shows when connected to the computer, that I have downloaded the correct scripts, but I cannot access the script menu when back in my camera.
If you can't bring up the script menu,  it doesn't matter if you have downloaded any scripts correctly.  You don't have the fselect.flt module in the /CHDK/MODULES directory on your SD card so can't bring up the file browser.
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline Jeffreydonaldnelson

  • *
  • 4
Re: D20 porting thread
« Reply #16 on: 28 / June / 2013, 02:19:08 »
"Does it flicker in playback mode or just in shooting mode?"
I believe that it flickers in both, but honestly the flickering doesn't bother me much. I just thought that it might be a symptom of a deeper issue.

"I  believe there is a way to change the config file for STICK to make it use that version."
That sounds sweet, let me know if you have any specific leads.

Again, I will walk through the upload basics this weekend (Sunday morning) and let you know if anything changes.  Thanks again for your patience and assistance.
Peace!

Logged
*

Offline Jeffreydonaldnelson

  • *
  • 4
Re: D20 porting thread
« Reply #17 on: 12 / July / 2013, 12:05:34 »
SUCCESS! Thanks again for all of your patience.  I was able to reload CHDK and the correct intervalometer onto my D20.  I just needed to reformat my card and transfer all of the CHDK files directly to my card.

THANK YOU!

I will keep you posted on finished products.
Logged
*

Offline lapser

  • *****
  • 1093
Re: D20 porting thread
« Reply #18 on: 23 / August / 2013, 12:34:04 »
In my first time lapse with the D20, I noticed that the the shot meter readings (out of the raw buffers) only changed every other picture. There appears to be a mistake in the D20 lib.c. Both raw buffer addresses are identical.
Code: [Select]
#include "platform.h"

char *hook_raw_image_addr()     {return (char*) 0x4138AE00;}   //Found @0xff363310 d20 100b Search on JPEG BUFF
char *hook_alt_raw_image_addr() {return (char*) 0x4138AE00;}   //Found @0xff363310 d20 100b
I also tried saving raw files in dng format. It worked, but I can't seem to read the dng files in Lightroom. The problem could be on my end, but I uploaded the dng and corresponding jpg files here:
http://www.adrive.com/public/PNF9g4/D20_RawTest.zip

The camera uses the same battery as the SX260, so I already have extra batteries. To get external power to the SX260, you need to insert a dummy battery, which comes with Canon's external power supply. The D20 has the same external connector built into the camera behind the door with the USB connector. The external power supply (Chinese version) powers the camera nicely from this connector, with no dummy battery needed.

This allows you to power the camera externally while you also have the internal battery installed. Unfortunately, if you disconnect the external power while the camera is on, it shuts off the camera. You can turn it back on, with the internal battery, but the internal battery isn't a backup for the external power supply. I lost all my pictures on the SX260 when the external battery shut off on my overnight time lapse, so this would have been a nice feature.

Fortunately, my time lapse script has exposure smoothing, so it was able to deal with the raw buffer address error and create a nice video:
http://www.youtube.com/watch?v=3dGj4CRDeqw#
Logged
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos
*

Offline reyalp

  • ******
  • 13840
Re: D20 porting thread
« Reply #19 on: 23 / August / 2013, 16:11:54 »
Quote from: lapser on 23 / August / 2013, 12:34:04
In my first time lapse with the D20, I noticed that the the shot meter readings (out of the raw buffers) only changed every other picture. There appears to be a mistake in the D20 lib.c. Both raw buffer addresses are identical.
Code: [Select]
#include "platform.h"

char *hook_raw_image_addr()     {return (char*) 0x4138AE00;}   //Found @0xff363310 d20 100b Search on JPEG BUFF
char *hook_alt_raw_image_addr() {return (char*) 0x4138AE00;}   //Found @0xff363310 d20 100b
What code are you looking at? In platform/d20/lib.c you should see the following:
Code: [Select]
char *hook_raw_image_addr()
{
    return raw_buffers[active_raw_buffer];
}

char *hook_alt_raw_image_addr()
{
    return raw_buffers[active_raw_buffer^1];
}
The original value in sub/100b/lib.c is commented out.
See http://trac.assembla.com/chdk/changeset/3011/trunk and link in the commit message
Quote
I also tried saving raw files in dng format. It worked, but I can't seem to read the dng files in Lightroom. The problem could be on my end, but I uploaded the dng and corresponding jpg files here:
http://www.adrive.com/public/PNF9g4/D20_RawTest.zip
There was a problem with this in the old code, but it should be fixed in the current trunk (edit and 1.2 release).

See the following http://trac.assembla.com/chdk/changeset/3007/trunk and forum link in the commit message.


Logged
Don't forget what the H stands for.
Pages: 1 [2] 3 4 5   Go Up
« previous next »
 

Related Topics