2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler

Hi,

i use lpc2468 mcu for a simple TFT pattern generator project. i have 3 interrupt sources
1- Timer 0
2- Timer 1
3- i2s

when i use
IENABLE at the begining of the interrupt handler codes and
IDISABLE at the end of the interrupt handler codes
my software halts and does not work properly.

i saw these macros in almost all sample programs.
When i dont use these macros there is no problem.

i read AN10381 but i'm not sure i do the correct thing not using these macros.

My question: is that macros really essential for handling routines?

regards

Mehmet

------------------------------------

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )