• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 538 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.

CC2642R-Q1: How do I get the protocol stack version number?

linqian wang
Intellectual 335 points
Part Number: CC2642R-Q1
Other Parts Discussed in Thread: SEGGER, CC2642R

1. Protocol stack version number Which is the API?

2, if you want to burn the program, in addition to through the IDE way, can also through jlink? In my understanding, jlink needs to burn the hex file of protocol stack and the app.hex file of protocol stack, so where is the hex file of protocol stack?

  • 0
    TI__Guru** 101490 points

    Hi,

    linqian wang said:
    1. Protocol stack version number Which is the API?

    There is no such API available

    linqian wang said:
    2, if you want to burn the program, in addition to through the IDE way, can also through jlink? In my understanding, jlink needs to burn the hex file of protocol stack and the app.hex file of protocol stack, so where is the hex file of protocol stack?

    Jlink (Segger) is supported.

    Our Bluetooth LE projects for CC2642R available in the SDK (at least since SDK 3.10, probably even before) are configured to build the stack and the application in the same HEX file.

    I hope this will help,

    Best regards,

  • 0 in reply to Clément
    Intellectual 335 points

    1. A part of API References is TI 15.4 MAC API. Can this part be applied in practical projects? I don't see usage of this part of the API in the routine ble5stack\simple_peripheral.

    2. What about the version of the protocol stack? For example, if simplelink_cc13xx_cc26xx_sdk_6_20_00_29 is the protocol stack version 6.20.00.29?

    Thank you！

  • 0 in reply to Clément
    Intellectual 335 points

    Another problem is that I don't see the serial port initialization in the routine simple_peripheral, but the routine calls to the interface TBM_SET_TITLE, BLE_LOG_INT_TIME, etc., are printable. Where is this part initialized?

  • 0 in reply to linqian wang
    TI__Guru** 101490 points

    Hi,

    linqian wang said:
    1. A part of API References is TI 15.4 MAC API. Can this part be applied in practical projects? I don't see usage of this part of the API in the routine ble5stack\simple_peripheral.

    This API is rather dedicated to projects enabling 15.4 stack.

    linqian wang said:
    2. What about the version of the protocol stack? For example, if simplelink_cc13xx_cc26xx_sdk_6_20_00_29 is the protocol stack version 6.20.00.29?

    The SDK and the BLE stack have different version numbers. The BLE stack version number can be found in the release notes of the stack (in <SDK>/docs/ble5stack/release_notes_ble5stack_x_xx_xx_xx.html).
    For example, the BLE5-Stack 2.02.06.00 is included in the simplelink_cc13xx_cc26xx_sdk_6_20_00_29.

    linqian wang said:
    Another problem is that I don't see the serial port initialization in the routine simple_peripheral, but the routine calls to the interface TBM_SET_TITLE, BLE_LOG_INT_TIME, etc., are printable. Where is this part initialized?

    The two-button menu is handled by the file two_btn _menu.c

    BLE_LOG functions are initalized in osal.c
    I wrote something about BLE_LOG_INT_ a while back https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/939054/faq-cc2642r-tips-and-tricks-to-use-ble_log_int_-functionalities

    For other questions not-related to the initial topic, it would be best you open a separate thread as it will help others to find the information. Thank you for your comprehension.

    I hope this will help,

    Best regards,

  • 0 in reply to Clément
    Intellectual 335 points

    The routine has #ifdef BLE_LOG, but I don't see #define BLE_LOG anywhere, including properties-&gt; predefined Sysbols, where is #define BLE_LOG?

  • 0 in reply to linqian wang
    Intellectual 335 points
    linqian wang said:

    1. In my understanding, the serial port needs to be initialized, but I don't see BLE_LOG related initialization, for example, I want to change the serial port properties, such as the baud rate, where should I change them?

    2. If the serial port is used for BLE_LOG, is it compatible with normal uart functions? I don't see any processing on the receiving part of the uart。

  • +1 in reply to linqian wang
    TI__Guru** 101490 points

    Hi,

    Please open a new thread for discussion non-related to the initial topic.

    Please also note BLE_LOG is used for logging to memory (not to serial). In case serial logging is needed, I would recommend to leverage the UART or Display driver.

    Best regards,