We are using a USB device for the CAN so we are using the AM3358 and
no CAPE and we are not using the P9 header.  The device is an OEM
version and similar to the kvaser USB/CAN connectors.

https://www.kvaser.com/product/kvaser-usb-hs-ii-hsls/

1) Do you see any kernel issues using this configuration once we have
set up the device tree for CAN0/CAN1 pins below?

CAN0 RX is D17
CAN0 TX is D18
CAN1 RX is E17
CAN1 TX is E18

2) Can we access the E17/E18 or D17/D18 through the P9 header?

3)  Is there a particular reason to use the P9 header instead of USB
for CAN (speed not a concern for us)?

4)  Any additional kernel support required for using CAN over USB?
https://www.kvaser.com/product/kvaser-usb-hs-ii-hsls/

On Mon, Oct 30, 2017 at 6:58 PM, Robert Nelson <robertcnel...@gmail.com> wrote:
>
>
> On Mon, Oct 30, 2017 at 5:39 PM, Tracy Smith <tlsmith3...@gmail.com> wrote:
>>
>> I see. Thanks Robert.  The P9 is the BBB expansion header?  If so, we are
>> not using an expansion header and we don't have P9 correct?  So, we need to
>> pinmux the following:
>>
>> CAN0 RX is D17
>> CAN0 TX is D18
>> CAN1 RX is E17
>> CAN1 TX is E18
>>
>> per our pinmux file using the TI PinMux tool to avoid conflicts.
>>
>
> Correct, P9_xy, are on the P9 header,
>
> AM33XX_IOPAD(0x0978, PIN_INPUT_PULLUP | MUX_MODE2) /* P9_20:
> uart1_ctsn.d_can0_tx */
> AM33XX_IOPAD(0x097c, PIN_INPUT_PULLUP | MUX_MODE2) /* P9_19:
> uart1_rtsn.d_can0_rx */
>
> AM33XX_IOPAD(0x0980, PIN_INPUT_PULLUP | MUX_MODE2) /* P9_26:
> uart1_rxd.dcan1_tx */
> AM33XX_IOPAD(0x0984, PIN_INPUT_PULLUP | MUX_MODE2) /* P9_24:
> uart1_txd.dcan1_rx */
>
> Sorry, you'll have to decode the iopad values for the pad names, i hardly
> look a the pad names..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/



-- 
Confidentiality notice: This e-mail message, including any
attachments, may contain legally privileged and/or confidential
information. If you are not the intended recipient(s), please
immediately notify the sender and delete this e-mail message.

-- 
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/CAChUvXMXKN74sWAEn3R7rO3Rc%2BqXZ9nx8nGjJHJUvrms337s1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to