Ok, so should I use config-pin on all the red PIN labels, P2_18, P2_6, P2_32, etc?
Correct. Pin labels in red coorespond to pins on PocketBeagle. The linux kernel has support for MCP2515 SPI. I'm not sure yet if that is compiled into the standard beagle kernel but I can check. Would I just set the SWC Mode pins to gpio? Correct again, 2 mode pins would just go to GPIO outputs. Bring both HIGH for normal mode. On Saturday, December 30, 2017 at 4:02:42 PM UTC-6, [email protected] wrote: > > Ok, so should I use config-pin on all the red PIN labels, P2_18, P2_6, > P2_32, etc? The linux kernel has support for MCP2515 SPI. I'm not sure > yet if that is compiled into the standard beagle kernel but I can check. > Would I just set the SWC Mode pins to gpio? > > On Friday, December 29, 2017 at 4:09:22 PM UTC-8, Earl S wrote: >> >> Since PocketBeagle (and M2) has 2 built-in CAN controllers, we needed an >> external CAN controller for Single-wire CAN. That MCP2515 controller is >> connected to PB via SPI and a couple other GPIO pins. >> >> The attached schematic sketch shows the connections. We'll make a table >> summarizing all of the other connections between the boards later. >> >> Keep in mind that the library you noted here: >> >> >> https://github.com/macchina/Single-Wire-CAN-mcp2515/blob/master/src/MCP2515_sw_can.cpp >> >> relies on this library for functionality: >> >> https://github.com/macchina/mcp2515 >> >> Thanks, ecs >> >> On Friday, December 29, 2017 at 3:29:43 PM UTC-6, RobertCNelson wrote: >>> >>> >>> >>> On Fri, Dec 29, 2017 at 2:55 PM, <[email protected]> wrote: >>> >>>> I'm familiar with the other M2 versions but I'm trying to get my head >>>> wrapped around the beagle version. It appears to enable can we use >>>> config_pin and that connects the can transceiver of the M2 to the linux >>>> kernel on the beagle, correct? >>>> >>>> If so the next thing that would be easy to test is to connect the >>>> SWCAN. As it looks like that just flows into the MCP2515 which should >>>> just >>>> show up as a CAN interface as well. Looking at the current SWCAN >>>> library >>>> <https://github.com/macchina/Single-Wire-CAN-mcp2515/blob/master/src/MCP2515_sw_can.cpp> >>>> It >>>> looks like we setup some specific M2 related settings. How would we do >>>> this as well as pass this information to the beagle to use as a can >>>> interface? >>>> >>>> My ultimate goal is to connect all the interfaces to the linux side but >>>> I'm trying to get up to speed on how the beagle works. I'm familiar with >>>> linux, coding and the M2 but how these all work together still hasn't >>>> clicked. I read the source for config-pin >>>> <https://github.com/cdsteinkuehler/beaglebone-universal-io/blob/master/config-pin> >>>> >>>> but that didn't really clear anything up. If I want to write the glue to >>>> make this cape 'just work' what's the worflow/process I should be going >>>> through? >>>> >>>> Craig >>>> >>> >>> So config-pin is just a user-space utility that allows us to easily >>> switch the peripheral/pin mapping. >>> >>> On the am335x, each pins usually has 8 different modes that can be >>> setup. (gpio, can, usart, spi, timer, pru, etc) >>> >>> By default the can interface is enabled, but it's not muxed to those >>> pins. >>> >>> So when you bootup, you will see the can interface listed under >>> "ifconfig", but till you actually configure the pins' for can (thru >>> config-pin), the am335x can ip will not see any traffic.. >>> >>> 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/eec9bea3-af9c-40d8-ae5a-7aa98137720f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
