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 revisionNext revisionBoth sides next revision | ||
| getting_started:install_and_setup_development_environment:use_with_cb20 [2019/10/11 15:52] – graf | getting_started:install_and_setup_development_environment:use_with_cb20 [2021/02/26 11:39] – 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. | + | |
| - | If a Linux host is used in a virtual machine, a [[https:// | + | |
| + | - Get an suitable image for your target platform from [[https:// | ||
| + | - 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 '' | ||
| < | < | ||
| use_simulator=false | use_simulator=false | ||
| - | use_flink=false | + | use_flink=true |
| - | use_bbblue=true | + | use_bbblue=false |
| 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 library | + | The entry '' |
| - | At the time of writing, the BeagleBone Blue Boards are shipped with an image that has the robotics cape library version 0.3.4 installed. Therefore, it is highly recommended to use this version. The bbblue-eeros wrapper library was implemented to work with the robotics cape library v0.3.4. Newer version were not tested yet. The right version is checked out by the clone script. | + | * downloading |
| + | * installing | ||
| - | To compile | + | Edit the file '' |
| < | < | ||
| - | $ cd robotics_cape_installer/libraries | + | environment_setup_script=/opt/ |
| </ | </ | ||
| - | and edit the '' | + | This will guide your make script to use the SDK. Make sure that the above path matches your installation path. |
| - | < | + | |
| - | CC := gcc | + | |
| - | LINKER := gcc | + | |
| - | </ | + | |
| - | to | + | |
| - | < | + | |
| - | CC := arm-linux-gnueabihf-gcc-4.9 | + | |
| - | LINKER := arm-linux-gnueabihf-gcc-4.9 | + | |
| - | </ | + | |
| - | This change is necessary because the library must be compiled with the cross compiler. | + | |
| - | Now, the cross tool chain is installed on the host machine with the following command. | + | If you want to use CAN, choose |
| - | < | + | |
| - | $ sudo apt-get install g++-4.9-arm-linux-gnueabihf | + | |
| - | </ | + | |
| - | Then, the roboticscape library is compiled using make. | + | |
| < | < | ||
| - | $ make | + | use_can=true |
| </ | </ | ||
| - | Change back into your project directory and start the compilation of EEROS, the hardware wrapper library, and the demo application | + | Setting |
| + | Now you can run the '' | ||
| < | < | ||
| - | $ ./make.sh | + | $ ./clone.sh |
| </ | </ | ||
| - | Finally, load the executable onto the target (see notes below if you are doing this on a brand new board) with | + | After this you can continue with [[getting_started: |
| + | |||
| + | |||
| + | ==== Test Application ==== | ||
| + | |||
| + | There is a test application for the cb20 board in [[https:// | ||
| < | < | ||
| - | $ ./deploy.sh | + | use_custom_application=true |
| - | </ | + | custom_application_name=cb20test |
| - | The default password on the BeagleBone Blue Board is " | + | </ |
| - | Use ssh to get on the target | + | and further down |
| - | Start the demo application with | + | |
| < | < | ||
| - | $ sudo ./demo -c HwConfigBBBlue.json | + | custom_application_git_remote_address=https:// |
| - | </ | + | custom_application_git_version=master |
| - | Now, everything is ready. The development can be started in the **BeagleBoneBlue/demoApp/** folder. | + | custom_application_source_dir=" |
| + | custom_application_build_dir=" | ||
| + | </ | ||
| - | ==== Notes ==== | + | Now you can run the '' |
| - | 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 | + | |
| < | < | ||
| - | debian@beaglebone: | + | $ ./clone.sh |
| - | debian@beaglebone: | + | |
| </ | </ | ||
| - | Also, some links must be created. The system must find the eeros libraries to dynamically load them. The following symbolic links are needed: | + | After this you can continue with [[getting_started:compile_eeros|]]. |
| - | < | + | |
| - | debian@beaglebone: | + | |
| - | 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/ | + | |