config.sh.in contains entries for the destination of deploying. Set these entries to
target_IP_address=192.168.7.2 target_username=ost target_application_folder=/opt/eeros/
Now, make sure that the directory /opt/eeros/ exists on the target. If not, ssh into the board. For credentials see Beaglebone Blue. Then, create the directory and set its ownership to user ost with
ost@bblue:$ sudo mkdir /opt/eeros ost@bblue:$ sudo chown ost:ost /opt/eeros/
deploy.txt in your project directory and enter all the programs and libraries you have to transfer.
install-armhf/lib/libeeros.so.18.104.22.168 install-armhf/lib/libbbblueeeros.so.22.214.171.124 build-armhf/simple-motor-control/HwConfigBBBlue.json build-armhf/simple-motor-control/simpleMotorControl
If you did not include the application https://github.com/eeros-project/simple-motor-control.git you have to alter the last two lines and set the entries according to your needs. E.g. if you wrote your own Say Hello with EEROS the file would look like
install-armhf/lib/libeeros.so.126.96.36.199 install-armhf/lib/libbbblueeeros.so.188.8.131.52 build-armhf/helloworld
Obviously, this application does not make use of a hardware configuration file.
Finally, load them onto the target with
The system must find the eeros and hardware wrapper libraries to dynamically load them. The following symbolic links must be created once.
debian@beaglebone:$ cd /usr/lib/ debian@beaglebone:$ sudo ln -s /opt/eeros/lib/libbbblueeeros.so.184.108.40.206 libbbblueeeros.so.220.127.116.11 debian@beaglebone:$ sudo ln -s libbbblueeeros.so.18.104.22.168 libbbblueeeros.so debian@beaglebone:$ sudo ln -s /opt/eeros/lib/libeeros.so.22.214.171.124 libeeros.so.126.96.36.199 debian@beaglebone:$ sudo ln -s libeeros.so.188.8.131.52 libeeros.so
Make sure the version information (….so.184.108.40.206) is not outdated! If you use newer versions of the libraries as given in
deploy.txt you must adapt the links accordingly.