Hi Khashayar, There were many changes from the 333 to the current 353 code, most changes happened after migrating from 7.x to 8.x versions, these differences are more than just changing parameters/names. Brief discussion is in the LinuxDevices article - http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Elphel-camera-under-the-hood-from-Verilog-to-PHP/ , most changes are erlated to pipeline operation of the camera, so there are no more "current" parameters (as was in 333 and 353 firmware 7.x) - different version of the same parameter maybe simultaneously active for different stages of the camera hardware. The camera control is separate from image acquisition and there is a special image server (on port 8081) that is used instead of the general purpose web server.
Can you describe your appluication in more details - what is it doing, so we can suggest how to make it work with the 353 camera. Andrey ---- On Sun, 07 Oct 2012 22:22:23 -0700 Khashayar Azad<[email protected]> wrote ---- Hi Andrey, There're two device files in the 333 camera that are not in the 353 camera which my apps need to run... /dev/ccam_dma.raw /dev/hist Is there an equivalent to these ones in the 353 camera? Also there are various stuff, see below, from the 333 camera that were not in the 353 camera which is needed to compile my apps. Are any of these referring to the camera hardware? If yes where have they gone? #define P_LPR 6 /* RD P_RO_LPR 3 32-bit words per row (aligned each row) */ #define P_IMAGE_SIZE 7 /* RD P_RO_SIZE 4 total image size (dma data) in bytes */ #define P_GAMMA 60 // 100*gamma (for now - just a hint table could be more complex. Use higher bytes for colors in 333) #define P_PIXEL_LOW 61 // (just a hint for gamma table) "fat zero" (on 8-bit scale) #define P_PIXEL_HIGH 62 // (just a hint for gamma table) highest pixel value (before table) on a 256-scale #define P_VIDEO 22 /* still (stopped) - 0, video - 1. KAC1310 - video only */ #define P_AUXCM 23 /* signal on AUXCLK pin: 0 - 0, 1 - 1, 1x - 20MHz */ #define P_MCLK 38 /* 2..129 */ #define P_SPEC_KAC_GGA 51 // KAC-1310 Global gain A , 6 bits, (14) #define P_SPEC_KAC_GGB 52 // KAC-1310 Global gain B , 6 bits, (14) #define P_SPEC_KAC_GGM 53 // KAC-1310 Global gain mode, 3 bits, 0 #define P_FP100S 55 // Frames per 100 sec (fps * 100) #define P_DONTCARE 63 // write anything - just to force update #define P_UPDATE 0 /* R/W, see above */ Be Tireless Khashayar T: +61 2 8006 9884 F: +61 2 8103 2029 M: +61 400 419 626 On Wed, Sep 5, 2012 at 3:25 PM, Khashayar Azad <[email protected]> wrote: Hi Andrey, thank you very much for your answer. It actually helps a lot. Cheers. Be Tireless K T: +61 2 8003 4787 F: +61 2 8103 2029 M: +61 400 419 626 On Wed, Sep 5, 2012 at 3:24 PM, support-list <[email protected]> wrote: Hello Khahsayar, Porting 333 code to the 353 maybe as easy as recompiling it using the appropriate SDK or it may require re-writing of the code if it relies on some hardware-specific features that are different in the newer cameras. The second is not very likely because generally both the 353 hardware and software are more advanced than used in the earlier model, but still there is no universal answer to your question - it depends on the specifics of your project. What I would recommend is to follow documentation on http://wiki.elphel.com/index.php?title=Elphel_Software_Kit_for_Ubuntu and recompile and reflash the camera from source, then add/modify your custom code. If you'll get any specific problems in the process - please do not hesitate to describe them here and we'll try to help you to resolve them. Andrey ---- On Tue, 04 Sep 2012 21:54:24 -0700 Khashayar Azad <[email protected]> wrote ---- Hi Andrey, any update on this? Can you help? Be Tireless K T: +61 2 8003 4787 F: +61 2 8103 2029 M: +61 400 419 626 On Sat, Sep 1, 2012 at 7:11 AM, Khashayar Azad <[email protected]> wrote: Hi Andrey and thanks for the info. Do I just build the 333 based firmware using the newer SDK and then flash it using net boot on the 353 or do I need to do source modifications in order to be able to compile the code on the 353? In the process you pointed to I assume that I just replace the section pointing to the Elphel source with my own, is this correct? Please advise. _______________________________________________ Support-list mailing list [email protected] http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
_______________________________________________ Support-list mailing list [email protected] http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
