LMX9830SMX National Semiconductor, LMX9830SMX Datasheet - Page 28

• Manufacturer Part Number: LMX9830SMX
• Manufacturer: National Semiconductor

Specifications of LMX9830SMX

• Lead Free Status / Rohs Status: Not Compliant

www.national.com
11.0 Integrated Firmware
The LMX9830 includes the full Bluetooth stack up to RF-
Comm to support the following profiles:
•
•
•
Figure 12 shows the Bluetooth protocol stack with command
interpreter interface. The command interpreter offers a num-
ber of different commands to support the functionality given
by the different profiles. Execution and interface timing is han-
dled by the control application.
The chip has an internal data area in RAM that includes the
parameters shown in Table 22.
11.1 FEATURES
11.1.1 Operation Modes
On boot-up, the application configures the module following
the parameters in the data area.
Automatic Operation
No Default Connections Stored:
In Automatic Operation the module is connectable and dis-
coverable and automatically answers to service requests.
The command interpreter listens to commands and links can
be set up. The full command list is supported.
If connected by another device, the module sends an event
back to the host, where the RFComm port has been connect-
ed, and switches to transparent mode.
Default Connections Stored:
If default connections were stored on a previous session,
once the LMX9830 is reset, it will attempt to connect each
device stored within the data RAM three times. The host will
be notified about the success of the link setup via a link status
event.
Non-Automatic Operation
In Non-Automatic Operation, the LMX9830 does not check
the default connections section within the Data RAM. If con-
GAP (Generic Access Profile)
SDAP (Service Discovery Application Profile)
SPP (Serial Port Profile)
FIGURE 12. LMX9830 Software Implementation
20180020
28
nected by another device, it will NOT switch to transparent
mode and continue to interpret data sent on the UART.
Transparent Mode
The LMX9830 supports transparent data communication from
the UART interface to a bluetooth link.
If activated, the module does not interpret the commands on
the UART which normally are used to configure and control
the module. The packages don’t need to be formatted as de-
scribed in Table 24. Instead all data are directly passed
through the firmware to the active bluetooth link and the re-
mote device.
Transparent mode can only be supported on a point-to-point
connection. To leave Transparent mode, the host must send
a UART_BREAK signal to the module.
Force Master Mode
In Force Master mode tries to act like an Accesspoint for mul-
tiple connections. For this it will only accept the link if a Master/
slave role switch is accepted by the connecting device. After
successful link establishment the LMX9830 will be Master
and available for additional incoming links. On the first incom-
ing link the LMX9830 will switch to transparent depending on
the setting for automatic or command mode. Additional links
will only be possible if the device is not in transparent mode.
11.1.2 Default Connections
The LMX9830 supports the storage of up to 3 devices within
its NVS. Those connections can either be connected after re-
set or on demand using a specific command.
11.1.3 Event Filter
The LMX9830 uses events or indicators to notify the host
about successful commands or changes at the bluetooth in-
terface. Depending on the application the LMX9830 can be
configured. The following levels are defined:
•
•
•
11.1.4 Default Link Policy
Each Bluetooth Link can be configured to support M/S role
switch, Hold Mode, Sniff Mode and Park Mode. The default
link policy defines the standard setting for incoming and out-
going connections.
11.1.5 Audio Support
The LMX9830 offers commands to establish and release syn-
chronous connections (SCO) to support Headset or Hands-
free applications. The firmware supports one active link with
all available package types (HV1, HV2, HV3), routing the au-
dio data between the bluetooth link and the advanced audio
interface. In order to provide the analog data interface, an ex-
ternal audio codec is required. The LMX9830 includes a list
of codecs which can be used.
No Events:
– The LMX9830 is not reporting any events. Optimized for
passive cable replacement solutions.
Standard LMX9830 events:
– Only necessary events will be reported
All events:
– Additional to the standard all changes at the physical
layer will be reported.