Perfect! That seems to have fixed my issues! Ill be sure to add a post on the
web describing the procedures we went through to help others!
I do have one other question for you. If this is out of scope, Ill ask it on
another forum, but I figured I would start here...
Now I have confirmed that I see NEMA messages on /dev/ttyS1 and I have pps data
on /dev/pps0.
I next installed gpsd via apt-get and also chrony via apt-get.
using cgps, I do have a fix, but at the bottom it flashes pps:false
32","activated":"2018-08-30T19:35:48.716Z","flags":1,"native":0,"bps":9600,"parity":"N","stopbits":1,"cycle":1.00,"mincycle":0.20}]}
{"class":"WATCH","enable":true,"json":true,"nmea":false,"raw":0,"scaled":false,"timing":false,"split24":false,"pps":false}
{
Not sure about that one, so I checked chronyc sources, and get the following:
210 Number of sources = 2
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
#? NMEA 0 4 17 23 +217ms[ +217ms] +/- 109ms
#? PPS 0 4 0 - +0ns[ +0ns] +/- 0ns
Any thoughts as to why chrony and/or gpsd are not seeing the pps signal?
I never told gpsd where to look for the /dev/pps0 device, but I did tell chrony
to look at:
# get NMEA data from gpsd over shared memory
refclock SHM 0 offset 0.395 delay 0.2 refid NMEA noselect
# get PPS data from pps-gpio, summarize every 16 seconds, prefer it
refclock PPS /dev/pps0 refid PPS poll 4 prefer
Thanks!
---- On Thu, 30 Aug 2018 12:26:35 -0500 Thomas <[email protected]>
wrote ----
> Robert,
> I can't thank you enough for helping me through this. There is very little
> information available online regarding this procedure with this kernel
> version...
>
> First, I made the edit that you recommended.. Now, the BBB reboots and I
> can see NEMA data coming from the GPS chip. However, when I run PPSTEST on
> /dev/pps0, I get the following:
>
> trying PPS source "/dev/pps0"
> found PPS source "/dev/pps0"
> ok, found 1 source(s), now start fetching data...
> time_pps_fetch() error -1 (Connection timed out)
> time_pps_fetch() error -1 (Connection timed out)
> time_pps_fetch() error -1 (Connection timed out)
> ^C
>
>
> I just measured the P9_12 pin, and I see 2.2v and a 100ms pulse width square
> wave coming from the Adafruit GPS receiver. Any other thoughts as to what
> might be causing the timeout?
>
>
>
>
> ---- On Thu, 30 Aug 2018 10:28:46 -0500 Robert Nelson
> <[email protected]> wrote ----
> > On Thu, Aug 30, 2018 at 10:18 AM Thomas <[email protected]>
> wrote:
> > >
> > > I have re-imaged my BBB and made the correction to the typo in my
> overlay file. However, it appears as if I am having the same issue. When I
> install the overlay in the uEnv.txt file and reboot, I am never able to ssh
> back into the BBB.
> > >
> > > My file is below for your review. I can't seem to find any problems
> with it, and seem to be stuck again. Do you have any recommendations on how
> to proceed?
> >
> > Your very close, just change one "4" to a "1".. ;)
> >
> >
> > >
> > > fragment@1 {
> > > target = <&am33xx_pinmux>;
> > > __overlay__ {
> > > bb_uart4_pins: pinmux_bb_uart1_pins {
> >
> > These don't match..
> >
> > > pinctrl-0 = <&bb_uart1_pins>;
> >
> > just change:
> >
> > bb_uart1_pins: pinmux_bb_uart1_pins {
> >
> > Then it loads correctly..
> >
> > uboot_overlays: [fdt_buffer=0x60000] ...
> > uboot_overlays: loading /lib/firmware/CLOCK.dtbo ...
> > 1607 bytes read in 377 ms (3.9 KiB/s)
> > uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
> > 1440 bytes read in 272 ms (4.9 KiB/s)
> > uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...
> > 5127 bytes read in 149 ms (33.2 KiB/s)
> > uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
> > 711 bytes read in 77 ms (8.8 KiB/s)
> > uboot_overlays: loading /lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo
> ...
> > 3513 bytes read in 459 ms (6.8 KiB/s)
> >
> > debian@beaglebone:~$ dmesg | grep pps
> > [ 0.617569] pps_core: LinuxPPS API ver. 1 registered
> > [ 0.617576] pps_core: Software ver. 5.3.6 - Copyright 2005-2007
> > Rodolfo Giometti <[email protected]>
> > [ 40.470657] pps pps0: new PPS source gps_pps.-1
> > [ 40.470808] pps pps0: Registered IRQ 115 as PPS source
> >
> >
> > debian@beaglebone:~$ ls /dev/pps0
> > /dev/pps0
> > debian@beaglebone:~$ sudo ppstest /dev/pps0
> > trying PPS source "/dev/pps0"
> > found PPS source "/dev/pps0"
> > ok, found 1 source(s), now start fetching data...
> > time_pps_fetch() error -1 (Connection timed out)
> > ^C
> >
> > (i don't have anything wired, so it'll time out)
> >
> > Regards,
> >
> > --
> > Robert Nelson
> > https://rcn-ee.com/
> >
>
>
> DISCLAIMER:
> This e-mail and any attachment(s) sent with it are intended exclusively for
> the addressee(s), and may not be used by, opened by, passed on to, or made
> available for use to, any person other than the addressee(s). LoneStar
> Tracking LLC rules out any and all liabilities resulting from any electronic
> transmission.
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/Qu78BPEdTtQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/1658bdf5ae1.fdceb56d442129.8075900310927319563%40lonestartracking.com.
>
> For more options, visit https://groups.google.com/d/optout.
>
DISCLAIMER:
This e-mail and any attachment(s) sent with it are intended exclusively for
the addressee(s), and may not be used by, opened by, passed on to, or made
available for use to, any person other than the addressee(s). LoneStar Tracking
LLC rules out any and all liabilities resulting from any electronic
transmission.
--
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/1658c57eea1.1129dc5a26297.4383771966949993024%40lonestartracking.com.
For more options, visit https://groups.google.com/d/optout.
