Difference between revisions of "DESK-MX9-L/Deployment/MAC Address programming"
| Line 3: | Line 3: | ||
!colspan="4" style="width:100%; text-align:left"; border-bottom:solid 2px #ededed"|History | !colspan="4" style="width:100%; text-align:left"; border-bottom:solid 2px #ededed"|History | ||
|- | |- | ||
| − | ! style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#ededed; padding:5px; color:#000000" |2024/01 | + | !style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#73B2C7; padding:5px; color:white"|Issue Date |
| − | + | !style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#73B2C7; padding:5px; color:white"|Notes | |
| + | |- | ||
| + | | style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#ededed; padding:5px; color:#000000" |2024/02/01 | ||
| + | | style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#ededed; padding:5px; color:#000000" |Preliminary DESK-MX9-L-5.0.0 documentation | ||
|} | |} | ||
<section end=History/> | <section end=History/> | ||
__FORCETOC__ | __FORCETOC__ | ||
| + | <section begin=Body/> | ||
| − | + | [[File:TBD.png | thumb| center | 600px| This page is still in progress...]] | |
== MAC Address programming == | == MAC Address programming == | ||
| Line 21: | Line 25: | ||
=== Platform supported=== | === Platform supported=== | ||
| − | In this Application Note, we will describe how to use the i. | + | In this Application Note, we will describe how to use the i.MX93x eFuse for programming and using the MAC address(es). |
| − | |||
{{ImportantMessage|text=This Application Note has been validated in the [[AURA SOM | AURA SOM]]. The commands used have been not validated in the other platform yet.}} | {{ImportantMessage|text=This Application Note has been validated in the [[AURA SOM | AURA SOM]]. The commands used have been not validated in the other platform yet.}} | ||
| Line 32: | Line 35: | ||
=== Permanent storage areas === | === Permanent storage areas === | ||
| − | Some SOCs provide programmable OTPs for security, MAC | + | Some SOCs provide programmable OTPs for security, MAC addresses, boot modes, etc. Usually, some of these are general-purpose registers and can be managed by the user. |
| − | In other cases, an external permanent storage device can be used for storing permanent settings like the MAC address: for the i. | + | In other cases, an external permanent storage device can be used for storing permanent settings like the MAC address: for the i.MX93x product family, DAVE proposes to use the ''General Purposes eFuses'' (OTP blocks) on SoC itself for storing permanently the MAC address(es). |
| − | === MAC address programming on i. | + | === MAC address programming on i.MX93x family === |
==== MAC address configuration in u-boot==== | ==== MAC address configuration in u-boot==== | ||
| Line 55: | Line 58: | ||
==== eFuse bank registers ==== | ==== eFuse bank registers ==== | ||
| − | i. | + | i.MX93x family uses the Bank39 Word3, Word4, and Word5 (if the SoC has two ethernet interfaces) for storing the MAC addresses. The MAC values should be properly divided into the three registers for correct programming. |
| − | {{ImportantMessage|text='''Warning!!''' eFuse programming is a permanent and non reversible action. Pay attention to the values and commands used during MAC programming.}} | + | {{ImportantMessage|text='''Warning!!''' eFuse programming is a permanent and non-reversible action. Pay attention to the values and commands used during MAC programming.}} |
==== eth0 eFuse programming ==== | ==== eth0 eFuse programming ==== | ||
| − | U-Boot uses the <code>fuse prog</code> command for writing the MAC address into the eFuse. The MAC address should be divided | + | U-Boot uses the <code>fuse prog</code> command for writing the MAC address into the eFuse. The MAC address should be divided into high 16 bits and low 32 bits. For example MAC address <code>AB:CD:12:34:56:78</code> for eth0 is then divided into: |
<pre> | <pre> | ||
| Line 121: | Line 124: | ||
==== eFuse locking ==== | ==== eFuse locking ==== | ||
| − | The OTP eFuse registers should be locked | + | The OTP eFuse registers should be locked to avoid unwanted registers (and then MAC addresses) modifications. OTP lock grants that the MAC values cannot be modified anymore. |
{{ImportantMessage|text=If not locked yet, OTP bits can be set to ''''1'''' but not reversed to ''''0'''' value, so some modifications can be applied if the eFuse registers are not locked.}} | {{ImportantMessage|text=If not locked yet, OTP bits can be set to ''''1'''' but not reversed to ''''0'''' value, so some modifications can be applied if the eFuse registers are not locked.}} | ||
| − | + | [[File:TBD.png | 200px]] | |
==== eFuse reading ==== | ==== eFuse reading ==== | ||
| Line 169: | Line 172: | ||
root@desk-mx93:~# | root@desk-mx93:~# | ||
</pre> | </pre> | ||
| + | |||
| + | <section end=Body/> | ||
Revision as of 09:54, 1 February 2024
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
| History | |||
|---|---|---|---|
| Issue Date | Notes | ||
| 2024/02/01 | Preliminary DESK-MX9-L-5.0.0 documentation | ||
Contents
MAC Address programming[edit | edit source]
Every network adapter has a Media Access Control address (usually shortened to MAC address). A MAC address is a six-byte identifying number permanently embedded in the firmware of the adapter, and is readable by the network and the operating system of the device on which the adapter is installed.
The address must follow the standards set by the Institute of Electrical and Electronics Engineers (IEEE), which sets computer networking standards.
The MAC address is a six-pair set of hexadecimal numbers, for example a1-c2-e3-44-5f-6d. Specifically, in Ethernet, the MAC address is known as the Ethernet Address, which is the unique ID serial number of the Ethernet device in one's computer. MAC Addresses are used in a Local Area Network (LAN) by computers to communicate with each other. Every adapter has a unique MAC address.
Platform supported[edit | edit source]
In this Application Note, we will describe how to use the i.MX93x eFuse for programming and using the MAC address(es).
 This Application Note has been validated in the AURA SOM. The commands used have been not validated in the other platform yet. |
Obtaining a MAC address[edit | edit source]
To obtain a MAC address for your organization, please refer to our Setting the MAC address wiki page with the overall information about this topic.
Permanent storage areas[edit | edit source]
Some SOCs provide programmable OTPs for security, MAC addresses, boot modes, etc. Usually, some of these are general-purpose registers and can be managed by the user.
In other cases, an external permanent storage device can be used for storing permanent settings like the MAC address: for the i.MX93x product family, DAVE proposes to use the General Purposes eFuses (OTP blocks) on SoC itself for storing permanently the MAC address(es).
MAC address programming on i.MX93x family[edit | edit source]
MAC address configuration in u-boot[edit | edit source]
If the MAC address is not already programmed in the OTPs and the ethaddr u-boot variable is not set, u-boot assignes a random value (different at every power on cycle):
Net: Warning: ethernet@428a0000 (eth1) using random MAC address - 56:ea:aa:42:d2:0e eth1: ethernet@428a0000 [PRIME]
If the ethaddr is set and saved in the u-boot environment, its value is used as the MAC Address:
u-boot=> setenv ethaddr 00:50:c2:1e:af:a8 u-boot=> saveenv Saving Environment to MMC... Writing to MMC(1)... OK u-boot=>
eFuse bank registers[edit | edit source]
i.MX93x family uses the Bank39 Word3, Word4, and Word5 (if the SoC has two ethernet interfaces) for storing the MAC addresses. The MAC values should be properly divided into the three registers for correct programming.
|
Warning!! eFuse programming is a permanent and non-reversible action. Pay attention to the values and commands used during MAC programming. |
eth0 eFuse programming[edit | edit source]
U-Boot uses the fuse prog command for writing the MAC address into the eFuse. The MAC address should be divided into high 16 bits and low 32 bits. For example MAC address AB:CD:12:34:56:78 for eth0 is then divided into:
fuse prog -y 39 3 0x12345678 fuse prog -y 39 4 0xABCD
In the following example the MAC address 00:50:c2:1e:af:a8 is stored in the SOC:
- (in case of presence) clear the
ethaddru-boot variable
u-boot=> setenv ethaddr u-boot=> saveenv Saving Environment to MMC... Writing to MMC(1)... OK
- program the MAC address in the OPTs with the following commands:
u-boot=> fuse prog 39 3 c21eafa8
Programming bank 9 word 0x00000000 to 0xc21eafa8...
Warning: Programming fuses is an irreversible operation!
This may brick your system.
Use this command only if you are sure of what you are doing!
Really perform this fuse programming? <y/N>
y
u-boot=> fuse prog 39 4 0050
Programming bank 9 word 0x00000001 to 0x00000050...
Warning: Programming fuses is an irreversible operation!
This may brick your system.
Use this command only if you are sure of what you are doing!
Really perform this fuse programming? <y/N>
y
u-boot=>
If you want to write the eFuse value directly without confirmation, uses the -y parameter with the fuse prog command, as per the previous example:
u-boot=> fuse prog -y 39 3 c21eafa8 u-boot=> fuse prog -y 39 4 0050
At the next boot, the ethaddr value wil be read from the OPTs:
Warning: ethernet@428a0000 using MAC address from ROM eth0: ethernet@428a0000 Fastboot: Normal Normal Boot Hit any key to stop autoboot: 0 u-boot=> print ethaddr ethaddr=00:50:c2:1e:af:a8 u-boot=>
The warning message informs that the ethaddr is not present in the u-boot environment and it has been set using the value read from the OTPs. For clearing the warning, it is enough to save the environment with saveenv.
u-boot=> saveenv
eFuse locking[edit | edit source]
The OTP eFuse registers should be locked to avoid unwanted registers (and then MAC addresses) modifications. OTP lock grants that the MAC values cannot be modified anymore.
|
If not locked yet, OTP bits can be set to '1' but not reversed to '0' value, so some modifications can be applied if the eFuse registers are not locked. |
eFuse reading[edit | edit source]
The eFuse registers can be read - after programming - for checking the written values:
u-boot=> fuse read 39 3 Reading bank 39: Word 0x00000003: c21eafa8 u-boot=> fuse read 39 4 Reading bank 39: Word 0x00000004: 00000050 u-boot=> fuse read 39 5 Reading bank 39: Word 0x00000005: 0050c21e u-boot=>
Linux kernel MAC address[edit | edit source]
The MAC Address configured in u-boot is passed to the kernel which configures the eth0 and eth1 peripherals with the correct values:
root@desk-mx93:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:c2:1e:af:a8
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:82 errors:0 dropped:0 overruns:0 frame:0
TX packets:82 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6220 (6.0 KiB) TX bytes:6220 (6.0 KiB)
root@desk-mx93:~#
