Re: Interrupts don't interrupt?!

Hi Leon

That is really nice! I stand corrected as I have been using the cpu32 system. I am glad to hear the world is improving.

Ken B

At 03:53 PM 4/18/2007, you wrote:
>No, the BDM on the ColdFire is non-intrusive. It does not HALT the CPU and only
>steals an occasional memory cycle to read and write RAM locations. The older
>BDMs (like the CPU32) would FREEZE or HALT the CPU whenever they were performing
>I/O. The new CF ones don't do that (much nicer :)
>
>--Leon
>
>
>> -----Original Message-----
>> From: swiftx-bounce_at_forth.com
>> [mailto:swiftx-bounce_at_forth.com] On Behalf Of Kenneth Butterfield
>> Sent: Wednesday, April 18, 2007 2:51 PM
>> To: swiftx_at_forth.com
>> Subject: [swiftx] Re: Interrupts don't interrupt?!
>>
>> Hi Gerry
>>
>> Your problem is not with the interrupts but with the BDM
>> port/XTL system in SWIFTX. This system over-rides the
>> interrupts. It totally controls the processor when it wants
>> to do i/o. The best thing you can do to test interrupt
>> operation is to download, remove the BDM, boot and run. This
>> means that you have to test your results through a serial
>> port or some other I/O. While on the BDM interrupts do occur,
>> but not in a timely fashion.
>>
>> Ken B
>>
>>
>> >I checked the mask registers, they read as zero - so why don't
>> >interrupts inter-rupt?! What am I doing wrong?
>> >
>> >Best regards,
>> >Gerry
>> >
>> >-------------------------------------------------------------
>> ---------
>> >swiftx_at_forth.com The SwiftX programming discussion
>> email list
>> >To unsubscribe, send subject "unsubscribe" to
>> swiftx-request_at_forth.com
>> >For list command help, send subject "help" to
>> swiftx-request_at_forth.com
>> >Message archives are located at http://www.forth.com/archive/swiftx
>> >-------------------------------------------------------------
>> ---------
>> >This list is a forum for SwiftX users. For product support and bug
>> >reports, please send email to support_at_forth.com
>> >-------------------------------------------------------------
>> ---------
>>
>>
>> ----------------------------------------------------------------------
>> swiftx_at_forth.com The SwiftX programming discussion email list
>> To unsubscribe, send subject "unsubscribe" to
>> swiftx-request_at_forth.com For list command help, send subject
>> "help" to swiftx-request_at_forth.com Message archives are
>> located at http://www.forth.com/archive/swiftx
>> ----------------------------------------------------------------------
>> This list is a forum for SwiftX users. For product support
>> and bug reports, please send email to support_at_forth.com
>> ----------------------------------------------------------------------
>>
>>
>
>----------------------------------------------------------------------
>swiftx_at_forth.com The SwiftX programming discussion email list
>To unsubscribe, send subject "unsubscribe" to swiftx-request_at_forth.com
>For list command help, send subject "help" to swiftx-request_at_forth.com
>Message archives are located at http://www.forth.com/archive/swiftx
>----------------------------------------------------------------------
>This list is a forum for SwiftX users. For product support and bug
>reports, please send email to support_at_forth.com
>----------------------------------------------------------------------

----------------------------------------------------------------------
swiftx_at_forth.com The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe" to swiftx-request_at_forth.com
For list command help, send subject "help" to swiftx-request_at_forth.com
Message archives are located at http://www.forth.com/archive/swiftx
----------------------------------------------------------------------
This list is a forum for SwiftX users. For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Fri Apr 20 2007 - 11:55:52 PDT