John Allwine

This may be tied to #361.

Thanks @cerna! I rebuilt the machinekit-hal packages and tried again. Now I'm getting this error: ``` CMake Error at CMakeLists.txt:21 (add_library): Target "bb_gpio" links to target "Machinekit::HAL::managed_hal" but the target...

@cerna @cdsteinkuehler Following the build steps documented [here](http://www.machinekit.io/docs/developing/machinekit-developing/), I'm able to cross compile my fork of machinekit-hal, but it appears that I'm not properly handling the cross compilation of the...

Looks like it was just a matter of replacing objcopy with $OBJCOPY and ld with $LD variables. Sorry for the spam!

Looks like there are issues with using PRU0 on the BBB when using the changes from pull request #320. Still tracking down what they are, but PRU1 seems to work.

I developed a new [HAL driver](https://github.com/PocketNC/bb_gpio) for reading/writing to the pins of the P8 and P9 headers on the Beaglebone Black and AI. The component is also generic enough that...

> if I understand it correctly - and I am not sure about it - you would like to create a generic HAL driver for all devices using memory access...

Is this still the recommended way to build from source? http://www.machinekit.io/docs/developing/machinekit-developing/ It references cloning this repository. If it's been split up into machinekit-hal and machinekit-cnc, is that still correct?

I'd like to see the changes that were implemented in LinuxCNC to address this issue integrated into MachineKit: https://github.com/LinuxCNC/linuxcnc/issues/550 Another thing I'm looking into is increasing the max compensation table...

Has there been any progress on this issue? At Pocket NC we're interested in previewing G code from MachineKit as well. We've developed a [standalone WebGL-based G code simulator](https://sim.pocketnc.com/) with...