Robert,
Thank you again for your assistance. I am stuck trying to get the overlay to
compile and am assuming that I have something incorrect. Below is the overlay
that I created:
/*
* Copyright (C) 2013 CircuitCo
*
* Virtual cape for UART1 on connector pins P9.24 P9.26
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License version 2 as
* published by the Free Software Foundation.
*/
/dts-v1/;
/plugin/;
#include <dt-bindings/board/am335x-bbw-bbb-base.h>
#include <dt-bindings/pinctrl/am33xx.h>
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black",
"ti,beaglebone-green";
// identification
part-number = "BB-UART1";
version = "00A0";
// resources this cape uses
exclusive-use =
"P9.24", // uart1_txd
"P9.26", // uart1_rxd
"P9.12", // rtc: gpio1_29
// "P9.19", // uart1_rtsn conflict with
uart1_rtsn.i2c2_scl, i.e. the cape EEPROMS
// "P9.20", // uart1_ctsn conflict with
uart1_ctsn.i2c2_sda, i.e. the cape EEPROMS
"uart1"; // hardware ip used
/*
* Free up the pins used by the cape from the pinmux helpers.
*/
fragment@0 {
target = <&ocp>;
__overlay__ {
P9_12_pinmux { status = "disabled"; }; /* P8_26:
gpmc_csn0.gpio1_29 */
P9_24_pinmux { status = "disabled"; }; /* uart1_txd */
P9_26_pinmux { status = "disabled"; }; /* uart1_rxd */
};
};
fragment@1 {
target = <&am33xx_pinmux>;
__overlay__ {
bb_uart1_pins: pinmux_bb_uart1_pins {
pinctrl-single,pins = <
BONE_P9_24 (PIN_OUTPUT | MUX_MODE0)
// uart1_txd.uart1_txd
BONE_P9_26 (PIN_INPUT | MUX_MODE0)
// uart1_rxd.uart1_rxd
// BONE_P9_19 (PIN_OUTPUT | MUX_MODE0)
// uart1_rtsn.uart1_rtsn
// BONE_P9_20 (PIN_INPUT | MUX_MODE0)
// uart1_ctsn.uart1_ctsn
>;
};
};
};
fragment@2 {
target = <&uart1>;
__overlay__ {
bb_gpio1_29_pins: pinmux_bb_gpio1_29_pins {
pinctrl-single,pins = <
BONE_P9_12 (PIN_INPUT | MUX_MODE7)
/* P9_12: gpmc_csn0.gpio1_29 */
>;
};
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&bb_uart1_pins>;
};
};
};
---- On Thu, 23 Aug 2018 16:47:34 -0500 Robert Nelson
<[email protected]> wrote ----
>
>
> On Thu, Aug 23, 2018 at 4:38 PM <[email protected]> wrote:
> Robert,
> Thank you for the fast reply.
> So I assume that I need to edit your lines: P2_01_pinmux { status =
> "disabled"; }; /* gpio1_18 - EXTINT */
>
> P2_03_pinmux { status = "disabled"; }; /* gpio0_23 - PULSE */
>
> P2_05_pinmux { status = "disabled"; }; /* gpio0_30 - TXD */
>
> P2_07_pinmux { status = "disabled"; }; /* gpio0_31 - RXD */
> P1_04_pinmux { status = "disabled"; }; /* gpio2_25 - RST */
>
>
> I am unsure how you are getting the naming convention for these pins. Can
> you shed some light on it for me?
>
>
> Those pin defintion's are tied to the PocketBeagle..
> For the older BeagleBone use this example for the usart pis
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-UART1-00A0.dts#L36-L66
>
> and expand that for P9_12, look at P8_26 here for help:
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-RTC-01-00A0.dts#L39
>
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-RTC-01-00A0.dts#L61-L65
>
> The main thing to take away from the PB-UART4-GNSS-5-CLICK.dts example is
> the pps node..
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/PB-UART4-GNSS-5-CLICK.dts#L46-L58
>
> and the test it with the ppstest binary:
> [ 30.902060] pps_core: LinuxPPS API ver. 1 registered[ 30.907113]
> pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
> <[email protected]>[ 30.945900] pps pps0: new PPS source pps.-1[
> 30.956911] pps pps0: Registered IRQ 74 as PPS sourcedebian@beaglebone:~$
> sudo ppstest /dev/pps0 trying PPS source "/dev/pps0"found PPS source
> "/dev/pps0"ok, found 1 source(s), now start fetching data...source 0 -
> assert 1523553378.571630304, sequence: 15 - clear 0.000000000, sequence:
> 0source 0 - assert 1523553379.571678846, sequence: 16 - clear 0.000000000,
> sequence: 0
> Regards,
> --
> Robert Nelson
> https://rcn-ee.com/
> --
> 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/CAOCHtYhHUGGU-Ms4%2BgisnpzOmK2ti%3DuTeWyYyr1y4V_2jq_QdA%40mail.gmail.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/1657c06b4ea.10499a7bb56793.4247480615828062530%40lonestartracking.com.
For more options, visit https://groups.google.com/d/optout.
