CC2640R2F: Sensor controller data only setup and sends on debug or reset

its a simple peripheral project, the same issue I have with the newer version of our firmware for a cc2652rb

i both initialise and then poll the sensors using

// Schedule the next execution
fwScheduleTask(1);

i believe there to be something wrong with initalising the sensor on startup on power cycle could it be to do with this, I set up the sci before tasks ect as instructed running at 40hz readings

using i2c the pins are definitely not being shared anywhere, on startup cannot find any logical reason why on debug and reset the values from the sensor would be valid and power cycle would be 0

isit possible to read out the tick value from the sensor contoller?

Hey Alexander,

I'm linking your prior related E2E thread for reference.  I have several questions:

• Are you experiencing this issue with the standalone SCS-provided CCS project or does it only occur after integrating the BLE project? 
  
• Are you using the on-chip/off-chip OAD version of simple_peripheral? 
  
• Is the BLE functionality still working as expected although the SCS is unresponsive? 
• Have you also tested this behavior with a JTAG or other 3.3V power supply instead of the battery?  What is the battery voltage?  
• Have you tried initializing the SCIF Driver after BLE initialization within the application task?

You could provide the tick as a counter variable to the application.

Regards,
Ryan

it is once integrated into a BLE project

Not using any OAD version in this instance

BLE functionality is correct it is reading the same values over and over or zero

yes the behaviour was both battery and JTAG

Yes I believe this did resolve the issue, I added a large delay at the beginning of the sensor setup and set the sensor controller to setup on BLE connection not on power up, this resolves the issue I believe, thanks

How can I expose the tick as a counter from within sensor controller? thanks

Thanks for confirming that the issue was a startup race condition.  There are several tick sources in the Sensor Controller so I don't know exactly what you are referring to.  My suggestion was to create a variable which is incremented every time the Execution Code is processed.

Regards,
Ryan

so we are running the sensor controller at 40hz and we want to make sure that there isnt a delay between that data as previously when reading the sensors through i2c on the boards the timestamp showed a larger gap of readings than 25ms, due to the functions taking longer, so what we wanted was extra to the timestamp we have external to the sensor controller, a way of confirming these readings are taking place at 40hz, and our external timestamp isnt timestamping older readings ect

Thank you for providing further details.  The Sensor Controller can send an ALERT event at which point the System CPU can record the time within the application callback.  https://software-dl.ti.com/lprf/sensor_controller_studio/docs/cc13x2_cc26x2_help/html/firmware_framework__1.html 

Regards,
Ryan