search

tom-2015 / rpi-AR1100

Calibration program for the AR1100 on the Raspberry Pi
27 stars 22 forks source link

Segmentation Fault #4

Open Bishamon1987 opened 5 years ago

Bishamon1987 commented 5 years ago

Hello, I installed the whole thing like described in the readme. But i get this segmentation fault when i run sudo ./AR1100 -c 9 I cant figure out what im doing wrong. I use the latest Raspbian Stretch with desktop. I updated everything.

tom-2015 commented 5 years ago

What if you enable debugging?

make clean make DEBUG=1

Then install gdb (sudo apt-get install gdb) Run the program through gdb debugger: sudo gdb -ex=r --args AR1100 -c 9

gdb should show you information about which code line the segmentation error occurs.

Bishamon1987 commented 5 years ago

I will try this to night. Thanks! I keep you posted

Op za 6 jul. 2019 10:24 schreef Tom notifications@github.com:

What if you enable debugging?

make clean make DEBUG=1

Then install gdb (sudo apt-get install gdb) Run the program through gdb debugger: sudo gdb -ex=r --args AR1100 -c 9

gdb should show you information about which code line the segmentation error occurs.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tom-2015/rpi-AR1100/issues/4?email_source=notifications&email_token=AHGXD73JNT75E2QSPHLTVNLP6BJCPA5CNFSM4H42FKZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZKVBEA#issuecomment-508907664, or mute the thread https://github.com/notifications/unsubscribe-auth/AHGXD7YPD7SQF2R7VF6UAYTP6BJCPANCNFSM4H42FKZA .

ghost commented 5 years ago

Sorry, NOT he "right" answer as I didn't debug, but an FYI workaround:

Bizzarely I had this same issue today on Pi 3+ using "2019-06-20-raspbian-buster".

I worked around this by calibrating with a very old Pi and downloading 2017-07-05-raspbian-jessie. Worked like a charm, but used:

Bishamon1987 commented 5 years ago

Well, I have it running now. But I used the official ar1100 configuration utility on a Windows 7 virtual desktop on my MacBook pro. Used an HDMI to av converter on my cars 7" display. Calibrated it as a mouse. First my system was running ECG and worked as a mouse. When I ran it as X11 it changed the usage to touchscreen. For me it's working but the lower part of the screen isn't recognize as touchscreen I thing. Maybe the calibration didn't work perfectly... Thanks for the help anyway!

Op za 6 jul. 2019 14:45 schreef flcgit notifications@github.com:

Sorry, NOT he "right" answer as I didn't debug, but an FYI workaround:

Bizzarely I had this same issue today on Pi 3+ using "2019-06-20-raspbian-buster".

I worked around this by calibrating with a very old Pi and downloading 2017-07-05-raspbian-jessie. Worked like a charm, but used:

  • an external HDMI monitor right until the actual calibration command
  • needed a "apt-get update" before installing libusb-1.0-0-dev & libgtk2.0-dev (git, make & g++ were already installed)
  • Performed on cmd line (out of X11 GUI) most of the time until the calibration step); I had CPU load issues which hung the Pi a couple of times

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tom-2015/rpi-AR1100/issues/4?email_source=notifications&email_token=AHGXD72ESHW6335L7QI4D7TP6CHXNA5CNFSM4H42FKZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZKZAII#issuecomment-508923937, or mute the thread https://github.com/notifications/unsubscribe-auth/AHGXD74OV2J65R5XBFRSGA3P6CHXNANCNFSM4H42FKZA .

tom-2015 commented 5 years ago

Finally found some time and an AR1100 to look into this problem. I found there was a "return result" missing. The calibration is now working on my Raspberry Pi 3B+ and Raspbian buster.

Bishamon1987 commented 5 years ago

I'll try it ASAP since the calibration could be better