Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: "Dr. Aditya Nagrath PhD" <anagrath@elephantheadsoft.com>
Cc: linux-zigbee-devel@lists.sourceforge.net, linux-wpan@vger.kernel.org
Subject: Re: [Linux-zigbee-devel] Cannot get MRFs talking. Not sure what I've done wrong.
Date: Sat, 1 Nov 2014 20:27:43 +0100	[thread overview]
Message-ID: <20141101192740.GC31204@omega> (raw)
In-Reply-To: <A4A370F0-05B7-4FCC-83BA-2633D54680E0@elephantheadsoft.com>

On Sat, Nov 01, 2014 at 10:40:39AM -0600, Dr. Aditya Nagrath PhD wrote:
> Hi,
> 
> Apologize for leaving out version information.  
> I am using kernel:
> Linux beaglebone 3.8.13-bone50 #1 SMP Tue May 13 13:24:52 UTC 2014 armv7l GNU/Linux
> 

can you try to use bleeding edge kernel? [0]

> 
> I had to compile the libn1 and tools to get this far since there was a crash in iz add.  These are the versions that I downloaded and compiled.
> drwxr-xr-x 11 debian admin 4096 Oct 28  2014 libnl-3.2.25
> drwxr-xr-x 11 debian admin 4096 Oct 28  2014 lowpan-tools-0.3.1
> 

this looks fine.

> and just to confirm that they updated:
> root@beaglebone:~# iz --version
> iz: /lib/arm-linux-gnueabihf/libnl-genl-3.so.200: no version information available (required by iz)
> iz: /lib/arm-linux-gnueabihf/libnl-3.so.200: no version information available (required by iz)

mhhh, I didn't get such warning.

> iz 0.3.1
> 
> Appreciate your help Alex.  Right now I’m under water as well so I understand your pain.  Let me know if I can help in anyway
> 

Just try a bleeding edge kernel and try again. Then we can see what's
going on there. Also set a eui-64 address (extended address) before
running "iz set". You can do that by "ip link set $WPAN_INTERFACE address $EXTENDED_ADDR".

exmaples for variables:

WPAN_INTERFACE="wpan0"
EXTENDED_ADDR="aa:aa:aa:aa:aa:aa:aa:aa"

Please do these steps while $WPAN_INTERFACE is down.

- Alex

[0] http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git

      parent reply	other threads:[~2014-11-01 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <01C25E88-7F4B-4669-9BB6-AED08C4B66EE@elephantheadsoft.com>
2014-11-01  8:47 ` [Linux-zigbee-devel] Cannot get MRFs talking. Not sure what I've done wrong Alexander Aring
     [not found]   ` <A4A370F0-05B7-4FCC-83BA-2633D54680E0@elephantheadsoft.com>
2014-11-01 19:27     ` Alexander Aring [this message]

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=20141101192740.GC31204@omega \
    --to=alex.aring@gmail.com \
    --cc=anagrath@elephantheadsoft.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=linux-zigbee-devel@lists.sourceforge.net \
    /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