Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 Jan 2017 00:30:08 -0800
From:      "Tony Hain" <tony@tndh.net>
To:        "'Ian Lepore'" <ian@freebsd.org>, <freebsd-arm@freebsd.org>
Subject:   RE: BBB uarts & pps dts definitions
Message-ID:  <03c101d277ae$70f142c0$52d3c840$@tndh.net>
In-Reply-To: <03bb01d2779d$45d6edd0$d184c970$@tndh.net>
References:  <03a801d2776e$cae997e0$60bcc7a0$@tndh.net> <1485400906.30533.54.camel@freebsd.org> <03bb01d2779d$45d6edd0$d184c970$@tndh.net>

next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message-----
> From: owner-freebsd-arm@freebsd.org [mailto:owner-freebsd-
> arm@freebsd.org] On Behalf Of Tony Hain
> Sent: Wednesday, January 25, 2017 10:28 PM
> To: 'Ian Lepore'; freebsd-arm@freebsd.org
> Subject: RE: BBB uarts & pps dts definitions
>=20

FOLLOWUP ...........

> > If you have full source code on the BB, do:
>=20
> Didn't really want to put full source on the BBB.
>=20
> >
> > =A0=A0cd /usr/src/tools/test/ppsapi
> > =A0 make ppsapitest
>=20
> I had full source on a 10.1 system, so I copied the files in that
directory and
> tried to make, but it is complaining about the last line needing an
operator.
>=20
> make: "src/ppsapitest/Makefile" line 13: Need an operator
> make: Fatal errors encountered -- cannot continue
> make: stopped in src/ppsapitest
>=20
>=20
> # $FreeBSD: releng/10.1/tools/test/ppsapi/Makefile 264485 2014-04-15
> 02:17:46Z gnn $
>=20
> PROG=3D   ppsapitest
> MK_MAN=3Dno
>=20
> WARNS?=3D 5
>=20
> .include <bsd.prog.mk>
>=20
> CFLAGS+=3D-Wno-format-security
>=20
> test:   ${PROG}
>         ./${PROG} /dev/cuau0
>=20

Removed the Makefile and it built fine. As I suspected it didn't show
anything due to the pulse being squashed when connected to that pin.
# ./ppsapitest -v /dev/dmtpps
Supported modebits: CAPTUREASSERT OFFSETASSERT CANWAIT TSPEC
^C

>=20
>=20
> Even when it gets built though, the scope shows that the signal is =
being
> pulled to ground as soon as the wire is connected to P8-7, so I don't
expect it
> to work. Is there a way to check the state of the gpio? I would expect
> something like # gpioctl -N gpio_66 Can't find pin named "gpio_66"
>=20
> # gpioctl -l
> pin 00: 0       gpio_0<>
> pin 01: 0       gpio_1<>
> ...
> pin 30: 1       gpio_30<IN,PU>
> pin 31: 1       gpio_31<IN,PU>
> #
>=20
> How do the 3 additional pinmux controllers get enabled?
>=20
>=20
> > =A0 ./ppsapitest /dev/dmtpps
> >
> > You should get something like:
> >
> > =A0 1485400775 .009578536 204 0 .000000000 0
> > =A0 1485400776 .009621995 205 0 .000000000 0
> > =A0 1485400777 .009665453 206 0 .000000000 0
> > =A0 1485400778 .009708869 207 0 .000000000 0
> >
> > -- Ian
>=20
>=20
>=20
> _______________________________________________
> freebsd-arm@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?03c101d277ae$70f142c0$52d3c840$>