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.

Sign up for GitHub

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

Jump to bottom

test rack CUAV v5 nano icm20689 persistent transfer errors #14644

Closed
dagar opened this issue Apr 11, 2020 · 2 comments
Closed

test rack CUAV v5 nano icm20689 persistent transfer errors #14644

dagar opened this issue Apr 11, 2020 · 2 comments
Assignees
@dagar
Labels
bug Drivers 🔧 Sensors, Actuators, etc
Milestone
Release v1.11.0

Comments

@dagar
Copy link
Member

dagar commented Apr 11, 2020 •
edited
Loading

The test rack's CUAV v5 nano icm20689 IMU appears to be getting stuck with near 100% transfer errors. While in this state the other sensors on the same bus (bmi055 and icm20602) are in good health.

http://ci.px4.io:8080/blue/organizations/jenkins/PX4_misc%2FFirmware-hardware/detail/master/1678/pipeline/586

Screen Shot 2020-04-11 at 12 47 58 PM

Several other boards on the test rack with the icm20689 (several other fmu-v5s, holybro durandal) do not exhibit this problem over many test runs.

TODO

  • is the problem with this particular unit?
  • does lowering the SPI bus speed help?
  • should the drivers self reset more aggressively (eg 1000+ consecutive failures)
@dagar dagar added bug Drivers 🔧 Sensors, Actuators, etc labels Apr 11, 2020
@dagar dagar added this to the Release v1.11.0 milestone Apr 11, 2020
@dagar dagar self-assigned this Apr 11, 2020
@dagar dagar changed the title CUAV v5 nano icm20689 transfer errors test rack CUAV v5 nano icm20689 persistent transfer errors Apr 11, 2020
@dagar dagar mentioned this issue Apr 11, 2020
Closed
@dagar
Copy link
Member Author

dagar commented Apr 11, 2020 •
edited
Loading

More examples.
http://ci.px4.io:8080/blue/organizations/jenkins/PX4_misc%2FFirmware-hardware/detail/pr-fmu_rename/1/pipeline/827

Unable to reproduce on CUAV v5+ (or pixhawk 4).

dagar added a commit that referenced this issue Apr 11, 2020
@dagar
icm20689: track consecutive failures and trigger reset
25ab285 
 - fixes #14644
dagar added a commit that referenced this issue Apr 15, 2020
@dagar
icm20689: track consecutive failures and trigger reset
17cad4f 
 - fixes #14644
@dagar dagar mentioned this issue Jun 3, 2020
Merged
@dagar
Copy link
Member Author

dagar commented Jun 6, 2020

Fixed in #15004.

@dagar dagar closed this as completed Jun 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dagar dagar

Labels
bug Drivers 🔧 Sensors, Actuators, etc
Projects
None yet
Milestone
Release v1.11.0
Development

No branches or pull requests
1 participant
@dagar