CC2652R: CC2652R sdk for development of TPMS custom application

Hi,

I don't think we have a public released version of TPMS solution. Do you have a related FAE or Sales of TI? You may try to talk to them to find if there's something to apply for.
Best regards

Hi Simon,

Alright let me check and revert, thanks for the update.

Also with sdk version #simplelink_cc13xx_cc26xx_sdk_5_40_00_40, getting following build error when switching to debug build. Any suggestion

Description    Resource    Path    Location    Type
#1965 cannot open source file "ti_drivers_config.h"  

 .ccsproject    /simple_peripheral_CC26X2R1_LAUNCHXL_tirtos_ccs    line 62, external location: C:\ti\simplelink_cc13xx_cc26xx_sdk_5_40_00_40\source\ti\ble5stack\npi\src\inc\npi_config.h    C/C++ Problem

Additonally, I am using Code Composer Studio Version: 11.1.0.00011 but cannot find any instructions on how to resolve this build issue in debug mode by regeneration of these "ti_drivers_config.h"   files for cc2642 chip?

Hi Viany,

Did you import the simple_peripheral project right? you should follow the steps in Quick Start Guide (ti.com) .You can change another workspace to import the example code you want.

Hi Simon,

 Yes, I followed steps in quick start guide but imported /simple_peripheral_CC26X2R1_LAUNCHXL_tirtos_ccs.

It builds in release mode only, but when I switch to debug mode build fails with errors I mentioned.

Also one more observation where project zero from quick start guide only builds in debug mode.

In quick start quide I can see these section but the relevant makefile path are not present in my sdk at C:\ti\simplelink_cc13x2_26x2_sdk_5_20_00_52\kernel\tirtos\builds

"The TI Drivers project makefiles are configured to use the Release kernel configuration by default. If you want to use the debug kernel build, edit the makefile as shown below:"

Please advise if some configuration is required or setup and point me to section in quick start guide I have to relook into probably?

Regards,

Vinay

Hi,

In CCS 11 we don't edit makefile to configure the compiler, you can open file->properties to correct the illegal link of ti_drivers_config.h I believe that's the problem here.

In addition, I have tested on the newest SDK 5.40, and the problem does not show. It is the fastest way to make thing go right.

Hi Simon,

 Ok, in 5.40 the debug build issue is resolved.

But regarding your comment,

1. you can open file->properties to correct the illegal link >> did you mean to edit arm linker properties. If yes, can you be more specific about the file, sysconfig or path to edit as it might break my build system if wrongly updated?

2. In debug build I don't see any extra logging when compared to release build. Please let me know if any further configuration required to fetch these logs which has 'BLE_LOG_INT_TIME' and other debug logs dumped in my serial port console?

Hi

1-I mean not only the arm linker, but wherever the missing file links to (in your case, the ti_drivers_config.h).

2-The Debug build configuration usually has no optimization and full symbolic debug enabled, to enable easy debugging. The Release build configuration will often have optimization enabled and symbolic debug disabled, to get your code as small or fast as possible without the need for source level debug. Since the Debug configuration is what comes up by default in CCS (both when creating a new project and when importing a project) users usually start tweaking the Debug configuration directly when they are ready to start optimizing their code or modifying other compiler and linker options. Instead it would be advisable to switch to the Release configuration when you are ready to optimize your code.

I think you are looking for a way to show debug log, please review this threadCCS/TMS320F28022: Log file(s) for loading program to target - Code Composer Studio forum - Code Composer Studio︎ - TI E2E support forums

I am not sure you got my query, what I meant is to fetch bluetooth related logs under print statements like 'BLE_LOG_INT_TIME', BLE_LOG_INT_STR from TI sdk file simple_peripheral.c and other debug bluetooth driver logs to be dumped in my serial port console?

The link you mentioned is about debug server logs and not sure it helps here.

Please elaborate.

HI,

The link I mentioned is what is actually in a debug log. To print whatever you want (I think this is what you asked for ), you may need to review BLE-Stack Debugging Guide (ti.com) and do your configuration.