fyi - I have created a pull request to add this dts:
https://github.com/beagleboard/bb.org-overlays/pull/101
-drew
--
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
To followup, here is a GitHub gist which shows how I was able to wire
the MCP2515 to SPI0 on the BeagleBone Black and successfully observe
the mcp251x
initialize it and load the can0 interface:
https://gist.github.com/pdp7/20dddbeffe83082e3c94ab0903563783
(also attached)
Photos of MCP2515
For anyone else finding this, the discussion/development is continued on
[Github](https://github.com/battlesnake/beaglebone-spi0-mcp2515)
On Sunday, 23 December 2018 15:54:25 UTC, Drew Fustini wrote:
>
> Hello Mark, thank you for sharing your overlay file. I am trying to
> get a MCP2515 working
Hello Mark, thank you for sharing your overlay file. I am trying to
get a MCP2515 working with the BeagleBone Black on SPI0 with the
4.14.78-bone17 kernel.
Would it be possible for to document how you had the MCP2515 wired to
the P8/P9 headers on the BeagleBone Black?
Also, I would be curious to
On Sat, 2/18/17, robertsmaria934 via BeagleBoard <beagleboard@googlegroups.com>
wrote:
Subject: Re: [beagleboard] Re: Microchip mcp2515, can over spi, not working.
Wrong device tree overlay?
To: beagleboard@googlegroups.com
Date: Sa
On Sat, 2/18/17, Mark K Cowan <m...@open-cosmos.com> wrote:
Subject: Re: [beagleboard] Re: Microchip mcp2515, can over spi, not working.
Wrong device tree overlay?
To: "BeagleBoard" <beagleboard@googlegroups.com>
Date: Satur
I solved it with my own devicetree overlay, loaded after the BB-SPIDEV0
overlay. It's available
at https://github.com/battlesnake/beaglebone-spi0-mcp2515
On Saturday, 18 February 2017 14:22:19 UTC, Laurits Telle Riple wrote:
>
> Hi!
>
> I got it to work, but not using the mainline driver. I
Hi!
I got it to work, but not using the mainline driver. I bought a cape from
towertech to be sure that my hardware was correct. They shipped the device
with some modified version of the driver. Got some help in the beagle irc
chat to try to find the origin of that driver. IIRC the driver was
Hi,
Did you ever get the MCP2515 working over SPI? I'm attempting that now,
but I'm not sure where to start.
Thanks,
Mark
On Tuesday, 20 September 2016 14:30:39 UTC+1, Laurits Telle Riple wrote:
>
> After chatting in the IRC channel with Matthijs I was encouraged to not
> use overlays,
After chatting in the IRC channel with Matthijs I was encouraged to not use
overlays, and just make my own dtb. I have tried that now, but it doesn't
seem to work properly. I've enabled spi0 and spi1. And used the
spi_loopback to see that my dtb was working, then i expanded it by adding a
Something I noticed about your device tree file. First, the mcp251x.c /
mcp2515.c driver would be loaded as a module in a device tree. I see no
"status=okay" so the driver would never load. Honestly I've yet to setup
SPI on the beaglebone in ~3.5 years. So I'm no expert. However if I were
you. I
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
>
> 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
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
The clocks node is definitely wrong. Every top-level node in an overlay
file is treated as a fragment (names like fragment@0 are conventional but
not actually important), but your clocks-node has no target property nor an
__overlay__ child node, so it accomplishes nothing.
Matthijs
--
For
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
16 matches
Mail list logo
