IXUS160/ELPH160 Porting attempt - page 15 - DryOS Development - CHDK Forum

IXUS160/ELPH160 Porting attempt

  • 497 Replies
  • 174356 Views
*

Offline adong

  • **
  • 66
Re: IXUS160/ELPH160 Porting attempt
« Reply #140 on: 25 / July / 2015, 12:13:51 »
Advertisements
Hmm I'm pretty sure it's in caps in the source, so maybe you didn't download it properly ?
Anyway, I'll try to find some time this weekend to enable the video button and I'll call it a day for this port :)

*

Offline appas

  • *
  • 10
Re: IXUS160/ELPH160 Porting attempt
« Reply #141 on: 26 / July / 2015, 10:50:57 »
Hi all!
I have an IXUS 170, and I was wondering if any of your fine work would be adaptable for that camera? I've opened a new thread for this effort, and welcome any pointers on how to get started.

*

Offline nafraf

  • *****
  • 1308
Re: IXUS160/ELPH160 Porting attempt
« Reply #142 on: 26 / July / 2015, 12:00:21 »
Hmm I'm pretty sure it's in caps in the source, so maybe you didn't download it properly ?
Yes, your source was right. I found a bug in my working copy. Now it compiles without problem.

Re: IXUS160/ELPH160 Porting attempt
« Reply #143 on: 26 / July / 2015, 12:04:36 »
Hi all,
 I am new to CHDK so I might be doing something wrong.
 I got CHDK running, but had to use 2 partions as the IXUS does not want to boot from fat32. However, it doesn't recognize the two partitions. I am testing this on the ixus160 under Linux with a 16GB SDcard (lexar class 10).

Here are the steps so far:
0. Stick did not work on my system (did not properly recognize the SDcard), so I had to resort to licks. 
1. I first tried a single fat32 partition. The camera did not want to boot from a fat32 partition, so I had to create 2 partitions, one fat16 and one fat32.
2. Licks made a 16MB fat16 partition, with DISKBOOT.bin on it and it put the CHDK dir on the large fat32 partition
3. After booting the camera, it complained of a missing module.
4. After I copied the CHDK dir to the first partition it works,
Errors so far:
5. When I browse the CHDK menu, it is constantly drawn over by the image the camera is currently aimed at.
6. When I just boot up the camera, and start shooting, it puts the images on the small boot partition and not on the bigger data partition.

Any help?


IXUS160/ELPH160 Porting attempt
« Reply #144 on: 26 / July / 2015, 12:43:53 »
Cameras that do not need to use dual partitions (i.e newer ones) typically do not have support for them.  You need to figure out why you are not able to boot from a FAT32 partition

http://chdk.wikia.com/wiki/EOScard might help?

The screen overwrite problem you see is normal for most CHDK ports. It tends to be less of a problem in playback mode. Turning off focus or face tracking also helps.
« Last Edit: 26 / July / 2015, 12:59:04 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: IXUS160/ELPH160 Porting attempt
« Reply #145 on: 01 / August / 2015, 09:52:42 »
Because of the dual partition the disk became full quite quickly. When that happened the camera flashed a message and crashed. The  crash caused the lens to extend to far and it developed the infamous canon lens error... I was lucky in fixing that, but a second attempt to boot chdk bricked it completely...

So there is possibly an error in the code when there is no space left on the card...

*

Offline srsa_4c

  • ******
  • 4426
Re: IXUS160/ELPH160 Porting attempt
« Reply #146 on: 01 / August / 2015, 10:30:28 »
Because of the dual partition the disk became full quite quickly.
As waterwingz mentioned, new ports no longer support dual partitions.
You mentioned Licks, so I assume you're on Linux. If all utilities fail, you can make a card bootable manually, see the Linux section(s) here: http://chdk.wikia.com/wiki/Prepare_your_SD_card
Quote
So there is possibly an error in the code when there is no space left on the card...
I think I have encountered issues when the card is almost full and CHDK RAW is enabled: in this case, the Canon firmware may encounter an unexpected out-of-space situation which triggers a Canon error. That may have been the crash you were experiencing.

I assume that the crash itself did not cause the lens to move.
When you tried re-starting the cam afterwards, the camera tried to retract the lens, but it failed.
Quote
I was lucky in fixing that, but a second attempt to boot chdk bricked it completely...
Can you detail what happened at that second attempt and what does the "completely" bricked camera do since then?

*

Offline srsa_4c

  • ******
  • 4426
Re: IXUS160/ELPH160 Porting attempt
« Reply #147 on: 01 / August / 2015, 10:55:14 »
@adong or anybody else with the camera
I have a few requests and suggestions.

- Can somebody test the camera in playback mode with chdkptp? Do you get the same image as the one on the LCD?
- Please run the hooktest script in P mode and in "Digital IS" mode. The script's description is here.

If you get bad display in the chdkptp test, try replacing

Code: [Select]
// guessed from sub_FF84E884
DEF(viewport_fb_d, 0x00003314)
with
Code: [Select]
// 0xff883c54 (0x32d4), 0xff883c90 (0x54); see ixus140 0xff0a7858, 0xff0a7890
DEF(viewport_fb_d, 0x00003328)
in stubs_min.S .

I think 0x3314 is an eventflag (0x32d4 + 0x40, see the code right before 0xff883074).


*

Offline nafraf

  • *****
  • 1308
Re: IXUS160/ELPH160 Porting attempt
« Reply #148 on: 01 / August / 2015, 12:43:01 »
Your suggestion fixed playback mode with chdkptp. Thanks.

hooktest script fails. Log files in attachments.

Additionally, there is a bug with power up mode detection, camera always start up on REC mode.

EDIT: Source code committed to SVN to facilitate further development (trunk r4197) but it is not included in autobuild.
« Last Edit: 01 / August / 2015, 13:08:43 by nafraf »

*

Online reyalp

  • ******
  • 13450
Re: IXUS160/ELPH160 Porting attempt
« Reply #149 on: 01 / August / 2015, 15:10:51 »
hooktest script fails. Log files in attachments.
P mode looks OK, exp counter started at 3, reset to 1 at first shot. All other tests passed.

Digital IS looks like raw hook is not being called. shoot() shoots twice, raw hook always times out. remote hook is also not called.

Don't forget what the H stands for.

 

Related Topics