delta:setup
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
delta:setup [2018/08/07 14:43] – fink | delta:setup [2018/08/19 19:05] – [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 | + | $ cd robotics_cape_installer |
</ | </ | ||
and checkout version 0.3.4. | and checkout version 0.3.4. | ||
Line 44: | Line 44: | ||
$ sudo apt-get install g++-4.9-arm-linux-gnueabihf && sudo apt-get install cmake | $ sudo apt-get install g++-4.9-arm-linux-gnueabihf && sudo apt-get install cmake | ||
</ | </ | ||
- | Now you can build the robotics cape library with | + | Build the robotics cape library with |
< | < | ||
$ make | $ make | ||
Line 106: | 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. | ||
Line 117: | Line 117: | ||
==== 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 142: | Line 142: | ||
- 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). | - 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. | - Click finish. | ||
- | - Create the build configuration. It is recommended to put the target architecture in the name of the build folder. Put the location | + | - 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 " |
{{ : | {{ : | ||
Line 153: | Line 153: | ||
$ ./deploy.sh | $ ./deploy.sh | ||
</ | </ | ||
- | Else you have to change the project name in the deploy.txt file | + | otherwise |
< | < | ||
install-armhf/ | install-armhf/ |