Software architecture
26/70
FDL Content: Basic Device Data
The following table shows the section of the FDL that holds the
Basic
Device Data
; i.e. the identification data of the device.
Important:
Hilscher tools like the
Communication Studio
(though not the
Flasher tool) check some of these IDs for conformity against the IDs
contained in the File header (a.k.a. “device header”) of the *
.nxi
communication firmware before downloading the firmware to the
device. If these IDs do not match, the Hilscher tool will refuse to
download the COM firmware.
The same applies to the *
.mxf
maintenance firmware, which
manages firmware updates on the netX: It also checks these IDs
and refuses to update the COM firmware if these IDs do not match.
We therefore strongly advise you not to change the preset default
values of the basic device data in the FDL. Change or customize
only the serial number and the production date.
Offset
Size
(bytes)
Data type
Name
Description/comments/values
16
2
UINT16
Manufacturer ID
Manufacturer ID managed and assigned by Hilscher. By
default, this field is filled with the code for Hilscher.
0
Undefined
1
Default code for Hilscher
2
...
255
Hilscher
256
...
65535
OEM ID
(managed and assigned to OEM by Hilscher)
18
2
UINT16
Device classification
number (device class)
0x003C
netX 90 (COM CPU)
0x0045
netX 90 (COM CPU) with SDRAM
20
4
UINT32
Device number
The numbers for Manufacturer
1
...
255
(Hilscher) are
managed by Hilscher.
Note
: Hilscher tools use Manufacturer ID, device class and
device number for identifying a device type. The tools display
the device type and add a serial number, thus making
devices individually identifiable (in case multiple devices are
connected to the tool at once).
24
4
UINT32
Serial number
Serial number of the device. To be defined and incremented
for each device during production by OEM.
28
1
UINT8
Hardware
compatibility number
Index indicating whether a hardware version is compatible
with a firmware version. The index starts with zero and is
incremented each time if changes made to the hardware
require the firmware to be changed (adapted) as well.
29
1
UINT8
Hardware revision
number
Index starts with
1
and is incremented each time if hardware
is changed.
30
2
UINT16
Production date
Format is
0xYYWW
:
Year
((usProductionDate >> 8) &
0x00ff) + 2000
Week
((usProductionDate >> 0) &
0x00ff)
Example
:
0C2Bh
(where
0Ch
is year 2012 and
2Bh
is week 43)
Note
: In the binary, the data is stored in
Little endian format
,
thus offset
30
contains the week and offset
31
the year.
32
16
UINT8[16]
Reserved fields
Currently not used, set to
0
Table 11: FDL Content: Basic Device Data
netX 90 | Production guide
DOC190101PG03EN | Revision 3 | English | 2019-07 | Released | Public
© Hilscher 2019
