Differences

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

--- getting_started:deploy:deploy_cb20 [2021/03/29 18:02] – [flink] ursgraf
+++ getting_started:deploy:deploy_cb20 [2023/04/13 11:21] (current) – [Deploying] ursgraf
@@ Line 3: / Line 3: @@
 ===== 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.
 <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_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.
 <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>
 If you wrote your own [[getting_started:write_app:use_on_cb20#Say Hello with EEROS|]] the file would look like
 <code>
-build-armhf/hello/helloworld
+../hello/build-armhf/helloworld
 </code>
@@ Line 66: / Line 72: @@
 ===== 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.