SX520HS Porting thread. - page 6 - DryOS Development - CHDK Forum  

SX520HS Porting thread.

  • 209 Replies
  • 65488 Views
*

Offline srsa_4c

  • ******
  • 4430
Re: SX520HS Porting thread.
« Reply #50 on: 08 / May / 2016, 19:23:01 »
Advertisements
Playback mode:
Module inspector:
Mem= 0031f0d8-00563208: 2375984
alloc= now=1683448(400) max=1715264
free= now=692536(5) max= 691032

Record mode (picture taking mode):
Module inspector:
Mem= 0031f0d8-00563208: 2375984
alloc= now=1683904(425) max=1907216
free= now=231464(3) max= 230416

After taking one picture:
Module inspector:
Mem= 0031f0d8-00563208: 2375984
alloc= now=1709520(438) max=1907216
free= now=205848(4) max= 204400
Looking at this again, 460616 bytes of memory "vanish" when rec mode is entered.
The "alloc now" + "free now" should be equal to the whole allocatable memory (2375984 bytes).
This seems to suggest that memory is getting corrupted...

@wobelaar
Do you get the same results after resetting all CHDK settings (CHDK settings -> Reset options to default) and restarting the camera?
« Last Edit: 08 / May / 2016, 19:25:33 by srsa_4c »

Re: SX520HS Porting thread.
« Reply #51 on: 09 / May / 2016, 00:57:22 »
Before installing test build 2 or after?

Re: SX520HS Porting thread.
« Reply #52 on: 09 / May / 2016, 06:41:28 »
After installation sx520hs-100b-1.5.0-4626-test2.zip, chdk starts, but after trying to choose scripts - there is a tree with the letters a, a, etc., and 12  letters. Thank you.

Re: SX520HS Porting thread.
« Reply #53 on: 09 / May / 2016, 08:39:28 »
After installation sx520hs-100b-1.5.0-4626-test2.zip, chdk starts, but after trying to choose scripts - there is a tree with the letters a, a, etc., and 12  letters. Thank you.


I don't know anything about coding, but did you check if you had the right camera firmware?


edit:
I really have no idea what could be wrong other than something with your camera itself... My camera works just fine. I am using a script right now (intervalometer) and I don't see a tree with letters... What script did you use?
« Last Edit: 09 / May / 2016, 10:28:46 by wobelaar »


*

Offline srsa_4c

  • ******
  • 4430
Re: SX520HS Porting thread.
« Reply #54 on: 09 / May / 2016, 10:43:35 »
Before installing test build 2 or after?
Before, preferably. That would make the comparison easier.

after trying to choose scripts - there is a tree with the letters a, a, etc., and 12  letters.
I can only guess that you have a problem with the CHDK file browser. Can you upload a screenshot?

Re: SX520HS Porting thread.
« Reply #55 on: 09 / May / 2016, 11:03:05 »
I just installed the second to see if I would have the same problem with the tree. But tonight I will install test build 1 again to get the number for you!

Re: SX520HS Porting thread.
« Reply #56 on: 09 / May / 2016, 22:24:18 »
after trying to choose scripts - there is a tree with the letters a, a, etc., and 12  letters.
Can you upload a screenshot?

screenshot - http://imgur.com/g3PmPyx
Where is sx520hs-100b-1.5.0-4626-test1.zip?

Re: SX520HS Porting thread.
« Reply #57 on: 10 / May / 2016, 08:32:52 »
after trying to choose scripts - there is a tree with the letters a, a, etc., and 12  letters.
Can you upload a screenshot?

screenshot - http://imgur.com/g3PmPyx
Where is sx520hs-100b-1.5.0-4626-test1.zip?


It's deleted I think that's because there's a newer test build...


*

Offline srsa_4c

  • ******
  • 4430
Re: SX520HS Porting thread.
« Reply #58 on: 10 / May / 2016, 10:40:13 »
screenshot - http://imgur.com/g3PmPyx
That is a 64GB card. It is either corrupted or it is formatted as exFAT and CHDK did not recognize it as exFAT.
Try formatting it again.
If you format it to FAT32, you can use the bootable card method to start CHDK automatically.

Quote
Where is sx520hs-100b-1.5.0-4626-test1.zip?
As wobelaar said, it was removed because there is a newer test build.

Re: SX520HS Porting thread.
« Reply #59 on: 10 / May / 2016, 10:44:41 »
Sorry for the late answer I'm quite busy with school etc.


Module inspector Playback mode:
Mem:0031f0d8-00563208
alloc: now=16803052 (394) max=1708064
free: now=695632(3) max=695208


Rec mode:
Mem: 0031f0d8-00563208: 2375984
alloc: now=1680792(419) max=1708064
free: now=695192(2) max=693944


after taking one picture:
Mem: 0031f0d8-00563208: 2375984
alloc: now=1774752(429) max=1877608
free: now=601232(4) max=545352

BTW I'm using for these number test build 1 again ;) So it's easier for you!

 

Related Topics