* NuttX cmake
* px4_macros:Pass the stringified predicate as second arg to static assert
CC_ASSERT mapes to the c++ static_assert or provides the same
funtionality for c via the other macros. The c++ static assert
takes 2 argumants the prdicate and a message. This fixes the
lacking second argument.
* Updated nuttx and apps submodule to upstream nuttx 7.21+==master
This is the latest uptake of upstream nuttx and apps.
* ROMFS generate with xxd instead of objcopy
* delete nuttx-patches
* NuttX update submodules to latest px4_nuttx-master
* fix nuttx apps and board dependency
* docker_run update to latest container 2017-08-29
* cmake ROMFS portable sed usage
* NuttX update submodules to latest px4_nuttx-master
The new upstream nuttx defconfig format is compressed. This
will not work well for board configs that are out of the
upstream NuttX tree.
The reconstitution step will not replace all the non default
settings. I.E. CONFIG_ARCH_BOARD_PX4xxxx and will remove
setting that are not defined from the config/KConfig. Like
CONFIG_ARCH_BOARD_PX4xxxx=y.
Also the configure script will fail if run without
and intervening make distclean
The only 2 steps from configure that re needed are
Copying the defconfig to .config and Make.defs
We are running out of flash space in AeroFC so a cleanup is necessary.
Tools not used in Aero RTF, INAV, fixed wing control, vtol control and
unused libs was removed.
before
$ size build_aerofc-v1_default/src/firmware/nuttx/firmware_nuttx
text data bss dec hex filename
956880 3524 14608 975012 ee0a4 firmware_nuttx
after
$ size build_aerofc-v1_default/src/firmware/nuttx/firmware_nuttx
text data bss dec hex filename
832200 3508 14616 850324 cf994 build_aerofc-v1_default/src/firmware/nuttx/firmware_nuttx
This commit changes old trone driver into a generic
TeraRanger driver that supports both TeraRanger One
and TeraRanger Evo.
As a part of the change a new parameter was created
SENS_EN_TRANGER that allows to specify the following
modes of operation:
0 - sensors disabled
1 - autodetect sensors
2 - use TeraRanger One rangefinder
3 - use TeraRanger Evo rangefinder
Signed-off-by: Mateusz Sadowski <msadowski90@gmail.com>
* updated to use rc driver from PX4, instead of from FC addons
* fixed format
* update per comments
* fix format
* fix format
* remove duplicated __PX4_QURT
inverted S.bus signal and fetch the data of each channel and publish it
2. Fix the bug of linux_pwm_out, when the protocol is pca9685,
after the init method is executed,the method of determining the return
value of init method is incorrect,this will cause the driver to fail
3. Add linux_sbus driver to other posix prefixes cmake files