??? 07/23/04 12:28 Read: times |
#74747 - RE: LPC932 Interrupt Solution Responding to: ???'s previous message |
Juan,
It takes extreme skill to make code work where events in one interrupt depend on events in another. I try to avoid it as often as I can ("takes extreme skill" = likely bugs). One thing you can never expect to work is one thread waiting for another to do something. I have had a brief look at your code and suggest the following change: Interrupt a set a flag interrupt b set a flag Main does something based on the flags. That is a safe and sane way to accomplish thread interaction. Erik |
Topic | Author | Date |
LPC932 Interrupt Solution | 01/01/70 00:00 | |
RE: LPC932 Interrupt Solution | 01/01/70 00:00 | |
RE: LPC932 Interrupt Solution | 01/01/70 00:00 | |
RE: LPC932 Interrupt Solution | 01/01/70 00:00 | |
RE: LPC932 Interrupt Solution | 01/01/70 00:00 | |
RE: LPC932 Interrupt Solution | 01/01/70 00:00 | |
RE: LPC932 Interrupt Solution | 01/01/70 00:00 | |
RE: LPC932 Interrupt Solution | 01/01/70 00:00 | |
RE: LPC932 Interrupt Solution | 01/01/70 00:00 | |
RE: LPC932 Interrupt Solution | 01/01/70 00:00 | |
RE: LPC932 Interrupt Solution | 01/01/70 00:00 | |
RE: LPC932 Interrupt Solution | 01/01/70 00:00 | |
RE: LPC932 Interrupt Solution | 01/01/70 00:00 | |
RE: LPC932 Interrupt Solution![]() | 01/01/70 00:00 |