SX60HS Porting - page 10 - DryOS Development - CHDK Forum  

SX60HS Porting

  • 915 Replies
  • 238638 Views
Re: SX60HS Porting
« Reply #90 on: 23 / March / 2016, 17:09:40 »
Advertisements
Some how by booting without lock and then with lock I got the EVF to activate
this shows 0x141000 in the dump. You can see some red lines near the top which are chdk trying to write ERROR:MISSING MODULES (easily confirmed by moving the slider from 640 to 736) (this varies as it starts up, first two garbled bars, one near the center presumeably displaying CHDK version info), So is CHDK getting the wrong address, or some other info incorrectly?

at 0x153E200 the pure CANON screen is visible without the lines

posting the dump

https://drive.google.com/open?id=0ByFsa83WedojTWk1RVlyZGpWLVE

Now I suppose I'll try this again on the LCD and see if I can get the same sort of screen to appear.

*

Offline srsa_4c

  • ******
  • 4262
Re: SX60HS Porting
« Reply #91 on: 23 / March / 2016, 17:16:00 »
So is CHDK getting the wrong address, or some other info incorrectly?
No, the buffer address is probably right. You need these in platform_camera.h though:
Code: [Select]
    #undef  CAM_BITMAP_WIDTH
    #undef  CAM_BITMAP_HEIGHT
    #undef  CAM_SCREEN_WIDTH
    #undef  CAM_SCREEN_HEIGHT
    #define CAM_BITMAP_WIDTH                    640
    #define CAM_BITMAP_HEIGHT                   480
    #define CAM_SCREEN_WIDTH                    640
    #define CAM_SCREEN_HEIGHT                   480

Re: SX60HS Porting
« Reply #92 on: 23 / March / 2016, 17:19:18 »
Did this for the LCD, with an ICON saying unidentified image.

0144100 shows some red lines near the top, and the words UNIDENTIFIED IMAGE but not the graphical ICON
0153E200 shows the same, but also in the middle lines the version info of CHDK is visible when moving the slider to 736....
So the graphics for the ICON that was visible has gone missing, or is somewhere else

Re: SX60HS Porting
« Reply #93 on: 23 / March / 2016, 17:22:08 »
So is CHDK getting the wrong address, or some other info incorrectly?
No, the buffer address is probably right. You need these in platform_camera.h though:
Code: [Select]
    #undef  CAM_BITMAP_WIDTH
    #undef  CAM_BITMAP_HEIGHT
    #undef  CAM_SCREEN_WIDTH
    #undef  CAM_SCREEN_HEIGHT
    #define CAM_BITMAP_WIDTH                    640
    #define CAM_BITMAP_HEIGHT                   480
    #define CAM_SCREEN_WIDTH                    640
    #define CAM_SCREEN_HEIGHT                   480

YES
    #define CAM_BITMAP_WIDTH                    640 // Actual width of bitmap screen in <s>bytes</s> pixels
    #define CAM_BITMAP_HEIGHT                   480 // Actual height of bitmap screen in rows
    #define CAM_SCREEN_WIDTH                    640// Width of bitmap screen in CHDK co-ordinates (360 or 480)
    #define CAM_SCREEN_HEIGHT                   480 // Height of bitmap screen in CHDK co-ordinates (always 240 on all cameras so far)
//    #define CAM_SUPPORT_BITMAP_RES_CHANGE         1
    #undef CAM_SUPPORT_BITMAP_RES_CHANGE


*

Offline srsa_4c

  • ******
  • 4262
Re: SX60HS Porting
« Reply #94 on: 23 / March / 2016, 17:29:13 »
YES
So, the attached files are for the build you're running right now, but the CHDK display is still 736 pixels wide? You must be picking up 736 from somewhere. edit: Or, you're running an older build.

So the graphics for the ICON that was visible has gone missing, or is somewhere else
It might be in the "other" (not overlay) buffer.

Re: SX60HS Porting
« Reply #95 on: 23 / March / 2016, 17:38:49 »
Here's the dump of the above run
   
https://drive.google.com/open?id=0ByFsa83WedojTXlrMzBuZmFGbDQ

The build is correct....must be picking it up somewhere...maybe programatically in some part of lib.c that I copied....I've watched the dump size increase for example. I'll make clean and make fir again just in case

checking more.

Re: SX60HS Porting
« Reply #96 on: 23 / March / 2016, 17:55:28 »
That was it. make clean.  Had to compile finsig_thumb2.c by hand because of include problems....
Apparently modifying platform_camera.h, does not trigger a recompile of lib.c because it is only included indirectly in lib.c via platform.h.

Does that make sense? now things appear properly albeit, in a rather small font...

https://drive.google.com/open?id=0ByFsa83WedojY2ZPbGptNXhhekE

I've attached a screen shot of -x0153e200

now what should i focus on?  :)

Re: SX60HS Porting
« Reply #97 on: 23 / March / 2016, 19:53:08 »
I got chdkptp to work and connect to the camera.  I can also use gphoto to see files on the camera under linux. I am completely inexperienced with lua scripting.  It seems that most commands like 'ls' or file transfer in chdkptp return with "compile error" so I must need to build or install something on the camera side i think. There must be a tutorial on this somewhere.


Re: SX60HS Porting
« Reply #98 on: 23 / March / 2016, 21:29:25 »
There must be a tutorial on this somewhere.
The  USAGE.TXT file in your chdkptp trunk directory might be a place to start?  A bit terse but it covers most of what you will need to know.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 12690
Re: SX60HS Porting
« Reply #99 on: 23 / March / 2016, 21:59:22 »
I got chdkptp to work and connect to the camera.  I can also use gphoto to see files on the camera under linux. I am completely inexperienced with lua scripting.  It seems that most commands like 'ls' or file transfer in chdkptp return with "compile error" so I must need to build or install something on the camera side i think. There must be a tutorial on this somewhere.
As I mentioned, you need kdb_task running for anything involving lua script to work (this isn't obvious, but all CHDK scripting runs in kdb_task).

You also need the modules files in CHDK/MODULES. These should be updated any time you build anyway.

without kbd_task, you should be able to use the rmem to read memory from the camera, and the download and upload commands with the -nolua option.

The help command will give you a list of chdkptp commands, or details of a specific command, but again, most camera commands will be broken until you have kbd_task working.
Don't forget what the H stands for.

 

Related Topics