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.

Porting to BLE stack 2.2 ble_user_config

Other Parts Discussed in Thread: CC2650, CC2640, CC2590

Hi,

I was able to get the CC2650 DK-7ID to advertise with the BLE stack 2.2.

I am still using CCS 6.1.2 with ARM compiler 5.2.7.

I am now trying to add a CC2640 custom board directory (4x4 package). I

have a predefined symbol I add to the simple_peripheral project that is

recognized by main.c and builds fine.

ble_user_config.c and ble_user_config.h files don't accept this symbol like

the files from BLE stack 2.1. Any ideas why?

In BLE stack 2.1, I had this in the ble_user_config.h file:

#elif defined (CC2640_Custom)
 #define RF_FE_MODE_AND_BIAS           ( RF_FE_DIFFERENTIAL |                 \
                                          RF_FE_INT_BIAS )

The design uses a CC2590 PA. Should the custom board choice inside ble_user_config.c

be made with differential output? This question applies to both BLE stacks 2.1 and 2.2.

There seem many choices inside ble_user_config.c  for BLE stack 2.2. Can you advice

where to place the custom board hooks? 

Thanks,

Priya

  • Hello Priya,

    You can add your custom define in ble_user_config.h and add the define to the existing Tx Power Values table for Differential Output in ble_user_config.c. Make sure it's all under the CC26xx section.

    Best wishes
  • I completed porting the custom project to BLE stack 2.2 today. I am able to observe advertising.

    However, when I connect a meter in series to measure current draw, the advertising stops and

    the circuit opens, drawing no current. Any idea why this may be happening? I am using default

    options for the power driver that includes calibrating the oscillator.

    Thanks,

    Priya

  • Hi Priya,

    Due to the ultra low power nature of our chips, the traditional way of measuring current with a DMM will not work for you. This is likely because the RF core is causing spikes that is outside of your meter's range. For example if you are trying to measure sleep current you would set your meter to the uA mode, but then when the RF core wakes up the advertise the radio will instantaneously consume current in the mA range.

    If you must use a DMM, I recommend a current limiting resistor such as 10 Ohm. However please be aware that this is not a precise power measurement. To get the most precise power numbers, we recommend using a dedicated power analyzer like the steps described here:
    www.ti.com/lit/swra478
  • Hi Sean,
    This is something I am observing only after porting to BLE stack 2.2. I followed the recommended power consumption measurement methods with BLE stack 2.1 and the same product measures 1-3 uA in standby and continues to advertise.
    Thank you,
    Priya
  • The power consumption curve for BLE Stack v2.2 is slightly different than before. Can you try the current limiting resistor approach to validate that you aren't tripping your meter?
  • A 10 Ohm resistor has always been in place.
    Thanks,
    Priya
  • Can you try with a scope then so we can get a better picture of what is going on? If the device is advertising/behaving normally without any test equipment setup then it is possible that the measurement is interfering with the device.
  • Yes, my setup also has a scope in place. The PAEN signal disappears once I connect a meter in series. I will check the old stack results to verify any connection/setup problems.

    Thank you,
    Priya
  • Thanks Priya. Please post the scope captures here when you get them.

    Also please confirm that the current project with stack v2.2 is working as expected without measurement hardware attached.
  • Yes, BLE stack2.2 without the meter is displaying PAEN on the scope.
    Thanks,
    Priya
  •  Here is the advertising current draw using BLE stack 2.2 taken today. The meter had a blown fuse. The meter is reading between 0.4 uA - 3 uA. Let me know your comments.

    Priya

  • I am marking this issue as resolved. It would be nice if adding custom board options to BLE user config.c and .h files was made simpler.

    Thanks,
    Priya