• State
  • Replies 2 replies
  • Subscribers 55 subscribers
  • Views 42 views
  • Users 0 members are here
Support feedback
Options
Options
Related

Original question:

LAUNCHXL-CC1352R1: Coprocessor device blocked on macRadioPowerUpWait

LAUNCHXL-CC1352R1: MAC_ASSOCIATE_IND with keyIdMode out of the bounds

Fábio Faria Dias
Prodigy 40 points
Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: CC1352R

Tool/software:

Hi

I am trying to connect two LP CC1352R in the same network, one of them is running the sensor example, and the other the coprocessor example.
The examples' source code has been taken from the SIMPLELINK-LOWPOWER-F2-SDK version 8.30.01.01 (Jan 27, 2025). The coprocessor is being configured with security disabled, and it opens a network successfully for other devices to join. My issue arises when a sensor tries to connect to this network.
Whenever the coprocessor receives the MAC_ASSOCIATE_IND message, it reports to the host machine a message containing a KeyIdMode out of the bounds specified in the ti-15.4-stack-cop-interface-guide.pdf.
See below that the allowed values for the keyIdMode are within the range of 0x00 to 0x03.




The next figure shows the MAC_ASSOCIATE_IND bytes sent from the coprocessor to a host via UART. In this case, the host receives 0xE9 in the keyIdMode byte.


I need help to understand what is happening here. Can this keyIdMode field have any value outside the bounds?
I have also tested it with the SDK version 3.10.01.11, and this field is set to zero using the same coprocessor configuration.
  • 0
    TI__Guru* 81751 points

    Hi Fabio,

    Which mode are you running the TI 15.4-Stack in (non-beacon, beacon or FH)?

    Cheers,

    Marie H

  • 0 in reply to Marie H
    TI__Intellectual 1510 points

    Hi Fabio,

    Thanks for reporting this.

    It seems that the RSSI value (ranging from -128 to 127) is carried in the KeyIdMode value of the association indication. This is only used when security of the association indication is disabled (securityLevel = 0). Since the TI15.4-Stack examples do not use the security in the association requests or responses, there is no risk of using this value for transmitting the rssi.

    Best regards,

    Daniel