> Bas 

> I ran the commandline sudo dd if=/dev/zero of=/dev/mmcblk1 count=1 seek=1 
> bs=128k .The good news is that  running config-pin P8.08 gpio no longer gives 
> an error, but now both of the beaglebone boards give the same error message 
> (the one from my previous post).
> the following is written in the log file:

> Nov 12 09:14:40 beaglebone rtapi:0: 1:rtapi_app:5910:user halg_xinitfv:199 
> HAL error: duplicate component name 'hal_lib'
> Nov 12 09:14:40 beaglebone rtapi:0: rtapi_app_main(hal_lib): -16 Device or 
> resource busy
> Nov 12 09:14:40 beaglebone rtapi:0: 1:rtapi_app:5910:user init_actions() 
> failed
> Nov 12 09:14:40 beaglebone msgd:0: rtapi_app exit detected - scheduled 
> shutdown
> Nov 12 09:14:41 beaglebone rtapi:0: 1:rtapi_app:5563:user hal_pru_generic: 
> cant find /usr/lib/linuxcnc/xenomai/pru_generic.bin in /home/machinekit or 
> /lib/firmware/pru/
> Nov 12 09:14:41 beaglebone rtapi:0: 1:rtapi_app:5563:user hpg: ERROR: failed 
> to initialize PRU
> Nov 12 09:14:41 beaglebone rtapi:0: rtapi_app_main(hal_pru_generic): -1 
> Operation not permitted
> Nov 12 09:14:41 beaglebone rtapi:0: 1:rtapi_app:5563:user 
> rtapi_app_main(hal_pru_generic): -1 Operation not permitted
> Nov 12 09:14:42 beaglebone msgd:0: msgd shutting down
> Nov 12 09:14:42 beaglebone rtapi:0: rtapi_msgd went away, exiting

> I attached the comet.hal file, as well as the logfile after I ran export 
> DEBUG=5

The 5th line in linuxcnc.log says exactly what’s happening.
You need to look at your INI file. Have a look at the line that says [PRUBIN]. 
Since you run a (probably) rt-preempt kernel the pru driver cannot find what 
it's looking for (xenomai). It should be like so: 
https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/CRAMPS/CRAMPS.ini#L5

-- 
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/00dc01d59951%2443e61310%24cbb23930%24%40basdebruijn.com.

Reply via email to