ARM for ubuntu

So, this was quite a bit more lengthy than I hoped. Nevertheless, I think this is worth sharing. I made all this with my old trusty net book and the BBB connected via HDMI to an external monitor (theoretically, you could create a script to set up everything for you, but I don't know how to do that... yet), and coupled with its own keyboard and mouse the first time, then I realized I could have used SSH from the very beginning (how dull of me) controlling the BBB with my computer. You will also need a fast micro sd card, 4 GB at the very least (and 32 GB at most, I strongly recommend at least 8 gb, class 10) to set up Ubuntu ARM. To install things, an internet connection is required. You could use an Ethernet cable, but personally I had access to a USB-Stick Wireless Network Adapter by CISCO/Linksys that worked right away.In short, make sure you have the following:If you are going to use SSH:4 GB (or more, I recommend 8gb class 10) SD card (and the sd card reader for the imaging in your PC with Ubuntu)Ethernet Cable (or Wifi USB adapter) and internet connectionPlenty of time and patience (time being the most important, I warn you)If you want graphical output from the BBB, to control it "directly", add:Micro HDMI cable (and the HDMI Monitor or TV, of course)USB Hub (connected to the BBB)Keyboard (in the hub)Mouse (If you wish to use the graphical environment right away. I used a wireless one without problem, connect it to the hub)So, lets begin with this. There is an alternative way to install ROS, using Angstrom, covered by Victor Mayoral Vilches (don't know him), on his blog: / . I have not tried it, but will do sometime.1.- Prepare the sd card for imagingModified from /BeagleBoardUbuntuUsing: "Method 1: Download a Complete Pre-Configured Image", download a premade image of Quantal 12.10 armhf. 12.10 being important, as it is the latest Ubuntu version supported by ROS.In my case, I extracted the files for ubuntu-12.10-console-armhf-2013-07-22. Be careful when imaging the card, you must be absolutely sure that the sdX you are using is the RIGHT one (or risk trashing your computer data). Position yourself via the terminal inside the folder of the extracted premade image and enter:sudo ./setup_sdcard.sh --probe-mmcThis showed me that my sd card was in sdb, then, I used:sudo ./setup_sdcard.sh --mmc /dev/sdb --uboot bone_dtbWhen finished, just put the SD card in the slot of the BBB, and power it on with the USB Cable and your PC. The default user is ubuntu and the pass is temppwd2.- Configure SSHIf for some reason you need special configuration, do:On the BBB, enter in the terminal or command line:sudo nano /etc/ssh/sshd_configAnd follow the instructions of the Configuration section of https:///12.04/serverguide/openssh-server.html but LEAVE the port as 22. Then do:sudo /etc/init.d/ssh restartIf you do not need special configuration, just do:On your PC, go to /Getting%20Started and look for mkudevrule.sh . Download it, make the file executable and run it with sudo. See /questions/77929/how-to-run-a-script if needed, and then reboot.Make sure you are connected to the network created by the BBB via the USB cable, in my case, it's named "Wired connection 2" and appears as an Ethernet Network (Circuitco BeagleBoneBlack). You could set up the network manually if needed, like in/2013/05/11/remote-desktop-connection-to -a-raspberry-pi/ but I found it unnecessary (also, don't follow the instructions in that link, it's for the RaspberryPi and Fedora).If succesful, you should be able to do:ping 192.168.7.1ping 192.168.7.2And get a response from the BBB. On your PC, update the /etc/hosts (sudo nano bla bla bla) file, adding the line:192.168.7.2 armto the list of known hosts. You should have the SSH server and client installed already, if in doubt, see https:///12.04/serverguide/openssh-server.html . Thus, you could now do:ping armOn your PC (you may need to reboot it again, I don't really remember), enter in a terminal:sudo ufw allow 22ssh ubuntu@armI'm not sure if the first line is really neccesary, seen in /questions/51925/how-do-i-configure-a-new-ubuntu-installatio n-to-accept-ssh-connections .Then enter the pass temppwd, and you will be connected via SSH to the BBB, via the USB cable. If worried about security, see https:///community/SSH/OpenSSH/Configuring .3.- Configure the wifi adapter (if not using ethernet)If you don't mind, you can connect to the BBB via SSH right away, and do everything on your computer, see step 1 if you need to configure the SSH connection from the BBB itself. I suggest using SSH so you don't have to bother with HDMI, keyboard, etc. You need to set up the hosts file on your computer so it includes the BBB ip and name key-value pair, and "install" the driver script from the BBB webpage.The BBB will ask you for a login, enter ubuntu (the user) and the the password temppwd. You are now at ubuntu@arm. In the section named "Ubuntu Software" at /BeagleBoardUbuntu there is an example of the interface configuration file (see /showthread.php?t=202834 for more detail). I used:sudo nano /etc/network/interfacesIn my case, I had a WPA-2 public ssid AES encrypted personal DHCP network, thus after the Wifi Example comments I entered:auto wlan0iface wlan0 inet dhcpwpa-driver wextwpa-ssid INFINITUM1234wpa-ap-scan 1wpa-proto RSNwpa-pairwise CCMPwpa-group CCMPwpa-key-mgmt WPA-PSKwpa-psk ...Again, see /showthread.php?t=202834 for more details. INFINITUM1234 being the name of my wireless network. To get the pass phrase, exit nano (saving changes) and enter in the terminal:wpa_passphrase your_essid your_ascii_keyLets say (as an example) that I used:wpa_passphrase INFINITUM1234 1234567890Write down (if not using SSH, sorry for that... but you could just use SSH, or Ethernet you know, or finish this later with a GUI) the long string of letters and numbers generated after psk, and update the wpa-psk line in /etc/network/interfaces with the string. Finally, reboot:sudo reboot4.- Configure the keyboard layout (if yours is not US standard and you are using the BBB "directly")I used a Spanish (Spain) keyboard. To configure it, follow the instructions at /questions/155424/changing-keyboard-layout-in-ubuntu-12-04-s erver-command-line-interfacesudo apt-get updatesudo apt-get install console-dataHit enter when showed "Configuring console-data", and then use:sudo dpkg-reconfigure keyboard-configurationSelect an appropriate keyboard and the desired language. Leave other optionsunchanged.5.- Start the Graphical Environment (if so you wish)Same user as ubuntu and pass as temppwd. Refer to /BeagleBoardUbuntu under the subsection "Raring 13.04 armhf". Position yourself inside /boot/uboot/tools/ubuntu/ (not really really needed) and run the script small-lxde-desktop.sh with sudo:cd /boot/uboot/tools/ubuntu/sudo ./small-lxde-desktop.shWill take a while, around 30 minutes for me. Then reboot. Use again ubuntu as user and temppwd as password. For some reason the mouse will be "hidden" even thought it's still there. You can access a terminal in Start/System_Tools/XTermIf you want Lubuntu (the core part, install apps later), you will need an 8gb card or bigger, use:sudo apt-get updatesudo apt-get install lubuntu-coreThis will take 1-2 hours to finish.6.- Configure TightVNCI used Vinagre (Remote Desktop Viewer) on my laptop with Ubuntu 13.04. I installed it via the software center.We will use a variation of /2013/01/13/remote-server-access-lxde-vnc/ . On the BBB (either directly on it or via SSH, I prefer SSH), enter in a terminal or command line:sudo apt-get updatesudo apt-get install aptitudesudo aptitude install tightvncservertightvncserver :1I (maybe foolishly, but whatever) put temppwd as the password for VNC too. Do not create a view-only password. Then, on the BBB:tightvncserver -kill :1nano ~/.vnc/xstartupAnd add this line at the end of the file if using small LXDE:lxterminal & /usr/bin/lxsession -s LXDE &If using Lubuntu, erase the line /etc/X11/Xsession, and add:/usr/bin/startlubuntu &Again, on the BBB:tightvncserver :1Start the remote desktop viewer, and connect via VNC to 192.168.7.2:1, enter the pass temppwd, and you will get the remote desktop. You can change the resolution, on the BBB:tightvncserver -kill :1tightvncserver :1 -geometry 800x600 -depth 16 -pixelformat rgb565:And connect again with Remote Desktop Viewer. That's all for the basics. As you may see, the theme does not behaves well right now, don't know how to fix it, but it seems perfectly usable, if bare bones. Personally, I think that you should use the VNC as a last resort, as it's heavy and resource consuming. Kill the server when finished:tightvncserver -kill :1To run the VNC at the BBB startup with small LXDE, do on the BBB:sudo nano /etc/init.d/tightvncserverAnd copy and paste (taken from /2013/01/13/remote-server-access-lxde-vnc/ ):#!/bin/sh### BEGIN INIT INFO# Provides: tightvncserver# Required-Start: $local_fs# Required-Stop: $local_fs# Default-Start: 2 3 4 5# Default-Stop: 0 1 6# Short-Description: Start/stop tightvncserver### END INIT INFO# More details see:# /linux/tightvnc### Customize this entry# Set the USER variable to the name of the user to start tightvncserver under export USER='root'### End customization requiredeval cd ~$USERcase "$1" instart)su $USER -c '/usr/bin/tightvncserver :1'echo "Starting TightVNC server for $USER ";;stop)pkill Xtightvncecho "Tightvncserver stopped";;*)echo "Usage: /etc/init.d/tightvncserver {start|stop}"exit 1;;esacexit 0Remember to change the USER key value (export USER='root'). I have not tested any of this, so be careful. If this is done wrong, you may need to erase /etc/init.d/tightvncserver via SSH or directly from the card using your PC. Then run on the BBB:sudo chmod 775 /etc/init.d/tighvncserversudo update-rc.d tightvncserver defaultsAnd finally reboot. Again, a word of caution, as I have not tested this myself and if done wrong may be tedious to fix.7.- AdditionalsThe BBB can be accessed via SSH without HDMI output right away. If LXDE was installed, it's convenient to be able to select whether or not the GUI is automatically started.To disable the slim login "thing" in LXDE (do it anyway, really), enter in the BBB:sudo update-rc.d -f slim removeAnd reboot (seen in /2009/01/disable-service-startup-in-ubuntu/ ). You can re enable it (in the BBB, via SSH) if you wish, by doing:sudo update-rc.d slim defaultsThis way, you can stop using the HDMI output, and start the SSH session from your PC directly. If you were to use the HDMI output, you would see a simple command line. You can use SSH either way.To start the VNC session, simple enter via SSH:tightvncserver :1 -geometry 800x600 -depth 16 -pixelformat rgb565:And then connect via the Remote Desktop Viewer. Finish the VNC session in the RDV, and then use via SSH:tightvncserver -kill :1You can monitor resource usage in the BBB via SSH with:sudo ps auxThe LXDE session for VNC consumes around 7% of RAM space while idle.8.- Installing ROSWe will have to install from source, as in /wiki/groovy/Installation/Source , but with some modifications to the process. This WILL take a lot of time, at least 4-5 hours, if not more.On the BBB (I used SSH), enter:sudo sh -c 'echo "deb /ros/ubuntu quantal main" > /etc/apt/sources.list.d/ros-latest.list'wget /ros.key -O - | sudo apt-key add -sudo apt-get updateThen, on the BBB:sudo apt-get install python-rosdep python-rosinstall-generator python-wstool build-essentialsudo rosdep initrosdep updateThen, on the BBB (note that the last line is different from the ROS wiki version):mkdir ~/ros_catkin_wscd ~/ros_catkin_wsrosinstall_generator ros_comm --rosdistro groovy --deps --wet-only > groovy-ros_comm-wet.rosinstallwstool init -j1 src groovy-ros_comm-wet.rosinstallTo resolve dependencies, use:rosdep install --from-paths src --ignore-src --rosdistro groovy -yAfter around 1 hour, an error will occur, install sbcl-source and sbcl-doc, then retry 2 times.sudo apt-get install sbcl-source sbcl-docrosdep install --from-paths src --ignore-src --rosdistro groovy -yrosdep install --from-paths src --ignore-src --rosdistro groovy -yInstall liblog4cxx10 (if dependencies were resolved correctly, this is unneeded):sudo apt-get install liblog4cxx10 liblog4cxx10-devBuild the workspace:./src/catkin/bin/catkin_make_isolated --installThis is going to take around 2 hours. Finally:source ~/ros_catkin_ws/install_isolated/setup.bashAnd enter via SSH:export LC_ALL=CThis line should be added to the .bashrc file, to be executed by default in all terminals (I could avoid this fix, after installing a ton of senseless packages and messing around, impossible to say how now, though I think that maybe it was updating the build tools, gcc, and the like)The end of my .bashrc looks like (my workspace is ~/catkin_ws, see the ros wiki tutorials):# ROS stuffexport LC_ALL=Cexport ROS_HOSTNAME=armexport ROS_MASTER_URI=http://arm:11311source ~/ros_catkin_ws/install_isolated/setup.bashsource ~/catkin_ws/devel/setup.bashsource ~/catkin_ws/install/setup.bash9.- Test itOn the BBB, try:ssh ubuntu@armroscore10.- Other problems I had* DNS Issues (wifi adapater works fine but system cannot resolve for ip addresses), just do:sudo rm /etc/resolv.confsudo dpkg-reconfigure resolvconfMy resolv.conf looks like:# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTENnameserver 1.1.1.1domain localdomainsearch localdomainnameserver 192.168.1.1The problem seems to be the first nameserver line. The ip above should be different for you, and you could simply add the google DNS addresses (8.8.8.8 and 8.8.4.4).Then reboot.See:/questions/142327/can-not-access-internet-dns-names-do-n ot-resolve-after-update-today/questions/292622/cannot-resolve-dns-on-12-10-install* The icon theme on the VNC session with LXDE seems missing:No idea why, share if you know any fix. Maybe install Lubuntu, seems to work finewith VNC.* roscore fails to start, cannot ping ubuntuSeems that a dirty fix is to simply add:192.168.7.2 ubuntuTo /etc/hosts hosts list (with sudo nano ...). I don't really know what's going on, if you have this problem and you know a better fix, please share.My hosts file looks like:127.0.0.1 localhost127.0.1.1 arm192.168.7.2 ubuntu* SSH is rejectedDon't know why, sometimes all I need is to reboot, another time I just redid the steps for configuring SSH.* Cannot recognize USB device (fails to power)Seems like a driver/hardware bug, reboot.11.- Compiling and installing open-cvModified from: /raspberry-pi-opencv/Position yourself in a workspace folder (if you wish), then:wget/projects/opencvlibrary/files/opencv-unix/2.4.3/OpenCV-2.4 .3.tar.bz2tar –xvf OpenCV-2.4.3.tar.bz2sudo apt-get updatesudo apt-get -y install build-essential cmake cmake-qt-gui pkg-config libpng12-0 libpng12-dev libpng++-dev libpng3 libpnglite-dev zlib1g-dbg zlib1g zlib1g-dev pngtools libtiff4-dev libtiff4 libtiffxx0c2 libtiff-tools sudo apt-get -y install libjpeg8 libjpeg8-dev libjpeg8-dbg libjpeg-progs ffmpeg libavcodec-dev libavcodec53 libavformat53 libavformat-dev libgstreamer0.10-0-dbg libgstreamer0.10-0 libgstreamer0.10-dev libxine1-ffmpeg libxine-dev libxine1-bin libunicap2 libunicap2-dev libdc1394-22-dev libdc1394-22libdc1394-utils swig libv4l-0 libv4l-dev python-numpy libpython2.7 python-dev python2.7-dev libgtk2.0-dev pkg-configcd OpenCV-2.4.3mkdir buildcd buildcmake -D CMAKE_BUILD_TYPE=RELEASE -D CMAKE_INSTALL_PREFIX=/usr/local -D BUILD_PYTHON_SUPPORT=ON -D BUILD_EXAMPLES=ON ..Compiling and installing will take a LONG time (+5 hours):makesudo make installConfigure with:sudo nano /etc/ld.so.conf.d/opencv.confAnd add the line at the end of file:/usr/local/libThen:sudo ldconfigsudo nano /etc/bash.bashrcAnd add at the end of file:PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfigexport PKG_CONFIG_PATHReboot, and finally:sudo apt-get upgradeEXTRA.- Make a backup image of your sd cardJust in case something goes terribly wrong and you need to restore the sd card to a previously working state. See/questions/299081/how-do-i-create-a-backup-image-of-an-sd-ca rd/questions/119211/how-to-write-image-to-sd-cardSHAR INTERNET CONNECTION VIA SSH/USBCOMPILE OPENCVCREAT BLOG AND UPLOADUPDATE SERVO INFOTEST ROSSERIAL ARDUINO BBB pyserial? FIX ICON THEME lubuntu?MAKE NEW PCB AND RESEND OLD ONE。