-
Notifications
You must be signed in to change notification settings - Fork 13.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about output of ESP.getChipId()? #921
Comments
This is correct. By default, ESP sets its MAC address as a concatenation of On Thu, Oct 22, 2015, 18:16 Environmental Logging Equipment OPEN SOURCE <
|
Many thanks, I was trying to see if a version number could be returned, Thanks again...... On Thu, Oct 22, 2015 at 4:30 PM, Ivan Grokhotkov [email protected]
|
Hi @igrr
My mac is: 84:F*:E*:52:F1:6C but it returns ESP5435756 |
Probably it returns 5435756(DEC) -> toHEX == 52F16C - it is MAC address without OUI (https://en.wikipedia.org/wiki/MAC_address). |
I've also noticed the three first bytes being different, wondered about the
significance and also questioned whether the last three bytes are, in fact,
truly unique across all ESP8266 devices or only in relation to the
groupings given by the first three bytes.
I think it would be very helpful to have an explanation of those first
three bytes and on the reality of the uniqueness of the last three bytes.
…On Thu, 21 Jul 2016, 14:35 whyameye, ***@***.***> wrote:
Sorry to reopen. I'm wondering about this statement: "ESP sets its MAC
address as a concatenation of 3 fixed bytes and 3 unique bytes." I think
you mean that the 1st 3 bytes of the MAC address are the same between all
8266s. However, looking at the MAC addresses of my 12Es, some have 1st 3
bytes 18:FE:34 and some have first 3 bytes are 5C:CF:7F. Moreover I just
purchased a 12F and its 1st 3 bytes are 60:01:94.
I'm concerned about this because I have been using getChipId as a unique
identifier for my 8266s. But now that I see that the 1st 3 bytes of the MAC
address are perhaps not fixed after all, I wonder if it is possible that
the last 3 bytes may not be unique between different runs of 12Es or
between the 12E and 12F. Thoughts on this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#921 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALP8xb_ea3kfuOjRIwscuvZP4jZuM5M0ks5qX2eDgaJpZM4GT10X>
.
|
The first three bytes are the OUI and are allocated to Espressif by IEEE. They currently have 23 allocated:
Given that the last three digits are supposedly "unique", that gives 256256256*28 possible MAC addresses Espressif have available to them currently. That's 469,762,048 possible MAC addresses. These are across their entire range of products, of course, and some may be only used internally for testing, but it's already a large number. As they run out they can request another allocation from IEEE. It's up to them if they do make them globally unique, though. Ideally, they should. In general it's accepted that the last three bytes aren't unique, but the MAC address is. You have to take the entirety of the MAC address to have it unique, not just the last three bytes. Especially since 16777216 is far far below the number of chips Espressif have sold. The full list of OUI allocations is available from http://standards-oui.ieee.org/oui.txt |
I've got an ESP-WROVER-B (16MB flash) and this function gives me the MAC backwards by 2 digits:
By the way, I've seen a comment here, the Espressif Inc. has extended the registered MAC list :) |
Hi,
when this is run it returns the last three portions of the mac address is this correct?
Serial.printf(" ESP8266 Chip id = %08X\n", ESP.getChipId());
Using ver. 1.6.5-1160-gef26c5f
Thanks....
The text was updated successfully, but these errors were encountered: