Part Number: CC2652R
Hi TI Team,
We are using SDK 3.10 for zed switch. What is the reason why MAC turned to be FF:FF:FF:FF:FF:FF:FF:FF?
The wireshark log is ttached.
What is the fix of this problem?

Regards,
Walter
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Part Number: CC2652R
Hi TI Team,
We are using SDK 3.10 for zed switch. What is the reason why MAC turned to be FF:FF:FF:FF:FF:FF:FF:FF?
The wireshark log is ttached.
What is the fix of this problem?

Regards,
Walter
Walter,
The following code in main.c should prevent the extended IEEE address from becoming all 0xFFs:
// OTA client projects use BIM, so CCFG isn't present in this image
#ifndef OTA_CLIENT
/*
* Copy the extended address from the CCFG area
* Assumption: the memory in CCFG_IEEE_MAC_0 and CCFG_IEEE_MAC_1
* is contiguous and LSB first.
*/
/* Used to check for a valid extended address */
static const uint8_t dummyExtAddr[] =
{ 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF };
OsalPort_memcpy(zstack_user0Cfg.extendedAddress, (uint8_t *)&(__ccfg.CCFG_IEEE_MAC_0),
(APIMAC_SADDR_EXT_LEN));
/* Check to see if the CCFG IEEE is valid */
if(memcmp(zstack_user0Cfg.extendedAddress, dummyExtAddr, APIMAC_SADDR_EXT_LEN) == 0)
#endif // OTA_CLIENT
{
/* No, it isn't valid. Get the Primary IEEE Address */
OsalPort_memcpy(zstack_user0Cfg.extendedAddress, (uint8_t *)(FCFG1_BASE + EXTADDR_OFFSET),
(APIMAC_SADDR_EXT_LEN));
}
And is further validated in zstackstartup.c:
if ( pZStackCfg )
{
uint8_t dummyAddr[8];
memset( dummyAddr, 0xFF, Z_EXTADDR_LEN );
if ( OsalPort_memcmp( pZStackCfg->extendedAddress, dummyAddr, 8 ) != TRUE )
{
pExtAddr = pZStackCfg->extendedAddress;
}
}
// Determine the extended address
zmain_ext_addr( pExtAddr );
You would also do well to look inside zmain_ext_addr which attempts to read the address from NV and further debug these files to discover the issue. Your description makes it sound as though the IEEE address was once not all 0xFFs, please describe what occurs to cause this change.
Regards,
Ryan