User avatar
joan
Posts: 14177
Joined: Thu Jul 05, 2012 5:09 pm
Location: UK

pigpio - request for testers

Sat Sep 24, 2016 6:02 pm

I've had reports of timing problems on the Pi3. It only seems to affect those people using waves (which include bit banged serial links).

It seems that the PWM clock is slow and there is a strange interaction to do with whether a HDMI monitor is plugged in or not. Plugging in a HDMI monitor during boot seems to fix the problem for those who have it.

Could you run the following script and report the file size which should be 144000 (or close).

The pigpio daemon need to be running.

sudo pigpiod

If GPIO4 is in use (pin 7) change the G= line.

Code: Select all

#!/bin/bash

G=4 # change 4 to any spare GPIO if 4 is being used

pigs m $G w 
B=$((1<<$G))
pigs wvag $B 0 5000 0 $B 5000 >/dev/null
W=$(pigs wvcre)
N=$(pigs no)
pigs nb $N $B
cp /dev/pigpio$N pigpio-log &
pigs wvtxr $W mils 60000 wvhlt nc $N wvdel $W >/dev/null
wc -c pigpio-log
The test takes 60 seconds.

$ ./pt.sh
144000 pigpio-log
$ ./pt.sh
144000 pigpio-log
$

User avatar
DougieLawson
Posts: 35789
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: pigpio - request for testers

Sat Sep 24, 2016 6:21 pm

I ran the test on a RPi3B with the official RPF 7" display. It's running the BRANCH=next 4.4.17-v7+ #902 kernel booted from a 32GB USB stick.

Code: Select all

[email protected]:~# pigpiod
[email protected]:~# cd /tmp
[email protected]:/tmp# vi f160849.sh
[email protected]:/tmp# chmod 755 f160849.sh
[email protected]:/tmp# ./f160849.sh
127356 pigpio-log
[email protected]:/tmp# ./f160849.sh
127332 pigpio-log
[email protected]:/tmp#
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

User avatar
joan
Posts: 14177
Joined: Thu Jul 05, 2012 5:09 pm
Location: UK

Re: pigpio - request for testers

Sat Sep 24, 2016 7:10 pm

Thanks Dougie. Your Pi set up has the problem. Do you remember which Raspbian download you used? I've never been able to repeat the problem on my Pi3B.

User avatar
FTrevorGowen
Forum Moderator
Forum Moderator
Posts: 5048
Joined: Mon Mar 04, 2013 6:12 pm
Location: Bristol, U.K.
Contact: Website

Re: pigpio - request for testers

Sat Sep 24, 2016 7:20 pm

FWIW, I've run your test on an older version than Dougie (nothing on the GPIO's, both LAN & WiFi connected):

Code: Select all

[email protected]:~ $ uname -a
Linux raspiP3B16Gb 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux
[email protected]:~ $ sudo pigpiod
[email protected]:~ $ ./joanstest.sh 
143988 pigpio-log
Edit: Re-checked, following an "update/upgrade"

Code: Select all

[email protected]:~ $ uname -a
Linux raspiP3B16Gb 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux
[email protected]:~ $ sudo pigpiod
[email protected]:~ $ ./joanstest.sh 
144000 pigpio-log
[email protected]:~ $ ./joanstest.sh 
144000 pigpio-log
Trev.
Still running Raspbian Jessie on some older Pi's (an A, B1, B2, B+, P2B, 3xP0, P0W) but Stretch on my 2xP3A+, P3B+, P3B, B+, A+ and a B2. See: https://www.cpmspectrepi.uk/raspberry_pi/raspiidx.htm

tvjon
Posts: 710
Joined: Mon Jan 07, 2013 9:11 am

Re: pigpio - request for testers

Sat Sep 24, 2016 7:31 pm

joan,

most recent f/w.

$ ./joan-test
144012 pigpio-log
$ ./joan-test
144000 pigpio-log
$

User avatar
joan
Posts: 14177
Joined: Thu Jul 05, 2012 5:09 pm
Location: UK

Re: pigpio - request for testers

Sat Sep 24, 2016 7:34 pm

Thanks Trev. It seems to be related more to the Raspbian image rather than the Linux kernel. Your Pi is fine.

This was the first definite report I saw https://github.com/joan2937/pigpio/issues/80

User avatar
joan
Posts: 14177
Joined: Thu Jul 05, 2012 5:09 pm
Location: UK

Re: pigpio - request for testers

Sat Sep 24, 2016 7:35 pm

tvjon wrote:joan,

most recent f/w.

$ ./joan-test
144012 pigpio-log
$ ./joan-test
144000 pigpio-log
$
Thanks tvjon. Your Pi is fine.

User avatar
DougieLawson
Posts: 35789
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: pigpio - request for testers

Sat Sep 24, 2016 9:11 pm

Hi Joan,

Base download for that machine would have been the earliest RPi3 Raspbian. But it's been upgraded frequently since then.

It's running the experimental kernel as it boots from a SanDisk USB stick.

I can disconnect the official display and try it on a TV. I can also run it headless. Or I can boot from a Jessie Lite SDCard.

Pick your poison.
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

JimmyN
Posts: 1109
Joined: Wed Mar 18, 2015 7:05 pm
Location: Virginia, USA

Re: pigpio - request for testers

Sat Sep 24, 2016 9:16 pm

I tried it, both with and without HDMI plugged in.

Pi3B with HDMI plugged in gave me "126060 pigpio-log"

Boot up without HDMI plugged in gave me "127560 pigpio-log"

uname -a "Linux rpi5 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux

My initial Raspbian image install was several months ago and I've just been doing the normal apt-get upgrades.

User avatar
joan
Posts: 14177
Joined: Thu Jul 05, 2012 5:09 pm
Location: UK

Re: pigpio - request for testers

Sat Sep 24, 2016 10:51 pm

DougieLawson wrote:Hi Joan,

Base download for that machine would have been the earliest RPi3 Raspbian. But it's been upgraded frequently since then.

It's running the experimental kernel as it boots from a SanDisk USB stick.

I can disconnect the official display and try it on a TV. I can also run it headless. Or I can boot from a Jessie Lite SDCard.

Pick your poison.
I'll need to think a bit more.

User avatar
joan
Posts: 14177
Joined: Thu Jul 05, 2012 5:09 pm
Location: UK

Re: pigpio - request for testers

Sat Sep 24, 2016 10:54 pm

JimmyN wrote:I tried it, both with and without HDMI plugged in.

Pi3B with HDMI plugged in gave me "126060 pigpio-log"

Boot up without HDMI plugged in gave me "127560 pigpio-log"

uname -a "Linux rpi5 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux

My initial Raspbian image install was several months ago and I've just been doing the normal apt-get upgrades.
That's a pity. Your Pi has the fault, but it isn't fixed by plugging in a HDMI monitor, which contradicts other results. Do you have any active audio going on?

dgordon42
Posts: 759
Joined: Tue Aug 13, 2013 6:55 pm
Location: Dublin, Ireland

Re: pigpio - request for testers

Sat Sep 24, 2016 11:49 pm

Have you tried this with the sound set to analogue out, and some speakers plugged into the audio/visual port?

I'm running my Pi 3B from an old DEC Terminal over a Serial to USB connection. The only things plugged in are the USB to Serial lead, and a set of powered speakers. The Pi's built in WiFi is connected to my local network.

If I boot or reboot the Pi and run your test script, I get the "correct" answer, 144000, but I also get a sound, not unlike the old dial up internet sound, on the right hand speaker only.
If I issue any sound playing commands, or just start and stop the GUI over an RDP session and then run your testing script, I get the "wrong" answer, 7032. More interestingly however that i now get the modem like sound from both speakers!

Your difficulty reproducing this problem with or without a HDMI monitor may be due to the fact that some people will be using HDMI sound with their monitors, while others will be using analogue sound.

Some of my Pi details:

Code: Select all

[email protected] ~ $ pigs pigpv
50
[email protected] ~ $ uname -a
Linux RaspberryThree 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux
[email protected] ~ $ cat /boot/cmdline.txt
dwc_otg.lpm_enable=0 console=tty1 console=serial0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[email protected] ~ $ cat /boot/config.txt

disable_overscan=1

start_x=1

gpu_mem=128

dtparam=i2c_arm=on

dtparam=audio=on
Hope this helps, I'll try with a HDMI monitor with and without HDMI sound tomorrow.
Dave.

PS, Love what you have done with pigpio, many thanks.

User avatar
dasmanul
Posts: 502
Joined: Wed Sep 30, 2015 10:20 am
Location: Frankfurt, Germany

Re: pigpio - request for testers

Sun Sep 25, 2016 6:06 am

My Pi 3 apparently doesn't show the problem:

Code: Select all

$ ./pt.sh 
144012 pigpio-log
$ ./pt.sh 
143988 pigpio-log
This is on a fully updated Jessie which was originally based off 2016-03-18-raspbian-jessie.img. Let me know if you need any other information.

JimmyN
Posts: 1109
Joined: Wed Mar 18, 2015 7:05 pm
Location: Virginia, USA

Re: pigpio - request for testers

Sun Sep 25, 2016 7:32 am

joan wrote:
JimmyN wrote:I tried it, both with and without HDMI plugged in.

Pi3B with HDMI plugged in gave me "126060 pigpio-log"

Boot up without HDMI plugged in gave me "127560 pigpio-log"

uname -a "Linux rpi5 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux

My initial Raspbian image install was several months ago and I've just been doing the normal apt-get upgrades.
That's a pity. Your Pi has the fault, but it isn't fixed by plugging in a HDMI monitor, which contradicts other results. Do you have any active audio going on?
No, not using audio at all. Just an HDMI connection to an LG monitor with no speakers.

User avatar
joan
Posts: 14177
Joined: Thu Jul 05, 2012 5:09 pm
Location: UK

Re: pigpio - request for testers

Sun Sep 25, 2016 8:23 am

dgordon42 wrote:Have you tried this with the sound set to analogue out, and some speakers plugged into the audio/visual port?

I'm running my Pi 3B from an old DEC Terminal over a Serial to USB connection. The only things plugged in are the USB to Serial lead, and a set of powered speakers. The Pi's built in WiFi is connected to my local network.

If I boot or reboot the Pi and run your test script, I get the "correct" answer, 144000, but I also get a sound, not unlike the old dial up internet sound, on the right hand speaker only.
If I issue any sound playing commands, or just start and stop the GUI over an RDP session and then run your testing script, I get the "wrong" answer, 7032. More interestingly however that i now get the modem like sound from both speakers!

Your difficulty reproducing this problem with or without a HDMI monitor may be due to the fact that some people will be using HDMI sound with their monitors, while others will be using analogue sound.

Some of my Pi details:

Code: Select all

[email protected] ~ $ pigs pigpv
50
[email protected] ~ $ uname -a
Linux RaspberryThree 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux
[email protected] ~ $ cat /boot/cmdline.txt
dwc_otg.lpm_enable=0 console=tty1 console=serial0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[email protected] ~ $ cat /boot/config.txt

disable_overscan=1

start_x=1

gpu_mem=128

dtparam=i2c_arm=on

dtparam=audio=on
Hope this helps, I'll try with a HDMI monitor with and without HDMI sound tomorrow.
Dave.

PS, Love what you have done with pigpio, many thanks.
ANY use of audio using the PWM or PCM peripherals will cause this problem.

By default pigpio uses the PCM peripheral for timing, which leaves the PWM peripheral free for audio.

Using waves or bit banged serial output (which uses waves) or hardware PWM uses the other audio peripheral. In the default case the other peripheral is PWM. If pigpio is told to use PWM by default the other peripheral will be PCM.

So yes, if you are using audio the test will fail.

My problem is that it's failing when people apparently aren't using audio and indeed the clocks look correct.

The following code will display the clock settings.

Code: Select all

/*
   gcc -o get_clocks get_clocks.c
   sudo ./get_clocks
*/

/*
get_clocks.c
2016-06-17
Public Domain
*/

#include <stdio.h>
#include <stdlib.h>
#include <stdarg.h>
#include <unistd.h>
#include <stdint.h>
#include <string.h>
#include <fcntl.h>
#include <errno.h>
#include <sys/mman.h>
#include <sys/stat.h>
#include <sys/types.h>

static volatile uint32_t piModel = 1;

static volatile uint32_t piPeriphBase = 0x20000000;
static volatile uint32_t piBusAddr = 0x40000000;

#define CLK_BASE   (piPeriphBase + 0x101000)

#define CLK_LEN   0xA8

#define CLK_PASSWD  (0x5A<<24)

#define CLK_CTL_MASH(x)((x)<<9)
#define CLK_CTL_BUSY    (1 <<7)
#define CLK_CTL_KILL    (1 <<5)
#define CLK_CTL_ENAB    (1 <<4)
#define CLK_CTL_SRC(x) ((x)<<0)

#define CLK_CTL_SRC_OSC  1  /* 19.2 MHz */
#define CLK_CTL_SRC_PLLC 5  /* 1000 MHz */
#define CLK_CTL_SRC_PLLD 6  /*  500 MHz */
#define CLK_CTL_SRC_HDMI 7  /*  216 MHz */

#define CLK_GP0_CTL 28
#define CLK_GP1_CTL 30
#define CLK_GP2_CTL 32
#define CLK_PCM_CTL 38
#define CLK_PWM_CTL 40

typedef struct
{
   char *name;
   int base;
} clock_info_t;

clock_info_t clock_info[]=
{
   {"GP0", CLK_GP0_CTL},
   {"GP1", CLK_GP1_CTL},
   {"GP2", CLK_GP2_CTL},
   {"PCM", CLK_PCM_CTL},
   {"PWM", CLK_PWM_CTL},
};

/*

Clock sources

0     0 Hz     Ground
1     19.2 MHz oscillator 
2     0 Hz     testdebug0
3     0 Hz     testdebug1
4     0 Hz     PLLA
5     1000 MHz PLLC (changes with overclock settings)
6     500 MHz  PLLD
7     216 MHz  HDMI auxiliary
8-15  0 Hz     Ground
*/

int src_freq[]=
{
   0, 19200000, 500000000, 0, 0, 1000000000, 500000000, 216000000,
   0,        0,         0, 0, 0,          0,         0,         0
};

static volatile uint32_t  *clkReg  = MAP_FAILED;

unsigned hardwareRevision(void)
{
   static unsigned rev = 0;

   FILE * filp;
   char buf[512];
   char term;
   int chars=4; /* number of chars in revision string */

   if (rev) return rev;

   piModel = 0;

   filp = fopen ("/proc/cpuinfo", "r");

   if (filp != NULL)
   {
      while (fgets(buf, sizeof(buf), filp) != NULL)
      {
         if (piModel == 0)
         {
            if (!strncasecmp("model name", buf, 10))
            {
               if (strstr (buf, "ARMv6") != NULL)
               {
                  piModel = 1;
                  chars = 4;
                  piPeriphBase = 0x20000000;
                  piBusAddr = 0x40000000;
               }
               else if (strstr (buf, "ARMv7") != NULL)
               {
                  piModel = 2;
                  chars = 6;
                  piPeriphBase = 0x3F000000;
                  piBusAddr = 0xC0000000;
               }
            }
         }

         if (!strncasecmp("revision", buf, 8))
         {
            if (sscanf(buf+strlen(buf)-(chars+1),
               "%x%c", &rev, &term) == 2)
            {
               if (term != '\n') rev = 0;
            }
         }
      }

      fclose(filp);
   }
   return rev;
}

static int showClock(int clock)
{
   int ctl, div, src, divi, divf;
   double d, freq;
   char * hz;

   ctl = clock_info[clock].base;
   div = clock_info[clock].base+1;

   src = clkReg[ctl]&15;
   divi = (clkReg[div]>>12)&4095;
   divf = clkReg[div]&4095;

   d = divi + (divf / 4096.0);

   if (divi) freq = src_freq[src]/d;
   else      freq = 0;

   if (freq < 1000)         {hz =  "Hz";                 }
   else if (freq < 1000000) {hz = "kHz"; freq /= 1000;   }
   else                     {hz = "MHz"; freq /= 1000000;}


   printf("%s: src=%d divi=%-4d divf=%-4d freq=%-7.3f %s\n",
      clock_info[clock].name, src, divi, divf, freq, hz);
}

/* Map in registers. */

static uint32_t * initMapMem(int fd, uint32_t addr, uint32_t len)
{
    return (uint32_t *) mmap(0, len,
       PROT_READ|PROT_WRITE|PROT_EXEC,
       MAP_SHARED|MAP_LOCKED,
       fd, addr);
}

int initialise(void)
{
   int fd;

   hardwareRevision(); /* sets piModel, needed for peripherals address */

   fd = open("/dev/mem", O_RDWR | O_SYNC) ;

   if (fd < 0)
   {
      fprintf(stderr,
         "This program needs root privileges.  Try using sudo\n");
      return -1;
   }

   clkReg   = initMapMem(fd, CLK_BASE,  CLK_LEN);

   close(fd);

   if (clkReg == MAP_FAILED)
   {
      fprintf(stderr,
         "Bad, mmap failed\n");
      return -1;
   }
   return 0;
}

int main(int argc, char *argv[])
{
   int i;

   if (initialise() < 0)
   {
      fprintf(stderr, "initialise failed\n");
      return 1;
   }

   for (i=0; i<(sizeof(clock_info)/sizeof(clock_info_t)); i++) showClock(i);
}
After sudo pigpiod but before running the tests I get the following output.

Code: Select all

gcc -o get_clocks get_clocks.c
sudo ./get_clocks  
GP0: src=0 divi=0    divf=0    freq=0.000   Hz
GP1: src=6 divi=20   divf=0    freq=25.000  MHz
GP2: src=0 divi=0    divf=0    freq=0.000   Hz
PCM: src=6 divi=250  divf=0    freq=2.000   MHz
PWM: src=0 divi=0    divf=0    freq=0.000   Hz

User avatar
DougieLawson
Posts: 35789
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: pigpio - request for testers

Sun Sep 25, 2016 9:41 am

Booted with HDMI:

Code: Select all

[email protected]:/tmp# ./f160849.sh
143988 pigpio-log
[email protected]:/tmp# ./f160849.sh
144000 pigpio-log

Code: Select all

[email protected]:~/c# ./get_clocks
GP0: src=0 divi=0    divf=0    freq=0.000   Hz
GP1: src=6 divi=20   divf=0    freq=25.000  MHz
GP2: src=1 divi=600  divf=0    freq=32.000  kHz
PCM: src=6 divi=250  divf=0    freq=2.000   MHz
PWM: src=6 divi=50   divf=0    freq=10.000  MHz
[email protected]:~/c#
Booted headless:

Code: Select all

[email protected]:/tmp# ./f160849.sh
127116 pigpio-log
[email protected]:/tmp# ./f160849.sh
127128 pigpio-log

Code: Select all

[email protected]:~/c# ./get_clocks
GP0: src=0 divi=0    divf=0    freq=0.000   Hz
GP1: src=6 divi=20   divf=0    freq=25.000  MHz
GP2: src=1 divi=600  divf=0    freq=32.000  kHz
PCM: src=6 divi=250  divf=0    freq=2.000   MHz
PWM: src=6 divi=50   divf=0    freq=10.000  MHz
[email protected]:~/c#
Booted with RPF display (first get_clocks is before testing):

Code: Select all

[email protected]:~/c# ./get_clocks
GP0: src=0 divi=0    divf=0    freq=0.000   Hz
GP1: src=6 divi=20   divf=0    freq=25.000  MHz
GP2: src=1 divi=600  divf=0    freq=32.000  kHz
PCM: src=0 divi=0    divf=0    freq=0.000   Hz
PWM: src=6 divi=5    divf=0    freq=100.000 MHz
[email protected]:~/c#

Code: Select all

[email protected]:/tmp# ./f160849.sh
127524 pigpio-log
[email protected]:/tmp# ./f160849.sh
127524 pigpio-log

Code: Select all

[email protected]:~/c# ./get_clocks
GP0: src=0 divi=0    divf=0    freq=0.000   Hz
GP1: src=6 divi=20   divf=0    freq=25.000  MHz
GP2: src=1 divi=600  divf=0    freq=32.000  kHz
PCM: src=6 divi=250  divf=0    freq=2.000   MHz
PWM: src=6 divi=50   divf=0    freq=10.000  MHz
[email protected]:~/c#
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

User avatar
joan
Posts: 14177
Joined: Thu Jul 05, 2012 5:09 pm
Location: UK

Re: pigpio - request for testers

Sun Sep 25, 2016 9:59 am

@Dougie

The working with HDMI, not working without HDMI is expected (although I never use HDMI and don't have the problem).

I'm not sure what to make of the display results.

User avatar
DougieLawson
Posts: 35789
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: pigpio - request for testers

Sun Sep 25, 2016 10:14 am

It seems to me to be a firmware bug (since we're not changing your code). Connecting / disconnecting HDMI shouldn't make any difference to how the RPi runs.

Most of my eleven RPis run headless (the few that are close to a TV/monitor (my zero, 2B & one 1B) have a cable connected, just in case I want to do something which isn't headless).
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

User avatar
joan
Posts: 14177
Joined: Thu Jul 05, 2012 5:09 pm
Location: UK

Re: pigpio - request for testers

Sun Sep 25, 2016 10:39 am

DougieLawson wrote:It seems to me to be a firmware bug (since we're not changing your code). Connecting / disconnecting HDMI shouldn't make any difference to how the RPi runs.

Most of my eleven RPis run headless (the few that are close to a TV/monitor (my zero, 2B & one 1B) have a cable connected, just in case I want to do something which isn't headless).
I'm a bit stumped as I'm not able to duplicate the problem on my headless Pi3.

There is no evidence that the clock settings are being changed and yet one of PWM or PCM start to run slow even though they both use the same core clock.

Perhaps some low level clock stuff has changed along the way for the Pi3.

I am rather assuming this only affects the Pi3. If the test also fails on a non-Pi3 that would be useful to know.

User avatar
DougieLawson
Posts: 35789
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: pigpio - request for testers

Sun Sep 25, 2016 11:07 am

I'll give it a go on my 2B.
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

User avatar
Laurens-wuyts
Posts: 716
Joined: Wed Aug 21, 2013 7:35 pm
Location: Belgium
Contact: Website

Re: pigpio - request for testers

Sun Sep 25, 2016 11:15 am

On my Pi2, running headless, I don't see any problem. ;)

Code: Select all

[email protected]:~ $ ./joan.sh
144000 pigpio-log
[email protected]:~ $ ./joan.sh
144000 pigpio-log
Laurens

User avatar
joan
Posts: 14177
Joined: Thu Jul 05, 2012 5:09 pm
Location: UK

Re: pigpio - request for testers

Sun Sep 25, 2016 11:27 am

Laurens-wuyts wrote:On my Pi2, running headless, I don't see any problem. ;)

Code: Select all

[email protected]:~ $ ./joan.sh
144000 pigpio-log
[email protected]:~ $ ./joan.sh
144000 pigpio-log
Laurens
Thanks Laurens. Hopefully only the Pi3B is affected.

fivdi
Posts: 208
Joined: Sun Sep 23, 2012 8:09 pm
Contact: Website

Re: pigpio - request for testers

Sun Sep 25, 2016 11:28 am

Headless test (no monitor, no speakers.)

Without "dtparam=audio=on" in config.txt

[email protected]:~ $ ./pt.sh
144012 pigpio-log
[email protected]:~ $ ./pt.sh
144000 pigpio-log
[email protected]:~ $

With "dtparam=audio=on" in config.txt

[email protected]:~ $ ./pt.sh
127596 pigpio-log
[email protected]:~ $ ./pt.sh
127572 pigpio-log
[email protected]:~ $

Which means the Pi is ok if I'm not mistaken.

User avatar
DougieLawson
Posts: 35789
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: pigpio - request for testers

Sun Sep 25, 2016 11:31 am

2B headless

Code: Select all

[email protected] /tmp # ./f160849.sh
144024 pigpio-log
[email protected] /tmp # ./f160849.sh
144000 pigpio-log

Code: Select all

[email protected] ~/c # ./get_clocks
GP0: src=0 divi=0    divf=0    freq=0.000   Hz
GP1: src=6 divi=20   divf=0    freq=25.000  MHz
GP2: src=0 divi=0    divf=0    freq=0.000   Hz
PCM: src=6 divi=250  divf=0    freq=2.000   MHz
PWM: src=6 divi=50   divf=0    freq=10.000  MHz
2B after reboot with HDMI (and get_clocks before testing):

Code: Select all

[email protected] ~/c # ./get_clocks
GP0: src=0 divi=0    divf=0    freq=0.000   Hz
GP1: src=6 divi=20   divf=0    freq=25.000  MHz
GP2: src=0 divi=0    divf=0    freq=0.000   Hz
PCM: src=0 divi=0    divf=0    freq=0.000   Hz
PWM: src=0 divi=0    divf=0    freq=0.000   Hz

Code: Select all

[email protected] /tmp # pigpiod -a 1
[email protected] /tmp # ./f160849.sh
144024 pigpio-log
[email protected] /tmp # ./f160849.sh
144000 pigpio-log

Code: Select all

[email protected] ~/c # ./get_clocks
GP0: src=0 divi=0    divf=0    freq=0.000   Hz
GP1: src=6 divi=20   divf=0    freq=25.000  MHz
GP2: src=0 divi=0    divf=0    freq=0.000   Hz
PCM: src=6 divi=250  divf=0    freq=2.000   MHz
PWM: src=6 divi=50   divf=0    freq=10.000  MHz
All of my Raspberries have a unified /boot/config.txt

Code: Select all

#
# Unified config.txt @ 16/09/2016 00:50
#

[0x5a67d427]
# ** Eagle      : 5a67d427 **
dtoverlay=i2c-rtc,ds1307
max_usb_current=1

[0x5b592f7f]
# ** Aplus      : 5b592f7f **
gpu_mem=16

[0x9b930691]
# ** Raspberry  : 9b930691 **
#dtoverlay=rpi-cirrus-wm5102-overlay
dtoverlay=rpi-cirrus-wm5102
dtoverlay=i2s-mmap
kernel=kernel.4.1.16+.img.1

[0xc2355259]
# ** Odyssey    : c2355259 **
dtoverlay=lirc-rpi,gpio_in_pin=23,gpio_in_pull=high
gpu_mem=128
start_x=1

[0xe685c936]
# ** Apollo     : e685c936 **
dtoverlay=i2c-rtc,ds1307
gpu_mem=16
initramfs initrd.sda followkernel
max_usb_current=1

[0xebd5f1e8]
# ** Falcon     : ebd5f1e8 **
#dtoverlay=enc28j60,int_pin=25,speed=20000000
gpu_mem=64
dtparam=act_led_activelow=on
disable_audio_dither=1
#dtparam=i2c_vc=on
#dtdebug=on

#[0x4800069e]
# ** Pi         : 4800069e **

#[0x62144670]
# ** Saturn     : 62144670 **

#[0x3d5fffed]
# ** Raspberrypi: 3d5fffed **

#[0x8e8dd26c]
# ** Challenger : 8e8dd26c **

[0x7fbb0a6c]
# ** Beaufort   : 7fbb0a6c **
dtoverlay=w1-gpio
dtoverlay=i2c-rtc,pcf8523

[all]
dtparam=audio=on
dtparam=spi=on
dtparam=i2c_arm=on
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

fivdi
Posts: 208
Joined: Sun Sep 23, 2012 8:09 pm
Contact: Website

Re: pigpio - request for testers

Sun Sep 25, 2016 11:40 am

Is the error not to be expected on DougieLawsons Pi 3 if config.txt contains "dtparam=audio=on"?

Return to “General discussion”