startup: NuttX seems to free memory only AFTER the next command is issued, requiring us to give it some time to do memory management so it does not keep starting tasks on top of each other. May need some consideration on main startup script as well.

This commit is contained in:
Lorenz Meier
2014-05-15 08:17:31 +02:00
parent 4bc06381a9
commit 0655aeb7ec
+6
View File
@@ -6,11 +6,17 @@
mavlink start -r 10000 -d /dev/ttyACM0 mavlink start -r 10000 -d /dev/ttyACM0
# Enable a number of interesting streams we want via USB # Enable a number of interesting streams we want via USB
mavlink stream -d /dev/ttyACM0 -s NAMED_VALUE_FLOAT -r 10 mavlink stream -d /dev/ttyACM0 -s NAMED_VALUE_FLOAT -r 10
usleep 1000
mavlink stream -d /dev/ttyACM0 -s OPTICAL_FLOW -r 10 mavlink stream -d /dev/ttyACM0 -s OPTICAL_FLOW -r 10
usleep 1000
mavlink stream -d /dev/ttyACM0 -s VFR_HUD -r 20 mavlink stream -d /dev/ttyACM0 -s VFR_HUD -r 20
usleep 1000
mavlink stream -d /dev/ttyACM0 -s ATTITUDE -r 20 mavlink stream -d /dev/ttyACM0 -s ATTITUDE -r 20
usleep 1000
mavlink stream -d /dev/ttyACM0 -s ATTITUDE_CONTROLS -r 30 mavlink stream -d /dev/ttyACM0 -s ATTITUDE_CONTROLS -r 30
usleep 1000
mavlink stream -d /dev/ttyACM0 -s SERVO_OUTPUT_RAW_0 -r 20 mavlink stream -d /dev/ttyACM0 -s SERVO_OUTPUT_RAW_0 -r 20
usleep 1000
# Exit shell to make it available to MAVLink # Exit shell to make it available to MAVLink
exit exit