beautypg.com

2 ram/data memory, 3 build configuration, 1 flash/code and ram size – Maxim Integrated 78M6612 M-API Library User Manual

Page 11: Ram/data memory, Build configuration, Flash/code and ram size

background image

UG_6612_036

78M6612 M-API Library User Guide

Rev. 1.00

11

3.2.2 RAM/Data Memory

The 78M6612 has 2K bytes of Data Memory for exclusive use by the embedded 80515 MPU library and
application layers. In addition, there are 512 bytes reserved for the Compute Engine.

Table 3: Data RAM Shared by CE and MPU

Address (hex)

Type

Typical Usage

Size (bytes)

0000-07FF

Volatile

MPU data XRAM,

2KB

1000-11FF

Volatile

CE data

512

2000-20FF

Volatile

Miscellaneous I/O RAM
(configuration RAM)

256

3.3 Build Configuration

The accompanying example application source code has been set up to link to each library under specific
hardware configuration. Each configuration is defined under a different ‘Target’. However, for all ‘Targets’,
specific area of Flash is reserved for specific function as described below.

3.3.1 Flash/Code and RAM Size

The attached zipped file (78M6612MAPIv200.zip) contains a sample Application code, of which source
code is also included. The functions of this application are detailed in

Section 6

.


This sample application is taking up Flash/RAM usage according to the table below. It was written to
demonstrate the use of the MAPI libraries via two types of commands: the ‘M’ commands (as shown in

Section 6

) to specifically address the MAPI calls; and the ‘CLI’, aka Command Line Interface, commands

for backward compatibility to support those who have evaluated, or are familiar with, Teridian OMU
products in the past.

The following tables show RAM and Flash consumptions by this sample application. They also show a
breakdown of Flash consumption by different features as implemented in the MAPI libraries.

Table 4: Flash and RAM Consumption by MAPI and Sample Application

Firmware Module

RAM

Used

Flash Used

Note

6612S22_WB_MAPI.lib
6612S22_NB_MAPI.lib

~

26K

The RAM usage is overlay-able. See the
breakdown of Flash usage in Table 5.

6612IVIV_50F0_v200WB.hex
6612IVIV_50F0_v200NB.hex

1.7K

6K + 26K(lib)

The app from this build uses every single API
library call.

Table 5: Breakdown of M-API’s Flash Consumption

Library:

6612S22_WB_MAPI.lib

6612S22_NB_MAPI.lib

Flash Used

Features

Calibration

5.7K

Includes calibration for: Temperature, Current, Voltage,
Watt and Phase.

Initialization, Default Settings

5.8K

Initializes Defaults, Metering Constants Tables,
Registers, etc.

MAPI Interface (to App)

1.5K

Direct interface to the library from application.

Flash Manager

2K

Flash Read/Write management.