Double-check your device tree setup. The error "external abort on
non-linefetch" almost always means the underlying hardware is not
responding, typically because it's not been setup (taken out of reset,
clock enabled, etc) by the kernel.
On 9/13/2020 2:33 AM, Jacek Radzikowski wrote:
Hello,
Loading hal_arm335xQEP with loadrt causes rtapi_app to crash with bus error:
Sep 13 07:22:29 machinekit rtapi:0: 1:rtapi_app:5330:user signal 7 - 'Bus
error' received, dumping core (current dir=/home/machinekit)
Sep 13 07:22:29 machinekit kernel: [ 440.186026] Unhandled fault: external
abort on non-linefetch (0x1818) at 0xb6f041a8
Sep 13 07:22:29 machinekit kernel: [ 440.186041] pgd = bf066d95
Sep 13 07:22:29 machinekit kernel: [ 440.186045] [b6f041a8] *pgd=9c782831,
*pte=48300343, *ppte=48300833
Sep 13 07:22:29 machinekit rtapi:0: 1:rtapi_app:5330:user --- rtapi_app
backtrace: ---
Sep 13 07:22:29 machinekit rtapi:0: 1:rtapi_app:5330:user ERROR decoding
backtrace: no debug info in ELF executable (-1)
Sep 13 07:22:29 machinekit rtapi:0: 1:rtapi_app:5330:user ERROR decoding
backtrace: no debug info in ELF executable (-1)
Sep 13 07:22:29 machinekit rtapi:0: 1:rtapi_app:5330:user ERROR decoding
backtrace: no debug info in ELF executable (-1)
Sep 13 07:22:29 machinekit rtapi:0: 1:rtapi_app:5330:user ERROR decoding
backtrace: no debug info in ELF executable (-1)
Sep 13 07:22:29 machinekit rtapi:0: 1:rtapi_app:5330:user
--------------------
Sep 13 07:22:30 machinekit msgd:0: rtapi_app exit detected - scheduled
shutdown
Sep 13 07:22:32 machinekit msgd:0: msgd shutting down
I used the following commands to load the module:
$ halrun
msgd:0 stopped
rtapi:0 stopped
rtapi_msgd command: /usr/libexec/linuxcnc/rtapi_msgd --instance=0
--rtmsglevel=1 --usrmsglevel=1 --debug=1 --halsize=524288
rtapi_app command: /usr/libexec/linuxcnc/rtapi_app_rt-preempt --instance=0
--debug=1
halcmd: loadrt hal_arm335xQEP encoders=eQEP0
<stdin>:1: insmod failed, returned -1:
rtapi_rpc(): reply timeout
halcmd:
Pin modes are set up by loading bone_eqep0-00A0.dtbo by uboot, audio
overlay (with conflicting pins) is disabled. System has been installed from
bone-debian-9.12-machinekit-armhf-2020-05-02-4gb.img, and kernel updated to
4.19.135-bone-rt-r55
I tried to google the problem, but couldn't find any information.
I will appreciate any ideas on how to make the module work.
Thank you,
Jacek.
--
Charles Steinkuehler
[email protected]
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/machinekit/8ae2751e-9c8f-df95-5ffc-b49a4ba6ba7c%40steinkuehler.net.
