ELPH 110 HS (IXUS 125 HS) Porting Thread - page 7 - DryOS Development - CHDK Forum supplierdeeply

ELPH 110 HS (IXUS 125 HS) Porting Thread

  • 246 Replies
  • 102613 Views
*

Offline nafraf

  • *****
  • 1308
Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #60 on: 09 / March / 2013, 08:12:59 »
Advertisements
Not to intrude here, but a bit of attention to the posting conventions of this forum when quoting text would help many of us follow this thread and maybe contribute?
I agree.  To follow Hardware-Hacker's post is not easy.

I Noted, but ignored, a Long list of warnings.

Should I be using a newer version of Gcc ?.
What kind of warnings? Could you post a log?

Quote
Please check the power-up button behavior:-

A short tap -> camera turns on in PLAY mode. [A Quick Test = Ok]

Long press -> camera turns on in REC mode. [A Quick Test = Ok]
OK, power-up button tested.

Quote
Some known issues:-

* Colors are wrong.      CHDK Logo Orange [But, Not yet Tested]
 
If you post a image of palette in REC and PLAY mode would be possible to use LOAD_CUSTOM_COLORS.
Lakeroe send LCD screen photos to me, please test colors with nafraf- Rev 280

Quote
* RAW is not working, please test it with Rev 276 [A Quick-Quick, Test = "May Be but not Sure"]
Please try to create badpixel.com

Quote
Attached:- Ixus 125-100e & Digi-5  #4

Someting I previously noted, so It may have been changed, Should the The "125-xxx" Reference:-

#1/ Digi5 Property's [?]

#2/ DryOS Rel 47 [?]

#3/ DryOS Rel 50 [?]
Could you explain this better?

thanks

Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #61 on: 11 / March / 2013, 03:55:51 »
Hi All,

Re: ELPH 110 HS (IXUS 125 HS) Porting Thread & Post #60

Attached Files:-

# 60 Response

IXUS125-100e Testing the Blind Port


thanks

H-H

Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #62 on: 12 / March / 2013, 04:18:58 »
Hi all,

Ixus 125-100e Build N.... TRUNK-1.2.2621.281 ok

Boots ok

Runs ok

TRUNK-1.2.2621.281, Mods, But only to try to find these:-


Ixus 125-xxx Mode Map porting progress -=+ NEWS +=-

Found up to 10 Additional Modes [with Working Icons]

But not yet fully tested


 1/ Tv      = Icon Ok

 2/ Av      = Icon Ok

 3/ M      = "Invisible" Icon Ok

 4/ Video Std   = Icon Ok

 5/ Hi S Burst   = Icon Ok

 6/ "ToDo"   = Icon Ok

 7/ U. Water   = Icon Ok

 8/ Colour A.   = Icon Ok

 9/ Night....   = Icon Ok

10/ "ToDo"   = Icon Ok

-=-=-=-=-

A/ More testing is required for these.

B/ ToDo Cross check Modes against "icons" in Ixus 125 users Manual.pdf

C/ Badpixel.bin, Ran, .... Messages, .... etc. But I did not fully test this.

Logs Attached:-

#1 Ixus 125-281 errors #1

H-H

Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #63 on: 12 / March / 2013, 04:31:49 »
Hi all,

Ixus 125-100e Build N.... TRUNK-1.2.2621.281 ok

More Logs Attached:-

#2 log-Ixus125_elph110hs-100e-281 #1

H-H


Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #64 on: 12 / March / 2013, 10:20:54 »
Hello.

I haven't visit this forum for some time now since my last post here

Again: I'm willing to help with testing. So please tell me what I have to do.

The firmware of my camera is 101a.

Cheers

*

Offline nafraf

  • *****
  • 1308
Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #65 on: 12 / March / 2013, 10:49:35 »
@HardwareHacker
In your logfile I found three messages, but they don't seem to be problem.

Code: [Select]
-> signatures_vxworks.h
CAUTION! Signature generation is turned off!
If you check tools/Makefile, you will see the cause of warnings.
It depends on OPT_GEN_SIGS value, defined in buildconf.inc.  But you are compiling for dryos camera, I don't see problem.

Code: [Select]
-> signatures_dryos.h
CAUTION! Signature generation is turned off!
If you want to remove this.. OPT_GEN_SIGS=1 should solve it.

Code: [Select]
-> stubs_entry.S
CAUTION! 'stubs_entry.S' is not updated due to target firmware binary not found!
It seems that you don't have platform/ixus125_elph110hs/sub/100e/PRIMARY.BIN
Then, stubs_entry.S can't be updated

*

Offline MKR

  • *
  • 11
Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #66 on: 12 / March / 2013, 12:35:47 »


This black bar appears in all DNG files. The camera crops it out when producing the JPG file, so I'm assuming the engineers at Canon omitted a handful of pixels in the sensor on purpose. It appears in UFRaw and RawTherapee, so I don't think it's the software. Does anyone have insights on this?

edit: I found a thread on an identical phenomenon with another camera: http://forums.dpreview.com/forums/thread/2878810
« Last Edit: 12 / March / 2013, 12:40:42 by MKR »

*

Offline nafraf

  • *****
  • 1308
Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #67 on: 12 / March / 2013, 13:23:54 »
Again: I'm willing to help with testing. So please tell me what I have to do.

I sent you a PM with the link to CHDK for IXUS125 101a.
To load it, it is necessary to use bootable sd card method.

That version has been tested by MKR, something to do/to test:
- Test Video quality override
- Test Long Exposure
- Complete Modemap table
- Detect led_table[] indexes.

Thanks

Please test and report.


Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #68 on: 12 / March / 2013, 14:58:08 »
Hello,


I managed now to boot.

I will try the first two points in the next fours or tomorrow.

However I do not know what the last two point are... Some hint please?

Cheers

*

Offline nafraf

  • *****
  • 1308
Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #69 on: 12 / March / 2013, 15:08:32 »
However I do not know what the last two point are... Some hint please?
In source code, we have these warnings related to modemap table:
Code: [Select]
// Check of modemap from 'platform/CAMERA/shooting.c':
// Firmware modemap table found @ff0841bc -> ff080a6c -> ff1ca4f0 -> ff333640 -> ff5e8cf0
// Mode 33329 in firmware but not in current modemap
// Mode 33332 in firmware but not in current modemap
// Mode 33313 in firmware but not in current modemap
// Mode 33298 in firmware but not in current modemap
// Mode 32796 in firmware but not in current modemap
// Mode 32776 in firmware but not in current modemap

There are two option to detect those values:
* Follow instructions here: http://chdk.wikia.com/wiki/Adding_support_for_a_new_camera  section modemap[] in platform/<camera>/shooting.c.

*Use set_capture_mode_canon script command to identify the modes.  You can use script running in your camera, or execute command from using chdkptp and see what happens :)
Something like this:
Code: [Select]
$chdkptp -i -c
connected: Canon PowerShot xxxxxxx
con> rec                     
con 1> =set_capture_mode_canon(32796)
32796 is the mode to test.

 

Related Topics