User's Manual

SC14CVMDECT SF Cordless Voice Module
© 2012 Dialog Semiconductor B.V. 40 July 1, 2014 v1.6
7.0 Design guidelines
This section describes the software and hardware con-
siderations to be taken into account when designing
the target application.
The SC14CVMDECT SF can be used standalone or
next to an MCU that controls the module. In case the
module is used standalone the application will be
stored in its on-board Flash. In total 324 kB of Flash is
available for this purpose.
Applications can be developed with the Athena soft-
ware development environment (see reference [3]).
7.1 APPLICATION SOFTWARE FOR PP
In a PP application the following software tasks must
be handled by the MCU or within the module itself:
• UART communication (external microprocessor
only)
• PP MMI
• Display interface (optional)
• Keyboard interface (optional)
• Battery Charge interface (optional)
• Audio handling
• Tone / Melodies handling
For control commands see document reference [2].
UART communication
The UART communication is the main control interface
of the SC14CVMDECT SF.
PP MMI
The MMI state machine must handle the call setup and
call termination on the PP.
Display Interface
The MCU / PP handles the display interface including
the display driver.
Keyboard Interface
The MCU/ PP handles the keyboard interface including
the keyboard driver.
Audio handling
The Application Software state machine must control
when to open and close the audio. The headset plug-in
detection must handled by the host, and a status is
send to the PP MMI from the PP stack software. The
PP MMI must handle the volume control.
Headset detection boundaries can be adjusted in VES.
When headset indication is received from the PP
Headset detection logic, the Application Software can
decide if audio should be switched to the headset and
sends a request to the PP stack software.
The PP audio handling basically consists of 4 audio
modes (see Figure 14):
1. Idle (Alert) mode
2. Earpiece mode
3. Handsfree mode (Speakerphone)
4. Headset mode
Shifting between modes is done through the API.
Tone handling
The Application Software state machine must control
when to play tones and the volume setting. Custom
melodies can be defined in the VES.
7.2 APPLICATION SOFTWARE FOR FP
In an FP application the following software tasks must
be handled by the MCU or within the module itself:
• UART communication (external microprocessor
only)
•FP MMI
• Display interface (optional)
• Keyboard interface (optional)
• Audio handling
• Tone / Melodies handling
For control commands see document reference [1].
UART communication
The UART communication forms the basic of the FP
operation because via this interface the
SC14CVMDECT SF is controlled.
FP MMI
The MMI state machine must handle the call setup and
call termination on the FP.
Display interface
The MCU/ FP handles the display interface including
the display driver.
Keyboard interface
The MCU/ FP handles the keyboard interface including
the keyboard driver.
Audio handling
The Application Software state machine must control
when to open and close the audio. The FP MMI must
handle the volume control.
Tone handling
The Application Software state machine must control
when to play tones and the volume setting. Custom
melodies can be defined in VES.
7.3 HARDWARE DESIGN GUIDELINES
Within this section general design guidelines for
SC14CVMDECT SF FP and PP applications are given.
7.3.1 Circuit design guidelines
For a reference schematic refer to the SC14CVMDECT
SF reference kit. With the reference kit package a non-
cost optimised reference design is presented.