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/03/29 17:40] – ursgraf | getting_started:deploy:deploy_cb20 [2023/04/13 11:21] (current) – [Deploying] ursgraf | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== Preparations ===== | ===== Preparations ===== | ||
+ | |||
+ | Fetch the [[https:// | ||
+ | $ git clone https:// | ||
+ | $ cd eeros-build-scripts | ||
+ | $ git checkout sdk_cb20 | ||
+ | </ | ||
The file '' | The file '' | ||
< | < | ||
- | 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=/ | target_application_folder=/ | ||
Line 15: | Line 21: | ||
Next, edit '' | Next, edit '' | ||
< | < | ||
- | build-armhf/ | + | ../ |
- | build-armhf/ | + | ../ |
</ | </ | ||
If you wrote your own [[getting_started: | If you wrote your own [[getting_started: | ||
< | < | ||
- | build-armhf/hello/helloworld | + | ../hello/build-armhf/ |
</ | </ | ||
Line 28: | Line 34: | ||
</ | </ | ||
+ | ===== Running your Application===== | ||
+ | ssh into the board with < | ||
+ | $ ssh ost@es140.ntb.ch | ||
+ | </ | ||
+ | For credentials see [[https:// | ||
- | The flink utilities are only used for testing | + | Change into your target application folder and run the example < |
- | If you did not include the application [[https:// | + | $ cd bin |
- | < | + | $ ./helloworld |
- | install-armhf/ | + | or |
+ | $ sudo ./simpleMotorControl | ||
+ | </code> | ||
- | build-armhf/helloworld | + | ===== Running your Application which is a ROS Node ===== |
+ | |||
+ | Be sure to setup your network settings according to [[getting_started: | ||
+ | export ROS_MASTER_URI=http: | ||
+ | </ | ||
+ | Add the following line to your ''/ | ||
+ | 192.168.7.2 | ||
</ | </ | ||
- | Obviously, this application does not make use of a hardware configuration file. | ||
- | Finally, load them onto the target | + | Run your application |
- | < | + | $ sudo -E ./application |
- | $ ./deploy.sh | + | |
</ | </ | ||
- | ===== 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: | ||
+ | $ sudo / | ||
+ | </ | ||
- | ===== 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. | ||
- | < | + | ===== flink ===== |
- | ntb@cb20:$ cd /usr/lib/ | + | |
- | ntb@cb20:$ sudo ln -s /opt/eeros/ | + | The flink utilities can be used for testing the experimental setup as given in [[getting_started:tutorials: |
- | ntb@cb20:$ sudo ln -s /opt/eeros/ | + | |
- | ntb@cb20:$ sudo ln -s libflinkeeros.so.1.0.0.0 libflinkeeros.so | + | ===== CANopen ===== |
- | ntb@cb20:$ sudo ln -s /opt/eeros/ | + | 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. |
- | ntb@cb20:$ sudo ln -s libeeros.so.1.2.0.0 libeeros.so | + | |
- | </ | + | |
- | 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 '' | + | |
getting_started/deploy/deploy_cb20.1617032405.txt.gz · Last modified: 2021/03/29 17:40 by ursgraf