[Tinyos-help] Damaged IEEE 802.15.4 header in TinyOS 2.x

2010-10-20 Thread Jan Bauer
Hi all, since I've updated my TinyOS version from 2.1.1 to the newest SVN version, I've got problems with decoding transmitted packets in wireshark (using the Jackdaw RZUSBStick). For example, I've captured these two Drip/Deluge-Hello-Packets below. The first was sent from a TelosB mote runni

Re: [Tinyos-help] Damaged IEEE 802.15.4 header in TinyOS 2.x

2010-10-21 Thread Philip Levis
On Oct 20, 2010, at 12:41 PM, Jan Bauer wrote: > > > Hi all, > > since I've updated my TinyOS version from 2.1.1 to the newest SVN > version, I've got problems with decoding transmitted packets in > wireshark (using the Jackdaw RZUSBStick). > > For example, I've captured these two Drip/Deluge

Re: [Tinyos-help] Damaged IEEE 802.15.4 header in TinyOS 2.x

2010-10-21 Thread Philip Levis
Stephen, I think you broke CC2420CsmaP.nc on r5174. In particular, the setting of the FCF. Can you please check that it still works with regular AM packets. Also, the current code is such that if you compile with HW security support it won't compile. Phil On Oct 20, 2010, at 12:41 PM, Jan Baue

Re: [Tinyos-help] Damaged IEEE 802.15.4 header in TinyOS 2.x

2010-10-22 Thread Jan Bauer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Phil, thanks for your reply. You're right, there's a problem with the current version of the CC2420CsmaP.nc. If I use the previous version of this file, wireshark captures correct IEEE headers of my applications again. However, there's one except

Re: [Tinyos-help] Damaged IEEE 802.15.4 header in TinyOS 2.x

2010-11-02 Thread Stephen Dawson-Haggerty
I think the problem is that I changed where the fcf is set in the stack, in order to support both short and long (EUI64) addresses, however not all entry points of the stack know this. fcf should be initialized to (at least) to: ( 1 << IEEE154_FCF_INTRAPAN ) | ( IEEE154_ADDR_S