Thanks! There's a lot to sort through, but it looks like the sine wave test for the PRU PWM is pretty self-contained. So that I understand correctly:
* You see problems on the physical output pin, but *NOT* on anything in halscope, correct? * The behavior shown can happen when two or more devices are trying to use the same GPIO pin. It looks like your HAL files are OK in this regard (the PRU is driving P9.21, and the hal_bb_gpio driver is not), but this can also happen if you try accessing the GPIO banks via Linux. Is there any chance you're running something other than the HAL drivers that is talking to the I/O pins? A write to any GPIO in bank 0 via Linux would cause the behavior you are seeing. I'll try to setup a test platform here and see if I can reproduce the problem. On 12/14/2016 6:53 AM, Marius Alksnys wrote: > This was a complete Furaday cape v1.2 setup template with temporary > POSTGUI_HALFILE = ao_test.hal > It should be started from run_servo.py > display is axis, but it should be flexible.. > > zip file attached > > 12/12/2016 11:48 PM, Charles Steinkuehler rašė: > ... >> That looks very much like a bug in the PRU code or ARM side HAL >> driver. Do you have an example HAL config you can share (or send me >> direct) that causes this behavior? -- Charles Steinkuehler [email protected] -- 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 an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
