Skip to content

Skycontroller nap-linux-2.0.0-rc3: software stack and protocols

Static read of the Skycontroller nap-linux-2.0.0-rc3 image’s software stack by one agent, 2026-10-04. Status: Agent-cited, with these claims re-checked by the commissioning session: the device-type and update-file tables (also re-derived in skycontroller-hardware-identity.md), that libmppd_hw_nap.so is the only hardware library shipped and contains nap_gamepad and nap_bb but not mpp_gamepad (control: nap_gamepad hits; libmpphw.so knows mpp2_gamepad, mpp_bb and nap_bb), the /video SDP relay template strings in usr/bin/mppd (matching a live unit’s reply), and the order of the factory-reader strings behind the serial and MAC correction. Not re-derived: the ARSDK project and command counts, the mppd call-site and action-table readings (section 4.5 is the agent’s own low-confidence decode), and the bottom-board protocol. Product facts from this report are about the image, which is the NG firmware and not the Skycontroller 2’s (see skycontroller-live-vs-image.md).

Correction 2026-10-04: where this report (and the first line of skycontroller-live-vs-image.md’s earlier text) says the live note’s TCP 7711 is not in mppd, that was a search method error; the port is built from a byte-swapped immediate (movw #0x1f1e) at 0x249a0 in this build’s mppd, and the RTP source port 5004 at 0x249b6. See skycontroller2-software-mapping.md.

Do not turn the emergency-action and takeoff-gate readings into public claims without a second read of mppd.

Static analysis only. Image root R = firmware/extracted/skycontroller-nap/rootfs; every path below is relative to R unless it starts with docs/. Nothing was connected to. Tools: llvm-objdump, llvm-readelf, radare2, strings, /usr/bin/grep, small Python scripts for table decoding.

Tags: Verified (bytes, listing or disassembly read), Agent-cited (taken from an existing project note, not re-read), Inference, Open, Recollection (my memory of public Parrot material, not evidence).

Address convention: mppd is an ET_EXEC with vaddr = file offset + 0x10000, so addresses quoted for it are vaddrs. For libarsdk.so the text segment has vaddr = file offset and the data segment is shifted by 0x10000; for libnapbb.so and nap_factory_reader vaddr = file offset (+0x10000 for the latter, which is also ET_EXEC).

Negative results: each one below was run with the same tool against a string or symbol known to exist (the control is named next to the result).

  1. The image identifies itself as ARSDK product id 0x0913. etc/boxinit.rc:23 sets ro.product.model.id "0x0913" and the image’s own arsdk_device_type_str (usr/lib/libarsdk.so 0x1fc08) names 0x0913 SKYCTRL_NG; 0x090f is SKYCTRL_2, 0x0915 SKYCTRL_2P, 0x0903 SKYCTRL. The default Wi-Fi name prefix is nap-ng-. Verified.
  2. The only bottom-board firmware in the image (lib/firmware/xmega.hex) presents USB 03eb:2407 with the strings “NAP GAMEPAD” and “www.parrot.com”, and libmppd_hw_nap.so, the only hardware backend mppd links, handles only nap_gamepad/nap_bb, never the mpp id 03eb:2406. A unit that enumerates as 03eb:2406 (the second-hand live reading) is not the hardware this build drives. Verified for the image, Agent-cited for the live unit.
  3. Architecture: mppd is the hub. It reads sticks from an evdev node fed by an ATxmega32C4 over USB HID, battery and LEDs over hidraw plus four sysfs GPIOs, attitude from sensorsd-mpp (@sensorsd), Wi-Fi from wifid (@wifid, @wifid-ap), GPS from gpsd (@gps), and talks ARSDK to the drone over Wi-Fi (STA, TCP 44444, video ARStream2 55004/55005) and to the phone over USB (Android accessory via aoad, iOS via /dev/ttyGS1, both carried in libmux) or over its own Wi-Fi AP. Verified for the links, Inference for some framing.
  4. Video: mppd receives the drone’s H.264 stream and re-sends it to the phone (mux channels over USB, or a UDP bridge plus an HTTP GET /video SDP handshake over Wi-Fi) and, when the hdmi_plugged property is 1, also to hudd, which decodes with the Hantro hx270 decoder and draws the HUD with Qt/EGL on the Mali GPU for HDMI. Verified strings and modules, Inference for the gating.
  5. ARSDK: 17 projects compiled in (602 command descriptors). A Skycontroller-specific project exists: Skyctrl (project id 0x04, 27 classes, 77 commands), plus Mapper (0x8a), Mapper_mini (0x8d), Drone_manager (0x89), Rc (0x88), Wifi (0x87), Controller_info (0x8c), Debug (0x8b). mppd references only a subset: the legacy Skyctrl AxisMappings, ButtonMappings, AxisFilters, GamepadInfos, Device and Wifi request classes are in libarsdk but unused by this mppd. Verified.
  6. New in mppd: action 26 emergency reaches the drone as Ardrone3_Piloting_Emergency from exactly one call site (0x20dca), unconditionally; takeoff is refused when the controller battery state is CRITICAL (at or below 10965 mV); ro.factory.type is the content of /customer_prod/type.txt or, if that file is absent, milos when the serial from /customer_prod/parameters.xml starts with a hard-coded 10 character product-code prefix and bebop otherwise; the ARSDK product to mapping-file table gives bebop (0x901), bebop_2 (0x90c), disco (0x90e, Evinrude), anafi4k (0x914), chimera (0x916) and nothing for any other id. Verified.
  7. Bottom board protocol: USB HID, 100 Hz endpoints. Report 1 is 24 button bits plus 8 signed-byte axes (-100..100); report 2 is a vendor report of 16 bytes in and 16 bytes out. Host to board commands are report 2, byte 1 = 0 axis threshold, 1 raw mode, 2 calibrate; board to host carries battery millivolts. LEDs are bit-banged by the host over GPIO 55 to 58. Verified.
  8. Corrections to an existing note: docs/notes/reverse-engineering/skycontroller-services-network.md says the serial comes from /factory/parameters.xml; the disassembly of nap_factory_reader shows serial from /customer_prod/parameters.xml and the MAC from /factory/parameters.xml. Open items are listed in section 9.

Everything user-facing runs inside mppd (153,772 bytes, stripped, Parrot, revision 75e90131... which equals the manifest’s drones/mpp/mppd). It is built from named modules visible as ulog cookies: main, config, mapper, piloting, camera, gps, sensors, wifi, wifi_ap, updater, blackbox, mppd_hud, router, drone_manager, drone_cfg, drone_item, proxy_manager, proxy_mpp, proxy_drone, proxy_mobile_mux, proxy_mobile_net, libwifid (all Verified, __ulog_cookie_* symbols in usr/bin/mppd).

Toward the pilot’s hands: an Atmel ATxmega32C4 on the bottom board enumerates as a USB HID device (03eb:2407). The kernel exposes it twice: as an evdev node, which libmppd_hw_nap.so reads through libevdev, and as a hidraw node, which libnapbb.so reads and writes for battery level and calibration commands. Both nodes are found by libjuba (udev tag JUBA) rather than by fixed path. The four status LEDs are not on the board’s USB protocol at all: libnapbb bit-bangs them through /sys/class/gpio/gpio55..58/value.

Toward the controller’s own sensors and radios, mppd is a client of local daemons over pomp message sockets: sensorsd-mpp at abstract @sensorsd (IMU and magnetometer attitude), gpsd at @gps (fed by btgpsdemux through /tmp/gps.socket), and wifid at @wifid for the station interface that joins the drone and @wifid-ap for the access-point interface the phone can join. System properties (libputils) carry the rest: ro.factory.*, hdmi_plugged, hudd.visibility.*, mppd.restream.ip, mppd.led.enable, mppd.mobile.debug, persist.aoa.uri.

Toward the drone: Wi-Fi station wlan0 (Qualcomm QCA9375, static fallback 192.168.42.3), ARSDK net backend with discovery, TCP 44444 for the command link, and the ARStream2 video link on UDP client ports 55004 (data) and 55005 (control). proxy_drone decodes and encodes drone traffic and owns the restream.

Toward the phone, three alternative paths, with USB preferred over Wi-Fi (net peer disconnected because mux peer is a priority): (a) USB to an Android phone, where aoad watches udev for USB devices, switches them to Android Open Accessory mode with libaoa, opens an abstract socket @/com/parrot/aoad/<bus>/<dev> and bridges the accessory bulk endpoints; mppd connects to that socket and runs libmux on it; (b) USB to an iOS device, where mppd opens /dev/ttyGS1 in raw mode (“iap tty opened”) and runs libmux on it; (c) Wi-Fi, where proxy_mobile_net runs an ARSDK net backend with an avahi publisher on the AP interface (wlan1, 192.168.44.1, wl18xx radio) and bridges stream sockets.

Toward the HDMI port: a udev rule on the hdmi switch runs usr/bin/hdmi_hotplug, which loads the GPU and decoder modules, sets property hdmi_plugged and starts hudd. mppd sends hudd telemetry messages and an H.264 restream; hudd decodes in hardware and draws the HUD.

From To Transport Framing Evidence Status
ATxmega32C4 bottom board kernel HID USB 2.0 full speed, VID 03eb PID 2407, interrupt IN ep1 and OUT ep2, 32 byte packets, bInterval 10 HID reports (section 5) descriptor bytes in lib/firmware/xmega.hex at 0x32da to 0x3341 Verified
kernel evdev “NAP GAMEPAD” mppd via libmppd_hw_nap.so /dev/input/event*, found by JUBA tag nap_gamepad evdev events, libevdev lib/udev/rules.d/55-juba-gamepad.rules; libevdev imports in libmppd_hw_nap.so; nap_gamepad string Verified
kernel hidraw libnapbb.so (in mppd, and nap_bb_cli) /dev/hidraw*, JUBA tag nap_bb report id 2, 16 bytes 56-juba-bb.rules; nap_bb_new/fcn.000010f8 read and fcn.000013ac write (17 byte write) Verified
libnapbb 4 LEDs bar graph sysfs GPIO 55,56,57,58, 16 bit shift per update write("0"/"1",2) loop over bit 15..0 fcn.000012d8 in usr/lib/libnapbb.so Verified; shift-register reading is Inference
sensorsd-mpp mppd abstract unix socket @sensorsd libpomp messages (SYNC, MAGNETO_CALIB, attitude %d%hhu%hhu%hhu%f%f%f%f) usr/bin/mppd strings, plus docs/notes/reverse-engineering/skycontroller-stick-path.md Verified strings; Agent-cited for the decode
gpsd (Parrot, 14 KB, libhardware backed) mppd @gps, pomp “unknown gps message: %u” strings in usr/bin/mppd, usr/bin/gpsd; etc/gps_config.txt has $tty=@/tmp/gps.socket Verified strings; socket type Inference
btgpsdemux gpsd @/tmp/gps.socket, sets property gps.socket.ready NMEA/ai2 style ($protocol=ai2) etc/gps_config.txt, etc/boxinit.d/50-wifi.rc Verified (file text)
wifid (STA) mppd abstract @wifid, pomp typed messages (scan results, network changed, cmd status) strings @wifid, @wifid-%s, decode error strings in usr/bin/mppd Verified strings
wifid --suffix ap mppd abstract @wifid-ap, pomp same etc/boxinit.d/50-wifi.rc; strings Verified
mppd hudd pomp IPC (hudd has pomp_ctx_bind, inet_addr, string 127.0.0.1, no @ names) plus RTP/H.264 restream into hudd’s vstrm_receiver messages SYNC, CTRL_ATTITUDE, CTRL_GPS, CTRL_BATTERY, DRONE_MODEL, CAMERA, RECORD_STATE hud_update_* strings in mppd; imports in hudd Verified names; loopback IP transport and ports Open
hdmi_hotplug (udev) modules, hudd /sys/devices/virtual/switch/hdmi/state, pstart hudd, property hdmi_plugged shell usr/bin/hdmi_hotplug, lib/udev/rules.d/99-hdmi.rules Verified
aoad Android phone libusb, AOA protocol, bulk endpoints raw bytes bridged to socket strings in usr/bin/aoad (“supports AOA protocol v%d”, “found bulk ep”) Verified
aoad mppd abstract unix socket @/com/parrot/aoad/%d/%d libmux usr/bin/aoad strings; “aoa socket opened” in mppd Verified
mppd iOS device /dev/ttyGS1 (USB gadget serial), raw mode libmux strings “cannot open /dev/ttyGS1”, “iap tty opened” Verified
mppd mux phone app libmux channels; IP hosts: skycontroller at 192.168.53.1 and the drone at 192.168.42.1 (mux_add_host), channels opened by immediate ids 4 and 5 (stream data, stream control) plus an updater channel and a blackbox channel ARSDK over mux mppd 0x25578 (mux_add_host x2, fcn.0001713c with r1=4 and r1=5); strings “cannot open stream data/control/updater mux_channel” Verified calls; channel to name pairing is Inference
mppd phone over Wi-Fi AP wlan1 192.168.44.1, ARSDK net backend, avahi publisher, UDP stream bridges, ports 5004/5005 server side, fragment size 65000 ARSDK over TCP, ARStream2 over UDP proxy_mobile_net strings, embedded JSON {"arstream_fragment_size": 65000, ... "c2d_update_port": 51, "c2d_user_port": 21} Verified strings; ports from movw immediates
mppd drone Wi-Fi STA wlan0, TCP 44444 (ARSDK), drone address 192.168.42.1, ARStream2 client ports 55004/55005 ARSDK net backend + ARStream2 movw 0xad9c (44444) at 0x2a90c with “192.168.42.1” at 0x2a916; JSON arstream2_client_stream_port: 55004 Verified
mppd libmppblackbox libmux channel, pomp messages %hhi%hhi%hhi%hhi%hhi (piloting info), button action usr/lib/libmppblackbox.so strings Verified
mppd updater mux updater channel from phone; also inotify on /update and the watch dir /data/lib/update_ftp; USB mass storage PLF header checks, MD5 strings in mppd (section 4.6) Verified strings
mppd debug TCP 127.0.0.1:%d when property mppd.mobile.debug is set ARSDK mux/IP bridge strings “DEBUG enabled: listen on 127.0.0.1:%d” Verified string; port Open
  1. The drone sends H.264 with ARStream2 to controller UDP 55004 (data) and 55005 (control). The controller’s own stream ports are announced in a JSON blob: arstream2_client_stream_port 55004, arstream2_client_control_port 55005, arstream2_supported_metadata_version 1 (string in mppd). Verified.
  2. proxy_drone (“initialize_restream”, “start_restream”) re-sends to the phone. For an HTTP-style client it answers GET /video with an SDP body (c=IN IP4 addr:%s, m=video %d RTP/AVP 96, a=rtpmap:96 H264/90000) and then sends RTP, with an IP TOS set (setsockopt(IP_TOS), qos_mode). The requested destination is taken from property mppd.restream.ip (“enable restream: ip=‘%s’”, “disable restream”). Verified strings. The live note’s TCP 7711 for this request is not a literal in the image: a scan of every movw/literal in mppd for 7711 found nothing, while the same scan found 44444, 5004, 5005, 55004, 55005 (control). Open.
  3. Over USB mux, stream data and control are carried on two mux channels (immediate ids 4 and 5). Over Wi-Fi, proxy_mobile_net bridges the sockets (“stream bridge data created”, “stream bridge ctrl created”). Verified strings.
  4. For HDMI, “hud restream” is a second UDP destination set up by initialize_hud_restream and sent to hudd; mppd reads property hdmi_plugged (string present). hudd links libvideo-streaming (vstrm_receiver_*), the Hantro decoder (H264DecInit, H264DecDecode, post-processor PP*, DMA buffers allocated through p7ump), and draws with Qt5 on -platform eglfs plus Mali (eglCreateImageKHR, UMP handles). If no frame has arrived it clears to /usr/share/hudd/default_frame.argb (1,658,880 bytes of ARGB pixels). Verified imports and strings; that mppd only restreams to hudd when hdmi_plugged=1 is Inference.
  5. The video path does not leave the controller by any other route: no ffmpeg-like binary, no RTSP server, no HLS. The hudd and mppd binaries are the only video consumers (libh264, librtp, libvideo-* link only into arsdk/hudd/mppd). Inference from the import lists.

3.1 Which command projects are compiled in

Section titled “3.1 Which command projects are compiled in”

usr/lib/libarsdk.so (333,456 bytes, ARSDK-ng revision d0abf562..., equal to the manifest’s drones/arsdk-ng; the XML generator libarsdkgen is at the same revision, and the manifest lists drones/arsdk-xml at e76d8e8...) exports 603 g_arsdk_cmd_desc_* symbols: 602 command descriptors named g_arsdk_cmd_desc_<Project>_<Class>_<Command> plus g_arsdk_cmd_desc_table. Project id is the low byte of the second descriptor word (decoded with arsdk_cmd_dec layout: word1 = cmd<<16 | class<<8 | project; cross-checked on Ardrone3_Piloting_PCMD = 0x20001, Emergency = 0x40001, Common_Common_AllStates = 0x400).

Project Id Descriptors Used by mppd Status
Common 0x00 85 11 Verified
Ardrone3 0x01 163 28 Verified
Minidrone 0x02 78 0 Verified
Jpsumo 0x03 53 0 Verified
Skyctrl 0x04 77 25 Verified
Powerup 0x08 33 0 Verified
Follow_me 0x86 24 1 (Stop) Verified
Wifi 0x87 14 0 Verified
Rc 0x88 11 0 Verified
Drone_manager 0x89 8 7 Verified
Mapper 0x8a 16 16 Verified
Mapper_mini 0x8d 5 0 Verified
Debug 0x8b 4 0 Verified
Controller_info 0x8c 2 0 Verified
Thermal_cam 0x8e 5 0 Verified
Animation 0x90 21 0 Verified
Generic 0x85 3 0 Verified

(“Used” counts come from the g_arsdk_cmd_desc_ names present in usr/bin/mppd; the full list is 88 names, all of which resolve to a descriptor in libarsdk, so the used column sums to 88. Positive control: Skyctrl_CoPiloting_SetPilotingSource is present by the same method, and mppd’s own earlier-documented Ardrone3_Piloting_PCMD is present.)

Yes. Skyctrl is project 0x04 with these 27 classes (class id in hex), exact names from the descriptor symbols:

WifiState (0x00), Wifi (0x01), Device (0x02), DeviceState (0x03), Settings (0x04), SettingsState (0x05), Common (0x06), CommonState (0x07), SkyControllerState (0x08), AccessPointSettings (0x09), AccessPointSettingsState (0x0a), Camera (0x0b), ButtonMappings (0x0c), ButtonMappingsState (0x0d), AxisMappings (0x0e), AxisMappingsState (0x0f), AxisFilters (0x10), AxisFiltersState (0x11), GamepadInfos (0x12), GamepadInfosState (0x13), CoPiloting (0x14), CoPilotingState (0x15), Calibration (0x16), CalibrationState (0x17), ButtonEvents (0x18), Factory (0x19), CommonEventState (0x1a). Verified (descriptor table decoded).

Classes mppd actually references (Verified, names in usr/bin/mppd): AccessPointSettings (SSID, WifiSecurity, WifiSelection), AccessPointSettingsState (the three ...Changed), Calibration (EnableMagnetoCalibrationQualityUpdates), CalibrationState (MagnetoCalibrationQualityUpdatesState, MagnetoCalibrationState), CommonEventState (Shutdown), CommonState (AllStatesChanged), CoPiloting (SetPilotingSource), CoPilotingState (PilotingSource), DeviceState (ConnexionChanged), SettingsState (AllSettingsChanged, ProductSerialChanged, ProductVersionChanged; ProductVariantChanged and CPUID are referenced from libmppd_hw_nap.so), SkyControllerState (AttitudeChanged, BatteryChanged, BatteryState, GpsFixChanged, GpsPositionChanged), WifiState (WifiAuthChannelListChangedV2, WifiCountryChanged, WifiEnvironmentChanged).

Classes present in the library and never referenced by mppd: Wifi request class (RequestWifiList, ConnectToWifi, ForgetWifi, RequestCurrentWifi, WifiAuthChannel), Device request class, ButtonMappings, ButtonMappingsState, AxisMappings, AxisMappingsState, AxisFilters, AxisFiltersState, GamepadInfos, GamepadInfosState, ButtonEvents, Camera (ResetOrientation), Factory (Reset), Settings (Reset, AllSettings). Control for the negative: the same strings | grep finds Skyctrl_CoPiloting_SetPilotingSource in mppd. Verified for “name not in the binary”; Inference that this mppd therefore does not answer those commands (a generic path through arsdk_cmd_find_desc could still decode an id it receives).

The Mapper project replaces the legacy mapping classes in this build. The Mapper command names present are: Grab, Grab_state, Grab_axis_event, Grab_button_event, Map_button_action, Map_axis_action, Set_expo, Set_inverted, Reset_mapping, Active_product, Button_mapping_item, Axis_mapping_item, Expo_map_item, Inverted_map_item, Application_axis_event, Application_button_event; Mapper_mini (id 0x8d) has the same shape for a second controller type (Axis_mapping_item, Button_mapping_item, Map_axis_action, Map_button_action, Reset_mapping) and is not used by mppd. Verified.

3.3 Product identifiers known to the image

Section titled “3.3 Product identifiers known to the image”

All four tables are in usr/lib/libarsdk.so or mppd; decoded from bytes.

Table A: arsdk_device_type_str (0x1fc08, switch on id - 0x900, 23 entries). Verified.

Id Name Id Name
0x0900 RS 0x090d POWERUP
0x0901 BEBOP 0x090e EVINRUDE
0x0902 JS 0x090f SKYCTRL_2
0x0903 SKYCTRL 0x0910 WINGX
0x0905 JS_EVO_LIGHT 0x0911 PAROS
0x0906 JS_EVO_RACE 0x0913 SKYCTRL_NG
0x0907 RS_EVO_LIGHT 0x0914 ANAFI4K
0x0909 RS_EVO_BRICK 0x0915 SKYCTRL_2P
0x090a RS_EVO_HYDROFOIL 0x0916 CHIMERA
0x090b RS3 0x090c BEBOP_2
0x0904, 0x0908, 0x0912 UNKNOWN

Table B: media directory per product (pointer table at libarsdk file offset 0x45320, used by the media/FTP interface). Verified.

Id Directory Id Directory
0x0901 Bebop_Drone/ 0x0903 SkyController/
0x090c Bebop_2/ 0x090f SkyController_2/
0x0911 Paros/ 0x0915 SkyController_2/
0x0914 Anafi4k/ 0x0902,0x0905,0x0906 Jumping_Sumo/, Jumping_Night/, Jumping_Race/
0x0916 Chimera/ 0x0900,0x0907,0x0909,0x090a,0x090d Rolling_Spider/, Airborne_Nigh/, Airborne_Cargo/, Hydrofoil/, Power_Up/

0x0913 is absent from this table.

Table C: firmware file name per product (pointer table at libarsdk file offset 0x453f8, used by arsdk_updater for uploads). Verified.

Id File Id File
0x0901 bebopdrone_update.plf 0x0903 nap_update.plf
0x090c bebop2_update.plf 0x090f mpp_update.plf
0x0911 paros_update.plf 0x0915 mpp2_update.tar
0x0914 anafi4k_update.tar 0x0916 chimera_update.plf

0x0913 is absent here too. The same strings list powerup_update.plf, disco_update.plf, jumpingsumo_update.plf, rollingspider_update.plf.

Table D: mppd product to mapping-file slot (byte table at 0x2e87c, indexed by id - 0x901, 22 entries, value 5 = unsupported; used by fcn.0001ea38). Verified.

Id Name (Table A) Slot
0x0901 BEBOP mapping_bebop
0x090c BEBOP_2 mapping_bebop_2
0x090e EVINRUDE mapping_disco
0x0914 ANAFI4K mapping_anafi4k
0x0916 CHIMERA mapping_chimera
all others (including all Skycontroller ids and Power Up) unsupported (“Bad product %04x, using default product instead”)

This resolves the “which product number selects which file” Open row on the published mapping page: the selector is the drone’s product id, not the controller’s. Disco maps through its codename id 0x090e, which Table A names EVINRUDE (Inference that Evinrude is the Disco: the slot is called disco and the id is not otherwise used; the image gives no direct statement).

Table E: the image’s own identity. etc/boxinit.rc:21,23,25: ro.product.model "Skycontroller", ro.product.model.id "0x0913", ro.updater.filename "nap_update.plf"; etc/boxinit.rc:32: ro.product.usb.pid 6860 (0x1acc) with the comment “USB pid from SkyController”; usr/bin/nap_factory_reader: default SSID is nap-ng- plus the last four characters of the serial (section 4.5). usr/bin/mppd reads ro.product.model.id at 0x25534 and 0x2721c, next to the code that builds the ARSDK device record it publishes; Inference that this id is what the phone sees as the device type.

  • Transports compiled in: arsdk_backend_net (TCP, avahi or net discovery, listener), arsdk_backend_mux, arsdk_publisher_avahi, arsdk_publisher_mux. usr/bin/arsdk-cli (44,824 bytes) can run either backend, either role, either discovery type, default mux-over-IP port 4321. Verified (usage text).
  • Updater: ARSDK updater interface over FTP and over mux; version string format %d.%d.%d%19[a-z-]%d%c with -alpha/-beta suffixes. Verified strings.
  • usr/bin/pomp-cli (libpomp client with pomp_addr_parse, timers) is a generic pomp socket tool, useful for talking to the abstract sockets listed in section 2.2 from a debug shell. Verified (imports).

Items already on the published page (file format, action and button numbers, expo, invert, default tables, emergency binding per directory) are not repeated. What follows is new or corrects something.

4.1 Which directory a unit loads (answer to an Open row)

Section titled “4.1 Which directory a unit loads (answer to an Open row)”

etc/mppd/{ro.factory.type} is expanded by a small template engine in mppd (strings “Multiple properties in a search pattern !”, “Missing ‘}’ in search pattern !”, “Property name is too long !”, “Property %s not found”). ro.factory.type is set once at early boot by nap_factory_reader (disassembled in main, 0x10a08):

  1. Try to open /customer_prod/type.txt (0x10b46). If it opens, read up to 0x5b bytes, strip one trailing newline and set ro.factory.type to that text (0x10c36 to 0x10c3e). So the directory name is whatever that file contains.
  2. If the file does not exist (errno 2), take the serial string (the value of serial_number read from /customer_prod/parameters.xml into ro.factory.serial by the first call at 0x10a24) and, if it is longer than 9 characters and its first 10 characters equal a hard-coded constant (string at file offset 0x1143 of usr/bin/nap_factory_reader; not reproduced here because it is a serial-format prefix), set milos; otherwise set bebop (0x10b64 to 0x10b84).
  3. A fifth write sets ro.factory.default.ssid to nap-ng- plus the last four characters of the serial (0x10c74 to 0x10caa).

Verified by disassembly. Which branch a given unit takes, and what its type.txt contains, remains Open (the partition is not in the image). The bebop and milos directories therefore are not firmware generations of the app but hardware or SKU variants of the same controller family.

Correction: docs/notes/reverse-engineering/skycontroller-services-network.md and skycontroller-stick-path.md put the serial in /factory/parameters.xml. The first call in main passes /customer_prod/parameters.xml with key serial_number and property ro.factory.serial; the second passes /factory/parameters.xml with key mac_address and property ro.factory.wifi-ap.mac_address. Verified (r2 operands 0x11055, 0x11043, 0x11063 and 0x110a0, 0x11081, 0x110ad). The boxinit statexec /factory/parameters.xml guard is unaffected.

Also: libmppd_hw_nap.so mppd_hw_send_all_settings (0x3ef4) reads ro.factory.type and sends Skyctrl_SettingsState_ProductVariantChanged with value 0 if the first character is b (0x62), otherwise 1. So bebop reports variant 0 and milos reports variant 1 to the app. Verified (instructions at 0x3f18 to 0x3f24).

4.2 Config persistence (answer to two Open rows)

Section titled “4.2 Config persistence (answer to two Open rows)”

Strings show the sequence: “no config file found for module %s”, “Copying default config %s to config %s”, “unable to copy file”, “Config read error for module %s. Reset default config”, “unable to reset config %s”, .cfg.tmp then rename. Module configs live in /var/lib/mppd/<module>.cfg (/var/lib is a link to /data/lib). Inference: on first use the default under /etc/mppd/<type>/ is copied there, and from then on the /var/lib/mppd copy is what is read, so it takes precedence over /etc and survives reboots; Reset_mapping copies the default over it. Not traced instruction by instruction.

etc/mppd/drone_manager.cfg (known_drones = ( );) is the default for the Drone Manager module. Strings wifi_key, security, drone_cfg, known_drones indicate that each known drone entry stores its Wi-Fi key in that file after the phone supplies it (“drone protected: wifi_key=‘%s’ given by mobile”, “already known”). Inference that it is stored in the clear in /data/lib/mppd/drone_manager.cfg.

4.3 Action dispatch (the part the published page marks Open: “other binding paths in code”)

Section titled “4.3 Action dispatch (the part the published page marks Open: “other binding paths in code”)”

mppd 0x20b90 is the button-action handler (log “Button Action %s(%d)” at 0x2f5b4). Structure, Verified by disassembly:

  • Action 28 (cycle_hud) is tested first (cmp r8, 0x1c at 0x20bcc) and handled through system properties hudd.visibility.level_count and hudd.visibility.level: it cycles a number stored in property hudd.visibility.level, which hudd reads. It never touches the drone.
  • Actions 16 to 27 go through a 12 entry halfword jump table at 0x20c84 (tbh), one entry per action in order.
  • Case table, with the descriptor each case loads (descriptor identified from the GOT-relative literal; the GOT slot is base 0x44358 + literal, cross-checked against the relocation names):
Action Name What the case does Descriptor Status
16 return_home reads the NavigateHome state; log “navigate home unavailable: do nothing” if not available Ardrone3_Piloting_NavigateHome (earlier note) Agent-cited for descriptor; Verified for the log branch
17 takeoff_land chooses TakeOff/UserTakeOff/Landing from the flying state; refuses takeoff with “Refusing takeoff because MPP battery is critically low” (0x20d1c, 0x20d86) Piloting_TakeOff, Piloting_UserTakeOff, Piloting_Landing Verified
18 video_record toggles using a stored state (ldr r2,[r4,0x64]; subs 1; movne 1) Ardrone3_MediaRecord_VideoV2 (literal 0x4c8 = slot 0x44820) Verified
19 take_picture Ardrone3_MediaRecord_PictureV2 (literal 0x43c = 0x44794) Verified
20 camera_exposition_inc adds a stored float step to the stored exposure value (offsets 0x70, 0xb0), rejects a negative step Ardrone3_PictureSettings_ExpositionSelection Verified for arithmetic; descriptor Inference
21 camera_exposition_dec subtracts, same bounds same same
22 flip_left direction argument 3 Ardrone3_Animations_Flip (literal 0x570 = 0x448c8) Verified
23 flip_right direction 2 same Verified
24 flip_front direction 0 same Verified
25 flip_back direction 1 same Verified
26 emergency loads descriptor and sends Ardrone3_Piloting_Emergency (literal 0x4bc = 0x44814) Verified
27 center_camera calls the camera object (0x18a12) with its saved default orientation Ardrone3_Camera_Orientation(V2) family (Inference) Open

(Flip direction values 3,2,0,1 for left,right,front,back agree with the ARSDK enum as I remember it, Recollection; the argument values themselves are Verified.)

Findings about emergency:

  • The literal that addresses the Emergency descriptor, 0x4bc, occurs exactly once in the code (0x20f3c, used by case 26 at 0x20dca). The scan was validated by finding the other descriptor literals (0x570, 0x4c8, 0x43c) at their known sites. So mppd itself originates Ardrone3_Piloting_Emergency at only one place, and that place does not test the flying state, the battery or any other condition before sending. Verified.
  • The route has no confirmation, hold or long-press logic in this handler. Whether a long-press is enforced by the gamepad layer (button combination masks exist: “button combination 0x%08x already mapped”) is not shown by the default tables, where every buttons field in axes is 0. Open.
  • Messages that arrive from the phone for the drone are forwarded by the proxy, so the app can also send Emergency through mppd irrespective of the mapping (Inference from the router rule table in 4.5; the 0x01000002 exact rule is Ardrone3_Piloting_PCMD).
  • In the milos directory no button is bound to action 26 (published page), and no other call site exists, so on a unit that loads milos the only hardware path to Emergency in this build is absent. Verified for the image; the unit’s type is Open.

Power and system actions (Verified strings): the power key triggers “user action: poweroff, syncing filesystem…”, “soft reboot”, “hard reboot” (the reboot path is in libmppd_hw_nap.so, which imports reboot); mppd_hw_shutdown_on_power_release exists; Skyctrl_CommonEventState_Shutdown is sent to the app. “Unable to create factory-reset file” with /update/.factory_reset: mppd can create the flag file that etc/boxinit.rc:78 acts on at the next boot. What triggers it is Open (no Skyctrl_Factory_Reset descriptor in mppd; probably another command id).

4.4 Other behaviours not on the published page

Section titled “4.4 Other behaviours not on the published page”
Item Detail Status
Controller battery policy libnapbb classifies battery millivolts: above 11065 NORMAL, 10965 to 11065 LOW, at or below 10965 CRITICAL; mppd refuses takeoff in CRITICAL Verified
Time accepts Common_Common_CurrentDate/CurrentTime from the phone, sets system time (“updating system time”), keeps an RTC fallback (“RTC not initialized, do not use it”, “RTC Timezone not saved, defaulting to GMT”) Verified strings
Periodic status log when persist.periodic.log is set, logs cpu:, battery, rssi_mpp, rssi, state, position, attitude Verified strings
Controller tells the drone its location Common_Common_.../position descriptors present; Ardrone3_PilotingState_PositionChanged used for the HUD Inference
Follow-me only Follow_me_Stop is referenced Verified
Blackbox libmppblackbox sends piloting info (5 signed bytes: flag, roll, pitch, yaw, gaz) and button actions over a mux channel to the app Verified strings
Debug bridge property mppd.mobile.debug enables a TCP listener on 127.0.0.1 Verified string
LEDs property mppd.led.enable (“enable LED module”, “disable LED module”) Verified strings
mppd “hardware” capability answers mppd_hw_has_wifi_ap returns 1, mppd_hw_is_gps_supported 1, mppd_hw_get_wifi_bands_supported 3, mppd_hw_get_mobile_connectivity 3 (constants in libmppd_hw_nap.so at 0x3fc0 to 0x3fc8) Verified constants; meaning of 3 is Inference (two bits, probably 2.4 and 5 GHz; USB plus Wi-Fi)
Axis shaping libmppd_hw_nap has apply_axis_expo, apply_axis_expo_int, axis_squaring_circle, axis_bound_inscribed_circle Agent-cited decode, Verified symbol names
Updater policy “refuse to downgrade software version”, “bad plf target (not %d)”, “bad plf app (not %d)”, “plf md5sum mismatch”; an update must be an UPDATE-type PLF whose target platform and application match mppd’s own, and an optional md5_check.md5 is compared (“No md5 file, don’t check update file integrity”) Verified strings; no signature check strings were found (control: md5 strings do exist)

4.5 The router (what stays local and what goes to the drone)

Section titled “4.5 The router (what stays local and what goes to the drone)”

mppd 0x286a0 and 0x287d4 are the printer and lookup for a rule table at 0x31680: 14 exact message ids, then 9 rules of the form (id, mask, set). Decoded (id layout project<<24 | class<<16 | cmd): mask 0xff000000 rules for project 0x04 (Skyctrl), 0x8a (Mapper) and 0x89 (Drone_manager), with set values 6 and 8; exact rules 0x01000002 (Ardrone3_Piloting_PCMD) and 0x01150000 with set 8; exact rules 0x00040001 and 0x00040002 with set 9. Inference: the sets name the destination proxies (a bit set over proxy_mpp, proxy_drone, proxy_mobile_*), so that the controller-owned projects are consumed by mppd itself instead of being forwarded to the drone. The mapping of set bits to proxies was not decoded. Open.

Three entry points, all Verified strings: a USB stick (“Update file found on USB (%s), starting update process”), the watch directory /data/lib/update_ftp set by ro.updater.watch.dir (“Update found on watch directory”), and the mux updater channel from the phone (“open update channel”, “update request: version=‘%s’ md5=‘%s’, size=‘%d’”, chunk ids with “chunk id gap”). It writes to /update, checks the PLF header, then reboots into update mode through libpinst (“rebooting in update mode”, pinst_setup_trigger; usr/bin/pinst_trigger documents boot mode 0 = kernel, 1 = updater).

All of this section is Verified from lib/firmware/xmega.hex (decoded to a 13,122 byte image, extents 0x0 to 0x3341), usr/lib/libnapbb.so, usr/bin/nap_bb_cli and the udev rules, unless marked.

  • Device descriptor at 0x32da: bcdUSB 2.00, class 0, bMaxPacketSize0 8, VID 0x03eb, PID 0x2407, bcdDevice 1.00, manufacturer index 1, product index 2, one configuration.
  • Strings at 0x330a and 0x3316 (stored as ASCII in the table; the USB string descriptor wrapper is generated by the firmware): NAP GAMEPAD, www.parrot.com.
  • Configuration 0x29 bytes: attributes 0xa0 (bus powered, remote wakeup), 100 mA; one interface, class 3 HID, subclass 1, protocol 3 as written in the descriptor; interrupt IN endpoint 0x81 and interrupt OUT endpoint 0x02, 32 bytes each, bInterval 10 ms (so 100 Hz polling); HID descriptor length 0x50 (80 bytes).
  • The same MCU flash path: usr/bin/bottom_board_update runs dfu-programmer atxmega32c4 flash /lib/firmware/xmega.hex --force --validate-first --ignore-outside, then launch, when the Atmel DFU id 03eb:2fd9 appears (52-bottomboard.rules), and sets property mpp.services.start 1, which is what starts mppd and aoad (class mpp). So the daemons do not start until the bottom board has been seen in DFU mode at least once per boot.

5.2 HID report descriptor (decoded from 0x324c)

Section titled “5.2 HID report descriptor (decoded from 0x324c)”
Report id Direction Content
1 (Generic Desktop, Joystick) input Buttons 1 to 24 as 24 single bits (3 bytes), then 8 axes with usages 0x30 to 0x37 (X, Y, Z, Rx, Ry, Rz, Slider, Dial), logical range -100 to +100, signed 8 bit each. Total payload 11 bytes
2 (vendor page 0xff00, usage 1) input and output 16 bytes each way, logical 0 to 255

Consequences: stick resolution is 201 steps per axis, which answers the “evdev range to signed char” question as far as the board’s side is concerned (the live note’s -100..100 is the same range); the 8 axes match the eight axis ids in the mapping files (AXIS_LEFT_LR…AXIS_MINI_RIGHT_UD) in order, and 24 button bits cover the eight physical buttons plus the 16 VIRTUAL_* direction bits of the button table only in part (the virtual bits are synthesized in mppd, since the mask table needs 24 bits for 8 physical plus 16 virtual, but the board reports at most 24 button bits; mapping of board bits to names was not read). Inference for the last point.

Exports (Verified): nap_bb_new, nap_bb_destroy, nap_bb_start, nap_bb_stop, nap_bb_set_debug_level, nap_bb_set_rec_led, nap_bb_set_wifi_leds, nap_bb_set_battery_leds, nap_bb_set_drone_leds, nap_bb_set_leds, nap_bb_axis_threshold_set, nap_bb_calibratie_zero, nap_bb_set_raw_mode, nap_bb_battery_state_str.

  • nap_bb_new (0x15a0) allocates a 0xd4 byte context, opens the hidraw path with open(path, 2) (O_RDWR) and, if a pomp loop is given, registers the fd with pomp_loop_add; nap_bb_start (0x1414) opens the four GPIO value files write-only and creates a pomp timer of 200 ms (“cannot start wd timer”).
  • Read path, callback at 0x10f8: read(fd, buf, 0x80); debug log “New HID raw frame : {DT : %4lli ms} : [0x..”. On the first frame it calls the connected callback with 1 and arms a 200 ms watchdog; the timer expiry (and nap_bb_stop) calls the same callback with 0. mppd logs these as “bottom board USB connection : OK/KO”. A frame is parsed only when length is at least 16, byte 0 is 2 and byte 1 is 0: bytes 2 to 5 are a little-endian 32 bit battery voltage in millivolts. The percentage is computed on the host: with x = mV/1000, p = 543.153 x^2 - 14.5276 x^3 - 6801.857 x + 28532.856, battery percent = 100 - trunc(p) clamped to 0..100 (constants at 0x1250 to 0x126c; spot check: 12.6 V gives about 100, 11.1 V gives about 14). State: above 11065 mV NORMAL (0), 10965 to 11065 LOW (1), at or below 10965 CRITICAL (2). The callback receives (millivolts, percent, state) only when any of them changed. The voltage range implies a 3-cell pack (Inference).
  • Write path (0x13ac): write(fd, buf, 0x11), so 17 bytes: report id 2 then 16 data bytes; anything other than 17 written is an error. Commands, byte 0 = 2, byte 1 = command:
Byte 1 Function Bytes 2, 3 CLI
0 per-axis threshold axis number, threshold (1 to 100; axis 0 to 8 per CLI help) th_set <axis> <th>, th_del <axis> (Inference: delete is threshold 0 through the same call)
1 raw mode flag 0 or 1 raw <flag>
2 calibrate gamepad none calibrate (nap_bb_calibratie_zero)
  • LEDs: not part of the USB protocol. fcn.000012d8 writes the 16-bit LED word one bit at a time, from bit 15 down to bit 0, as “0” or “1” (2 byte writes) to GPIO 0xc4/0xc8 fds, with the other two GPIOs written once per update (latch and clock, Inference: a 16 bit serial shift register on GPIOs 55 to 58). nap_bb_set_wifi_leds(level -1..4) ORs a 5-step bar into bits 14 to 10 (masks 0x4000, 0x2000, 0x3000, 0x3800, 0x3c00); nap_bb_set_rec_led toggles the top bit; battery and drone bars use the lower fields. Verified for the wifi bar and rec bit; other bit fields not decoded.

11,832 byte ARM binary linked only against libnapbb, libpomp. Actions: rec <flag>, wifi <level> (-1..4), nap <level> (battery bar), drone <level>, leds <16 bit hex>, th_set, th_del, bat (prints “Battery status : %u mV, %d%%. %s.”), raw, calibrate, debugon, debugoff, help, quit; -i for interactive. Verified (usage text).

Report id 1 is consumed by the kernel HID layer and surfaces as the evdev device named after the product string; lib/udev/rules.d/55-juba-gamepad.rules tags it nap_gamepad by VID/PID. libmppd_hw_nap.so gamepad_create opens it through the libjuba client, calls libevdev_new_from_fd, reads absolute min and max per axis, logs “Gamepad device [name=%s] [path=%s]” and “Gamepad device ID: [bus=%#x] [vendor=%#x] [product=%#x]”. The hidraw node also sees report 1 but libnapbb ignores it (it only accepts id 2 frames of 16 bytes or more). So libnapbb is a control and battery channel, and the stick stream is the evdev path, which settles the stick-path note’s Inference. Verified for both consumers; “report 1 is what feeds evdev” is Inference from the descriptor and the rules (the kernel HID driver binding was not examined).

Parrot items carry a git revision string embedded by the build; where it equals the manifest revision I say so. Third-party versions come from strings.

Section titled “6.1 usr/bin and usr/sbin (137 are symlinks, 120 of them to bin/busybox v1.25.0, built 2017-08-09)”
Path What it is Origin, version Status
usr/bin/mppd Controller hub, mapping, piloting, proxies, updater (153,772 B) Parrot, rev 75e90131 = manifest Verified
usr/bin/hudd HUD renderer, hardware H.264 decode, Qt5 eglfs (70,212 B) Parrot, manifest rev 39cc782f Verified (no embedded rev)
usr/bin/aoad Android Open Accessory bridge Parrot, rev 864646da = manifest Verified
usr/bin/avabye minimal mDNS/DNS-SD responder (19,000 B) Parrot, rev 47732564 = manifest Verified
usr/bin/jubamountd USB storage automounter, notifies juba clients Parrot, rev 58ffa8b8 = manifest juba Verified
usr/bin/jubadump dumps juba (udev-tagged device) state Parrot, same rev Verified
usr/bin/pomp-cli generic libpomp client Parrot, rev 22e24c3d = manifest libpomp Verified
usr/bin/nap_bb_cli bottom board CLI Parrot, uses libnapbb b318b530 Verified
usr/bin/nap_factory_reader reads factory XML and type file into ro.factory.* Parrot, rev a32e37b5 = manifest Verified
usr/bin/bottom_board_update shell: flash xmega with dfu-programmer Parrot script Verified
usr/bin/arsdk-cli ARSDK test client (mux or net, controller or device) Parrot, rev 5c5d5bec = manifest Verified
usr/bin/sensorsd-mpp IMU and magnetometer daemon (libiio, Eigen) Parrot, libsensorsd 51016fe9 = manifest Verified
usr/bin/wifid, usr/bin/wifid-cli Wi-Fi manager (STA and AP) and its CLI Parrot, libwifid 8407a900 = manifest Verified
usr/bin/gpsd Parrot GPS daemon, not the gpsd project (14 KB, libgps/libhardware) Parrot, rev 0e3ad46c = manifest libgps Verified
usr/bin/btgpsdemux Bluetooth GPS demultiplexer Parrot, rev 4859bb4d = manifest Verified
usr/bin/crashdump crash dumper (libunwind) Parrot, rev 66c204ed = manifest Verified
usr/bin/kmsgd, ulogcat, ulogctl, ulogger, ulogwrapper ulog logging stack Parrot, ulog b338c97d = manifest Verified
usr/bin/pinst_trigger, pinst_version, ubi_check installer boot-mode and UBI tools Parrot, rev 27d5f915 = manifest parrot_libs Verified
usr/bin/shs-cli settings service CLI (libshs) Parrot, dbee3bb8 = manifest Verified
usr/bin/cprop, gprop, sprop, wprop property compare-and-set, get, set, wait Parrot libputils da7509e3 Verified
usr/bin/pstart, pstop, pterm, prestart, askfirst service control and login shell wrapper over boxinit Parrot, rev 622f144a = manifest boxinit Verified
usr/bin/i2ctool I2C read/write tool Parrot, rev 64d38689 = manifest Verified
usr/bin/hdmi_hotplug shell, HDMI plug handler Parrot script Verified
usr/bin/start_dnsmasq_wlan1 shell, DHCP and NAT for the AP Parrot script Verified
usr/bin/factory_reset shell, factory reset Parrot script Verified
usr/bin/adbd Android debug bridge daemon Android adb, rev 1b2c1a48 = manifest external/adb Verified
usr/bin/dfu-programmer Atmel DFU flasher third party, 0.7.2 Verified
usr/bin/evtest, libevdev-tweak-device, mouse-dpi-tool, touchpad-edge-detector input device test tools libevdev project Verified (names)
usr/bin/lsusb, usb-devices, usbhid-dump, libusb-config, update-usbids.sh USB inspection usbutils 006, usbhid-dump Verified
usr/bin/iio_generic_buffer, lsiio IIO tools libiio / iio-utils Verified (names)
usr/bin/htop process viewer htop 1.0.2 Verified
usr/bin/top2, ps_procps, vmstat, pwdx/pmap/pstree (BusyBox) process tools procps 3.2.8 for the ELF ones Verified (libproc-3.2.8)
usr/bin/strace, strace-graph, strace-log-merge tracer strace 4.16 Verified
usr/bin/iperf bandwidth test iperf 2.0.5 Verified
usr/bin/openssl, c_rehash OpenSSL CLI OpenSSL 1.0.1u (22 Sep 2016) Verified
usr/bin/pcregrep, pcretest, pcre-config, pcap-config PCRE and pcap helpers PCRE 8.x (libpcre.so.1.2.7), libpcap 1.1.x Verified (names)
usr/bin/xmllint, xmlcatalog, xmlwf, xml2-config, ncurses5-config libxml2 2.9.0, expat, ncurses 5.9 tools third party Verified (lib versions)
usr/bin/chattr, lsattr, uuidgen, tree, nsenter-ng, ldd misc e2fsprogs 1.42.12, util-linux, tree, shell Verified (names)
usr/bin/udevd, udevadm udev daemon and tool udev, rev d81608ad = manifest Verified
BusyBox applets in usr/bin (120 names across usr/bin and usr/sbin) [ [[ awk basename blkdiscard chrt chvt clear cmp cut dc deallocvt dirname dos2unix du env expr fgconsole find flock free ftpget groups head hexdump hostid id install killall less logger logname lsof lspci lzopcat md5sum mkfifo mkpasswd nc nsenter nslookup od openvt passwd pmap pstree pwdx readlink renice reset resize rx seq setsid sha1sum sha3sum shuf smemcap sort strings tail taskset tee telnet test time top tr traceroute truncate tty uniq unix2dos unlink unlzop unshare unxz uptime uudecode uuencode vlock volname wc wget which whoami whois xargs xz xzcat yes; sbin: addgroup adduser arping chroot delgroup deluser fbset fdformat ftpd i2cdetect i2cdump i2cget i2cset ifplugd inetd nanddump nandwrite nbd-client ntpd powertop rdate telnetd ubiattach ubidetach ubimkvol ubirename ubirmvol ubirsvol ubiupdatevol BusyBox 1.25.0 Verified (symlinks)
usr/sbin/dnsmasq DHCP server dnsmasq (version string is %s, number not found) Verified
usr/sbin/hostapd, hostapd_cli AP daemon hostapd v2.1-devel Verified
usr/sbin/wpa_supplicant, wpa_cli, wpa_passphrase station supplicant wpa_supplicant v2.0 Verified
usr/sbin/iw nl80211 tool iw 3.17 Verified
usr/sbin/tcpdump packet capture tcpdump 4.1.1 Verified
usr/sbin/iftop, genl-ctrl-list, nl-* (14 tools) traffic and netlink tools iftop, libnl 3.x (soname 200.19) Verified
usr/sbin/iptables, ip6tables, -save, -restore, usr/bin/iptables-xml links to xtables-multi iptables Verified
usr/sbin/e2fsck, mke2fs, tune2fs, resize2fs, dumpe2fs, e2image, e2undo, e2freefrag, e4defrag, badblocks, blkid, debugfs, filefrag, fsck, fsck-ng, logsave, mklost+found, sfdisk-ng, uuidd, links fsck.ext2/3/4/4dev, mkfs.ext2/3/4/4dev, e2label, findfs filesystem tools e2fsprogs 1.42.12, util-linux-ng Verified
Library What it is Origin, version Status
libarsdk.so ARSDK core, descriptors, backends, updater, media Parrot, d0abf562 = manifest Verified
libpomp.so Parrot message and event loop library Parrot, 22e24c3d = manifest Verified
libmux.so multiplexing transport (hosts, channels) Parrot, 15a249e5 = manifest Verified
libaoa.so AOA mode switch helper (libaoa_switch_device) Parrot, 864646da = manifest Verified
libmpphw.so juba-based hardware discovery for mpp_bb, nap_bb, mpp2_gamepad, plus P7 temperature readers Parrot, e3e86c76 = manifest Verified
libmppd_hw_nap.so nap hardware backend: gamepad, LEDs, shutdown, capability constants (built from the mppd repository, rev 75e90131) Parrot Verified
libnapbb.so bottom board HID and GPIO library Parrot, b318b530 = manifest Verified
libmppblackbox.so flight blackbox over mux Parrot, 989aeaa5 = manifest Verified
libhud.so.1.0.0 (links libhud.so, libhud.so.1, libhud.so.1.0) HUD widgets, Qt resources (icons for RSSI, satellites, batteries, recording, home) Parrot Verified (no embedded rev)
libhx270_dwl.so, libhx270_h264.so, libhx270_pp.so Hantro hx270 decoder wrapper, H.264 decoder, post-processor third party vendor Verified (symbols)
libvideo-streaming.so, libvideo-metadata.so, librtp.so, libh264.so ARStream2 receiver, metadata, RTP, H.264 parsing Parrot, f62ca00b/a8f40b92 = manifest Verified
libMali.so, libUMP.so, libGLES*, libEGL*, libion_parrot.so Mali-400 MP GPU userspace, memory ARM / Parrot Verified (Mali-400 string)
libjuba.so, libjuba_legacy.so, libjuba_provider.so udev-tag device discovery for clients and providers Parrot, 58ffa8b8 = manifest Verified
libwifid (inside mppd), usr/lib/wifid/cfg80211driver.so Wi-Fi driver glue (cfg80211, qca9375, wl18xx) Parrot Verified (path)
libshs.so settings service Parrot, dbee3bb8 Verified
libpinst.so, plib.so installer and PLF helpers Parrot Verified
libputils.so, libcutils.so, libbase.so, libfutils.so, libcrashdump.so, libcrypto_utils.so, libquaternion.so, libulog.so, libulogcat.so, libulogctl.so, libulog_syslogwrap.so Parrot and Android base libraries Parrot / Android Verified
libgps.so GPS hardware abstraction Parrot, 0e3ad46c Verified
libevdev.so.2.1.12 evdev access libevdev, rev 211bebeb = manifest Verified
libiio.so IIO sensor access libiio, rev fb9624e2 = manifest Verified
libconfig.so.9.2.0, libconfig++.so.9.2.0 libconfig (mapping file parser) libconfig Verified
libjson-c.so.2.0.2 JSON (also libjson.so link) json-c, rev 2daa4c57 = manifest Verified
libcrypto.so.1.0.0, libssl.so.1.0.0 TLS and MD5 OpenSSL 1.0.1u; usr/lib/engines/* are its stock engine plug-ins Verified
libusb-1.0.so.0.1.0, libusb-0.1.so.4.4.4 USB access libusb Verified
libudev.so, libudev-private.so udev client libs udev Verified
libnl-3, -cli-3, -genl-3, -idiag-3, -nf-3, -route-3 (.so.200.19.0) netlink libnl 3.x Verified
libpcap.so.1.1.1, libpcre.so.1.2.7, libpcrecpp, libpcreposix, libpopt.so.0, libproc-3.2.8.so misc third party Verified (names)
libxml2.so.2.9.0, libexpat.so.1.5.2, tinyxml.so, libyaml-0.so.2.0.4, libz.so.1.2.11 parsers and zlib third party Verified (names)
libncurses.so.5.9, libform, libmenu, libpanel (5.9), terminfo/ curses ncurses 5.9 Verified
libQt5{Core,Gui,Network,OpenGL,PrintSupport,Sql,Test,Widgets,Xml,Concurrent}.so.5.2.1, usr/lib/qt5/plugins Qt Qt 5.2.1 (manifest qtbase) Verified (names)
libstdc++.so.6.0.20 C++ runtime GCC 4.9 (GLIBCXX_3.4.20) Verified
libunwind*.so.8, .so.0 (6 libs) stack unwinding libunwind, rev 647cabb1 = manifest Verified
liburcu*.so.4.0.0 (7 libs) userspace RCU userspace-rcu Verified (names)
libip4tc, libip6tc, libiptc, libxtables.so.10.0.0, usr/lib/xtables/* iptables libs and match modules iptables Verified
libdaemon.so.0.5.0 daemon helpers libdaemon Verified
libnss_mdns* (6 files) glibc NSS mDNS resolvers libnss-mdns Verified
libwpa_cli.so wpa_cli client lib wpa_supplicant Verified
e2initrd_helper, usr/lib/fonts/* (Vera, DejaVu, Type 1 faces), usr/lib/terminfo helper, fonts Bitstream Vera, DejaVu Verified

Base system: glibc 2.19 (lib/libc-2.19-2014.08-1-git.so), Linaro GCC 4.9-2016.02, kernel modules for Linux 3.4.11+ with Parrot P7 drivers (p7-i2cmux, mali, ump, p7ump, hx270-vdec, hx-uio), InvenSense MPU6050 and AKM AK8975 sensors, TI wl12xx/wl18xx and a Qualcomm cfg80211 stack (Verified module list in lib/modules/3.4.11+).

The question: which Skycontroller generation is this image, and can it be matched to a Skycontroller 2? Evidence only from this image, listed once with its tag, then the reading.

# Evidence Where Tag
1 ro.product.model "Skycontroller" (no “2”) etc/boxinit.rc:21 Verified
2 ro.product.model.id "0x0913" etc/boxinit.rc:24 Verified
3 The image’s own table names 0x0913 SKYCTRL_NG, 0x090f SKYCTRL_2, 0x0915 SKYCTRL_2P, 0x0903 SKYCTRL libarsdk.so 0x1fc08 (Table A) Verified
4 Default SSID prefix nap-ng- nap_factory_reader strings and code 0x10c74 Verified
5 Build identity: project nap, variant linux, uid nap-linux-2.0.0-rc3, built 2017-08-09 etc/build.prop Verified
6 ro.product.usb.pid 6860 with comment “USB pid from SkyController” etc/boxinit.rc:32 Verified
7 Firmware table pairs 0x0903 SKYCTRL with nap_update.plf, 0x090f SKYCTRL_2 with mpp_update.plf, 0x0915 SKYCTRL_2P with mpp2_update.tar; 0x0913 is in neither the update-file table nor the media-directory table libarsdk.so Tables B and C Verified
8 This image’s own updater name is nap_update.plf (ro.updater.filename) etc/boxinit.rc:25 Verified
9 Media directories: 0x0903 SkyController/, 0x090f and 0x0915 SkyController_2/ Table B Verified
10 Bottom board firmware: USB 03eb:2407, strings “NAP GAMEPAD”, “www.parrot.com” lib/firmware/xmega.hex 0x32da to 0x3341 Verified
11 udev rules know mpp_gamepad 03eb:2406, nap_gamepad 03eb:2407, mpp2_gamepad (input name), mpp2_power (input qpnp_pon), mpp_bb, nap_bb lib/udev/rules.d/55-*, 56-* Verified
12 libmpphw.so discovers mpp_bb, nap_bb, mpp2_gamepad; libmppd_hw_nap.so handles only nap_gamepad and nap_bb (13 string hits for `nap_gamepad nap_bb, 0 for mpp_gamepad mpp_bb, same grep) and mppd` links only this backend
13 No libmppd_hw_mpp* and no libmppbb* library exists in the image although the manifest lists drones/mpp/libmppbb, drones/mpp2/mpp2-gamepad, drones/mpp/atmel, drones/mpp2/atmel, and three products mpp, mpp2, nap ls usr/lib (both patterns, ls of a name that exists, libmpphw.so, returned it); etc/manifest.xml Verified
14 Only one bottom-board firmware (xmega.hex), flashed by one script that watches only the Atmel DFU id lib/firmware, 52-bottomboard.rules Verified
15 Hardware features the image’s mppd reports: Wi-Fi AP present, GPS present, mobile connectivity bits = 3, wifi bands = 3; dual radio (QCA9375 STA, wl18xx AP), HDMI hotplug, Mali-400 and hx270 decoder libmppd_hw_nap.so 0x3fc0 to 0x3fc8, 50-wifi.rc, 99-hdmi.rules Verified
16 The update container targets platform 6, application 103, version 2.0.0, hardware compatibility 183847359 metadata.json (outside R) Agent-cited
17 etc/boxinit.rc: “When updating from 1.x.x, wipe the data partition to remove android-related files” etc/boxinit.rc:75-76 Verified

Reading, each step with its tag:

  • The image says it is product 0x0913, named SKYCTRL_NG by its own library. It does not say “Skycontroller 2” and does not use id 0x090f. Verified.
  • The firmware and hardware code it carries is the nap family only (items 10, 12, 14). A controller whose bottom board enumerates as 03eb:2406, as the second-hand live reading says Ryan’s does, would be an mpp board; this image has no backend that would read it (items 12, 13). So this image does not support a unit with the mpp board. Verified for the image side; the 03eb:2406 reading is Agent-cited (docs/notes/reverse-engineering/skycontroller-live-vs-image.md).
  • In the image’s own firmware table the mpp project goes with id 0x090f SKYCTRL_2 and the mpp2 project with 0x0915 SKYCTRL_2P; nap goes with 0x0903 SKYCTRL in that table although the image itself carries 0x0913. Verified for the pairings. That the live unit’s hostname mpp and its 03eb:2406 board correspond to the mpp project is Inference; if so, the id it would report is 0x090f.
  • Whether 0x0913 hardware is also sold or called “Skycontroller 2”: nothing in the image says. Recollection: Parrot’s public ARDiscovery enum has names SKYCONTROLLER, SKYCONTROLLER_2, SKYCONTROLLER_NG and SKYCONTROLLER_2P, and the “Skycontroller 2” sold with the Bebop 2 FPV pack is SKYCONTROLLER_2. The image’s own table having the same four names is consistent with that recollection but is not a statement of marketing names. What would confirm which one Ryan’s unit is, from this image’s point of view: (a) the value of ro.product.model.id on the unit (0x090f would mean SKYCTRL_2, 0x0913 SKYCTRL_NG), (b) the USB PID its bottom board shows (2406 mpp, 2407 nap), (c) ro.updater.filename (mpp_update.plf versus nap_update.plf), (d) the default SSID prefix (nap-ng- appears only for this build’s reader), (e) ro.parrot.build.uid on the unit.
  • Item 17 (the update wipes an Android layout) together with the original 03eb:2407 board and the SkyController/ media directory suggests the nap project is the older first-generation hardware line re-released on Linux, but nothing in the image says so. Inference only; and then the 0x0913 id and nap-ng- SSID are unexplained. Open.
  • Kernel image and device tree (not in R); the HID driver binding for 03eb:2407 and the evdev name it creates.
  • Dynamic behaviour of every daemon. Nothing was run.
  • wifid and cfg80211driver.so internals; Wi-Fi security decisions; hostapd generation.
  • The mux wire protocol of libmux (frame layout, channel numbering) and the ARSDK frame layout in libarsdk (arg encodings of any descriptor).
  • Router rule table semantics for the set values 6, 8, 9 and the 14 exact ids at 0x31680.
  • mppd modules gps, camera, sensors and drone_manager state machines beyond the strings; piloting was covered by the earlier stick-path note.
  • Arguments and order of the libaoa_switch_device call (the strings “Parrot”, the Play Store URI for the FreeFlight 3 app and property persist.aoa.uri are present; which AOA field each fills was not decoded).
  • hudd rendering, shader code under usr/share/hudd/shaders, and the exact loopback ports and transport used between mppd and hudd.
  • sensorsd-mpp beyond what the stick-path note records; gpsd and btgpsdemux protocols beyond config text.
  • libnapbb GPIO shift register details other than the wifi bar and record bit; the board’s own firmware logic (only descriptors and strings of xmega.hex were decoded, not the code).
  • BusyBox applet configuration, inetd.conf and network exposure: covered in skycontroller-services-network.md, not re-read.
  • The Qt plug-ins under usr/lib/qt5/plugins.
  1. What is the content of /customer_prod/type.txt (or the serial prefix) on Ryan’s unit, i.e. does it load bebop or milos, and is the milos set the one without an emergency button? Needs the unit; read-only property or file read.
  2. Is a unit that reports 03eb:2406 running a different firmware project (mpp) than this image? That firmware is not in the repository.
  3. Why does the image advertise 0x0913 while the firmware table in the same library pairs nap_update.plf with 0x0903, and why is 0x0913 missing from the media and update tables? Possible explanation: the tables predate the NG id; unverifiable from the image.
  4. What is the port that mppd listens on for GET /video (the live note says 7711; no literal in mppd matches), and what ports and transport connect mppd to hudd?
  5. Does the app-originated Emergency always pass the router, and does any long-press or combination logic gate the physical emergency button (button combination masks exist but no default uses them)?
  6. What triggers the factory-reset flag creation in mppd, and does Skyctrl_Factory_Reset get handled by a generic path?
  7. Which board report bits map to which of the 24 button bits, and what exactly does “raw mode” (host command 1) change in the board’s reports?
  8. Does the board report the stick data on hidraw as well (report 1 on hidraw is ignored by libnapbb), and what does nap_bb_calibratie_zero persist? The board’s own code is the only authority.
  9. Is /var/lib/mppd read in preference to /etc/mppd once the file exists (Inference above), and are the per-drone Wi-Fi keys stored there in the clear?

Comments

Spotted a mistake, or tried this on your own Bebop? Leave a note. Comments are kept on this site's own server.