Tengfei,
We are putting together different pieces of the stack contained in many
document written by different organizations. It's of course a bit
confusing, and it's great that so many eyes are looking so closely at it.
You're not "making trouble" in any way, please keep on doing exactly what
you
Jonathan, Simon,
After the discussion on the format order of ieee802.15.4, I believe now the
format that proposed by Simon is right.
The text I copied from IEEE802.15.4 didn't cover the case of 2.4GHz O-QPSK
radio chip, which will transmit the data by bits group, not bit by bit.
Thanks Thomas for
+1
Thanks
On Thu, Jun 25, 2015 at 12:40 AM, Jonathan Hui wrote:
> There are a number of examples in Annex C in IEEE 802.15.4-2011 that
> express IEEE 802.15.4 frames as a a sequence of hex bytes. For example,
> Section C.2.1.1 has the following text:
>
> Secured beacon frame:
> 08 D0 84
There are a number of examples in Annex C in IEEE 802.15.4-2011 that
express IEEE 802.15.4 frames as a a sequence of hex bytes. For example,
Section C.2.1.1 has the following text:
Secured beacon frame:
08 D0 84 21 43 01 00 00 00 00 48 DE AC || 02 05 00 00 00 || 55 CF 00 00
51 52 53 54 22
To make sure we're on the same page, below are two examples of the
bit-and-byte ordering in the IEEE802.15.4e-2011 and IEEE802.15.4e-2012
standard, as I read them.
Please indicate whether this is what you understood.
@JonathanHui, I have IEEE802.15.4-2011 and IEEE802,15,4e-2012 in front of
me. Whic
Agreed. We've struggled with this Endianness issue since the early days
of Ethernet and IEEE 802. Blame it on HDLC.
To eliminate the ambiguities, always list the bytes in transmission
order, together with a prominent note that
a) the bytes are listed in transmission order, and
b) each bytes is
Hello,
I believe what we want is the frame content as a series of bytes (not bits,
symbols or 16-bit words) in the order in which they are sent and received.
Here the second byte, in binary form starting with least significant bit,
is: 1100 (as mentioned in your mail). That's unambiguously 0x3
Sorry option 2 was incorrect.. too fast copy&paste
2) Another option is to convert to hex by considering the MSb first within
the octet
MSb LSb
1100
0x0 0x0 0xF 0xC
0x00 0xFC
regards,
X
2015-06-24 17:53 GMT+02:00 Xavier Vilajosana
:
Hi Tengfei,
this is confusing. Lets make sure this is the right way.
For me the problem is how do we transform an HEX WORD to 16bits
for example can be interpreted from left to right as LSB and from MSB being
right to left when transforming the binary representation to the Hex
representation
Tak
