User's Manual

Table Of Contents
iChip Parameter Update
AT+i Programmer‘s Manual Version 8.32 26-1
26 iChip Parameter Update
26.1 Introduction
The iChip remote parameter update file allows users to remotely modify various non-
volatile parameters in iChip products. The file is an ASCII-formatted text file, edited by
the user or created by a dedicated application. The file‘s size must not exceed 10k.
The remote parameter file (RPF) naming convention is <filename>.rpf. If a parameter is
assigned a legal value within the file, that value replaces the current value in iChip‘s non-
volatile parameter database. A parameter value that is not referred to in the file, or that is
not defined using the correct syntax rules, specified below, does not affect the current
parameter value.
26.2 Remote Parameter File (RPF) Structure
The RPFfile must include the letters ―RP_‖ as its first 3 characters, and can include
additional header lines (defined below), as well as various parameter assignments.
Assignments follow the rules defined for parameter settings, but excluding the AT+i
prefix. For example, to assign the value myname to the POP3 mailbox name parameter,
the correct assignment is MBX=myname This is equivalent to the host sending
AT+iMBX=myname to iChip. Each line, terminated with <CR>/<LF>, can contain one
assignment only. The order of assignments is not important, except for the RPF header
parameters, which must be first and must follow the header definitions below. After the
first non-RPF header parameter, additional header parameters are ignored.
Comment lines can appear anywhere in the file. Comment line syntax is defined as:
#<anything>CR/LF
The first line in the file that is not a comment line is considered the authentication header
line and must have the following syntax:
RP_[GROUP=<string><space_character>][RP_DEST=<string>]CR/LF
The remainder of the header must contain lines with the following syntax:
<header_parameter_name>=<general_parameter_value>CR/LF