PX4-Autopilot icon indicating copy to clipboard operation
PX4-Autopilot copied to clipboard

Published 20 hours ago • verified publisher icon PX4

[Bug] PIXHAWK6X-RT generates HARD FAULT

Open muramura opened this issue 1 year ago • 16 comments

Describe the bug

I purchased two PIXHAWK6X-RT from HOLYBRO. I connected the QGC to check the operation. One of them generates a HARD FAULT in untimed. The other one generates a HARD FAULT.

I believe it is an initial failure of the FC.

To Reproduce

  1. launch QGC
  2. Connect PIXHAWK6X-RT to your PC.
  3. Connect for more than 30 minutes.

Expected behavior

Restart when a HARD FAULT occurs.

Screenshot / Media

No response

Flight Log

HARD FAULT https://review.px4.io/plot_app?log=25dad990-4315-43bf-8021-e79b4d47065c

NOT HARD FAULT https://review.px4.io/plot_app?log=8f3832c5-2f10-47c0-aa08-3aebe1411b61

Software Version

V1.15.0alpha

Flight controller

PIXHAWK6X-RT

Vehicle type

Multicopter

How are the different components wired up (including port information)

No response

Additional context

No response

muramura avatar Jan 21 '24 02:01 muramura

@davids5 @PetervdPerk-NXP @dk7xe Any idea what can be causing this?

vincentpoont2 avatar Jan 23 '24 19:01 vincentpoont2

@muramura Please test current main.

davids5 avatar Jan 25 '24 11:01 davids5

@muramura your logs show month old code Dec 22 2023 11:18:10.

HW arch: PX4_FMU_V6XRT
HW type: V6XRT000000
HW version: 0x000
HW revision: 0x000
PX4 git-hash: 6be8cbe43966d57630e6743e163307c216444be7
PX4 version: 1.15.0 40 (17760320)
PX4 git-branch: main
OS: NuttX
OS version: Release 11.0.0 (184549631)
OS git-hash: 1e3aaefc60a18838dc696e8f0f335d8c989f35cc
Build datetime: Dec 22 2023 11:18:10

From @PetervdPerk-NXP today.

I just ran commit 9da162243600164558bda1941d6143bc4ab5babb on V6X-RT with Holybro baseboard and T1 RC02 baseboard with SIH and QGC for 30+ minutes without crashes.

Please run today's main.

davids5 avatar Jan 25 '24 14:01 davids5

I uploaded the latest MAIN to PIXHAWK6X-RT where HARD FAULT occurs. A HARD FAULT has occurred.

Can this FC be determined to be a hardware failure?

https://review.px4.io/plot_app?log=d248f3e0-1d98-4b57-a354-6fa14c0876f6

muramura avatar Jan 25 '24 15:01 muramura

@muramura What is connected to the Setup? A picture would help.

davids5 avatar Jan 25 '24 15:01 davids5

@davids5 san.

I am connecting PIXHAWK6X-RT alone to my PC. PIXHAWK6X-RT is only connected to a PC.

PIXHAWK6X-RT<-(USB)->PC(UBUNTU, QGC)

muramura avatar Jan 25 '24 15:01 muramura

@muramura I think it could be related to SD card corruption. Could you swap the sd cards from both boards and see if the crash moves over to the other FMU?

PetervdPerk-NXP avatar Jan 26 '24 12:01 PetervdPerk-NXP

@PetervdPerk-NXP san.

I put the MICRO SD card of the PIXHAWK6X-RT, which does not generate a HARD FAULT, into the PIXHAWK6X-RT, which does.

The result was that a HARD FAULT occurred.

Log: https://review.px4.io/plot_app?log=feccc2c9-ff17-4416-827c-d106e7104bad

muramura avatar Jan 26 '24 14:01 muramura

Okay I think I've might found a procedure to get your PIXHAWK6X-RT into a correct state.

  1. Remove the SD card
  2. Startup PIXHAWK6X-RT
  3. Open up a nsh console and type mtd erase
  4. Format the SD card
  5. Re-insert the SD card

PetervdPerk-NXP avatar Jan 26 '24 17:01 PetervdPerk-NXP

@PetervdPerk-NXP san.

I have implemented the procedure.

The result was a HARD FAULT occurred.

https://review.px4.io/plot_app?log=95af7a19-74c2-4bfe-93bb-cea90b22391b

muramura avatar Jan 26 '24 18:01 muramura

@PetervdPerk-NXP san.

I put the MICRO SD card of the PIXHAWK6X-RT, which does not generate a HARD FAULT, into the PIXHAWK6X-RT, which does.

The result was that a HARD FAULT occurred.

Log: https://review.px4.io/plot_app?log=feccc2c9-ff17-4416-827c-d106e7104bad

@muramura , you are saying you have two Pixhawk 6x-RT that uses the same FW and setup, and only one of them have hardfault. The other one is working without issue, is that correct?

vincentpoont2 avatar Jan 30 '24 06:01 vincentpoont2

Dear HOLYBRO STAFF

Yes, that is correct. One does not experience a single HARD FAULT.

2024年1月30日(火) 15:15 Vincent Poon @.***>:

@PetervdPerk-NXP https://github.com/PetervdPerk-NXP san.

I put the MICRO SD card of the PIXHAWK6X-RT, which does not generate a HARD FAULT, into the PIXHAWK6X-RT, which does.

The result was that a HARD FAULT occurred.

Log: https://review.px4.io/plot_app?log=feccc2c9-ff17-4416-827c-d106e7104bad

@muramura https://github.com/muramura , you are saying you have two Pixhawk 6x-RT, and only one of them have hardfault. The other one is working without issue, is that correct?

— Reply to this email directly, view it on GitHub https://github.com/PX4/PX4-Autopilot/issues/22660#issuecomment-1916148475, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE5YMSXW7UWXBVDTO7DK3LYRCFW7AVCNFSM6AAAAABCDUE75CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJWGE2DQNBXGU . You are receiving this because you were mentioned.Message ID: @.***>

muramura avatar Jan 30 '24 06:01 muramura

I guess this is the same https://github.com/PX4/PX4-Autopilot/issues/22610 ?

dk7xe avatar Feb 06 '24 06:02 dk7xe

@muramura - Please test current main.

davids5 avatar Feb 06 '24 13:02 davids5

I installed the master MAIN. The result was not resolved. HARD FAULT occurs PIXHAWK6X-RT generates HARD FAULT. PIXHAWK6X-RT that does not generate a HARD FAULT does not generate a HARD FAULT.

muramura avatar Feb 06 '24 22:02 muramura

I purchased a third PIXHAWK6X-RT. I let it heat run on its own for over an hour. This PIXHAWK6X-RT did not cause a HARD FAULT.

I was convinced. The PIXHAWK6X-RT that generates a HARD FAULT is a hard defect.

https://review.px4.io/plot_app?log=865c086b-5ea4-4b12-97c2-931e5f04545e

muramura avatar Feb 10 '24 01:02 muramura