Line 20: Line 20:
  
 
<span style="color: red; font-weight: bold">TODO: Add image which shows structure of module communication (WebGUI -> RESTServer > Daemon, and back)</span>
 
<span style="color: red; font-weight: bold">TODO: Add image which shows structure of module communication (WebGUI -> RESTServer > Daemon, and back)</span>
 +
 +
The control daemon project currently consists of three different modules:
 +
* '''Web UI''' - HTML5, sends REST requests to the backend, currently by using JQuery (still evaluating alternatives)
 +
* '''RESTServer''' - receives REST requests, converts them to Flatbuffers packages and sends them to the daemon, through socket
 +
* '''Daemon''' - processes received packages and calls suitable handler
 +
  
 
=== Unit tests ===
 
=== Unit tests ===

Revision as of 00:26, 8 December 2017

1 Control Deamon

>>>>TODO Overview text.

Currently, booting up the camera is as follows:

  • A systemd service is activated which runs a shell script
  • This script then loads a bitstream into the FPGA and uses a ton of other scripts and C programs to train the LVDS channels and set up the HDMI output

When the service is disabled, the user can run this script manually, which:

  • Of course, does not keep the user from running it even if it has already been activated by systemd
  • And on the other hand, simple scripts which query the registers (e.g. to get the temperature of the sensor) can be actived even if the FPGA bitstream was not loaded

All of those lead to a solid lockup of the Beta, because if you write to one of those memory addresses which are used for communicating with the PL, and there is no handler in the FPGA, the ARM cores lock up solid, no recovery possible they basically wait for an ACK/NACK forever.

Research is taking place in the Labs here.

1.1 Structure

TODO: Add image which shows structure of module communication (WebGUI -> RESTServer > Daemon, and back)

The control daemon project currently consists of three different modules:

  • Web UI - HTML5, sends REST requests to the backend, currently by using JQuery (still evaluating alternatives)
  • RESTServer - receives REST requests, converts them to Flatbuffers packages and sends them to the daemon, through socket
  • Daemon - processes received packages and calls suitable handler


1.2 Unit tests

Unit tests have been added to the project to verify correct functionality. Catch2 framework is used because it's single-header only and utilizes the C++11 way of doing things.

Note: (for development on PC) - RAM access of the camera is different from x86/x64 CPUs, modified classes have to be used to bypass this, otherwise SEGFAULT would be the result.

In the CMake scripts a switch called ENABLE_MOCK was added so that users can disable any code which won't work on a regular PC (see CMV12000AdapterTests.cpp for an example). While running the build on camera cmake .. is sufficient, but for development one should use:

$ cmake -DENABLE_MOCK=ON ..