You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: 5f3e883f2c

main

master

my1.12

my1.12-iic

pr-sensor-distance

release/1.12

sbg

tf-1.12

tf-1.12-print_test

tf-iic2uart

tf_driver-1.12

tf_i2c-1.12

tf_i2c_collis_pre

v1.13.0-BW

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '5f3e883f2c'

${ noResults }

px4_autopilot/ROMFS

History

Lorenz Meier aacbc04730 PX4IO: Robustify upgrade process ... These changes remove the two code paths to updates (forceupdate and update) and try to reboot and bootload IO independent of its state, wether it is in bootloader mode already, safety switch is off or if it is in "nominal state" (running and safety on). This ensures that there are no conditions where user error or boot sequence can prevent a successful upgrade. The only state where an upgrade will not be done is if the system is fully armed.		4 years ago
..
cannode	uORB move to PX4 platform layer	4 years ago
px4fmu_common	PX4IO: Robustify upgrade process	4 years ago
px4fmu_test	PX4IO: Robustify upgrade process	4 years ago
CMakeLists.txt	ROMFS:Bake in UAVCAN FW with builds that end in _uavcan	4 years ago