ELPH 340 (IXUS 265) - page 3 - DryOS Development - CHDK Forum supplierdeeply

ELPH 340 (IXUS 265)

  • 97 Replies
  • 45918 Views
Re: ELPH 340 (IXUS 265)
« Reply #20 on: 10 / July / 2014, 05:13:30 »
Advertisements
Ixus 265 Porting Progress Report #3.

General Porting Progress:-

* Up Dated some more easy stuff. [Re; 1.3496.0]
* To Do, stuff in Post's #17 and #18
* Aim is to just get a compiled version and not a boot-able version

Ixus 265-100a, Porting Progress

Version #3 and Log Attached

I am still struggling with the errors and to shut-up the compiler.

H-H
« Last Edit: 11 / November / 2014, 18:13:03 by Hardware_Hacker »

*

Offline srsa_4c

  • ******
  • 4082
Re: ELPH 340 (IXUS 265)
« Reply #21 on: 11 / July / 2014, 18:55:01 »
A partial boot.c is attached. It was done with CHDK-PT, loosely following the sx510 port. The functions are copied straight from CHDK-PT, indentation and comments show where the changes and additions are. I hope it's enough for a "hint".
Quote
main.c: In function 'startup':
main.c:19: error: '_end' undeclared (first use in this function)
See http://chdk.setepontos.com/index.php?topic=11212.msg109996#msg109996
Pull a new svn copy and insert your files into it.

I'd highly recommend using code_gen to make the C task files.
I would also recommend this, but convincing H-H seems rather hard. I think he'd also have to use the command line as code_gen is probably not supported from the GUI.

Re: ELPH 340 (IXUS 265)
« Reply #22 on: 15 / July / 2014, 17:45:45 »
A partial boot.c is attached. It was done with CHDK-PT, loosely following the sx510 port. The functions are copied straight from CHDK-PT, indentation and comments show where the changes and additions are. I hope it's enough for a "hint".

Continued from here http://chdk.setepontos.com/index.php?topic=11689.msg114537#msg114537

Thanks for partial boot.c

Compiling Issue was due to some sort of "Cleaning" issue as NO CHDK camera would complie successufly.
Wiped every thing and started afresh.

Re:- "hint" Ive got your hint but there is one basic point I am still confused on:-

Some Brief History:-

* Original Firmware Dump for Ixus 265.
* Compile Sig-find error.
* DumpF, then Edited, "-10000"
* DumpF_Edited used to produce, incorrect, Versions #1, #2 and #3
* CHDK Version then changed to CHDK_3496 which  fixed Compile Sig-find error.
* Reverting back to DumpF.....

DumpF is the only version of the three that aligns correctly with your boot.c
DumpF also aligns correctly with the new ELPH 340 Dump.

BUT it appears, to me, to have a hard firmware coded backward reference. ???

So

# Which is the correct version that I should continue with.
# What is the correct CHDK value for the ROM start.
# Is the backward reference important.

H-H
« Last Edit: 16 / July / 2014, 01:33:53 by Hardware_Hacker »

*

Offline srsa_4c

  • ******
  • 4082
Re: ELPH 340 (IXUS 265)
« Reply #23 on: 15 / July / 2014, 18:51:27 »
So

# Which is the correct version that I should continue with.
Since you now have the camera, you can use the current Canon Basic dumper script to make a dump that the CHDK tools expect, or you can just use rkomar's dump. Note that the script will dump the ROM from address 0xff010000, because the first 0x10000 bytes are worthless from CHDK perspective.
Quote
# What is the correct CHDK value for the ROM start.
ROMBASEADDR should be 0xff010000 (in platform/ixus265_elph340/sub/100a/makefile.inc). The actual firmware starts at 0xff020000 in ROM. You can see in my partial boot.c that boot() starts at 0xFF02000C.
Quote
# Is the backward reference important.
I don't quite understand what you're referring to. You might be confused by the mentioned addresses, so again:
0xff000000 is where the camera's ROM starts
0xff010000 is where the bootloader starts
0xff020000 is the start of the main firmware. All the ROM addresses you'll encounter during porting are above 0xff020000.


Re: ELPH 340 (IXUS 265)
« Reply #24 on: 15 / July / 2014, 20:16:37 »
Thanks, ... Will continue using rkomar's dump.

H-H

Re: ELPH 340 (IXUS 265)
« Reply #25 on: 15 / July / 2014, 21:00:29 »
Thanks, ... Will continue using rkomar's dump.

H-H

And hurry up, will ya?  I'm waiting!

 :lol

Re: ELPH 340 (IXUS 265)
« Reply #26 on: 15 / July / 2014, 22:23:50 »

And hurry up, will ya?  I'm waiting!

 :lol

Thanks for the ELPH 340 Dump

Is there any reason why you chose the ELPH 340 of other Canon Models ???

H-H

As I only have a invalid certificate of incompetence, .... I am Proceeding Slowly ????
« Last Edit: 15 / July / 2014, 22:25:40 by Hardware_Hacker »

Re: ELPH 340 (IXUS 265)
« Reply #27 on: 15 / July / 2014, 22:43:17 »
Thanks for the ELPH 340 Dump

Is there any reason why you chose the ELPH 340 of other Canon Models ???

H-H

As I only have a invalid certificate of incompetence, .... I am Proceeding Slowly ????

I chose it because it is HS, and you recommended it over the cheaper CCD options.  It also has 16MP, and was on sale for $180.  I can't do a good comparison with my A4000 cameras until CHDK is working on the 340HS, but for handheld shots, it does seem to perform a bit better.  I took some pictures of a flat page, and the focus seems better.


Re: ELPH 340 (IXUS 265)
« Reply #28 on: 15 / July / 2014, 23:23:06 »
I took some pictures of a flat page, and the focus seems better.

Any Pictures of your steup or  rig available

H-H

Re: ELPH 340 (IXUS 265)
« Reply #29 on: 16 / July / 2014, 00:49:59 »
So # Which is the correct version that I should continue with.
Quote
# Is the backward reference important.
0xff020000 is the start of the main firmware. All the ROM addresses you'll encounter during porting are above 0xff020000.

See the Attached ..... BackwardReference.png

H-H

 

Related Topics