A800 Porting Thread - page 21 - DryOS Development - CHDK Forum  

A800 Porting Thread

  • 277 Replies
  • 75799 Views
Re: A800 Porting Thread
« Reply #200 on: 06 / April / 2012, 02:44:52 »
Advertisements
If you select "save RAW directory JPEG" The camera takes a picture on and off with an open lens.

Re: A800 Porting Thread
« Reply #201 on: 06 / April / 2012, 09:35:09 »
If you select "save RAW directory JPEG" The camera takes a picture on and off with an open lens.
Do you mean that the camera takes a picture and then crashes with the lens extended ? 

What happens when you do not select "save RAW directory JPEG" and take a picture ?
Ported :   A1200    SD940   G10    Powershot N    G16

Re: A800 Porting Thread
« Reply #202 on: 06 / April / 2012, 12:25:00 »
Quote
Do you mean that the camera takes a picture and then crashes with the lens extended ?

Re: A800 Porting Thread
« Reply #203 on: 06 / April / 2012, 12:26:27 »
Quote from: waterwingz
[/quote
Do you mean that the camera takes a picture and then crashes with the lens extended ?


yes,the camera takes a picture and then crashes with the lens extended

[/quote]What happens when you do not select "save RAW directory JPEG" and take
 a picture ? [/quote]

then the camera is working fine. except the video mode.
« Last Edit: 06 / April / 2012, 12:36:11 by nifelim »


Re: A800 Porting Thread
« Reply #204 on: 06 / April / 2012, 16:49:39 »
Quote
What happens when you do not select "save RAW directory JPEG" and take
 a picture ?

then the camera is working fine

Where does the RAW image get stored when you do not select "save RAW directory JPEG" ?  Maybe we don't need that option (its configurable at build time).
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: A800 Porting Thread
« Reply #205 on: 06 / April / 2012, 20:59:26 »
Quote from: waterwingz
[/quote
Do you mean that the camera takes a picture and then crashes with the lens extended ?


yes,the camera takes a picture and then crashes with the lens extended


Could be the 'get_target_dir_name'  function is wrong in shooting.c.
There are two variation of this for cameras that use date based folder naming.
The older version (G12) has to add the drive letter to the path in the CHDK code.
The newer version (SX40) does not since it is added by the firmware code.

The A800 is currently using the G12 version; but given the release date of the camera should probably be using the SX40 version.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

Re: A800 Porting Thread
« Reply #206 on: 06 / April / 2012, 21:11:02 »
The A800 is currently using the G12 version; but given the release date of the camera should probably be using the SX40 version.
Qanthelas : what happens when you select this option on your 1.00C camera ? (new version for your camera posted below if that helps).

I asked the question above about where RAW was stored for the same reason philmoz suggested that the CAM_DATE_FOLDER_NAMING choice in platform_camera.h was wrong.
« Last Edit: 06 / April / 2012, 21:23:35 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: A800 Porting Thread
« Reply #207 on: 06 / April / 2012, 21:16:00 »
New beta version of A800 f/w 1.00B and 1.00C    Disables CAM_DATE_FOLDER_NAMING option in platform_camera.h,  which should fix the RAW save bug reported by nifelim

A800 1.00B Beta 3

A800 1.00C Beta 3

UPDATE : corrected these files to use SX40 version of 'get_target_dir_name' per suggestion from philmoz in post below.
« Last Edit: 06 / April / 2012, 23:06:40 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: A800 Porting Thread
« Reply #208 on: 06 / April / 2012, 21:31:48 »
New beta version of A800 f/w 1.00B and 1.00C    Disables CAM_DATE_FOLDER_NAMING option in platform_camera.h,  which should fix the RAW save bug reported by nifelim

A800 1.00B Beta 3

A800 1.00C Beta 3


If the camera actually uses data based folder naming then this is not a good idea.
The option to save RAW/DNG in the JPEG folder will not work and will instead create a new folder named 100CANON.
I've also experienced problems with this 100CANON folder causing the camera to forget the latest image number and restart image numbering from 0.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

Re: A800 Porting Thread
« Reply #209 on: 07 / April / 2012, 12:03:55 »
I got two log files and both show "ASSERT!! MotionVector.c Line 133" a search indicates that MotionVector is from the original firmware
In case of a crash, the camera tries to record debugging information (function of the original firmware). When you request a romlog, you always get the information about the latest recorded crash event (watch the timestamp to see whether a new crash has happened).
In some cases the camera's operating system fails to catch the event and the crash doesn't leave a trace.
Quote
and the times stamps don't match the times when the camera actually stopped.
Are you sure? Your current log shows a fresh timestamp with about 78 minutes uptime (the 8 digit numbers in the second half of the log show the elapsed milliseconds).

If your camera crashes again, try to get another romlog.

I had another couple crashes.
To recap - I am taking a picture every 15 min during daylight times.
The camera just stops working randomly, sometimes after 2 hours sometimes after as much as 3 days.

RomLog4
 - worked correctly for 1 hour 15 min, or 6 pictures.
 - Last picture taken was 07:00
 - Occured Time  2012:04:04 06:00:38


RomLog5
 - worked correctly for almost two days.
 - Last picture taken was 10:30
 - Occured Time  2012:04:07 09:30:40

I have a third log that is also off by one hour. If the time stamp is off by an hour the crashes are happening right after taking a picture.

I will update to beta 3 and continue my time-lapse.

If these logs do not help narrow down the problem is there something in particular I should be looking for or missing in the log file that will help narrow down the problem?

Jim

 

Related Topics