🚀 go-pugleaf

	It's been awhile since I've dealt with the low level stuff on the ST,
but some general things:

	When enabling an interrupt, you almost always initialize the vector
before you enable the interrupt. So, in this case, you'd do:

{
	Mfpint(14,interrupt);
	Jenabint(14);
}

	Also, it makes life easier if you use the constants included in the
header files, e.g. "Mfpint(RING_INT,interrupt" (this is not a real constant,
just an example).

	One possible reason for the routine bombing: You say that in your
"other" routine (we'll call it "loop()"), you "...print stuff on screen in
endless loop...". You then also try to print from within your interrupt
routine. Perhaps there's a conflict? Even if there isn't, it'd probably be
cleaner to set a flag, and then have loop() check it. So, we have:

	int	rings;

loop()	/* Set the interrupt up & loop	*/
{
	rings = 0;		/* Initialize the ring count	*/
	Mfpint(14,interrupt);	/* Install my ring handler	*/
	Jenabint(14);		/* Enable interrupt		*/

	for (;;)		/* Loop forever			*/
	{
		if (!rings)	/* If no rings, say so...	*/
			printf("No rings...\n");
		else		/* Otherwise, show # of rings	*/
		{
			printf("There've been %d rings\n",rings);
			rings = 0;
		}
	}
}

interrupt()
{
	setrte();	/* MWC's function so we can rte instead of rts	*/
	rings++;	/* Increment the ring count			*/
}

	I didn't use Cconws because I didn't feel like dealing with printing
a decimal conversion... Also, note that this code chunk doesn't deal with what
would happen if there was a ring after the printf() in the else {}, but before
the "rings = 0" statement - it would lose a ring.

	I hope this helped...
 ------------------------------------------------------------------------------
		Jason Blochowiak (blochowi@garfield.cs.wisc.edu)
			"Not your average iconoclast..."
 ------------------------------------------------------------------------------