• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 1266 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC2564MODN: CC2564MODN: SPPDemo and SPPLEDemo stack won't start on console

Juan Sanchez25
Prodigy 160 points

Part Number: CC2564MODN
Other Parts Discussed in Thread: CC2564C,

Hello guys,

I'm programing a STM32DiscoveryF4 with the API "CC256x STM32 Bluetopia SDK v4.2.1.0" which TI brings, but I can't initializate the stack on console when I've programmed the board, via Keil v5.24a.

I've my TTL-USB adapter connected to the USART 2 pins PA2 (TX) and PA3 (RX) and to the ground pin. And I've make all the changes that have to be done in order to work with the DiscoveryF4 and also configure the COM port on the device manager (112500, 8, n, 1)

The SPPDemo that is on "CC256x STM32 Bluetopia SDK v4.0.2.2" WORKS on my PC via the COM port. But the SPPLEDemo don't work as the other two.

When the board is flashed, I open the COM port, reset the board and just appear:

"OpenSt"

If anyone had this problem and know how to resolve it please let mw know ASAP. I'm working on my final degree project.

Regards and thank you!!

Juanjo

  • 0
    TI__Mastermind 29361 points
    Juan,

    Have you followed every step in the "Enable_STM32_Discovery.pdf" document in the SDK? Especially hcitrans vs/ hcitrans.dma?

    Also, the latest CC256x STM32 Bluetopia SDK v4.2.1.0 is configured for CC2564C devices by default. The CC2564MODN have CC2564B IC inside it. So please make sure that the CC256XB.h is included in the BTPSVEND.c instead of the CC256XC.h.

    BR,
    Vihang
  • 0 in reply to Vihang Parmar
    Prodigy 160 points

    Hi Vihang,

    thank you for your response again.

    Yes I follow every step, and with the NoOs version of the Bluetopia SDK v4.0.2.2 I can work perfectly with the CC564MODN because it's primarly programmed for CC256XB module.

    And I've already tried your advice. The CC256XB.h is include, and I remove the CC256XC.h. And when I programmed into the board. The stack initializate with an error.

    OpenStack().
    Bluetooth Stack ID: 1
    LOW ENERGY Support not initialized -104.
    Device Chipset: 4.1
    BTPS Version  : 4.2.1.0
    PLAT Version  : 1.0
    App Name      : SPPLEDemo
    App Version   : 0.6
    Project Type  : 6
    FW Version    : 7.26
    Local BD_ADDR: 0x0017E9D335D0
    GAP_LE_Set_Pairability_Mode Failed: -104.
    SetPairable Failed: -104.

    In the preprocessor symbols I change the define and eliminate the  __SUPPORT_CC256XC_PATCH__,  what do you think that I'm missing or is wrong? Thank you so much for your support really apprecciate that!!

  • 0 in reply to Juan Sanchez25
    TI__Mastermind 29361 points
    Juan,

    The "LOW ENERGY Support not initialized -104" indicates that the BT controller does not have the LE capabilities. The (-104) error refers to the BTPS_ERROR_LOCAL_CONTROLLER_DOES_NOT_SUPPORT_LE error code defined in the BTErrors.h.

    Are you using the CC2564MODN module? Or some other module?

    BR,
    Vihang
  • 0 in reply to Vihang Parmar
    Prodigy 160 points
    Yes I'm using the CC256MODN
    do you know what is going wrong ?
  • 0 in reply to Juan Sanchez25
    TI__Mastermind 29361 points

    Juan Sanchez25 said:
    do you know what is going wrong ?

    The stack "thinks" that the controller does not support BLE. If the SPPLEDemo has been ported properly, this should not happen.

    Can you make sure that you have "__SUPPORT_LOW_ENERGY__" defined in your project settings as well?

    BR,

    Vihang

  • 0 in reply to Vihang Parmar
    Prodigy 160 points

    Yes I have done everyhting so far. In the Preprocessor Symbols I have "STM32F40_41xxx,DEBUG_ENABLED,HSE_VALUE=8000000,"assert_param(expr)"=" ",__SUPPORT_LOW_ENERGY__" and remove the patch for CC256C.

    The stack give me the same problem.