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.

No ADVERTISING with CC2541F128

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

Dears,

I am working on a project based on the SimpleBLEPeripheral project inside BLE1.3.2

The IAR version is 8.20.2. the hardware is CC2541F128.

I followed the step from link http://processors.wiki.ti.com/index.php/128kproject and created the project.

The defined symbols in the IAR setting are as following:

"INT_HEAP_LEN=3072
HALNODEBUG
OSAL_CBTIMER_NUM_TASKS=1
HAL_AES_DMA=TRUE
HAL_DMA=TRUE
POWER_SAVING
xPLUS_BROADCASTER
HAL_LCD=FALSE
HAL_LED=FALSE
CC2540_MINIDK
HAL_BOARD_128K"

And i changed DEFAULT_DISCOVERABLE_MODE definition to GAP_ADTYPE_FLAGS_GENERAL and initial_advertising_enable to TRUE as following:

   "#define DEFAULT_DISCOVERABLE_MODE GAP_ADTYPE_FLAGS_GENERAL //GAP_ADTYPE_FLAGS_LIMITED"

   "uint8 initial_advertising_enable = TRUE; //FALSE"

When i do debugging with IAR via CC Debugger, i can see the adv packets continuously with one Packet Sniffer. But when i disconnect the cc debugger and power off/on the dev kit again, i can only see one (to three adv) packet(s).

With the same project with CC2540F256, i can see   the adv packets continuously as i expected.

Do you know where i missed something for CC2541F128 to let it work?

You are highly appreciated for any comment and help.

BR,

Sun

  • With POWER_SAVING ON, after some timeout, the pwrmgr_attribute.pwrmgr_task_state would be 0x01 and there would be no advertising.

    Could we let the CC2541 in advertising state when it is in sleep mode with POWER_SAVING  ON?

  • Hello. 

    1. Are you using our EM or is this on your own board?

    2. Does this occur if you don't define POWER_SAVING in the project?

    -Tim

  • Hi Tim,

    1. We are using one BLE113 from Bluegiga - one CC2541DK-MINI is ordered and it would arrive at my place in next week.

    2. If i don't define POWER_SAVING, it would not occur - it would advertise as we expect.

    BR,

    Sun

  • Hello.  This leads me to believe that it is a hardware issue.  Please provide an update if the issue continues with the CC2541DK-MINI.

    Regards,

    Tim

  • Hi,

    we are also using the BLE113 and do see the same problems.

    Do you have a solution for the BLE113 module?

    Thanks

    Marcus

  • Hi,

    I'm facing the same problem.

    I'm testing the Simple BLE Peripheral demo on BLE113 128K Flash Hardware without any kays/botton. 

    All seems to work fine for 10 Hours.. After that, the BLE113 stop to respond to scan request and it is impossible to connect to the device.

    The only way to restore the normal work is to disconnect the 3V battery and reconnect again.

    I notice also that when the BLE113 stop to work, the battery (CR2032) charge level go down from 90% to 60%.

    The Same software compiled and tested on  TI CC2540 Keyfob and TI SensorTAG work fine.

    The only difference is that the TI devices have 256K Flash while the BLE113 has 128k Flash 

     Any idea regarding this problem with ble113 ???

    Thanks,

    Vittorio

  • Hello.  If you are using the default simpleBLEperipheral project that comes with the TI stack, there is no 128kB project configuration.  See the following wiki page for creating a 128 kB project:

    http://processors.wiki.ti.com/index.php/128kproject

    -Tim