Real-Time Robotics Framework

User Tools

Site Tools

You are here: EEROS Wiki » Get Started Using EEROS » Deploying » Deploy to cb20 Board
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:58] – [Running your Application which is a ROS Node] 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 47: Line 53:
 </code> </code>
 Add the following line to your ''/etc/hosts'' file (under Ubuntu) <code> Add the following line to your ''/etc/hosts'' file (under Ubuntu) <code>
-192.168.7.2  bblue+192.168.7.2  cb20
 </code> </code>
  
Line 54: Line 60:
 </code> </code>
  
 +===== Running the Built-in Examples of EEROS =====
  
 +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>
  
  
 +===== flink =====
  
-The flink utilities are only used for testing the experimental setup as given in [[getting_started:tutorials:oneaxis_cb20|]]. \\ +The flink utilities can be used for testing the experimental setup as given in [[getting_started:tutorials:oneaxis_cb20|]]. \\
-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 +
-<code> +
-install-armhf/lib/libeeros.so.1.2.0.0 +
- +
-build-armhf/helloworld +
-</code> +
-Obviously, this application does not make use of a hardware configuration file. +
- +
-Finally, load them onto the target with +
-<code> +
-$ ./deploy.sh +
-</code>+
  
 ===== CANopen ===== ===== CANopen =====
-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.+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 application. There is no need to transfer is to the target separately.
  
  
  
getting_started/deploy/deploy_cb20.1617033539.txt.gz · Last modified: 2021/03/29 17:58 by ursgraf