libpruio is PRUSS assembler code to control the subsystems GPIO, ADC,
PWM/CAP. An API is available to control that assembler part from host CPU
(ARM), written in FreeBASIC. Also a C wrapper is shipped in the package.
When you say Python fits well, why do you think FreeBASIC doesn't? It
combines
So libpruio looks like it wraps calls to interface with the GPIOs via the
PRU with Freebasic or C calls, yes?
We are committed to building this application in a language that is
1. High level and
2. Prevalent in the job market--we need to be able to find people who know
it reasonably well.
(also
Thanks for the help Robert. I'e hacked around the problem for the short
term.
--Mark
On Tuesday, February 9, 2016 at 11:44:56 AM UTC-5, RobertCNelson wrote:
>
> On Tue, Feb 9, 2016 at 8:02 AM, Mark A. Yoder > wrote:
> > Robert:
> > I tried it. What should I see? It looks like I get yet a
A bunch of code for a single GPIO pin (in order to get slow sysfs access).
Keep in mind that you've to maintain all that code for each pin you use in
your project.
For libpruio it is
chgrp pruio /dev/uio5
chmod g+rw /dev/uio5
and you're done for all GPIO, CAP and PWM pins (and you'll get much
Did you have any luck with the EDMA and slave mode in Starterware?
I've created a standard slave driver for starterware with success, but I'm
having trouble getting the EDMA portion to work. Any tips you'd care to
share?
On Tuesday, November 3, 2015 at 1:26:22 PM UTC-5, john3909 wrote:
>
> Hi M
Yes, they are. And I think my partially-successful solution is udev based.
I copied this rule from the robot project I linked to before:
# Install in: /etc/udev/rules.d/
# from cnobile2012@ github
#
KERNEL=="gpio*", SUBSYSTEM=="gpio", ACTION=="add",
PROGRAM="/bin/fix_udev_gpio.sh"
and this scrip
On Tue, Feb 9, 2016 at 8:02 AM, Mark A. Yoder wrote:
> Robert:
> I tried it. What should I see? It looks like I get yet another ordering
> of the aliases.
>
> # universaln
> # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:32 pwmchip0 ->
> ../../devices/platform/ocp/4830.epwmss/48300200.ehrpwm/pwm/p
Joshua Datko :
>
> I'm not sure what solution would work for the pi that can't also be
> used for the BBB.
>
> I referred to this discussion without answer :
https://groups.google.com/forum/#!topic/beagleboard/LD4UPN-GIYM
Joshua Datko :
>
> You should know that anybody can walk up to any BBB, ov
Robert:
I tried it. What should I see? It looks like I get yet another ordering
of the aliases.
# universaln
# 0 lrwxrwxrwx 1 root root 0 Feb 8 19:32 pwmchip0 ->
../../devices/platform/ocp/4830.epwmss/48300200.ehrpwm/pwm/pwmchip0
# 0 lrwxrwxrwx 1 root root 0 Feb 8 19:32 pwmchip2 ->
..
Greg, thanks a bunch. It seems like page 89 of the user guide does the
trick! I am not yet sure how to debug both PRUs at the same time, but I can
write to the scratch pad from one PRU and read it back.
example code:
void testScratchPad(){
static unsigned int test = 0;
test++;
unsi
OK, I see they extended the C language for R30 and R31!
I haven't found any good examples were C and assembler are mixed. I have
seen statements which say there are multiple ways to accomplish it.
It looks like the simplest is to inject assembler code directly into the C
code. See page 76. Th
And of course reboot to have the changes take effect.
-hilmar
Sent from away
> On Feb 9, 2016, at 12:20 AM, Robert Nelson wrote:
>
> cd /opt/scripts/tools/
> git pull
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Go
Ah, thank you. These are excellent resources. I think I found the answer to
my first question in the PRU Optimizing C/C++ Compiler v2.1 User Guide:
Section: 5.7.2 Global Register Variables
The C/C++ compiler extends the C language by adding a special convention to
> the register storage class s
There is a manual for the C compiler and the assembler:
http://processors.wiki.ti.com/index.php/PRU-ICSS
The links are on the right side of the page.
Some of the PRU hardware specific registers are accessed via a large union
in a header file. It uses structs with "bit fields" so you can easily
Can I get the package with instruction?
Thanks,
Kevin
On Thursday, October 8, 2015 at 3:16:17 PM UTC-6, Alessandro Zummo wrote:
>
>
> Hi!
>
> Debian is now supported and you don't need any particular kernel, we give
> a package
> with full drivers sources and a script that does it all.
>
> A gi
Hi,
I am building an application based on the PRU_Hardware_UART example of the
"Programmable Real-time Unit (PRU) Software Support Package release 4.0"
from TI. And I am using the TI C compiler v2.1.2. The UART works great.
I am able to use the GPIO pins by declaring "volatile register uint32_t
16 matches
Mail list logo
