> On Monday, May 20, 2019 at 11:07:12 AM UTC+8, mlampert wrote:
> >
> > Am I correct that the support for the PB is a 'compile time'
> > decision?
>
> Try`board=PocketBeagle`
>
> https://github.com/machinekit/machinekit/blob/b58f6e83/src/hal/drivers/hal_bb_gpio/hal_bb_gpio.c#L83
>
> John
W
On Monday, May 20, 2019 at 11:07:12 AM UTC+8, mlampert wrote:
>
> Am I correct that the support for the PB is a 'compile time' decision?
>
Try`board=PocketBeagle`
https://github.com/machinekit/machinekit/blob/b58f6e83/src/hal/drivers/hal_bb_gpio/hal_bb_gpio.c#L83
John
> So if hal_bb_gpio
Am I correct that the support for the PB is a 'compile time' decision?
So if hal_bb_gpio is compiled for a BBB the driver does not support the
PB headers - right?
The MK image is from April 5 2019 - I made sure I updated to the latest
from deb.machinekit.io - the installed version is 0.1.155255826
On Monday, May 20, 2019 at 5:37:31 AM UTC+8, mlampert wrote:
>
> I've installed the stretch Machinekit image from elinux.org on a
> PocketBeagle to play around with. As it turns out some of the installed
> drivers are indeed specific to the BBB, hal_bb_gpio being one of them (it
> insists on m
I've installed the stretch Machinekit image from elinux.org on a
PocketBeagle to play around with. As it turns out some of the installed
drivers are indeed specific to the BBB, hal_bb_gpio being one of them (it
insists on mapping pin 201 to 901 and then complain that it cannot be
configured). A
I'm looking for a simple example on how to connect to machinekit (remotely)
and - for argument's sake - retrieve the MachineInfo.
I've started up mkwrapper-sim and I can connect to it and use the Cetus UI,
so that seems to work alright. When I try to use pymachinetalk I get the
this error:
mark
