getting_started:install_and_setup_development_environment:use_with_cb20
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
getting_started:install_and_setup_development_environment:use_with_cb20 [2019/10/11 15:53] – graf | 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 ====== | ====== Use on a cb20 Board ====== | ||
- | The following is a step-by-step procedure to get started using EEROS on the [[https:// | + | The following is a step-by-step procedure to get started using EEROS on the [[https:// |
- | As cross tool chain, the **arm-linux-gnueabihf-gcc-4.9** is needed. It is recommended to use a Ubuntu 16.04 as host operating system, since this packet is available in the default repositories. | + | Get an suitable image for your target platform from [[https://wiki.bu.ost.ch/infoportal/software/ |
- | If a Linux host is used in a virtual machine, a [[https://lubuntu.net/downloads/|lightweight Ubuntu distribution]] is recommended. In case you are using a newer Ubuntu version, you have to add //xenial// to your sources list, see [[https://askubuntu.com/questions/1036108/install-gcc-4-9-at-ubuntu-18-04]]. | + | |
+ | Get the associated SDK from [[https:// | ||
+ | |||
+ | Unpack it on your host system with < | ||
+ | |||
+ | Change into the sdk directory and execute the script therein with < | ||
+ | $ ./ | ||
Fetch the [[https:// | Fetch the [[https:// | ||
< | < | ||
- | $ git clone https:// | + | $ git clone https:// |
- | $ cd eeros-project | + | $ cd cb20 |
</ | </ | ||
Edit the file '' | Edit the file '' | ||
Line 17: | Line 22: | ||
use_comedi=false | use_comedi=false | ||
use_ros=false | use_ros=false | ||
+ | use_can=false | ||
use_custom_application=true | use_custom_application=true | ||
- | </ | + | use_cross_compilation_environment=true |
- | Now you can run the '' | + | use_ros_setup_script=false |
- | < | + | |
- | $ ./clone.sh | + | |
</ | </ | ||
+ | The entry '' | ||
+ | * downloading the SDK from [[https:// | ||
+ | * installing the SDK as described in [[https:// | ||
- | + | Edit the file '' | |
- | Change back into your project directory and start the compilation of EEROS, the hardware wrapper library, and the demo application with | + | |
< | < | ||
- | $ ./make.sh | + | environment_setup_script=/opt/ |
</ | </ | ||
+ | This will guide your make script to use the SDK. Make sure that the above path matches your installation path. | ||
- | Finally, load the executable onto the target (see notes below if you are doing this on a brand new board) with | + | If you want to use CAN, choose |
< | < | ||
- | $ ./deploy.sh | + | use_can=true |
</ | </ | ||
- | The default password on the BeagleBone Blue Board is " | + | |
- | Use ssh to get on the target and change into '' | + | Setting |
- | Start the demo application with | + | Now you can run the '' |
< | < | ||
- | $ sudo ./demo -c HwConfigBBBlue.json | + | $ ./clone.sh |
</ | </ | ||
- | Now, everything is ready. The development | + | After this you can continue with [[getting_started: |
+ | |||
+ | |||
+ | ==== Test Application ==== | ||
- | ==== Notes ==== | + | There is a test application for the cb20 board in [[https://github.com/ |
- | When the BeagleBone Blue Board is used the first time (never used with EEROS before or a brand new BeagleBone Blue / Image), some initial setup steps are needed. The script **deploy.sh** will copy the executable and libraries to **/opt/eeros**. Therefore, | + | |
< | < | ||
- | debian@beaglebone: | + | use_custom_application=true |
- | debian@beaglebone: | + | custom_application_name=cb20test |
- | </code> | + | </code> |
+ | and further down | ||
+ | < | ||
+ | custom_application_git_remote_address=https://github.com/ntb-ch/cb20.git | ||
+ | custom_application_git_version=master | ||
- | Also, some links must be created. The system must find the eeros libraries to dynamically load them. The following symbolic links are needed: | + | custom_application_source_dir=" |
+ | custom_application_build_dir=" | ||
+ | </ | ||
+ | |||
+ | Now you can run the '' | ||
< | < | ||
- | debian@beaglebone: | + | $ ./clone.sh |
- | debian@beaglebone: | + | |
- | debian@beaglebone: | + | |
- | debian@beaglebone: | + | |
- | debian@beaglebone: | + | |
</ | </ | ||
- | Make sure the version information (....so.1.0.0.0) is not outdated! This can be checked by browsing the **BeagleBoneBlue/ | + | |
+ | After this you can continue with [[getting_started: |