You copied the Doc URL to your clipboard.

B.1. About the .nv files

Some ARM networking products require various types of configuration to occur on the target system at run time. For example:

  • TCP/IP needs to know either its own IP address or whether an IP address is to be picked from a DHCP server.

  • DHCP server needs to know the IP address pools.

These values can be specified in .nv files. These files are plain text files that can be easily read and modified by a human operator. Each data item occupies one line of text. The name of the data item is first on the line. Every data item name ends with a colon character. The text after the colon is the data; usually an IP address, numeric parameter, or text string.

Note

A pattern-match is performed on the parameter names, so the end-user must be informed that these must not be changed.

All sample applications (Appendix C Sample Applications) read parameters from a primary .nv file and some of these applications also read parameters from secondary .nv file(s).

Primary .nv file

The primary file used depends upon the options that have been defined when building a target. Any one of the following files may be used:

ether.nv

Used when USE_PPP is undefined, that is, for ethernet-compatible targets.

direct.nv

Used when USE_PPP and DIRECT_RAS are defined, that is, where PPP is used over a serial link.

dialup.nv

Used when USE_PPP is defined and DIRECT_RAS is undefined, that is, where PPP is used over a modem.

The parameters documented in Primary .nv file parameters are all for use in primary .nv files.

Secondary .nv file(s)

The secondary .nv file(s) can be used by an application, depending on which products are implemented in the application. Secondary .nv files and their contents are described in Secondary .nv file parameters.

Was this page helpful? Yes No