The question about mac address in eeprom

Hi,

1.Is the nano module eeprom information in the i2c bus2 0x50?

2.I use i2ctool dump bus2 0x50, then I find the output about eth mac addr is different with it in ifconfig.
The following is outputs:

sudo i2cdump -f -y 2 0x50
No size specified (using byte-data access)
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 01 00 fc 00 78 0d 00 00 02 46 00 00 00 00 00 00    ?.?.x?..?F......
10: 00 00 00 00 36 39 39 2d 31 33 34 34 38 2d 30 30    ....699-13448-00
20: 30 30 2d 32 30 30 20 46 2e 30 00 00 00 00 00 00    00-200 F.0......
30: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
40: ff ff ff ff 74 3a e4 4b 04 00 30 34 32 31 35 31    ....t:?K?.042151
50: 39 30 31 35 35 37 37 00 00 00 00 00 00 00 00 00    9015577.........
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 4e 56 43 42 1c 00 4d 31 00 00    ......NVCB?.M1..
a0: ff ff ff ff ff ff ff ff ff ff ff ff 74 3a e4 4b    ............t:?K
b0: 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ?...............
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a2    ...............?
ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.19  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::b3cb:e9e6:cc4a:c7be  prefixlen 64  scopeid 0x20<link>
        ether 00:e0:4c:68:01:c3  txqueuelen 1000  (Ethernet)
        RX packets 5515  bytes 7858310 (7.8 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3814  bytes 303226 (303.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 151  base 0x8000

Before I get the right output with TX2(bus7 0x50), but now it seems have some questions with nano(bus2 0x50).
I want to see and assign mac addr about nano, please help me.
Thanks.

From the outout with “sudo i2cdump -f -y 2 0x50”, eth mac addr is: 04:4b:e4:3a:74
But the device eth mac addr is: 00:e0:4c:68:01:c3
We want to know why they are different and how to make they keep the same.

That is indeed weird. Could you share the boot log (bootloader log) from uart?

Sure, and I change another nano, get the same result.
Serial-COM13_1217_15-21-41.log (31.6 KB)

Sorry, #4’s log is for the another nano, not for #1 and #2.
The following is mac information for #4’s nano:
From the outout with “sudo i2cdump -f -y 2 0x50”, eth mac addr is: 00:04:4b:e4:3f:8d
But the device eth mac addr is: 00:e0:4c:68:01:e5

Hi arkinghts,

Is it a production module?

Hi WayneWWW,

No, it is:
Jetson Nano: P3450-0000(development module with SD Card memory)

Hi arknights,

Could you share the release you are using? I suspect there are some udev rules override the mac.

Please share the result of “sudo udevadm info -q all /sys/class/net/eth0”.

Hi WayneWWW,

I used Jetpack 4.2.1 rev.2. Another device used Jetpack 4.2.3

$ sudo udevadm info -q all /sys/class/net/eth0
P: /devices/1003000.pcie/pci0000:00/0000:00:02.0/0000:01:00.0/net/eth0
E: DEVPATH=/devices/1003000.pcie/pci0000:00/0000:00:02.0/0000:01:00.0/net/eth0
E: ID_BUS=pci
E: ID_MM_CANDIDATE=1
E: ID_MODEL_FROM_DATABASE=RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
E: ID_MODEL_ID=0x8168
E: ID_NET_DRIVER=r8168
E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
E: ID_NET_NAME_MAC=enx00e04c6801c3
E: ID_NET_NAME_PATH=enp1s0
E: ID_OUI_FROM_DATABASE=REALTEK SEMICONDUCTOR CORP.
E: ID_PATH=platform-1003000.pcie-pci-0000:01:00.0
E: ID_PATH_TAG=platform-1003000_pcie-pci-0000_01_00_0
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Realtek Semiconductor Co., Ltd.
E: ID_VENDOR_ID=0x10ec
E: IFINDEX=3
E: INTERFACE=eth0
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eth0
E: TAGS=:systemd:
E: USEC_INITIALIZED=4295962
E: net.ifnames=0

I don’t see any udev which is involved with mac address.

Is this mac address the same value in each reboot?

yes, no matter each reboot or reflash, mac address has the same value.

First nano:
From the outout with “sudo i2cdump -f -y 2 0x50”, eth mac addr is: 00:04:4b:e4:3a:74
But the device eth mac addr is: 00:e0:4c:68:01:c3

Second nano:
From the outout with “sudo i2cdump -f -y 2 0x50”, eth mac addr is: 00:04:4b:e4:3f:8d
But the device eth mac addr is: 00:e0:4c:68:01:e5

Since this is A02, could you confirm

  1. You are using devkit, right?

  2. Please dump below node and I think it should match your value in eeprom

root@nvidia-desktop:/proc/device-tree/chosen# xxd nvidia,ethernet-mac
  1. Please fallback to the oldest jetpack release (jetpack4.2) or sdcard image to clarify if the cause is in different software release.
  1. Yes, and I see it writes A02 backside again.

  2. yes, “/proc/device-tree/chosen/nvidia,ethernet-mac” shows the same mac address as the mac address value in eeprom, not the device eth mac address.

  3. Later I will try and reply the result.

I find the oldest jetpack release on SDK Manager for Nano(P3448-0020) is Jetpack 4.2.1(rev.2).
It is what I used.
Later I will download jetpack4.2 sdcard image to test.

Hi arknights,

This old issue comes to my mind. I think it is duplicated with your problem.

https://devtalk.nvidia.com/default/topic/1056705/jetson-nano/jetson-nano-developer-kit-ethernet-firmware-update/

Hi WayneWWW,

My board’s Serial Number is xxx1519xxxxxx.
Is there a jetpack version requirement for this firmware update?
I will try it with jetpack 4.2.3 and reply the result.

Thanks.

Hi WayneWWW,

Yes, after firmware update, the mac address value is right!
the mac address value from ifconfig is the same as it in eeprom!

Thanks.