IXUS 170 Porting - page 9 - General Discussion and Assistance - CHDK Forum supplierdeeply

IXUS 170 Porting

  • 87 Replies
  • 51890 Views
Re: IXUS 170 Porting
« Reply #80 on: 03 / August / 2022, 18:14:45 »
Advertisements
Can this port be released officially? That would makes things a lot easier (such as the stick utility being able to download the fw automatically).
It would be helpful if you can test whatever you are able to from https://chdk.fandom.com/wiki/Testing and report any issues.


@Caefix: Is the build you posted from the current trunk unmodified, or does it have your own changes? Generally, if you post a build you should say, and this is especially important if johnnybgoode is testing.

Also, you posted some changes earlier in https://chdk.setepontos.com/index.php?topic=12471.msg147233#msg147233 but I do not understand the changes or what issue they are supposed to address, and AFAIK they were never added. If there are specific problems with this port you are aware of, please described them.

Yes i will help wherever i can. Should i run with this firmware or wait until it is clear if this is a build from the autobuild server or a custom build?

*

Offline reyalp

  • ******
  • 14098
Re: IXUS 170 Porting
« Reply #81 on: 03 / August / 2022, 20:43:37 »
Yes i will help wherever i can. Should i run with this firmware or wait until it is clear if this is a build from the autobuild server or a custom build?
Please use the attached build from the current trunk.
Don't forget what the H stands for.

Re: IXUS 170 Porting
« Reply #82 on: 25 / December / 2022, 10:27:22 »
I have been using this latest build and did not find any problems. I'm not a very advanced user, but basic functionality is all there, raw files (dng) seem to be ok now. You have my blessing  :)

Re: IXUS 170 Porting
« Reply #83 on: 09 / April / 2023, 09:41:03 »
Hello,

I would like to port my IXUS 172 on CHDK and would like to know to which place I should start ?
Is it only a copy of the IXUS 170 rebranded ?
 
It seems it's a Switzerland specific model but I would like to test more my assumption before doing development effort.

EDIT

* HEX P-ID is identical between IXUS 170 and IXUS 172, entry point is the same in the CDUMPER.LOG

Quote
Started
FF810000 dry
done

Will try to build the lastest IXUS170 CHDK build on IXUS172 and will see what is going on.
Where can I upload the firmware dump of the IXUS172 ?

From what I see a major part of the dumped firmware on IXUS 172 and IXUS170 are identical, I'll now try to understand what is happening on the IXUS 172 that make the difference, from what I've seen on the hardware level it seems identical, however I cannot find a specification for the IXUS 172.

Thanks a lot,
hellgheast.
« Last Edit: 09 / April / 2023, 12:48:19 by hellgheast »


*

Offline reyalp

  • ******
  • 14098
Re: IXUS 170 Porting
« Reply #84 on: 09 / April / 2023, 14:21:35 »
Hello,

I would like to port my IXUS 172 on CHDK and would like to know to which place I should start ?
Is it only a copy of the IXUS 170 rebranded ?

It seems it's a Switzerland specific model but I would like to test more my assumption before doing development effort.
It's not listed in Canon's camera museum, which does suggest  it might be a simple rebadge (but why?) https://global.canon/en/c-museum/camera.html?s=dcc

Quote
* HEX P-ID is identical between IXUS 170 and IXUS 172, entry point is the same in the CDUMPER.LOG

Quote
Started
FF810000 dry
done

Will try to build the lastest IXUS170 CHDK build on IXUS172 and will see what is going on.
Note the firmware version could be different even if it's actually same model (e.g. 100b instead of 100a) . You can check the dump for a string like GM1...
Quote
Where can I upload the firmware dump of the IXUS172 ?
Any file hosting site like google drive, dropbox, box.com etc

If you are able to build CHDK, you can do the following:
put your ixus172 dump in the platform/sub/100a directory as PRIMARY.BIN
run make PLATFORM=ixus170_elph170 PLATFORMSUB=100a rebuild-stubs
Compare the resulting stubs_entry.S and funcs_by_address.csv with the original from SVN. If you did and svn checkout, you can just do svn diff.

If any function or variable addresses in stubs are different, a new port is needed.

If there are no differences in function and variable addresses, the build should be compatible. Since the PID is also the same, a CHDK build for the same firmware version should also work. If the firmware version is different (not 100a) then you need to make a new copied sub (like ixus140_elph130 100b) or disable the compatibility check.

« Last Edit: 09 / April / 2023, 16:51:57 by reyalp »
Don't forget what the H stands for.

Re: IXUS 170 Porting
« Reply #85 on: 09 / April / 2023, 14:54:43 »
Hello,

For what I've checked (inside the dump and with ACID) the firmware version is 100a.
I've not been able to find any special information about the difference betweem 170 and 172.

EDIT : Product ID between IXUS 170 and IXUS 172 is identical --> PID_32AC.
The difference i've seen in the USB description is the mention that's it's Revision 2

Quote
Extracted from windows registry.

USB\VID_04A9&PID_32AC&REV_0002
USB\VID_04A9&PID_32AC

Here's the firmware dump IXUS172_100a.

https://www.swisstransfer.com/d/7a99c1d2-ddf4-451b-a961-c785c808a504

EDIT:
* IXUS 170 and IXUS 172 are identical by putting the PRIMARY.BIN of IXUS172 in the folder of the IXUS170, only the name changes in the stubs
« Last Edit: 09 / April / 2023, 15:21:30 by hellgheast »

Re: IXUS 170 Porting
« Reply #86 on: 09 / April / 2023, 19:10:01 »
Hello,

I was able to build the firmware for CHDK for IXUS 170/172, what's the next step to flash CHDK on the SD Card with a built firmware ?

Thanks a lot,
hellgheast.

*

Offline Caefix

  • *****
  • 946
  • Sorry, busy deleting test shots...
All lifetime is a loan from eternity.


 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal