Forums - Incorrect Beacon Format

3 posts / 0 new
or Register
Last post
Incorrect Beacon Format
jesse
Join Date: 22 Aug 17
Posts: 22
Posted: Wed, 2019-08-14 10:28
Top

Qualcomm's Thread implementation sends a short address in the beacon instead of the extended address. Section "3.2 MAC Layer" of the Thread 1.1.0 Specification modifies section "7.5.2.4 Beacon generation" of the 802.15.4-2006 Specification to ALWAYS send an extended address. See Table 3-2. Modifications and Statements to Chapter 7 and Annexes of IEEE802.154 ( https://standards.ieee.org/findstds/standard/802.15.4-2006.html )

From the Thread 1.1.0 Specification:

"The address used in the Source Address field of the beacon frame generated by a Thread device SHALL contain the value of aExtendedAddress for all values of macShortAddress."

The ramifications are devices that conform to the Thread Specification reject the non-conforming beacon and are unable to join networks where a QCA4020 is acting as commissioner.

FYI, I first notified Qualcomm of problems with the beacon back on June 3, 1019.

https://developer.qualcomm.com/forum/qdn-forums/hardware/qca4020-qca4024/66927

  • Up0
  • Down0
Re: Incorrect Beacon Format
jesse
Join Date: 22 Aug 17
Posts: 22
Posted: Wed, 2019-08-14 10:41
Top

I meant to add that git commit 9a0b838e5bcbf70049a30aaf68abd22d231f5785 from the OpenThread repository, the version used to build the OpenThread Library used by QAPI SDK, does NOT exhibit this problem. When I check out commit 9a0b838e5bcbf70049a30aaf68abd22d231f5785 and build it for the NXP USBKW41Z the beacon is correct and conforming devices can successfully join the network.

 

  • Up0
  • Down0
Re: Incorrect Beacon Format
c_rpedad
Profile picture
Join Date: 18 Jun 18
Location: San Jose
Posts: 317
Posted: Mon, 2019-08-26 16:10
Top

We have created a SF# case and are working internally to fix the issue in next release.

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.