GPIOET interrupt and PPI in S110

RE: GPIOET interrupt and PPI in S110

AmbystomaLabs — Thu, 19 Apr 2018 15:11:21 GMT

So to be clear, what you are saying is that you are getting the correct timing values now but the SD stops working, correct?

So I don't have to read through your code and guess, how many gpiote ISR's are you generating per second?

RE: GPIOET interrupt and PPI in S110

Linlei — Thu, 19 Apr 2018 14:58:02 GMT

When I send signals to the pins, I can get the datas that I want. But then the bluetooth will disconnect , if the phone connect the board with BLE. And I cannot connect again. Looks the GPIOTE interrupt that I add in the GPIOTE_IRQHandle in the nrf_drv_gpiote.c cause the SD run out. How should I use the GPIOTE interrupt and does not affect the SD to run??

void GPIOTE_IRQHandler(void)
{
    uint32_t status = 0;
    uint32_t input = 0;
//I add the GPIOTE IN[0]and[1]
		if ((NRF_GPIOTE->EVENTS_IN[0] == 1) && (NRF_GPIOTE->INTENSET & GPIOTE_INTENSET_IN0_Msk))
    {
        NRF_GPIOTE->EVENTS_IN[0] = 0; //ÖÐ¶ÏÊÂ¼þÇåÁã.
				if(capture_state==1)
				{
					  NRF_PPI->CHENCLR = (PPI_CHEN_CH4_Enabled << PPI_CHEN_CH4_Pos) ;
					capture_state=2; 
					nrf_gpio_pin_clear(20); 
				}		
	   }
		
		 if ((NRF_GPIOTE->EVENTS_IN[1] == 1) && (NRF_GPIOTE->INTENSET & GPIOTE_INTENSET_IN1_Msk))
    {
				
        NRF_GPIOTE->EVENTS_IN[1] = 0; //ÖÐ¶ÏÊÂ¼þÇåÁã.
				if(capture_state==2)
				{	
					 NRF_PPI->CHENCLR = (PPI_CHEN_CH5_Enabled << PPI_CHEN_CH5_Pos) ;
					NRF_TIMER2->TASKS_CAPTURE[0] = 1;
					shoot_flag=1;						
	//				capture_time= NRF_TIMER2->CC[0];
					nrf_gpio_pin_clear(20);
					lock_time=10; 
					capture_state=3;
					NRF_TIMER2->TASKS_START = 1;					
				}
	//		  NRF_TIMER2->TASKS_STOP = 1;		//Í£Ö¹¶¨Ê±Æ÷
	//		NRF_TIMER2->TASKS_CAPTURE[0] = 1;		//²¶×½ÈÎÎñ
	//		capture_time= NRF_TIMER2->CC[0];		//»ñµÃÊ±¼ä		
	    }
			if(capture_state==3) lock_time=10;
//the end of my code

    /* collect status of all GPIOTE pin events. Processing is done once all are collected and cleared.*/
    uint32_t i;
    
    //I modified the events 0-3 to 2-3
   nrf_gpiote_events_t event = NRF_GPIOTE_EVENTS_IN_2;// nrf_gpiote_events_t event = NRF_GPIOTE_EVENTS_IN_0;			//´ÓÊÂ¼þ0¿ªÊ¼
    uint32_t mask = (uint32_t)NRF_GPIOTE_INT_IN2_MASK;//uint32_t mask = (uint32_t)NRF_GPIOTE_INT_IN0_MASK;			//ÖÐ¶Ï0±êÖ¾Î» mask±êÖ¾£¬ÆðÊ¼µÄµØÖ·
    for (i = 2; i < NUMBER_OF_GPIO_TE; i++)//for (i = 2; i < NUMBER_OF_GPIO_TE; i++)						//0-4
    {
        if (nrf_gpiote_event_is_set(event) && nrf_gpiote_int_is_enabled(mask))			//Èç¹ûÊÂ¼þÒÑ¾ÉèÖÃ£¬ÖÐ¶ÏÊ¹ÄÜ£¬Çå³ý±êÖ¾£¬×´Ì¬¼ÇÂ¼ÄÇÐ©Éè¶¨ÁËÊÂ¼þ
        {
            nrf_gpiote_event_clear(event);
            status |= mask;
        }
        mask <<= 1;
        /* Incrementing to next event, utilizing the fact that events are grouped together
         * in ascending order. */
       event = (nrf_gpiote_events_t)((uint32_t)event + sizeof(uint32_t));		//ÊÂ¼þµØÖ·ÒÆÎ»
    }

    /* collect PORT status event, if event is set read pins state. Processing is postponed to the
     * end of interrupt. */
    if (nrf_gpiote_event_is_set(NRF_GPIOTE_EVENTS_PORT))		//Èç¹û¶Ë¿ÚÊÂ¼þÉè¶¨
    {
        nrf_gpiote_event_clear(NRF_GPIOTE_EVENTS_PORT);			//Çå³ý
        status |= (uint32_t)NRF_GPIOTE_INT_PORT_MASK;				//×´Ì¬¼ÇÂ¼
        input = nrf_gpio_pins_read();												//Òý½Å¶ÁÈ¡
    }

    // Process pin events. 
    if (status & NRF_GPIOTE_INT_IN_MASK)										//ÖÐ¶ÏÊäÈë±êÖ¾ÓëÖÐ¶ÏÊäÈë±êÖ¾½øÐÐ±È½Ï£¬Èç¹ûÓÐÊäÈë±êÖ¾
    {
        mask = (uint32_t)NRF_GPIOTE_INT_IN2_MASK;//mask = (uint32_t)NRF_GPIOTE_INT_IN0_MASK;						//´ÓIN0µÄÖÐ¶Ï¿ªÊ¼£¬ÂÖÑ¯4´Î
        for (i = 2; i < NUMBER_OF_GPIO_TE; i++)//for (i = 0; i < NUMBER_OF_GPIO_TE; i++)
        {
            if (mask & status)															//Èç¹ûÖÐ¶Ï±êÖ¾ºÍÊ¹ÄÜ×´Ì¬
            {
                nrf_drv_gpiote_pin_t pin = nrf_gpiote_event_pin_get(i);				//		¶ÁÈ¡GPIOTE[i]¶ÔÓ¦µÄÊÇÄÄ¸öÒý½Å
                nrf_gpiote_polarity_t polarity = nrf_gpiote_event_polarity_get(i);			//  ¶ÁÈ¡GPIOTE[i]ÉèÖÃµÄÊÇÊ²Ã´¼«ÐÔ 
                nrf_drv_gpiote_evt_handler_t handler = channel_handler_get(i);					//m_cb.handlers[channel]
                handler(pin,polarity);											//´¦ÀíÒý½Å£¬¼«ÐÔ  
            }
            mask <<= 1;																			//ÒÆÎ»£¬´¦ÀíÏÂÒ»¸ö
        }
    }

    if (status & (uint32_t)NRF_GPIOTE_INT_PORT_MASK)				//ÅÐ¶Ï¶Ë¿Ú±êÖ¾ÊÇ·ñÊ¹ÄÜ
    {
        // Process port event. 												//´¦Àí¶Ë¿ÚÊÂ¼þ
        for (i = 0; i < GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS; i++)
        {
            if (m_cb.port_handlers_pins[i] != PIN_NOT_USED)
            {
                uint8_t pin_and_sense = m_cb.port_handlers_pins[i];
                nrf_drv_gpiote_pin_t pin = (pin_and_sense & ~SENSE_FIELD_MASK);
                nrf_drv_gpiote_evt_handler_t handler = channel_handler_get(channel_port_get(pin));
                if (handler)
                {
                    nrf_gpiote_polarity_t polarity =
                            (nrf_gpiote_polarity_t)((pin_and_sense & SENSE_FIELD_MASK) >> SENSE_FIELD_POS);
                    mask = 1 << pin;
                    nrf_gpio_pin_sense_t sense = nrf_gpio_pin_sense_get(pin);
                    if (((mask & input) && (sense==NRF_GPIO_PIN_SENSE_HIGH)) ||
                       (!(mask & input) && (sense==NRF_GPIO_PIN_SENSE_LOW))  )
                    {
                        if (polarity == NRF_GPIOTE_POLARITY_TOGGLE)
                        {
                            nrf_gpio_pin_sense_t next_sense = (sense == NRF_GPIO_PIN_SENSE_HIGH) ?
                                    NRF_GPIO_PIN_SENSE_LOW : NRF_GPIO_PIN_SENSE_HIGH;
                            nrf_gpio_cfg_sense_set(pin, next_sense);
                        }
                        handler(pin, polarity);
                    }
                }
            }
        }
    }
}

RE: GPIOET interrupt and PPI in S110

Linlei — Mon, 16 Apr 2018 12:33:13 GMT

Ambystomalabs, thank you very much for your answer. Now, I am trying the SD8.0 . I know I use the new SD must match the API. I tested the example program "ble_app_uart", because it is close to that I want. The example program works well on my board.

The APP is very simple. It get the time of signals on the two pins, calculate and send the datas out by Bluetooth and uart. So I don't worry about the bluetooth traffic will effect the measurement. Now I can use the PPI,it can work. And I can set the interrupt of GPIOTE. I add my codes in the GPIOTE_IRQHandle() in the nrf_drv_gpiote.c . Looks, it can work well.

void GPIOTE_IRQHandler(void)
{
    uint32_t status = 0;
    uint32_t input = 0;
    //these are my codes
	if ((NRF_GPIOTE->EVENTS_IN[0] == 1) && (NRF_GPIOTE->INTENSET & GPIOTE_INTENSET_IN0_Msk))
    {
        NRF_GPIOTE->EVENTS_IN[0] = 0; //ÖÐ¶ÏÊÂ¼þÇåÁã.
		if(capture_state==1)
		{
			//	NRF_TIMER2->TASKS_START = 1; 
			//NRF_TIMER2->TASKS_CLEAR = 1; 
		    capture_state=2; 
		}		
	}
		
	if ((NRF_GPIOTE->EVENTS_IN[1] == 1) && (NRF_GPIOTE->INTENSET & GPIOTE_INTENSET_IN1_Msk))
    {
				
        NRF_GPIOTE->EVENTS_IN[1] = 0; //ÖÐ¶ÏÊÂ¼þÇåÁã.
				if(capture_state==2)
				{		
					NRF_TIMER2->TASKS_CAPTURE[0] = 1;
					shoot_flag=1;						
					capture_time= NRF_TIMER2->CC[0];
					nrf_gpio_pin_clear(20);
					lock_time=10; 
					capture_state=3;
					NRF_TIMER2->TASKS_START = 1;					
				}
	//		  NRF_TIMER2->TASKS_STOP = 1;		//Í£Ö¹¶¨Ê±Æ÷
	//		NRF_TIMER2->TASKS_CAPTURE[0] = 1;		//²¶×½ÈÎÎñ
	//		capture_time= NRF_TIMER2->CC[0];		//»ñµÃÊ±¼ä		
	    }
			if(capture_state==3) lock_time=10;
			

    /* collect status of all GPIOTE pin events. Processing is done once all are collected and cleared.*/
    uint32_t i;
   nrf_gpiote_events_t event = NRF_GPIOTE_EVENTS_IN_2;// nrf_gpiote_events_t event = NRF_GPIOTE_EVENTS_IN_0;			//´ÓÊÂ¼þ0¿ªÊ¼
    uint32_t mask = (uint32_t)NRF_GPIOTE_INT_IN2_MASK;//uint32_t mask = (uint32_t)NRF_GPIOTE_INT_IN0_MASK;			//ÖÐ¶Ï0±êÖ¾Î» mask±êÖ¾£¬ÆðÊ¼µÄµØÖ·
    for (i = 2; i < NUMBER_OF_GPIO_TE; i++)//for (i = 2; i < NUMBER_OF_GPIO_TE; i++)						//0-4
   ...............

RE: GPIOET interrupt and PPI in S110

AmbystomaLabs — Sun, 15 Apr 2018 15:30:14 GMT

I meant this as a general statement, your code shows you capture in gpiote: "For the timings you have specified you can't possibly do it in handlers. Just pushing the registers to the stack and moving the program counter takes about 12 clocks, then depending on how many other things are queued up ahead of you will cause your ISR to be serviced later.

APP ISR's have a much lower priority than the SD. This is required to satisfy BLE radio protocol requirements. Advertisements alone will can cause delays of up to 1msec or more. Heavy BLE traffic will cause more frequent delays.

The basic timing of the Pclk is 16MHz. Most activities take about 2 clocks so the min resolution of the timers is functionally 0.125usec."

In order to achieve this you need to use PPI/GPIOTE to start and stop/capture the timers directly which I see you are doing in your code. You don't want to have the shorts enabled since you are counting and it appears you have that correct.

Your prescaler of 4 will give a 1MHz pclk or 1usec resolution.

You need to make sure that HFCLK is on all the time. Offhand I can't remember if using a timer forces the HF_EXT to run. You should double check the nrf51 series reference manual on this. If not you can either start it manually whenever you are doing your timing events or you can tell the SD to keep it on all the time. There are plenty of notes in the devzone on doing this just look it up. Otherwise the SD may put it on HFRC instead of HFEXT when your timer is running.

The problem I see happening in your solution is that your external event happens, the timer starts, event stops timer stops and there is enough delay that your don't get into the ISR fast enough to get the counter register and instead you get into the isr while the timer is running again. If you don't mind throwing away some data points just look to see if the timer is running when you are in the handler to prevent this mistake.

RE: GPIOET interrupt and PPI in S110

AmbystomaLabs — Sun, 15 Apr 2018 15:01:47 GMT

You only use the SD that comes with the SDK. So, not really an issue of using an old one, just using the correct one. SDK's and SD's are released in pairs. The SD's are in the components folder. Only by using the matching SD will the libraries and API calls work out. The API's are constantly changing and being improved on. Thus each new SD gets a new SDK. When one moves a project from one SDK to a later version (only if required for features, it is not normally necessary to do this) then you need to do some extensive reading of the SD release notes to make sure you are using the correct API's as they may be different.

RE: GPIOET interrupt and PPI in S110

Linlei — Sun, 15 Apr 2018 12:19:43 GMT

I can use PPI with the SDK 10.0. The errors of the time datas were less than 10us, although they were a bit of volatility. But I can not use GPIOTE interrupt with SD. If I set the interrupt of GPIOTE, it can run at first time. After that, it looks the SD clear the interrupt of GPIOTE, I can see the GPIOTE events be on, but it doesn't respond to the interrupt of GPIOTE events.

RE: GPIOET interrupt and PPI in S110

Linlei — Sat, 14 Apr 2018 01:10:06 GMT

Thank all of you. I find the table 22 and 24 in the S110_SDS_v2.pdf that about PPI and GPIOTE. The SD uses the channel 14-15. The APP can use channel 0-13. I think the SDK I used is too old. Now I am trying the SDK 10. But find I can not use GPIOTE interrupt directly. If I use bsp_event_handler, the delay is about 700us, it is too long.

I want to measure the time from a signal on one pin to another. About 200us-50ms. Error should less than 5us. How can I do?

RE: GPIOET interrupt and PPI in S110

AmbystomaLabs — Sun, 08 Apr 2018 20:30:37 GMT

As Turbo said, you have to use the API's to assign and enable/disable PPI channels. The SD uses PPI and thus will write over your settings. You can set gpiote directly through the register if you wish.

These are some of the API's. You would find them all listed in the SD reference docs.

sd_ppi_channel_assign
sd_ppi_channel_enable_set

You will find the PPI reserved channels on page 169 of the product spec.

RE: GPIOET interrupt and PPI in S110

Turbo J — Sun, 08 Apr 2018 18:35:02 GMT

Check the softdevice specifications, some PPI channels are reserved for softdevice usage. Also, direct access to PPI peripherial might be forbidden when softdevice is active.