new branch - CHDK : Elf Edition - Developers wanted - page 17 - General Discussion and Assistance - CHDK Forum  

new branch - CHDK : Elf Edition - Developers wanted

  • 316 Replies
  • 70050 Views
Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #160 on: 01 / January / 2012, 14:42:25 »
Advertisements
Ok, above was stupid confusion. Now real bug:

Memory browser crashes just after enter in it.

SX130IS firm. 1.01c
CHDK changeset 1522
just freshly-compiled and copied to SD card with almost no changes.

Other modules work well.

if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick

*

Offline philmoz

  • *****
  • 3156
    • Photos
Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #161 on: 01 / January / 2012, 16:00:23 »
Ok, above was stupid confusion. Now real bug:

Memory browser crashes just after enter in it.

SX130IS firm. 1.01c
CHDK changeset 1522
just freshly-compiled and copied to SD card with almost no changes.

Other modules work well.



A safety check on the memory address was removed from the code (because it made the module platform dependent).

I've fixed this (and made the browser even safer) in the reyalp-flt branch - can you try this version and let me know if it fixes your crash.

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 philmoz

  • *****
  • 3156
    • Photos
Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #162 on: 01 / January / 2012, 19:25:23 »
Does anyone have any objection to the main trunk being updated from the latest changes in the reyalp-flt branch?

This will get the 1.1 dev version back up to date.

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)

Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #163 on: 01 / January / 2012, 19:42:20 »
Does anyone have any objection to the main trunk being updated from the latest changes in the reyalp-flt branch?
Okay by me - but then I'm doing all my USB remote in a copy of the stable stuff for now

There will be a big honking change necessary to fix wait_until_remote_button_is_released()  in every camera's kbd.c code at some point.  I'd like to do that when the dev trunk is somewhat stable :)

Ported :   A1200    SD940   G10    Powershot N    G16


Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #164 on: 01 / January / 2012, 20:17:20 »
My A460 crashes on startup when calend.flt is present in the modules directory (this is on trunk).

Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #165 on: 02 / January / 2012, 01:35:04 »
A safety check on the memory address was removed from the code (because it made the module platform dependent).
I've fixed this (and made the browser even safer) in the reyalp-flt branch - can you try this version and let me know if it fixes your crash.

I will write guide in future. And it is ok for changes in branch and for this exact case when issued module just never work.

But just one quick note:
API versioning planed to use for binary safety - module check is structure is really that they expect. Adding to end of camera_info is backward compatible but could be requirement. Otherwise module will think that structure has address info but there will be just different binary data. And it will probably work but surely in strange way in previous revision.
Conclusion: if something added to end of structure  adding something, minor version of correspondent  api should be increased and if module use this data it should check this new version

Quote from: pelrun
My A460 crashes on startup when calend.flt is present in the modules directory (this is on trunk).
Is reyalp-flt branch have same issue? Or maybe it shutdown on first menu popup? Or (I hope) it work well?

*

Offline philmoz

  • *****
  • 3156
    • Photos
Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #166 on: 02 / January / 2012, 02:16:55 »
My A460 crashes on startup when calend.flt is present in the modules directory (this is on trunk).

This could be the same sort of problem experienced on DryOS based cameras (http://chdk.setepontos.com/index.php?topic=6179.0).

The VxWorks firmware seems to have a similar structure for file handling so the processing of the module files at startup could be conflicting with the firmware.

Attached is a version built with the CAM_STARTUP_CRASH_FILE_OPEN_FIX option enabled, can you try this and see if it has the problem.

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)

Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #167 on: 02 / January / 2012, 03:35:11 »
I got a successful boot after defining CAM_STARTUP_CRASH_FILE_OPEN_FIX, so hopefully that's all that is required. I know what to look for in the romlog now, so I'll keep an eye on it.


*

Offline reyalp

  • ******
  • 12586
Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #168 on: 03 / January / 2012, 23:15:20 »
http://chdk.setepontos.com/index.php?topic=845.msg79277#msg79277

This raises a question: Do we need to have things like edge overlay be a module *and* compile time optional ? Some things still need to be optional because the platform might not support them, but for standalone modules, I don't see much reason.
Don't forget what the H stands for.

*

Offline philmoz

  • *****
  • 3156
    • Photos
Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #169 on: 03 / January / 2012, 23:28:06 »
http://chdk.setepontos.com/index.php?topic=845.msg79277#msg79277

This raises a question: Do we need to have things like edge overlay be a module *and* compile time optional ? Some things still need to be optional because the platform might not support them, but for standalone modules, I don't see much reason.

Having the compile time option would allow creation of a build without the menu enties and module interface code.
So might be worth keeping; but will require some rework to ensure everything compiles properly.

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