Back to Writing EEROS Applications for cb20 Board.

The file config.sh.in contains entries for the destination of deploying.

target_IP_address=es140.ntb.ch      // use appropriate ip number or name
target_username=ost      
target_application_folder=/home/ost/

Next, edit deploy.txt on the host in your project directory and enter the application program you want to transfer together with the necessary hardware configuration file, e.g.

build-armhf/simple-motor-control/simpleMotorControl
build-armhf/simple-motor-control/HwConfigBBBlue.json

If you wrote your own Say Hello with EEROS the file would look like

build-armhf/hello/helloworld

Finally, load them onto the target with

$ ./deploy.sh

ssh into the board with

$ ssh ost@es140.ntb.ch

For credentials see cb20.

Change into your target application folder and run the example

$ cd bin
$ ./helloworld
or
$ sudo ./simpleMotorControl -c HwConfigBBBlue.json

Be sure to setup your network settings according to Network Setup. Set the environment variable ROS_MASTER_URI in your shell with

export ROS_MASTER_URI=http://192.168.7.3:11311

Add the following line to your /etc/hosts file (under Ubuntu)

192.168.7.2  cb20

Run your application with

$ sudo -E ./application

Running the built-in examples of EEROS as given in the tutorial pages in Tutorials is quite simple, e.g.

$ sudo /usr/examples/rtTest/rtTest

The flink utilities are only used for testing the experimental setup as given in Experimental Setup with a cb20 Board.
If you did not include the application https://github.com/eeros-project/simple-motor-control.git you have to alter the middle two lines and set the entries according to your needs. E.g. if you wrote your own say_hello the file would look like

install-armhf/lib/libeeros.so.1.2.0.0

build-armhf/helloworld

Obviously, this application does not make use of a hardware configuration file.

Finally, load them onto the target with

$ ./deploy.sh

If you have configured you EEROS project with CANopen, the library will have been fetched and compiled automatically. It will have been statically linked to your appplication and there is no need to transfer is to the target.