Clock (timer?) CC2640 UART monitoring

Alan,

Thank you for your reply. I have pasted relevant sections of the code below. If you need to see all of the SimpleBLEPeripheral file, I am happy to email the zipped up project to you. I am not finding the UART_waitFlag being set and the uart_read does not happen either. The system directly goes into BLE events.  Without the use of a clock, I can get the UART read to trigger as seen on the scope, however, after connecting to the sensor, advertising stops.

Thanks,

Priya

#define UART_READ_DELAY 3000   //time the task sleeps between consecutive UART messages

#define UART_WAIT_TIME  1000

#define UART_MSG_EVT         0x0010

#define WAIT_FOR_TALK_MODE_EVT                0x0080

In SimpleBLEPeripheral_init:

Util_constructClock(&WaitForTalkModeClock, SimpleBLEPeripheral_clockHandler,

                         UART_WAIT_TIME, 0, false, WAIT_FOR_TALK_MODE_EVT);

In SimpleBLEPeripheral_taskFxn:

    SOH = 0;
    if (events & WAIT_FOR_TALK_MODE_EVT) {
         events &= ~WAIT_FOR_TALK_MODE_EVT;

        waitForUARTMessage();
    }

static void waitForUARTMessage(void)
{
 uint8_t byte;

         Util_startClock(&WaitForTalkModeClock);

         UART_waitFlag = Util_isActive(&WaitForTalkModeClock);

         if (ValidUARTMsg)
             Util_stopClock(&WaitForTalkModeClock);

         if ((SOH == 0) || ValidUARTMsg || UART_waitFlag)
              UART_read(uart, &byte, 1);

         if (!ValidUARTMsg && !UART_waitFlag) {};

}

static void UARTCallback(UART_Handle uart, void *byte, size_t size)
{
 static uint8_t byte0, prevByte, i, MessageLength, LenInfo82, LenInfo83;

    byte0 = *((int*)byte);

    if (ValidUARTMsg){
      uart_rx_buf[i] = byte0;

      if ((uart_rx_buf[1] == 0x82) && (i == LenInfo82-1)){
       MessageLength = uart_rx_buf[i] + 5;

      if ((uart_rx_buf[1] == 0x83) && (i == LenInfo83-1)){
          MessageLength = uart_rx_buf[i] + 5;

      if ((uart_rx_buf[1] != 0x82) && (uart_rx_buf[1] != 0x83)){
       MessageLength = 5;

      i++;

            if ((uart_rx_buf[1] == 0x82) && (i == LenInfo82)){
             ValidUARTMsg = 0;
             i = 0;
             UART_enqueueMsg(MessageLength);
            }

            if ((uart_rx_buf[1] != 0x82) && (i == MessageLength) && (ValidUARTMsg == 1)){
             ValidUARTMsg = 0;
             i = 0;
             UART_enqueueMsg(MessageLength);
            }

    }

 if ((prevByte == 1) && ((byte0 >= 0x80) && (byte0 <= 0x8f))){
  SOH = 1;
  uart_rx_buf[0] = prevByte;
  uart_rx_buf[1] = byte0;

  if (uart_rx_buf[1] == 0x82)
      LenInfo82 = 6;
  if (uart_rx_buf[1] == 0x83)
   LenInfo83 = 5;

     prevByte = 0;
        ValidUARTMsg = 1;
        i = 2;
 }

 prevByte = byte0;
}

Alan,

I have attached my appBLE.cfg script to this post. Can you review it and let me know if anything is missing? Here are some sections of it:

BIOS.clockEnabled = true;

/* 10 us tick period */
Clock.tickPeriod = 10;
TIRTOS.useSPI = true;
Clock.tickSource = Clock.TickSource_TIMER;
Clock.swiPriority = 5;

Thank you,

Priya

4265.appBLE.cfg

The .cfg file looks OK to me.

In your C code, I don't see the definition of the "WaitForTalkModeClock" object. Can you verify that it is a global variable and not a function-local variable?

If I understand your code correctly, the timeout of the clock object is 1000 ticks. That translates to 10ms. But your comment says that you want to wait for 20 character times. At 9600 baud, each character takes around 1ms to transmit. So I'm thinking that timeout should be 2000 ticks. However, from your description of the problem, I think you're saying the clock function callback never gets called, not that it gets called too soon. Is that correct?

Since you're using CCS and have become familiar with ROV views. Can you please confirm that the "ticks" value in the Clock module's "module" view is advancing between successive halts and runs of the CPU?

Also can you confirm that the Hwi associated with the timer interrupt used to drive the Clock module is enabled? This can be verified by examining the detailed view within the Hwi module. IntNum 20 is the timer interrupt  number. The "status" column within the detailed view tells whether the interrupt is enabled or not. It also indicates whether it is currently pending or active. (See the second row in the screen capture below)

Alan

3007.simpleBLEPeripheral.cAlan,

Yes, the timer interrupt 20 is enabled. I created a simplified version of the application that uses only the UART. Five formatted messages are sent to the uart receive, and I use a clock to read the UART. This version works fine (processes the UART messages) without the clock. I have been editing the state machine function that monitors the UART, but in all of my versions of code, there should not be a reason why the clock callback function never gets called.

I was also thinking of a way to add a clock to the clean copy of SimpleBLEPeripheral, but there is no easy way to re-start the one shot clock. I also think this clock I added is interfering with the periodic clock in SimpleBLEPeripheral. I notice this when I try to connect to the sensor. That periodic clock is 5000 ticks and this UART wait clock is 2000 ticks, maybe this creates problems during a connection event. (SBP uses its periodic clock during the connection event).

I have put the simplified version of the application to this post if you have the time to review it.

I appreciate your time and help.

Priya

Today, I went to the CC2650 DK, 4x4 package. Added a clock to the clean copy of SimpleBLEPeripheral. I am still unable to execute any break point inside the clock callback function. I tried this with and without the task_sleep at the UART_MSG_EVT with no difference.

I have attached the copy of SimpleBLEPeripheral with the clock added to this post. I appreciate pointers on getting the clock module to work. 4331.simpleBLEPeripheral.c

Thanks,

Priya

The logic for starting the two clocks requires that the appropriate bit in the 'events' variable be set. However, I don't find any place in the code where 'events' is ever initialized with the required bits being set to true, except in the clock handler itself. Could it be that the clocks are never being started because 'events' never allows them to be?

Also, I assumed the timeout arguments passed to Util_constructClock() were in Clock tick units (ie 10us units). However, the documentation for the clockDuration argument to Util_constructClock() says the units are in milliseconds. Consequently, setting the one-shot timeouts to 2000 and 5000 will yield actual timeouts of 2 seconds and 5 seconds respectively.

Alan

One of the one shot clocks comes with SimpeBLEPeripheral and I suspect gets started at a connection event. I don't use this clock in my application.

I cannot wait to start the UART one shot clock at a BLE event (advertising or connection-- it drains battery life and cannot be done during sensor calibration). What other event do I create to start this clock? Do I keep calling construct clock inside the wait_ForUARTMessage function and have it start right away?

Thanks,

Priya