>
> *When I seperate each command by a delay, the rising edge of the clock
> takes ~90ns to go from 0V to 3.3V. I was under the impression that this
> operation would be performed at around ~5ns. I have attached the reading
> from my oscilloscope. My question is, is what I am seeing normal or am I
> doing something wrong?*
>

What kind of a delay are you using ? But if this delay has to interact with
an on chip timer of the L3 interconnect . . . it's going to take a lot
longer than ~5NS. Which is what I would think you're finding out now, but
I'm no expert . . .

On Tue, Feb 16, 2016 at 2:08 PM, John M <[email protected]> wrote:

> Hello All,
>
> I'm trying to create a clock using the PRU, and I have it working to an
> extent, but I am noticing a discrepancy between what I read in the TRM and
> what I'm seeing. When I use a series of SET CLR SET CLR commands on a pin,
> they do not resolve completely before the next command. When I seperate
> each command by a delay, the rising edge of the clock takes ~90ns to go
> from 0V to 3.3V. I was under the impression that this operation would be
> performed at around ~5ns. I have attached the reading from my oscilloscope.
> My question is, is what I am seeing normal or am I doing something wrong?
>
> Thank you.
>
>
> <https://lh3.googleusercontent.com/-HgSaQGizihc/VsOPr4eIEPI/AAAAAAAACwA/fJOdPU4KSlo/s1600/LeCroy.png>
>
>
> --
> 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 [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to