A495 porting thread - page 25 - DryOS Development - CHDK Forum
« previous next »
Pages: 1 ... 20 21 22 23 24 [25] 26 27 28 29 30 ... 35   Go Down

A495 porting thread

  • 346 Replies
  • 122307 Views
*

Offline astrosalva

  • *
  • 26
Re: A495 porting thread
« Reply #240 on: 04 / June / 2011, 12:13:18 »
Advertisements
I've tested on 100e:

 Video ok.

ND (I don't know what it is)
I I put it on  the two flavours: in position , and out  position, and writes on the screen correctly the status.
Logged
*

Offline astrosalva

  • *
  • 26
Re: A495 porting thread
« Reply #241 on: 04 / June / 2011, 12:20:33 »
A different question:

For astrophotography

Is possible to enable a mode of operation with chdk that never tests optical status in any way?.
I explain . I use the camera leaving free the way to the ccd ,removing and leaving hanging(connected) the optics and connecting the body to a telescope. For me it would be much better to remove  from the camera the  optics, but then the camera fails and refuses to boot.

thank you
Logged
*

Offline jose1711

  • *
  • 18
Re: A495 porting thread
« Reply #242 on: 04 / June / 2011, 12:26:25 »
i tested latest chdk for 100f firmware. sometimes camera reports and error and shuts itself down when recording video but it's much more stable than the build i had before. one other thing: when i zoom in into digital zoom during making video, optical zoom gets locked (so i can only zoom using digital zoom from that moment on). other things successfully tested:

- histogram
- zebra mode
- osd (clock, battery, filesystem etc)

thank you for good job. jose
Logged
*

Offline twilight_01

  • *
  • 3
Re: A495 porting thread
« Reply #243 on: 04 / June / 2011, 12:32:30 »
I have found a small bug in video mode:

If Digital zoom is put to standard and the user zooms over x3.3 (enters the digital zoom) then he cannot go back to the Optical zoom - zooming and unzooming only functions within the digital values. One has to interrupt the recording, then the unzoom functions. If the digital zoom is turned off there is no problem.
Logged
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: A495 porting thread
« Reply #244 on: 04 / June / 2011, 13:04:48 »
Quote from: astrosalva on 04 / June / 2011, 12:13:18
ND (I don't know what it is)
I I put it on  the two flavours: in position , and out  position, and writes on the screen correctly the status.
Take a picture with both flavours.   Do they look any different ?
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: A495 porting thread
« Reply #245 on: 04 / June / 2011, 13:07:34 »
Quote from: jose1711 on 04 / June / 2011, 12:26:25
i tested latest chdk for 100f firmware. sometimes camera reports and error and shuts itself down when recording video
Are you recording at high resolution on a slow SD card ? 

Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline jose1711

  • *
  • 18
Re: A495 porting thread
« Reply #246 on: 04 / June / 2011, 13:25:50 »
Quote from: waterwingz on 04 / June / 2011, 13:07:34
Quote from: jose1711 on 04 / June / 2011, 12:26:25
i tested latest chdk for 100f firmware. sometimes camera reports and error and shuts itself down when recording video
Are you recording at high resolution on a slow SD card ? 

well.. it might not be the fastest card on the market. 2 gb adata - i do not remember which class is that. jose
Logged
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: A495 porting thread
« Reply #247 on: 04 / June / 2011, 20:02:47 »
Logged
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)
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: A495 porting thread
« Reply #248 on: 04 / June / 2011, 20:15:12 »
Quote from: philmoz on 04 / June / 2011, 20:02:47
You mention firmware 1.00e in a previous post - is this the version you have on your camera?
I think its late where HankPoo lives - he/she is typically gone by this time of night - so I'll answer.   HankyPoo has been successfully testing my 1.00e ports on a 256M card for about a week now.   CHDK works fine on that card. 

Meanwhile, I've been using a 2G card for all my CHDK work.  When I tried a 4G card I gave up when it didn't work right away.  Also tried partitioning an 8G card but the instructions I found on the wiki had me switching back and forth between Linux and Windows and I didn't get that working either.   So far I've assumed it is just not reading the instructions correctly but with all the recent posts on several forums of people having difficulty, I'm starting to wonder.

Think I'll try playing with my 4G and 8G card again - probably using the SDM tools for partitioning and formatting.

Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: A495 porting thread
« Reply #249 on: 04 / June / 2011, 20:40:45 »
Quote from: waterwingz on 04 / June / 2011, 20:15:12
Quote from: philmoz on 04 / June / 2011, 20:02:47
You mention firmware 1.00e in a previous post - is this the version you have on your camera?
I think its late where HankPoo lives - he/she is typically gone by this time of night - so I'll answer.   HankyPoo has been successfully testing my 1.00e ports on a 256M card for about a week now.   CHDK works fine on that card. 

Meanwhile, I've been using a 2G card for all my CHDK work.  When I tried a 4G card I gave up when it didn't work right away.  Also tried partitioning an 8G card but the instructions I found on the wiki had me switching back and forth between Linux and Windows and I didn't get that working either.   So far I've assumed it is just not reading the instructions correctly but with all the recent posts on several forums of people having difficulty, I'm starting to wonder.

Think I'll try playing with my 4G and 8G card again - probably using the SDM tools for partitioning and formatting.



It sounds like the init_file_modules_task isn't getting injected - I had this problem early on with the G12 and SX30 and the A495 is close to the same DryOS version (A495 = R43, G12/SX30 = R45).

Looked at the code for 1.00e - the only thing I can see that may be a problem is where you initialise the taskHook calls:
Code: [Select]
*(int*)0x1934=(int)taskHook;
*(int*)0x1938=(int)taskHook;

On the G12 & SX30 I have to use:
Code: [Select]
*(int*)0x1938=(int)taskHook;
*(int*)0x193C=(int)taskHook;

I checked the 1.00e firmware and it seems to be using the 0x1938 & 0x193C addresses like the G12/SX30.

Also I'd suggest changing the code in taskHook to use address comparisons rather than string comparisons as this function gets called hundreds of times (see my G12/SX30 ports for example).
After you find the addresses in the firmware either insert the hex values directly in taskHook, or add them to stubs_entry_2.S and reference them by name (if you do this make sure to use the DEF() macro not the NHSTUB() macro).

Phil.
Logged
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)
Pages: 1 ... 20 21 22 23 24 [25] 26 27 28 29 30 ... 35   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal