Am Montag, 12. Januar 2015 22:48:04 UTC+1 schrieb AndyS:
I think I have grasped it now. You can set individual pins to different
mux modes?
Check src/config/dts_custom.bas
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/dts__custom_8bas.html#details
tool in the libpruio
Am Montag, 12. Januar 2015 18:02:35 UTC+1 schrieb Laurent d'Havé:
nice, never heard of kms_force_video though.
Just the name of a variable in the script that came with my distro.
Strange thing, the screen is receiving 1440x900 even though i forced
1024x600 (well i copy/pasted your
I'd need to check you complete /boot/uEnv.txt to give further help. Booting
from SD or eMMC?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop
You may find some inspiration in the BeagleLogic project
https://github.com/abhishek-kakkar/BeagleLogic/wiki.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this
You also can write a usual C application with GTK+ GUI and use Broadway
back-end https://developer.gnome.org/gtk3/stable/gtk-broadway.html to run
this application in a html5 browser window.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are
Looks wired to me. I miss a line like
mmcargs=setenv bootargs console=${console} ${optargs} ${kms_force_mode} root
=${mmcroot} rootfstype=${mmcrootfstype} ${expansion} ${systemd}
where the variable kms_force_mode gets used. Which kernel version (and
distro) are you using?
--
For more options,
Hi Andy!
The PRUSS can control the ADC subsystem. And the PRUSS can control all GPIO
subsystems, so there's no reason to control them from LINUX (host CPU).
Instead control also the slow GPIOs from the PRU code.
Find example code for both, GPIO (over OCP master port = slow) and ADC in
the
Setting the resolution in \boot\uEnv,txt should work:
#Video: Uncomment to override:
kms_force_mode=video=HDMI-A-1:1024x600M-16@60
Note the 'M' after the resolution spec.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the
The kernel driver uio_pruss gets auto-loaded when you enable the PRUSS in a
device tree overlay.
It creates the interrupts /dev/uio*. You can check in your /etc/init.d
script if those files are present, before starting your daemon.
BR
--
For more options, visit http://beagleboard.org/discuss
Am Freitag, 9. Januar 2015 15:57:30 UTC+1 schrieb oakbarn:
PID
Program any controller you want.
Motor Control
AC? DC? Stepper? All is possible. Up to 3 QEP inputs for speed / position
control.
PWM control
Up to 5 PWM outputs are available on the header pins.
7 Digits Remote
Yes, I use BBBs as standalone system. But I don't connect a keyboard, mouse
or screen. Instead I connect LAN and use the PC to control the BBB.
On LINUX it's simple to remote control other systems over LAN. It doesn't
matter which version is installed on PC or BBB. (But when both versions are
I neither use a cross-compiling tool chain nor Eclipse IDE (too bloated).
My PC runs Xubuntu (LINUX). The BBB runs Debian (LINUX kernel
3.8.13-bone37) and is connected over LAN. I host the source files on the
BBB (SD card) and load them over the LAN in to Geany IDE (on PC), writing
back over
I'm not Jason. I'll answer, though.
I have been looking at your presentation slides and am puzzled with Slide 25
PRU low-latency I/Os. I notice that a couple of the pins are suffixed
with 'PRU1_16 in' and 'PRU0_15 out 11 12 PRU0_14 out '
What is the significance of the in and out?
I'm not Jason. I'll answer, though.
I have been looking at your presentation slides and am puzzled with Slide 25
PRU low-latency I/Os. I notice that a couple of the pins are suffixed
with 'PRU1_16 in' and 'PRU0_15 out 11 12 PRU0_14 out '
What is the significance of the in and out?
Am Freitag, 2. Januar 2015 15:08:07 UTC+1 schrieb luciano...@gmail.com:
Hey TJF,
When possible, can you tell me something about my results when I got the
sample rate using the CAP pin?
Hi Luciano,
sorry, I can't, because I don't understand your code. The sequence
#define P1 P9_14
#define
The PRUSS don't cause any CPU usage. You can reduce CPU usage by adding a
nsleep() call to your while loop. Anyway, the max. speed of pulling the
GPIO state (as in your while loop) is limited to approx. 140 kHz.
An alternative is to configure a GPIO interrupt
1. Map an interrupt to any
Why do you ask again?
Am Donnerstag, 25. Dezember 2014 17:28:51 UTC+1 schrieb TJF:
Hi Carlos, and marry Christmas to everyone.
Am Donnerstag, 25. Dezember 2014 01:13:50 UTC+1 schrieb Carlos Cesario:
Someone please could help/explain me how isthe best and security way to
connect 5v relays
It's not really clear what you mean by 'digital image'.
The BBB CPU has an in-build ADC subsystem that can sample analog data on up
to 7 channels (input lines) in 12 bit resolution. If you need high sample
rates ('real time') you should have a look at libpruio
, RobertCNelson wrote:
2: This is open to more users, if you need something packaged and
distributed that is open source, ping us.
How about libpruio?
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/
Thanks for all the hard work!
Thanks Rick, i'll
Am Sonntag, 28. Dezember 2014 18:03:47 UTC+1 schrieb TJF:
The binary libprussdrv.so and ...
A typo, sorry!
The binary *libpruio.so* and ...
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
array. Find an example at this page
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/_cha_examples.html#SubSecExaStepper.
Just replace the stepper motor coils by your relay coils. Instead of the
ULN2003, which has 7 channels, you should find a similar IC with 8 channels
at your
Am Sonntag, 21. Dezember 2014 12:19:08 UTC+1 schrieb Lenny:
The ADC can definitely sample at 1.6 MHz, that is four channels could go
up to 400 kHz each (sequentially). The 1.6 MHz correspond to the minimal 15
steps for one sample when setting the ADC clock to 24 MHz, that is, setting
the
Am Dienstag, 16. Dezember 2014 22:57:41 UTC+1 schrieb luciano...@gmail.com:
Then I was scrolling and he said he still had problems. He proposed a
solution and then I saw the enum pinMixung.
I got the code you (*TFJ*) proposed next and I put it in the library
pruio.h at /usr/local/include.
Am Mittwoch, 17. Dezember 2014 21:24:46 UTC+1 schrieb luciano...@gmail.com:
So, if I'm understandig it right, what I conclude is that with only one
ADC working, the maximum sample rate we can get is around 93 kHz.
That's wrong. The above snippet is a closed loop control. Its output
)
between the AIN-6 pin and AGND to force the signal down. (You can use the
example oszi
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/_cha_examples.html#SubSecExaOszi
in the package libpruio http://beagleboard.org/project/libpruio/ to study
the behaviors of the ADC subsystem.)
2
@Luciano
Am Dienstag, 9. Dezember 2014 13:01:30 UTC+1 schrieb Luciano:
I did this way and I would be glad of you helped me in this question. I
have installed Libpruio0.0.2, and I wrote a simple code just to read the
ADC value (Value[1]) from the output port P9_14 to see it commute.(I don't
@Luciano
I changed your loop logic a bit, so that the GPIO output only changes after
the ADC value is present
IF .Adc-setStep(1, 0, 0, 0, 0) THEN _ ' configure fast Adc step
?ADC setStep failed ( *.Errr ) : EXIT DO
IF .config(1, 1 SHL 1) THEN _
Hi Luciano,
thanks for your reports. I didn't know that each update gets a new path and
that the download works even when the filename is wrong. I'll have to fix
this in the documentation.
Am Dienstag, 16. Dezember 2014 11:12:02 UTC+1 schrieb luciano...@gmail.com:
Hey TFJ,
Just to
I run the QEP modules in the PWMSS subsystems. All works well, unless I try
to switch the Quadrature Count mode (QDECCTL:QSRC bits). My target is to
change the mode dynamically (while the module is running). This works well
when I switch from Quadrature-count mode to Up-count mode.
But when I
Am Montag, 15. Dezember 2014 20:17:54 UTC+1 schrieb luciano...@gmail.com:
About the installation I did all the steps required with admin previleges (
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html+/ChaPreparation.html
).
Pardon my ignorance, but I really don't know what
(zero) for maximum speed, like
pruio_new(io, 0, 0, 0);
Find details here in the documentation.
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/class_pru_io.html#af82d57b4a8ece54e57576463c1be9b9e
- pruio_config() configures the steps to use in its second
Am Dienstag, 9. Dezember 2014 13:01:30 UTC+1 schrieb Luciano:
The thing is that I'm only getting about 10kHz. It is normal to just get
this sample rate
Hello Luciano,
the sampling rate could be higher if you activate less steps (in your code
steps 1 to 8 are active). And you're using the
Hello Rick,
there's also libpruio http://beagleboard.org/project/libpruio/. It can
sample at higher speed than the sysfs solution. And you can configure the
ADC device and its steps.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are
Am Mittwoch, 10. Dezember 2014 19:54:41 UTC+1 schrieb Tux Leonard:
I tried the libpruio solution with kernel 3.14.xx but there is no
capemanager. So I couldn't install libpruio.
libpruio doesn't depend on capemgr, there's no need for capemgr at all!
It's just convenient to use it to load
Am Mittwoch, 10. Dezember 2014 21:21:18 UTC+1 schrieb Tux Leonard:
But there is no /sys/devices/bone_capemgr.*/slots because there's no
capemanager.
I didn't know that. What does the manual say? How to load any device tree
overlay in that case? (uEnv.txt command?) The same way should work
Am Mittwoch, 10. Dezember 2014 21:54:20 UTC+1 schrieb William Hermans:
... and in this case you would probably use Charles' universal IO
https://github.com/cdsteinkuehler/beaglebone-universal-io and once loaded
you configure the pins ( on the fly ) from the command line.
You can use this
The *_raw files should contain the digits (0 to 4095), the other is the
voltage in mV (badly rounded, AFAIR, and I found further bugs in the
driver).
Am Montag, 1. Dezember 2014 14:55:12 UTC+1 schrieb craf...@gmail.com:
There are two ways to access analog input in beaglebone.
There're much
A stepper gets controlled by cycling through eight states. Here's the code
I use to drive a stepper motor (extract of example from libpruio
http://beagleboard.org/project/libpruio/)
//! Set values of all four output pins.
#define PIN_OUT(a, b, c, d) \
if (pruio_gpio_setValue(Io, P1, a))
It shouldn't be an issue to get a PID control running at 10 kHz on the host
processor (ie with libpruio http://beagleboard.org/project/libpruio/).
Complex network activities or grafics may slow it down, but in worst case
you can use one of the two Programmable Real-time Unit SubSystems (PRUSS)
The CPU ball mapping is hard coded in the AM335x logic, no tricks AFAIK.
Your list seems to be OK (I didn't check all details). There're just a few
header pins usable for PRUSS low latency GPIO, when LCD isn't enabled. All
other GPIOs can get accessed over the OCP master port with 2 or 3
The CPU ball mapping is hard coded in the AM335x logic, no tricks AFAIK.
Your list seems to be OK (I didn't check all details). There're just a few
header pins usable for PRUSS low latency GPIO, when LCD isn't disabled. All
other GPIOs can get accessed over the OCP master port with 2 or 3
the old build scripts included in libpruio-0.0.x.
But I recommend to install the new BBB_fbc-1.00, which I also use on my
board now. Just follow the instructions in (only point 1)
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/_cha_preparation.html#SecInstallation
BR
--
For more
Am Montag, 10. November 2014 21:52:26 UTC+1 schrieb William Hermans:
TJF,
I'd be willing at some point to help you port some code for your project,
Hello William, welcome at the libpruio project.
I know about many tasks to improve the libpruio package. Some of them might
be fun for you
Hello Nils,
I just had a closer look at your first example. Sorry, I've new concerns.
It seems that the code requires to customize the size of the external
memory, which is a downside for beginners. And it doesn't show the ring
buffer capabilities (, you could have used MM mode as well).
From
Oups, found a buck right when I posted:
line 70
SWAP p0, p1 : EXIT DO
should be
SWAP p0, p1 : EXIT WHILE
Soory!
--
For more options, visit http://beagleboard.org/discuss
---
You received this
Hello Roy,
there's an alternative way to fetch ADC data on the BBB. The library
libpruio http://beagleboard.org/project/libpruio/ provides several
functions to fetch analog input, much faster and more flexible than sysfs.
It also allows to configure the ADC subsystem steps. And furthermore it
Hello Nils,
thanks for the code. I think about including it in the libpruio examples
folder, but your main loop is endless and the user cannot abort the
program. (Shouldn't the file get closed?) Perhaps I can adapt it a bit.
Regarding the ADC speed I made some further testing and it seems that
Hello jleb!
Sorry for the late answer. I did some testing, meanwhile, and it seems that
you're right. The ADC subsystem is clocked by CLK_M_OSC directly at 24 MHz.
(First, I thought there's an additionaly pre-scaler in the PRCM.)
Find attached a libpruio measurement from four channels,
Write access to the Control Module pad registers is only possible for the
ARM CPU in protected mode. Neither mmaped C code nor the PRUSS can write
these registers. That's hard-coded in the AM33xx logic, no feedback on
failure.
BTW: Beside the universal device tree overlay from Charles
Hello jleb!
There's no problem fetching the samples from the ADC subsystem and store
them in the external memory block (or DRam area). You don't need both
PRUSS, one can do that.
But the ADC subsystem isn't fast enough. It needs 14 cycles to perform a
step and a further cycle to start the
Hello Bill!
I'm dealing with PRU stuff since month, creating the libpruio
http://beagleboard.org/project/libpruio/ library.
Am Freitag, 31. Oktober 2014 18:00:03 UTC+1 schrieb Bill Gray:
I'm wondering if there is some special way that one needs to access them
in order to get this low
Hello Nils,
thanks for feedback!
The maximum sample rate is limited by the ADC subsystem. It's 159 kS/s (15
cycles @ 2.4 MHz + safety buffer) for a single step (channel). It neither
matters if you operate in RB or MM mode, nor if you use FB or C compilers.
For me, writing C examples is
You can use one the universal device tree overlays by Charles Steinkuehler,
shipped with newer OSs (since 2014 June). Write the required state by
spawning
echo MODE /sys/devices/ocp.*/XX-pinmux.*/state
where MODE is a pre-defined mode (human readable) and XX is the header pin
(I'm not sure
William, sorry, my fault!
us can find the 'brand new' English project page at
http://beagleboard.org/project/libpruio/
Don't hesitate to ask if you need further assistance on downloading.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are
libpruio-0.2 is out now:
New:
- Ring buffer (RB) run mode (samples analog input continously).
- PWM output in IO and RB mode (variable frequency and duty cycles).
- CAP input in IO and RB mode (analyses frequency and duty cycles of a
pulse train).
- New examples *pwm_adc*,
Hello Nils!
Am Mittwoch, 17. September 2014 22:25:05 UTC+2 schrieb nils@gmail.com:
Hey TJF,
I'm currently working on underwater ultrasonic sound and wonder if you
think that with your library can produce constant and reliant ADC input
at sample rates of 200Khz per pin
The PRUSS
Hello!
Am Dienstag, 16. September 2014 20:50:47 UTC+2 schrieb
mahmou...@hotmail.com:
I got the following:
/usr/bin/ld: cannot find -lncurses
collect2: ld returned 1 exit status
make: *** [all] Error 1
Install libncurses
sudo apt-get install libncurses5-dev
I am setting the libpruio
Why do you think you'll need any cape?
BBB has more then 15 free GPIOs and 7 analog inputs. You can simply build
your prototype board to adjust the voltages (GPIO @ 3.3V, ADC @ 1.8 V) and
feed the signals to the header pins.
--
For more options, visit http://beagleboard.org/discuss
---
You
Hi Shoaib Ahmed,
thanks for your interrests in libpruio.
Am Mittwoch, 3. September 2014 18:05:05 UTC+2 schrieb sufialh...@gmail.com:
Am I missing something?
Forgive me if this sounds like a stupid question. Please help.
No stupid question. A stupid author of libpruio, instead. Pinmuxing
Am Montag, 18. August 2014 13:03:50 UTC+2 schrieb c...@isbd.net:
The group associated with the /sys/devices/ files associated with
the ADC is 'root' and, anyway, the group only has read permission so
even if I added my user to that group I wouldn't be able to configure
the ADC
I didn't check all your code (*../sage_pru.hp* is missing, so I don't know
how MEM_PRU_DATA0_BASE is defined).
But: From the PRU-0 point of view, the address of DRam-0 is *0x0* (and
DRam-1 is 0x2000).
--
For more options, visit http://beagleboard.org/discuss
---
You received this message
Am Sonntag, 17. August 2014 10:50:29 UTC+2 schrieb David Goodenough:
Do you have a pointer to the Java binding? Google could not find it.
ssl reports in the following thread that he did the job
http://www.freebasic.net/forum/viewtopic.php?f=14t=22501start=30#p198874
But it seems that he
Hello Rodrigo,
Am Samstag, 16. August 2014 00:19:01 UTC+2 schrieb Rodrigo Caropreso:
I was planning to use the libpruio Library (my assembly is a little bit
rusty and this library should help me to achieve this task) but last week
I've got stuck into this seg fault issue.
...
Is it
The (half) board voltage is connected on board to the ADC subsystem @
channel AIN-7. Just read that samples. (I wrote libpruio
http://beagleboard.org/project/libpruio/ for that purpose, see examples
*io_input* or *oszi*.)
Am Dienstag, 12. August 2014 12:58:11 UTC+2 schrieb mike:
Hello ,
trigger
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ChaExamples.html#SubExaTriggers
to show a graph of the inputs at AIN4 and AIN7 in a window. Or example 1
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ChaExamples.html#SecExaSimple,
which exports 13 lines
Am Dienstag, 8. April 2014 12:15:31 UTC+2 schrieb Youngtae Jo:
I've tried to find some example of ADC reading by PRU for my project, but
I couldn't find it.
What about libpruio http://beagleboard.org/project/libpruio/? (Flexible
step configuration, up to 8Mb samples (limited by the kernel
There're several bugs in the ADC kernel drivers in the different distros.
That's why I wrote libpruio http://beagleboard.org/project/libpruio/. You
might want to check it out.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to
PWM
There're 14 header pins connected to a PWM signal. But some of them connect
to the same signal. (Your bike has more than 20 gears but only about 14
gear ratios.)
The CPU can generate 10 PWM signals in parallel, either by using a ePWM
module (16 bit timer, A and B output) or by using an
Am Mittwoch, 2. Juli 2014 07:25:45 UTC+2 schrieb Spaced Cowboy:
1) I have an assembly program running on PRU0 receiving data in a tight
loop, and I want to signal PRU1 at some point to do further processing on
the bytes received. Is it possible to have PRU0 write into a register (say
r2)
://beagleboard.org/project/libpruio/. Here's a direct link to the
online-documentation
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/.
Good luck for your project.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you
Hi cowboy!
I confirm, GPIO high is 3.3V. Unconnected pins (input pins without
resistor) have about 0.8V.
Why don't you use the PWM devices for that task?
Anyway, P8_11 isn't connected to the PRUSS. This pin only works in GPIO
mode (mode 7) and I'm not sure if you can reach 50MHz that way.
@Cowboy
You can reach 100 MHz to toggle a GPIO pin in open loop control. This is as
fast as the PWM devices. (When you need closed loop control it slows down a
lot due to the latency on the OCP port.)
--
For more options, visit http://beagleboard.org/discuss
---
You received this message
Find infos on how to use the PRUSS in the PRU FAQ
https://groups.google.com/forum/embed/?place=forum/beagleboardshowsearch=trueshowpopout=trueshowtabs=truehideforumtitle=trueparenturl=http%3A%2F%2Fbeagleboard.org%2FCommunity%2FForums#!category-topic/beagleboard/u28ytaoNenU
.
I'd try the inbuild
Hi Ben!
Am Mittwoch, 25. Juni 2014 14:36:30 UTC+2 schrieb family...@googlemail.com:
Or is the dtbo file doing all the magic?
The dtbo file is pretty simple. It only powers on the PRUSS. Here's the dts
file to compile:
/* Minimal device tree overlay to activate PRUSS
Licence: GPLv3
(C)
Am Montag, 23. Juni 2014 06:19:52 UTC+2 schrieb serge...@gmail.com:
why set r3, r31.t16 results in r3=0x08 ?
I'd like the pru asm compiler just reject this code as it seems of little
sense.
Yes, I agree. pasm should output the same error message as for
MOV r3, r31.t16
which is
Hello Rafael,
thanks for your complete installation instructions. I plan to include them
in the next version of the documentation, if you don't mind (at least I
like to add a link to your post here).
BTW: In your C code example the destructor pruio_destroy() wont be called
in case of an
A miss click and a miss post ...
The PRUSS can access the Control Modul pin mux registers. It's working for
a lot of libpruio users. Did you enable the OCP master port?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the
Are you sure that your 'cape-like thingy' doesn't interfere with the boot
sequence? (HDMI pins control the boot process!) I'd change to other pins
(ie. P8_07 to P8_11).
You can do pin-muxing from user space (without any device tree overlays)
using libpruio
Just try it out ...
It should work, since the pin-muxing is done by software running on a
PRUSS. The kernel on the host has no influence on that process (and cannot
prevent your system in case of unintentional changes).
By default, libpruio locks the pins used by the system. But you can unlock
Thanks for feedback. Feel free to mail your suggested improvements for the
installation instructions.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and
Find examples on how to configure and access GPIO and ADC pins from the
PRUSS in the source code of libpruio
http://beagleboard.org/project/libpruio/.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
You can use libpruio http://beagleboard.org/project/libpruio/ to do the
pin-muxing.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving
This seems to be a problem with the ADC configuration. You could run one of
the libpruio examples io_input
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ChaExamples.html#SubExaIoInp
or oszi
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ChaExamples.html
Each PRUSS has its own set of output (and input) pins:
- pr1_pru0_pru_... -- PRU-0
- pr1_pru1_pru_... -- PRU-1
You can open more than one event. Default is:
- ret = prussdrv_open(PRU_EVTOUT_0); -- PRU-0 to host
- ret = prussdrv_open(PRU_EVTOUT_1); -- PRU-0 to host
And
-
Just found a typo in my previous post:
- ret = prussdrv_open(PRU_EVTOUT_1); -- PRU-0 to host
should be
- ret = prussdrv_open(PRU_EVTOUT_1); -- PRU-1 to host
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google
Hi Charles,
P8_03 is used as gpmc_ad6 by the board. Free pins start at P8_07 ff.
You can find examples in the source code of libpruio
http://beagleboard.org/project/libpruio/ on how to use a PRUSS to do
pinmuxing and how to change the state of an output pin (or read the state
of input pins).
Version 0.0.2 is out now:
- added: new example button.bas (.c)
- bugfix: gpio_get() returns correct value now
- cosmetic: pruio_c_wrapper.h contains headers pruio.h and pruio.hp
(all-in-one)
- cosmetic: minor changes in documentation
--
For more options, visit
Hi Tony,
there`s also libpruio http://www.beagleboard.org/project/libpruio/. It
supports configuring and controling (input / output) of any GPIOs in an
easy and fast manner (by using driver software running on a PRUSS).
Additionally it contains some ADC features.
--
For more options, visit
Hello guy,
as Sungjin said, not all header pins can be used as GPIO. And some of the
possible GPIO pins are used by the system (HDMI, EMMC2, I2C2, MCASP0 on
BBB). About 30 pins are free. The way to configure them depends on the
programing environment you intend to use (C, Cloud9, FreeBASIC,
What do you mean by 'load a custom pru'? The PRUSS are hardware devices,
inbuild in the CPU. You cannot load or unload them!
You can load software to the instruction memory and execute it. Have a look
at the PRU FAQ
https://groups.google.com/forum/#!topic/beagleboard/u28ytaoNenU for the
in C.
In that case it's best to use libpruio
http://beagleboard.org/project/libpruio/. You can configure the pins
(getting an error message when locked by the system) and control them
(input and output) in an easy and fast manner. See stepper.c source code
http://users.freebasic-portal.de/tjf
You can use libpruio http://beagleboard.org/project/libpruio/ to
re-configure the pins. Are you really sure that you want that? AFAIR i2c2
is used for the communication between the CPU and the power control device.
The CPU has six UART devices. You can use ie. UART2 on P9, pin 21 and 22
(in
Am Sonntag, 1. Juni 2014 22:25:57 UTC+2 schrieb andre...@googlemail.com:
Any help is appreciated. I am running out of ideas!
Andy
Hello Andy,
I recommend to check out libpruio http://beagleboard.org/project/libpruio/.
Using this library you can configure and control GPIOs without device
a function to switch the LED on or off. Find
the example sos.c in the package that makes the USER LED-3 blinking in SOS
code:
- description:
http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ChaExamples.html#SubExaSos
- source code:
http://users.freebasic-portal.de/tjf
Check out libpruio http://www.beagleboard.org/project/libpruio/. It makes
a PRUSS fetching ADC data.
Using default ADC settings you get 10 ksamples per channel, so ~1.4
ksamples for 7 channels (0.7 ms). Additionally you can customize the ADC
settings (open- and sample delay, as well as
This is an old thread, but the answer meight still be helpful:
Check out libpruio http://beagleboard.org/project/libpruio/. Find the
desired code in file src/pruio/pruio_init.p. It enables devices TSC_ADC_SS
and GPIOs (if not up before).
--
For more options, visit
This should be possible with assembler code running on PRU-1. You can use
about 10 input and output pins in a fast manner. The clock is 200 MHz, so
you'll have 50 cycles for your operations. The PRUSS can also generate an
external clock signal for you.
--
For more options, visit
Am Samstag, 24. Mai 2014 15:16:27 UTC+2 schrieb John Brookes:
Thanks Sungiin,
Do you know a route to capture ADC and store in memory (eg SSD on USB,
etc.) RT ?
Is this possible?
jb
Hi John,
you can use libpruio http://beagleboard.org/project/libpruio/ to store
ADC data in PRUSS
Am Montag, 10. September 2012 13:59:55 UTC+2 schrieb Evan Thomas:
Hello,
embedded/real time/hardware newbie here. I have an requirement to read an
ADC, perform some simple FP calculations and write to DAC. It needs to be
at least 20KHz but importantly the latency on the DAC/ADC needs to
Check out libpruio http://openbeagle.org/project/libpruio/. It's designed
for that purpose and contains a C wrapper.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from
501 - 600 of 605 matches
Mail list logo
