A2200 IS porting thread - page 49 - DryOS Development - CHDK Forum supplierdeeply

A2200 IS porting thread

  • 515 Replies
  • 142394 Views
*

Offline poussin

  • *
  • 36
  • A2200
Re: A2200 IS porting thread
« Reply #480 on: 19 / October / 2013, 11:34:36 »
Advertisements
Looks like hardware fault to me. The lines are curved because the camera corrects its jpeg images at wide angle (they will be straight if you shoot in raw/dng).
exact , lines are straight in .dng

It could be that the external power supply fried something in the camera (assuming you weren't using batteries for scanning pages), but that's just a guess.

I am using batteries.
The problem is more apparent  when luminosity of the scene increases.


*

Offline poussin

  • *
  • 36
  • A2200
Re: A2200 IS porting thread
« Reply #481 on: 19 / October / 2013, 16:11:27 »
Thanks for your replies
here is the .dng showing straight lines http://dl.free.fr/vth5zjWdS
with its information :
Image Description               :
Make                            : Canon
Camera Model Name               : Canon PowerShot A2200
Orientation                     : Horizontal (normal)
Software                        : CHDK_DE ver. 1.3.0
Modify Date                     : 2013:10:19 10:22:13
Artist                          :
Subfile Type                    : Full-resolution Image
Image Width                     : 4416
Image Height                    : 3296
Bits Per Sample                 : 12
Compression                     : Uncompressed
Photometric Interpretation      : Color Filter Array
Strip Offsets                   : 38400
Samples Per Pixel               : 1
Rows Per Strip                  : 3296
Strip Byte Counts               : 21832704
X Resolution                    : 180
Y Resolution                    : 180
Planar Configuration            : Chunky
Resolution Unit                 : inches
CFA Repeat Pattern Dim          : 2 2
CFA Pattern 2                   : 1 2 0 1
Black Level                     : 127
White Level                     : 4095
Default Crop Origin             : 8 3
Default Crop Size               : 4320 3240
Active Area                     : 29 16 3275 4352

*

Offline reyalp

  • ******
  • 13502
Re: A2200 IS porting thread
« Reply #482 on: 19 / October / 2013, 16:28:59 »
That certainly looks like a hardware fault to me.
Don't forget what the H stands for.

Re: A2200 IS porting thread
« Reply #483 on: 18 / November / 2014, 02:14:49 »
Hi there,

Not sure if it's the right place or not to post a bug report on the A2200 build or I should be starting a new thread but here goes...

I'm trying to use chdkptp (r658) to trigger a shot but it's crashing the camera. Steps in chdk are:

Code: [Select]
gareth@cagliostro:~$ chdkptp
___> list
-1:Canon PowerShot A2200 b=002 d=005 v=0x4a9 p=0x322a s=C6D2107DA75B43F5948C8344A3E0CBA7
___> connect
connected: Canon PowerShot A2200, max packet size 512
con> rec
con 1> shoot
ERROR: I/O error
___>

I'm seeing this behaviour across two different A2200s, one is v1.00b and one is v1.00d. Both are running 1.3.0 build 3746.

Attached is the ROMLOG.TXT. The top couple of lines are:

Code: [Select]
ASSERT!! ExMemMan.c Line 1251
Occured Time  2014:11:18 06:58:38
Task ID: 12386329
Task name: CtrlSrv
SP: 0x00305490
StackDump:
0x00000000
0xFF8855E4

My dayjob involves embedded programming so I'm happy to dive in if someone can give me an indication where to start.

Cheers
Gareth


*

Offline poussin

  • *
  • 36
  • A2200
Re: A2200 IS porting thread
« Reply #484 on: 18 / November / 2014, 05:05:52 »
hello
If you use the stable 1.20 build 3659  from http://mighty-hoernsche.de/ , is it working ok ?
Then compare the sources for changes

*

Offline srsa_4c

  • ******
  • 4430
Re: A2200 IS porting thread
« Reply #485 on: 18 / November / 2014, 12:37:56 »
Not sure if it's the right place or not to post a bug report on the A2200 build or I should be starting a new thread but here goes...

I'm trying to use chdkptp (r658) to trigger a shot but it's crashing the camera.
Hi,

the porting thread is a good place for camera-specific bugreports. This specific issue has already been noted (at least I think it is the same issue that you can find in the first post of this thread). If you just want to shoot, try the workaround (1st post). edit: I think "mode 1" is rec mode, "mode 0" is playback mode, but I can be wrong.

If you'd like to investigate instead, here's what you could do (addresses are from 100b):
- The assert is due to [0x2d24 + 8] not being 0x14. 0x14 seems to be the total number of exmem types. Exmem is a memory allocation system used by the camera for various operations that require a big memory area (playing/shooting movies, compressing stills, etc.). The assert is in the internal allocator routine (sub_FF8853B8, appears to be similar to sub_FF813884 in ixus30 100k), the ixus30 assert text is "m_TopAllocType == MAX_NUM_OF_EXMEMORY_TYPE".
- Try dumping (or observing) that memory area
 - in playback and rec mode without using PTP
 - in playback mode before connecting PTP
 - in playback mode after connecting PTP
 - after issuing "rec" in chdkptp
 - ...
... and see when (and how) does that piece of memory change

A few notes:
- The assert happens in a task that CHDK does not influence.
- PTP itself allocates a chunk of exmem (usually ~1MB) when a PTP connection is active.
- The a2200 100d CHDK port places CHDK in exmem area, the 100b port does not (and the error you're getting is not affected by this difference).
- This camera does not officially support an active USB connection while in rec mode, so this scenario is likely not tested by the manufacturer (but it does work on a majority of CHDK cameras).
- Some ports show various strange symptoms which might be the result of some RAM corruption by either the Canon firmware or CHDK.
- You can find lots of function addresses in funcs_by_address.csv files.
« Last Edit: 18 / November / 2014, 12:52:42 by srsa_4c »

Re: A2200 IS porting thread
« Reply #486 on: 18 / November / 2014, 16:43:11 »
Hi srsa_4c,

Quote
If you just want to shoot, try the workaround (1st post). edit: I think "mode 1" is rec mode, "mode 0" is playback mode, but I can be wrong.

aha! this is the information I was missing. Going rec, play, rec then shoot or remoteshoot executes without the crash.

Quote
If you'd like to investigate instead, here's what you could do (addresses are from 100b)

I will definitely look into it further - this is the recommended camera for the DIY bookscanner project and I'm surprised no-one has run into it before, so I'd like to understand it.

Thanks for your help,
Gareth

*

Offline nafraf

  • *****
  • 1308
Re: A2200 IS porting thread
« Reply #487 on: 19 / November / 2014, 07:44:51 »
aha! this is the information I was missing. Going rec, play, rec then shoot or remoteshoot executes without the crash.
If you call remoteshoot without going rec, play, rec, does camera crash?  Are you using spreads?

Quote
I will definitely look into it further - this is the recommended camera for the DIY bookscanner project and I'm surprised no-one has run into it before, so I'd like to understand it.
IIRC, before spreads, DIY bookscanner used USB port for trigger, and now spreads uses remote remoteshoot command.


*

Offline poussin

  • *
  • 36
  • A2200
Re: A2200 IS porting thread
« Reply #488 on: 21 / November / 2014, 13:57:14 »
My two cents ,


As far I remember from my past experience :

the  A2200 1.00d was working fine

for "useful" book scanning , the A2200 was limit

Re: A2200 IS porting thread
« Reply #489 on: 22 / November / 2014, 06:49:50 »
hello
If you use the stable 1.20 build 3659  from http://mighty-hoernsche.de/ , is it working ok ?
Then compare the sources for changes

Stable build crashes in the same way on my v1.00d camera.

If you call remoteshoot without going rec, play, rec, does camera crash?

Yes. Both shoot and remoteshoot behave the same way in both cases.

Quote from: nafraf
Are you using spreads?

Yes, and I'm discussing the failure with jbaiter who is going to try to reproduce. I see others have had success with this camera though so I am still surprised I am running into it.


 

Related Topics