-
Notifications
You must be signed in to change notification settings - Fork 13.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pixhawk/PX4FMUv2 startup without external mag fails #9061
Comments
Check current Master (IMHO the above is not current Master), since there was a Fix for SPI Bus Reset, which fixes the LSM303D not found after a Soft Reboot (Warm Start): #8992 |
The "above" (63121b7) is the current master as of right now, and the issue unfortunately persists. |
Tested on 2 different Pixhawk units during ~10 hard-reboots, worked every time. Thanks @dagar for the quick fix! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Issue:
On Pixhawk with rev. 3 microprocessor (i.e. compiled via px4fmu-v3_default), current master firmware (63121b7) and stock startup script (rcS with airframe "standard plane" / Autostart ID 2100), bootup without an external magnetometer does not work because lsm303d fails. The system is a 64bit Ubuntu 16.10LTS. The exact log output for the configuration is:
Steps to reproduce the problem:
However, when doing a soft reboot (via nsh
reboot
command), both sensors start up correctly!Questions:
I know that it is preferred to use an external mag, but why is lsm303d completely disabled in nuttx_px4fmu-v3_default.cmake ? And why does it not start after a power cycle (the pixhawks were supplied via either an external power supply or the USB port, but the issue remained the same) although it does start after nsh's
reboot?
Notes:
This was tested on 3 different Pixhawks, all with revision 3 microprocessors and thus 2MB flash (on the PCB, these are just marked as "PX4FMU 2.4"). Same issue on all of them. However, on a fourth Pixhawk (which also has a rev. 3 microprocessor) this works every time (PCB mark is "PX4FMU 2.4.6", could be an mRo Pixhawk)! Is this a known problem of some hardware versions of Pixhawk?
@dagar @ASM3
The text was updated successfully, but these errors were encountered: