CC2640R2F: Connection/commands for Bluetooth Qualification Requirements

Hi,

For Bluetooth qualification, the tester should send HCI commands to the device. The HCI commands are supposed to be sent over UART. The UART communication does not transit via the XDS110.

In other words, I don't expect any issue here.

Have you contacted your test house and BQC to discuss with them if they see some potential issues for testing your implementation?

As a side note, I have updated your initial message. I have removed the email you have attached. If you think this email can be posted on a public forum, please share it once more.

Kind regards,

Hi Clement ,

Hi,

Yes, it is definitely possible to connect the UART directly.

The UART pins are here:

To use them, remove the corresponding jumpers and connect the signals to the pin closer to the CC26xx device.

Best regards,

We are tried the suggested option and connected to the interlab Automation explorer to check the HCI communication between tester and DUT.

We have performed HCI LE Reset option and getting Success but the response are getting change on each time. Please find below 

1. Taking Tx & Rx from Cluster i.e. DUT.
2. Connecting directly to TX, RX of USB.
3. Running LE Reset from Interlab Application.

   Following are the logs:-

   Logs for LE Reset

   14:23:12 - Running Serial - Two-Wire LE Reset: 1

   Send: 0000

   Expected: 0x0000

   Received: C6000000

   LE Reset: Completed. Result: Success

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

   14:23:13 - Running Serial - Two-Wire LE Reset: 2

   Send: 0204

   Expected: 0x0000

   Received: F7000000

   LE Reset: Completed. Result: Success

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

   Below response getting error: 

   14:23:14 - Running Serial - Two-Wire LE Reset: 3

   Send: 0300

   Expected: 0x0000

   Received: 0000 

   LE Reset: Completed. Result: Error.

   Driver Used : FTDI version :2.12.28.0

Hi,

Apparently, you do have a working link between the tester and the Device Under Test (DUT, i.e. the CC2640R2F). This is a great first step.

- Could you please provide a picture of your setup?

- Could you please specify which Software is flashed on the CC2640R2F device?

- In order to validate the behavior of the software, could you please run a few tests using BTool.

Best regards,

Hi Clement Please find below :

Setup Given below 

SW used to flash the device :SDK --> simplelink_cc2640r2_sdk_4_10_00_10

Hi,

Thank you for the picture provided.

Could you please verify the code running on the CC2640R2F device behaves properly - see the two last points of my previous message

If yes, then I would recommend to verify if the "UART to USB converter" and the "Interlab Software" are configured properly. I guess the provider of these can help.

Best regards,

Hi Clement

Please find the UART to USB Driver details.

(HCI interface used in Interlab - Serial 2 Wire )

Driver Provider: FTDI

Driver Date:8/16/1027

Driver version: 2.12.28.0

Digital Signer :Microsoft Windows Hardware Compatibility Publisher.

Hi Puneet ,

As per the request,  please verify the code running on the CC2640R2F device behaves properly.

Regards

Alwin

Hi

During testing direct HCI communication. BLE chip is disconnected from micro. so no interaction between micro & BLE chip. Also SW in BLE chip is running okay.

Regards

Puneet

Hi Evan

We have implemented production test software.

For DTM, we need to flash other software? or we can configure through RF studio?

Regards

Puneet

Hi Evan,

In the pdf that you have linked in your comment, there is a section called Programming the DUT, in the below steps are written:

The settings for the CC2650DK and CC2650LP are the same, as shown below:
1. In the Connected devices panel, select the DUT.
• For the CC2650DK, select “CC2650” under the “XDS100v3”
• For the CC2650LP, select “CC2650” under the “XDS110”
2. Main Tab -> Flash image(s). Select “Multiple”.
3. Use “Browse” to select the APP project hex file.
• For the CC2650DK: host_test_cc2650em_app.hex
• For the CC2650LP: host_test_cc2650lp_app.hex
4. Use Browse again to select the STACK project hex file. •
• For the CC2650DK: host_test_cc2650em_stack.hex
• For the CC2650LP: host_test_cc2650lp_stack.hex
5. Main Tab -> Actions (see Figure 1)
(a) Erase. Select Pages in image
(b) Program. Select “Entire source file”
(c) Verify. Select “Readback”
6. Image Overrides. Check “Keep CCFG”
7. Click on the icon below the Verify box to start programming.

I need to know one thing, we are using CC2640R2F, and for our board what are the things that we need to select?

Regards,

Saurav

Hi Clement

Since Evan is OoO. can you please reply on above queries??

Regards

Puneet

Hi Puneet, Saurav,

I have responded to Puneet via an internal email thread. There are a few things that need to conclude before this conversation is furthered. 

Evan

Hi Evan,

Below are the things we had done in the workspace:

1) added and removed predefined symbols from the workspace according to the table given in pdf

APP Project

Remove: POWER_SAVING 
Remove: NPI_USE_SPI
Add: NPI_USE_UART

STACK Project
Remove: POWER_SAVING

2) added below in the predefined symbols section of the app

CC2640R2DK_5XD

By following the steps we were able to generate "app" hex file only.

Regards,

Saurav