Skip to content
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

[DNM] Testing CI hardfault on NXP #14097

Closed
wants to merge 49 commits into from
Closed

Conversation

BazookaJoe1900
Copy link
Member

this pr is not for merge and is just for testing hardfault that found on #14031.
the hardfault exist from commit ~0c9161f004531b5c8a342ca2a075fbbfd97823ae but not in ~7d295fd99d274e7d4248241ce99f4b11edfc400b.
Because I don't have the NXP board, I am using the CI to run the tests.

BazookaJoe1900 and others added 29 commits February 3, 2020 20:02
…#13761)

 - rename of flag in position sp: from allow_weather_vane to disable_weather_vane
 - flag now doesn't have to be set for all auto modes, meaning that weather vane is also active outside of mission
 - flag is set before front transition to align with wp, and unset after alignment is over

Signed-off-by: Silvan Fuhrer <[email protected]>
* Publish I2C battery data as battery_status
* Mavlink: subscribe to airspeed_validated instead of airspeed topic

	This e.g. changes the way QGC displays the airspeed in case of an
	airspeed failure (0 instead of the last valid airspeed). It will
	always display the airspeed that's used currently in the control
	modules.

* FW land detector: move to subscribe to airspeed_validated instead of airspeed topic
	- the land detector checks further if the airspeed is NAN, in which case
	it sets the airspeed to 0 (min groundspeed, vz  and accel checks still
	have to pass.

* Fixed-wing land detector use airspeed_vaidated: addressed review comments
	- replaced ternary by conditional
	- set airspeed to 0 if airspeed_validated stops publishing

Signed-off-by: Silvan Fuhrer <[email protected]>
    - matrix in PX4/Firmware (8224403): PX4/PX4-Matrix@e81483a
    - matrix current upstream: PX4/PX4-Matrix@d18be0d
    - Changes: PX4/PX4-Matrix@e81483a...d18be0d

    d18be0d 2019-12-28 kritz - Fix AngleAxis constructors (#117)
 - wait_to_exist() shouldn't depend on lockstep (px4_usleep)
@julianoes julianoes changed the title [DNM] Testing CI haradrfault on NXP [DNM] Testing CI hardfault on NXP Feb 4, 2020
@BazookaJoe1900
Copy link
Member Author

BazookaJoe1900 commented Feb 14, 2020

@dagar I am abit stack here because I don't have the fmuk66 hardware (and not really using it...)
is there someone that does use this board that you can point the hardfault issue to?

I am still working on how to read the hardware test output to identify errors such hardfaults

@dagar
Copy link
Member

dagar commented Feb 22, 2020

Do you have any additional evidence that points to this hardware or not specifically?

Have you verified all the stacks have a healthy margin?

@BazookaJoe1900
Copy link
Member Author

@dagar I have problem to check the fmuk66, because I don't have this hardware. and basiclly I need to do the test by this hardware check.
I Try on this PR to make the hardware check to fail on hardfault.
If it just stack issue, it will be easy to check and fix. but it might be much more complex

@BazookaJoe1900
Copy link
Member Author

closing this PR, its better in this stage to find hardfault is better to do with real HW, and not by CI

@BazookaJoe1900 BazookaJoe1900 deleted the pr-test_nxp_hardfault branch February 28, 2020 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants