XMEGA interrupts

Go To Last Post
4 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Is the interrupt sequence described somewhere in the documentation?

I've tried to find it, but no luck.

What I'd like to know is how the device remembers its state before interrupt.

 

Most devices push return address and status register (with interrupt status), but what does XMEGA do?

 

Debugging is for sissies and delivery for surgeons. Real men do demonstration.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Please see "Interrupts and Programmable Multilevel Interrupt Controller" in the data sheet.

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks, but that still doesn't show how the status before interrupt (where to return to) is remembered.

 

I'm trying to figure out from someone else's code, why the interrupts stop taking place after some I2C communication.

I'm sorry, but I can't show the code in public.

What I recon is that after returning from an interrupt, the interrupts are left masked somehow.

 

The program uses library driver for TWI.

 

Debugging is for sissies and delivery for surgeons. Real men do demonstration.

Last Edited: Sat. Nov 10, 2018 - 10:01 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

A-ha, It doesn't remember anything but the return address. The rest needs to be done in SW.

 

https://electronics.stackexchange.com/questions/149578/how-does-the-call-stack-operated-during-an-interrupt-on-avr

Debugging is for sissies and delivery for surgeons. Real men do demonstration.