User Tools

Site Tools


getting_started:deploy:deploy_cb20

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
getting_started:deploy:deploy_cb20 [2021/03/29 17:40] ursgrafgetting_started:deploy:deploy_cb20 [2023/04/13 11:21] (current) – [Deploying] ursgraf
Line 3: Line 3:
  
 ===== Preparations ===== ===== Preparations =====
 +
 +Fetch the [[https://github.com/eeros-project/eeros-build-scripts.git|EEROS scripts]] in your project root directory on your host and checkout the branch for the cb20 board <code>
 +$ git clone https://github.com/eeros-project/eeros-build-scripts.git
 +$ cd eeros-build-scripts
 +$ git checkout sdk_cb20
 +</code>
  
 The file ''config.sh.in'' contains entries for the destination of deploying. The file ''config.sh.in'' contains entries for the destination of deploying.
 <code> <code>
-target_IP_address=es140.ntb.ch      // use appropriate ip number or name+target_IP_address=146.136.100.8      // use appropriate ip number or name
 target_username=ost       target_username=ost      
 target_application_folder=/home/ost/ target_application_folder=/home/ost/
Line 15: Line 21:
 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. 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.
 <code> <code>
-build-armhf/simple-motor-control/simpleMotorControl +../simple-motor-control/build-armhf/simpleMotorControl 
-build-armhf/simple-motor-control/HwConfigBBBlue.json+../simple-motor-control/build-armhf/HwConfigBBBlue.json
 </code> </code>
 If you wrote your own [[getting_started:write_app:use_on_cb20#Say Hello with EEROS|]] the file would look like If you wrote your own [[getting_started:write_app:use_on_cb20#Say Hello with EEROS|]] the file would look like
 <code> <code>
-build-armhf/hello/helloworld+../hello/build-armhf/helloworld
 </code> </code>
  
Line 28: Line 34:
 </code> </code>
  
 +===== Running your Application=====
 +ssh into the board with <code>
 +$ ssh ost@es140.ntb.ch
 +</code>
 +For credentials see [[https://wiki.bu.ost.ch/infoportal/software/linux/yocto/cb20#Accessing_the_cb20|cb20]]. 
  
-The flink utilities are only used for testing the experimental setup as given in [[getting_started:tutorials:oneaxis_cb20|]]\\ +Change into your target application folder and run the example <code> 
-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 [[getting_started:say_hello|]] the file would look like +$ cd bin 
-<code> +./helloworld 
-install-armhf/lib/libeeros.so.1.2.0.0+or 
 +$ sudo ./simpleMotorControl -c HwConfigBBBlue.json 
 +</code>
  
-build-armhf/helloworld+===== Running your Application which is a ROS Node ===== 
 + 
 +Be sure to setup your network settings according to [[getting_started:ros_run#network_setup|Network Setup]]. Set the environment variable ''ROS_MASTER_URI'' in your shell with <code> 
 +export ROS_MASTER_URI=http://192.168.7.3:11311 
 +</code> 
 +Add the following line to your ''/etc/hosts'' file (under Ubuntu) <code> 
 +192.168.7.2  cb20
 </code> </code>
-Obviously, this application does not make use of a hardware configuration file. 
  
-Finally, load them onto the target with +Run your application with <code> 
-<code> +sudo -E ./application
-$ ./deploy.sh+
 </code> </code>
  
-===== CANopen ===== +===== Running the Built-in Examples of EEROS =====
-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.+
  
 +Running the built-in examples of EEROS as given in the tutorial pages in [[getting_started:tutorials:start|]] is quite simple, e.g. <code>
 +$ sudo /usr/examples/rtTest/rtTest
 +</code>
  
-===== Set Library Links ===== 
-The system must find the eeros and hardware wrapper libraries to dynamically load them. The following symbolic links must be created once. 
  
-<code> +===== flink ===== 
-ntb@cb20:$ cd /usr/lib/ + 
-ntb@cb20:$ sudo ln -s /opt/eeros/lib/libflink.so libflink.so +The flink utilities can be used for testing the experimental setup as given in [[getting_started:tutorials:oneaxis_cb20|]]. \\ 
-ntb@cb20:$ sudo ln -s /opt/eeros/lib/libflinkeeros.so.1.0.0.0 libflinkeeros.so.1.0.0.0 + 
-ntb@cb20:$ sudo ln -s libflinkeeros.so.1.0.0.0 libflinkeeros.so +===== CANopen ===== 
-ntb@cb20:$ sudo ln -s /opt/eeros/lib/libeeros.so.1.2.0.0 libeeros.so.1.2.0.0 +Make sure to fetch the CANopen library, see [[https://github.com/eeros-project/eeros-build-scripts]]The library has to be compiled and linked statically to your applicationThere is no need to transfer is to the target separately. 
-ntb@cb20:$ sudo ln -s libeeros.so.1.2.0.0 libeeros.so +
-</code> +
-IMPORTANT Make sure the version information (....so.1.2.0.0) 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.1617032405.txt.gz · Last modified: 2021/03/29 17:40 by ursgraf