I try to install ardupilot firmware version above 3.5.3 but unfortunately after installation when I do the calibration and try to run the drone also immediately after the arm stops working.
In version 3.5.3 everything works properly but this version doesn't have my leader support. When I install any version of nuttx for example 1.9.2 everything works fine.
I tried all available versions of ardupilot from 3.5.3 and above and none of them works.
After trying to run with ardupilot version 3.6.10 I can't even read the firmware version:
BIOS_VERSION = Aero-01.00.16
OS_VERSION = Ubuntu 16.04.6 LTS"
AIRMAP_VERSION = unknown
FPGA_VERSION = 0xc2
AeroFC firmware version = unknown
once it's activated:
journalctl -u mavlink-router
I receive:
at 05 12:42:55 p.m. Cherry-Trail mavlink-routerd[1444]: Open UDP [5] 83.220.114.114.14:14550
at 05 12:42:55 p.m., Cherry-Trail mavlink-routerd[1444]: Open UDP [6] 192.168.7.255:14550
at 05 12:42:55 p.m., Cherry-Trail mavlink-routerd[1444]: Open UDP [7] 0.0.0.0.0:80550 *
at 05 12:42:55 p.m., Cherry-Trail mavlink-routerd[1444]: Open UART [8] /dev/ttyS1 *
at 05 12:42:55 p.m., Cherry-Trail mavlink-routerd[1444]: UART [8] speed = 921600
at 05 12:42:55 p.m., Cherry-Trail mavlink-routerd[1444]: Open TCP [10] 0.0.0.0.0:5760 *
at 05 12:42:55 p.m., Cherry-Trail mavlink-routerd[1444]: Baudrate 921600 responded, keeping it
at 05 12:42:55 p.m., Cherry-Trail mavlink-routerd[1444]: Logging target system_id=1 on 00182-2019-08-05_12-42-55.bin
05 12:42:42:56 Cherry-CherryTrail systemd[1]: mavlink-router.service: Main process exited, code=dumped, status=11/SEGV
05 12:42:42:56 Cherry-CherryTrail systemd[1]: mavlink-router.service: Unit entered failed state.
s 05 12:42:56 Cherry-CherryTrail systemd[1]: mavlink-router.service: Failed with result 'core-dump'.
sie 05 12:42:42:56 CherryTrail systemd[1]: mavlink-router.service: Service hold-off time over, scheduling restart.
05 12:42:42:56 CherryTrail systemd[1]: Stopped MAVLink Router.
05 12:42:42:56 Cherry-Trail systemd[1]: mavlink-router.service: Start request repeated too quickly.
05 12:42:42:56 Cherry-CherryTrail systemd[1]: Failed to start MAVLink Router.
05 12:42:42:56 Cherry-CherryTrail systemd[1]: mavlink-router.service: Unit entered failed state.
05 12:42:56 Cherry-CherryTrail systemd[1]: mavlink-router.service: Failed with result 'start-limit-hit'.
System reboot does not help
QgroundControl can't connect to a drone.
It only helps to turn the drone off and on completely.
The power supply system has an adequate current capacity.
Link Copied
For more complete information about compiler optimizations, see our Optimization Notice.