delta:setup
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
delta:setup [2018/08/05 14:57] – fink | delta:setup [2018/08/19 19:04] – [EEROS for Beagle Bone Blue] fink | ||
---|---|---|---|
Line 3: | Line 3: | ||
How to setup the wifi, copy your image to the onboard eMMC or any other FAQs can be found [[https:// | How to setup the wifi, copy your image to the onboard eMMC or any other FAQs can be found [[https:// | ||
- | ======= EEROS on Beagle Bone Blue ======= | + | ===== EEROS for Beagle Bone Blue ===== |
There are already existing wrapper libraries to use EEROS with your Beagle Bone Blue. Switch to your current working directory | There are already existing wrapper libraries to use EEROS with your Beagle Bone Blue. Switch to your current working directory | ||
< | < | ||
Line 14: | Line 14: | ||
Get into that cloned folder and run the shell script | Get into that cloned folder and run the shell script | ||
< | < | ||
- | $cd BeagleBoneBlue | + | $ cd BeagleBoneBlue |
$ ./clone.sh | $ ./clone.sh | ||
</ | </ | ||
Line 20: | Line 20: | ||
First you have to build a running version of the Robotics Cape library for your target device. To do that, switch to the robitics_cape folder | First you have to build a running version of the Robotics Cape library for your target device. To do that, switch to the robitics_cape folder | ||
< | < | ||
- | $cd robotics_cape_installer/libraries | + | $cd robotics_cape_installer |
</ | </ | ||
- | and edit its Makefile. | + | and checkout version 0.3.4. |
< | < | ||
+ | $ git checkout v0.3.4 | ||
+ | </ | ||
+ | Afterwards go into the libraries folder and edit its Makefile. | ||
+ | < | ||
+ | $ cd libraries | ||
$ nano Makefile | $ nano Makefile | ||
</ | </ | ||
Line 37: | Line 42: | ||
This is necassary because we work on the host and must make sure to choose the right cross compiler for our target. If you do not have this compiler on your host, you can get it with | This is necassary because we work on the host and must make sure to choose the right cross compiler for our target. If you do not have this compiler on your host, you can get it with | ||
< | < | ||
- | $ sudo apt-get install g++-4.9-arm-linux-gnueabihf | + | $ sudo apt-get install g++-4.9-arm-linux-gnueabihf |
</ | </ | ||
- | At time of writing | + | Build the robotics |
< | < | ||
- | $ git checkout v0.3.4 | + | $ make |
</ | </ | ||
- | Now you can build the robotics cape library with | + | Now you have to change 2 files.First go to your BeagleBoneBlue/ |
< | < | ||
- | $ make | + | link_directories(" |
+ | </ | ||
+ | and change this absolute path to match your path. | ||
+ | < | ||
+ | link_directories("/ | ||
+ | </ | ||
+ | Second, the current main.cpp is not working. Copy and paste the "Hello EEROS" tutorial into your main.cpp. | ||
+ | <code c> | ||
+ | #include < | ||
+ | #include < | ||
+ | #include < | ||
+ | |||
+ | int main() { | ||
+ | using namespace eeros:: | ||
+ | |||
+ | StreamLogWriter w(std:: | ||
+ | Logger log; | ||
+ | log.set(w); | ||
+ | |||
+ | log.info() << " | ||
+ | |||
+ | return 0; | ||
+ | } | ||
</ | </ | ||
Change back to your BeagleBoneBlue git repository and run the make shellscript | Change back to your BeagleBoneBlue git repository and run the make shellscript | ||
Line 61: | Line 88: | ||
$ mkdir / | $ mkdir / | ||
</ | </ | ||
- | | + | Back on the host copy or deploy the necassary files to your target run |
< | < | ||
$ ./deploy.sh | $ ./deploy.sh | ||
</ | </ | ||
- | Run the myApp application | + | On the target run the myApp application |
< | < | ||
$ cd / | $ cd / | ||
Line 72: | Line 99: | ||
If the libraries have not been copied to the target, copy them by hand to the right place | If the libraries have not been copied to the target, copy them by hand to the right place | ||
< | < | ||
- | $ scp ./build-armhf/ | + | $ scp ./install-armhf/lib/ |
- | $ scp ./build-armhf/ | + | $ scp ./install-armhf/lib/ |
$ scp ./ | $ scp ./ | ||
$ scp ./ | $ scp ./ | ||
Line 79: | Line 106: | ||
On your target link both libraries to /usr/lib | On your target link both libraries to /usr/lib | ||
< | < | ||
- | $ sudo ln -s /opt/eeros/bin/ | + | $ sudo ln -s /opt/eeros/lib/ |
- | $ sudo ln -s /opt/eeros/bin/ | + | $ sudo ln -s /opt/eeros/lib/ |
- | $ sudo ln -s /opt/eeros/bin/ | + | $ sudo ln -s /opt/eeros/lib/ |
- | $ sudo ln -s /opt/eeros/bin/ | + | $ sudo ln -s /opt/eeros/lib/ |
</ | </ | ||
Now you should be able to run the myApp application. | Now you should be able to run the myApp application. | ||
- | ======= Linux on Beagle Bone Blue ======= | + | ===== Linux on Beagle Bone Blue ===== |
The Beagle Bone Blue comes with a preinstalled Debian 8 with Kernel 4.4.54-ti-r93 or similar. Do not upgrade to Debian 9 cause robitics cape will not work anymore. Also do not use any newer Kernel, this will cause the same problem. The latest Debian Images for your Beagle Bone Blue can be downloaded [[https:// | The Beagle Bone Blue comes with a preinstalled Debian 8 with Kernel 4.4.54-ti-r93 or similar. Do not upgrade to Debian 9 cause robitics cape will not work anymore. Also do not use any newer Kernel, this will cause the same problem. The latest Debian Images for your Beagle Bone Blue can be downloaded [[https:// | ||
- | ===== RT Kernel for Beagle Bone Blue ===== | + | ==== RT Kernel for Beagle Bone Blue ==== |
You can also run the Beagle Bone Blue with a real-time Kernel. | You can also run the Beagle Bone Blue with a real-time Kernel. | ||
- | Check if there is already a RT-Kernel: | + | Check if there is already a RT-Kernel: |
< | < | ||
uname -r | uname -r | ||
Line 103: | Line 130: | ||
sudo apt remove --purge linux-image-4.4.54-ti-r93 | sudo apt remove --purge linux-image-4.4.54-ti-r93 | ||
</ | </ | ||
+ | |||
+ | ===== Get your IDE ===== | ||
+ | It is highly recommended to use an IDE for your EEROS applications. You can use an IDE of your choice. The following steps explain how to setup an EEROS application with KDevelop. | ||
+ | < | ||
+ | $ sudo apt-get install kdevelop | ||
+ | </ | ||
+ | ==== Import an EEROS project ==== | ||
+ | - Start KDevelop | ||
+ | - Project -> Open/Import project | ||
+ | - Get to your working directory and choose the folder " | ||
+ | - You can use myApp as name, or any other, as you prefer. If you change this name, you also have to make changes to the deploy file (later on). | ||
+ | - Click finish. | ||
+ | - Create the build configuration. It is recommended to put the target architecture in the name of the build folder. Put the path where EEROS is install in the " | ||
+ | {{ : | ||
+ | |||
+ | You now have your main.cpp, HwConfigBBBlue.json and the CMakeLists.txt in your project solution. You can build this application by pressing the build-button in the top left corner. To run this application on your target device, get to your working directory | ||
+ | < | ||
+ | $ cd / | ||
+ | </ | ||
+ | If your project name is still myApp you can run the | ||
+ | < | ||
+ | $ ./deploy.sh | ||
+ | </ | ||
+ | otherwise you have to change the project name in the deploy.txt file | ||
+ | < | ||
+ | install-armhf/ | ||
+ | install-armhf/ | ||
+ | |||
+ | myApp/ | ||
+ | build-armhf/ | ||
+ | </ | ||
+ | and run the deploy.sh afterwards. |