-
Notifications
You must be signed in to change notification settings - Fork 15k
Open
Description
Describe the bug
I encountered a bus error while writing logs on a PX4 running on a Raspberry Pi 3B.
I'm running PX4 on the Raspberry Pi, and the simulation environment is running on an x86 host.
The startup command is:
./bin/px4_org -s px4_hil_complated.config
To Reproduce
No response
Expected behavior
No response
Screenshot / Media
No response
Flight Log
Below are the detailed runtime information.
px4 starting.
INFO [px4] startup script: /bin/sh px4_hil_complated.config 0
HW arch: EMLID_NAVIO2
PX4 git-hash: 93eef0c78719a9ac972d46593262c76c978ed3c4
PX4 version: 1.15.1 0 (17760512)
OS: Linux
OS version: Release 5.10.11 (84544511)
Build datetime: Aug 2 2025 16:44:24
Build uri: localhost
Build variant: default
Toolchain: Clang/LLVM, Clang 16.0.0 (https://github.com/llvm/llvm-project.git 08d094a0e457360ad8b94b017d2dc277e697ca76)
PX4GUID: 100449495052303030443030303030303030
UNKNOWN MCU
INFO [param] selected parameter default file ./parameters.bson
INFO [param] importing from './parameters.bson'
INFO [parameters] BSON document size 38 bytes, decoded 38 bytes (INT32:2, FLOAT:0)
MAV_TYPE: curr: 0 -> new: 2
Board defaults: ./etc/init.d/rc.board_defaults
Loading HIL airframe: ./etc/init.d/airframes/1001_rc_quad_x.hil
ERROR [param] Parameter UAVCAN_ENABLE not found.
INFO [dataman] data manager file './dataman' size is 7872608 bytes
px4_hil_complated.config: 153: px4_hil_complated.config: px4io: not found
INFO [commander] LED: open /dev/led0 failed (22)
WARN [health_and_arming_checks] Too many arming check events (1, 14 > 14). Not reporting all
WARN [health_and_arming_checks] Preflight Fail: Accel Sensor 0 missing
WARN [health_and_arming_checks] Preflight Fail: barometer 0 missing
WARN [health_and_arming_checks] Preflight Fail: No CPU load information
WARN [health_and_arming_checks] Preflight Fail: ekf2 missing data
WARN [health_and_arming_checks] Preflight Fail: Gyro Sensor 0 missing
WARN [health_and_arming_checks] Preflight Fail: Compass Sensor 0 missing
ERROR [param] Parameter GPS_1_CONFIG not found.
INFO [mavlink] mode: Normal, data rate: 1000000 B/s on udp port 14550 remote port 14577
INFO [mavlink] using network interface eth0, IP: 192.168.1.103
INFO [mavlink] with netmask: 255.255.255.0
INFO [mavlink] and broadcast IP: 192.168.1.255
INFO [mavlink] mode: Normal, data rate: 1000000 B/s on udp port 14551 remote port 14552
INFO [mavlink] using network interface eth0, IP: 192.168.1.103
INFO [mavlink] with netmask: 255.255.255.0
INFO [mavlink] and broadcast IP: 192.168.1.255
INFO [mavlink] mode: Normal, data rate: 1000000 B/s on udp port 14554 remote port 14553
INFO [mavlink] using network interface eth0, IP: 192.168.1.103
INFO [mavlink] with netmask: 255.255.255.0
INFO [mavlink] and broadcast IP: 192.168.1.255
INFO [rc_input] valid device required
ERROR [rc_input] Task start failed (-1)
px4_hil_complated.config: 323: px4_hil_complated.config: cdcacm_autostart: not found
px4_hil_complated.config: 325: px4_hil_complated.config: sercon: not found
Starting MAVLink on /dev/ttyACM0
ERROR: /dev/ttyACM0 does not exist, cannot start MAVLink.
INFO [logger] logger started (mode=all)
INFO [px4] Startup script returned successfully
pxh> WARN [health_and_arming_checks] Too many arming check events (1, 14 > 14). Not reporting all
WARN [health_and_arming_checks] Preflight Fail: Accel Sensor 0 missing
WARN [health_and_arming_checks] Preflight Fail: barometer 0 missing
WARN [health_and_arming_checks] Preflight Fail: ekf2 missing data
WARN [health_and_arming_checks] Preflight Fail: Gyro Sensor 0 missing
WARN [health_and_arming_checks] Preflight Fail: Compass Sensor 0 missing
INFO [mavlink] partner IP: 192.168.1.100
WARN [health_and_arming_checks] Preflight Fail: ekf2 missing data
reset
reset
start fake position fusion
reset fake position fusion
reset position to last known (0.000, 0.000)
reset velocity to zero
start fake height fusion
reset fake height fusion
reset height to last known (0.000)
350254899: EKF aligned, (unknown hgt, IMU buf: 20, OBS buf: 20)
starting mag fusion, resetting states
reset mag heading -0.000 -> -0.054 rad (bias:[0.000, 0.000, 0.000], declination:0.0)
initializing mag I [0.215, 0.000, 0.430], mag B [0.000, 0.000, 0.000]
starting baro height fusion
fallback to secondary height reference
stop fake height fusion
WARN [health_and_arming_checks] Preflight: GPS fix too low
WARN [health_and_arming_checks] Preflight Fail: CPU load too high: 146.0%
WARN [health_and_arming_checks] Preflight: GPS fix too low
pxh> INFO [gyro_calibration] gyro 0 (1310988) updating offsets [0.000, 0.000, 0.000]->[0.000, -0.000, 0.000] 0.0 WARN [health_and_arming_checks] Preflight Fail: CPU load too high: 144.0%
WARN [health_and_arming_checks] Preflight: GPS fix too low
pxh> loggerWARN [health_and_arming_checks] Preflight Fail: CPU load too high: 156.0%
pxh> logger on
pxh> INFO [logger] Start file log (type: full)
INFO [logger] [logger] ./log/2026-01-14/13_46_34.ulg
INFO [logger] Opened full log file: ./log/2026-01-14/13_46_34.ulg
Bus error
When I try to enable logging, I get a "bus error" error.
Software Version
1.15
Flight controller
No response
Vehicle type
copter
How are the different components wired up (including port information)
No response
Additional context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels