I tried to build this SDK on more variants of linux than I care to admit. It only works successfully out of the box on Ubuntu. Specifically, Ubuntu 12.04.5.  I compiled this for use with my AR Drone 2, but I don’t see why it couldn’t be used with the AR Drone as well. There’s nothing here that makes the SDK specific to either model.

  1. Download Ubuntu 12.04.5 32bit. It probably works with 64bit (although I didn’t test it), if you really must use 64bit.
  2. Either install Ubuntu 12.04.5 alongside (dual boot) with another operating system, or in a virtual machine. I installed it in a VMware Fusion virtual machine on macOS. The Ubuntu operating system is agnostic, so it doesn’t really matter how you choose to virtualise it, if you do.
    1. Don’t install Ubuntu 12.04.5 updates during the installation process (leave the option unticked).
    2. Don’t install updates or upgrade Ubuntu to the next release when asked after the first login.
  3. Download the SDK (or copy it from somewhere to the Desktop).
  4. Open a terminal and change to your Desktop directory.
    1. # cd Desktop
  5. Unzip the SDK.
    1. # unzip ARDrone_SDK_2_0_1.zip
  6. Change to the ARDrone_SDK_2_0_1 directory
    1. # cd ARDrone_SDL_2_0_1 directory
  7. Run the following command (using sudo) to compile and install dependencies.
    1. # sudo ARDroneLib/Soft/Build/check_dependencencies.sh
      1. You’ll be asked to confirm installation of some packages, be sure to say Yes (y).
  8. Run the following command (using sudo) to compile the linux binaries.
    1. # cd Examples\Linux
    2. # sudo make
      1. Wait for the SDK binaries to be compiled
  9. The binaries are built in /home/<username>/Desktop/ARDrone_SDL_2_0_1/Examples/Linux/Build/Release/. Move them to you desktop and make them accessible as follows.
    1. # sudo mv /home/<username>/Desktop/ARDrone_SDL_2_0_1/Examples/Linux/Build/Release/ /home/<username>/Desktop/ARDroneApps
    2. # sudo chown -R <username>:<username> /home/<username>/Desktop/ARDroneApps
  10. Run the apps! You’ll need to be connected to your AR Drone 2 WiFi network first of course. Make sure you don’t have the Free Flight app open on any smart phones or tablets at the same time, as this will interfere with communications between your computer and your drone.
    1. # cd /home/<username>/Desktop/ARDroneApps
    2. # ./ardrone_navigation
    3. # ./linux_sdk_demo
    4. # ./linux_video_demo
    5. # ./sym_ardrone_testing_tool

Oh no! Your Motorola Xoom is Bricked (or is it)

You’ve tried everything you can think of. Hard reset, soft reset, factory reset, factory restore, factory wipe and erase. Nothing works! I thought that too!

Please read this entire article before trying anything!

So long as you can still reach the ‘Starting Fastboot Protocol Support’, by powering the device on (or resetting with Power + Volume Up) while holding the power and volume down button, you are probably not in as much trouble as you may think.

Visit this link and download the zip file:

http://www.android.net/forum/downloading/67/guest/SDK_tools.zip
(leave me a comment if the file is unavailable, I’ll upload a copy to this website)

Extract it to your C: drive, so the contents exist in:

C:SDK_tools

Visit this link:

http://developer.motorola.com/products/software/

Read this article for more information about the bundles.

Download the corrosponding bundle version for your location or region. I’m in Australia, so I downloaded the ‘Build H.6.1-38-9 for Telstra Australia’ bundle. Take a few moments to peruse the list, it’s a little confusing and I almost downloaded the wrong one. Make sure you download the right one. I’ve no idea what happens if you restore with the wrong files.

You’ll have to register to download the files. It’s free, which is not bad for something that is about to bring your Motorola Xoom back to life 🙂

Extract the archive and dump all the files directly into the C:SDK_tools directory.

Your directory listing should look something like this:

adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
ddms.bat
fastboot.exe
recovery.img
system.img
userdata.img

Depending on the amount of damage you’ve done to your Motorola Xoom, you may or may not need to do all of the following commands:

fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock

Note 1. If you intend to root or otherwise modify the OS in the near or far future, skip the last command (fastboot oem lock).

Note 2. If no userdata.img file is present in your download, please issue the command:

fastboot erase userdata

I only managed to screw up my boot partition (I think) as I only needed to excute the first command. Try them one at a time and reboot the Motorola Xoom. Give it time to come back to life before re-entering ‘Starting Fastboot Protocol Support’ again. When I say give it some time, I mean wait at least 5 minutes.

Note: you can unlock your Motorola Xoom with the following command:

fastboot oem unlock.

As for rooting the device… well I’m sure that’s the reason some of you are here! Do some more research before attempting it again, I know I did!