ElphelWiki - User contributions [en]

FFT Cuda

2010-11-05T01:23:38Z

Skinkie:

=== Input ===
* Image is presented in TIFF file structure
* Array of, FFT of kernels (64x64)

=== Todo ===
* Take a windows 128x128, step by 32 pixels
* Make a FFT (DFT_2D)
* Get nth-kernel, pad 32px zero's to each side
* Multiply FFT with kernel
* Inverse FFT of the result
* Save 128x128 window to the n'th position in the TIFF

=== Knowledge required ===
CuFFT is modeled after FFTW. To create a new operation we start with cufftPlan2d. The actual operation happens wth cufftExecC2C. cufftExecC2C takes input and output data, respectivily idata and odata in GPU memory.

To use the GPU memory use cudaMalloc.

=== How to copy from 'CPU' memory to 'GPU' memory? ===

cudaMemcpy(dstcudaMallocLocation, srchostTiffLocation, counthost, cudaMemcpyHostToDevice)

=== How to open a TIFF file? ===
Start with:
* TIFFOpen
* TIFFReadRGBAImage
* Copy Host memory to GPU memory

=== How to write a new TIFF file? ===
Start with:
* Copy GPU memory to Hostmemory
* TIFFOpen
* TIFFWriteTile

FFT Cuda

2010-11-05T01:18:59Z

Skinkie:

FFT Cuda

2010-11-05T01:13:44Z

Skinkie:

FFT Cuda

2010-11-05T01:02:46Z

Skinkie:

FFT Cuda

2010-11-05T00:46:02Z

Skinkie:

FFT Cuda

2010-11-05T00:45:38Z

Skinkie:

== FFT Cuda ==

=== Input ===
* Image is presented in TIFF file structure
* Array of, FFT of kernels (64x64)

=== Todo ===
* Take a windows 128x128, step by 32 pixels
* Make a FFT (DFT_2D)
* Get nth-kernel, pad 32px zero's to each side
* Multiply FFT with kernel
* Inverse FFT of the result
* Save 128x128 window to the n'th position in the TIFF

Talk:Sensors table

2010-09-08T12:22:52Z

Skinkie:

What about the Samsung BSI-CMOS sensors?

S5K4E5 5MP @ 60fps Full-HD
S5K2N1 14.6MP

373/Development

2009-10-31T02:00:09Z

Skinkie:

The 373 camera root and kernel will be compiled using [http://www.openembedded.org/ OpenEmbedded] on this wikipage we document some good to remember hints that most likely can be used for new development later. Babysteps ;)

=== Minicom ===
We are doing serial uploading in modemy file transfermode for Minicom this is ctrl-a s, modemy. Because browsing in Minicom is bad, it is good to set a default root directory in the configuration. Once you found your file, press Space and Enter.

In order to transfer with Minicom you will require the package '''lrzsz''', without it nothing happens.

=== Kernel Config ===
The defkernel in OpenEmbedded has an option: CONFIG_INITRAMFS_SOURCE, this should get the '''full path''' to the rootfs we want to serve. In order to get a new rootfs into the kernel:

<pre>
bitbake -c clean virtual/kernel
bitbake virtual/kernel
</pre>

This really sucks, because it takes a '''long''' time.

Additionally, disable CONFIG_RD_GZIP, for some smaller kernel replace it with:

<pre>
CONFIG_KERNEL_LZMA=y
CONFIG_RD_LZMA=y
</pre>

=== Making uImages as Ramdisk ===
<pre>
pundit:~/10373/angstrom-2008# ./staging/x86_64-linux/usr/bin/uboot-mkimage -n 'Simple Ramdisk Image' -A arm \
-O linux -T ramdisk -C gzip -d ./deploy/glibc/images/dm6467-evm/minimalist-image-dm6467-evm.jffs2 \
./deploy/glibc/images/dm6467-evm/test.gz
Image Name: Simple Ramdisk Image
Created: Fri Oct 30 19:42:12 2009
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 5767168 Bytes = 5632.00 kB = 5.50 MB
Load Address: 0x00000000
Entry Point: 0x00000000
</pre>

373/Development

2009-10-31T01:59:46Z

Skinkie:

The 373 camera root and kernel will be compiled using [http://www.openembedded.org/ OpenEmbedded] on this wikipage we document some good to remember hints that most likely can be used for new development later. Babysteps ;)

=== Minicom ===
We are doing serial uploading in modemy file transfermode for Minicom this is ctrl-a s, modemy. Because browsing in Minicom is bad, it is good to set a default root directory in the configuration. Once you found your file, press Space and Enter.

In order to transfer with Minicom you will require the package '''lrzsz''', without it nothing happens.

=== Kernel Config ===
The defkernel in OpenEmbedded has an option: CONFIG_INITRAMFS_SOURCE, this should get the '''full path''' to the rootfs we want to serve. In order to get a new rootfs into the kernel:

<pre>
bitbake -c clean virtual/kernel
bitbake virtual/kernel
</pre>

This really sucks, because it takes a '''long''' time.

Additionally, disable CONFIG_RD_GZIP, for some smaller kernel replace it with:

<pre>
CONFIG_KERNEL_LZMA=y
CONFIG_RD_LZMA=y
</pre>

=== Making uImages as Ramdisk ===
<pre>
pundit:~/10373/angstrom-2008# ./staging/x86_64-linux/usr/bin/uboot-mkimage -n 'Simple Ramdisk Image' -A arm -O linux -T ramdisk -C gzip -d ./deploy/glibc/images/dm6467-evm/minimalist-image-dm6467-evm.jffs2 ./deploy/glibc/images/dm6467-evm/test.gz
Image Name: Simple Ramdisk Image
Created: Fri Oct 30 19:42:12 2009
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 5767168 Bytes = 5632.00 kB = 5.50 MB
Load Address: 0x00000000
Entry Point: 0x00000000
</pre>

373/Development

2009-10-31T01:59:21Z

Skinkie: mkimage

The 373 camera root and kernel will be compiled using [http://www.openembedded.org/ OpenEmbedded] on this wikipage we document some good to remember hints that most likely can be used for new development later. Babysteps ;)

=== Minicom ===
We are doing serial uploading in modemy file transfermode for Minicom this is ctrl-a s, modemy. Because browsing in Minicom is bad, it is good to set a default root directory in the configuration. Once you found your file, press Space and Enter.

In order to transfer with Minicom you will require the package '''lrzsz''', without it nothing happens.

=== Kernel Config ===
The defkernel in OpenEmbedded has an option: CONFIG_INITRAMFS_SOURCE, this should get the '''full path''' to the rootfs we want to serve. In order to get a new rootfs into the kernel:

<pre>
bitbake -c clean virtual/kernel
bitbake virtual/kernel
</pre>

This really sucks, because it takes a '''long''' time.

Additionally, disable CONFIG_RD_GZIP, for some smaller kernel replace it with:

<pre>
CONFIG_KERNEL_LZMA=y
CONFIG_RD_LZMA=y
</pre>

=== Making uImages as Ramdisk ===
pundit:~/10373/angstrom-2008# ./staging/x86_64-linux/usr/bin/uboot-mkimage -n 'Simple Ramdisk Image' -A arm -O linux -T ramdisk -C gzip -d ./deploy/glibc/images/dm6467-evm/minimalist-image-dm6467-evm.jffs2 ./deploy/glibc/images/dm6467-evm/test.gz
Image Name: Simple Ramdisk Image
Created: Fri Oct 30 19:42:12 2009
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 5767168 Bytes = 5632.00 kB = 5.50 MB
Load Address: 0x00000000
Entry Point: 0x00000000

373/Development

2009-10-28T00:57:11Z

Skinkie: /* Kernel Config */

373/Development

2009-10-28T00:38:40Z

Skinkie:

Q and A

2009-03-30T03:08:42Z

Skinkie: /* Answers */

== About Q&A page ==
Hello, I have a question about the best way to set up the camera as a server, to assign IP's to clients that access the camera. Our application is in a medical lab, where the camera is looking at Petri dishes. The clients will access the camera, to execute a vision based system which determines antibiotic sensitivities for bacteria.

I could run the camera through a wireless router, and have the router assign IP's to the clients. Would it be simple to install a dhcp daemon on the camera to serve incoming requests?

Thank you,

Per Bj. Bro

== Answers ==

* I think the quickest way is to compile DNSMasq for Etrax (udhcpd is not installed by default), this will give you all what your 'clients' want. DNS, DHCP, etc. If you want more info just reply here or come to IRC. --[[User:Skinkie|Skinkie]] 22:08, 29 March 2009 (CDT)

Q and A

2009-03-30T03:08:22Z

Skinkie: DNSMasq

Compass Widget

2009-03-29T11:55:35Z

Skinkie:

== Use Case ==

You would like to see the direction your camera is heading.

== Implementation ==

The widget is implemented as SVG, Javascript and a php script to expose the exif data.

== Screenshots ==

[[Image:Svgcompass.png]]

== Finished this task ==
http://elphelcommunity.cvs.sourceforge.net/viewvc/elphelcommunity/elphel353-7.1-community/apps/widgets/compass/

== Wishlist ==
* Adding widgets voor rolling and pitch.
* Smooth animation

User:Skinkie

2009-03-28T10:14:25Z

Skinkie: /* Timeline */

My name is Stefan de Konink, I live in The Netherlands and study Artificial Intelligence at the University of Amsterdam. Almost heading for writing a MSc thesis. I noticed Elphel years ago when they first made an implementation of Theora in hardware. Later I found that they made cameras that also did Geo. Personally I would really like to have a professional still camera that is able to be scripted. Canon is a solution for that, but annoying as I am... all my lenses are Nikon based ;)

I'm active in the OpenStreetMap community and because of adding GPS features our project [[OSMCAM]] is selection to get a 'free' developer camera there is work to do. At this page I'll keep a diary what I am doing so my conscious is clean and I'm really using this device in a way that it has been offered to me.

== Timeline ==

* '''DONE''' [http://wiki.elphel.com/index.php?title=Elphel_Software_Kit_for_Ubuntu#Packages_requirement_for_Ubuntu Getting the etrax toolkit to work]
* [[Gentoo embedded]]... (yeah right!)
* '''DONE''' [[Cherokee]]
* '''DONE''' [[Implement calibration]]
* '''DONE''' [[Compass Widget|AJAX Compass]] + Calibration
* OpenLayers tayormade for the Elphel
* Making some use-cases for the GPS tools and interface

Compass Widget

2009-03-28T10:11:10Z

Skinkie: /* Screenshots */

File:Svgcompass.png

2009-03-28T10:10:05Z

Skinkie: SVG Compass screenshot

SVG Compass screenshot

Compass Widget

2009-03-28T10:09:38Z

Skinkie:

User:Skinkie

2009-03-28T10:03:25Z

Skinkie: /* Timeline */

My name is Stefan de Konink, I live in The Netherlands and study Artificial Intelligence at the University of Amsterdam. Almost heading for writing a MSc thesis. I noticed Elphel years ago when they first made an implementation of Theora in hardware. Later I found that they made cameras that also did Geo. Personally I would really like to have a professional still camera that is able to be scripted. Canon is a solution for that, but annoying as I am... all my lenses are Nikon based ;)

I'm active in the OpenStreetMap community and because of adding GPS features our project [[OSMCAM]] is selection to get a 'free' developer camera there is work to do. At this page I'll keep a diary what I am doing so my conscious is clean and I'm really using this device in a way that it has been offered to me.

== Timeline ==

* '''DONE''' [http://wiki.elphel.com/index.php?title=Elphel_Software_Kit_for_Ubuntu#Packages_requirement_for_Ubuntu Getting the etrax toolkit to work]
* [[Gentoo embedded]]... (yeah right!)
* '''DONE''' [[Cherokee]]
* '''DONE''' [[Implement calibration]]
* '''DONE''' [[Compass Widget|AJAX Compass]] + Calibration
* Making some use-cases for the GPS tools and interface

Implement calibration

2009-03-28T10:01:38Z

Skinkie: /* Working on this task */

== Problem ==
In order to reliably use the compass it needs to calibrated by the user. This process can be initiated by accessing the compass module, and providing it the required commands. Sadly only one daemon can access the information of a serial port and it is thus required to make it available to multiple applications concurrently.

== Calibration Procedure ==
The callibration can only happen if the module is leveled, hence the pitch and roll are less than one degree off, and the camera is slowely spinned around while doing this. Other forms of calibration, for example by providing magnetic field strength should be open for the user.

This would require an application that must be:
* Allowed to write to the module
* Able to initiate the command sequence
* Able to detect pitch/roll
* Able to detect end of calibration sequence
* Available to the user in a user friendly way

The application could:
* Fetch field strength for its GPS position from an information source on the internet (if available)

== Finished this task ==
http://elphelcommunity.cvs.sourceforge.net/viewvc/elphelcommunity/elphel353-7.1-community/apps/compass-calibration/

== References ==
http://www.ocean-server.com/download/OS5000_Compass_Manual.pdf

Talk:Fast Boot

2008-12-29T04:42:54Z

Skinkie:

I have played with things like uboot and lzma compression for embedded routers recently. I wonder if it wouldn't be possible to shrink the basics of the firmware enormously. To a predefined set of functionalities. Bootup time of 2 secs is nice. But what can one expect after 2 seconds? --[[User:Skinkie|Skinkie]] 22:42, 28 December 2008 (CST)

User:Skinkie

2008-09-21T23:44:42Z

Skinkie:

My name is Stefan de Konink, I live in The Netherlands and study Artificial Intelligence at the University of Amsterdam. Almost heading for writing a MSc thesis. I noticed Elphel years ago when they first made an implementation of Theora in hardware. Later I found that they made cameras that also did Geo. Personally I would really like to have a professional still camera that is able to be scripted. Canon is a solution for that, but annoying as I am... all my lenses are Nikon based ;)

I'm active in the OpenStreetMap community and because of adding GPS features our project [[OSMCAM]] is selection to get a 'free' developer camera there is work to do. At this page I'll keep a diary what I am doing so my conscious is clean and I'm really using this device in a way that it has been offered to me.

== Timeline ==

* '''DONE''' [http://wiki.elphel.com/index.php?title=Elphel_Software_Kit_for_Ubuntu#Packages_requirement_for_Ubuntu Getting the etrax toolkit to work]
* [[Gentoo embedded]]... (yeah right!)
* '''DONE''' [[Cherokee]]
* '''DONE''' [[Implement calibration]]
* AJAX Compass + Calibration
* Making some use-cases for the GPS tools and interface

Firefox Resize Bug

2008-09-19T22:56:48Z

Skinkie:

=== Problem ===
When a user starts the webinterface by clicking on the Ok button in the Firefox webbrowser, Firefox will add a popup bar in the new window. This bar causes the webinterface to rescale down.

=== Workaround ===
* Don't press OK, just cancel
* Allow popups from 192.168.0.9
* Quickly remove the popup bar by pressing the cross on the right

Known Bugs

2008-09-19T22:47:54Z

Skinkie:

On this page we will collect the bugs users have observed using the camera or the embedded software running on top of it. If you have an issue, please look at the list here. If not present add it here.

=== Webinterface ===

* [[Firefox Resize Bug]] when the popup blockline is present in the webinterface, by launching the popup after pressing ok, the webinterface resizes down to an absolute minimum.

Known Bugs

2008-09-19T22:47:20Z

Skinkie: Firefox

On this page we will collect the bugs users have observed using the camera or the embedded software running on top of it. If you have an issue, please look at the list here. If not present add it here.

=== Webinterface ===

[*] [Firefox Resize Bug]; when the popup blockline is present in the webinterface, by launching the popup after pressing ok, the webinterface resizes down to an absolute minimum.

Wishlist

2008-09-18T23:39:15Z

Skinkie:

Today I received a development sample of the 353 camera. As ''user'' I noticed some things I wanted to have, I hope anyone that has ideas can write them on a central place and make a new page on the wiki to it. If a project has been completed just add the developer that did it, or is busy on it.

=== Sensor ===
* [[Dead/Hot pixel correction]]

=== Compass ===
* '''DONE''' [[Implement calibration]]

=== Networking ===
* [[DHCP (timeouted) and DNS-SD]]

=== Fastest Boot ===
* [[Fast Boot]]

=== C API ===
* [[C API]]

=== UDMA support ===
* Enable [[UDMA]] in the Axis kernel. Needed to support most fast CF cards, will also boost speed on SATA.

Implement calibration

2008-09-18T23:38:42Z

Skinkie: /* Working on this task */

== Problem ==
In order to reliably use the compass it needs to calibrated by the user. This process can be initiated by accessing the compass module, and providing it the required commands. Sadly only one daemon can access the information of a serial port and it is thus required to make it available to multiple applications concurrently.

== Calibration Procedure ==
The callibration can only happen if the module is leveled, hence the pitch and roll are less than one degree off, and the camera is slowely spinned around while doing this. Other forms of calibration, for example by providing magnetic field strength should be open for the user.

This would require an application that must be:
* Allowed to write to the module
* Able to initiate the command sequence
* Able to detect pitch/roll
* Able to detect end of calibration sequence
* Available to the user in a user friendly way

The application could:
* Fetch field strength for its GPS position from an information source on the internet (if available)

== Working on this task ==
Implemented GPSd driver for the compass, now going to test. --[[User:Skinkie|Skinkie]] 14:34, 9 September 2008 (CDT)

[http://kinkrsoftware.nl/contrib/elphel/compass_calibration.c]

== References ==
http://www.ocean-server.com/download/OS5000_Compass_Manual.pdf

Implement calibration

2008-09-18T23:37:37Z

Skinkie:

== Problem ==
In order to reliably use the compass it needs to calibrated by the user. This process can be initiated by accessing the compass module, and providing it the required commands. Sadly only one daemon can access the information of a serial port and it is thus required to make it available to multiple applications concurrently.

== Calibration Procedure ==
The callibration can only happen if the module is leveled, hence the pitch and roll are less than one degree off, and the camera is slowely spinned around while doing this. Other forms of calibration, for example by providing magnetic field strength should be open for the user.

This would require an application that must be:
* Allowed to write to the module
* Able to initiate the command sequence
* Able to detect pitch/roll
* Able to detect end of calibration sequence
* Available to the user in a user friendly way

The application could:
* Fetch field strength for its GPS position from an information source on the internet (if available)

== Working on this task ==
Implemented GPSd driver for the compass, now going to test. --[[User:Skinkie|Skinkie]] 14:34, 9 September 2008 (CDT)
A [http://kinkrsoftware.nl/contrib/elphel/compass_calibration.c|Tool] has been made, needs some minor updates for being a CGI program, after that is done it will be in the Elphel CVS.

== References ==
http://www.ocean-server.com/download/OS5000_Compass_Manual.pdf

Implement calibration

2008-09-09T19:34:38Z

Skinkie: gpsd work in process

== Problem ==
In order to reliably use the compass it needs to calibrated by the user. This process can be initiated by accessing the compass module, and providing it the required commands. Sadly only one daemon can access the information of a serial port and it is thus required to make it available to multiple applications concurrently.

== Calibration Procedure ==
The callibration can only happen if the module is leveled, hence the pitch and roll are less than one degree off, and the camera is slowely spinned around while doing this. Other forms of calibration, for example by providing magnetic field strength should be open for the user.

This would require an application that must be:
* Allowed to write to the module
* Able to initiate the command sequence
* Able to detect pitch/roll
* Able to detect end of calibration sequence
* Available to the user in a user friendly way

The application could:
* Fetch field strength for its GPS position from an information source on the internet (if available)

== Working on this task ==
Implemented GPSd driver for the compass, now going to test. --[[User:Skinkie|Skinkie]] 14:34, 9 September 2008 (CDT)

== References ==
http://www.ocean-server.com/download/OS5000_Compass_Manual.pdf

Implement calibration

2008-09-09T02:47:40Z

Skinkie: Real update with todo

== Problem ==
In order to reliably use the compass it needs to calibrated by the user. This process can be initiated by accessing the compass module, and providing it the required commands. Sadly only one daemon can access the information of a serial port and it is thus required to make it available to multiple applications concurrently.

== Calibration Procedure ==
The callibration can only happen if the module is leveled, hence the pitch and roll are less than one degree off, and the camera is slowely spinned around while doing this. Other forms of calibration, for example by providing magnetic field strength should be open for the user.

This would require an application that must be:
* Allowed to write to the module
* Able to initiate the command sequence
* Able to detect pitch/roll
* Able to detect end of calibration sequence
* Available to the user in a user friendly way

The application could:
* Fetch field strength for its GPS position from an information source on the internet (if available)

== Working on this task ==
--[[User:Skinkie|Skinkie]] 21:47, 8 September 2008 (CDT)

== References ==
http://www.ocean-server.com/download/OS5000_Compass_Manual.pdf

Talk:Implement calibration

2008-09-09T00:49:36Z

Skinkie:

You are using the ocean server compass?

Are you using the depth sensor as well?

There is no calibration SW? or just no linux SW?
Would you know if there is depth calibration SW?

I would guess that the elphel should just be able to parse NMEA-0183, then it
can work with most compass modules (KVH, PNI TCM-2, etc.)

--[[User:Aegdss|aegdss]] 18:19:40, 2008-09-05 (CDT)

On IRC I heared there is no calibration on the compass. So probably it only gives lets say the rotation it makes like a gyro does.

--[[User:Skinkie|Skinkie]] 21:32, 5 September 2008 (CDT)

FWIW, the compass does support hard-iron calibration via simple serial commands plus manual rotation of the compass. See [http://www.ocean-server.com/download/OS5000_Compass_Manual.pdf ocean server compass manual]. This is similar to other compass modules. It would seem that this is an application level procedure and not really suitable for embedding in the camera. It would be nice if the camera did allow for a redirect of the serial comms to a network socket or something.

--[[User:Aegdss|aegdss]] 13:38:42, 2008-09-08 (CDT)

Why not doing it from the camera ? It's what we did the first time we got the compass. We calibrate it via the serial port with some special commands. It is possible I think to build a PHP app that will launch compass calibration on request from the browser. So the user will only have to manually rotate the camera.

--[[User:Polto|Alexandre.Poltorak]] 14:10, 8 September 2008 (CDT)

You guys love PHP don't ya ;) I'll see what I can come up with.

--[[User:Skinkie|Skinkie]] 15:13, 8 September 2008 (CDT)

No reason you couldn't do it in the camera, and using PHP if you wanted, but in some situations it would be nice to be able to get high update rate (10 Hz or whatever) from the compass without having to transmit images as well. If the camera could bridge the net interface to the serial port this would be trivial. But that's the really nice thing about open source, people can implement many different methods.

--[[User:Aegdss|aegdss]] 18:27:21, 2008-09-08 (CDT)

I'll take a look into the documentation. I think the main point is to write a small server (maybe compass is already this) that allows multiple sources to query the actual input at a certain time or a continuous flow. And is able to do the calibration effort by some simple input commands.

Just read the entire documentation again, it seems to be trival (if direct access to the module is possible) to make a neat callibration procedure. Basically instruct the user with some pictures what to do. It requires some AJAX to get it life, but I guess the code for that must be somewhere around.

--[[User:Skinkie|Skinkie]] 19:49, 8 September 2008 (CDT)

User talk:Bnewbold

2008-09-09T00:19:47Z

Skinkie: /* ROV */

Hi.

The problem with VLC is due to RTP/RTSP implementation with live555. Our patches for mplayer solve this problem, you can try to modify the patch to work with VLC.

For lenses: try the Fujinon DF6HA-1B

ccam.cgi: we are working now on rewriting it with PHP. for the interface: yes camvc is something standard, you need something more adapted to your needs. Why not use Pure-Data to build a real hardware control unit? (with buttons, cross faders etc..)

== ROV ==

What is the maximum pressure you expect the Elphel to be handling? I see a possibility to use an Elphel as ROV too, but I wonder if the pressure it must handle could break it (especially when surfacing again).

Zook

We have made several housings for the camera. our latest housing will go 1000M deep. We only plan on going 300M this year but in the future we hope to go 2500M with this camera.

Of course it must be understood that the camera is in a pressure housing. The actual pressure that the camera parts (electronics boards 10353, 10359, sensors, and cables) will experience is only 1 atm (14.7 psi)

--[[User:Aegdss|aegdss]] 16:39:00, 2008-09-05 (CDT)

In this case you have a box in a box, how do you handle the optics in that respect? Is your ''hardware design'' also ''open'' I would really like to see how you have solved this.

--[[User:Skinkie|Skinkie]] 19:19, 8 September 2008 (CDT)

Talk:Implement calibration

2008-09-09T00:16:36Z

Skinkie:

You are using the ocean server compass?

Are you using the depth sensor as well?

There is no calibration SW? or just no linux SW?
Would you know if there is depth calibration SW?

I would guess that the elphel should just be able to parse NMEA-0183, then it
can work with most compass modules (KVH, PNI TCM-2, etc.)

--[[User:Aegdss|aegdss]] 18:19:40, 2008-09-05 (CDT)

On IRC I heared there is no calibration on the compass. So probably it only gives lets say the rotation it makes like a gyro does.

--[[User:Skinkie|Skinkie]] 21:32, 5 September 2008 (CDT)

FWIW, the compass does support hard-iron calibration via simple serial commands plus manual rotation of the compass. See [http://www.ocean-server.com/download/OS5000_Compass_Manual.pdf ocean server compass manual]. This is similar to other compass modules. It would seem that this is an application level procedure and not really suitable for embedding in the camera. It would be nice if the camera did allow for a redirect of the serial comms to a network socket or something.

--[[User:Aegdss|aegdss]] 13:38:42, 2008-09-08 (CDT)

Why not doing it from the camera ? It's what we did the first time we got the compass. We calibrate it via the serial port with some special commands. It is possible I think to build a PHP app that will launch compass calibration on request from the browser. So the user will only have to manually rotate the camera.

--[[User:Polto|Alexandre.Poltorak]] 14:10, 8 September 2008 (CDT)

You guys love PHP don't ya ;) I'll see what I can come up with.

--[[User:Skinkie|Skinkie]] 15:13, 8 September 2008 (CDT)

No reason you couldn't do it in the camera, and using PHP if you wanted, but in some situations it would be nice to be able to get high update rate (10 Hz or whatever) from the compass without having to transmit images as well. If the camera could bridge the net interface to the serial port this would be trivial. But that's the really nice thing about open source, people can implement many different methods.

--[[User:Aegdss|aegdss]] 18:27:21, 2008-09-08 (CDT)

I'll take a look into the documentation. I think the main point is to write a small server (maybe compass is already this) that allows multiple sources to query the actual input at a certain time or a continuous flow. And is able to do the calibration effort by some simple input commands.

--[[User:Skinkie|Skinkie]] 19:16, 8 September 2008 (CDT)

Talk:Implement calibration

2008-09-08T20:13:54Z

Skinkie:

UDMA

2008-09-08T17:25:37Z

Skinkie:

Is this just a standard kernel setting?

Wishlist

2008-09-08T17:25:16Z

Skinkie: /* UDMA support */

Today I received a development sample of the 353 camera. As ''user'' I noticed some things I wanted to have, I hope anyone that has ideas can write them on a central place and make a new page on the wiki to it. If a project has been completed just add the developer that did it, or is busy on it.

=== Sensor ===
* [[Dead/Hot pixel correction]]

=== Compass ===
* [[Implement calibration]]

=== Networking ===
* [[DHCP (timeouted) and DNS-SD]]

=== Fastest Boot ===
* [[Fast Boot]]

=== C API ===
* [[C API]]

=== UDMA support ===
* Enable [[UDMA]] in the Axis kernel. Needed to support most fast CF cards, will also boost speed on SATA.

Talk:Gentoo embedded

2008-09-08T03:02:21Z

Skinkie:

Why don't you try to make an ebuild for Axis' cris-dist-glibc ?

--[[User:Polto|Alexandre.Poltorak]] 13:24, 6 September 2008 (CDT)

I have created a crossdev crisv32-axis-linux-uclibc. Glibc was broken on another point in the middle of compilation. Now I'm trying to actually get a normal program to compile with the toolchain just made.
And to answer your question, to get the axis compilation to work is trivial, I made a hello world with that, but it is not trivial is to compile things with an old GCC ;) So if this works it gives me an uclibc system, I can run the camera from and a cross compiler to make software. And I presume crisv32 is more optimal than cris.

--[[User:Skinkie|Skinkie]] 13:52, 6 September 2008 (CDT)

As far as I know cris and crisv32 are different arch. EtraxFS is crisv32.

About testing the rootfs... It's safe. The camera is unkillable. :) You can boot in a network boot mode and reflash the camera.

The network boot loader is build in to the EtraxFS SoC. To put the camera in this mode you have to power-up-down-up the camera 6 times with a 3 second delay between each operation. More on this in the beginning of http://linuxdevices.com/articles/AT5102023409.html

--[[User:Polto|Alexandre.Poltorak]] 20:07, 6 September 2008 (CDT)

...I really think I should connect the serial cable and become a professional embedded user ;) Does it do TFTP? Or is the network boot something proprietary?

--[[User:Skinkie|Skinkie]] 11:15, 7 September 2008 (CDT)

Are you sure you need uclibc? As I understand this library is used for the processors w/o MMU. ETRAX (and camera) uses regular libc ( http://192.168.0.9/admin-bin/editcgi.cgi?file=/lib )--[[User:Andrey.filippov|Andrey.filippov]] 20:18, 7 September 2008 (CDT)

''Need'' is a big word, Axis supports newlib. But I ''needed'' a supported libc version for crosscompiling, and a ''newer'' GCC. That uClibc is also smaller could be considered beneficial.

--[[User:Skinkie|Skinkie]] 22:02, 7 September 2008 (CDT)

Talk:Gentoo embedded

2008-09-07T16:15:53Z

Skinkie:

Gentoo embedded

2008-09-07T01:47:24Z

Skinkie: /* Howto do it */

In order to get Embedded support somethings obviously need to be compiled. Now this is not yet going smoothly but I'll give some indication what can be done to fix it and where I am struggling.

Currently I have compiled a toolchain with gcc 4.3.1, uclibc-2008-09-06, a patch and patience. I am able to run code on the camera, if it is statically linked. Technically I could try to make a rootfs and see what happens. But currently I don't have the time to test that (and I don't want to break my cam before [http://www.softwarefreedomday.eu/ SoftwareFreedomDay].

Keep in mind that the 'native' cris memcpy.c is broken, I am positive I can get it into shape :) Please validate the code I write, I'm not an embedded professional :)

== Howto do it ==
* export USE="-iconv -nls -userlocales -fortran -mudflap -openmp nocxx minimal savedconfig"
* crossdev --target crisv32-axis-linux-uclibc

However due to screwups in linux-headers you have to:
* manually copy the linux kernel includes (gentoo has amnesia!)
* symlink asm/arch-v32 to asm/arch
* use the latest uclibc, patch it

* use your own config of uclibc, for now disable platform specific strings
* hope it works automatically, trust me it won't

In that case:
* emerge crisv32-axis-linux-uclibc/gcc
* emerge crisv32-axis-linux-uclibc/uclibc
* emerge crisv32-axis-linux-uclibc/gcc

== Output first tests ==
[http://developer.axis.com/wiki/doku.php?id=axis:gdb-debug-threads]

crisv32-axis-linux-uclibc-gcc --static -o /tmp/test2 /tmp/test2.c /mnt/dv/elphel/uClibc/lib/libpthread.a

[root@Elphel353 /mnt/flash/root/test]1157# ./test2
Hello World from 0!
Hello World from 1!
Hello World from 2!
Hello World from 3!
Hello World from 4!

== uclibc patch ==
--- libc/sysdeps/linux/cris/crti.S.orig 2008-09-06 23:51:14.017004350 +0200
+++ libc/sysdeps/linux/cris/crti.S 2008-09-06 23:54:28.477004350 +0200
@@ -10,8 +10,7 @@
move $srp,$r1
subq 4,$sp
move.d $r0,[$sp]
- move.d $pc,$r0
- sub.d .:GOTOFF,$r0
+ lapc _GLOBAL_OFFSET_TABLE_,$r0
.align 1

.section .fini
@@ -24,6 +23,5 @@
move $srp,$r1
subq 4,$sp
move.d $r0,[$sp]
- move.d $pc,$r0
- sub.d .:GOTOFF,$r0
+ lapc _GLOBAL_OFFSET_TABLE_,$r0
.align 1

Gentoo embedded

2008-09-07T01:46:44Z

Skinkie:

Talk:Cherokee

2008-09-07T01:37:06Z

Skinkie:

Currently cherokee-worker works for me, but cherokee itself (the guardian) doesn't. This is a bug. --[[User:Skinkie|Skinkie]] 20:37, 6 September 2008 (CDT)

Talk:Main Page

2008-09-07T01:33:48Z

Skinkie: /* Wishlist */ == done

Ilya, that seems correct. We should probably remove 10331/332/334, RTC from user docs - it is for debvelopers now. When there will be lens control and USB we will make user documentation for these features.

User documentattion should probably target needs of a camera _user_ - how to operate it (with ...) How to upgrade software? How to install client software on ... What to do if you see no image, distorted image. Why camera does not respond etc.

Andrey
----
OK, I will correct the pages you say about.

Ilya
----

Roadmap is not for developers only.
It can contain an information about future of the user interface too.

Sergey
----

Sure, not only for developers and curious users are welcome to read that section too. I was just suggesting to keep [[User Documentation]] exactly as a prototype for the static pages to be included with the cameras.

[[User:Andrey.filippov|Andrey.filippov]] 01:58, 24 September 2005 (MDT)

----

Ups, I don't know the delete page procedure. How I can do it?

Ilya

----

Me too - need to read documentation. Or just remove links to it, mark it on top as deleted and leave it there - maybe we will later use it (at list the name).
BTW - there is a "signature" button above the text area field that inserts you login name and timestamp.
--[[User:Andrey.filippov|Andrey.filippov]] 11:50, 24 September 2005 (MDT)

----

I read documentation, but I not find the information about that.

P.S. Signature test.

But I'm stupid, I don't understand the applicability, sorry ;)

OK, I did it ;)

--[[User:Ilya|Ilya]] 05:39, 4 October 2005 (MDT)

Cherokee

2008-09-07T01:32:56Z

Skinkie:

With the right toolchain everything gets more easy this is how you get cherokee on your cam:

export CC=crisv32-axis-linux-uclibc-gcc
export LD=crisv32-axis-linux-uclibc-ld
export AR=crisv32-axis-linux-uclibc-ar

ac_cv_func_malloc_0_nonnull=yes \
ac_cv_func_realloc_0_nonnull=yes \
./autogen.sh \
--host=crisv32-axis-linux-uclibc \
--prefix=/mnt/flask/root/cherokee \
--enable-static \
--enable-shared=no \
--enable-static-module=all \
--disable-tls \
--enable-beta \
--enable-trace \
CC=crisv32-axis-linux-uclibc-gcc
make -j2

Since we want it to make ''real'' static.

cd cherokee
crisv32-axis-linux-uclibc-gcc -g -O2 -o cherokee main.o -static
crisv32-axis-linux-uclibc-gcc -g -O2 -o cherokee-worker main_worker.o -D_XOPEN_SOURCE=500 ./.libs/libcherokee-base.a ./.libs/libcherokee-server.a -lcrypt /mnt/dv/elphel/cherokee/cherokee/.libs/libcherokee-client.a /mnt/dv/elphel/cherokee/cherokee/.libs/libcherokee-base.a -lpthread -ldl -static
cd ..

Now install it

make install

You could remove useless stuff now, such as documentation, includes. After this, copy it to your device.

scp -r /mnt/flash/root/cherokee root@192.168.0.9:/mnt/flash/root/.

As you can see from the above everything is still compiled with debugging on, and even -O2. You could shrink it more if you specify:

CFLAGS=-Os

And strip the binaries afterward.

User:Skinkie

2008-09-07T01:23:44Z

Skinkie:

My name is Stefan de Konink, I live in The Netherlands and study Artificial Intelligence at the University of Amsterdam. Almost heading for writing a MSc thesis. I noticed Elphel years ago when they first made an implementation of Theora in hardware. Later I found that they made cameras that also did Geo. Personally I would really like to have a professional still camera that is able to be scripted. Canon is a solution for that, but annoying as I am... all my lenses are Nikon based ;)

I'm active in the OpenStreetMap community and because of adding GPS features our project [[OSMCAM]] is selection to get a 'free' developer camera there is work to do. At this page I'll keep a diary what I am doing so my conscious is clean and I'm really using this device in a way that it has been offered to me.

== Timeline ==

* '''DONE''' [http://wiki.elphel.com/index.php?title=Elphel_Software_Kit_for_Ubuntu#Packages_requirement_for_Ubuntu Getting the etrax toolkit to work]
* [[Gentoo embedded]]... (yeah right!)
* '''DONE''' [[Cherokee]]
* Making some use-cases for the GPS tools and interface

Gentoo embedded

2008-09-07T00:29:09Z

Skinkie:

In order to get Embedded support somethings obviously need to be compiled. Now this is not yet going smoothly but I'll give some indication what can be done to fix it and where I am struggling.

Currently I have compiled a toolchain with gcc 4.3.1, uclibc-2008-09-06, a patch and patience. I am able to run code on the camera, if it is statically linked. Technically I could try to make a rootfs and see what happens. But currently I don't have the time to test that (and I don't want to break my cam before [http://www.softwarefreedomday.eu/ SoftwareFreedomDay].

Keep in mind that the 'native' cris memcpy.c is broken, I am positive I can get it into shape :) Please validate the code I write, I'm not an embedded professional :)

== Output first tests ==
[http://developer.axis.com/wiki/doku.php?id=axis:gdb-debug-threads]

crisv32-axis-linux-uclibc-gcc --static -o /tmp/test2 /tmp/test2.c /mnt/dv/elphel/uClibc/lib/libpthread.a

[root@Elphel353 /mnt/flash/root/test]1157# ./test2
Hello World from 0!
Hello World from 1!
Hello World from 2!
Hello World from 3!
Hello World from 4!

== uclibc patch ==
--- libc/sysdeps/linux/cris/crti.S.orig 2008-09-06 23:51:14.017004350 +0200
+++ libc/sysdeps/linux/cris/crti.S 2008-09-06 23:54:28.477004350 +0200
@@ -10,8 +10,7 @@
move $srp,$r1
subq 4,$sp
move.d $r0,[$sp]
- move.d $pc,$r0
- sub.d .:GOTOFF,$r0
+ lapc _GLOBAL_OFFSET_TABLE_,$r0
.align 1

.section .fini
@@ -24,6 +23,5 @@
move $srp,$r1
subq 4,$sp
move.d $r0,[$sp]
- move.d $pc,$r0
- sub.d .:GOTOFF,$r0
+ lapc _GLOBAL_OFFSET_TABLE_,$r0
.align 1

Gentoo embedded

2008-09-06T23:55:30Z

Skinkie:

In order to get Embedded support somethings obviously need to be compiled. Now this is not yet going smoothly but I'll give some indication what can be done to fix it and where I am struggling.

Currently I have compiled a toolchain with gcc 4.3.1, uclibc-2008-09-06, a patch and patience. I am able to run code on the camera, if it is statically linked. Technically I could try to make a rootfs and see what happens. But currently I don't have the time to test that (and I don't want to break my came before [http://www.softwarefreedomday.eu/ SoftwareFreedomDay].

Keep in mind that the 'native' cris memcpy.c is broken, I am positive I can get it into shape :) Please validate the code I write, I'm not an embedded professional :)

== Output first tests ==
[http://developer.axis.com/wiki/doku.php?id=axis:gdb-debug-threads]

crisv32-axis-linux-uclibc-gcc --static -o /tmp/test2 /tmp/test2.c /mnt/dv/elphel/uClibc/lib/libpthread.a

[root@Elphel353 /mnt/flash/root/test]1157# ./test2
Hello World from 0!
Hello World from 1!
Hello World from 2!
Hello World from 3!
Hello World from 4!

== uclibc patch ==
--- libc/sysdeps/linux/cris/crti.S.orig 2008-09-06 23:51:14.017004350 +0200
+++ libc/sysdeps/linux/cris/crti.S 2008-09-06 23:54:28.477004350 +0200
@@ -10,8 +10,7 @@
move $srp,$r1
subq 4,$sp
move.d $r0,[$sp]
- move.d $pc,$r0
- sub.d .:GOTOFF,$r0
+ lapc _GLOBAL_OFFSET_TABLE_,$r0
.align 1

.section .fini
@@ -24,6 +23,5 @@
move $srp,$r1
subq 4,$sp
move.d $r0,[$sp]
- move.d $pc,$r0
- sub.d .:GOTOFF,$r0
+ lapc _GLOBAL_OFFSET_TABLE_,$r0
.align 1

Gentoo embedded

2008-09-06T23:41:27Z

Skinkie:

In order to get Embedded support somethings obviously need to be compiled. Now this is not yet going smoothly but I'll give some indication what can be done to fix it and where I am strugling.

I am able to compile uclibc-0.29 with gcc-4.3.1, but out of the box glibc or uclibc is not possible. I'll try to get the ebuild of uclibc-0.29 and see if I can make some changes to it so it will leave us a successful uclibc. (That will still lack pthreads...)

Also the 'native' cris memcpy.c is broken :(

== Output first tests ==
[http://developer.axis.com/wiki/doku.php?id=axis:gdb-debug-threads]

crisv32-axis-linux-uclibc-gcc --static -o /tmp/test2 /tmp/test2.c /mnt/dv/elphel/uClibc/lib/libpthread.a

[root@Elphel353 /mnt/flash/root/test]1157# ./test2
Hello World from 0!
Hello World from 1!
Hello World from 2!
Hello World from 3!
Hello World from 4!

== uclibc patch ==
--- libc/sysdeps/linux/cris/crti.S.orig 2008-09-06 23:51:14.017004350 +0200
+++ libc/sysdeps/linux/cris/crti.S 2008-09-06 23:54:28.477004350 +0200
@@ -10,8 +10,7 @@
move $srp,$r1
subq 4,$sp
move.d $r0,[$sp]
- move.d $pc,$r0
- sub.d .:GOTOFF,$r0
+ lapc _GLOBAL_OFFSET_TABLE_,$r0
.align 1

.section .fini
@@ -24,6 +23,5 @@
move $srp,$r1
subq 4,$sp
move.d $r0,[$sp]
- move.d $pc,$r0
- sub.d .:GOTOFF,$r0
+ lapc _GLOBAL_OFFSET_TABLE_,$r0
.align 1

Gentoo embedded

2008-09-06T23:41:15Z

Skinkie: big change

In order to get Embedded support somethings obviously need to be compiled. Now this is not yet going smoothly but I'll give some indication what can be done to fix it and where I am strugling.

I am able to compile uclibc-0.29 with gcc-4.3.1, but out of the box glibc or uclibc is not possible. I'll try to get the ebuild of uclibc-0.29 and see if I can make some changes to it so it will leave us a successful uclibc. (That will still lack pthreads...)

Also the 'native' cris memcpy.c is broken :(

== Output first tests ==
[[http://developer.axis.com/wiki/doku.php?id=axis:gdb-debug-threads]]

crisv32-axis-linux-uclibc-gcc --static -o /tmp/test2 /tmp/test2.c /mnt/dv/elphel/uClibc/lib/libpthread.a

[root@Elphel353 /mnt/flash/root/test]1157# ./test2
Hello World from 0!
Hello World from 1!
Hello World from 2!
Hello World from 3!
Hello World from 4!

== uclibc patch ==
--- libc/sysdeps/linux/cris/crti.S.orig 2008-09-06 23:51:14.017004350 +0200
+++ libc/sysdeps/linux/cris/crti.S 2008-09-06 23:54:28.477004350 +0200
@@ -10,8 +10,7 @@
move $srp,$r1
subq 4,$sp
move.d $r0,[$sp]
- move.d $pc,$r0
- sub.d .:GOTOFF,$r0
+ lapc _GLOBAL_OFFSET_TABLE_,$r0
.align 1

.section .fini
@@ -24,6 +23,5 @@
move $srp,$r1
subq 4,$sp
move.d $r0,[$sp]
- move.d $pc,$r0
- sub.d .:GOTOFF,$r0
+ lapc _GLOBAL_OFFSET_TABLE_,$r0
.align 1

Talk:Gentoo embedded

2008-09-06T18:52:20Z

Skinkie: