A2200 IS porting thread - page 51 - DryOS Development - CHDK Forum  

A2200 IS porting thread

  • 515 Replies
  • 138761 Views
*

Offline reyalp

  • ******
  • 13448
Re: A2200 IS porting thread
« Reply #500 on: 15 / February / 2015, 20:24:21 »
Advertisements
Another useful link http://chdk.wikia.com/wiki/User:Srsa_4c/Working_with_a_broken_camera
Quote
2011 and later entry level cameras have a dummy version of DisableLensError, which has no effect. These cameras seem to be the ones without optical IS hardware (A800, A810, A1200, A1300, A2200, A2300
Which means you either need a hardware solution like spectroplasm posted, or additional reverse engineering.
Don't forget what the H stands for.

Re: A2200 IS porting thread
« Reply #501 on: 22 / February / 2015, 10:12:44 »
Something on the computer 'talks' to the camera and sets it to a different internal state. This is known to cause problems. Try to disable the software component that causes it.

Just to close out this issue: after a fair amount of research (related: gvfs documentation is appalling) I found that making the following edit to /usr/share/dbus-1/services/org.gtk.Private.GPhoto2VolumeMonitor.service was the minimal edit required to get my camera happy:

Code: [Select]
[D-BUS Service]
Name=org.gtk.Private.GPhoto2VolumeMonitor
Exec=/bin/false
#Exec=/usr/lib/gvfs/gvfs-gphoto2-volume-monitor

I guess that the CHDK image doesn't like the PTP mount by libgphoto2 for some reason.

Thanks to everyone that helped.

*

Offline reyalp

  • ******
  • 13448
Re: A2200 IS porting thread
« Reply #502 on: 22 / February / 2015, 15:23:15 »
Just to close out this issue: after a fair amount of research (related: gvfs documentation is appalling) I found that making the following edit to /usr/share/dbus-1/services/org.gtk.Private.GPhoto2VolumeMonitor.service was the minimal edit required to get my camera happy:

Code: [Select]
[D-BUS Service]
Name=org.gtk.Private.GPhoto2VolumeMonitor
Exec=/bin/false
#Exec=/usr/lib/gvfs/gvfs-gphoto2-volume-monitor
Good to know.
Quote
I guess that the CHDK image doesn't like the PTP mount by libgphoto2 for some reason.
FWIW,  it's the camera firmware's reaction to some normal (non CHDK) PTP commands, not really specific to CHDK.

An alternative way to deal with this is through udev rules:
http://chdk.setepontos.com/index.php?topic=10664.msg115401#msg115401

This is useful in the case where you might want other devices to continue to work with libgphoto
Don't forget what the H stands for.

Re: A2200 IS porting thread
« Reply #503 on: 25 / February / 2015, 14:31:30 »

An alternative way to deal with this is through udev rules:
http://chdk.setepontos.com/index.php?topic=10664.msg115401#msg115401

This is useful in the case where you might want other devices to continue to work with libgphoto

Good point. I've now backed out my change to the dbus service definition and made the following edit to a copy of /lib/udev/rules.d/40-libgphoto2-6.rules that I've made in /etc/udev/rules.d/; what was /lib/udev/rules.d/40-libgphoto2-6.rules:

Code: [Select]
ACTION!="add", GOTO="libgphoto2_rules_end"
SUBSYSTEM!="usb", GOTO="libgphoto2_usb_end"
ENV{ID_USB_INTERFACES}=="", IMPORT{builtin}="usb_id"
ENV{ID_USB_INTERFACES}=="*:060101:*", ENV{ID_GPHOTO2}="1", ENV{GPHOTO2_DRIVER}="PTP", MODE="0664", GROUP="plugdev"

LABEL="libgphoto2_rules_end"

is now in /etc/udev/rules.d/40-libgphoto2-6.rules

Code: [Select]
ACTION!="add", GOTO="libgphoto2_rules_end"
SUBSYSTEM!="usb", GOTO="libgphoto2_usb_end"
ENV{ID_USB_INTERFACES}=="", IMPORT{builtin}="usb_id"
ENV{ID_USB_INTERFACES}=="*:060101:*", ATTR{idVendor}=="04a9", MODE="0664", GROUP="plugdev", GOTO="libgphoto2_rules_end"
ENV{ID_USB_INTERFACES}=="*:060101:*", ENV{ID_GPHOTO2}="1", ENV{GPHOTO2_DRIVER}="PTP", MODE="0664", GROUP="plugdev"

LABEL="libgphoto2_rules_end"
This inhibits libgphoto2 PTP mounter launching for all Canon cameras (and these Canons for CHDKPTP use are the only Canons I own).


*

Offline reyalp

  • ******
  • 13448
Re: A2200 IS porting thread
« Reply #504 on: 28 / February / 2016, 00:14:17 »
From the ultimate intervalometer thread https://chdk.setepontos.com/index.php?topic=9969.msg126874#msg126874
Ultimate 4.1 was running fine on an A470. Now when I run it on an A2200, I get a " :1: not enough memory error". Could this be a firmware issue?
What canon firmware version does your camera have?

Can you report what get from "show memory info" in the CHDK misc menu?

There is an oddity in this port that versions 100b and 100c are not configured to use EXMEM, but 100d is. This should not vary by sub, if one doesn't have enough memory, then the others almost certainly don't either.
Don't forget what the H stands for.

Re: A2200 IS porting thread
« Reply #505 on: 02 / March / 2016, 17:07:35 »
Free Memory : 239176 bytes
CHDK  size : 134788 bytes
loaded at 0x1698CC

firmware is 100B

--tom

*

Offline reyalp

  • ******
  • 13448
Re: A2200 IS porting thread
« Reply #506 on: 02 / March / 2016, 17:24:42 »
Free Memory : 239176 bytes
Yup, that's really not enough.

Here's a build with ARAM enabled. Please report whether this fixes your problem, and how much free memory is available.

edit:
bad build removed, see below
« Last Edit: 03 / March / 2016, 00:49:34 by reyalp »
Don't forget what the H stands for.

Re: A2200 IS porting thread
« Reply #507 on: 02 / March / 2016, 23:43:31 »
First I replaced the old CHDK software with the new. Camera would not even power on until I inserted a non-CHDK card that was locked. Also had to remove and replace battery.


So, I low level formatted the card and copied over the new software, locked the card. Powered on, did not boot, got "memory card locked" message.


Hmmm. I've not been using this long enough to know that is going on,


--tom


*

Offline reyalp

  • ******
  • 13448
Re: A2200 IS porting thread
« Reply #508 on: 03 / March / 2016, 00:28:08 »
First I replaced the old CHDK software with the new. Camera would not even power on until I inserted a non-CHDK card that was locked. Also had to remove and replace battery.
You're sure your camera is an A2200 with Canon firmware 100b? If so, I probably messed something up, but I don't see what. edit; see next post.

Do you know what CHDK version you had installed before?

Quote
So, I low level formatted the card and copied over the new software, locked the card. Powered on, did not boot, got "memory card locked" message.
Formatting the card erases the Canon boot flag, so you will need to make the card bootable again to autoboot. You can try loading with the "firmware update" option. If it works, you can make the card bootable in the CHDK miscellaneous -> SD card menu. I suspect that the build I posted will crash the same as autoboot did though.

You can also use stick http://zenoshrdlu.com/stick/stick.html to re-install and make the card bootable.
« Last Edit: 03 / March / 2016, 00:50:00 by reyalp »
Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 13448
Re: A2200 IS porting thread
« Reply #509 on: 03 / March / 2016, 00:49:04 »
Found my mistake (forgot to set MEMISOSTART  :-[ ), new test build attached.
Don't forget what the H stands for.

 

Related Topics