Is there a difference between factory-assigned IEEE EUI-64 and Extended Address?

214 views
Skip to first unread message

an...@picapica.im

unread,
Feb 3, 2018, 12:32:07 PM2/3/18
to openthread-users
Do platform API functions

otPlatRadioGetIeeeEui64() and

otPlatRadioSetExtendedAddress()

work with the same entity?


If yes, should otPlatRadioSetExtendedAddress() implementation change hardware address and make change persistent,

i.e. otPlatRadioGetIeeeEui64() returning new value after device reset?


Giedrius Medzevičius

unread,
Feb 4, 2018, 2:16:34 AM2/4/18
to openthread-users
No, they are not the same. In fact, according to Thread specification, IEEE EUI-64 must not be used as an extended address. I have created an issue with somewhat related question here: https://github.com/openthread/openthread/issues/2537

Jonathan Hui

unread,
Feb 5, 2018, 12:24:53 PM2/5/18
to Giedrius Medzevičius, openthread-users
They are different:
- The IEEE EUI-64 an administered identifier that contains an Organizationally Unique Identifier (OUI).
- The IEEE 802.15.4 Extended Address is an 8-byte identifier used to address devices in IEEE 802.15.4 frames.  Thread requires this not to be based on the IEEE EUI-64 in normal operation.

The `otPlatRadioSetExtendedAddress()` implementation does not need to persistently store this value.  OpenThread manages the persistent storage of the Extended Address.

--
Jonathan Hui

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To post to this group, send email to openthread-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/f1f03a66-b985-4de7-a9f2-d242cda7d612%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages