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/12 17:11] – [Use on a cb20 Board] ursgraf | ||
---|---|---|---|
Line 2: | Line 2: | ||
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, | + | On the host, you have to install |
- | 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]]. | + | |
Fetch the [[https:// | Fetch the [[https:// | ||
Line 10: | Line 9: | ||
$ cd eeros-project | $ cd eeros-project | ||
</ | </ | ||
- | Edit the file '' | + | If you want to use flink, 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 | ||
</ | </ | ||
- | Now you can run the '' | + | If you do a cross development and your target contains a different processor architecture from your host, you have to choose a suitable SDK. |
< | < | ||
- | $ ./clone.sh | + | toolchain_file=" |
</ | </ | ||
+ | You can omit the toolchain file if you use our [[https:// | ||
- | The library for the roboticscape must be compiled manually. Though the library is already on the target, we must also have it on the host, in order to be able to link an application. | + | If you want to use CAN, choose |
- | 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 compile the library, change into: | + | |
< | < | ||
- | $ cd robotics_cape_installer/ | + | use_can=true |
</ | </ | ||
- | and edit the '' | + | Setting |
+ | Now you can run the '' | ||
< | < | ||
- | CC := gcc | + | $ ./clone.sh |
- | 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 | + | After this you can continue |
- | < | + | |
- | $ sudo apt-get install g++-4.9-arm-linux-gnueabihf | + | |
- | </ | + | |
- | Then, the roboticscape library is compiled using make. | + | |
- | < | + | |
- | $ make | + | |
- | </ | + | |
- | Change back into your project directory and start the compilation of EEROS, the hardware wrapper library, and the demo application with | ||
- | < | ||
- | $ ./make.sh | ||
- | </ | ||
- | Finally, load the executable onto the target (see notes below if you are doing this on a brand new board) with | + | ==== 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/ | + |