aboutsummaryrefslogtreecommitdiff
path: root/ROMFS
diff options
context:
space:
mode:
authorpx4dev <px4@purgatory.org>2013-02-19 21:45:17 -0800
committerpx4dev <px4@purgatory.org>2013-02-23 22:00:59 -0800
commitd3a6f448c93aaf6d611f1aa3d3af60788eb0ff7a (patch)
tree6d22a45ddba21b5af24bb2c806b51ae92480556a /ROMFS
parenteece05a287e48754a424d2a824a2ace3a5a89d51 (diff)
downloadpx4-firmware-d3a6f448c93aaf6d611f1aa3d3af60788eb0ff7a.tar.gz
px4-firmware-d3a6f448c93aaf6d611f1aa3d3af60788eb0ff7a.tar.bz2
px4-firmware-d3a6f448c93aaf6d611f1aa3d3af60788eb0ff7a.zip
Git zombies must die.
Diffstat (limited to 'ROMFS')
-rw-r--r--ROMFS/scripts/rc.FMU_quad_x40
-rw-r--r--ROMFS/scripts/rc.PX4IO73
-rw-r--r--ROMFS/scripts/rc.PX4IOAR80
-rw-r--r--ROMFS/scripts/rc.jig10
-rw-r--r--ROMFS/scripts/rc.logging9
-rw-r--r--ROMFS/scripts/rc.sensors34
-rw-r--r--ROMFS/scripts/rc.standalone13
-rwxr-xr-xROMFS/scripts/rcS136
8 files changed, 0 insertions, 395 deletions
diff --git a/ROMFS/scripts/rc.FMU_quad_x b/ROMFS/scripts/rc.FMU_quad_x
deleted file mode 100644
index d9c9a8457..000000000
--- a/ROMFS/scripts/rc.FMU_quad_x
+++ /dev/null
@@ -1,40 +0,0 @@
-#
-# Startup for X-quad on FMU1.5/1.6
-#
-
-echo "[init] uORB"
-uorb start
-
-echo "[init] eeprom"
-eeprom start
-if [ -f /eeprom/parameters ]
-then
- param load
-fi
-
-echo "[init] sensors"
-#bma180 start
-#l3gd20 start
-mpu6000 start
-hmc5883 start
-ms5611 start
-
-sensors start
-
-echo "[init] mavlink"
-mavlink start -d /dev/ttyS0 -b 57600
-usleep 5000
-
-echo "[init] commander"
-commander start
-
-echo "[init] attitude control"
-attitude_estimator_ekf start
-multirotor_att_control start
-
-echo "[init] starting PWM output"
-fmu mode_pwm
-mixer load /dev/pwm_output /etc/mixers/FMU_quad_x.mix
-
-echo "[init] startup done, exiting"
-exit
diff --git a/ROMFS/scripts/rc.PX4IO b/ROMFS/scripts/rc.PX4IO
deleted file mode 100644
index 84e181a5a..000000000
--- a/ROMFS/scripts/rc.PX4IO
+++ /dev/null
@@ -1,73 +0,0 @@
-#!nsh
-
-set USB no
-
-#
-# Start the object request broker
-#
-uorb start
-
-#
-# Init the EEPROM
-#
-echo "[init] eeprom"
-eeprom start
-if [ -f /eeprom/parameters ]
-then
- param load
-fi
-
-#
-# Enable / connect to PX4IO
-#
-px4io start
-
-#
-# Load an appropriate mixer. FMU_pass.mix is a passthru mixer
-# which is good for testing. See ROMFS/mixers for a full list of mixers.
-#
-mixer load /dev/pwm_output /etc/mixers/FMU_pass.mix
-
-#
-# Start the sensors.
-#
-sh /etc/init.d/rc.sensors
-
-#
-# Start MAVLink on UART1 (dev/ttyS0) at 57600 baud (CLI is now unusable)
-#
-mavlink start -d /dev/ttyS0 -b 57600
-usleep 5000
-
-#
-# Start the commander.
-#
-commander start
-
-#
-# Start the attitude estimator
-#
-attitude_estimator_ekf start
-
-#
-# Start the attitude and position controller
-#
-fixedwing_att_control start
-fixedwing_pos_control start
-
-#
-# Start GPS capture. Comment this out if you do not have a GPS.
-#
-gps start
-
-#
-# Start logging to microSD if we can
-#
-sh /etc/init.d/rc.logging
-
-#
-# startup is done; we don't want the shell because we
-# use the same UART for telemetry
-#
-echo "[init] startup done"
-exit
diff --git a/ROMFS/scripts/rc.PX4IOAR b/ROMFS/scripts/rc.PX4IOAR
deleted file mode 100644
index 640cdf541..000000000
--- a/ROMFS/scripts/rc.PX4IOAR
+++ /dev/null
@@ -1,80 +0,0 @@
-#!nsh
-#
-# Flight startup script for PX4FMU on PX4IOAR carrier board.
-#
-
-# Disable the USB interface
-set USB no
-
-# Disable autostarting other apps
-set MODE ardrone
-
-echo "[init] doing PX4IOAR startup..."
-
-#
-# Start the ORB
-#
-uorb start
-
-#
-# Load microSD params
-#
-echo "[init] loading microSD params"
-param select /fs/microsd/parameters
-if [ -f /fs/microsd/parameters ]
-then
- param load /fs/microsd/parameters
-fi
-
-#
-# Start MAVLink
-#
-mavlink start -d /dev/ttyS0 -b 57600
-usleep 5000
-
-#
-# Start the sensors and test them.
-#
-sh /etc/init.d/rc.sensors
-
-#
-# Start the commander.
-#
-commander start
-
-#
-# Start the attitude estimator
-#
-attitude_estimator_ekf start
-
-#
-# Configure PX4FMU for operation with PX4IOAR
-#
-fmu mode_gpio_serial
-
-#
-# Fire up the multi rotor attitude controller
-#
-multirotor_att_control start
-
-#
-# Fire up the AR.Drone interface.
-#
-ardrone_interface start -d /dev/ttyS1
-
-#
-# Start logging
-#
-#sdlog start
-
-#
-# Start GPS capture
-#
-gps start
-
-#
-# startup is done; we don't want the shell because we
-# use the same UART for telemetry
-#
-echo "[init] startup done"
-exit \ No newline at end of file
diff --git a/ROMFS/scripts/rc.jig b/ROMFS/scripts/rc.jig
deleted file mode 100644
index e2b5d8f30..000000000
--- a/ROMFS/scripts/rc.jig
+++ /dev/null
@@ -1,10 +0,0 @@
-#!nsh
-#
-# Test jig startup script
-#
-
-echo "[testing] doing production test.."
-
-tests jig
-
-echo "[testing] testing done"
diff --git a/ROMFS/scripts/rc.logging b/ROMFS/scripts/rc.logging
deleted file mode 100644
index 09c2d00d1..000000000
--- a/ROMFS/scripts/rc.logging
+++ /dev/null
@@ -1,9 +0,0 @@
-#!nsh
-#
-# Initialise logging services.
-#
-
-if [ -d /fs/microsd ]
-then
- sdlog start
-fi
diff --git a/ROMFS/scripts/rc.sensors b/ROMFS/scripts/rc.sensors
deleted file mode 100644
index 42c2f52e9..000000000
--- a/ROMFS/scripts/rc.sensors
+++ /dev/null
@@ -1,34 +0,0 @@
-#!nsh
-#
-# Standard startup script for PX4FMU onboard sensor drivers.
-#
-
-#
-# Start sensor drivers here.
-#
-
-ms5611 start
-adc start
-
-if mpu6000 start
-then
- echo "using MPU6000 and HMC5883L"
- hmc5883 start
-else
- echo "using L3GD20 and LSM303D"
- l3gd20 start
- lsm303 start
-fi
-
-#
-# Start the sensor collection task.
-# IMPORTANT: this also loads param offsets
-# ALWAYS start this task before the
-# preflight_check.
-#
-sensors start
-
-#
-# Check sensors - run AFTER 'sensors start'
-#
-preflight_check \ No newline at end of file
diff --git a/ROMFS/scripts/rc.standalone b/ROMFS/scripts/rc.standalone
deleted file mode 100644
index 67e95215b..000000000
--- a/ROMFS/scripts/rc.standalone
+++ /dev/null
@@ -1,13 +0,0 @@
-#!nsh
-#
-# Flight startup script for PX4FMU standalone configuration.
-#
-
-echo "[init] doing standalone PX4FMU startup..."
-
-#
-# Start the ORB
-#
-uorb start
-
-echo "[init] startup done"
diff --git a/ROMFS/scripts/rcS b/ROMFS/scripts/rcS
deleted file mode 100755
index 69d791da5..000000000
--- a/ROMFS/scripts/rcS
+++ /dev/null
@@ -1,136 +0,0 @@
-#!nsh
-#
-# PX4FMU startup script.
-#
-# This script is responsible for:
-#
-# - mounting the microSD card (if present)
-# - running the user startup script from the microSD card (if present)
-# - detecting the configuration of the system and picking a suitable
-# startup script to continue with
-#
-# Note: DO NOT add configuration-specific commands to this script;
-# add them to the per-configuration scripts instead.
-#
-
-#
-# Default to auto-start mode. An init script on the microSD card
-# can change this to prevent automatic startup of the flight script.
-#
-set MODE autostart
-set USB autoconnect
-
-#
-# Start playing the startup tune
-#
-tone_alarm start
-
-#
-# Try to mount the microSD card.
-#
-echo "[init] looking for microSD..."
-if mount -t vfat /dev/mmcsd0 /fs/microsd
-then
- echo "[init] card mounted at /fs/microsd"
-else
- echo "[init] no microSD card found"
-fi
-
-#
-# Look for an init script on the microSD card.
-#
-# To prevent automatic startup in the current flight mode,
-# the script should set MODE to some other value.
-#
-if [ -f /fs/microsd/etc/rc ]
-then
- echo "[init] reading /fs/microsd/etc/rc"
- sh /fs/microsd/etc/rc
-fi
-# Also consider rc.txt files
-if [ -f /fs/microsd/etc/rc.txt ]
-then
- echo "[init] reading /fs/microsd/etc/rc.txt"
- sh /fs/microsd/etc/rc.txt
-fi
-
-#
-# Check for USB host
-#
-if [ $USB != autoconnect ]
-then
- echo "[init] not connecting USB"
-else
- if sercon
- then
- echo "[init] USB interface connected"
- else
- echo "[init] No USB connected"
- fi
-fi
-
-#
-# If we are still in flight mode, work out what airframe
-# configuration we have and start up accordingly.
-#
-if [ $MODE != autostart ]
-then
- echo "[init] automatic startup cancelled by user script"
-else
- echo "[init] detecting attached hardware..."
-
- #
- # Assume that we are PX4FMU in standalone mode
- #
- set BOARD PX4FMU
-
- #
- # Are we attached to a PX4IOAR (AR.Drone carrier board)?
- #
- if boardinfo test name PX4IOAR
- then
- set BOARD PX4IOAR
- if [ -f /etc/init.d/rc.PX4IOAR ]
- then
- echo "[init] reading /etc/init.d/rc.PX4IOAR"
- usleep 500
- sh /etc/init.d/rc.PX4IOAR
- fi
- else
- echo "[init] PX4IOAR not detected"
- fi
-
- #
- # Are we attached to a PX4IO?
- #
- if boardinfo test name PX4IO
- then
- set BOARD PX4IO
- if [ -f /etc/init.d/rc.PX4IO ]
- then
- echo "[init] reading /etc/init.d/rc.PX4IO"
- usleep 500
- sh /etc/init.d/rc.PX4IO
- fi
- else
- echo "[init] PX4IO not detected"
- fi
-
- #
- # Looks like we are stand-alone
- #
- if [ $BOARD == PX4FMU ]
- then
- echo "[init] no expansion board detected"
- if [ -f /etc/init.d/rc.standalone ]
- then
- echo "[init] reading /etc/init.d/rc.standalone"
- sh /etc/init.d/rc.standalone
- fi
- fi
-
- #
- # We may not reach here if the airframe-specific script exits the shell.
- #
- echo "[init] startup done."
-fi