Software architecture
28/70
FDL Content: MAC Addresses for application side
The following table shows the section of the FDL that holds the
MAC
Addresses for the application side
; i.e. the MAC addresses to be used
by the application CPU. These MAC addresses can be set individually for
each device during production.
Note:
Whether the application side needs its own MAC addresses or not,
depends on the requirements of the application firmware running on
the APP CPU. Ask your application developer if this is the case.
Offset
Size
(bytes)
Data type
Name
Description/comments/values
112
6
UINT8[6]
MAC address 1
1st. MAC Address
118
2
UINT8[2]
Reserved fields 1
2 bytes, reserved for alignment, set to
0
120
6
UINT8[6]
MAC address 2
2nd. MAC Address
126
2
UINT8[2]
Reserved fields 2
2 bytes, reserved for alignment, set to
0
128
6
UINT8[6]
MAC address 3
3rd. MAC Address
134
2
UINT8[2]
Reserved fields 3
2 bytes, reserved for alignment, set to
0
136
6
UINT8[6]
MAC address 4
4th. MAC Address
142
2
UINT8[2]
Reserved fields 4
2 bytes, reserved for alignment, set to
0
Table 13: FDL Content: MAC Addresses for application side
FDL Content: Product identification
The following table shows the section of the FDL that holds the
Product
identification
; i.e. various IDs that could be assigned to “built-in
interfaces” (like e.g. USB), which are not assigned by Hilscher. Note that
the netX 90 has no internal USB interface, therefore all values must be set
to zero.
Offset
Size
(bytes)
Data type
Name
Description/comments/values
144
2
UINT16
USB Vendor ID
(VID)
Not used, set to
0
146
2
UINT16
USB Product ID
(PID)
148
16
UINT8[16]
USB Vendor
Name
164
16
UINT8[16]
USB Product
Name
180
76
UINT8[76]
Reserved fields
Table 14: FDL Content: Product identification
netX 90 | Production guide
DOC190101PG03EN | Revision 3 | English | 2019-07 | Released | Public
© Hilscher 2019