intel-aero / meta-intel-aero Goto Github PK

Hi.
We have been struggling for weeks now with a lot of technical issues with the Intel Aero drone and the "default" Yocto installation that comes with it (and released here on Github).
I am here trying to mark down our findings and issues.

• Old MAVROS version which does not support Ulogger
• Old meta-ros version
• meta-ros layer does not include librealsense

Finally we will now be trying to install Ubuntu as we are simply giving up on these Yocto issues!

Regards Thomas

Redo the patches on #30 to make it work

There are lots of outdated info on our wiki. And they will become even more after M0 and M1 are completed. Review and update the wiki after each milestone.

In order to provide better update process we need to boot from a thumb drive, without touching BIOS. There are some ways to do this:

1. We can add a boot entry on the bootloader of our internal drive to boot from a different drive and then allow it to boot from it only on next reboot
2. We can play with efivars in order to instruct the bios to boot from another place on next reboot

(1) is probably the easiest one and should allow us to provide an update mechanism without the user needing to connect keyboard and external monitor.

Mavlink Router already has capability to save the flight stack log (for PX4 is done, for ArduPilot is wip). Enable it by default on BSP.

Issue Type: bug?

Summary: When I try to run any of the librealsense examples on the Aero board I get an error. I have updated both the bios and the OS to the latest

Description:
in usr/share/librealsense/examples/cpp-multicam
Starting Intel RealSense R200 .... Done
terminate called after throwing an instance of 'std::runtime_error'
what(): VIDIOC_DQBUF error 19, No such device

Component affected: Realsense camera

BIOS Version: Exmaple: Aero-01.00.03

I have successfully built the Intel Aero image using the instructions in Quickstart Guide, and the images are located in intel_aero/poky/build/tmp/deploy/images/intel-aero. The files in here are:

bzImage
bzImage--4.4.3+git0+6ec93aaa70_3d2455f9da-r0-intel-aero-20170403025532.bin
bzImage-intel-aero.bin
core-image-minimal-initramfs-intel-aero-20170403025532.rootfs.cpio.gz
core-image-minimal-initramfs-intel-aero-20170403025532.rootfs.manifest
core-image-minimal-initramfs-intel-aero.cpio.gz
core-image-minimal-initramfs-intel-aero.manifest
intel-aero-image-intel-aero-20170403025532.hddimg
intel-aero-image-intel-aero-20170403025532.iso
intel-aero-image-intel-aero-20170403025532.rootfs.ext4
intel-aero-image-intel-aero-20170403025532.rootfs.manifest
intel-aero-image-intel-aero.ext4
intel-aero-image-intel-aero.hddimg
intel-aero-image-intel-aero.iso
intel-aero-image-intel-aero.manifest
modules--4.4.3+git0+6ec93aaa70_3d2455f9da-r0-intel-aero-20170403025532.tgz
modules-intel-aero.tgz
README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt

However, is there a way to run the image in the qemu emulator? (The configuration in meta-intel-aero/conf/local.conf.sample seems to provide some settings.)

I ran runqemu qemux86 intel-aero-image and got:

Assuming intel-aero-image really means /media/ruijia/143d637d-e685-4a48-8f62-c35a040695da/intel_aero/poky/build/tmp/deploy/images/qemux86/intel-aero-image-qemux86.ext4

Continuing with the following parameters:
KERNEL: [/media/ruijia/143d637d-e685-4a48-8f62-c35a040695da/intel_aero/poky/build/tmp/deploy/images/qemux86/bzImage-qemux86.bin]
ROOTFS: []
FSTYPE: [ext4]
Setting up tap interface under sudo
Error: Unable to find tunctl binary in '/media/ruijia/143d637d-e685-4a48-8f62-c35a040695da/intel_aero/poky/build/tmp/sysroots/x86_64-linux/usr/bin', please bitbake qemu-helper-native
ruijia@bliss:/media/ruijia/143d637d-e685-4a48-8f62-c35a040695da/intel_aero/poky/build/tmp/deploy/images/intel-aero$ runqemu qemux86 intel-aero-image
Assuming intel-aero-image really means /media/ruijia/143d637d-e685-4a48-8f62-c35a040695da/intel_aero/poky/build/tmp/deploy/images/qemux86/intel-aero-image-qemux86.ext4

Continuing with the following parameters:
KERNEL: [/media/ruijia/143d637d-e685-4a48-8f62-c35a040695da/intel_aero/poky/build/tmp/deploy/images/qemux86/bzImage-qemux86.bin]
ROOTFS: []
FSTYPE: [ext4]
Setting up tap interface under sudo
[sudo] password for ruijia: 
Error: Unable to find tunctl binary in '/media/ruijia/143d637d-e685-4a48-8f62-c35a040695da/intel_aero/poky/build/tmp/sysroots/x86_64-linux/usr/bin', please bitbake qemu-helper-native

rpm with dnf would be preferable.

Recovery firmware is useful for holding the FC into bootloader during boot so users can recover from a partly bricked scenario

Hi,
I am trying to determine the most minimally invasive way of switching the default ap_mode on boot to station mode. I have found some sources on system_ctl but I am unfamiliar with that tool. Any help is greatly appreciated.

Transmitting small chunks of bytes is fine at higher baudrates but when there is continuous transitions of data it start to drop some bytes.

On dmesg we can see several messages like this:
[ 224.450230] serial8250: too much work for irq39

A easy way to reproduce it is flash the FPGA with: /etc/aero_compute_board_only_fpga.jam connect a FTDI to the HSUART pins on the power connector and send continuous data from you host machine to Aero compute board.

This is the same HSUART used to communicate with AeroFC so is very important have a this HSUART working.

Issue Type: Feature/Task

Summary: Ubuntu has a mature package management system, which provides a large number of precompiled libraries such as boost, ros, opencv openpcl. Yocto does not.

Description: Can we get an Ubuntu 16.04 image for the Aero board

Component affected: All features of the board

http://logs.px4.io/plot_app?log=fea66d89-2473-4690-9508-c3d151be6543#Nav-Raw-Acceleration
In this plot you can see that there is too much noise. We suspect that this has to do with the motors not being dampened.

meta-intel-aero-* can be removed and the respective layers from yocto could be forked directly. Or depending on the package we could just have some .bbappend files. This way it's easier to see what's different from baseline and intel-aero

We should be using meta-intel layer so 1) we share all the improvements from that layer and 2) It makes our lives easier wrt updates.

• meta-intel-aero should be a thin layer, basically for configuration
• Bump kernel to meta-intel: 4.4, 4.9 or 4.10

I had have some random disconnects when using the WIFI of the Aero. BIOS, OS and FPGA are all up to date.

BIOS_VERSION = Aero-01.00.12_Prod
OS_VERSION = v01.00.04
AIRMAP_VERSION = 1.8
FPGA_VERSION = 0xff 0xff

The dmesg output can be seen here: http://pasted.co/6e217e2b

Some ways to keep the user notified about the installation progress:

• Use the RGB LED: for compute-board only since RGB LED is not visible on RTF.
• Open a mavlink shell on the FC and instructs tap_esc to make a sound (need to check ESC commands and ensure it works) - for RTF only since compute-board alone doesn't have a FC
• Create an http server so the user can go to http://intel-aero.local and keep updated about the progress

We can consider each of the items above as a task for this issue.

Issue Template:

Issue Type: It can be Bug, Task, Feature, Risk, Story

Summary: A short summary to explain the issue in one or two lines

Description: Add details of the issue such as, expected behavior, current behavior, how often its reproduced, steps to reproduce etc

Component affected: Such as USB, wifi, etc

Git tag tested: Example: v01.00.01

BIOS Version: Exmaple: Aero-01.00.03

Note: Attach logs, validation reports, test cases or any other issue related documents

Issue Type: Feature/Enhancement

Summary: Add Airspace Data Access

Description: The AirMap airspace management system facilitates regulation conformity and notification compliance based on current location. Additionally, AirMap provides weather data, flight telemetry endpoint, and live alerts based on updated drone location.

Component: Airspace Management

BIOS version: 01.00.05

Issue Type: Documentation feature request

Summary: Wiki: Application example in "Develop on Intel Aero" section should be updated to use devtool

Description: devtool is a Yocto tool that simplifies application development by generating recipes from source code, deploying resulting package and even allows building of image with that package included. See https://wiki.yoctoproject.org/wiki/Application_Development_with_Extensible_SDK#Creating_a_recipe_from_existing_source as an example. I can make changes if given access to wiki.

Component affected: Documentation

Git tag tested: N/A

BIOS Version: N/A

http://logs.px4.io/plot_app?log=fea66d89-2473-4690-9508-c3d151be6543#Nav-GPS-Noise-_-Jamming
The GPS jamming indicator is very high. This could be due to the FPGA interfering with the GPS. I guess this could be improved by isolating and grounding the FPGA.

I also have problems getting a stable usb connection. I use sudo ifconfig <name> 192.168.7.1 to set the IP and then I can connect with ssh [email protected]. But usually after ~1min I get disconnected.

This is the ouput of dmesg on the aero:

[    6.888954] usb 2-4: new SuperSpeed USB device number 2 using xhci_hcd
[    6.940290] udevd[489]: failed to execute '/usr/local/bin/usb-R200-in_udev' '/usr/local/bin/usb-R200-in_udev': No such file or directory
[    6.967235] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[    6.970080] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[    6.971238] uvcvideo: Unable to create debugfs 2-2 directory.
[    6.972258] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[    6.973440] uvcvideo: Unable to create debugfs 2-2 directory.
[    6.973771] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.4/input/input5
[    6.975115] usbcore: registered new interface driver uvcvideo
[    6.975118] USB Video Class driver (1.1.1)
[    6.979028] NOHZ: local_softirq_pending 08
[    7.349047] NOHZ: local_softirq_pending 08
[    8.455382] NOHZ: local_softirq_pending 08
[   11.058927] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   11.059625] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   11.186927] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   11.187271] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   11.280887] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   11.304678] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   12.415367] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   12.415372] Bluetooth: BNEP filters: protocol multicast
[   12.415393] Bluetooth: BNEP socket layer initialized
[   12.419724] cherryview-pinctrl INT33FF:01: request() failed for pin 23
[   12.427044] cherryview-pinctrl INT33FF:01: pin-23 (INT33FF:01:414) status -16
[   13.369925] random: nonblocking pool is initialized
[   59.965088] serial8250: too much work for irq39
[   61.637765] serial8250: too much work for irq39
[   65.779958] serial8250: too much work for irq39
[   67.788440] serial8250: too much work for irq39
[   71.242480] serial8250: too much work for irq39
[   72.558296] serial8250: too much work for irq39
[   90.202296] serial8250: too much work for irq39
[   91.779111] serial8250: too much work for irq39
[   93.301081] serial8250: too much work for irq39
[  100.071983] serial8250: too much work for irq39
[  101.503165] serial8250: too much work for irq39
[  102.868234] serial8250: too much work for irq39
[  113.260915] serial8250: too much work for irq39
[  114.743131] serial8250: too much work for irq39
[  117.963209] serial8250: too much work for irq39
[  118.899672] serial8250: too much work for irq39
[  124.121901] serial8250: too much work for irq39
[  126.076408] serial8250: too much work for irq39
[  135.068071] serial8250: too much work for irq39
[  147.692916] serial8250: too much work for irq39
[  151.559838] serial8250: too much work for irq39
[  155.088738] serial8250: too much work for irq39
[  161.126032] serial8250: too much work for irq39
[  165.499261] serial8250: too much work for irq39
[  165.670239] serial8250: too much work for irq39
[  167.365762] serial8250: too much work for irq39
[  172.087731] g_ether gadget: high-speed config #1: CDC Ethernet (ECM)
[  172.621653] serial8250: too much work for irq39
[  178.257274] serial8250: too much work for irq39
[  181.301903] serial8250: too much work for irq39
[  188.029162] serial8250: too much work for irq39
[  202.056139] serial8250: too much work for irq39
[  206.889507] serial8250: too much work for irq39
[  206.941699] serial8250: too much work for irq39
[  207.558103] serial8250: too much work for irq39
[  212.268219] serial8250: too much work for irq39
[  212.740386] serial8250: too much work for irq39
[  223.867089] serial8250: too much work for irq39
[  226.630896] serial8250: too much work for irq39
[  229.477377] serial8250: too much work for irq39
[  229.556597] serial8250: too much work for irq39
[  231.961654] serial8250: too much work for irq39
[  232.462053] serial8250: too much work for irq39
[  234.578169] serial8250: too much work for irq39
[  239.800998] serial8250: too much work for irq39
[  242.054934] serial8250: too much work for irq39
[  250.933705] serial8250: too much work for irq39
[  276.998103] serial8250: too much work for irq39
[  277.111708] serial8250: too much work for irq39
[  284.885358] serial8250: too much work for irq39

and this is dmesg of my desktop:

[ 2279.421051] cdc_ether 1-9:1.0 usb0: register 'cdc_ether' at usb-0000:00:14.0-9, CDC Ethernet Device, f2:55:10:c7:eb:3a
[ 2279.427867] cdc_ether 1-9:1.0 enp0s20f0u9: renamed from usb0
[ 2279.452109] IPv6: ADDRCONF(NETDEV_UP): enp0s20f0u9: link is not ready
[ 2279.452250] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2279.452256] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2279.652318] userif-3: sent link down event.
[ 2279.652324] userif-3: sent link up event.
[ 2299.505039] userif-3: sent link down event.
[ 2299.505046] userif-3: sent link up event.
[ 2325.031929] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2325.031945] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2325.032360] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2325.060499] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2325.060894] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2325.235132] userif-3: sent link down event.
[ 2325.235136] userif-3: sent link up event.
[ 2370.025001] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2370.025009] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2370.025058] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2370.034206] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2370.034234] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2370.034238] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2387.489447] wlx98ded0115c14: authenticate with a0:c5:89:02:3e:15
[ 2387.509840] wlx98ded0115c14: send auth to a0:c5:89:02:3e:15 (try 1/3)
[ 2387.540019] wlx98ded0115c14: authenticated
[ 2387.543176] wlx98ded0115c14: associate with a0:c5:89:02:3e:15 (try 1/3)
[ 2387.551067] wlx98ded0115c14: RX AssocResp from a0:c5:89:02:3e:15 (capab=0x411 status=0 aid=1)
[ 2387.551822] wlx98ded0115c14: associated
[ 2387.566810] bridge-wlp4s0: disabling the bridge
[ 2387.583189] bridge-wlp4s0: down
[ 2387.583194] bridge-wlp4s0: detached
[ 2387.583217] /dev/vmnet: open called by PID 1636 (vmnet-bridge)
[ 2387.583221] /dev/vmnet: hub 0 does not exist, allocating memory.
[ 2387.583228] /dev/vmnet: port on hub 0 successfully opened
[ 2387.583232] bridge-wlx98ded0115c14: device is wireless, enabling SMAC
[ 2387.583233] bridge-wlx98ded0115c14: up
[ 2387.583275] bridge-wlx98ded0115c14: attached
[ 2387.766739] userif-3: sent link down event.
[ 2387.766741] userif-3: sent link up event.
[ 2415.044235] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2415.044252] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2415.044550] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2415.044560] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2415.062641] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2415.062695] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2415.062704] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2460.024246] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2460.024261] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2460.024544] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped
[ 2460.024553] cdc_ether 1-9:1.0 enp0s20f0u9: kevent 12 may have been dropped

PX4 is the flight stack coming on the FC. Adding both PX4 and ArduPilot binaries on the BSP allows to switch back and forth between them.

The 10 seconds delay is pretty annoying for on-vehicle use and as the boot prompt has only one choice its not adding any value. If the recovery console is significant then it should be cut to 2-3 seconds.

I'm not getting the hostap / SSID being broadcasted. I have the image from Tue Aug 16, built 15:11:54. I checked the known limitations but that did neither fix it nor is it practical to do this in the field. Reliable wifi is critical to make operating the board feasible.

hi
I bought an Aero board this time. There is a problem trying to connect wifi before basic test.
When switching from AP mode to station mode, the program continues to repeat as if it had an infinite loop.
When you exit the mode, wlan0 disappears. In this case, wlan0 appears in the format.
In addition, iwconfig does not hold all drives.
Also, after updating the BIOS, the board suddenly goes on fire, and then it dies and can not even format it.
Please let me know what the reason is.

Issue Type: Feature/Enhancement

Summary: Enable Watchdog functionality

Description: This patch aims to enable watchdog capability for the intel-aero platform, so that if the kernel/platform hangs by any chance the platform will be rebooted automatically after the TIMEOUT period.

Component: system feature

BIOS version: 01.00.05

https://github.com/01org/collision-avoidance-library

While trying to sort out all the librealsense mess I simply can't get my head around the missing parts from the librealsense library build.
I have managed to successfully build the image (obs. without build errors) while using librealsense 1.12.0 within the librealsense meta layer and realsense-camera in the ROS layer pointing/using this version.

But when I boot the image it does not boot properly but it detects the camera.
Though after detecting the camera I get an error that it does not find: "/usr/local/bin/usb-R200-in_udev"
This seem to be a part of the librealsense build which should have been copied from the config folder, see: https://github.com/IntelRealSense/librealsense/blob/master/scripts/install-r200-udev-fix.sh

What am I missing in my bb files to get this installed and become a part of the image as well?

PS. With regard to the realsense-camera layer, can anyone explain why this does not get included in the image automatically but always have to be built seperately as a package afterwards ("bitbake realsense-camera")?

This is a collection of tools that we keep adding here that should be provided by the original tools, not the cap'ed ones from busybox.

• ps
• tar

Just because it's horrible to use them and this should be developer-friendly.

The mavlink router service for the localhost would not start after the first time. The service runs perfectly initially but does not run after reboot. This is not always the case as sometimes it does run after reboot. I can test as needed to make sure we run multiple times to assure functionality.

Testing:

Add the localhost to mavlink router startup script (-e 127.0.0.1). Check connection locally using python example mavlink client. Reboot using CL command and also by pulling power.

Atomisp has been merged as a staging driver on upstream. Backport to 4.4.x to replace our current version

Review current list of packages on the image and remove unnecessary cruft. There are lots of packages installed that aren't used anymore and shouldn't be installed. And on the other hand there are useful packages like psutils that aren't.

The git clone command for getting the meta-intel layer was missing the -b krogoth flag. It would be a good idea to add that to the instruction to avoid getting the master branch of the layer instead of the Krogoth

Several recipes for ROS packages from the Yocto layer https://github.com/bmwcarit/meta-ros experience packaging issues of the following kind:

ERROR: genmsg-0.5.7-r0 do_package: QA Issue: genmsg: Files/directories were installed but not shipped in any package:
ERROR: roscpp-traits-0.5.7-r0 do_package: Fatal QA errors found, failing task.
ERROR: roscpp-traits-0.5.7-r0 do_package: Function failed: do_package
ERROR: genmsg-0.5.7-r0 do_package: Fatal QA errors found, failing task.
ERROR: genmsg-0.5.7-r0 do_package: Function failed: do_package
ERROR: roscpp-traits-0.5.7-r0 do_package: QA Issue: roscpp-traits: Files/directories were installed but not shipped in any package:
roscpp-traits: 3 installed and not shipped files. [installed-vs-shipped]

I have isolated the issue to come from f2374a8, specifically the additions to the conf/local.conf file to support a 32-bit arch cross-compilation scheme: f2374a8#diff-f95cc75ba253227ffb1e5b0c0705be2fR242

This prevents the a successful inclusion of ROS for the intel-aero platform.

This will be needed in case we want to provide a solution that also stores flight logs directly in a microSD card with the user just "plugging it in".

You already provide the pre-built yocto image ready to flash, why don't you provide the generated yocto sdk's for the image that can be generated by the same server+command line that created the image in first place. If you already do so, plz update the wiki + intel download center page accordingly.

It saves a lot of time and effort for developers who want to build apps on top of your product.

With the latest commit 07c3b7e the RealSense camera patch for the Kernel can not be applied and is failing when building.
Notice I am using librealsense 1.12.1 as supposed with the patch used (see https://github.com/intel-aero/meta-intel-aero/blob/master/recipes-kernel/linux/linux-yocto/realsense_camera_formats_linux-yocto_4.4.patch).
See error log below:

|    mark --> gen_homethomasintel_aeropokymeta-intel-realsenserecipes-kernellinuxfiles_desc.scc
|          patch RealSense_Camera_Support_linux-yocto_4.4.patch (.kernel-meta/patches/standard/base/series)
|    mark <-- gen_homethomasintel_aeropokymeta-intel-realsenserecipes-kernellinuxfiles_desc.scc
| (1/1) RealSense_Camera_Support_linux-yocto_4.4.patch
| [INFO]: check of .kernel-meta/patches/standard/base/links/files/RealSense_Camera_Support_linux-yocto_4.4.patch with "git am" did not pass, trying reduced context.
| [INFO]: Context reduced git-am of .kernel-meta/patches/standard/base/links/files/RealSense_Camera_Support_linux-yocto_4.4.patch with "git am" did not work, trying "apply".
| /home/thomas/intel_aero/poky/build/tmp/work-shared/intel-aero/kernel-source/.git/rebase-apply/patch:15: space before tab in indent.
|  	{
| Context reduced to (1/1) to apply fragment at 105
| error: patch failed: drivers/media/usb/uvc/uvcvideo.h:91
| error: drivers/media/usb/uvc/uvcvideo.h: patch does not apply
| Context reduced to (1/1) to apply fragment at 608
| [ERROR]: Application of .kernel-meta/patches/standard/base/links/files/RealSense_Camera_Support_linux-yocto_4.4.patch failed.
|          Patch needs to be refreshed. Sample resolution script:
|              .git/rebase-apply/resolve_rejects
| ERROR. could not update git tree
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_patch (log file is located at /home/thomas/intel_aero/poky/build/tmp/work/intel_aero-poky-linux/linux-yocto/4.4.3+gitAUTOINC+6ec93aaa70_3d2455f9da-r0/temp/log.do_patch.10359)
ERROR: Task 50 (/home/thomas/intel_aero/poky/meta/recipes-kernel/linux/linux-yocto_4.4.bb, do_patch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1500 tasks of which 1413 didn't need to be rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
  /home/thomas/intel_aero/poky/meta/recipes-kernel/linux/linux-yocto_4.4.bb, do_patch
Summary: There was 1 WARNING message shown.

After recent commits (eg. 3a09bb0) the default manifest file and the BBLayers file are no longer matching.

The result is a broken build.
OBS. All new users trying to build will not be able to follow the guide and build.

http://logs.px4.io/plot_app?log=fea66d89-2473-4690-9508-c3d151be6543#Nav-Altitude-Estimate
The barometer shows an altitude of almost 6000 meters. Is it a driver issue?

USB ethernet uses 192.168.7.x subnet which avoids conflicts with common used ranges. However the WiFi AP uses 192.168.1.x which makes it difficult to use when you have to wifi adapters on your computer and want to use one to keep connected to the internet.

Similar to #33, but we could combine both firmwares so people don't have to flash a new one.