99aae8b891
NuttX use toolchain math.h and avoid empty drivers/Kconfig
2019-11-16 11:43:42 +01:00
00d00fdca9
drivers: heater: fix module build and startup
...
- Startup was broken due to unnecessary cyclic check probably introduced during transition to work_queues
- Module never used other than on Teal One which had a hacky heater input GPIO, this enables usage on general boards
drivers: heater: reduce verbosity and simplify commandline options
- We prefer the linux way of only reporting errors and staying quiet when everything is functioning as designed
- Most of the commandline options just read out the values of the system parameters, and one can just check the parameter values directly.
sensor_params: make thermal control parameters system parameters
heater_params: make thermal control parameters system parameters
drivers: heater: remove pin control hacks
- px4_arch_configgpio(GPIO_HEATER_OUTPUT) directly inits the heater pin to OFF, and as a PUSHPULL (TTL totem pole) OUTPUT
drivers: heater: set default device ID to 0
2019-11-16 11:43:42 +01:00
d965b928f8
px4iofirmware: convert atomic macro into methods
...
Reduces flash size by 744 bytes.
CPU (loop time) is not affected.
2019-11-16 11:43:42 +01:00
0f2a7ad2b7
bl_update:STM32H7 use AIXRAM
2019-11-16 11:43:42 +01:00
645b6c3fbc
bl_update:STM32H7 use 128K
2019-11-16 11:43:42 +01:00
e847698c9f
PX4 System changes Supporting STM32H7
...
stm32:ToneAlarmInterfacePWM TIM15-TIM17 have a BDTR Register
common:board_crashdump Add H7 support
stm32/board_mcu_version:Support H7
PX4 ADC:Use 32 interface and resoution abstraction
Added PX4 stm32h7 ADC driver
stm32h7:adc fix ADC ready check
fmu: handle BOARD_HAS_PWM==5
cmake: improve error handling for NuttX olddefconfig failures
WorkQueueManager:Quiet loadmon stack warning
camera_trigger:GPIO support < 6 GPIO
Adjust stack sizes (under hw stack check)
PX4 System changes Supporting STM32H7 PX4IO Driver
aerotenna_ocpoc:ADC add px4_arch_adc_dn_fullcount
init.cmake:Track Upstream change needing Make.def at config time
PX4 System changes Supporting STM32H7
NuttX CMakeLists.txt Track upstream changes
Common board_crashdump add header and px4 config
NuttX simplify callinb make libapps
Use UINT32_MAX for error return
drivers:uavcannode NuttX chip is now hardware
drivers:uavcanesc NuttX chip is now hardware
px4io:Avoid Race on AP to PX4 IO upgrade
2019-11-16 11:43:42 +01:00
36a75b79a4
uavcan:Changes to support Nuttx 7.31+
...
libuavcan:Update with Kinetis NuttX 8.1+ support
Traking master uavcan changes
2019-11-16 11:43:42 +01:00
11b1573961
mpu9250: cleanup main
2019-11-15 10:18:41 -05:00
cc41e5be20
mavlink: stream battery status fields ( #13420 )
...
* Implement battery status "charge state" on mavlink battery status message
2019-11-15 09:25:30 -05:00
452657face
hmc5883: build on linux and qurt
2019-11-14 21:02:52 -05:00
9364393e9d
mavlink_receiver: Reject own autopilot messages for battery status.
...
Signed-off-by: Claudio Micheli <claudio@auterion.com >
2019-11-14 22:20:22 +01:00
6369ae858a
Update submodule matrix to latest Wed Nov 13 22:07:30 UTC 2019
...
- matrix in PX4/Firmware (d3184c866c3012105c8950a9f6652a9722fa3296): https://github.com/PX4/Matrix/commit/93d42947b612733d2bd05e66ae093ada3e35ba12
- matrix current upstream: https://github.com/PX4/Matrix/commit/cd185c995b6b28c12e06d20a2743a94bd68be7c2
- Changes: https://github.com/PX4/Matrix/compare/93d42947b612733d2bd05e66ae093ada3e35ba12...cd185c995b6b28c12e06d20a2743a94bd68be7c2
cd185c9#107 )
38e966c#105 )
2019-11-13 19:07:24 -05:00
99a7491cde
bmp280: build on linux and qurt
2019-11-13 15:16:24 -05:00
bcfa2eecd8
ms5611: build on linux (navio2)
2019-11-13 13:01:00 -05:00
7996ee496c
lib: name folders consistently
2019-11-13 09:29:21 -05:00
c5520cbaca
mpu9250: start building "NuttX" driver for Linux and QuRT
2019-11-13 09:21:02 -05:00
6bd4273b9c
mavlink: handle cellular_status messages for logging
2019-11-13 09:19:02 -05:00
675af4f5f9
uavcan_kinetis: fix flexcan code style
...
* flexcan: fix code style
* flexcan: exclude from style check to avoid that a different version of astyle breaks indentation again
2019-11-12 20:50:54 -05:00
9183f44243
px4_fmu-v4: deprecate boscch pixracer variant and cleanup SPI devs
2019-11-12 11:18:57 -05:00
00a7ac013c
ak09916: fix mag spikes
...
This fixes spuriously occuring mag spikes in the external mag of Here2.
The reason for the spikes was that the fact that the I2C registers were
not read out correctly as suggested in the datasheet.
Before we were reading out ST1, data, and ST2 in one pass and ignoring
the data ready bit (DRDY) in ST1. This meant that we could run into race
conditions where the data was not ready when we started reading and
being updated as the registers are read.
Instead, we need to check the read the ST1 register first to check the
data ready bit and then read the data and ST2 if the data is ready. By
reading ST2 we then trigger the next measurement in the chip.
2019-11-12 10:04:35 -05:00
035e81e084
ak09916: cleanup only
...
Note: the author name was removed because this file has almost no
resemblence with the code written by that author 4 years ago, has been
copied to new places, and was initially commited without author anyway.
Also, my opinion is that the version control system should take care of
attribution, and not outdated comments.
2019-11-12 10:04:35 -05:00
17a84a691f
mavlink_receiver: simplify and fix statustext.severity handling
2019-11-11 17:12:37 -05:00
f06a6ba898
set TC_ as 'system' parameters
2019-11-11 15:13:01 -05:00
1c4e854f93
cmake don't build param "c" files and remove param defines
...
- these aren't actual source code
2019-11-11 10:25:42 -05:00
4dfe3e199e
Update submodule matrix to latest Sat Nov 9 00:39:54 UTC 2019
...
- matrix in PX4/Firmware (c475bb84b7274d041065fc3fd673127ae2438f4d): https://github.com/PX4/Matrix/commit/9f464839510a2779b9418ffbc2303a31f155e851
- matrix current upstream: https://github.com/PX4/Matrix/commit/93d42947b612733d2bd05e66ae093ada3e35ba12
- Changes: https://github.com/PX4/Matrix/compare/9f464839510a2779b9418ffbc2303a31f155e851...93d42947b612733d2bd05e66ae093ada3e35ba12
93d4294#104 )
2019-11-09 00:51:44 -05:00
1fc85da4b0
Update submodule GPSDrivers to latest Fri Nov 8 12:40:32 UTC 2019
...
- GPSDrivers in PX4/Firmware (085bdd14b41ac3977d612a1cae27f111de7fe4fb): https://github.com/PX4/GpsDrivers/commit/011959b4dabc6edbc1b22f5e0fa42a62d137e993
- GPSDrivers current upstream: https://github.com/PX4/GpsDrivers/commit/085a85c48aafff6e388f8ce8d15c1371f8556a35
- Changes: https://github.com/PX4/GpsDrivers/compare/011959b4dabc6edbc1b22f5e0fa42a62d137e993...085a85c48aafff6e388f8ce8d15c1371f8556a35
085a85c 2019-10-15 Andreas Antener - sbf: invalidating gps position when invalid data is received We have encountered a case where do-not-use values were being reported in velocity fields without a corresponding error code or fix-type 0. This adds a check for known invalid data and sets the appropriate flags.
2019-11-08 09:43:53 -05:00
073298bc8e
batt_smbus: fix incorrect CLI description
2019-11-08 13:52:23 +01:00
b943bd72ab
commander: Added a parameter to control the timeout period for disarming after the kill switch is engaged. ( #13325 )
2019-11-07 10:03:59 -05:00
1896c758d0
[SQUASH ME] trivial style fix
2019-11-07 15:57:29 +01:00
3595941554
Reposition landing gear check so that it is not overwritten by setpoint operations.
2019-11-07 15:57:29 +01:00
b60a955501
ColPrev: No direction change if no obstacle ( #13398 )
...
* only change direction if in other bin
2019-11-07 14:21:12 +01:00
a5af1c8afc
batt_smbus: add missing PRINT_MODULE_USAGE_DEFAULT_COMMANDS()
2019-11-07 10:56:27 +01:00
f94236dcc9
batt_smbus: fix getopt arguments (-A does not have an argument)
2019-11-07 10:56:27 +01:00
ce1ae3fcb7
batt_smbus: exit/continue correctly when no device is on the bus
2019-11-07 10:56:27 +01:00
72e62a62cb
batt_smbus: make bus_options const and rename to smbus_bus_options
...
as it is a global name.
2019-11-07 10:56:27 +01:00
adad11f247
batt_smbus: remove unused defines
2019-11-07 10:56:27 +01:00
b487920cf4
fix batt_smbus: add bound checks when accessing argv
2019-11-07 10:56:27 +01:00
60f55a4fa1
fix batt_smbus: check if module running for custom_command
2019-11-07 10:56:27 +01:00
f63b55b219
fix batt_smbus: do not block the work queue while suspended
2019-11-07 10:56:27 +01:00
3f3304fefc
batt_smbus: variable init cleanup + remove unused declarations
2019-11-07 10:56:27 +01:00
32359168d6
smbus: fix invalid memory access in read_word()
...
read_word() expected 3 bytes (uint16_t + PEC byte), but was passed an
address to an uint16_t value.
write_word() is changed to be type-safe as well.
2019-11-07 10:56:27 +01:00
e772ddf012
motor_test: remove note about supported drivers
...
This is now supported by all main output drivers.
2019-11-07 10:40:03 +01:00
6622f04feb
uavcan drivers: update code style
...
Pure refactoring, just running 'make format'.
2019-11-07 10:40:03 +01:00
6049a95073
uavcan drivers: remove unused code for other OSs/bare metal
2019-11-07 10:40:03 +01:00
5dff065ec5
uavcan: move to work queue and use MixingOutput
...
Main UAVCAN protocol handling and ESC updates run on the same thread/wq as
before. There are 2 WorkItems for separate scheduling of the 2, so that
ESC updates run in sync with actuator_control updates. UAVCAN is scheduled
at a fixed rate of 3ms (previously the poll timeout) and on each UAVCAN
bus event.
This leads to roughly the same behavior as before. CPU & RAM usage are
pretty much the same (tested on Pixhawk 4).
Testing done: Motors still work (with feedback), param changes and a
UAVCAN optical flow sensor.
2019-11-07 10:40:03 +01:00
b7a480b45b
refactor uavcan: add stm32 and kinetis drivers directly
2019-11-07 10:40:03 +01:00
6854b14dd6
esc_report: remove unused fields to reduce message size
...
esc_setpoint in UAVCAN was just wrong, this is what it really is:
uint7 power_rating_pct # Instant demand factor in percent
(percent of maximum power); range 0% to 127%.
2019-11-07 10:40:03 +01:00
0db0981b1b
uavcan: remove actuator_direct (no publisher)
2019-11-07 10:40:03 +01:00
06f20ad892
sensors: ensure angular velocity publication on selected sensor update
2019-11-07 09:53:44 +01:00
60343cc168
mavlink: warning for actuator offboard & lockstep
...
Currently actuator offboard control interferes with SITL lockstep.
Therefore, the least we can do is to warn a user and inform them how to
workaround the issue.
2019-11-06 12:30:30 -05:00
Daniel Agar