IXUS145/ELPH135 Porting attempt - page 4 - DryOS Development - CHDK Forum supplierdeeply

IXUS145/ELPH135 Porting attempt

  • 136 Replies
  • 63696 Views
*

Offline akira

  • *
  • 19
Re: IXUS145/ELPH135 Porting attempt
« Reply #30 on: 08 / January / 2015, 14:50:32 »
Advertisements
Tried

Code: [Select]
   #undef  CAM_BITMAP_WIDTH
    #define CAM_BITMAP_WIDTH                          960 // Actual width of bitmap screen in bytes (may be larger than displayed area)
    #undef  CAM_BITMAP_HEIGHT
    #define CAM_BITMAP_HEIGHT                         270 // Actual height of bitmap screen in rows (240 or 270)

And:
Code: [Select]
    #undef  CAM_BITMAP_HEIGHT
    #define CAM_BITMAP_HEIGHT               240
    #undef  CAM_BITMAP_WIDTH
    #define CAM_BITMAP_WIDTH                1080

The only that worked:
Code: [Select]
    #undef  CAM_BITMAP_HEIGHT
    #define CAM_BITMAP_HEIGHT               360
    #undef  CAM_BITMAP_WIDTH
    #define CAM_BITMAP_WIDTH                720

It seems that the correct height is 360, and any change in the width mess the things up.

*

Offline srsa_4c

  • ******
  • 4426
Re: IXUS145/ELPH135 Porting attempt
« Reply #31 on: 08 / January / 2015, 17:19:04 »
It seems that the correct height is 360, and any change in the width mess the things up.
Well, 720*360 == 960*270.
The 960 * 270 buffer size is related to full HD resolution (even if the camera doesn't have HDMI connector). I have a partial RAM dump from an Ixus265 camera which also has these buffer dimensions. That model uses a 720*240 sized area from the buffer in LCD mode (see attached image).
To confirm this visually, you could dump the first 8MB of RAM with the built-in RAM dumper (it's in the Debug menu, you also need to set "debug shortcut" to DmpRAM, leave the menu then press DISP(?) in ALT mode) then use a utility that can visualize binary data, such as Hexplorer (or its hacked version).

edit:
I'm always confused about what the "debug shortcut" is on various cameras. Try removing
#undef  CAM_HAS_DISP_BUTTON
from platform_camera.h. That should make the disp (down?) button the debug shortcut.
« Last Edit: 08 / January / 2015, 17:26:54 by srsa_4c »

*

Offline akira

  • *
  • 19
Re: IXUS145/ELPH135 Porting attempt
« Reply #32 on: 12 / January / 2015, 16:51:55 »
Hi,

Quote
Well, 720*360 == 960*270.
Sure, but any witdth different than 720 make the each subsequent line to be shifted (attached).

Regarding to the palette, I think it worked, I was able to change the menus, less the initial logo and Alt menu.

Regards

*

Offline srsa_4c

  • ******
  • 4426
Re: IXUS145/ELPH135 Porting attempt
« Reply #33 on: 13 / January / 2015, 18:23:25 »
Hi,

Quote
Well, 720*360 == 960*270.
Sure, but any witdth different than 720 make the each subsequent line to be shifted (attached).
I understand. I'd suggest you to fix the issue by redefining those #defines (I mentioned previously where to look), and remove changes from CHDK core.
Quote
Regarding to the palette, I think it worked, I was able to change the menus, less the initial logo and Alt menu.
If you made the palette working, you should be able to see the CHDK custom color block in the palette viewer. Since the palette override doesn't start instantly at startup, the splash screen may be shown in white for a few moments.
If you think there's a problem with the palette, show your changes and show screenshots of the palette viewer in playback and record mode.


*

Offline srsa_4c

  • ******
  • 4426
Re: IXUS145/ELPH135 Porting attempt
« Reply #34 on: 14 / January / 2015, 17:14:43 »
@akira
Can you please run the cpuinfo module? (Browse into CHDK/MODULES with the file browser, highlight cpuinfo.flt and press SET.) It will create a file with some information about the ARM CPU in the camera. I'm curious how different the ARM core of DIGIC4+ is from DIGIC 4 and 5.

*

Offline akira

  • *
  • 19
Re: IXUS145/ELPH135 Porting attempt
« Reply #35 on: 16 / January / 2015, 09:12:43 »
Hi,

Sorry for the delay, little busy on the "former" job  :(

Quote
Can you please run the cpuinfo module? (Browse into CHDK/MODULES with the file browser, highlight cpuinfo.flt and press SET.) It will create a file with some information about the ARM CPU in the camera. I'm curious how different the ARM core of DIGIC4+ is from DIGIC 4 and 5

Follow attached


Regards

*

Offline srsa_4c

  • ******
  • 4426
Re: IXUS145/ELPH135 Porting attempt
« Reply #36 on: 16 / January / 2015, 15:27:16 »
Follow attached
Thanks. The CPU has the same configuration as DIGIC 4, caches are 8k.
I linked your post here: Getting CPU configuration from CP15.

Re: IXUS145/ELPH135 Porting attempt
« Reply #37 on: 28 / January / 2015, 10:56:39 »
Hello, I own a Canon IXUS 145. It's a good camera and I'm looking forward for CHDK for it. Thank you for working on it :D

Are there any more news about CHDK for this camera?
« Last Edit: 30 / January / 2015, 13:40:46 by bgmx »


*

Offline akira

  • *
  • 19
Re: IXUS145/ELPH135 Porting attempt
« Reply #38 on: 10 / February / 2015, 11:46:28 »
Sorry, but no progress, lack of time    :(

Re: IXUS145/ELPH135 Porting attempt
« Reply #39 on: 21 / February / 2015, 07:33:34 »
Thank you very much for your attempt to port CHDK Akira !

 

Related Topics