I am trying to get MachineKit with hm2-soc running on the Snickerdoodle. So
far, I have a bitstream for the FPGA and a configuration for Machinekit and
for QtQuickVcp. I can launch qtquickvcp on the Snickerdoodle, and then
connect to it with MachinekitClient. However, any attempt to home the
sy
Hello,
I can put some image on a BeagleBoard.org hardware piece. I am interested
in learning more about MachineKit. I have been to their site, seen ideas,
and I already have an odd board w/ a version of GRBL on it.
Seth
P.S. I am actually setting up a CNC now. I just posted in the Freenode
s
> On 31 Dec 2018, at 17:28, mugginsac wrote:
>
> Bas,
>
> Thanks that was the problem. I deleted the PRU pins from the "loadrt
> hal_gpio" statement and added a note to the comment.
>
> # load low-level drivers (must not include pins used by PRU)
> loadrt hal_bb_gpio output_pins=807,813,819
Bas,
Thanks that was the problem. I deleted the PRU pins from the "loadrt
hal_gpio" statement and added a note to the comment.
# load low-level drivers (must not include pins used by PRU)
loadrt hal_bb_gpio output_pins=807,813,819,826,914,913,911
input_pins=809,810,814,818
I also cleaned up th
You have both the read (capture position) and update threads of the
PRU driver commented in your HAL file (lines 26 & 30), effectively
disabling the HAL PRU driver.
On 12/31/2018 5:13 AM, Malte Schmidt wrote:
> Dear all,
>
> I have another issue which results in joint 0 following errors. My
> hy
Dear all,
I have another issue which results in joint 0 following errors. My
hypothesis is that the PRU is not running as hal-meter shows position-cmd
being input to the hpg.stepgen but position-fb stays unchanged.
The cape was detected during boot. I have sucessfully used GPIO pins but
the PRU
OK, it was just a thought.
The 4.14 kernel seems to be problematic.
There are quite a few references to problems on RPi forums as well
as some on this forum, where
users went back to the 4.4 or 4.9.
On 31/12/18 08:17, Malte Schmidt wrote:
I changed fstab to contain UUID and uncommented uuid in uEnv.txt. I don't
think this is it.
Kernel boots with the commmandline containing the UUID for root. UUID set
in fstab but still no improvement :-(
machinekit@beaglebone:~$ uname -a
Linux beaglebone 4.14.79-ti-rt-r84 #1 SMP PREEMPT RT Tue
