On 2/27/2019 9:35 AM, Damien.D wrote:
>
> Another question, regarding write to GPIO output register. I could also
> measure it but do you happen to know how long does it take to write those
> 4*2 (8 total) gpio set/clr register?
>
>
> The existing XIN/XOUT instructions will need to make sure r0.b0 is
> cleared first
yep, that's what I thought
Another question, regarding write to GPIO output register. I could also
measure it but do you happen to know how long does it take to write those
4*2 (8 total) gpio set/clr register?
On 2/27/2019 7:26 AM, Damien Dando wrote:
>
>> Sadly, the Decamux code is using state register 6, or you could use
>> registers 4-7 for the GPIO values. But you can do an offset when
>> performing the XIN/XOUT (set SHIFT_EN in the SPP register), so you can
>> use any other chunk of 4
> I typically use PRU periods around 2-3 uS, so the GPIO read is a
> bigger chunk of the timing budget.
> If you make the GPIO reads and timer processing individual "tasklets",
> I have no issue with merging them into master. Given the way the PRU
> code works, there isn't much down-side to
answer post test
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send
On 2/26/2019 7:24 AM, Damien.D wrote:
> Le lundi 25 février 2019 17:46:06 UTC+1, Charles Steinkuehler a écrit :
>>
>> Personally I don't really want to see hal_pru_generic code reading
>> from the fabric, it eats up too much time. I'd rather see "slow" code
>> like this running on the other PRU,
