Differences

This shows you the differences between two versions of the page.

--- build [2019/11/13 12:31] – [Compile] graf
+++ build [2019/11/15 16:39] – [Notes] graf
@@ Line 10: / Line 10: @@
 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://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]].
-==== Start your Beagle Bone Blue ====
-  * Connect the micro USB with the PC.
-  * It takes about 15 seconds until the Beagle Bone Blue is powered up and another 15 seconds until a network adapter is shown on your host pc. Open a Terminal and check if this network is already available. <code>$ ifconfig </code> If you work on the host in a virtual machine, you might need to select the device //BeagleBone.org// among your various USB devices.
-  * Connect via ssh to your Beagle Bone Blue <code>$ ssh debian@192.168.7.2</code> Default credentials are "debian:temppwd"
-==== Login ====
-The first time you do this you will get a security alert in the console - type "yes" and hit enter.
-Then enter the password "temppwd" and confirm with enter. Don't be alarmed if the console does not response while you type your password.
 ===== Getting the Sources with a Script =====
@@ Line 64: / Line 57: @@
 </code>
-===== Deploy =====
-Finally, load the executable onto the target (see notes below if you are doing this on a brand new board) with
-<code>
-$ ./deploy.sh
-</code>
-The default password on the BeagleBone Blue Board is "temppwd". Edit the ''deploy.txt'' file to define which files should be downloaded. \\
-==== Notes ====
-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 **deploy.sh** will copy the executable and libraries to **/opt/eeros**. Therefore, this folder must be present on the target or the copy fails. To create the folder, execute the following on the BeagleBone:
-<code>
-debian@beaglebone:$ sudo mkdir /opt/eeros
-debian@beaglebone:$ sudo chown debian:debian /opt/eeros/
-</code>
-Also, some links must be created. The system must find the eeros libraries to load them. The following symbolic links are needed:
-<code>
-debian@beaglebone:$ cd /usr/lib/
-debian@beaglebone:$ sudo ln -s /opt/eeros/lib/libbbblueeeros.so.1.1.0.0 libbbblueeeros.so.1.1.0.0
-debian@beaglebone:$ sudo ln -s libbbblueeeros.so.1.1.0.0 libbbblueeeros.so
-debian@beaglebone:$ sudo ln -s /opt/eeros/lib/libeeros.so.1.0.0.30 libeeros.so.1.0.0.30
-debian@beaglebone:$ sudo ln -s libeeros.so.1.0.0.30 libeeros.so
-</code>
-Make sure the version information (....so.1.0.0.0) is not outdated! This can be checked by browsing the **BeagleBoneBlue/install-armhf/lib/** folder on the development computer before copying the libraries to the target.
 ----
-**Next: [[test|]] **
+**Next: [[connect|]] **