Hi everyone,
Just wanted to report that I got Machinekit to successfully cross-compile
through a Debian Stretch debootstrap. It seems that the latest multiarch
support in stretch is good enough that (most) of the armhf libraries
installed correctly. This doesn't require qemu, so it takes a
Hi,
I'm using:* Linux beaglebone 4.14.106-bone-rt-r19 #1 PREEMPT RT Tue Mar
26 19:02:06 UTC 2019 armv7l GNU/Linux*
I started by disabling the emmc in uEnv.txt
I then tried to modify the config-pin script for P8_14 (which would be
gpmc_AD14 as a starting example), but I get
*Cannot
Hello, I have just installed the latest (April 14) distro for Machinekit.
Now, I want to install the pasm. I tried
sudo apt-get install machinekit-dev
Which I think might be the right package, but I get :
Package machinekit-dev is not available, but is referred to by another
package.
I'm
You are correct...you error is at a lower level than config-pin.
The problem is the mode you want is not implemented by the universal
overlay:
https://github.com/RobertCNelson/bb.org-overlays/blob/master/src/arm/cape-universal-00A0.dts#L1551-L1562
You can either request an update to the
On Fri, Apr 19, 2019 at 3:08 PM Jeff Pollard wrote:
>
> Hi,
> That makes sense, but
>
> I can use config-pin to set the value to something like:
> pwm
> for example:
> config-pin P8.14 pwm
> will work just fine
> as will gpio
> and gpio_pd, etc.
>
> But, gpmc (mode 0) is not
Hi,
That makes sense, but
I can use config-pin to set the value to something like:
* pwm*
for example:
* config-pin P8.14 pwm*
will work just fine
as will *gpio*
and
*gpio_pd, etc.*
But, *gpmc* (mode 0) is not a valid choice i.e. config-pin p8.14 gpmc is
invalid
I
If other pins exist in that location and others are writeable but this one
isn't, this means that pin has been claimed by some other device already.
Like if you try to use HDMI pins, but don't disable HDMI first... you'll
get what you got.
The other scenario is you are using the wrong build and
Hello,
The config-pin utility can be used in user land or user land w/ a .sh
script and .service file to boot the board w/ the required config-pin
utility being present.
Seth
P.S. If you know how to do this instead, this may work for you. So, use:
config-pin P8.14 <--- this would be your
Hi,
Thanks Robert and Charles.
I've taken this:
https://github.com/RobertCNelson/bb.org-overlays/blob/master/src/arm/cape-universal-00A0.dts#L1551-L1562
and added what would be necessary to get the gmpc pins usable following
the convention of the rest of the file.
Hopefully this
Hi,
Not taken the wrong way.
I've already used the gpmc to communicate with my fpga board.
I have a servo system based on hostmot2 and a custom driver to go between
hm2-servo and the gpmc which then 'talks' to the fpga.
This all works fine
This way way back in 2015 though.
The
On 4/19/2019 6:39 PM, Jeff Pollard wrote:
>
> Hi,
>
> Thanks Robert and Charles.
> I've taken this:
> https://github.com/RobertCNelson/bb.org-overlays/blob/master/src/arm/cape-universal-00A0.dts#L1551-L1562
>
> and added what would be necessary to get the gmpc pins usable following
> the
OK, so for that I would definitely recommend crafting your own overlay
that enables the GPMC pins you need. Again, most "casual" users will
not be able to do anything with GPMC, which is why it isn't part of
the "universal" cape to begin with.
It shouldn't be too hard to migrate your existing
I have been looking for the same information for a while and have looked at
all the links listed in the past. My purpose being to design a remote gui
that strictly interfaces via a network. ZMQ would also be used. I have done
some python and qtpy work with linuxcnc but my goal is to use a
Hi,
One of the reasons I'm trying to update is the uSD card I was using
stopped working(booting). I can access some of the files, but I don't
remember exactly the process I used to enable the pins (it was 4 to 5 years
ago!). So, I'm not actually "running" it any more.
In any case I
14 matches
Mail list logo
