An update. In u-boot/board/ti/am335x I do see the following. So, the pad
name for I2C_DATA is uart1_ctsn for D18. For pad name uart1_rtsn it is pin
D17. So this will give the DCAN0_TX/RX for u-boot.
static struct module_pin_mux i2c2_pin_mux[] = {
{OFFSET(uart1_ctsn), (MODE(3) | RXACTIVE |
PULLUP_EN | PULLUDEN | SLEWCTRL)}, /* I2C_DATA
*/
{OFFSET(uart1_rtsn), (MODE(3) | RXACTIVE |
PULLUP_EN | PULLUDEN | SLEWCTRL)}, /* I2C_SCLK
*/
{-1},
};
Now looking in u-boot/board/ti/am335x for E17/E18 for DCAN1_TX/RX. One
could use E17/E18 for CAN1 instead of the P9 expansion header.
On Tuesday, October 31, 2017 at 5:37:43 PM UTC-5, Tracy Smith wrote:
>
> The pad names in u-boot/arch/arm/include/asm/arch-am33xx/mux_am33xx.h
> includes i2c0_sda (pin C17) and i2c0_scl (pin C16), but I don't see names
> for i2c2_scl (pin D17) and i2c2_sda (pin D18), nor tstpt1 (pin E17) nor TP9
> (pin E18),
>
> 1. Did I miss the names for these pins in u-boot?
>
> 2. If u-boot does not support these pins, should they be added to u-boot,
> and/or added to the kernel to support these pins?
>
> Need these pins to support USB/CAN device on a custom BBB. Need to pinmux
> these for the USB/CAN from Lawicel.
>
> thx,
> Tracy
>
--
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/f1e6ec6e-97c4-4d27-ac1f-4fd4fa881efc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
