A800 Porting Thread - page 6 - DryOS Development - CHDK Forum supplierdeeply

A800 Porting Thread

  • 277 Replies
  • 81710 Views
Re: A800 Porting Thread
« Reply #50 on: 01 / February / 2012, 22:29:00 »
Advertisements
After playing a bit with settings canon turned off.
It shows splash screen on start (including CHDK logo) and then turns off.

Formated card again. Now works.

Where is the place where CHDK stores it's settings?

Re: A800 Porting Thread
« Reply #51 on: 01 / February / 2012, 22:34:40 »
Quote
Do you understand that there are data tables embedded in the ARM code and that you cannot dissassemble them into code ?

Of course.

Quote
The capt_seq.c code for the 1.00c skips over the data table that starts at 0xffc983c4 and continues as code beginning at 0xffc98430

So exp_drv_task() contains merged code from different addrs.
Ok, now it is clear. Thanks.

Re: A800 Porting Thread
« Reply #52 on: 01 / February / 2012, 23:02:23 »
Where is the place where CHDK stores it's settings?
CCHDK.CFG in directory CHDK
Ported :   A1200    SD940   G10    Powershot N    G16

Re: A800 Porting Thread
« Reply #53 on: 02 / February / 2012, 00:11:27 »
I am hearing the porting of version 100b. On 100c,  I don't see the logo displaying  but just the starting message box from chdk. Waterwingz, would you know where probably is the problem? Or where is placed the routine that displays the logo ?


*

Offline fe50

  • ******
  • 3139
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: A800 Porting Thread
« Reply #54 on: 02 / February / 2012, 00:44:25 »
I don't see the logo displaying  but just the starting message box from chdk.
If logo.dat is not available in \CHDK\DATA, a textbox splash is used instead of the CHDK logo.
Get the file (and also others or better the whole \CHDK folder) either from any full CHDK download package or from the SVN server (e.g. http://trac.assembla.com/chdk/browser/branches/release-1_0/CHDK/DATA )...

Re: A800 Porting Thread
« Reply #55 on: 02 / February / 2012, 04:53:55 »
Mlands,
So now I have everything you done on 100c ported to 100b.

What things left todo?
What things need testing?

I'll try to help with further progress.

Re: A800 Porting Thread
« Reply #56 on: 02 / February / 2012, 12:36:06 »
Hi madman,
  I will check the code. By memory, I didn't find the nrflag. But I think that the new implementation of the remote make this not necessary(I think). Yesterday, when I was using the camera in OSD Parameter menu, show battery temperature (or show all) and then entering the OSD layout Editor, the camera shuts down. So probably some problem in identifying the associated address in firmware.
either from any full CHDK download package or from the SVN server
  I get the file and is working. I thought I had gotten everything (surely not). I am already using the option of the SVN updating  in chdk Shell (not permanently on, for I have to add some changes - camera_list.csv, modelist.h). The directory branches exists but was empty.  I will eventually reinstall everything.

*

Offline reyalp

  • ******
  • 13625
Re: A800 Porting Thread
« Reply #57 on: 02 / February / 2012, 16:49:49 »
  I get the file and is working. I thought I had gotten everything (surely not). I am already using the option of the SVN updating  in chdk Shell (not permanently on, for I have to add some changes - camera_list.csv, modelist.h). The directory branches exists but was empty.  I will eventually reinstall everything.
If you are doing development, I'd strongly suggest checking out an actual working copy from svn using a client like tortoise, rather than using CHDK shell to download. Getting code updates is much more convenient, because they will be automatically merged with the changes in your working copy. In the rare case there is a conflict, it's left for you to resolve, clearly marked. If you are developing on windows, tortoisesvn is the recommended client.

Quote
I will check the code. By memory, I didn't find the nrflag. But I think that the new implementation of the remote make this not necessary(I think)
nrflag is used to control dark frame subtraction in the canon firmware. By default, the Canon firmware does a darkframe for long exposures (usually 3 sec or so). CHKD allows you to force this on or off.
Don't forget what the H stands for.


Re: A800 Porting Thread
« Reply #58 on: 02 / February / 2012, 18:07:57 »
Thanks Reyalp. Could you post the link to tortoisesvn (I use windows).
nrflag: Ok. I will examine the firmware again. When I have searched it on the code I couldn't find analogous code sections to firmware of other cameras. The section is somehow similar to ixus220, but when I confronted to other sections I was unsure. On the other hand captseq.c from ixus220 doesn't call (at least directly) the routine capt_seq_hook_set_nr (from generic/captseq.c) and I have searched the core source code. So I suppose it is used from a lib section. As I said I will reexamine the firmware and bring more consistent doubts. Surely I will need help to confirm the value.

Re: A800 Porting Thread
« Reply #59 on: 02 / February / 2012, 18:53:40 »
tortoisesvn.net/
Ported :   A1200    SD940   G10    Powershot N    G16

 

Related Topics