Segmentation Fault on Flight software with I2C Driver #798
-
|
Hi it's me again. I cross compile my code from ubuntu 18.04 to raspberry pi. The reference for programming and reading ADXL 345 is available here. I know I could have just use adxl 345 library but I can see myself working on an i2c device that might not have this kind of library available so I'm trying to stick to the generic software for better practice. The error log from R PI terminal is here
I have verified that i2c is open for my pi and I have a success on reading accelerometer data via python. I wonder if anyone here have had similar problem and can guide me to how to solve this. Thank you in advance! Hopefully it's not me accidentally deleting block driver or something again. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
I'd recommend running the F' application with gdb or collecting a core dump from the segfault so you can get the backtrace of the crash. A segmentation fault could be a lot of things, so figuring out where in the code the fault is occurring would probably help! As a tip, this sort of error can be caused by incorrect topology files, so double checking to make sure you have everything connected properly and initialized is a good first step as well. |
Beta Was this translation helpful? Give feedback.
-
|
Do you know which kind of standard ports an i2c driver has? It doesn't use modeler = true so I couldn't really see or double check which ports are used except from the custom made ones. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for recommend me using gdb. Turned out I used sscanf incorrectly so I changed the way to read the sensor data. Now I seem to be somewhat successful at opening, writing and reading something from i2c port. I still have to format the data correctly though. My repo is updated to the current work. This might not be a lot to give it back to you guys but I'm going to turn this into a i2c driver tutorial/documentation. i2c is not in a rpi demo so this might be something useful for the community. I should have this done by this weekend and will share it with you guys for some feedback. |
Beta Was this translation helpful? Give feedback.
I'd recommend running the F' application with gdb or collecting a core dump from the segfault so you can get the backtrace of the crash. A segmentation fault could be a lot of things, so figuring out where in the code the fault is occurring would probably help!
As a tip, this sort of error can be caused by incorrect topology files, so double checking to make sure you have everything connected properly and initialized is a good first step as well.