Product Description

nanoBTS Product Description Software Specification

5.11 Peripherals

5.11.1 Backhaul

5.11.1.1 Miscellaneous

The BTS contains a Fast Ethernet Controller IC (FEC) with 10/100 mbps auto-negotiation

(auto-negotiation occurs without needing to reboot).

5.11.1.2 EEPROM Storage

The EEPROM structure is protected against bit error using a CRC check mechanism.

5.12 NV Configuration

5.12.1 Parameters

The NV management state model for each parameter is as shown in Figure 8. All

attributes are initially in the "illegal" state. This means that the store is completely invalid. If

the store is "illegal" when the software starts up then its structure is written and all

attributes are "defaulted".

Type 1 attributes will be "initialised" and cannot be "modified", for example the MAC

address. Type 2 attributes can be "modified", for example whether DHCP is enabled. To

prevent changing read-only "initialised" values, if the OEMid value is non-null (has been

"initialised") then write access to Type 1 attributes is denied. Given this model, the factory

code requirements can be achieved using a single software image and a single defined

use of the dongle.

ILLEGAL

INITIALISED

DEFAULTED

MODIFIED

corruption

default

initialise

modify

reset (if not retained)

modify (if retained)

Figure 8 - NV configuration model

All attributes listed in Table 4 with "Initialised? == Y" are assumed to be type 1 attributes

and cannot be overridden once OEMid has been set in the factory (except for the case of

"OCXO DAC Value" which can be adjusted using the SetNVAttributes message or as a

result of a frequency synchronisation test using NWL). For returned units in the factory, the

OemID can be overridden with a special command (see FAT_017).