Looking for build without EXMEM - page 2 - Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes) - CHDK Forum supplierdeeply

Looking for build without EXMEM

  • 25 Replies
  • 5428 Views
*

Offline srsa_4c

  • ******
  • 3943
Re: Looking for build without EXMEM
« Reply #10 on: 25 / December / 2015, 13:11:26 »
Advertisements
Here's nafraf's patch, updated for current trunk. It also implements the UI memory reduction trick mentioned above and disables EXMEM.

*

Offline reyalp

  • ******
  • 12000
Re: Looking for build without EXMEM
« Reply #11 on: 26 / December / 2015, 15:37:24 »
Thanks.

@seejay
Here's a build with this patch applied, please test this and report how much memory is free.
101a: https://app.box.com/s/o3vbac4goqwiv4z3usr4ncy09o4sqok2



For any other sx230hs users willing to test, here are builds for the other firmware versions
101b, 101c and 101e: https://app.box.com/s/ahlrqcl3mfnfsjzlt6ufhqrr3mhf9n6h

100c: https://app.box.com/s/2pss96v4x7fs1jlj10y3bzntuslypfsu

A number of people have already run the earlier code-gen and ui memory builds, so I'm inclined to check these changes in to the trunk if no problems reported.
Don't forget what the H stands for.

Re: Looking for build without EXMEM
« Reply #12 on: 26 / December / 2015, 16:46:09 »
Build 4317 with patch applied - Free Memory report SX230 - 1.01A

Free Memory:396584
CHDK size 159776
Loaded at: 0x3CE000

Still feel like a 'noob dummy' here - so if you have any suggestions about my posting in wrong place etc. please let me know.

Re: Looking for build without EXMEM
« Reply #13 on: 27 / December / 2015, 15:33:59 »
Using the 101b release

The camera has been set up with the badpixel.bin file created. I then turn the camera off, and then back on and put it into live view before pulling the memory info.

This resulted in the data below:

Free Memory: 310008 bytes
CHDK size: 159776 bytes

Loaded at: 0x3CE000


I then restarted the camera again, without it in live view:

Free Memory: 310016 bytes
CHDK size: 159776 bytes

Loaded at: 0x3CE000


Re: Looking for build without EXMEM
« Reply #14 on: 27 / December / 2015, 16:05:56 »
Seems to be stable so far, though there is some script weirdness that is preventing one of them from working. (yellow text)


*

Offline reyalp

  • ******
  • 12000
Re: Looking for build without EXMEM
« Reply #15 on: 27 / December / 2015, 16:31:30 »
Free Memory: 310008 bytes
CHDK size: 159776 bytes
How large is the badpixel.bin file?

Quote
Seems to be stable so far, though there is some script weirdness that is preventing one of them from working. (yellow text)
That warning shouldn't prevent the script from working. It just means the script has no version specified, and CHDK has loaded the backward compatibility code for 1.3. CHDK 1.4.1 changed the return values of some functions, so scripts written with chdk 1.4.1 (and later) in mind should have @chdk_version 1.4.1

To make the warning go away, without changing the behavior of the script, you can add @chdk_version 1.3

If the script is actually failing, please describe what happens when you run it.
Don't forget what the H stands for.

Re: Looking for build without EXMEM
« Reply #16 on: 27 / December / 2015, 17:01:57 »
The bad pixel file is 91KB

As for the weirdness, it simply freezes after taking the when it attempts to take the second picture in the HDR set. (have to take the battery out and put it back in in order to restart the camera). When you restart,you see that no images were saved (the first one did not save) and it crashed on the second image.


*

Offline reyalp

  • ******
  • 12000
Re: Looking for build without EXMEM
« Reply #17 on: 27 / December / 2015, 17:25:08 »
As for the weirdness, it simply freezes after taking the when it attempts to take the second picture in the HDR set. (have to take the battery out and put it back in in order to restart the camera). When you restart,you see that no images were saved (the first one did not save) and it crashed on the second image.
Thanks. this isn't related to the chdk version warning.

When you say the camera is hung, the screen etc remains on, but the camera is unresponsive? If you leave it for ~30 seconds, does it shut down on it's own?

Does the current 1.5 autobuild have the same problem?  http://mighty-hoernsche.de/trunk/

Can you post the exact script you are using, or a link to it?

As I mentioned in the other thread, the issues with raw in continuous mode (e.g. http://chdk.setepontos.com/index.php?topic=12183.20 ) are NOT expected to be resolved by any of these changes, so if this is the same problem, that's expected. Unfortunately, I still don't understand this issue and don't have a solution for it.
Don't forget what the H stands for.


Re: Looking for build without EXMEM
« Reply #18 on: 27 / December / 2015, 17:46:52 »
I recorded a video of the issue. With it failed the first time, I tried manually setting the new version to the settings I used on the older version,but the issue still remained.

(I linked right to the time when I was testing the script on the new build)
Sorry for the poor video quality, youtube has been slow with processing videos lately, and will likely be on 360p for a while.

Edit: the same issue happens with the autobuild version too.
   sx230hs-101b-1.5.0-4317-full.zip
« Last Edit: 27 / December / 2015, 18:03:56 by Razor512 »

*

Offline reyalp

  • ******
  • 12000
Re: Looking for build without EXMEM
« Reply #19 on: 30 / December / 2015, 18:02:38 »
I recorded a video of the issue. With it failed the first time, I tried manually setting the new version to the settings I used on the older version,but the issue still remained.

(I linked right to the time when I was testing the script on the new build)
Sorry for the poor video quality, youtube has been slow with processing videos lately, and will likely be on 360p for a while.

Edit: the same issue happens with the autobuild version too.
   sx230hs-101b-1.5.0-4317-full.zip
Thanks. I'm pretty sure this is the same issue, longstanding issue you have had with raw and this script. As I mentioned, this is not expected to be resolved by any of the recent changes. This is confirmed by the trunk having the same problem.

Do you know what the working build was? I'm guessing it would be one of the test builds I posted a long time ago?

The display glitching you mention in the video is normal, CHDK doesn't really know when the normal firmware draws on the screen.
Don't forget what the H stands for.

 

Related Topics