ASF4 : configuring external IO interrupts without Event Driver?

Log in or register to post comments
Go To Last Post
4 posts / 0 new
Author
Message
bird-man
bird-man's picture
Level: Rookie
Joined: Thu. Jun 27, 2019
Posts: 48 View posts
Location: Tennessee, USA
#1
Posted by bird-man: Tue. Jul 9, 2019 - 04:58 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

ASF4 reference manual provides description and example of External IO Interrupts implementation done without Event Driver. I also found similar example API code after configuring and downloading configuration for the SAME70-XPLD board. After proper re-configuration of the pin to match pin used for the on-board button and placing this code in the right file the project did not trigger Interrupt.

After trying different variation of the same approach I came to think that this path might be not working in ASF4 because it might require the Event System Driver to be called to process any external Interrupt.

The following made me think this way - I found example of using External IO Interrupt in ASF4 - the SAM D21 Event System example. It does trigger interrupt driven input from the button but here this is done using Event Driver.

So the larger question is as follows, in ASF4  :

can the external interrupts be processed and implemented using the direct registration of User Callback function (as per Chapter 19 of ASF4 manual) WITHOUT registration with Event Driver (meaning that both approaches can work - with or without Event Driver) ?

or

the External Interrupt will only work in ASF4 if the Callback is registered with the Event System Driver and not otherwise (which means the Ch. 19 example is wrong)?
 

This is important topic to de-mystify ASF4  so please clarify...

 

This topic has a solution.

Tags:

Tools, Atmel Studio (ARM-related), #ASF4 #External Interrupts #Event Driver, solved, #sam #e70 #cortex #m7 #sam #3X #m4
Last Edited: Wed. Jul 10, 2019 - 04:28 AM
Top
Lajon
Lajon's picture
Level: Raving Lunatic
Joined: Fri. Mar 12, 2004
Posts: 2932 View posts
Location: Linköping, Sweden
This reply has been marked as the solution. 
Posted by Lajon: Tue. Jul 9, 2019 - 08:24 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

The gfx mono menu example is not using the event driver.

/Lars

Top
bird-man
bird-man's picture
Level: Rookie
Joined: Thu. Jun 27, 2019
Posts: 48 View posts
Location: Tennessee, USA
Posted by bird-man: Wed. Jul 10, 2019 - 04:28 AM (Reply to #2)
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thank you Lajon for pointing to this example. I repeated it's setup for the IRQ driven button and it worked. This fully answers my question - External IRQ can be used directly through Callback or by registering with Event Driver.

Thanks again

Vlad

Last Edited: Wed. Jul 10, 2019 - 04:29 AM
Top
VGS_MLN
VGS_MLN's picture
Level: New Member
Joined: Thu. Jan 20, 2022
Posts: 13 View posts
Location: Germany
Posted by VGS_MLN: Wed. May 4, 2022 - 01:03 PM (Reply to #2)
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi Lars,

I had a look at the GFX example. I just don't understand why the INTFLAG register with the corresponding interrupt number is not written with a '1' after the interrupt occurs. That would be much faster than deleting the interrupt and registering it again. Do you have any idea why this is done?

 

static void BUTTON2_pressed(void)
{
	gfx_mono_menu_process_key(&MONOCHROME_WIDGET_0, GFX_MONO_MENU_KEYCODE_ENTER);

	delay_ms(500);
	ext_irq_register(OLED1_BUTTON2, NULL);
	ext_irq_register(OLED1_BUTTON2, BUTTON2_pressed);

	gpio_set_pin_level(OLED1_LED1, on);
}

 

ATSAMx5x INTFLAG

 

Kinde regards

ATSAMC21
ATSAME51
ATMEGA

Top