dark0707
/
px4-firmware
forked from Archive/PX4-Autopilot
1
0
Fork 0
Code Pull Requests Activity

Hotfix: Identified mavlink issue source, workaround, working on a fix

This commit is contained in:
Lorenz Meier 2013-09-03 22:45:33 +02:00
parent b5ec359c79
commit 175020cb5b
2 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ROMFS/px4fmu_common/init.d/rcS
View File

@ -63,8 +63,6 @@ then
if sercon if sercon
then then
echo "USB connected" echo "USB connected"
sleep 3
mavlink start -d /dev/ttyACM0 -b 230400
fi fi
# #
@ -104,7 +102,7 @@ then
fi fi
# Try to get an USB console # Try to get an USB console
#nshterm /dev/ttyACM0 & nshterm /dev/ttyACM0 &
# #
# Upgrade PX4IO firmware # Upgrade PX4IO firmware

2
src/modules/mavlink/mavlink.c
View File

@ -739,7 +739,7 @@ int mavlink_thread_main(int argc, char *argv[])
tcsetattr(uart, TCSANOW, &uart_config_original); tcsetattr(uart, TCSANOW, &uart_config_original);
/* destroy log buffer */ /* destroy log buffer */
mavlink_logbuffer_destroy(&lb); //mavlink_logbuffer_destroy(&lb);
thread_running = false; thread_running = false;