---------- Forwarded message ---------- From: William Hermans <yyrk...@gmail.com> Date: Wed, Nov 1, 2017 at 9:58 AM Subject: Re: [beagleboard] Re: u-boot support for pins To: Tracy Smith <tlsmith3...@gmail.com>
https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-CAN1- 00A0.dts Pad name is on the beaglebone schematic. Which for the purpose of using overlays is useless. On Wed, Nov 1, 2017 at 5:44 AM, Tracy Smith <tlsmith3...@gmail.com> wrote: > Hi William, > > Thanks for the email and here is what I’m trying to do. > > The CANUSB from Lawicel is a standard USB device that looks like a serial > port since it can use the FTDI driver. > > > > On the MachineKit Debian Beagle the CANUSB is a dev/ttyUSB0 device. > > > On our *custom* BeagleBone Black, we want both CAN0 and CAN1 accessible > USB devices. We don’t want to have to add a P9 expansion header on the > custom board for I2C and we have specific pins E17 and E18 we want to use > that are designated as possible CAN1 pins on the BeagleBone Black > schematic. > > > These two pins for CAN1 are tstpt1 pin E17 and TP9 pin E18. Just need to > see if there is a pad name associated with these pins so I can use them for > the pinmux file and device tree to make CAN1 available as a USB device for > uboot and the kernel. This is what I need. > > > Looking through the pinmux files for any pad names associated with these > two pins. > > > Thx, Tracy > > On Oct 31, 2017, at 7:55 PM, William Hermans <yyrk...@gmail.com> wrote: > > SO what is it that you're trying to do ? I've read your posts, but am > still mystified. Just sayin' . . . I've been working with this hardware for > around 5 years now, have written many device tree overlays for various > hardware configurations. Including GPIO, I2C, UART, CAN, SPI, etc. > > I'm willing to give you some guidance, but need to understand what it is > you're trying to do . . . > > I2C really isn't that hard to get working. Nor is most of it. > > -- > 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/to > pic/beagleboard/dE1bIym6rDg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ms > gid/beagleboard/CALHSORrdO87s1J7uKrJ%2BEvRKQRmKhahZBq%3DmtK1 > ktk4sChsbkA%40mail.gmail.com > <https://groups.google.com/d/msgid/beagleboard/CALHSORrdO87s1J7uKrJ%2BEvRKQRmKhahZBq%3DmtK1ktk4sChsbkA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORoStvWHYsRVk_z_rE-pMNMvVv_MRviyEeH-FqJco1gfTw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
