New Powershot D30 - page 4 - General Discussion and Assistance - CHDK Forum  

New Powershot D30

  • 72 Replies
  • 21080 Views
*

Offline reyalp

  • ******
  • 13363
Re: New Powershot D30
« Reply #30 on: 28 / July / 2014, 14:14:43 »
Advertisements
Regarding the chdkptp test - is there a short summary how to get the tool running on Ubuntu 14.04 LTS. I installed lua5.2 but what to do then? The hint to find information about the Linux installation in README.TXT file didn't help me.
You would have to build it from source, or get someone else to do it. The Linux binaries I post are built on 10.04 (yes, I know it's ancient), and require your to have the IUP and CD libraries installed.

Building is not terribly hard if you don't need the GUI: You need to install the development packages mentioned in the readme (the exact names may vary depending on the distro), copy config-sample-linux.mk to config.mk and edit it to match your configuration, and then run make. You will also gcc etc installed of course.
Don't forget what the H stands for.

Re: New Powershot D30
« Reply #31 on: 30 / July / 2014, 15:23:29 »
Hello Everyone,

I also own a powershot d30 and am interested in implementing chdk. How can I be of assistance? I can test builds or assist with coding. Thanks for the help and look forward to working with everyone.

Cody

Re: New Powershot D30
« Reply #32 on: 04 / August / 2014, 06:51:19 »
Hi!
Today I found the time to test chdkptp again on Windows 7.
This time the special usb driver installed successful. Start of chdkptp worked as well and the camera was displayed in chdkptp gui. But when I push the button "Connect" I get the following error message on the PC and on the camera's display:

ERROR: error loading module 'capmode' from file 'A/CHDK/LUALIB/capmode.lua':
   cannot fopen A/CHDK/LUALIB/capmode.lua

The file capmode.lua exists on the path - I checked that with the chdk filebrowser!
I even opened capmode.lua with Notepad++ without a problem (inserted the camera's SD-card in a card reader on the PC)

UPDATE:
I tried the same procedure now with my Canon D10 and chdkptp works perfectly! I was able to shoot pictures, replay etc. Everything worked fine.


What's wrong?
« Last Edit: 04 / August / 2014, 07:07:47 by miti.ranieri »

*

Offline reyalp

  • ******
  • 13363
Re: New Powershot D30
« Reply #33 on: 04 / August / 2014, 13:16:40 »
ERROR: error loading module 'capmode' from file 'A/CHDK/LUALIB/capmode.lua':
   cannot fopen A/CHDK/LUALIB/capmode.lua
What's wrong?
This can happen if there isn't much free memory on the cam.
Try
=return get_meminfo()
and
=return get_meminfo('system')

Also check that capmode.lua is actually visible to chdk:
=return os.stat('A/CHDK/LUALIB/capmode.lua')
Don't forget what the H stands for.


Re: New Powershot D30
« Reply #34 on: 05 / August / 2014, 03:00:44 »
This is what the commands returned:

ERROR: error loading module 'capmode' from file 'A/CHDK/LUALIB/capmode.lua':
   cannot fopen A/CHDK/LUALIB/capmode.lua
> =return get_meminfo()
2:return:table:{chdk_start=3461540,free_size=9440,chdk_size=171008,allocated_size=1899096,free_block_count=14,name="combined",allocated_count=1500,chdk_malloc=true,free_block_max_size=7256,allocated_peak=1903168,total_size=1908536,}
> =return get_meminfo('system')
3:return:table:{start_address=1684248,chdk_start=3461540,free_size=8984,chdk_size=171008,allocated_size=1899552,free_block_count=16,allocated_count=1501,name="system",end_address=3592784,chdk_malloc=true,free_block_max_size=6600,allocated_peak=1903168,total_size=1908536,}
> =return os.stat('A/CHDK/LUALIB/capmode.lua')
4:return:table:{is_file=true,mtime=1405333320,ctime=1406275608,attrib=32,is_dir=false,size=2517,}

Is there a possibility to free some memory?

*

Offline reyalp

  • ******
  • 13363
Re: New Powershot D30
« Reply #35 on: 05 / August / 2014, 17:15:26 »
free_size=8984
That confirms that free memory is the problem. Maybe nafraf can implement exmem.

Otherwise, this camera will have very limited functionality with CHDK.
Don't forget what the H stands for.

*

Offline srsa_4c

  • ******
  • 4426
Re: New Powershot D30
« Reply #36 on: 05 / August / 2014, 17:48:17 »
The other possibility is to reduce the memory size reserved for the UI. This cam has 600000 bytes allocated for that purpose. The code in question is:
Code: [Select]
task_Startup:
ff00a638: push {r4, lr}
ff00a63c: bl loc_ff0048c8
ff00a640: bl loc_ff025e10
ff00a644: bl loc_ff025ea4
ff00a648: bl loc_ff026158
ff00a64c: bl loc_ff026324
ff00a650: bl loc_ff02614c
ff00a654: bl loc_ff02602c
ff00a658: bl loc_ff0242a8
ff00a65c: bl loc_ff02632c  // ->
ff00a660: bl loc_ff01e454
ff00a664: bl loc_ff021fd8
ff00a668: bl loc_ff026344
ff00a66c: bl loc_ff01ba14
ff00a670: bl loc_ff01c55c
ff00a674: bl loc_ff025b04
ff00a678: bl loc_ff01cb94
ff00a67c: bl loc_ff01c4f8
ff00a680: bl loc_ff026150
ff00a684: bl loc_ff026ffc
ff00a688: bl loc_ff01c4bc
ff00a68c: pop {r4, lr}
ff00a690: b loc_ff0049e8

loc_ff02632
ff02632c: push {r4, lr}
ff026330: bl loc_ff080de0 // ->
ff026334: bl loc_ff07e434
ff026338: bl loc_ff07ede8
ff02633c: pop {r4, lr}
ff026340: b loc_ff07fdec

loc_ff080de
ff080de0: push {r4, r5, r6, lr}
ff080de4: bl loc_ff0200c4 ; <IsFactoryMode_FW>
ff080de8: cmp r0, #0
ff080dec: ldr r4, =0x3390
ff080df0: ldrne r0, =0xff02437c
ff080df4: strne r0, [r4, #4]
ff080df8: ldrne r0, =0xff024380
ff080dfc: strne r0, [r4, #8]
ff080e00: popne {r4, r5, r6, pc}
ff080e04: ldr r0, [r4]
ff080e08: cmp r0, #0
ff080e0c: popne {r4, r5, r6, pc}
ff080e10: ldr r5, =0x927c0 // 600000 bytes, change this to something smaller
ff080e14: mov r0, r5
ff080e18: bl loc_ff024384
ff080e1c: mov r1, r5
ff080e20: bl loc_ff0243b8
ff080e24: tst r0, #1
ff080e28: str r0, [r4]
ff080e2c: popeq {r4, r5, r6, pc}
ff080e30: pop {r4, r5, r6, lr}
ff080e34: mov r1, #0x4d
ff080e38: ldr r0, =0xff080e5c
ff080e3c: b loc_476afc ; <DebugAssert>

Re: New Powershot D30
« Reply #37 on: 20 / August / 2014, 03:27:36 »
The other possibility is to reduce the memory size reserved for the UI. This cam has 600000 bytes allocated for that purpose. The code in question is:
Code: [Select]
task_Startup:
ff00a638: push {r4, lr}
ff00a63c: bl loc_ff0048c8
ff00a640: bl loc_ff025e10
ff00a644: bl loc_ff025ea4
ff00a648: bl loc_ff026158
ff00a64c: bl loc_ff026324
ff00a650: bl loc_ff02614c
ff00a654: bl loc_ff02602c
ff00a658: bl loc_ff0242a8
ff00a65c: bl loc_ff02632c  // ->
ff00a660: bl loc_ff01e454
ff00a664: bl loc_ff021fd8
ff00a668: bl loc_ff026344
ff00a66c: bl loc_ff01ba14
ff00a670: bl loc_ff01c55c
ff00a674: bl loc_ff025b04
ff00a678: bl loc_ff01cb94
ff00a67c: bl loc_ff01c4f8
ff00a680: bl loc_ff026150
ff00a684: bl loc_ff026ffc
ff00a688: bl loc_ff01c4bc
ff00a68c: pop {r4, lr}
ff00a690: b loc_ff0049e8

loc_ff02632
ff02632c: push {r4, lr}
ff026330: bl loc_ff080de0 // ->
ff026334: bl loc_ff07e434
ff026338: bl loc_ff07ede8
ff02633c: pop {r4, lr}
ff026340: b loc_ff07fdec

loc_ff080de
ff080de0: push {r4, r5, r6, lr}
ff080de4: bl loc_ff0200c4 ; <IsFactoryMode_FW>
ff080de8: cmp r0, #0
ff080dec: ldr r4, =0x3390
ff080df0: ldrne r0, =0xff02437c
ff080df4: strne r0, [r4, #4]
ff080df8: ldrne r0, =0xff024380
ff080dfc: strne r0, [r4, #8]
ff080e00: popne {r4, r5, r6, pc}
ff080e04: ldr r0, [r4]
ff080e08: cmp r0, #0
ff080e0c: popne {r4, r5, r6, pc}
ff080e10: ldr r5, =0x927c0 // 600000 bytes, change this to something smaller
ff080e14: mov r0, r5
ff080e18: bl loc_ff024384
ff080e1c: mov r1, r5
ff080e20: bl loc_ff0243b8
ff080e24: tst r0, #1
ff080e28: str r0, [r4]
ff080e2c: popeq {r4, r5, r6, pc}
ff080e30: pop {r4, r5, r6, lr}
ff080e34: mov r1, #0x4d
ff080e38: ldr r0, =0xff080e5c
ff080e3c: b loc_476afc ; <DebugAssert>
well ,anyluck?


Re: New Powershot D30
« Reply #38 on: 20 / August / 2014, 03:29:09 »
The other possibility is to reduce the memory size reserved for the UI. This cam has 600000 bytes allocated for that purpose. The code in question is:
Code: [Select]
task_Startup:
ff00a638: push {r4, lr}
ff00a63c: bl loc_ff0048c8
ff00a640: bl loc_ff025e10
ff00a644: bl loc_ff025ea4
ff00a648: bl loc_ff026158
ff00a64c: bl loc_ff026324
ff00a650: bl loc_ff02614c
ff00a654: bl loc_ff02602c
ff00a658: bl loc_ff0242a8
ff00a65c: bl loc_ff02632c  // ->
ff00a660: bl loc_ff01e454
ff00a664: bl loc_ff021fd8
ff00a668: bl loc_ff026344
ff00a66c: bl loc_ff01ba14
ff00a670: bl loc_ff01c55c
ff00a674: bl loc_ff025b04
ff00a678: bl loc_ff01cb94
ff00a67c: bl loc_ff01c4f8
ff00a680: bl loc_ff026150
ff00a684: bl loc_ff026ffc
ff00a688: bl loc_ff01c4bc
ff00a68c: pop {r4, lr}
ff00a690: b loc_ff0049e8

loc_ff02632
ff02632c: push {r4, lr}
ff026330: bl loc_ff080de0 // ->
ff026334: bl loc_ff07e434
ff026338: bl loc_ff07ede8
ff02633c: pop {r4, lr}
ff026340: b loc_ff07fdec

loc_ff080de
ff080de0: push {r4, r5, r6, lr}
ff080de4: bl loc_ff0200c4 ; <IsFactoryMode_FW>
ff080de8: cmp r0, #0
ff080dec: ldr r4, =0x3390
ff080df0: ldrne r0, =0xff02437c
ff080df4: strne r0, [r4, #4]
ff080df8: ldrne r0, =0xff024380
ff080dfc: strne r0, [r4, #8]
ff080e00: popne {r4, r5, r6, pc}
ff080e04: ldr r0, [r4]
ff080e08: cmp r0, #0
ff080e0c: popne {r4, r5, r6, pc}
ff080e10: ldr r5, =0x927c0 // 600000 bytes, change this to something smaller
ff080e14: mov r0, r5
ff080e18: bl loc_ff024384
ff080e1c: mov r1, r5
ff080e20: bl loc_ff0243b8
ff080e24: tst r0, #1
ff080e28: str r0, [r4]
ff080e2c: popeq {r4, r5, r6, pc}
ff080e30: pop {r4, r5, r6, lr}
ff080e34: mov r1, #0x4d
ff080e38: ldr r0, =0xff080e5c
ff080e3c: b loc_476afc ; <DebugAssert>
well,anyluck?

Re: New Powershot D30
« Reply #39 on: 28 / August / 2014, 04:28:37 »
Hi, I'm new to CHDK but keen to test anything on Powershot D30 if it helps

I've got a D10 and I'll try to set that up to familiarize myself.

 

Related Topics