Makes sense. Thanks for your ideas.
Is there a header file, along the lines of sys_mcspi.h that Jason provided,
that you use for the GPIO?
Kirk
On Wednesday, September 7, 2016 at 2:28:43 PM UTC-7, Charles Steinkuehler
wrote:
>
> On 9/7/2016 1:02 PM, Kirk wrote:
> &g
with a custom cape board on the Beaglebone
Black that has already been built.
And I'm trying to move some time critical code to the PRU.
I don't think all the GPIO pins that are used are in the group of PRU GPIO
pins.
Thanks again,
Kirk
On Wednesday, September 7, 2016 at 3:55:36 AM UTC-7, Jason
pru_ctrl.h
pru_ecap.h
pru_iep.h
pru_intc.h
pru_uart.h
sys_mailbox.h
sys_pwmss.h
I don't see anything for SPI0 and SPI1 on the host processor.
I'll be needing to get at them too.
Any ideas?
Thanks,
Kirk
On Thursday, September 1, 2016 at 5:18:07 PM UTC-7, Jason Reeder wrote:
>
> Che
pru_ctrl.h
pru_ecap.h
pru_iep.h
pru_intc.h
pru_uart.h
sys_mailbox.h
sys_pwmss.h
I don't see anything for SPI0 and SPI1 on the host processor.
I'll be needing to get at them too.
Any ideas?
Thanks,
Kirk
On Thursday, September 1, 2016 at 5:18:07 PM UTC-7, Jason Reeder wrote:
>
> Che
reference manual.
Thanks,
Kirk
--
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 emails from it, send an email
to beagleboar
On Wednesday, August 3, 2016 at 6:22:03 PM UTC-7, William Hermans wrote:
>
>
>
> On Wed, Aug 3, 2016 at 3:50 PM, Kirk <kirkmit...@gmail.com >
> wrote:
>
>> I have a scope on the SPI signals there is nothing I can see that is
and then uses the SPI to transfer the data.
I assume there must be things going on in Linux like WiFi communications
and Ethernet communications that interrupt my code.
I'm using a somewhat older image.
What image should I use to get started working with the PRU?
Kirk
On Wednesday, August 3
. The problem is when Linux gets buys with something it just
"goes away" for multiple milliseconds or more and data is lost.
If I want to experiment with the PRU, which debian image should I use?
Thanks,
Kirk
On Tuesday, August 2, 2016 at 3:36:38 PM UTC-7, William Hermans wrote:
>
>
for ideas on how to improve this so data samples are not missed.
Any ideas?
Kirk
--
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 e
Maybe this will help:
Here's what the serial debug output looks like when it doesn't work.
I need some help interpreting it.
Thanks
U-Boot SPL 2013.04 (Sep 25 2013 - 00:49:30)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
SoftConn)
musb-hdrc: MHDRC RTL version 2.0
k.
Should this work?
Or do I need something new?
Thanks,
Kirk
--
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 emails from it,
rom it.
Unable to set system clock.
Any idea on what could cause this error?
Thanks,
Kirk
--
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 s
That solved the problem! Thanks very much for your help with this.
I'm going to cycle on/off all night to make sure there are no more hang's
at boot up due to phantom serial port characters.
Have you (or anyone else) seen any documentation on differences in the
Arrow board?
Kirk
13 matches
Mail list logo
