Other Parts Discussed in Thread: CC2650
Hello,
There are two questions, perhaps each warranting an individual thread but I'm wondering if they're related. As background: I have imported the SensorTag project into Code Composer Studio because I have a Rev 1.3 CC2650 sensor tag (and dev debugger pack) and I would like to utilize this platform for my application...
The CCS project import path is: C:\ti\simplelink\ble_cc26xx_2_01_01_44627\Projects\ble\SensorTag\CC26xx\CCS\SensorTag which should be the default install path.
I should note that I had to include "st_util.h" in PROFILES/peripheral.h to resolve 'bStatus_t' for compilation; unsure if this is indicative of a larger issue.
Once the application compiled it was downloaded to the sensortag. I next used a service discovery device (Asus BT400 and node js noble). The results of this polling indicated that the SensorTag was not advertising by default.
So as a sanity check I tried to put breakpoints on the initialization functions of the sensors, and the SensorTag task initialization functions to check to see if any of that code was being executed. The breakpoints never resolved.
Then I tried implementing a regular application task (with low priority, ie 1) to blink an LED similar to basic RTOS examples (ie set up a task with a blink rate argument and register the task). The LED does not blink... so does ICall scheduling preempt any other task scheduling or is there an issue with the overall application?
I would be happy to provide any code that might help shed some light on this issue; this is step 0/10 for me so it appears like this is going to be a long and painful climb to resolving. I also saw this thread: https://e2e.ti.com/support/wireless_connectivity/bluetooth_low_energy/f/538/t/451388 if I'm not the only person with this problem.
