Yes I checked they are all enabled by calling config-pin -q on them and this showed the right configuration. I started working on the setup again today though and now it works fine, but I didn't change anything in my code or my pinmux setup, weird....
And I agree this a bad idea because it is a huge waste of computing power. I have tried using the BBB built in PWM pin which, as far as I know, can be configured to be a 50% duty cycle, stable clk signal by following this link : ... But so far as I haven't been able to make it work because the files mentioned there are not present in my kernel (Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l GNU/Linux). I would like to use that PWM though, is there a way to do it on the more recent kernels ? I could also do both operations on one PRU yes. However, since the audio processing steps involve memory writes to the host, I am worried these might not take deterministic time, which would prevent my clock my clock from being stable. Le jeudi 9 novembre 2017 13:32:02 UTC+1, [email protected] a écrit : > > How about the pin-multiplexing of your two PRU-pins? Are they really > enabled as PRU in/outputs or are they still mapped to some other functions > of the main core? > > On Wednesday, November 8, 2017 at 9:27:20 PM UTC+1, Loïc Droz wrote: >> >> However, I also need to be able to read the CLK signal from PRU1, so I >> figured I would plug the CLK signal generated by PRU0 to pin P8.46 which I >> then poll from PRU1. >> > > This seems to be a bad idea in general. For me it looks like you waste > computing power in PRU1 to retrieve an information PRU0 already has. Can't > you do both operations on one single PRU? Or use an EHRPWM-output to > generate the clock in order to not to waste a complete PRU for such a > stupid task? > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/57291b51-b28e-4095-a74c-704f2d28b72e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
