From: Varka Bhadram <varkabhadram@gmail.com>
To: Karol Poczesny <kpoczesny@gmail.com>, linux-wpan@vger.kernel.org
Subject: Re: cc2520 issue
Date: Tue, 12 May 2015 09:18:02 +0530 [thread overview]
Message-ID: <555177F2.7060502@gmail.com> (raw)
In-Reply-To: <5551768F.1000206@gmail.com>
On 05/12/2015 09:12 AM, Varka Bhadram wrote:
> Hi Karol Poczesny,
>
> On 05/12/2015 03:24 AM, Karol Poczesny wrote:
>
>> Hello all,
>>
>> I have tested simple ping communication between two devices:
>> 1.) Raspberry Pi with at86rf233 transceiver - (openlab module)
>> and
>> 2.) Raspberry Pi with CC2520 transceiver - my own radio board.
> I used BeagleBoneBlack with cc2520. It worked for me. Able to communicate
> with TinyOS nodes.
>
>> I am able to run the interface and start transmit frames for both nodes,
>> but only node with at86rf233 respond.
>>
>> Node with CC2520 can send e.g ping message but cannot answer for ping from
>> at86rf233 node and ignore any other requests.
>>
>> I had checked my radio board - I complied my system with debug in cc2520.c
>> and received this:
>>
>> ...
>> [ 661.896458] cc2520 spi32766.0: SFD for RX
>> [ 937.179079] cc2520 spi32766.0: SFD for RX
> It will just a debug message that will indicate a packet has received. After a packet
> has received cc2520 will generate SFD interrupt.
>
>> so - I received SFD interrupt for RX this function is processed and it
>> seems that received packet stuck somewhere on Rx path.
> Can you please enable the debug for mac802154 and see whether the packet is going
> to the upper layers or not..?
>
>> I'm going to track this anomaly but maybe someone had similar problem.
>> Maybe there are some issues related with configuration cc2520 + RPi?
>> Somebody tested this configuration ?
>>
>> I use pretty old kernel version (3.17.0-rc1+) and old userspace tool - iz
>> on both sides. Configuration is this same as on openlab web.
> Use the latest bluetooth-next [0] tree. And this iz tools are now deprecated
> with the new kernel versions. Use the iwpan [1] tools (similar to iw for wireless).
iwpan/wpan-tools
[0]: git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git
[1]: https://github.com/linux-wpan/wpan-tools
>> Solution is described on my blog:
>> [0] http://zanaster.blogspot.com/2015/05/rpi-6lowpan-solution-with-cc2520.html
> Nice.
>
>> Best,
>> Karol
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Thanks,
>
--
Varka Bhadram
next prev parent reply other threads:[~2015-05-12 3:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 21:54 cc2520 issue Karol Poczesny
2015-05-12 3:42 ` Varka Bhadram
2015-05-12 3:48 ` Varka Bhadram [this message]
2015-05-13 14:46 ` Johann Fischer
2015-05-13 17:36 ` Alexander Aring
2015-05-29 19:18 ` Karol Poczesny
2015-05-30 10:56 ` 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=555177F2.7060502@gmail.com \
--to=varkabhadram@gmail.com \
--cc=kpoczesny@gmail.com \
--cc=linux-wpan@vger.kernel.org \
/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