The need to use E18 and E19 For CAN1 comes from the TI pinmux tool. Sent from my iPhone
> On Nov 1, 2017, at 1:19 PM, Robert Nelson <[email protected]> wrote: > >> On Wed, Nov 1, 2017 at 1:14 PM, Tracy Smith <[email protected]> wrote: >> E17 and E18 we want to use that are designated as possible CAN1 pins on the >> BeagleBone Black schematic. >> >> Not using a different overlay, using the existing 4.14 kernel and 2017 I >> boot that Robert Nelson suggests using for the BBB. But we need to pinmux >> for E17 and E18 because the TI pinmuxing tool finds no conflict with these >> two pins on our custom board. I’ll go back and check the CAN1 but prior to >> Roberts changes last week that did not use the P9 expansion header, the unit >> pinmux used different pins CAN1 I believe. With the P9 expansion header, >> can’t use Roberts overlay because there is no P9 expansion header on our BBB >> board. I’ll go back look at the pins for CAN1 prior to then P9 overlay >> changes from last week by Robert. > > What i suggested, assumed you were using a BBB. Thus since you have a > custom board, it's all null and void.. > > Use TI's pinmux tool and properly route your can signals. > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ -- 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/57260CA6-814D-4F21-8D3A-43A47490B236%40gmail.com. For more options, visit https://groups.google.com/d/optout.
