Pushbutton Event Handler: Part 3

Event Queue

In the two step process described at the Part 1, short and fast process should transfer information of certain event to the long and slow process. This can be done simply by raising a flag. Alternatively it can be done more systematically by using a data structure such as a ring buffer.

You can create a ring buffer whose element size is few byte long and use it as a queue to convey short information about events. Let us call it an event queue. As a minimum, you need two functions, put and get (or enqueue and dequeue).

   66 #define EVT_QDEPTH              (8)
   67 /** The maximum size of the event data. It consists of one byte of event code
   68  * with variable length of data bytes.
   69  */
   70 #define EVT_QWIDTH              (16)
   71 
   72 /// Register a new event
   73 bool Evt_EnQueue(uint8_t *event);
   74 /// Checkout the oldest event
   75 bool Evt_DeQueue(uint8_t *event);
   76 /// Initialize the event queue
   77 void Evt_InitQueue(void);

As for the usage, for the sake of argument, let us the first byte of a queue element denote the category of event and the next byte detailed type. Then we can define event data structure for pushbutton handler like below.

    4 /** Pushbutton input event
    5  *
    6  * Event Data: (EVT_SRC)(EVT_TYPE)
    7  * 
    8  *  * EVT_SRC: id of the pushbutton that generated the event
    9  *  * EVT_TYPE: type of the event such as single click, double click, 
   10  */
   11 #define PBTN_INPUT              0x10        ///< event Source: pushbutton input
   12 
   13 #define PBTN_SCLK               0x01        ///< event Type: single click 
   14 #define PBTN_LCLK               0x02        ///< event Type: long click
   15 #define PBTN_DCLK               0x03        ///< event Type: double click
   16 #define PBTN_TCLK               0x04        ///< event Type: triple click
   17 #define PBTN_DOWN               0x05        ///< event Type: button state down
   18 #define PBTN_ENDN               0x06        ///< event Type: button state changed to up

When event is detected by the fast process (PushButton_Routine), it pushes relevant information to the queue.

  112         // up-down mode
  113         if(((pp.mode >> i) & 0x01)  == PUSHBTN_MODE_UDOWN)
  114         {
  115             // the button pressed
  116             if(((pp.new_state >> i) & 0x01) == 0x01)
  117             {
  118                 event[0] = EVT_PBTN_INPUT;
  119                 event[1] = (uint8_t)(i+1);
  120                 event[2] = PBTN_DOWN;
  121     
  122                 // post the event as long as the button is pressed down
  123                 Evt_EnQueue(event);
In the main loop, event handler (slow process) keeps checking the queue and processes it whenever new event is posted.
  115     while (1)
  116     {
  117         /* USER CODE END WHILE */
  118 
  119         /* USER CODE BEGIN 3 */
  120 
  121         // check event queue
  122         if(Evt_DeQueue(event))
  123         {
  124             switch(event[0])
  125             {
  126             // pushbutton event ================================================
  127             // event[1]: button id
  128             // event[2]: PBTN_SCLK, _DCLK, _TCLK, _LCLK, _DOWN, _ENDN
  129             case EVT_PBTN_INPUT:
  130 
  131                 if(event[2] == PBTN_SCLK)
  132                 {
  133                     UartPrintf("\r\nButton %d: single click.", event[1]);
  134                 }

(timing consideration) Since the software timer is based on 1 msec SysTick, each callback should do its job much faster than 1 msec, preferably within a few millisecond. So slow routines such as ADC conversion or SPI transaction should be strictly avoided.

(race condition) The event queue is shared by the slow processes and the fast processes, where the fast processes preempt the slow processes since they are the callback of SysTick interrupt. To avoid race condition, Software timer should be paused when slow process access the queue.

   63 bool Evt_DeQueue(uint8_t *event)
   64 {
   65     uint8_t i;
   66     bool flag = false;
   67 
   68     // disable all timers
   69     UsrTimer_Enable(false);
   70 
   71     // queue is not empty
   72     if(evt_queue.tail != evt_queue.head)
   73     {
   74         // copy event bytes into the buffer
   75         for(i = 0; i < EVT_QWIDTH; i++)
   76         {
   77             event[i] = evt_queue.buff[evt_queue.tail][i];
   78         }
   79         // move to the next position
   80         evt_queue.tail = ADVANCE_QPTR(evt_queue.tail);
   81         // set flag
   82         flag = true;
   83     }
   84 
   85     // enable all timers
   86     UsrTimer_Enable(true);
   87 
   88     // return with the flag
   89     return flag;
   90 }

(source code)

Pushbutton Event Handler: Part 2

Software Timer

In typical hardware timer use cases, you set up a timer with certain settings such as interval then assign a callback function that is called when the timer expires and let the function do certain task. You can instead write a timer callback function to call other callback functions, i.e. cascade the callback functions. This way, you can hook up multiple callback functions to a timer with arbitrary interval. Original timer now works as a base timer but the callback function works as a software timer.

Cortex-M processors have generic 1 millisecond timer called SysTick. Write a SysTick callback function that handles host of other callback functions with intervals of multiple of 1msec. For example, you can make the SysTick callback function call pushbutton state check routine every 300msec, as well as many other routines that are called at various intervals.

In STM32Cube framework, SysTick interrupt handler calls the function HAL_SYSTICK_IRQHandler (Warning: This was broken in the version 5.0.0 of STM32CubeMX. So you need to do it manually), which in turn calls HAL_SYSTICK_Callback function.

    1 /**
    2 * @brief This function handles System tick timer.
    3 */
    4 void SysTick_Handler(void)
    5 {
    6     /* USER CODE BEGIN SysTick_IRQn 0 */
    7 
    8     /* USER CODE END SysTick_IRQn 0 */
    9     HAL_IncTick();
   10     HAL_SYSTICK_IRQHandler();
   11     /* USER CODE BEGIN SysTick_IRQn 1 */
   12 
   13     /* USER CODE END SysTick_IRQn 1 */
   14 }

Thus it is a good place to put your software timer routine.

  355 /** SysTick callback function override.
  356  */
  357 void HAL_SYSTICK_Callback()
  358 {
  359     // UsrTimer_Routine will have 1msec resolution
  360     UsrTimer_Routine();
  361 }

Following example registers a function that toggles LED at every 100msec.

    1 void TestCallback()
    2 {
    3     HAL_GPIO_TogglePin(LED_GPIO_Port, LED_Pin);
    4 }
    5 
    6 main()
    7 {
    8     // start software timer routine
    9     UsrTimer_Init();
   10 
   11     // register a callbackfunction with 100msec interval
   12     UsrTimer_Set(100, 0, TestCallback);

Software timer implemented in the sample project file support following functions

   43 /// Initialize all timers
   44 void UsrTimer_Init();
   45 /// Enable or disable main routine
   46 void UsrTimer_Enable(bool flag);
   47 /// Clear the timer
   48 void UsrTimer_Clear(uint32_t index);
   49 /// Pause the timer 
   50 void UsrTimer_Pause(uint32_t index);
   51 /// Resume the timer
   52 void UsrTimer_Resume(uint32_t index);
   53 /// Main timer routine
   54 void UsrTimer_Routine(void);
   55 /// Set a new timer with the callback function
   56 int UsrTimer_Set(uint32_t interval, uint32_t duration, usrtimer_callback f);

(source code)

Pushbutton Event Handler: Part 1

Project Design

Pushbuttons or tactile switches are most popular input devices. But properly handling them is not so trivial. Let us check out what do we need to consider for the implementation.

(Chattering and Debouncing) Most type of mechanical contact switches produce contact bouncing effect. Following snapshot of an oscilloscope taken from Wikipedia illustrates this phenomenon well.

Actual situation varies a lot depending on the type of switch however. In a certain way chattering like above is quite exceptional, since it lasts only 2-3msec. Such short chattering can be dealt with simple hardware like R-C filter. More typically however chattering can last more than 100msec easily.

Robust implementation of pushbutton input handler thus requires polling of the switch state with a regular interval, eliminating erroneous input caused by momentary glitches.

(Short Click, Long Click and Multiple Click) Sometimes you want to assign a multiple functions on a single switch. You may want to distinguish between short click and long click or you may want to assign different tasks for single click, double click, triple click and so on.

This requires an algorithm that keeps track of the state of the button in time. For example when a single click is detected, it should be able to determine whether it has to wait certain amount of time for the next click or it can declare the single click event now. The timer based pushbutton state polling routine is well suited for this purpose.

(Event Generation and Handling) Finally, there is a situation when you want to divide one task into at least two parts, one part that needs to be executed in very short duration of time, usually much less than a millisecond, and the other part that has no particular time limit and that can be interrupted at any moment.

Instead of having a single routine that (1) polls states of pushbuttons regularly (2) determines the type of the button action based on the history, (3) then run certain tasks depending on the result of (2), you can divide them into two parts, i.e. fast processing part (1+2) and slow processing part (3). The fast processing part can be implemented as a interrupt callback function since it takes only a few microseconds at most. Then it generates an event when valid input is detected. The slow processing part can be called in a main loop checking the event, runs dedicated function if necessary, with no particular time constraint.

In the following posts, we will implement basic structure on a STM32 platform.