System Memory Management - Samsung OfficeServ 7400 Technical Manual

OfficeServ 7400
TECHNICAL MANUAL

1.3 SYSTEM MEMORY MANAGEMENT

In previous OfficeServ Systems such as the OfficeServ 100, 500, and 7200, SRAM
memory stored the active system database and Smart Media was where the Database
was saved on a more permanent basis. The SRAM was battery-backed on the MCP
card by a super-capacitor with a battery backup switch which could clear the memory
and default the system. However, the memory architecture of the OfficeServ 7400 is
considerably different.
The OS7400 has 4 types of memory:
1) SRAM (2MB): Holds information such as Call Logs, Alarms, UCD call stats,
program logs and traffic reports. SRAM is backed by the Super Capacitor on the
MP40. If the switch is ON, data can last up to 12 hours without main system power.
The SRAM DOES NOT STORE THE SYSTEM DATABASE.
2) DRAM: This is where active system Database resides. During WebMMC or KMMC
programming, the data being programmed is written to DRAM.
DRAM IS CLEARED WHEN SYSTEM BOOTS. During system boot up, the latest
NAND FLASH contents are reloaded into DRAM.
3) NAND FLASH: A more permanent memory that will hold the system database for
many years. During WebMMC or KMMC programming, the data being
programmed is written to DRAM. The database will be written from DRAM to NAND
FLASH upon the following conditions:
- 5 minutes after a system boot
- From that point every 15 minutes
- When you log out of WebMMC or KMMC (mmc 800 disable)
- When KMMC or WebMMC lockout timer expires
- MMC 811 restart
4) SMART MEDIA (32MB): When you use MMC 815 and save the Database to Smart
Media, it copies the active Database from DRAM and saves it to Smart Media. This
way the most up-to-date database is saved to Smart media.
WHAT THIS MEANS TO YOU?
From the information described above, you can see that if you made a
programming change in KMMC and pressed the right soft key to save, the change
is made immediately to DRAM and the change takes effect immediately. Likewise, if
you make a programming change using WebMMC and click the SAVE button, the
change is effective immediately and is saved to DRAM active system database.
However, once the change is saved in DRAM, if the system reboots before one of
the events listed in item 3 above occurs, then you will lose the changes you just
made. This is because the changes never got a chance to write from DRAM to
1.3.1
Table of Contents
Home Page
PROGRAMMING
PART 1 JUNE 2006