iPod IWIP3G User Guide - Page 12

Introduction

Page 12 highlights

1. INTRODUCTION iWRAP is an embedded firmware running entirely on the RISC processor of WRAP THOR modules. It implements the full Bluetooth protocol stack, and many Bluetooth profiles as well. All software layers, including application software, run on the internal RISC processor in a protected user software execution environment known as a Virtual Machine (VM). The host system can interface to iWRAP firmware through one or more physical interfaces, which are also shown in the figure below. The most common interfacing is done through the UART interface by using the ASCII commands that iWRAP firmware supports. With these ASCII commands, the host can access Bluetooth functionality without paying any attention to the complexity, which lies in the Bluetooth protocol stack. GPIO interface can be used for event monitoring, command execution and PCM, SPDIF, I2S or analog interfaces are available for audio. The available interfaces depend on the used hardware. The user can write application code to the host processor and DSP to control iWRAP firmware with ASCII commands or GPIO events. In this way, it is easy to develop Bluetooth enabled applications. The DSP processor is only available on WT32 Bluetooth module. Bluetooth stack + iWRAP iWRAP RFCOMM L2CAP HCI LM LC SDP WRAP THOR Bluetooth module + iWRAP firmware Host RAM USB UART Host I/O GPIO / AIO PCM / SPDIF / I2S Analog audio Audio I/O Baseband MCU cmd & data channel DSP processor (WT32 only) Radio Physical hardware Figure 1: iWRAP Stack 12

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211

12
1.
INTRODUCTION
iWRAP is an embedded firmware running entirely on the RISC processor of WRAP THOR
modules. It implements the full
Bluetooth
protocol stack, and many
Bluetooth
profiles as
well. All software layers, including application software, run on the internal RISC processor
in a protected user software execution environment known as a Virtual Machine (VM).
The host system can interface to iWRAP firmware through one or more physical interfaces,
which are also shown in the figure below. The most common interfacing is done through
the UART interface by using the ASCII commands that iWRAP firmware supports. With
these ASCII commands, the host can access
Bluetooth
functionality without paying any
attention to the complexity, which lies in the
Bluetooth
protocol stack. GPIO interface can
be used for event monitoring, command execution and PCM, SPDIF, I2S or analog
interfaces are available for audio. The available interfaces depend on the used hardware.
The user can write application code to the host processor and DSP to control iWRAP
firmware with ASCII commands or GPIO events. In this way, it is easy to develop
Bluetooth
enabled applications.
The DSP processor is only available on WT32
Bluetooth
module.
Audio I/O
Host I/O
Radio
RAM
Baseband MCU
LC
LM
HCI
L2CAP
RFCOMM
SDP
iWRAP
Host
PCM / SPDIF / I2S
Bluetooth stack + iWRAP
Physical
hardware
WRAP THOR
Bluetooth module
+
iWRAP firmware
Analog audio
GPIO / AIO
UART
USB
DSP processor
(WT32 only)
cmd & data
channel
Figure 1:
iWRAP Stack