This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

BLE-CC254x-1.3.2与BLE-CC254x-1.2.1 区别

Other Parts Discussed in Thread: CC2540, CC2541, CC2541DK-MINI, TPS62730

有谁清楚BLE-CC254x-1.3.2与BLE-CC254x-1.2.1的区别,我公司现在要用BLE-CC254x-1.3.2,我原来用的是BLE-CC254x-1.2.1,想了解一下两者的区别

  • 看协议栈的readme.txt,节录如下。

    Texas Instruments, Inc.

    CC2540/41 Bluetooth Low Energy Software Development Kit
    Release Notes

    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抯 host would accept invalid connection parameters requested
      by the Slave, and would send back the Connection Parameter Update Response
      with 憄arameters 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 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
      infomration.

    - 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 succesfully.

    - 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 everytime 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 unecessarily 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 Pofile (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

x 出现错误。请重试或与管理员联系。