Adding feature support "File Write Task" (FWT): 52 Cams || 41 done || 11 to go - page 4 - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: 1 2 3 [4] 5 6 7 8 9 ... 26   Go Down

Adding feature support "File Write Task" (FWT): 52 Cams || 41 done || 11 to go

  • 258 Replies
  • 75235 Views
*

Offline koshy

  • *****
  • 1090
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 46 to go
« Reply #30 on: 23 / August / 2014, 19:27:39 »
Advertisements
Quote from: reyalp on 23 / August / 2014, 17:12:15
edit:
re "Another note on the IXUS 100: I couldn't select any modes in CHDKPTP. The mode pull down was empty in rec mode."
Are there any messages in the console area?

There are two common causes of this
1) The capmode lua library is missing, probably due to not having a full install on the SD card.
2) The camera has very low free memory, and so cannot load the capmode module.

Both will give you an error about the capmode script, but you can use
=return get_meminfo()
to check the amount of memory available.
The patch was for one year old trunk 3042 and that's what I applied it to (just to make sure this is known).

No messages in the console area (screen shot attached)
I'm certain that a full CHDK is on the SD card.

=return get_meminfo() returns:
Code: [Select]
3:return:table:{chdk_start=2627132,free_size=315648,chdk_size=150840,allocated_size=1326160,free_block_count=16,name="combined",allocated_count=1467,chdk_malloc=true,free_block_max_size=313472,allocated_peak=1387728,total_size=1641808,}
Logged
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)
*

Offline reyalp

  • ******
  • 13882
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 46 to go
« Reply #31 on: 23 / August / 2014, 19:57:19 »
Quote from: koshy on 23 / August / 2014, 19:27:39
The patch was for one year old trunk 3042 and that's what I applied it to (just to make sure this is known).
Thanks. I don't think that should matter.
Quote
No messages in the console area (screen shot attached)
Did you try scrolling up, the console scrolling is a bit weird sometimes.

You can use
gui_verbose=2
before connecting to make the gui output more diagnostic messages, although I think something should be printed if getting the mode list fails.

From your get_meminfo, there is ~300k available, which is a bit low, but shouldn't prevent you from loading the file.

Some additional things you can try

make sure the OS heap has enough
=return get_meminfo'system'.free_block_max_size

make sure CHDK can access the file
=return os.stat'A/CHDK/LUALIB/CAPMODE.LUA'

make sure it can be loaded.
 =return require'capmode'.name_to_mode
Logged
Don't forget what the H stands for.
*

Offline koshy

  • *****
  • 1090
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 50 to go
« Reply #32 on: 23 / August / 2014, 19:58:23 »
Quote from: reyalp on 23 / August / 2014, 17:05:31
That crash in spytask (chdk code), so it's not the usual remoteshoot playback mode crash (http://chdk.setepontos.com/index.php?topic=11481.0). Possibly worth more investigation, but figuring out where it happened will require the core/main.bin.dump from that build, and possibly the modules.log.
Where do I find that? (core/main.bin.dump)

Quote from: reyalp on 23 / August / 2014, 17:05:31
Note if you aren't already, it's a good idea to enable module logging when testing: chdk menu->miscellaneous->modules->enable logging. This records the load addresses of CHDK modules so you can match them up with stack traces.
OK I turned it on. Didn't know I should.

I can recreate the crash now. Click panic between rec and play will crash the cam. I think I was just too fast on trying to switch from play back to rec or to play after shooting. Whatever I did I needed to take out the cam's battery and didn't get a new ROMLOG for the new crash. But it seems unrelated to FWT.
« Last Edit: 23 / August / 2014, 20:09:58 by koshy »
Logged
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)
*

Offline koshy

  • *****
  • 1090
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 45 to go
« Reply #33 on: 23 / August / 2014, 20:04:47 »
Quote from: reyalp on 23 / August / 2014, 19:57:19
You can use
gui_verbose=2
before connecting to make the gui output more diagnostic messages, although I think something should be printed if getting the mode list fails.

From your get_meminfo, there is ~300k available, which is a bit low, but shouldn't prevent you from loading the file.

Some additional things you can try

make sure the OS heap has enough
=return get_meminfo'system'.free_block_max_size

make sure CHDK can access the file
=return os.stat'A/CHDK/LUALIB/CAPMODE.LUA'

make sure it can be loaded.
 =return require'capmode'.name_to_mode
Results are attached.
Logged
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)
*

Offline reyalp

  • ******
  • 13882
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 50 to go
« Reply #34 on: 23 / August / 2014, 20:21:21 »
Quote from: koshy on 23 / August / 2014, 19:58:23
Where do I find that? (core/main.bin.dump)
It should be in your build directory after you build.  If you are using CHDKShell, see http://chdk.wikia.com/wiki/Debugging#Locating_CHDK_code_from_romlog_addresses

Quote
I can recreate the crash now. Click panic between rec and play will crash the cam. I think I was just too fast on trying to switch from play back to rec or to play after shooting. Whatever I did I needed to take out the cam's battery and didn't get a new ROMLOG for the new crash. But it seems unrelated to FWT.
OK, if it doesn't create a romlog, then my previous comments don't matter anyway. I'm not really surprised that switching rapidly causes a crash.

Regarding the mod switch issue. verbose command should be
set gui_verbose=2

From your output, it's not one of the usual problems. Verbose may show something.
Logged
Don't forget what the H stands for.
*

Offline koshy

  • *****
  • 1090
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 45 to go
« Reply #35 on: 23 / August / 2014, 20:47:47 »
Quote from: reyalp on 23 / August / 2014, 20:21:21
Quote from: koshy on 23 / August / 2014, 19:58:23
Where do I find that? (core/main.bin.dump)
It should be in your build directory after you build.  If you are using CHDKShell, see
Ah, it's called dump-ixus120_sd940-103b.txt. I'm attaching it if it's still useful.
Quote from: reyalp on 23 / August / 2014, 20:21:21
I'm not really surprised that switching rapidly causes a crash.
Neither am I. I think that is what it comes down to. I was too quick with the buttons. It worked many times thereafter...
Logged
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)
*

Offline koshy

  • *****
  • 1090
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 50 to go
« Reply #36 on: 23 / August / 2014, 20:53:56 »
Quote from: reyalp on 23 / August / 2014, 20:21:21
Regarding the mod switch issue. verbose command should be
set gui_verbose=2

From your output, it's not one of the usual problems. Verbose may show something.
It gives me:
Code: [Select]
> set gui_verbose=2
update mode dropdown 0
update mode dropdown nil
update mode dropdown 0Where the 0 comes up when entering shooting mode and the nil when entering play mode.
So the sequence above was Rec > Play > Rec.
Logged
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)
*

Offline reyalp

  • ******
  • 13882
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 45 to go
« Reply #37 on: 23 / August / 2014, 21:59:55 »
Quote from: koshy on 23 / August / 2014, 20:47:47
Ah, it's called dump-ixus120_sd940-103b.txt. I'm attaching it if it's still useful.
That romlog is quite strange.
Exception 4 is invalid instruction
The PC is 0xFF9CB944
The actual exception should have been on the immediately preceding instruction, which is
FF9CB940                 BLX     R12
This is a valid  ARM instruction. R12 in the romlog is 4 which suggests this bit of code jumped directly to the invalid instruction handler, rather than there being an actual exception involved.

Nothing in the stack or registers looks like a CHDK address. In fact, the stack looks suspiciously empty of real data.
Logged
Don't forget what the H stands for.
*

Offline reyalp

  • ******
  • 13882
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 50 to go
« Reply #38 on: 23 / August / 2014, 22:15:04 »
Quote from: koshy on 23 / August / 2014, 20:53:56
Where the 0 comes up when entering shooting mode and the nil when entering play mode.
After switching to rec, try:
=c=require'capmode' return c.get(),c.get_name(),c.get_canon()
Logged
Don't forget what the H stands for.
*

Offline koshy

  • *****
  • 1090
Re: Adding feature support "File Write Task" (FWT): 50 Cams || 45 to go
« Reply #39 on: 24 / August / 2014, 08:32:57 »
Quote from: reyalp on 23 / August / 2014, 22:15:04
After switching to rec, try:
=c=require'capmode' return c.get(),c.get_name(),c.get_canon()
Code: [Select]
> =c=require'capmode' return c.get(),c.get_name(),c.get_canon()
3:return:0
3:return:'UNKNOWN'
3:return:32772
Logged
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)
Pages: 1 2 3 [4] 5 6 7 8 9 ... 26   Go Up
« previous next »
 

Related Topics