Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: "\"Thomas B. Rücker\"" <thomas@ruecker.fi>
To: "Michael C. Cambria" <mcc@fid4.com>,
	Alexander Aring <alex.aring@gmail.com>
Cc: Varka Bhadram <varkabhadram@gmail.com>, linux-wpan@vger.kernel.org
Subject: Re: at86rf233 on BeagleBone Black
Date: Tue, 21 Apr 2015 07:23:16 +0000	[thread overview]
Message-ID: <5535FAE4.60302@ruecker.fi> (raw)
In-Reply-To: <55353FC0.5050909@fid4.com>

On 04/20/2015 06:04 PM, Michael C. Cambria wrote:
>
> On 04/17/2015 06:19 PM, Alexander Aring wrote:
>> On Fri, Apr 17, 2015 at 09:28:37AM -0400, Michael C. Cambria wrote:
>> ....
>>> With those changes the "arguments longer than property" message does go
>>> away.  I now get this probe error:
>>>
>>>
>>> [    9.815400] of_get_named_gpiod_flags: parsed 'reset-gpio'
>>> property of
>>> node '/ocp/spi@481a0000/at86rf231@0[0]' - stat)
>>> [    9.815437] of_get_named_gpiod_flags: parsed 'sleep-gpio'
>>> property of
>>> node '/ocp/spi@481a0000/at86rf231@0[0]' - stat)
>>> [   10.287193] at86rf230 spi1.0: Non-Atmel dev found (MAN_ID 00 00)
>>> [   10.971416] at86rf230: probe of spi1.0 failed with error -22
>>>
>> Meanwhile I got private repsonse that somebody have a working openlabs
>> module on a beaglebone, so it's _really_ possible! :-)
>
> Thanks for all the help.  My BBB now works with the openlabs radio.  I
> had P9_28 & P9_30 in the the wrong holes (blush).

Funny, that's pretty much the same type mistake that I made, before I
got things working. I was the person Alexander referred to earlier.

I have it working on a pretty much vanilla 4.0 (a rebuild of RCN's deb
package) on the BBB.


> I'll test e..g ping6 to another BBB and Pi ASAP.

Yeah, still have to test mine too. Started working on wiring another
openlabs module into a Minnowboard Max, but that needs writing a board
file...
I think I'll first just flash one of my CC2530 nodes for some simple tests.

Cheers

Thomas


  parent reply	other threads:[~2015-04-21  7:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <551EDFCA.3070905@fid4.com>
2015-04-03 19:13 ` at86rf233 on BeagleBone Black Alexander Aring
2015-04-03 19:36   ` Alexander Aring
2015-04-14 15:06   ` Alexander Aring
2015-04-16 21:08     ` Michael C. Cambria
2015-04-17  3:26       ` Varka Bhadram
2015-04-17 13:28         ` Michael C. Cambria
2015-04-17 22:19           ` Alexander Aring
2015-04-20 18:04             ` Michael C. Cambria
2015-04-20 18:24               ` Alexander Aring
2015-04-21  7:23               ` "Thomas B. Rücker" [this message]
2015-04-22  6:57                 ` "Thomas B. Rücker"
2015-04-23  9:37               ` Alexander Aring
2015-04-23 13:47                 ` Michael C. Cambria
2015-04-23 14:59                   ` Alexander Aring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5535FAE4.60302@ruecker.fi \
    --to=thomas@ruecker.fi \
    --cc=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=mcc@fid4.com \
    --cc=varkabhadram@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox