User Tools

Site Tools


Deploy to cb20 Board

The file contains entries for the destination of deploying. Set these entries to      // use appropriate ip number or name
target_username=ost                 // use appropriate user name

Now, make sure that the directory /opt/eeros/ exists on the target. If not, ssh into the board, mount the read-only file system as read-write, create the directory, and set its ownership to user toradex with

$ sudo mount / -o remount,rw
$ sudo mkdir /opt/eeros
$ sudo chown ost:ost /opt/eeros/

Next, edit deploy.txt in your project directory and enter all the programs and libraries you have to transfer.




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 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 with EEROS the file would look like



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

Finally, load them onto the target with

$ ./


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.

The system must find the eeros and hardware wrapper libraries to dynamically load them. The following symbolic links must be created once.

ntb@cb20:$ cd /usr/lib/
ntb@cb20:$ sudo ln -s /opt/eeros/lib/
ntb@cb20:$ sudo ln -s /opt/eeros/lib/
ntb@cb20:$ sudo ln -s
ntb@cb20:$ sudo ln -s /opt/eeros/lib/
ntb@cb20:$ sudo ln -s

IMPORTANT Make sure the version information (….so. is not outdated! If you use newer versions of the libraries as given in deploy.txt you must adapt the links accordingly.

getting_started/deploy/deploy_cb20.txt · Last modified: 2021/02/12 17:13 by ursgraf