PowerShot SX210 IS - Porting Thread - page 29 - General Discussion and Assistance - CHDK Forum supplierdeeply
« previous next »
Pages: 1 ... 24 25 26 27 28 [29] 30 31 32 33 34 ... 59   Go Down

PowerShot SX210 IS - Porting Thread

  • 589 Replies
  • 301589 Views
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: PowerShot SX210 IS - Porting Thread
« Reply #280 on: 22 / September / 2010, 14:01:33 »
Advertisements
Thanks moonbeast, great job documenting the testing,

I will see what I can do to start solving things

To solve some of the issues I think we need to check all the stubs auto and stub2, here they are:

   AUTO      MANUAL   
   NSTUB(_log, 0xffb613b4)         
   NSTUB(_log10, 0xffb60040)         
   NSTUB(_pow, 0xffb601b0)         
   NSTUB(_sqrt, 0xffb62fbc)         
   NSTUB(AllocateMemory, 0xffac3f54)      NHSTUB(AllocateMemory, 0xFFAC3F54)   
   NSTUB(AllocateUncacheableMemory, 0xff83a658)      NHSTUB(AllocateUncacheableMemory, 0xFF83A658)   
         NHSTUB(apex2us, 0xFFA2260C)   
   NSTUB(close, 0xff81aa94)      NHSTUB(close, 0xFF81AA94)   
   NSTUB(Close, 0xff836c50)      NHSTUB(Close, 0xff836c50)   
   NSTUB(closedir, 0xffaa1d64)      NHSTUB(closedir, 0xFFAA1B7C)   
   NSTUB(closefastdir, 0xffaa1d64)      NHSTUB(closefastdir, 0xFFAA1B7C)   
   NSTUB(CreateTask, 0xff81e83c)         
   NSTUB(DeleteFile_Fut, 0xff8365c8)         
         NHSTUB(DoAFLock, 0xFF8383F0)   
   NSTUB(ExecuteEventProcedure, 0xff88d3dc)         
   NSTUB(ExitTask, 0xff81eacc)      NHSTUB(eventproc_export_ExitTask, 0xFF81EACC)   
         NHSTUB(EnterToCompensationEVF, 0xFF838598)    
         NHSTUB(ExitFromCompensationEVF, 0xFF8385DC)    
         NHSTUB(ExpCtrlTool_StartContiAE, 0xFF846458)   
         NHSTUB(ExpCtrlTool_StopContiAE, 0xFF846530)   
         NHSTUB(fclose, 0xff836744)   
   NSTUB(Fclose_Fut, 0xff836744)         
   NSTUB(Feof_Fut, 0xff836930)         
   NSTUB(Fflush_Fut, 0xff83696c)         
   NSTUB(Fgets_Fut, 0xff836898)         
         NHSTUB(fopen, 0xff836704)   
   NSTUB(Fopen_Fut, 0xff836704)         
         NHSTUB(fread, 0xff8367f0)   
   NSTUB(Fread_Fut, 0xff8367f0)         
   NSTUB(free, 0xff81415c)      NHSTUB(free, 0xFF81415C)   
   NSTUB(FreeMemory, 0xffac3f4c)         
   NSTUB(FreeUncacheableMemory, 0xff83a698)      NHSTUB(FreeUncacheableMemory, 0xFF83A698)   
   NSTUB(Fseek_Fut, 0xff8368e4)         
         NHSTUB(fwrite, 0xff836844)   
   NSTUB(Fwrite_Fut, 0xff836844)         
         NHSTUB(GetBatteryTemperature, 0xFF866F08)   
         NHSTUB(GetCCDTemperature, 0xFF866E94)   
   NSTUB(GetDrive_ClusterSize, 0xff873868)      NHSTUB(GetDrive_ClusterSize, 0xFF873868)   
         NHSTUB(GetDrive_FreeClusters, 0xFF8738C8)    
   NSTUB(GetDrive_TotalClusters, 0xff87389c)      NHSTUB(GetDrive_TotalClusters, 0xFF87389C)   
   NSTUB(GetFocusLensSubjectDistance, 0xff964644)      NHSTUB(GetFocusLensSubjectDistance, 0xFF964644)   
   NSTUB(GetFocusLensSubjectDistanceFromLens, 0xff9649cc)         
   NSTUB(GetOpticalTemperature, 0xff866f7c)      NHSTUB(GetOpticalTemperature, 0xFF866F7C)   
   NSTUB(GetParameterData, 0xff99d9a8)         
   NSTUB(GetPropertyCase, 0xff891070)         
   NSTUB(GetSystemTime, 0xffac3fac)      NHSTUB(GetSystemTime, 0xFFAC3FAC)   
         NHSTUB(GiveSemaphore, 0xFF83A074)    
         NHSTUB(GetZoomLensCurrentPosition, 0xFFAB484C)    
         NHSTUB(GetCurrentTargetDistance, 0xFF964644)    
         NHSTUB(GetZoomLensCurrentPoint, 0xFF9698AC)   
         NHSTUB(GetLogToFile, 0xFF977918)   
         NHSTUB(GetCurrentAvValue, 0xFF9665D4)   
   NSTUB(IsStrobeChargeCompleted, 0xff8da74c)         
   NSTUB(kbd_p1_f, 0xff8346e4)         
   NSTUB(kbd_p1_f_cont, 0xff8346f0)         
   NSTUB(kbd_p2_f, 0xff833f90)      NHSTUB(kbd_p2_f, 0xFF833F90)   
   NSTUB(kbd_read_keys, 0xff83466c)      NHSTUB(kbd_read_keys, 0xFF83466C)   
   NSTUB(kbd_read_keys_r2, 0xff861580)      NHSTUB(kbd_read_keys_r2, 0xFF861580)    
         NHSTUB(kbd_pwr_off, 0xFF810B1C)                   //  ???????????????????   
         NHSTUB(kbd_pwr_on, 0xFF810B1C)                    //  ???????????????????    
   NSTUB(LocalTime, 0xff88ac58)         
   NSTUB(LockMainPower, 0xff8975b4)         
   NSTUB(lseek, 0xff836d78)         
         NHSTUB(LockAndRefresh, 0xFFA1ED98)    
         NHSTUB(LEDDrive, 0xff96eae4)   
         NHSTUB(MakeAFScan, 0xFF970F5C)   
   NSTUB(MakeDirectory_Fut, 0xff83663c)         
   NSTUB(malloc, 0xff814100)      NHSTUB(malloc,0xFF814100)   
   NSTUB(memcmp, 0xff82067c)      NHSTUB(memcmp, 0xff82067c)   
   NSTUB(memcpy, 0xff83fdb4)         
   NSTUB(memset, 0xffa21644)         
   NSTUB(mkdir, 0xff8370ec)      NHSTUB(mkdir, 0xFF8370EC)   
   NSTUB(mktime_ext, 0xff8af464)         
   NSTUB(MoveFocusLensToDistance, 0xffb2918c)         
   NSTUB(MoveZoomLensWithPoint, 0xffac1d10)         
         NHSTUB(Mount_FileSystem, 0xFF810B1C)              //  ???????????????????   
   NSTUB(NewTaskShell, 0xff890a7c)         
   NSTUB(open, 0xff81a9e4)      NHSTUB(open, 0xFF81A9E4)   
   NSTUB(Open, 0xff870b74)      NHSTUB(Open, 0xff836be4)   
   NSTUB(opendir, 0xffaa1bcc)      NHSTUB(opendir, 0xFFAA1BCC)    
         NHSTUB(openfastdir, 0xFFAA1BCC)   
   NSTUB(PostLogicalEventForNotPowerType, 0xff89538c)      NHSTUB(PostLogicalEventForNotPowerType, 0xFF89538C)   
   NSTUB(PostLogicalEventToUI, 0xff8953d8)      NHSTUB(eventproc_export_PostLogicalEventToUI, 0xFF8953D8)    
         NHSTUB(PT_PlaySound, 0xFF885CD0)    
         NHSTUB(PostLEDMessage, 0xFF860FF8 )   
         NHSTUB(platformsub_kbd_fetch_data, 0xFF861D88)   
         NHSTUB(qsort, 0xFFB17F74)   
« Last Edit: 22 / September / 2010, 14:05:54 by asm1989 »
Logged
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: PowerShot SX210 IS - Porting Thread
« Reply #281 on: 22 / September / 2010, 14:06:52 »
And the rest, (limit of 7500 chars)

   NSTUB(rand, 0xff820784)         
   NSTUB(Read, 0xff81ac7c)         
   NSTUB(read, 0xff81ac7c)      NHSTUB(read, 0xff836cdc)   
         NHSTUB(Read, 0xff836cdc)   
         NHSTUB(readfastdir, 0xFFAA1D20)   
         NHSTUB(ReadFastDir, 0xFFAA1D20)   
         NHSTUB(ReadSDCard, 0xFF953F88)   
         NHSTUB(RefreshPhysicalScreen, 0xFFA1DB68)   
         NHSTUB(rewinddir, 0xFF810B1C)                     //  ???????????????????   
         NHSTUB(rename, 0xFF836534)   
   NSTUB(RenameFile_Fut, 0xff836700)      NHSTUB(RenameFile_Fut, 0xFF836534)   
         NHSTUB(Remove, 0xFF836C84)   
   NSTUB(SetAutoShutdownTime, 0xff897628)         
   NSTUB(SetCurrentCaptureModeType, 0xff8a0618)         
   NSTUB(SetFileTimeStamp, 0xff9531a0)      NHSTUB(SetFileTimeStamp, 0xFF836EEC)   
   NSTUB(SetLogicalEventActive, 0xff8972f0)         
   NSTUB(SetParameterData, 0xff99d918)         
   NSTUB(SetPropertyCase, 0xff890f40)      NHSTUB(SetPropertyCase, 0xFF890F40)   
         NHSTUB(SetScriptMode, 0xFF897340)   
         NHSTUB(SetZoomActuatorSpeedPercent, 0xFF810B1C)   //  ???????????????????     
   NSTUB(SleepTask, 0xff83a2dc)      NHSTUB(eventproc_export_SleepTask, 0xFF83A2DC)    
         NHSTUB(SleepTask, 0xFF83A2DC)   
   NSTUB(srand, 0xff820778)         
   NSTUB(stat, 0xff836db4)      NHSTUB(stat, 0xFF836DB4)   
   NSTUB(strcat, 0xff813f5c)         
   NSTUB(strchr, 0xff813fe4)         
   NSTUB(strcmp, 0xff820638)         
   NSTUB(strcpy, 0xff820620)      NHSTUB(strcpy, 0xff820620)   
   NSTUB(strftime, 0xff8aee6c)         
   NSTUB(strlen, 0xff814030)      NHSTUB(strlen, 0xff814030)   
         NHSTUB(Strlen, 0xff814030)   
   NSTUB(strncmp, 0xff813f98)      NHSTUB(strcmp, 0xff820638)   
   NSTUB(strncpy, 0xff813f5c)         
         NHSTUB(strchr, 0xFF813FE4)    
   NSTUB(strrchr, 0xff83fd8c)      NHSTUB(strrchr, 0xFF814008)   
   NSTUB(strtol, 0xff840094)         
   NSTUB(strtolx, 0xff83fe98)         
         NHSTUB(TurnOffBackLight, 0xFF8A732C)   
         NHSTUB(TurnOnBackLight, 0xFF8A7314)   
   NSTUB(TakeSemaphore, 0xff839fa4)         
   NSTUB(time, 0xff88b238)         
         NHSTUB(TurnOffMic, 0xFF810B1C)                    //  ???????????????????   
         NHSTUB(TurnOnMic, 0xFF810B1C)                     //  ???????????????????   
   NSTUB(UnlockMainPower, 0xff897508)         
   NSTUB(UpdateMBROnFlash, 0xff813f98)      NHSTUB(UpdateMBROnFlash, 0xFF8736E8)   
         NHSTUB(UIFS_WriteFirmInfoToFile, 0xFF98A11C)    
         NSTUB(umalloc,0xFF83A658)   
         NHSTUB(UnlockAF, 0xFF838480)   
         NHSTUB(UnlockAndRefresh, 0xFFA1EDDC)    
         NHSTUB(UnsetZoomForMovie, 0xFF810B1C)    
         NHSTUB(Unmount_FileSystem, 0xFF810B1C)            //  ???????????????????   
   NSTUB(VbattGet, 0xff832ffc)      NHSTUB(VbattGet, 0xff96eae0)   
   NSTUB(vsprintf, 0xff8205e4)      NHSTUB(vsprintf, 0xFF8205E4)   
   NSTUB(write, 0xff81acdc)      NHSTUB(write, 0xff836ce0)   
   NSTUB(Write, 0xff836ce0)      NHSTUB(Write, 0xff836ce0)   
         NHSTUB(WriteSDCard, 0xFF95416C)    
Logged
*

Offline diverbert

  • *
  • 1
Re: PowerShot SX210 IS - Porting Thread
« Reply #282 on: 23 / September / 2010, 12:40:11 »
Hello

I am trying to following this thread, but.. its to complicated for me.. :/
i bought the ixus 130 with the underwater case: http://www.digitalcamerawarehouse.com.au/images/canwpdc37_bk.jpg
however.. with this case i cant use the manually white balance, cause when i start the cam in the case the 2 buttons "Disp" & "menu" are alrdy hold. and i cant use the "set", "up" & "Down" button (see at pic). a friend of mine told me thats maybe possible with CHDK.
as i understand, CHDK isnt as far for the ixus 130, is it?
will it be somehow possible with CHDK that i can (with the limited buttons) make a manually white balance and use the normale things (foto, video, makro, zoom, flash..) too?
Logged
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: PowerShot SX210 IS - Porting Thread
« Reply #283 on: 23 / September / 2010, 14:28:22 »
minor version update RC1.2.1
Solved finally the issue with the file numbers in RAW, now works in all cams, using the right
Code: [Select]
define PARAM_FILE_COUNTER      0x3A 
-> The problem is that the number you have in param debug in the osd is in decimal (58) and the number the shooting.c file expect is hex, simple things can take a lot of time.

anyway here you have it:
http://es.drop.io/chdk_sx210_rc
Binary -> CHDK-sx210is-ASM1989-RCv1.2.1.zip

Source code also uploaded:
Sources -> Sourcesx210isASM1989-RCv1.2.1.zip


@diverbert, you may better post in the ixus 130 forum, about you question could be posible if programmed so.
Logged
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: PowerShot SX210 IS - Porting Thread
« Reply #284 on: 23 / September / 2010, 15:35:52 »
Dual Screen Size

Question for the CHDK gurus :blink:,  sx210 has to difrent sets of resolutions, in most of the modes the screen is 4:3 and some of the screen size is dark and wasted,  and in video mode it changes to 16:9 and uses all the screen.

Has this happened with other cams, and its implemented already in the chdk core code????

I think that's why zebra, edge and other sutuf only "works" in video mode, but shows like 4:3 mode.
Logged
*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: PowerShot SX210 IS - Porting Thread
« Reply #285 on: 23 / September / 2010, 20:05:46 »
Quote from: asm1989 on 23 / September / 2010, 15:35:52
Dual Screen Size

Question for the CHDK gurus :blink:,  sx210 has to difrent sets of resolutions, in most of the modes the screen is 4:3 and some of the screen size is dark and wasted,  and in video mode it changes to 16:9 and uses all the screen.

Has this happened with other cams, and its implemented already in the chdk core code????

I think that's why zebra, edge and other sutuf only "works" in video mode, but shows like 4:3 mode.
If i remember correctly there are other cams with different display resolutions (maybe all cameras with HD Video?). Looks liks SD4000 does simular...

Maybe this will help us:
lib.c  (SD900 and other VxWorks cameras)
Code: [Select]
long vid_get_viewport_height() {
    return ((mode_get()&MODE_MASK) == MODE_PLAY)?240:230;
}different video buffer size for play / rec mode.
Logged
*

Offline reyalp

  • ******
  • 14082
Re: PowerShot SX210 IS - Porting Thread
« Reply #286 on: 23 / September / 2010, 22:04:46 »
Quote from: asm1989 on 23 / September / 2010, 15:35:52
Dual Screen Size

Question for the CHDK gurus :blink:,  sx210 has to difrent sets of resolutions, in most of the modes the screen is 4:3 and some of the screen size is dark and wasted,  and in video mode it changes to 16:9 and uses all the screen.

Has this happened with other cams, and its implemented already in the chdk core code????

I think that's why zebra, edge and other sutuf only "works" in video mode, but shows like 4:3 mode.
SX1 has CAM_HAS_VARIABLE_ASPECT define. This has an actual 16:9 screen like yours I think.

I thought some other cameras had this but now I'm not sure.
Logged
Don't forget what the H stands for.
*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: PowerShot SX210 IS - Porting Thread
« Reply #287 on: 24 / September / 2010, 05:53:46 »
Quote
I thought some other cameras had this but now I'm not sure.

Apart from SX1 and  p::d's SD 4000 / ixus 300 HS AFAIK there's 2 other cams being ported:
 
SD 980 / ixus 200 also has a 230k pixel 16:9 screen AND a porting thread by RaduP
and SD3500 / ixus 210 (460k pixel 16:9 screen), port recently started by Ameglin here

The recently introduced SD 4500 / ixus 1000 HS (460k pixel 16:9 screen) does not appear to be dumped yet

hope that helps,

wim

PS Apart from the well-known dpreview, this is a decent source for specs & reviews
« Last Edit: 24 / September / 2010, 06:03:13 by whim »
Logged
*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: PowerShot SX210 IS - Porting Thread
« Reply #288 on: 24 / September / 2010, 08:56:43 »
Thanks all for the kick start Info, I will get into it,

The first discovery is that PROPCASE_ASPECT_RATIO  in propset3.h seams to be wrong, at least in this camera,

propest 294 , has nothing to do with it,

find it here:
Code: [Select]
#define PROPCASE_ASPECT_RATIO          215
value is 1 in all the modes and 0 in video mode (16:9)

must be verified with other propset3 cams with 16:9 and 4:3


Also y Think  CAM_USES_ASPECT_CORRECTION in gui_draw.c maybe is not ready for this ,

I mean aspect correction and aspect ratio at the same time, since sx1 for example dont use aspect correction

for example this comments from nanodiode:
Code: [Select]
//     the default mapping is x=x (NOTE: I think important to check that on every model, and necessary in newer models. it seems to me very strange screen sizes of 360x240 for 4/3 and 480/240 for 16/9 (SX1S).
« Last Edit: 24 / September / 2010, 09:18:59 by asm1989 »
Logged
*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: PowerShot SX210 IS - Porting Thread
« Reply #289 on: 24 / September / 2010, 19:39:28 »
Quote from: asm1989 on 24 / September / 2010, 08:56:43
Code: [Select]
#define PROPCASE_ASPECT_RATIO          215value is 1 in all the modes and 0 in video mode (16:9)

must be verified with other propset3 cams with 16:9 and 4:3
Same on SD4000.

Propset 215
Power on (Play Mode) = 1
Picture Auto & Manual = 1
Video = 0
Switch back to play = last value in Record Mode

Propset 294
Power on (Play Mode) = 1
Picture Manual = 0
Picture Auto = 1
Video = 0
Switch back to play = last value in Record Mode
Logged
Pages: 1 ... 24 25 26 27 28 [29] 30 31 32 33 34 ... 59   Go Up
« previous next »
 

Related Topics