-
Notifications
You must be signed in to change notification settings - Fork 1
/
README.txt
945 lines (678 loc) · 40.7 KB
/
README.txt
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
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
Texas Instruments, Inc.
CC2540/41 Bluetooth Low Energy Software Development Kit
Release Notes
Version 1.4.0
November 8, 2013
Notices:
- This version of the Texas Instruments BLE stack and software is a minor
update to the v1.3.2 release. It contains some minor bug fixes and a few
functional changes.
- The BLE protocol stack, including both the controller and host, was
completely retested for v1.4.0.
Changes and Enhancements:
- All projects have been migrated from IAR v8.10.4 to IAR 8.20.2. In order to
build all projects, be sure to upgrade to IAR v8.20.2.
- Updated SPI and UART_DMA drivers for improved robustness and throughput.
- Added an overlapped processing feature to improve throughput and reduce power
consumption in devices where peak power consumption isn't an issue. Overlapped processing allows the stack to concurrently process while the radio
is active. Since the stack is concurrently processing, it is able to insert
new data in the Tx buffer during the connection event, causing additional
packets to be sent before the end of the event.
- Added a Number of Completed Packets HCI command which offers the possibility
of waiting for a certain number of completed packets before reporting to the
host. This allows higher throughput when used with overlapped processing.
- Added an HCI Extension command HCI_EXT_DelaySleepCmd which provides the user
control of the system initialization sleep delay (wake time from PM3/boot
before going back to sleep). The default sleep delay is based on the
reference design 32 kHz XOSC stabilization time.
- Added a low duty cycle directed advertising option.
- Added support for deleting a single bond with the GAP_BondSetParam command.
- Decreased CRC calculation time during OAD by using DMA.
Bug Fixes:
- Using a short connection interval and exercising high throughput, there was
some loss of packets. This was fixed by adding host to application flow control support.
- Bonding was unstable at short connection intervals. This is now fixed.
- Fixed USB CDC Drivers to work with Windows 8.
- OAD sample project would fail if long connection interval was used. This was fixed by not allowing parameter updates to the central device.
- Fixed linking errors in UBL project.
- Fixed minor issues in sample apps to work with PTS dongle.
- Fixed USB descriptors in HostTestRelease to display correct string.
Known Issues:
- Use of the NV memory (to save application data or BLE Host bonding
information) during a BLE connection may cause an unexpected disconnect.
The likelihood of this happening increases with frequent usage, especially
when using short connection intervals. The cause is related to the NV wear
algorithm which at some point may cause an NV page erase which can disrupt
system real-time processing. It is therefore recommended that the NV memory
be used sparingly, or only when a connection is not active.
- HCI packet size of 128 bytes or more will be disregarded by the stack, and as
such, no HCI event will be returned.
For technical support please visit the Texas Instruments Bluetooth low energy
E2E Forum:
http://e2e.ti.com/support/low_power_rf/f/538.aspx
For additional sample applications, guides, and documentation, visit the Texas
Instruments Bluetooth Low Energy wiki page at:
http://processors.wiki.ti.com/index.php/Category:BluetoothLE
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Version 1.3.2
June 13, 2013
Notices:
- This version of the Texas Instruments BLE stack and software is a minor
update to the v1.3.1 release. It contains some minor bug fixes and a few
functional changes.
- The BLE protocol stack, including both the controller and host, was
completely retested for v1.3.2. The profiles Running Speed and Cadence,
Cycling Speed and Cadence, and Glucose were fully tested and passed
certification. Other profiles with no code changes since 1.3.1 were sanity
tested only.
Changes and Enhancements:
- Added Running Speed and Cadence profile and service. An example application
demonstrating running speed and cadence is provided.
- Added Cycling Speed and Cadence profile and service. An example application
demonstrating cycling speed and cadence is provided.
- Added delay before performing Connection Parameter changes. Implemented
conn_pause_peripheral) and TGAP(conn_pause_central) timers as described in
CSA 3 rev 2, Gap Connection Parameters Changes, Section 1.12. Updated
HIDAdvRemote, HIDEmuKbd, KeyFob, SensorTag, and SimpleBLEPeripheral
applications.
- Update Privacy Flag and Reconnection Address characteristics permissions
(Erratum 4202)
- A new Windows USB CDC driver has been included in the installer. This new
driver is signed and is functional on Windows 8 systems.
Bug Fixes:
- Some minor updates to glucose sensor and collector were made.
- The gyroscope would draw continuous 6mA when enabled. The updated
code now performs a read and turns off the gyro after 60ms.
- The master’s host would accept invalid connection parameters requested
by the Slave, and would send back the Connection Parameter Update Response
with ‘parameters accepted’. The host now performs validation on these
parameters.
- When coming out of sleep, the HCI_EXT_ExtendRfRangeCmd would override
HCI_EXT_SetRxGainCmd setting and set it to default gain. This has been fixed.
Known Issues:
- Use of the NV memory (to save application data or BLE Host bonding
information) during a BLE connection may cause an unexpected disconnect.
The likelihood of this happening increases with frequent usage, especially
when using short connection intervals. The cause is related to the NV wear
algorithm which at some point may cause an NV page erase which can disrupt
system real-time processing. It is therefore recommended that the NV memory
be used sparingly, or only when a connection is not active.
- HCI packet size of 128 bytes or more will be disregarded by the stack, and as
such, no HCI event will be returned.
- The HAL SPI driver that was implemented since the v1.3 release can sometimes
hang, particularly in cases in which power management is used and when there
is heavy traffic on the SPI bus.
For technical support please visit the Texas Instruments Bluetooth low energy
E2E Forum:
http://e2e.ti.com/support/low_power_rf/f/538.aspx
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Version 1.3.1
April 18, 2013
Notices:
- This version of the Texas Instruments BLE stack and software is a minor
update to the v1.3 release. It contains some minor bug fixes, with no major
functional changes. It also contains two additional projects for the CC2541
Advanced Remote Control Kit.
- Since none of the profile source code was significantly changed since the
v1.3 release, no additional re-testing of the profiles and sample
application were done for v1.3.1. The only exception is the HID-over-GATT
profile, which was fully re-tested for this release. The BLE protocol stack,
including both the controller and host, was completely retested for v1.3.1.
Major Changes and Enhancements:
- The GAP parameter TGAP_LIM_ADV_TIMEOUT now uses units of seconds instead
of milliseconds.
- The HidAdvRemote Project has been added. This implements a full mouse-like
pointing functionality using motion and gesture control. The project runs on
the CC2541 BLE Advanced Control included as part of the CC2541DK-REMOTE kit.
The application implements the HID-over-GATT (HOGP) profile with a report
descriptor supporting the keyboard, mouse, and consumer control classes of
HID devices.
- The HidAdvRemoteDongle project has been added. This application runs on the
CC2540USB dongle, and implements partial functionality of HID-over-GATT
(HOGP) host with a fixed report descriptor to match that of the descriptor
of the HidAdvRemote Project. This means that the HidAdvRemoteDongle was
designed only to work with the HidAdvRemote, and will not be compatible
with any other HOGP devices. This project was created to allow users who
are using a host device that does not have native Bluetooth Smart Ready
support and/or does not have HOGP support to use the BLE Advanced Remote
Control with their system.
- For GAP central role applications, the bond manager now properly handles
cases in which the peripheral device has erased previously stored bonding
information
- A new HCI extension API has been added to allow peripheral/slave devices to
temporarily ignore any nonzero slave latency value, and explicitly wake up
at every connection event regardless of whether it has any data to send.
The prototype for the API function HCI_EXT_SetSlaveLatencyOverrideCmd can
be found in hci.h, including the description of the function.
- A new HCI extension API has been added to allow the application layer to
get or set a build revision number.
Bug Fixes:
- In some cases L2CAP Peripheral Connection Parameter Update requests failed
due to a zero value in the transmitWindowOffset parameter when the
connection was initially established. This has been fixed and updates
should now work successfully.
- During bonding, connection failures would occasionally occur due to the
OSAL Simple NV driver performing a page compaction and halting the CPU for
longer than the time required for the link layer to maintain proper
connection timing. To prevent this from occurring, the simple NV driver now
has any API to force a page compaction if the page is full beyond a specified
threshold. The bond manager calls this API every time a connection is
terminated to ensure that compaction occurs before the next connection is set
up.
- Occasional slave connection failures would previously occur in cases in which
the master device sends Update Channel Map requests while a large slave
latency value is in use. This has been fixed.
- The SensorTag application now properly supports storage of GATT Client
Characteristic Configuration Descriptor values with bonded devices.
- After disabling advertising, the CC254x would unnecessarily wake up for a
short period of time 500ms later. This unecessary wake-up has been removed.
- Upon Power-On Reset or after wake-up from PM3, a 400ms delay has been
implemented, during which time the CC254x will not go into PM2 sleep. This
allows time for the 32kHz crystal to stabilize. Previously, in rare cases
with certain hardware configurations the CC254x could have timing issues due
to the crystal not having time to stabilize.
- Minor bug fixes to GlucoseSensor and GlucoseCollector projects.
Known Issues:
- Use of the NV memory (to save application data or BLE Host bonding
information) during a BLE connection may cause an unexpected disconnect.
The likelihood of this happening increases with frequent usage, especially
when using short connection intervals. The cause is related to the NV wear
algorithm which at some point may cause an NV page erase which can disrupt
system real-time processing. It is therefore recommended that the NV memory
be used sparingly, or only when a connection is not active.
- HCI packet size of 128 bytes or more will be disregarded by the stack, and as
such, no HCI event will be returned.
- The HAL SPI driver that was implemented since the v1.3 release can sometimes
hang, particularly in cases in which power management is used and when there
is heavy traffic on the SPI bus.
For technical support please visit the Texas Instruments Bluetooth low energy
E2E Forum:
http://e2e.ti.com/support/low_power_rf/f/538.aspx
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Version 1.3
Dec 12, 2012
Notices:
- This version of the Texas Instruments BLE stack and software features several
changes, enhancements, and bug fixes from v1.2.1. Details of these can be
found below.
Changes and Enhancements:
- A new sample project, SensorTag, has been added. This application runs on the
CC2541 Sensor Tag board, which is included as part of the CC2541DK-SENSOR
development kit. The application includes custom services for an
accelerometer, barometer, gyro, humidity sensor, IR temperature sensor, and
magnetometer.
- A new Boot Image Manager (BIM) is included. This allows one CC2540 or CC2541
device to contain two separate software images (an "A" image and a "B" image)
stored in flash. Upon power-up, the BIM selects which image to boot into.
This can be based on criteria such as the state of a GPIO pin, or based on a
selection from the previously running application upon reset.
- A new Over-the-air firmware download (OAD) feature is included. The feature
allows a peer device (which could be a central BT Smart device such as a
smartphone) to push a new firmware image onto a peripheral device and update
the firmware. This feature uses the BIM, in which case the downloaded image
gets stored in the opposite flash location as the currently running image.
For example, if the "A" image is the current image and is used to perform the
download, then the downloaded image becomes the "B" image. Upon reset, the
"B" image with the updated firmware would be loaded. The OAD feature
optionally allows for the firmware image to be signed (using AES). Both the
SensorTag and SimpleBLEPeripheral projects include configurations for using
the OAD feature. A central "OADManager" application is also included,
demonstrating a central implementation for sending a new firmware image to an OAD target device.
- The physical HCI interface used by the network processor (HostTestRelease)
has been enhanced to work while power management is enabled on the CC254x
device. The UART interface, when using RTS and CTS lines, can be used by an
external application processor to wake-up the CC254x network processor. When
the network processor has completed all processing, it will go into deep
sleep. In addition to UART, an SPI interface has been added as an option for
the physical HCI interface. It also supports power management by means of
the MRDY and SRDY lines.
- The CC2541 configuration of the KeyFobDemo project has been modified to
support the new CC2541 keyfob hardware, contained in the CC2541DK-MINI kit.
The accelerometer has been changed, and a TPS62730 DC/DC converter has been
added.
- The structure of all projects have been changed to include a Transport Layer
("TL") library and network processor interface "NPI" source code. This new
architecture allows for non-network processor applications to have slightly
reduced code size by removing unnecessary stack components.
- An API has been provided allowing the device name and appearance
characteristics in the GAP service to be modified by the application layer.
- KeyFobDemo project now includes visual feedback from LED to indicate when
device has powered up and when device is advertising.
- The HID-over-GATT Profile (HOGP) implementation has been updated to now
queue up HID report and send notifications upon reconnection to a HID host.
- A new implementation of the HID service has been included, which supports
a combined keyboard, mouse, and consumer class device in its HID report
descriptor.
- The API for sending L2CAP Connection Parameter Update Requests from the GAP
Peripheral Role Profile has been updated to take both the requested minimum
and maximum connection intervals as parameters.
- BTool has been enhanced with a new GATT explorer table, displaying discovered
attributes, handles, and values. An XML file is included which allows the
user to define descriptions of characteristics based on their UUIDs.
- HCI UART interface baud rate has been changed from 57600 to 115200.
Bug Fixes:
- When power management is used with long connection intervals (>2s), the
CC254x remains sleeping properly without unnecessary wake-ups.
- When slave latency is used, peripheral devices now properly wake-up before
the next connection event when a data packet is queued
- Various bug fixes on the GlucoseSensor and GlucoseCollector projects to
improve compliance with profile and service specifications.
- HID-over-GATT Pofile (HOGP) implementation has been updated to provide
better interoperability with HID hosts.
Known Issues:
- Use of the NV memory (to save application data or BLE Host bonding
information) during a BLE connection may cause an unexpected disconnect.
The likelihood of this happening increases with frequent usage, especially
when using short connection intervals. The cause is related to the NV wear
algorithm which at some point may cause an NV page erase which can disrupt
system real-time processing. It is therefore recommended that the NV memory
be used sparingly, or only when a connection is not active.
- HCI packet size of 128 bytes or more will be disregarded by the stack, and as
such, no HCI event will be returned.
For technical support please visit the Texas Instruments Bluetooth low energy
E2E Forum:
http://e2e.ti.com/support/low_power_rf/f/538.aspx
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Version 1.2.1
Apr 13, 2012
Notices:
- This version of the Texas Instruments BLE stack and software is a minor
update to the v1.2 release. It contains some minor enhancements and bug
fixes, with no API changes or major functional changes.
Changes and Enhancements:
- When advertising is enabled by calling GAP_MakeDiscoverable, the first
advertisement event will now occur within a few milliseconds, rather than
waiting for 10ms.
Bug Fixes:
- The HidEmuKbd project now properly implements the HID Service include of the
Battery Service. This bug fix allows for proper interoperability between the
CC254x HID Profile and host systems running Windows 8.
- The source code file hal_board_cfg.h has been updated to better support the
serial bootloader (SBL) and Universal Bootloader (UBL).
- Scanning in BTool can now be cancelled at any time without hanging or
freezing the system.
Known Issues:
- Use of the NV memory (to save application data or BLE Host bonding
information) during a BLE connection may cause an unexpected disconnect.
The likelihood of this happening increases with frequent usage, especially
when using short connection intervals. The cause is related to the NV wear
algorithm which at some point may cause an NV page erase which can disrupt
system real-time processing. It is therefore recommended that the NV memory
be used sparingly, or only when a connection is not active.
For technical support please visit the Texas Instruments Bluetooth low energy
E2E Forum:
http://e2e.ti.com/support/low_power_rf/f/538.aspx
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Version 1.2
Feb 13, 2012
Notices:
- This version of the Texas Instruments BLE stack and software includes support
for the CC2541, as well as some enhancements and bug fixes. Details of these
can be found below. If you have not previously worked with the v1.1b release
(which had limited distribution) it is recommended that you also read the notes
detailing the changes and enhancements from v1.1a to v1.1b in addition to the
notes for v1.2.
Changes and Enhancements:
- All projects have been migrated from IAR v7.60 to IAR v8.10.4. In order to
build all projects, be sure to upgrade and have IAR v8.10.4. Also, be sure to
download and install all of the latest patches from IAR for full CC2540 and
CC2541 support.
- Multi-role and combo-role support has been enhanced. The BLE stack can now
support simultaneously advertising and/or scanning while in a connection as
either a master or a slave. This allows for a central device to perform
device discovery while in a connection. All previous rules for multiple
simultaneous connections as a central device still apply (see v1.1a release
notes below).
- New sample projects "SimpleBLEBroadcaster" and "SimpleBLEObserver" have been
added, as example projects for pure broadcaster and observer applications
with very low code size. The projects make use of new GAP role profiles
broadcaster.c and observer.c that are included.
- All projects have a modified architecture from the v1.1, v1.1a, and v1.1b
releases. Each project contains a file "buildConfig.cfg" that can be found in
the project directory and is included in the IAR project workspace as part of
the "TOOLS" group. The settings in this file determine the role of the device
in the application. Based on this configuration, different pieces of the BLE
stack in object code are linked in, causing the code size to be larger or
smaller depending on the roles supported. For example, HostTestRelease by
default is now configured to support every single BLE GAP role in a single
build, and therefore has a large code size (approx. 165kB). On the other
hand, SimpleBLEBroadcaster is configured to only support the GAP broadcaster
role, and therefore has a very small code size (approx. 39kB).
- The function GAPRole_SendUpdateParam in peripheral.c has been made public to
allow a peripheral application to send an L2CAP connection parameter update
request at any time.
- The names and configuration of the BLE stack libraries have changed.
Different libraries are used depending on the GAP role (or combination of
roles) used by the application. More information can be found in section
3.3.5 of the BLE Software Developer's Guide.
- All library files now support power management. Power management must be
enabled by the application by calling osal_pwrmgr_device( PWRMGR_BATTERY );.
All sample applications that use power management make this call in the main
function.
- All GATT service source code has been cleaned up to make handling of client
characteristic configuration descriptors (CCCDs) simpler. All CCCDs are now
processing is now handled by GATTServApp and no longer must be handled by the
service itself. Examples of this can be found in the included example
services such as SimpleGATTprofile, Simple Keys service, Accelerometer
service, etc...
- The HostTestRelease network processor project now includes HCI Vendor
Specific commands for each GATT client sub-procedure, matching the GATT
client API. All GATT commands have been added to the "Adv. Commands" tab in
BTool. The functions in the BTool GUI "Read / Write" tab now make use of the
GATT commands as opposed to ATT commands.
- The old "EmulatedKeyboard" project has been removed and replaced with the new
"HIDEmuKbd" project. The new project performs the same functions as the old
one, but is now based on the "HID over GATT Profile" v1.0 specification
(HOGP_SPEC_V10) that has been adopted by the Bluetooth SIG. The HID profile
functionality has been implemented in a OSAL task that runs separate from the
application to allow for easy portability to other HID projects. More details
on the new application can be found in the BLE Sample Application Guide
included as part of the release. The following additional new services /
profiles have been included to fully support the HOGP specification:
- HID Service v1.0 (HIDS_SPEC_V10)
- Scan Parameters Profile v1.0 (ScPP_SPEC_V10)
- Scan Parameters Service v1.0 (ScPS_SPEC_V10)
- Device Information Service v1.1 (DIS_SPEC_V11r00)
- Battery Service v1.0 (BAS_SPEC_V10)
- The KeyFobDemo project has been updated to use the adopted battery service.
The custom battery service that was used in previous released has been
removed.
- The TimeApp project has been updated to include support for the Phone Alert
Status Profile (PASP_SPEC_V10) in the Client role.
- Support for "Production Test Mode" has been added, allowing a BLE application
in a "single-chip" configuration to temporarily expose the HCI over the UART
interface when triggered externally to do so (e.g. hold a GPIO pin low during
power up). This allows the device to be connected to a Bluetooth tester in
order to run direct test mode (DTM) commands on a production line using the
final release firmware, while leaving the UART GPIO pins available for the
application to use at all other times
- A Universal Boot Loader (UBL) using the USB Mass Storage Device (USB-MSD)
class has been added along with a Serial Boot Loader (SBL). The
HostTestRelease project includes configurations with examples of both boot
loaders. The SBL project is included with the installer. More information on
the UBL can be found in the following document:
C:\Texas Instruments\BLE-CC254x-1.2\Documents\
Universal Boot Loader for SOC-8051 by USB-MSD Developer's Guide.pdf
- HCI extension command HCI_EXT_MapPmIoPortCmd added to support toggling of a
GPIO line as CC254x device goes in and out of sleep. This command can be
used to automatically control the bypass line of the TPS62730 DC/DC
converter for reducing power consumption in an optimized manner.
- A slave device will now dynamically widen it's Rx window when a previous
connection event was missed. This improves connection stability by accounting
for additional clock drift that may have occurred since the last successful
connection event.
- The application now has the capability to change the permissions of the
device name in the GAP service by calling GGS_SetParameter and changing
the value of the parameter GGS_W_PERMIT_DEVICE_NAME_ATT. The application can
also receive a callback when a client device writes a new name to the device.
The application registers the callback by calling GGS_RegisterAppCBs. The
prototype for GGS_RegisterAppCBs can be found in gapgattserver.h.
Bug Fixes:
- Duplicate filtering now works with combination states.
- Various minor application / profile bug fixes.
Known Issues:
- Use of the NV memory (to save application data or BLE Host bonding
information) during a BLE connection may cause an unexpected disconnect.
The likelihood of this happening increases with frequent usage, especially
when using short connection intervals. The cause is related to the NV wear
algorithm which at some point may cause an NV page erase which can disrupt
system real-time processing. It is therefore recommended that the NV memory
be used sparingly, or only when a connection is not active.
For technical support please visit the Texas Instruments Bluetooth low energy
E2E Forum:
http://e2e.ti.com/support/low_power_rf/f/538.aspx
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Version 1.1b
Nov 30, 2011
Notices:
- This version of the Texas Instruments BLE stack and software includes support
for the CC2541, as well as some minor enhancements and bug fixes. Details of
these can be found below. The general software architecture remains the same
as in the v1.1 and v1.1a releases.
Changes and Enhancements:
- BLE stack libraries for the CC2541 are included.
- All BLE libraries are renamed and now indicate whether they are used for
CC2540 or CC2541.
- For each project and configuration, new IAR projects are included for use
with the CC2541. The only exception is that any project/configuration that
uses the USB interface has not been replicated for the CC2541, as it does not
have an on-chip hardware USB interface.
- Link-layer processing has been optimized to provide for reduced power
consumption during connection events and advertising events.
- SimpleBLEPeripheral and SimpleBLECentral now use the HCI_EXT_ClkDivOnHaltCmd,
which reduces the current level while the CC2540/41 radio is active.
- The bond manager has been updated to allow peripheral devices to properly
pair, bond, and resolve the address of central devices that use the private
resolvable address type.
- New command HCI_EXT_SetMaxDtmTxPowerCmd included, which allows the maximum
Tx power level to be set. This is useful when using Direct Test Mode (DTM),
in that the Tx power level will be set to the maximum value set by the
HCI_EXT_SetMaxDtmTxPowerCmd command, which may be less than +4dBm for the
CC2540 and less than 0dBm for the CC2541. The function prototype can be
found in hci.h.
Bug Fixes:
- The command HCI_EXT_SetTxPowerCmd is now properly working.
Known Issues:
- Use of the NV memory (to save application data or BLE Host bonding
information) during a BLE connection may cause an unexpected disconnect.
The likelihood of this happening increases with frequent usage, especially
when using short connection intervals. The cause is related to the NV wear
algorithm which at some point may cause an NV page erase which can disrupt
system real-time processing. It is therefore recommended that the NV memory
be used sparingly, or only when a connection is not active.
- Duplicate filtering does not work when scan is used in combination with a
connection.
For technical support please visit the Texas Instruments Bluetooth low energy
E2E Forum:
http://e2e.ti.com/support/low_power_rf/f/538.aspx
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Version 1.1a
Aug 10, 2011
Changes and Enhancements:
- The thermometer profile sample application has been updated to support
stored measurements. The TI_BLE_Sample_Applications_Guide has been updated
to match these changes.
Known Issues:
- Use of the NV memory (to save application data or BLE Host bonding
information) during a BLE connection may cause an unexpected disconnect.
The likelihood of this happening increases with frequent usage, especially
when using short connection intervals. The cause is related to the NV wear
algorithm which at some point may cause an NV page erase which can disrupt
system real-time processing. It is therefore recommended that the NV memory
be used sparingly, or only when a connection is not active.
- Duplicate filtering does not work when scan is used in combination with a
connection.
For technical support please visit the Texas Instruments Bluetooth low energy
E2E Forum:
http://e2e.ti.com/support/low_power_rf/f/538.aspx
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Version 1.1
July 13, 2011
Notices:
- This version of the Texas Instruments BLE stack and software features several
changes, enhancements, and bug fixes from v1.0. Details of these can be found
below.
Changes and Enhancements:
- All projects have been migrated from IAR v7.51A to IAR v.7.60. In order to
build all projects, be sure to upgrade and have IAR v7.60. Also, be sure to
download and install all of the latest patches from IAR for full CC2540
support.
- The stack now supports up to 3 simultaneous connection as a central / master
device, with a few constraints:
- All connection intervals must be a multiple of the minimum connection
interval (i.e. the minimum connection interval is the greatest common
denominator of all connection intervals).
- The minimum connection interval allowed is 25ms when using more than
one connection.
- When more than one connection is active, only one data packet per
connection event will be allowed in each direction.
- Scanning is not supported while in a connection. The consequences of
this is that device discovery is not possible while in a connection.
Therefore, to discover and connect to multiple devices, the device
discovery must occur before the first connection is established.
- Several new sample projects are included, with examples of many different BLE
applications / profiles. Full details on the sample applications can be found
in the BLE Sample Applications Guide, which can be accessed from the Windows
Start Menu. These sample applications implement various functions. Some are
based on adopted Bluetooth specifications, some are based on draft
specifications, and others are custom designed by Texas Instruments. These
projects should serve as good examples for various other BLE applications.
- The following updates have been made to BTool (more information on these
updates can be found in the CC2540DK-MINI User Guide which can be downloaded
here: http://www.ti.com/lit/pdf/swru270):
- Improved GUI and robustness.
- All functions on the GUI been updated to handle multiple simultaneous
connections.
- A new "Pairing / Bonding" tab has been added, allowing link
encryption and authentication, passkey entry, and saving / loading of
long-term key data (from bonding) to file.
- Ability to "Cancel" a link establishment while the dongle is
initiating.
- The following additional new controller stack features are included in this
release:
- Support for multiple simultaneous connections as a master (details
above)
- HCI Vendor Specific function HCI_EXT_SetSCACmd allows you to specify
the exact sleep clock accuracy as any value from 0 to 500 PPM, in
order to support any crystal accuracy with optimal power consumption.
This feature is only available for slave / peripheral applications.
- HCI Vendor Specific function HCI_EXT_SetMaxDtmTxPowerCmd allows you
to set the maximum transmit output power for Direct Test Mode. This
allows you to perform use the LE Transmitter Test command with power
levels less than +4dBm.
- A master device can now advertise while in a connection.
- New production test mode (PTM) has been added allowing the CC2540 to
run Direct Test Mode (DTM) while connected to a tester using a
"single-chip" BLE library.
- The controller now uses DMA to more efficiently encrypt and decrypt
packets. All BLE projects must now define HAL_AES_DMA=TRUE in the
preprocessor settings when using the v1.1 libraries.
- The following additional new host stack features are included in this
release:
- A new GAP central role profile for single-chip embedded central
applications is included, with functions similar to the GAP
peripheral role profile. The SimpleBLECentral project serves as an
example of an application making use of the central role profile.
- The GAP peripheral role has been optimized to significantly improve
power consumption while advertising with small amounts of data by
no longer transmitting non-significant bytes from in the
advertisement and scan response data.
- The following additional new application / profile features are included in
this release:
- The GAP peripheral bond manager has been replaced with a general GAP
bond manager, capable of managing bond data for both peripheral and
central role devices. The gap peripheral bond manager has been
included for legacy support; however it is recommend to switch to the
general GAP bond manager (gapbondmgr.c/h).
- The bond manager also now manages the storage of client
characteristic configurations for each bond as per the Bluetooth 4.0
spec.
- The simple GATT profile has a new fifth characteristic. This
characteristic is 5 bytes long, and has readable permissions only
while in an authenticated connection. It should serve as a reference
for development of other profiles which require an encrypted link.
- All GATT profiles have been updated to properly handle client
characteristic configurations for both single and multiple
connections. Characteristic configurations now get reset to zero
(notifications / indications off) after a connection is terminated,
and the bond manager now stores client characteristic configurations
for bonded devices so that they are remembered for next time when the
device reconnects.
- Added linker configuration file for support of 128kB flash versions
of the CC2540. An example is included in the SimpleBLEPeripheral
project.
- The SimpleBLEPeripheral project "CC2540 Slave" configuration has been
updated to better support the SmartRF05EB + CC2540EM hardware
platform, making use of the LCD display.
Bug Fixes:
- The following bugs have been fixed in the controller stack:
- Scanning now working for master devices with power savings enabled.
- RSSI reads no longer require a data packet to update.
- Improved stability when using very high slave latency setting
- HCI LE direct test modes now working properly.
- HCI Read Local Supported Features now returns the proper value.
- Use of two advertising channels now works.
- When connecting to a device on the whitelist, the correct peer device
address is returned to the host.
- The following bugs have been fixed in the host stack:
- Pairing no longer fails when either device is using a static, private
resolvable, or private non-resolvable address.
- The following bugs have been fixed in the profiles / applications:
- Reading of RSSI with peripheral role profile now working.
- Peripheral role profile now allows all legal whitelist modes.
- Can now connect with short connection intervals (such as 7.5ms),
since bond manager now reads data from NV memory upon initialization
rather than immediately after a connection is established. Pairing
still may not be stable when using the bond manager with very short
connection intervals (for reason noted in "Known Issues" below)
Known Issues:
- Use of the NV memory (to save application data or BLE Host bonding
information) during a BLE connection may cause an unexpected disconnect.
The likelihood of this happening increases with frequent usage, especially
when using short connection intervals. The cause is related to the NV wear
algorithm which at some point may cause an NV page erase which can disrupt
system real-time processing. It is therefore recommended that the NV memory
be used sparingly, or only when a connection is not active.
- Duplicate filtering does not work when scan is used in combination with a
connection.
For technical support please visit the Texas Instruments Bluetooth low energy
E2E Forum:
http://e2e.ti.com/support/low_power_rf/f/538.aspx
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Version 1.0
October 7, 2010
Notices:
- The Texas Instruments Bluetooth® low energy (BLE) software development kit
includes all necessary software to get started on the development of
single-mode BLE applications using the CC2540 system-on-chip. It includes
object code with the BLE protocol stack, a sample project and applications
with source code, and BTool, a Windows PC application for testing BLE
applications. In addition to the software, the kit contains documentation,
including a developer’s guide and BLE API guide.
- For complete information on the BLE software development kit, please read
the developer's guide:
BLE Software Developer's Guide:
<Install Directory>\Documents\TI_BLE_Software_Developer's_Guide.pdf
(Also can be accessed through the Windows Start Menu)
- The following additional documentation is included:
BLE API Guide:
<Install Directory>\Documents\BLE_API_Guide_main.htm
Vendor Specific HCI Guide:
<Install Directory>\Documents\TI_BLE_Vendor_Specific_HCI_Guide.pdf
HAL Drive API Guide:
<Install Directory>\Documents\hal\HAL Driver API.pdf
OSAL API Guide:
<Install Directory>\Documents\osal\OSAL API.pdf
- The following software projects are included, all built using IAR Embedded
Workbench v7.51A:
SimpleBLEPeripheral:
<Install Directory>\Projects\ble\SimpleBLEPeripheral\CC2540DB \SimpleBLEPeripheral.eww
HostTestRelease:
<Install Directory>\Projects\ble\HostTestApp\CC2540\HostTestRelease.eww
- The following Windows PC application is included:
BTool:
<Install Directory>\Projects\BTool\BTool.exe
(Also can be accessed through the Windows Start Menu)
Changes:
- Initial Release
Bug Fixes:
- Initial Release
Known Issues:
- Use of the NV memory (to save application data or BLE Host bonding
information) during a BLE connection may cause an unexpected disconnect.
The likelihood of this happening increases with frequent usage, especially
when using short connection intervals. The cause is related to the NV wear
algorithm which at some point may cause an NV page erase which can disrupt
system real-time processing. It is therefore recommended that the NV memory
be used sparingly, or only when a connection is not active.
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------