CC2541: Vulnerability sweyntooth

Hi Ashwani,

I've looped in someone on my team to respond. He will follow up within the day. 

Hello Ashwan,

Our recommendation is to upgrade to the latest BLE Stack. You may download it from http://www.ti.com/tool/BLE-STACK, and review the list of changes and bug fixes from 1.3.3 to 1.5.1 in the readme.txt file that will open up automatically after the installation (or, you can open it from C:\Texas Instruments\BLE-CC254x-1.5.1.1).

Please note that version 1.5.1 includes all the functionality from version 1.3.1, and has no major architectural changes.

Please let us know if you have any other questions.

-Luis

Thanks Luis for your prompt response. before we follow your recommendation, what I am interested to clarifiy is whether 1.3.3 is part of your official releases, i dont see its mention in swru271i.

Please note that during 2012 our colleagues worked directly with your colleague @ san diego and following their working togther this 1.3.3 was provided to us. I am interested to know the delta of 1.3.3 and 1.3.2.

our products are already in market with this stack since 2014 and we need to ensure any non regression in the application due to stack update.

Thanks for your support

best regards

Ashwani

Ashwani,

I understand your situation better now. I don't have the answer, but I'm trying to figure it out.

In the meantime, and since this is from a long time ago, do you have any other history as to what motivated the update from 1.3.2 to 1.3.3? (I'm trying to get you the delta) and also can you tell me, is your device a peripheral or a central device?

Thanks,

Luis

If I remember correctly, it was related to some issue in SPI communication between the host MCU and CC2541. We use the  CC2541 in NCP architecture, where application is running in an MSP430 MCU and which in turn is communicating with the CC2541 over SPI.

hope this helps, is it possible to orgnise a conf call on this matter,? with the time difference and exchanges over forum we loose lot of time.

Thanks in advance for your help

Best Regards

Ashwani

Ashwani,

Thanks for the information. Yes, from the release notes I can confirm that version 1.4.0 included fixes for the SPI driver, likely delivered to you on v1.3.3.

To organize the call, can you please tell me who is your TI Sales representative?

Also, would you be able to share the SDK installer for your 1.3.3 version? Or, the SPI & NPI files? That's going to help me identify the delta.

Thanks,

Luis

Hi Luis

Please find attached the project source that we use to get 1.3.3.

looking at the read me file I found this, it talks about schneider version 1.3.3:

============================================================

Texas Instruments, Inc.

CC2540/41 Bluetooth Low Energy Software Development Kit
Release Notes

Version 1.3.3
December 9, 2013

Differences between standard 1.3.2 release and Schneider version 1.3.3:

- _hal_uart_spi.c : inclusion of bug fixes for power saving feature and for
making sure that SRDY returns to a high level during SPI data reception
before the host MCU raises the SPI chip select signal.

- _hal_uart_spi.c : inclusion of DMA abort bug fix from BLE 1.4 release.

- hal_sleep.c: inclusion of bug fix for power management making sure that
the last instruction executed before putting the CC254x to sleep is a
verification that going to sleep is allowed. This removes the change for
an interrupt to arrive between the time where the decision is made to go
to sleep and when the CC2541 actually does go to sleep.

- CC2541_BLE.lib : contains the workaround for the tandem bug (bugzilla 4817)

- HostTestRelease.ewp : defines GATT_DB_OFF_CHIP

Notices:

- This version of the Texas Instruments BLE stack and software is a minor
update to the v1.3.2 release. It contains some bug fixes.

- The BLE protocol stack, including both the controller and host, was
completely retested for v1.3.3. 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.2 were sanity
tested only.

-------------------------------------------------------------------------------
-------------------------------------------------------------------------------

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/538/cc2541_5F00_stack_5F00_v1.3.3.7z

For the conference call our contact here is account manager: Eric SACRE.

Thanks & Regards

Ashwani

Ashwani,

Thanks for the new information and the file you provided. I'll work on my side to organize the conference call. 

-Luis

Thanks Luis

looking forward to the call.

Best regards

Ashwani