https://github.com/msperl/mcp2515/blob/master/mcp2515.c there it is.
By the way, the mcp2515 has a built in transceiver. The CANBUS controller on the am335x does not. the MCP2515 is also more cost efficient. So don't let anyone make you feel bad for going that route. On Fri, Aug 19, 2016 at 8:58 AM, William Hermans <[email protected]> wrote: > 1. Haha! It does? Must have missed it when I looked on the pinmap. >> 2. Tried to disable universal cape, makes no difference. >> >> Anyways. I still want to get it to work. Have spent so much time on it, >> and I would hate to just let it go. Even though I probably won't use it. I >> also need to get a spi to uart chip (max14830) to work, which has almost >> the same configuration so I'm hoping that solving this issue, will also >> solve the max14830. >> >> I will try out your tool, looks very promising ;) Thanks for the help. > > Well, you're device tree would simply be for SPI anyway. Since thats the > bus you're using. Also, so you know the mcp2515 driver already exists, so I > forget whatexactly the module name is, but something like $ sudo modprobe > mcp25xx should just work. > > > On Fri, Aug 19, 2016 at 7:21 AM, <[email protected]> wrote: > >> 1. Haha! It does? Must have missed it when I looked on the pinmap. >> 2. Tried to disable universal cape, makes no difference. >> >> Anyways. I still want to get it to work. Have spent so much time on it, >> and I would hate to just let it go. Even though I probably won't use it. I >> also need to get a spi to uart chip (max14830) to work, which has almost >> the same configuration so I'm hoping that solving this issue, will also >> solve the max14830. >> >> I will try out your tool, looks very promising ;) Thanks for the help. >> >> >> fredag 19. august 2016 15.42.06 UTC+2 skrev Matthijs van Duin følgende: >>> >>> I haven't really looked yet at your overlay, but two immediate thoughts: >>> 1. why on earth are you using an spi can controller when there are *two* >>> built-in CAN controllers already on the beaglebone? >>> 2. you have cape-universal enabled, this conflicts with pretty much >>> every overlay (remove the cape_universal=enable from cmdline in your >>> /boot/uEnv.txt >>> >>> BTW I made some utils to make the process of writing overlays less >>> painful: https://github.com/mvduin/overlay-utils >>> It lets you write them as device tree fragments and automatically >>> converts them to the structure requires for overlays. It also includes >>> macros that make pinmux much easier to read. No support for overlay >>> metadata though, I didn't bother since the new configfs mechanism to load >>> overlays ignores it anyway. >>> >>> Matthijs >>> >> -- >> 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/ms >> gid/beagleboard/01fc36f9-5d81-4597-acc6-d553e02a231b%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/01fc36f9-5d81-4597-acc6-d553e02a231b%40googlegroups.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORq7mUuJz%3DMLmZnKz_-pOg%3Dy%2BzNBHkzyBYuS0Oss6k9RnQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
