IXUS 240/ELPH 320 HS Porting thread - page 25 - DryOS Development - CHDK Forum supplierdeeply

IXUS 240/ELPH 320 HS Porting thread

  • 286 Replies
  • 68791 Views
Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #240 on: 28 / April / 2015, 16:06:37 »
Advertisements
Hello again! Just tried the latest build you gave me, but unfortunately it doesn't work. No CHDK button in record mode and camera hangs if I press it in review mode.
Now I will reinstall the previous build and I'll try to do the romlog as you asked me to do. Not sure if I'm able to do it, though... :)

Lorenzo

*

Online reyalp

  • ******
  • 12649
Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #241 on: 28 / April / 2015, 16:56:09 »
Hello again! Just tried the latest build you gave me, but unfortunately it doesn't work. No CHDK button in record mode and camera hangs if I press it in review mode.
Thanks. That definitely suggests there is some underlying bug that's sensitive to how things end up in memory.
Quote
Now I will reinstall the previous build and I'll try to do the romlog as you asked me to do. Not sure if I'm able to do it, though... :)
Just load a build that lets you get into the alt menu, and go to Miscellaneous -> debug -> Save ROM crash log.

That will save the log from the most recently recorded crash to your SD as ROMLOG.LOG
Don't forget what the H stands for.

Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #242 on: 03 / May / 2015, 07:34:13 »
Sorry for being late, but finally I have the romlog. Here in attachment. Thanks!

Lorenzo

*

Online reyalp

  • ******
  • 12649
Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #243 on: 03 / May / 2015, 18:07:08 »
Sorry for being late, but finally I have the romlog. Here in attachment. Thanks!
Thanks. The crash is in the Canon firmware ISO code, so it probably just doesn't like extreme out of range values like that. As I mentioned earlier, overriding that far outside of the canon specs probably doesn't work anyway, so for now just avoid trying to use those values. CHDK doesn't currently have a way to enforce a maximum on the ISO override value.

I've attached a new test build. This should allow the CHDK button to show in rec mode. It should be otherwise more similar to the 1.3 code, but I don't know if/how it will affect the other issues.

Also, if you can clarify what happens when the camera hangs, that might be helpful. Does the screen stop updating completely, or are you just unable to interact with the UI?


Finally, if anyone has an ixus240 with the 102a firmware, it would be helpful to know if the 1.3 and 1.4 autobuilds have the same behavior radiant has described.
Don't forget what the H stands for.


Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #244 on: 04 / May / 2015, 08:49:41 »
hello
my camera is 102a
before using this build ,i had no problem.
in v1.4 touch screen doesn't work and in 102a-1.3.0-4152-full_ALPHA ,i installed chdk with stick program.

lag in video after record or
after shots with (ev step value 1/100k) , camera hangs or
one time came black screen and green light blink and i had to remove battery because power button stop working
 romlog

Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #245 on: 04 / May / 2015, 09:48:44 »
I've attached a new test build. This should allow the CHDK button to show in rec mode. It should be otherwise more similar to the 1.3 code, but I don't know if/how it will affect the other issues.

Also, if you can clarify what happens when the camera hangs, that might be helpful. Does the screen stop updating completely, or are you just unable to interact with the UI?

Tried your latest test build. I report results as follows.
1) Good news: the CHDK button finally appears in rec mode!
2) Bad news: pressing this button freezes the camera again (both in rec and play mode).
I reloaded the last working firmware and tried taking another romlog, but it gives me back the same one I already attached.
Regarding your other question: when camera hangs, the screen continue to show either the live view if in rec mode or the last taken picture if in play mode. But the camera refuses to respond to any command, and doesn't take pictures.

Lorenzo

*

Online reyalp

  • ******
  • 12649
Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #246 on: 09 / May / 2015, 17:09:24 »
hello
my camera is 102a
before using this build ,i had no problem.
Do you know what build you were using?

When you say "no problem", were you able to access the CHDK menu while in shooting mode, or only in playback as radiant described?

Quote
in v1.4 touch screen doesn't work

When you say the "touch screen doesn't work" what does this mean? You don't get any response, or the camera hangs?

Quote
and in 102a-1.3.0-4152-full_ALPHA ,i installed chdk with stick program.

lag in video after record or
after shots with (ev step value 1/100k) , camera hangs or
one time came black screen and green light blink and i had to remove battery because power button stop working

 romlog
The two romlogs are the same, taken form the same crash on April 17 (2015:04:17 13:57:02 camera time) They are in focus related code, perhaps from problems with the focus override code. If the other hangs were after that date, they didn't generate a romlog (assume the camera clock is roughly correct)

If you had to take the battery out, a romlog was probably not generated.
Don't forget what the H stands for.

Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #247 on: 10 / May / 2015, 14:18:35 »
Quote
Do you know what build you were using?

When you say "no problem", were you able to access the CHDK menu while in shooting mode, or only in playback as radiant described?
i am using 102a-1.3.0-4152-full_ALPHA , my camera build is 102a
i able to access the CHDK menu while in shooting mode without problem

Quote
When you say the "touch screen doesn't work" what does this mean? You don't get any response, or the camera hangs?
i don't get any response , camera doesn't hang.

and in mf_test.lua script,  all exams passed Except aflock.


*

Online reyalp

  • ******
  • 12649
Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #248 on: 10 / May / 2015, 19:57:45 »
Thanks hamid3pnn. I'm still baffled by the problems with this port, but that did identify one issue.

Here are some more test builds, on box.com so I don't have to make a bunch of posts to get around the attachment limit:

1.4 tests with the old keyboard code:
firmware 101a https://app.box.com/s/sralp1pb5d640i6h5p20xufjtskcwhzi
firmware 102a https://app.box.com/s/bfu3hp01cm1ckowbkyygrlt1uasdd7of

1.3 test to enable the CHDK alt button in record mode, for 101a
https://app.box.com/s/l0y4e77ls4cw616apyag5gwpw0wq62ag


For developers
Regarding the touch button not showing in alt mode, stubs_min.S in both firmware versions has the following:
Code: [Select]
//To do: These were taken from ixus310
DEF(canon_play_menu_active,             0x0000e790)     //ixus240 e790: 0 - 0x32aae0 <- this is always set when in rec and goes back to 0 on play mode
The comment suggests this is always set in rec, making the behavior of never showing the alt button in rec mode the intended behavior. This seems undesirable to me.

ixus310 has a variable with the same name, but it's not clear if the behavior is the same.

The reason the button appears in shooting mode for firmware 102a is probably because the address is wrong on that port (I'm assuming 101a is "right" since that port was done first, and the discussion in http://chdk.setepontos.com/index.php?topic=9005.msg102256#msg102256 refers to this firmware version).
In 101a, sub_FF2CC698 refers to E78C+4
In 102a, the equivalent appears to be sub_FF2CC6CC, which refers to 0xE794+4
Other variables from stubs_entry.S confirm that addresses in this range would not be the same for both firmware versions.

The corresponding code in ixus310 100a seems to be sub_FF2348F0, but it refers to a completely different variable (0xA1C8+4) from what that port calls canon_play_menu_active (0xe784)
Don't forget what the H stands for.

Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #249 on: 11 / May / 2015, 18:14:35 »

1.3 test to enable the CHDK alt button in record mode, for 101a
https://app.box.com/s/l0y4e77ls4cw616apyag5gwpw0wq62ag


Hi again. I just loaded this one. It works! At a first glance, all seems to be OK, especially the alt button in main rec screen! I will tell you if some problems will show up.

Lorenzo

 

Related Topics