SX28AC-I/SO Parallax Inc, SX28AC-I/SO Datasheet - Page 22

• Manufacturer Part Number: SX28AC-I/SO
• Description: IC MCU 2K FLASH 50MHZ SO-28
• Manufacturer: Parallax Inc
• Series: SXr

Specifications of SX28AC-I/SO

• Core Processor: RISC
• Core Size: 8-Bit
• Speed: 75MHz
• Peripherals: Brown-out Detect/Reset, POR, WDT
• Number Of I /o: 20
• Program Memory Size: 3KB (2K x 12)
• Program Memory Type: FLASH
• Ram Size: 136 x 8
• Voltage - Supply (vcc/vdd): 3 V ~ 5.5 V
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 28-SOIC
• Eeprom Size: -
• Data Converters: -
• Connectivity: -
• Lead Free Status / Rohs Status: No

Parallax SX20AC/SX28AC
All interrupts are global in nature; that is, no interrupt has
priority over another. Interrupts are handled sequentially.
Figure 8-2 shows the interrupt processing sequence. Once
an interrupt is acknowledged, all subsequent global
interrupts are disabled until return from servicing the
current interrupt. The PC is pushed onto the single level
interrupt stack, and the contents of the FSR, STATUS,
and W registers are saved in their corresponding shadow
registers. The status bits PA0, PA1, and PA2 bits are
cleared after the STATUS register has been saved in its
shadow register. The interrupt logic has its own
singlelevel stack and is not part of the CALL subroutine
stack. The vector for the interrupt service routine is
address 0.
Once in the interrupt service routine, the user program
must check all external interrupt pending bits (contained
in the WKPND_B register) to determine the source of the
interrupt. The interrupt service routine should clear the
corresponding interrupt pending bit. If both internal and
external interrupts are enabled, the user program may also
need to read the contents of RTCC to determine any
recent RTCC rollover. This is needed since there is no
interrupt pending bit associated with the RTCC rollover.
Normally it is a requirement for the user program to
process every interrupt without missing any. To ensure
this, the longest path through the interrupt routine must
take less time than the shortest possible delay between
interrupts.
Note: the interrupt logic has its own single-level stack and is not part of the CALL subroutine stack.
© Parallax Inc.
Figure 8-2: Interrupt Processing
Page 22 of 51
If an external interrupt occurs during the interrupt routine,
the pending register will be updated but the trigger will be
ignored unless interrupts are disabled at the beginning of
the interrupt routine and enabled again at the end. This
also requires that the new interrupt does not occur before
interrupts are disabled in the interrupt routine. If there is a
possibility of additional interrupts occurring before they
can be disabled, the device will miss those interrupt
triggers. In other words, using more than one interrupt,
such as multiple external interrupts or both RTCC and
external interrupts, can result in missed or, at best, jittery
interrupt handling should one occur during the processing
of another. When handling external interrupts, the
interrupt routine should clear at least one pending register
bit. The bit that is cleared should represent the interrupt
being handled in order for the next interrupt to trigger.
Upon return from the interrupt service routine, the
contents of PC, FSR, STATUS, and W registers are
restored from their corresponding shadow registers. The
interrupt service routine should end with instructions such
as RETI and RETIW. RETI pops the interrupt stack and
the special shadow registers used for storing W,
STATUS, and FSR (preserved during interrupt handling).
RETIW behaves like RETI but also adds W to RTCC.
The interrupt return instruction enables the global
interrupts.
Rev 1.6 11/20/2006
www.parallax.com