RTOS/CC1350: CC1350 BLE Simple Peripheral Project Warnings and code execution failure

Michael Cress

Part Number: CC1350
Other Parts Discussed in Thread: CC2650

Tool/software: TI-RTOS

Hello:

I just installed the CC1350 SimpleLink SDK via the CCS Resource Explorer and imported the BLE simple peripheral sample project. The project builds to completion. However, the simple peripheral RTOS task doesn't execute and the Warnings window shows two warnings related to undefined environment variables. I have verified that the env vars are present but not set ( see screenshot ). How did this happen and how should I set the variables?

Thank you,

Michael Cress

over 6 years ago

0 Jessica H. over 6 years ago

TI__Genius 11535 points

Hi Michael,

What version of CCS are you using?

0 Michael Cress over 6 years ago in reply to Jessica H.

Expert 1455 points

Hi Jessica,

It's the latest...v8 I think?

Michael

0 Jessica H. over 6 years ago in reply to Michael Cress

TI__Genius 11535 points

Hi Michael,

I tried loading that example and received the same warnings. You can just delete those two defines from the include paths and it should work. You will also need to make sure you delete it from the stack project to remove the warning. My RTOS task ran OK and I was able to execute the project. Did you build the stack project as well? This SDK was ported to run on CCSv8.2 so it is recommended that you use that if you aren't already. To check the exact version, go to Help->About Code Composer Studio and it will give the version number.

0 Michael Cress over 6 years ago in reply to Jessica H.

Expert 1455 points

Jessica,

I am running CCSv8.2 with the latest updates to the various SDKs I have installed. I reimported and rebuilt the simpe ble peripheral sample project on my CC1350 board this evening with optimization turned off and still nothing happens for me. I am placing a breakpoint on simple_peripheral.c line 615 ( within the infinite loop of the BLE peripheral task ) and it never hits. The main() falls through to BIOS_start() but it never executes even SimpleBLEPeripheral_init().

Regards,

Michael

0 Jessica H. over 6 years ago in reply to Michael Cress

TI__Genius 11535 points

Hi Michael,

Does it stop if you place a breakpoint on a line that is not associated with ICALL? When this happens, does the device still advertise? Are you able to find the device using a BLE Scanner? Sometimes there are optimizations in the stack code that still exist even when you turn optimization off and as a result it may skip a breakpoint.

0 Michael Cress over 6 years ago in reply to Jessica H.

Expert 1455 points

I previously tried putting a breakpoint on line 604 ( SimpleBLEPeripheral_init() ) with no results. Just to be sure, I reran the test just now and don't see anything.

Michael

0 Michael Cress over 6 years ago in reply to Jessica H.

Expert 1455 points

Also, with respect to advertising, I had installed a TI Bluetooth Scanner app off of Google Play and it listed some results. However, none of them showed anything named "SimpleBLEPeripheral". It was working though because it picked up a Blue Gecko board that is advertising nearby.

Michael

0 Michael Cress over 6 years ago in reply to Jessica H.

Expert 1455 points

I just tried with a second CC1350 launchpad with identical results ( no call into simple ble peripheral task function ), so I don't think it is an issue with the one board.

Michael

0 Michael Cress over 6 years ago in reply to Jessica H.

Expert 1455 points

Ok...I have made progress. According to e2e.ti.com/.../689321, and subsequently dev.ti.com/.../platform.html, it seems that I have to Debug the stack project prior to debugging the app project in order to install some stack-related stuff. I now see it advertising and can connect to it with the TI Android app, which is good news I suppose.

I just am left with a question regarding development and the move to production process. From what I have read on the forums, this is the preferred starting point for BLE development with this Launchpad. So, why does the stack app have to be executing first? Is there not a way to force that within the app project? If I develop a product around this part, how do I address this in the firmware of that product?

Thanks,

Michael

0 Jessica H. over 6 years ago in reply to Michael Cress

TI__Genius 11535 points

Hi Michael,

I'm glad you were able to get it to work. In our newer devices like the CC13x2, CC2640R2, and CC26x2, the stack automatically gets built and flashed with the application project. This was not a feature when the CC1350 and CC2650 were released so it wasn't added to the build configurations. There should be some way to change the pre- and post-build configurations to make. I can look into how to do this for you if you would like?

0 Michael Cress over 6 years ago in reply to Jessica H.

Expert 1455 points

Jessica,

I would appreciate it if you could do that for me. I need to understand how this is done in a production environment.

Regards,

Michael Cress

0 Jessica H. over 6 years ago in reply to Michael Cress

TI__Genius 11535 points

Hi Michael,

I am still trying to find someone that knows how to do this. So far I have not found any documentation.

0 Michael Cress over 6 years ago in reply to Jessica H.

Expert 1455 points

Thanks for keeping me posted Jessica.

Regards,

Michael

0 Jessica H. over 6 years ago in reply to Michael Cress

TI__Genius 11535 points

Hi Michael,

I'm going to close this thread and take our conversation offline.

Sub-1 GHz

Sub-1 GHz forum

RTOS/CC1350: CC1350 BLE Simple Peripheral Project Warnings and code execution failure