CHDK 1.4 release + bug reports

nafraf

1308

Re: CHDK 1.4 release + bug reports

« Reply #20 on: 02 / June / 2016, 15:57:10 »

Advertisements

Test version for sx510hs 101a was posted to sx510hs porting thread. Please post the results to that thread.

Logged

srsa_4c

4451

Re: CHDK 1.4 release + bug reports

« Reply #21 on: 04 / June / 2016, 10:54:31 »

Quote from: reyalp on 01 / June / 2016, 23:40:06

Quote from: srsa_4c on 01 / June / 2016, 20:33:21
Does this occur on the g7x?
Yes, it seems to.

I set CHDK "disable LCD off" to "alt", set canon menu "Power saving" -> "display off" to 30 sec. Power up, switch to rec, just sits there with display on. Enter/exit alt, display turns off after ~30 sec.

I did not have Canon "ECO mode" enabled.

Started looking into this and found something unexpected.
Unless I'm wrong, the last CHDK version working normally in this regard is the 1.0 "stable". When "Disable LCD off" is set to "ALT", Canon power saving becomes disabled and is not enabled again until ALT mode is cycled.

Incomplete traceback:
- _LockMainPower() called by disable_shutdown() in platform/generic/wrappers.c
- disable_shutdown() called by conf_update_prevent_shutdown() in core/conf.c
- conf_update_prevent_shutdown() called in core/script.c, core/conf.c and core/gui.c
... ?

In my logs, when cam is started in playback mode, our _LockMainPower() gets issued around ~500ms after startup, _UnlockMainPower() is not called. Did not do a stack trace yet.

edit:
camera_info.state.gui_mode_none and camera_info.state.gui_mode seem normal, the problem is elsewhere

edit2:
traceback is

Code: [Select]

conf_update_prevent_shutdown core/conf.c
conf_info_func core/conf.c (func ptr)
config_load_defaults core/conf.c (func ptr)
conf_load_defaults core/conf.c
conf_restore core/conf.c
core_spytask core/main.c

We need to disallow issuing disable_shutdown() in conf_update_prevent_shutdown() when restoring config at startup. Any suggestions?

« Last Edit: 04 / June / 2016, 13:21:10 by srsa_4c »

Logged

reyalp

13878

Re: CHDK 1.4 release + bug reports

« Reply #22 on: 04 / June / 2016, 18:06:14 »

Quote from: srsa_4c on 04 / June / 2016, 10:54:31

We need to disallow issuing disable_shutdown() in conf_update_prevent_shutdown() when restoring config at startup. Any suggestions?

It seems like the

Code: [Select]

|| (conf.alt_prevent_shutdown == ALT_PREVENT_SHUTDOWN_ALT && !camera_info.state.gui_mode_none)

should prevent this, except that it (camera_info.state.gui_mode_none) isn't initialized when conf_restore is called. Should be able to just manually initialize at the start, or in camera_info_init.

It's possible there will be some interaction with script autostart, I'm not sure when/how that enters script and alt mode.

edit:
I think script will be OK since it calls conf_update_prevent_shutdown on start and end. Will check this in on the trunk shortly.

edit 2:
I checked this in, and verified that g7x now goes into display off as expected even if alt mode is not entered.
This seems correct to me, so unless someone else sees problems I'll merge it over to the stable branch soon.

« Last Edit: 04 / June / 2016, 18:46:16 by reyalp »

Logged

Don't forget what the H stands for.

srsa_4c

4451

Re: CHDK 1.4 release + bug reports

« Reply #23 on: 04 / June / 2016, 20:20:31 »

Quote from: reyalp on 04 / June / 2016, 18:06:14

edit:
I think script will be OK since it calls conf_update_prevent_shutdown on start and end. Will check this in on the trunk shortly.

edit 2:
I checked this in, and verified that g7x now goes into display off as expected even if alt mode is not entered.

Thanks for finishing.
I have no idea why I only noticed this recently. It should have been noticeable as I don't always browse the menu when shooting. Yet, no-one else seems to have reported it in 4 years.

Logged

reyalp

13878

Re: CHDK 1.4 release + bug reports

« Reply #24 on: 05 / June / 2016, 15:39:29 »

I checked this in for the stable branch.

Quote from: srsa_4c on 04 / June / 2016, 20:20:31

I have no idea why I only noticed this recently. It should have been noticeable as I don't always browse the menu when shooting. Yet, no-one else seems to have reported it in 4 years.

Yeah, seems a little odd. I thought maybe some other action in the normal canon firmware would clear it (e.g. shooting) but from a little testing this doesn't seem to be obviously the case.
Another weird thing is that my sx160 was affected, but still seemed to go into screen off mode regularly in actual use, even though I usually don't need to set anything in alt. Maybe alt and play being on the same button makes me trigger it accidentally.

Logged

Don't forget what the H stands for.

waterwingz

12132

Re: CHDK 1.4 release + bug reports

« Reply #25 on: 06 / June / 2016, 01:03:00 »

Quote from: reyalp on 05 / June / 2016, 15:39:29

Quote from: srsa_4c on 04 / June / 2016, 20:20:31
Yet, no-one else seems to have reported it in 4 years.
Yeah, seems a little odd.

Well, the somewhat heated discussion about CHDK and battery life does come up from time to time. I realize it probably predates this by a bit but anyone who noticed was probably dismissed due to that ongoing discussion.

Logged

Ported : A1200 SD940 G10 Powershot N G16

miti.ranieri

Re: CHDK 1.4 release + bug reports

« Reply #26 on: 06 / June / 2016, 03:56:28 »

Hello dear CHDK team! The zip-download of the 1.4 release for the Canon Powershot D30 is still tagged as BETA on mighty-hoernsche.de. What is the reason for the BETA suffix?

I installed CHDK 1.4 on my D30 today and did some minimal testing. For my special needs, creating RAW DNG, it seems to work properly.

Shall I execute a certain set of tests to remove the BETA status?

Logged

reyalp

13878

Re: CHDK 1.4 release + bug reports

« Reply #27 on: 07 / June / 2016, 02:13:23 »

Quote from: miti.ranieri on 06 / June / 2016, 03:56:28

Hello dear CHDK team! The zip-download of the 1.4 release for the Canon Powershot D30 is still tagged as BETA on mighty-hoernsche.de. What is the reason for the BETA suffix?

Because no one has removed it

Typically, new ports are added as alpha or beta. Since the main developers don't have most of the cameras, we don't really know what the status of each port is, and don't tend to update the status without input from someone who does have the camera.

Quote

Shall I execute a certain set of tests to remove the BETA status?

There is no specific set of tests.

From the porting thread it looks like most of the tests on the testing wiki have been run.

In http://chdk.wikia.com/wiki/Testing_Needed, the keyboard changes are not listed as tested. If you can perform the checks listed there, that would be helpful. So would the CAM_IS_VID_REC_WORKS check

In the porting thread, this camera was reported to have very little free memory. If you can report the value shown in miscellaneous -> memory info, that would be helpful.

Logged

Don't forget what the H stands for.

miti.ranieri

Re: CHDK 1.4 release + bug reports

« Reply #28 on: 13 / June / 2016, 16:10:37 »

Here are the first results of testing 1.4 release on my Powershot D30:
(tested with CHDK 1.4.1 - 4640)

Free Memory: 697944 bytes
Zebra doesn't seem to work at all, no matter what configuration

other tests were successful up to now - still some to do...

Logged

srsa_4c

4451

Re: CHDK 1.4 release + bug reports

« Reply #29 on: 13 / June / 2016, 18:50:48 »

Quote from: miti.ranieri on 13 / June / 2016, 16:10:37

Zebra doesn't seem to work at all, no matter what configuration

That seems odd. Can you test other, viewport related features, such as:
- histogram (does it look reasonably correct?)
- edge overlay
- motion detection
?

Dev notes:
- port already uses a trick to enlarge free RAM (UI memory reduction)
- ~~boot.c/code_gen.txt has this: #if defined(OPT_CHDK_IN_EXMEM), should be fixed~~ update: fixed in trunk
- ARAM is not enabled

« Last Edit: 16 / June / 2016, 20:26:29 by srsa_4c »

Logged