getting_started:deploy:deploy_cb20
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
getting_started:deploy:deploy_cb20 [2021/02/12 17:13] – ursgraf | getting_started:deploy:deploy_cb20 [2023/04/13 11:21] (current) – [Deploying] ursgraf | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Deploy to cb20 Board ====== | ====== Deploy to cb20 Board ====== | ||
- | The file '' | + | Back to [[getting_started: |
- | < | + | |
- | target_IP_address=es140.ntb.ch | + | ===== Preparations ===== |
- | target_username=ost | + | |
- | target_application_folder=/ | + | Fetch the [[https:// |
+ | $ git clone https://github.com/eeros-project/eeros-build-scripts.git | ||
+ | $ cd eeros-build-scripts | ||
+ | $ git checkout sdk_cb20 | ||
</ | </ | ||
- | 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 | + | |
+ | The file '' | ||
< | < | ||
- | $ sudo mount / -o remount, | + | target_IP_address=146.136.100.8 |
- | $ sudo mkdir /opt/eeros | + | target_username=ost |
- | $ sudo chown ost:ost /opt/eeros/ | + | target_application_folder=/home/ost/ |
- | </ | + | </ |
- | Next, edit '' | + | |
- | < | + | |
- | install-armhf/ | + | |
- | install-armhf/ | + | |
- | install-armhf/ | + | |
- | build-armhf/ | + | ===== Deploying ===== |
- | build-armhf/ | + | |
- | build-armhf/flinklib/ | + | Next, edit '' |
- | build-armhf/ | + | < |
- | build-armhf/ | + | ../ |
+ | ../simple-motor-control/ | ||
</ | </ | ||
- | The flink utilities are only used for testing the experimental setup as given in [[getting_started: | + | If you wrote your own [[getting_started: |
- | If you did not include the application [[https:// | + | |
< | < | ||
- | install-armhf/lib/libeeros.so.1.2.0.0 | + | ../hello/ |
- | + | ||
- | build-armhf/ | + | |
</ | </ | ||
- | Obviously, this application does not make use of a hardware configuration file. | ||
Finally, load them onto the target with | Finally, load them onto the target with | ||
Line 39: | Line 34: | ||
</ | </ | ||
- | ===== CANopen | + | ===== Running your Application===== |
- | If you have configured you EEROS project with CANopen, | + | ssh into the board with < |
+ | $ ssh ost@es140.ntb.ch | ||
+ | </ | ||
+ | For credentials see [[https:// | ||
+ | Change into your target application folder and run the example < | ||
+ | $ cd bin | ||
+ | $ ./ | ||
+ | or | ||
+ | $ sudo ./ | ||
+ | </ | ||
- | ===== Set Library Links ===== | + | ===== Running your Application which is a ROS Node ===== |
- | The system must find the eeros and hardware wrapper libraries to dynamically load them. The following symbolic links must be created once. | + | |
- | < | + | Be sure to setup your network settings according to [[getting_started: |
- | ntb@cb20:$ cd /usr/lib/ | + | export ROS_MASTER_URI=http://192.168.7.3:11311 |
- | ntb@cb20:$ sudo ln -s / | + | |
- | ntb@cb20:$ sudo ln -s / | + | |
- | ntb@cb20:$ sudo ln -s libflinkeeros.so.1.0.0.0 libflinkeeros.so | + | |
- | ntb@cb20:$ sudo ln -s / | + | |
- | ntb@cb20:$ sudo ln -s libeeros.so.1.2.0.0 libeeros.so | + | |
</ | </ | ||
- | IMPORTANT Make sure the version information | + | Add the following line to your ''/ |
+ | 192.168.7.2 | ||
+ | </ | ||
+ | |||
+ | Run your application with < | ||
+ | $ sudo -E ./ | ||
+ | </ | ||
+ | |||
+ | ===== Running the Built-in Examples | ||
+ | |||
+ | Running | ||
+ | $ sudo / | ||
+ | </ | ||
+ | |||
+ | |||
+ | ===== flink ===== | ||
+ | |||
+ | The flink utilities can be used for testing the experimental setup as given in [[getting_started: | ||
+ | |||
+ | ===== CANopen ===== | ||
+ | Make sure to fetch the CANopen library, see [[https:// | ||
getting_started/deploy/deploy_cb20.1613146397.txt.gz · Last modified: 2021/02/12 17:13 by ursgraf