Specifications

AN93
Rev. 0.8 57
Detailed EEPROM Examples
EEPROM Data is stored and read in hex ascii format in
eight address blocks beginning at a specified hex
address. For example, the
AT:M0000,y0,y1,y2,y3,y4,y5,y6,y7 command writes the
hex values y0…y7 at the hex addresses from 0000 to
0007, respectively. The AT:E0000 command reads the
hex values y0…y7 from the hex addresses 0000 to
0007, respectively.
Boot Commands (custom defaults)
Commands to be executed upon boot-up are stored
between the heading “BOOT” and the first <CR><CR>
delimiter. The boot command has the following format:
BOOT<CR>
<commands><CR>
:<commands><CR>
<CR>
The commands end with a <CR> which, in combination
with the final<CR>, provides the <CR><CR> delimiter.
Boot commands must be the first entry in the EEPROM
and are used to set the modem up with custom defaults,
such as settings for specific countries, auto answer, or
other special settings upon power-up or after a
hardware or software reset. This saves the host
processor from reloading special configuration strings at
power up or after a reset and allows the modem to be
customized by programming the EEPROM or
substituting pre-programmed EEPROMs. If the BOOT
command is the final entry in the EEPROM, it must end
with an additional <CR> to provide the
<CR><CR><CR> delimiter indicating the end of the
EEPROM.
AT Command Macros (customized AT commands)
Macros allow the creation of single custom AT
commands that execute combinations of default AT
commands including special register configurations. AT
command macros have the following format:
<command name><CR>
<commands><CR>
<commands><CR>
<CR>
Each AT Command Macro ends with a <CR><CR>. The
final entry in the EEPROM ends with an additional
<CR> to provide the <CR><CR><CR> delimiter
indicating the end of the EEPROM.
Firmware Upgrades
Firmware upgrades (“patches”) are typically executed
upon boot-up and stored between the heading “BOOT”
and the first <CR><CR> delimiter. A firmware upgrade
has the format: BOOT<firmware upgrade><CR>. The
firmware upgrade ends with a <CR> which, in
combination with the final<CR> provides the
<CR><CR> delimiter. Firmware upgrades could also be
stored as an AT command macro if there are cases
when using the firmware upgrade is optional.
The following are examples of Boot commands, AT
command macros, and automatically-loaded firmware
upgrades.
Boot Command Example
On power-up or reset, it is desired to set the UART rate
to 115.2 Kbps and limit the Si2493/57/34/15/04 to V.34
and lower operation.
The AT commands required to do this manually are:
AT\T12<CR>
AT&H2<CR>
To implement this as a Boot Command, the commands
are:
BOOT<CR>
AT\T12<CR>
AT&H2<CR>
<CR>
This must be written to the EEPROM as ascii hex in
eight (8) address blocks. The actual AT commands to
store this boot command in the EEPROM starting at hex
address 0000 are:
AT:M0000,42,4F,4F,54,0D,41,54,5C
AT:M0008,54,31,32,0D,41,54,26,48
AT:M0010,32,0D,0D,00,00,00
Note that 41h corresponds to the display character, A,
54h to T, 42 to B, 4F to O etc., and the value 0D for
carriage return corresponds to the decimal value 13
stored in S-Register 3 (S3). Table 31 shows the
relationship between the decimal values, hex values,
and display characters.
AT Command Macro Example
This example creates an AT command macro,
ATN<CR>, to configure the Si2493/57/34/15/04 for
operation in Norway.
The AT commands required to do this manually are:
AT:U2C,00B0,0080<CR>
AT:U67,000C,0010,0004<CR>
AT:U4D,001<CR>
To implement this as an AT command macro, the
EEPROM contents should be:
N<CR>
AT:U2C,00B0,0080<CR>