Hi everyone,
I am sorry to post another noob question here, but,
I am trying to use the hal module hal_spi, shortly I tried
with
CRAMPS.hal:15:
insmod failed, returned -1:
rtapi_rpc(): reply
timeout
See /var/log/linuxcnc.log for more
information.
in the log
Sep 21 14:22:09
realtimepi msgd:0:
startup pid=5979
flavor=posix rtlevel=1
usrlevel=1
halsize=524288 shm=Posix cc=gcc 6.3.0 20170516
version=unknown
Sep 21 14:22:09
realtimepi msgd:0: ØMQ=4.2.1 czmq=4.0.2
protobuf=3.0.0
atomics=gcc intrinsics
libwebsockets=2.0.3
Sep 21 14:22:09
realtimepi msgd:0:
configured: sha=b87920504
Sep 21 14:22:09
realtimepi msgd:0: built: Sep 18 2018 16:43:17 sha=b87920504
Sep 21 14:22:09
realtimepi msgd:0:
register_stuff: actual hostname as
announced by avahi='realtimepi.local'
Sep 21 14:22:09
realtimepi msgd:0:
zeroconf: registering: 'Log
service on realtimepi.local pid 5979'
Sep 21 14:22:10
realtimepi rtapi:0:
rtapi_msgd went away, exiting
Sep 21 14:22:10
realtimepi msgd:0:
zeroconf: registered 'Log
service on realtimepi.local pid 5979'
_machinekit._tcp 0 TXT "uuid=a42c8c6b-4025-4f83-ba28-dad21114744a" "instance=b9c730a2-bda9-11e8-bcc3-b827eb4bcf42" "service=log" "dsn=ipc:///tmp/0.log.a42c8c6b-4025-4f83-ba28-dad21114744a"
I tried launching machinekit without it and adding it later
using halcmd loadrt hal_spi, but with similar results
should I give it some arguments? I don't know how to
understand how to write them from the code...
Maybe the module is old and has lost some compatibility?
right now i am executing from
Linux
realtimepi 4.14.69-v7+ #1141
SMP Mon Sep 10 15:26:29 BST 2018 armv7l GNU/Linux
Debian Stretch, Machinekit compiled from source
maybe should I explicit the path to hal_spi?
mngr
--