User Manual
1 Solution Overview
1.1 ABSTRACT
TNETW1350/A-based WLAN subsystems (WLS) are intended for inclusion in larger
systems that already contain non-volatile storage (NVS). Because of this, NVS via an
EEPROM is not necessary and not included in TNETW1350/A-based WLSs. In addition,
the TNETW1350/A, by design, does not support a serial EEPROM interface. However,
unique NVS data for each TNETW1350/A-based WLS, such as calibration parameters,
MAC address, etc., is still required. This application note describes how to generate and
store this unique NVS data, how to match specific NVS data files with specific
TNETW1350/A-based WLSs, and how to transfer this NVS data to the NVS of the
complete RG system. This is an EEPROMless solution, as all of these operations are
accomplished without a local EEPROM in the WLS.
1.2 Assumptions
This EEPROMless solution presented in this application note assumes the following:
‧ A residential gateway motherboard and a WLAN subsystem (WLS) daughterboard
make up a complete residential gateway (RG) system.
‧
The two boards are manufactured separately before being assembled into the
complete RG system.
‧ The WLS is calibrated during its separate manufacturing process.
‧
The WLS EEPROM map is referred to as the NVS data file.
‧ The NVS device (flash) is on the RG motherboard.
1.3 Solution Summary
The EEPROMless solution consists of two main parts: the WLS manufacturing test
process and the RG manufacturing process. During the
WLS manufacturing test
process
, the WLS must be calibrated and the NVS data must be saved to an external
binary file. Each unique binary file will be identified with the correct WLS by using the
DIE_ID register value of the TNETW1350/A – this DIE_ID value will be part of the binary
file name.
Note: The DIE_ID register is programmed with a unique 64-bit value (16 Hex characters)
for each TNETW1350/A chip during manufacturing.
During the RG manufacturing process, the correct NVS data file from the WLS
manufacturer must be transferred to the NVS of the complete RG system. This will be
accomplished during the first boot by means of a TFTP server/client model, in which the
server runs on the test PC and the client is part of the APDK running on the complete
RG system. The DIE_ID of the TNETW1350/A will be read, and the TFTP client will
automatically download the correct NVS data file from the server (which has access to