Differences

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

--- getting_started:install_and_setup_development_environment:use_with_cb20 [2021/02/12 17:46] – ursgraf
+++ getting_started:install_and_setup_development_environment:use_with_cb20 [2021/02/26 11:42] – ursgraf
@@ Line 1: / Line 1: @@
 ====== Use on a cb20 Board ======
-The following is a step-by-step procedure to get started using EEROS on the [[https://wiki.ntb.ch/infoportal/embedded_systems/imx6/cb#cb20_board|cb20 Board]]. It describes how to set up the cross development tool chain. The application is developed on a Linux host machine and can then be deployed to the board.
+The following is a step-by-step procedure to get started using EEROS on the [[https://wiki.ntb.ch/infoportal/embedded_systems/imx6/cb#cb20_board|cb20 Board]]. It describes how to set up the SDK. The application is developed on a Linux host machine and can then be deployed to the board.
-On the host, you have to install the cross development SDK, see [[https://wiki.ntb.ch/infoportal/software/linux/toradex/start|Linux on Toradex Colibri i.MX6]]. Also make sure to have the newest image from our download section [[https://wiki.ntb.ch/infoportal/software/linux/images/start|Linux Images]] installed on the target.
+Get an suitable image for your target platform from [[https://wiki.bu.ost.ch/infoportal/software/linux/images/start|Linux Images]] and install it on your target system, see [[https://wiki.bu.ost.ch/infoportal/software/linux/toradex/toradex-easy-installer]].
+Get the associated SDK from [[https://wiki.bu.ost.ch/infoportal/software/linux/images/start|Linux Images]]
+Unpack it on your host system with <code>$ tar -vxJf ntb-dev-image-cb20-1.0_sdk.tar.xz</code>
+Change into the sdk directory and execute the script therein with <code>$ cd sdk
+$ ./tdx-xwayland-glibc-x86_64-ntb-ros-image-melodic-armv7at2hf-neon-cb20-toolchain-5.0.0.sh</code>
 Fetch the [[https://github.com/eeros-project/eeros-build-scripts.git|EEROS scripts]] on your cross development system with
 <code>
-$ git clone https://github.com/eeros-project/eeros-build-scripts.git eeros-project
+$ git clone https://github.com/eeros-project/eeros-build-scripts.git cb20
-$ cd eeros-project
+$ cd cb20
 </code>
 Edit the file ''config.sh.in'' as follows
@@ Line 21: / Line 27: @@
 use_ros_setup_script=false
 </code>
-If you do a cross development and your target contains a different processor architecture from your host, you have to choose a suitable SDK.
+The entry ''use_cross_compilation_environment'' ensures that you compile using an SDK built for the target platform. Make sure to install the SDK by
+  * downloading the SDK from [[https://wiki.bu.ost.ch/infoportal/software/linux/images/start|Linux Images]]
+  * installing the SDK as described in [[https://wiki.bu.ost.ch/infoportal/software/linux/toradex/toradex-sdk]]
+Edit the file ''config.sh.in'' as follows
 <code>
-toolchain_file="$wd"/toolchainfile/arm-linux-gnueabihf-gcc-4.9.cmake
+environment_setup_script=/opt/tdx-xwayland/5.0.0/environment-setup-armv7at2hf-neon-tdx-linux-gnueabi
 </code>
-You can omit the toolchain file if you use our [[https://wiki.ntb.ch/infoportal/embedded_systems/imx6/cb|cb20 board]] together with the associated [[https://wiki.ntb.ch/infoportal/software/linux/toradex/start|Cross Development SDK]]. \\
+This will guide your make script to use the SDK. Make sure that the above path matches your installation path.
 If you want to use CAN, choose
@@ Line 31: / Line 42: @@
 use_can=true
 </code>
-Setting the last entry to //true// will fetch an existing application from a git repository. Per default this will will be [[https://github.com/eeros-project/simple-motor-control.git]]. However, you could choose another repository in ''config.sh.in''. Or you could set the entry to //false// if you want to develop your own application. \\
+Setting the entry ''use_custom_application'' to //true// will fetch an existing application from a git repository. Per default this will will be [[https://github.com/eeros-project/simple-motor-control.git]]. However, you could choose another repository in ''config.sh.in''. Or you could set the entry to //false// if you want to develop your own application. \\
 Now you can run the ''clone'' script
 <code>