G11 porting - page 21 - DryOS Development - CHDK Forum  

G11 porting

  • 530 Replies
  • 236606 Views
*

Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #200 on: 06 / January / 2010, 05:37:43 »
Advertisements
Thanks for the links. I read the thread and know i knew that this is "really" caused by r39 fw.
I now also merged the changes from  RaduP (from the linked thread):
http://chdk.setepontos.com/index.php/topic,4228.msg41802.html#msg41802
http://chdk.setepontos.com/index.php/topic,4228.msg41848.html#msg41848
http://chdk.setepontos.com/index.php/topic,4228.msg41850.html#msg41850

and now, e.g. the script fileselect dialog is not crashing anymore.  :)

Re: G11 porting
« Reply #201 on: 06 / January / 2010, 06:01:56 »
Can the config file be loaded on startup ?


So, is it time to  enable the capture task ?

*

Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #202 on: 06 / January / 2010, 07:35:14 »
No, with configfile the camera crashes, or get freezed at startup.
I attached one of my "crashing" config files, looks this config file normal?
I currently dont have another CHDK capable camera here to compare.

I can find some printf() error/text strings in the configfile, so i think somthing went wrong here:
Code: [Select]
Snl %s: %d:  in function '%s'  in main chunk  ?  in function <%s:%d> level out of range flnSu

Also the CHDKConfig File Editor shows an error messsage if i load this cfg file (Error - unknown entry id=19268)

Re: G11 porting
« Reply #203 on: 06 / January / 2010, 07:57:09 »
It stops at entry 183 in the conf file which should be the menu-symbol rbf file but is actually symbol enable.

Entry 62 should be symbol enable but is Menu Symbol RBF File

They seem to have been swapped around.


*

Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #204 on: 06 / January / 2010, 09:01:58 »
Thanks man!
This was the problem, because the config_load was chrashing previously (caused by the open()/empty string problem as we now know), i patched the config_load function to skip the crashing config IDs. And i have forgotten to remove this debug code after i merged the patches from RaduP.

Now i am using an non patched conf.c and config load&save seems now to work!

Re: G11 porting
« Reply #205 on: 06 / January / 2010, 09:05:24 »
I don't know much about compiling or programming but I know just enough to be useful   :)

*

Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #206 on: 06 / January / 2010, 17:36:22 »
You are very helpful Microfunguy.  :)

And again i need some help. I try to get the caputure task running and it does not look so bad,
i got a 15MB raw file created on the SD-Card if i shoot with CHDK RAW feature active. But in raw_savefile()
the camera switches off. I find out that SetFileTimeStamp() causes the problem (it is called from utime(fn, &t) ) .

I took a look at this function and find out that the signature finder was not able to find the correct function address:
// Best match: 55% NSTUB(SetFileTimeStamp, 0xff94a8dc)
This address points into the middle of a function, so it is obviously wrong.

May be some one could help me and find the correct function pointer for SetFileTimeStamp()? (to avoid to nullsub the call)
« Last Edit: 06 / January / 2010, 17:49:59 by ERR99 »

Re: G11 porting
« Reply #207 on: 06 / January / 2010, 18:02:15 »
How about 0xFF835C3C  ?


As a matter of interest, why would you enable CHDK RAW support at all, why not exclude from the compilation ?

It is interesting that Canon state the RAW image is raw sensor data saved with ALMOST no image deterioration.
« Last Edit: 07 / January / 2010, 06:13:29 by Microfunguy »


*

Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #208 on: 07 / January / 2010, 14:12:09 »
SetFileTimeStamp() is also failing with 0xFF835C3C. It crashes also if i nullsub the call, so i have replaced
the SetFileTimeStamp() call in utime()  with this:
Code: [Select]
  //res=_SetFileTimeStamp(fd, ((int*)newTimes)[0] , ((int*)newTimes)[1]);
  res=1;

Enabling the simple CHDK-RAW (without DNG support) in the G11 firmware was no big deal, so why not doing it.  :lol
It is another question if this is really usefull for the chdk-user. I think not, because saving an 15MB RAW-Image takes a couple of seconds, the original (packed) raw file is written much faster.

But setting the correct timestamp on files makes trouble. And if i search for utime() references, i see that also motion_detector and lua using this function. So i am afraid that this calls will also crashing and maybe i have to patch them also, if no suitable function address is found for _SetFileTimeStamp().

Re: G11 porting
« Reply #209 on: 07 / January / 2010, 14:16:58 »
i am afraid that this calls will also crashing and maybe i have to patch them also, if no suitable function address is found for _SetFileTimeStamp().

OK, I will have another look later this evening.


 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal