# U-boot doesn't set dpmac.1?

**URL:** <https://community.solid-run.com/t/u-boot-doesnt-set-dpmac-1/698>\
**Category:** NXP LX2160\
**Created:** [August 3, 2023, 12:58pm UTC](https://community.solid-run.com/t/u-boot-doesnt-set-dpmac-1/698 "2023-08-03T12:58:26Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![joema](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@joema](https://community.solid-run.com/u/joema)\
**Post date:** [August 3, 2023, 12:58pm UTC](https://community.solid-run.com/t/u-boot-doesnt-set-dpmac-1/698/1 "2023-08-03T12:58:26Z")

</div>

how do I set the address of dpmac.1?

Even if I use 17 entries in tlv\_eeprom:

Base MAC Address 0x24 6 FA:00:E7:00:00:00  
MAC Addresses 0x2A 2 17

I don’t see any u-boot configuration of dpmac1:

Net: eth0: DPMAC3@xgmii, eth1: DPMAC4@xgmii, eth2: DPMAC5@xgmii, eth3: DPMAC6@xgmii, eth4: DPMAC7@xgmii, eth5: DPMAC8@xgmii, eth6: DPMAC9@xgmii, eth7: DPMAC10@xgmii, eth8: DPMAC17@rgmii-id [PRIME]

And indeed if I bring up eth1 (bound to dpmac.1) its mac address is random:

# dmesg | grep mac

[3.553631] fsl\_mac: fsl\_mac: FSL FMan MAC API based driver  
[5.374262] fsl\_dpaa2\_mac dpmac.17: Adding to iommu group 3  
[5.381445] fsl\_dpaa2\_mac dpmac.1: Adding to iommu group 3

# ls-addni dpmac.1

[44.132557] fsl\_mc\_allocator dpbp.1: Adding to iommu group 3  
[44.140511] fsl\_mc\_allocator dpmcp.53: Adding to iommu group 3  
[44.148359] fsl\_mc\_allocator dpcon.31: Adding to iommu group 3  
[44.155740] fsl\_mc\_allocator dpcon.30: Adding to iommu group 3  
[44.163464] fsl\_mc\_allocator dpcon.29: Adding to iommu group 3  
[44.170983] fsl\_mc\_allocator dpcon.28: Adding to iommu group 3  
[44.178377] fsl\_mc\_allocator dpcon.27: Adding to iommu group 3  
[44.186084] fsl\_mc\_allocator dpcon.26: Adding to iommu group 3  
[44.192935] fsl\_mc\_allocator dpcon.25: Adding to iommu group 3  
[44.199596] fsl\_mc\_allocator dpcon.24: Adding to iommu group 3  
[44.207119] fsl\_mc\_allocator dpcon.23: Adding to iommu group 3  
[44.213937] fsl\_mc\_allocator dpcon.22: Adding to iommu group 3  
[44.221549] fsl\_mc\_allocator dpcon.21: Adding to iommu group 3  
[44.228344] fsl\_mc\_allocator dpcon.20: Adding to iommu group 3  
[44.235607] fsl\_mc\_allocator dpcon.19: Adding to iommu group 3  
[44.243123] fsl\_mc\_allocator dpcon.18: Adding to iommu group 3  
[44.249939] fsl\_mc\_allocator dpcon.17: Adding to iommu group 3  
[44.257625] fsl\_mc\_allocator dpcon.16: Adding to iommu group 3  
[44.264715] fsl\_dpaa2\_eth dpni.1: Adding to iommu group 3  
[44.458785] fsl\_dpaa2\_eth dpni.1: Probed interface eth1  
Created interface: eth1 (object:dpni.1, endpoint: dpmac.1)

# ip a

…  
4: eth0: \<BROADCAST,MULTICAST,UP,LOWER\_UP\> mtu 1500 qdisc mq state UP group default qlen 1000  
link/ether fa:00:e7:00:00:08 brd ff:ff:ff:ff:ff:ff  
inet 192.168.68.64/22 metric 1024 brd 192.168.71.255 scope global dynamic eth0  
valid\_lft 7158sec preferred\_lft 7158sec  
inet6 fe80::f800:e7ff:fe00:8/64 scope link  
valid\_lft forever preferred\_lft forever  
5: eth1: \<BROADCAST,MULTICAST\> mtu 1500 qdisc noop state DOWN group default qlen 1000  
link/ether ce:89:2a:a8:0f:92 brd ff:ff:ff:ff:ff:ff

---

<div class="post-metadata">

**Author:** ![joema](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@joema](https://community.solid-run.com/u/joema)\
**Post date:** [August 3, 2023, 1:48pm UTC](https://community.solid-run.com/t/u-boot-doesnt-set-dpmac-1/698/2 "2023-08-03T13:48:31Z")

</div>

it seems u-boot/arch/arm/dts/fsl-lx2160a-cex7-8-x-x.dts sets only dpmac3 - dpmac10 and dpmac17:

&dpmac3 {  
status = “okay”;  
phy-connection-type = “xgmii”;  
};

&dpmac4 {  
status = “okay”;  
phy-connection-type = “xgmii”;  
};

&dpmac5 {  
status = “okay”;  
phy-connection-type = “xgmii”;  
};

&dpmac6 {  
status = “okay”;  
phy-connection-type = “xgmii”;  
};

&dpmac7 {  
status = “okay”;  
phy-connection-type = “xgmii”;  
};

&dpmac8 {  
status = “okay”;  
phy-connection-type = “xgmii”;  
};

&dpmac9 {  
status = “okay”;  
phy-connection-type = “xgmii”;  
};

&dpmac10 {  
status = “okay”;  
phy-connection-type = “xgmii”;  
};

&dpmac17 {  
status = “okay”;  
phy-handle = \<&rgmii\_phy1\>;  
phy-connection-type = “rgmii-id”;  
};

---

<div class="post-metadata">

**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\
**Post date:** [August 7, 2023, 4:41am UTC](https://community.solid-run.com/t/u-boot-doesnt-set-dpmac-1/698/3 "2023-08-07T04:41:07Z")

</div>

Yes, this will need to be adjusted for different networking configurations.

---

<div class="post-metadata">

**Author:** ![joema](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@joema](https://community.solid-run.com/u/joema)\
**Post date:** [August 7, 2023, 5:01am UTC](https://community.solid-run.com/t/u-boot-doesnt-set-dpmac-1/698/4 "2023-08-07T05:01:26Z")

</div>

just add something like the below?

&dpmac1 {  
status = “okay”;  
phy-connection-type = “xgmii”;  
};

---

<div class="post-metadata">

**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\
**Post date:** [August 7, 2023, 5:03am UTC](https://community.solid-run.com/t/u-boot-doesnt-set-dpmac-1/698/5 "2023-08-07T05:03:59Z")

</div>

and remove the interfaces that it will replace. These can be referenced in the LX2610a reference manual in the SERDES configuration section.

---

<div class="post-metadata">

**Author:** ![joema](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@joema](https://community.solid-run.com/u/joema)\
**Post date:** [August 7, 2023, 5:13am UTC](https://community.solid-run.com/t/u-boot-doesnt-set-dpmac-1/698/6 "2023-08-07T05:13:27Z")

</div>

thanks!
