| ??? 01/25/07 14:03 Read: times |
#131467 - Maybe it is the part Responding to: ???'s previous message |
In our analysis of competing 8051s, we have seen a spurious external interrupt if interrupts are enabled early in the code execution. It seems to be a hardware bug, and one we have agonized over as to whether we should include in our clones.
It is NOT a case of a delayed one level on the pin. |
| Topic | Author | Date |
| External Interrupt triggering on initialization | 01/01/70 00:00 | |
| Simple! | 01/01/70 00:00 | |
| yes, but..... | 01/01/70 00:00 | |
| There's probably a good reason. | 01/01/70 00:00 | |
| worth a shot...but | 01/01/70 00:00 | |
| Understanding interrupts | 01/01/70 00:00 | |
| Yes, I Know | 01/01/70 00:00 | |
| terse response | 01/01/70 00:00 | |
| tried clr IE0... | 01/01/70 00:00 | |
| clr IE ?? | 01/01/70 00:00 | |
| I do not use the SILabs deviates, but | 01/01/70 00:00 | |
| Interesting.... | 01/01/70 00:00 | |
| AH, now we get a good guess at the reason. The ex | 01/01/70 00:00 | |
| Maybe it is the part | 01/01/70 00:00 | |
| are you sure | 01/01/70 00:00 | |
| hmmm..... | 01/01/70 00:00 | |
| Hardware bug | 01/01/70 00:00 | |
| down memory lane | 01/01/70 00:00 | |
INT0 is assigned to P0.1 as the default | 01/01/70 00:00 |