| ??? 11/29/04 13:25 Read: times |
#82175 - OSC_FREQ Responding to: ???'s previous message |
I recommend that such routines be conditioned by a defined OSC_FREQ that, if changed, would make the routine disappear, thus creating an error andf alerting the developer to change the routine. Or do it directly - something like this: #if OSC_FREQ == 11059200L // Do the 11.059200MHz-dependent stuff #else #error Wrong Oscillator Frequency! #endifOf course, you could easily extend that to support a variety of frequencies For Keil uVision users, it would be nice if the XTAL value defined in the GUI were passed to the other tools... |
| Topic | Author | Date |
| Interrupt Function Prototype & Keil | 01/01/70 00:00 | |
| Re: Interrupt Function Prototype & Keil | 01/01/70 00:00 | |
| No Parameters | 01/01/70 00:00 | |
| ASM vs 'C' | 01/01/70 00:00 | |
| Interrupt Routines | 01/01/70 00:00 | |
| Assembly code no better than keil | 01/01/70 00:00 | |
| efficient C | 01/01/70 00:00 | |
| Hardware IIC | 01/01/70 00:00 | |
| I2C(C) = I2C(asm) | 01/01/70 00:00 | |
| C-asm delay | 01/01/70 00:00 | |
OSC_FREQ | 01/01/70 00:00 | |
| no need for prototypes! | 01/01/70 00:00 | |
| Same | 01/01/70 00:00 |