joan2937

http://abyz.me.uk/rpi/pigpio/faq.html#Sound_isnt_working

Perhaps something like the following. It should print 1.00 for no problem ```python #!/usr/bin/env python import time import pigpio GPIO=4 MICROS=1000 pi = pigpio.pi() if not pi.connected: exit() pi.set_mode(GPIO, pigpio.OUTPUT)...

The warning is for main() which as declared should return an int. Perhaps we should add a **return 0;** after the **gpioTerminate();**.

It should be **void myfunc** not void *myfunc. It looks like the prototype is wrong. I'm not going to change it. Just accept it is wrong and ignore it.

Not my day. The prototype and code are correct. Nothing is returned as the thread does not terminate. It is a while forever loop. The following is a better example....

Use the command **piscope** rather than **./piscope**.

It's not a trivial change because the DMA chain must be extended to allow writes to both GPIO registers. This was implemented in the very first versions of pigpio but...

I'm not sure I have ever suggested that pigpio supports the compute module completely. The most I remember saying is that pigpio works on all Pi models. Look at http://abyz.me.uk/rpi/pigpio/index.html...

piscope will probably run on any Linux platform. However it receives its data from pigpio which will only run on a Broadcom based SoC - specifically those SoCs found in...

Please supply a complete example with build instructions.