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

OSDK 3.3 - Telemetry sample crashes with "Bus error" #135

Closed
hhackbarth opened this issue Jun 26, 2017 · 2 comments
Closed

OSDK 3.3 - Telemetry sample crashes with "Bus error" #135

hhackbarth opened this issue Jun 26, 2017 · 2 comments

Comments

@hhackbarth
Copy link

hhackbarth commented Jun 26, 2017

Testing the telemetry sample on a RasPi Zero.

Everything seems to work fine until the loop starts. When a value is retrieved with
vehicle->subscribe->getValue<TOPIC...>()
the program crashes after reporting "Bus error" to the console.

Clean termination with removePackage is not carried out. If the program is started a second time, after initialization it immediately reports "ERROR/1 @ extractOnePackage, L364: Package does not have a valid DataBuffer".

I tried to reduce the amount of data by only subscribing to package 0 and 1 with reduced frequency. This did not help. Also reducing the output frequencies in the SDK configuration did not help.

@rohitsantdji
Copy link

The general opinion on various forums (example 1, example 2) is that variants of the Raspberry Pi do not like unaligned memory access (packed structs), which are used quite frequently in the DJI OSDK.

You could try going in to dji_telemetry.hpp and commenting out the #pragma packing, though we have not tested the SDK using this configuration so it is unexplored territory.

@hhackbarth
Copy link
Author

Thank you for your quick comment!

I tested it with commenting out the #pragma packing in dji_telemetry.hpp:
It does'nt crash anymore but now it shows weird figures for the latitude, longitude and altitude.

Looks like the telemetry cannot be used on RasPi (tested with Pi Zero and Pi 2 B).

pcler pushed a commit that referenced this issue May 7, 2020
… develop

* commit '9b66323cee0c125766dd8ff0c562ef6047e81a54':
  fix:fix readme for 4.0
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

No branches or pull requests

2 participants