Ok, but looking at the library for the M2 it looked like you configure pins 0 and 27 but there are also some modes that can be set. You tend to setup an interrupt to handle the comms. So I'm wondering how do I initialize the IC (TH8056 KDC <https://www.melexis.com/-/media/files/documents/product-flyers/th8056-product-flyer-melexis.pdf>)'s modes. Once that is done I imagine I can link the pins using CAN. For the other protocols I can't use CAN so I'll probably try to set them up as uart, however I still may need to talk to different ICs.
On Friday, December 29, 2017 at 1:29:43 PM UTC-8, RobertCNelson wrote: > > > > On Fri, Dec 29, 2017 at 2:55 PM, <[email protected] <javascript:>> 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/ffa2bd26-73f6-48bd-b8ea-56e49b0052b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
