Bug Reports against Recent Builds -- Report bugs here - page 24 - CHDK Releases - CHDK Forum supplierdeeply

Bug Reports against Recent Builds -- Report bugs here

  • 281 Replies
  • 77373 Views
*

Offline lapser

  • *****
  • 1093
Battery Voltage not updating in continuous mode
« Reply #230 on: 04 / March / 2013, 13:08:48 »
Advertisements
When you set the osd to display battery voltage all the time, the voltage display continually changes. However, if you hold the shutter down in continuous mode (and take pictures), the voltage display is still refreshed, but the value stays the same. When you let the shutter up, the voltage starts changing again.

I noticed this in my time lapse script shooting in continuous mode, so I added a script call to get_vbatt().  The value returned is accurate, and changes rapidly. So the problem must be in the osd refresh.
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos

*

Offline MGL

  • *
  • 1
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #231 on: 17 / April / 2013, 12:58:04 »
Using build 1.1.0-2692 (April 9, 2013) on an SX130 I occasionally get duplicate file names.  After shooting a series of images, downloading and then deleting them off the card, when I start another series of images the files names will be duplicated from the first series.  The images are deleted while the card is in the card reader which was used for downloading, and not by the camera (or via CHDK's file browser).

I've not experience this behavior with earlier builds.  The duplicate file naming occurs maybe 50% of the time (and so is a hassle to deal with).  I can find no pattern to when this issue will occur, it appears random.  Thank you.

*

Offline srsa_4c

  • ******
  • 3979
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #232 on: 18 / April / 2013, 14:11:22 »
Using build 1.1.0-2692 (April 9, 2013) on an SX130 I occasionally get duplicate file names.  After shooting a series of images, downloading and then deleting them off the card, when I start another series of images the files names will be duplicated from the first series.  The images are deleted while the card is in the card reader which was used for downloading, and not by the camera (or via CHDK's file browser).

I've not experience this behavior with earlier builds.  The duplicate file naming occurs maybe 50% of the time (and so is a hassle to deal with).  I can find no pattern to when this issue will occur, it appears random.  Thank you.
A few questions.
- Are you shooting in RAW/DNG or JPEG only? Are JPEG numbers (also) duplicated?
- In addition to the numbering problem, does it happen sometimes that the camera "forgets" your last shooting settings (in the Canon menu, stuff like white balance, ISO, etc.)?
- Is the camera working OK when using a card without CHDK?
- If the symptoms are related to that new CHDK build, can you name the last version that worked OK? Can you confirm that the camera works normal again when using a card with the previously used CHDK build?

Try getting a romlog (miscellaneous stuff -> debug parameters -> save ROM crash log), and attach it here if you can get one.

*

Offline srsa_4c

  • ******
  • 3979
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #233 on: 04 / May / 2013, 08:42:11 »
CHDK built as ARM is unusable using current trunk code.
(ARM compilation is achieved by replacing
CTHUMB=-mthumb
with
CTHUMB=
in makefile.inc)
Symptoms: loading a module (probably) crashes the task which tried to load the module. Switching to shooting mode also kills something (may be due to a module trying to load?). Camera records no romlog, it either continues running until a battery pull or switches off. Experienced on a3200 and ixus110 so far.

Note: using trunk code from february, I was able to use ARM CHDK on the s1is.
I'll try to come up with a better regression point, and update this post.

edit1: ARM CHDK core is able to use thumb modules, but not vice versa.
« Last Edit: 04 / May / 2013, 09:18:39 by srsa_4c »


*

Offline reyalp

  • ******
  • 12075
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #234 on: 04 / May / 2013, 15:17:22 »
CHDK built as ARM is unusable using current trunk code.
Switching to shooting mode also kills something (may be due to a module trying to load?).
CHDK shouldn't automatically load anything when you switch to shooting mode.

Shooting mode does increase memory use.
Don't forget what the H stands for.

*

Offline srsa_4c

  • ******
  • 3979
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #235 on: 04 / May / 2013, 20:34:29 »
CHDK shouldn't automatically load anything when you switch to shooting mode.
Not sure what was the cause. Now it "only" dies if any module is involved. Hard to tell what could cause this without a romlog. Free memory is not the issue (both cams use exmem, the ixus110 has over 1M available).

I wonder whether this has something to do with one of the recent code reorganizations or makefile changes.
The reason I tried this was to see whether an ARM build helps with that Lua error.

*

Offline reyalp

  • ******
  • 12075
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #236 on: 04 / May / 2013, 21:11:56 »
I wonder whether this has something to do with one of the recent code reorganizations or makefile changes.
That would be my guess as well, but offhand I can't think of anything specific.

I would expect mixing modules compiled differently than the core would be a problem. (e.g. ARM core vs thumb modules, or thumb core vs arm modules)
Quote
The reason I tried this was to see whether an ARM build helps with that Lua error.
I'm not sure if we have a reproducible enough case to tell if something helps.
Don't forget what the H stands for.

*

Offline philmoz

  • *****
  • 3123
    • Photos
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #237 on: 04 / May / 2013, 21:38:58 »
Note: using trunk code from february, I was able to use ARM CHDK on the s1is.

Are you sure?

Prior to the major reorg (rev 2453) it was not possible to build the modules as ARM code (_div0 error in fselect).

AFAIK compiling and running the modules as ARM code has never worked - there are comments in tsvstars conversion tool that implies that only THUMB code is supported. I haven't looked closely at it to see why.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)


*

Offline srsa_4c

  • ******
  • 3979
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #238 on: 04 / May / 2013, 22:16:38 »
Note: using trunk code from february, I was able to use ARM CHDK on the s1is.

Are you sure?
I was. However, I only found evidence of me trying ARM compilation on trunk 2579, and I remember I was a bit surprised to see that it (i.e. the compilation) worked. Since this happened when I was fighting with PTP on the S1, I haven't tested that build thoroughly.
My mistake, sorry for the noise  :-[


For the record, calendar and reversi does work on trunk 2579 (a3200), but not on 2760. Using ARM core and modules.
« Last Edit: 04 / May / 2013, 22:31:04 by srsa_4c »

*

Offline philmoz

  • *****
  • 3123
    • Photos
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #239 on: 05 / May / 2013, 03:33:52 »
Note: using trunk code from february, I was able to use ARM CHDK on the s1is.

Are you sure?
I was. However, I only found evidence of me trying ARM compilation on trunk 2579, and I remember I was a bit surprised to see that it (i.e. the compilation) worked. Since this happened when I was fighting with PTP on the S1, I haven't tested that build thoroughly.
My mistake, sorry for the noise  :-[


For the record, calendar and reversi does work on trunk 2579 (a3200), but not on 2760. Using ARM core and modules.

Fixed in revision 2761.

The program that converted the .elf file to the .flt format was not handling 24 bit relative branch relocation properly. So the module would work if it got compiled with none of these relocations.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)

 

Related Topics