On Saturday, May 4, 2019 at 10:44:17 AM UTC-5, scala...@free.fr wrote:
>
> Hello everyone,
> is there a step by step to configure machinekit with touchy?
>
>
> Touchy requires an MPG (hand wheel encoder) and a start and stop button
available as HAL pins.
You scroll through file lists and a
OH MY GOD!
This should NOT be this hard! I did this back in 2014, when I knew a lot
less about Machinekit and the Bone. But, the only way it seemed I could
get this to work NOW was just copying over files from that 2014 system.
I'm amazed this even worked, but it did. I had to copy
On Wednesday, May 1, 2019 at 10:18:06 PM UTC-5, Charles Steinkuehler wrote:
>
>
> AFAIK, there isn't a package.
>
> You can build from the Machinekit source tree, or the original source
> from github (see /pru_sw/app_loader):
>
> https://github.com/beagleboard/am335x_pru_package
>
> The
I have the latest Machinekit build (4.19.31-bone-rt-r31 #1stretch PREEMPT
RT) and am trying to set up to build PRU programs.
I got the compiler includes and pasm running, now when I compile a program
using prussdrv, I don't have the prussdrv library.
The error I get is :
/usr/bin/ld: cannot
So, I have some old test programs with compiled ARM and PRU binaries, and
they seem to work. Now, I need to create new programs on the
4.19.32-bone-rt-r31 kernel.
I didn't know where to find the includes for the prussdrv, so I got them
off my old bone system. That might be a mistake, they
OK, now I seem to have (maybe) got it! So, I put in :
###Custom Cape
dtb_overlay=/lib/firmware/cape-universalh-00A0.dtbo
And I seem to have both the uio_pruss module loaded, AND all the P8 pins
available!
Thanks to both Charles and Robert for getting me through all this.
Jon
--
website:
On Wednesday, May 1, 2019 at 3:38:22 PM UTC-5, Robert Nelson wrote:
>
>
> No, it's a variable, last one get's set and used..
>
>
> OK, ever so SLOWLY, I'm starting to understand a little bit.
So, am I supposed to use the AM335X-PRU-UIO-00A0.dtbo WITH the
cape-universalh-00A0.dtbo ?
If so, how
On Wednesday, May 1, 2019 at 3:38:22 PM UTC-5, Robert Nelson wrote:
>
>
> No, it's a variable, last one get's set and used..
>
>
> OK, sorry to be dense, but I don't get what the right syntax for this is.
There's a line :
enable_uboot_cape_universal=1
Do I change this to something like :
Meanwhile, there seems to be a discrepancy/deficiency in config-pin.
I can set a pin for gpio with pullup, or pruin, but I have not found ANY
syntax that allows you to set a pin for pruin WITH pullup.
the internal help with -? is pretty confusing. I KNOW the hardware can do
this, as I used to
On Wednesday, May 1, 2019 at 2:50:24 PM UTC-5, Charles Steinkuehler wrote:
>
>
> You'll need to disable HDMI to use those PRU pins on P8:
>
>
> ...I think you then need to either load a different universal overlay
> or a second chunk of the overlay that will add support for those pins.
>
>
On Tuesday, April 30, 2019 at 6:00:51 PM UTC-5, Charles Steinkuehler wrote:
>
> Is there a reason you like beating your head against the wall?
>
> Just let U-Boot load the universal and PRU-UIO overlays, and use
> config-pin to setup the PRU direct inputs/outputs.
>
>
> YES, config-pin is
On Tuesday, April 30, 2019 at 6:00:51 PM UTC-5, Charles Steinkuehler wrote:
>
> Is there a reason you like beating your head against the wall?
>
> Just let U-Boot load the universal and PRU-UIO overlays, and use
> config-pin to setup the PRU direct inputs/outputs.
>
> ...or do you really want
OK, made a little bit of progress, I think. I was confused looking at the
.dtbo, I think that now I **AM** getting a properly compiled .dtbo
including my pinctrl-single settings, in a stripped-down .dts file with
just one overlay fragment.
But, still, when I add this file into /boot/uEnv.txt
Well, this is just a big mess! I wonder if somebody could take the latest
machinekit build from 4/5 (4.19.31-bone-rt-r31 #1stretch PREEMPT RT)
and create a .dts file that selects one PRU input and one PRU output pin,
and then give me all the steps to compile it into a .dtbo and get that
Digging into stuff, I found /lib/firmware/cape-universala-00A0.dtbo, which
when disassembled has a whole bunch of definitions for all possible mux
settings of all the pins. There are such things as :
pinmux_P8_20_pruin_pin
pinmux_P8_20_gpio_pu_pin
pinmux_P8_28_pruout_pin
but, I have no idea
On Tuesday, April 30, 2019 at 7:43:46 AM UTC-5, Charles Steinkuehler wrote:
>
>
>
> What do you mean "locks up the Bone"? What's printed out on the
> serial console when booting?
>
> Sorry, I don't have a serial connection right now. I can hook that up
tomorrow.
>
> And you can always
On Monday, April 29, 2019 at 2:48:11 PM UTC-5, Charles Steinkuehler wrote:
>
>
> It looks like you are loading both your overlay and the universal
> overlay, which will conflict with each other. Just pick one or the
> other, not both.
>
>
> Thanks. So, I removed the line :
On Friday, April 26, 2019 at 9:48:47 PM UTC-5, Robert Nelson wrote:
>
>
> Let's see the output of this script:
>
> sudo /opt/scripts/tools/version.sh
>
>
> Thanks! So, that command shows :
git:/opt/scripts/:[9df8deb6b2ae7570c9102ab58f795d3bed592194]
eeprom:[A335BNLT000C1827BBBG0656]
OK, just another test, i switched over to the
uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo
in uEnv.txt, and I still do not see uio_pruss in the lsmod listing. Now,
when I was tinkering with uEnv.txt, I did take out the
On Friday, April 26, 2019 at 5:24:21 PM UTC-5, Charles Steinkuehler wrote:
>
> You need to make sure you have the UIO PRU driver enabled (vs. the
> remoteproc one). Both are generally available in most recent kernels,
> although the UIO only recently began working again for recent 4.x
>
On Friday, April 26, 2019 at 5:15:55 PM UTC-5, Charles Steinkuehler wrote:
>
> Yes, overlay handling has migrated to U-Boot, but the overlay files are
> otherwise unchanged. There will be some differences due to kernel
> versions, but these differences would exist regardless of whether you
>
On Friday, April 26, 2019 at 4:52:45 PM UTC-5, fun...@gmail.com wrote:
>
> Hello,
>
> I found this bunch of info:
> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Where_did_the_slots_file_go.3F
> .
>
>
> Yes, I was kind of aware the slots were gone. But, I'm still looking for
a step by
OK, now I've done it! So, I am working with this build :
Linux beaglebone 4.19.31-bone-rt-r31 #1stretch PREEMPT RT Fri Apr 5
22:32:32 UTC 2019 armv7l GNU/Linux
I tried to edit my .dtbo file into /boot/uEnv.txt and saw that the
uio_pruss module was no longer being loaded.
Well, I tinkered
I did a Beagle Bone PRU project in 2014, based on the Machinekit build, but
otherwise not related to Machinekit. Now, I've got another similar project.
I am working with the April 14 2019 Machinekit download.
I need 11 PRU direct outputs and 2 direct inputs. I created a .dts file
for the
On Tuesday, April 23, 2019 at 10:06:40 AM UTC-5, Schooner wrote:
>
>
>
> You just need to run 'git clone
> http://githib.com/machinekit/machinekit.git'
> then copy machinekit/src/hal/support/* to wherever you want to use it.
>
>
> Thanks, I got pasm compiled and running. I suspect prussdrv has
On Saturday, April 20, 2019 at 3:40:01 AM UTC-5, Schooner wrote:
>
> Hi Jon
>
> The pasm compiler is built from sources as part of the build for armhf.
> See
> https://github.com/machinekit/machinekit/tree/master/src/hal/support/pasm
>
> If you could give me the steps to get the source from
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
27 matches
Mail list logo
