+ Reply to Thread
Results 1 to 6 of 6

Thread: XMC4000 TIP of the day: Event Request Unit (ERU) for peripherals trigger.

  1. #1
    Travis will become famous soon enough
    Join Date
    Feb 2013
    Location
    Singapore
    Posts
    749
    Points
    4580

    XMC4000 TIP of the day: Event Request Unit (ERU) for peripherals trigger.

    Our previous TIP mentioned about peripherals triggering the DMA for data transfer from a source to a destination with a DLR.

    However we can also have peripherals to trigger other peripherals to start an action without any software intervention. So to do this we make use of the Event Request Unit (ERU).

    The Event Request Unit (ERU) is a versatile multiple input event detection and processing unit. The XMC4500 provides two units - ERU0 and ERU1.

    Each ERU unit consists of the following blocks:
    • An Event Request Select (ERS) unit.
    – Event Input Selectors allow the selection of one out of two inputs. For each of these two inputs, an vector of 4 possible signals is available.
    – Event Combinations allow a logical combination of two input signals to a common trigger.

    • An Event Trigger Logic (ETL) per Input Channel allows the definition of the transition (edge selection, or by software) that lead to a trigger event and can also store this status. Here, the input levels of the selected signals are translated into events.

    • The Trigger Cross Connect Matrix distributes the events and status flags to the Output Channels. Additionally, trigger signals from other modules are made available and can be combined with the local triggers.

    • An Output Gating Unit (OGU) combines the trigger events and status information and gates the Output depending on a gating signal.

    Click image for larger version

Name:	ERU.jpg
Views:	3
Size:	100.8 KB
ID:	1059
    Last edited by Travis; Oct 27th, 2014 at 12:00 AM.

  2. #2
    Travis will become famous soon enough
    Join Date
    Feb 2013
    Location
    Singapore
    Posts
    749
    Points
    4580
    Here is an example for ERU on XMC4500 Relax kit.

    https://www.infineonforums.com/thread...4500-Relax-kit

  3. #3
    AElGarem
    Guest
    I have a problem..I have set up three buttons on three pins to trigger interrupts using the ERU (Button pad signal connects to eru001 signal A input, eru001 connected to eru002 and eru002 connected to nvic002) but unfortunately only one of them works. Can you help?
    Thanks

  4. #4
    Travis will become famous soon enough
    Join Date
    Feb 2013
    Location
    Singapore
    Posts
    749
    Points
    4580
    Hi, Not all the buttons are connected to the ERU, please kindly check the related pins which are connected to the ERU.

  5. #5
    New Member New Member Huber is on a distinguished road
    Join Date
    Feb 2020
    Posts
    1
    Points
    40
    Hello,
    I am new to Microcontrollers and XMC / DAVE. I have a XMC1300 Boot Kit and I am trying to use the Event Detector and Event Generator apps to enable a LED when holding a Button.
    There is a number of ways to do this in software or with interrupts but I am doing a series of examples to get to know the XMC and would like to do this without interrupts.
    This is my configuration:
    Click image for larger version

Name:	Button_LED_Test.JPG
Views:	1
Size:	104.9 KB
ID:	4453
    The Button is connected to port 2.6 and I am using the onboard LED at port 0.0.
    When I debug this setup, the LED turns on immediately after startup and is always on. The button seems to do nothing.
    What am I doing wrong here?

  6. #6

    Infineon Employee
    Infineon Employee
    jferreira will become famous soon enough
    Join Date
    Oct 2012
    Posts
    689
    Hi,

    You need to enable the edge detector, i.e. on rising edge, and status flag autoclear.

    Regards,
    Jesus
    The views expressed here are my personal opinions, have not been reviewed or authorized by Infineon and do not necessarily represent the views of Infineon.

+ Reply to Thread

Tags for this Thread

Disclaimer

All content and materials on this site are provided “as is“. Infineon makes no warranties or representations with regard to this content and these materials of any kind, whether express or implied, including without limitation, warranties or representations of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, whether express or implied, is granted by Infineon. Use of the information on this site may require a license from a third party, or a license from Infineon.


Infineon accepts no liability for the content and materials on this site being accurate, complete or up- to-date or for the contents of external links. Infineon distances itself expressly from the contents of the linked pages, over the structure of which Infineon has no control.


Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Usage Terms of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Usage Terms of this site. Infineon reserves the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.