??? 01/31/06 16:17 Read: times |
#108820 - Design First Responding to: ???'s previous message |
Stanley Lio said:
When data lost occurs, the IRRC routine may keep waiting (due to some "JNB IR,$"). This is where you learn that you need a properly thought out design before you start debugging. In any time critical application, code like JNB IR,$ should not be used. It hogs the CPU and is bound to give you problems. You need to think carefully about the structure of your design and how it is going to ensure that each and every task gets CPU time when it needs it. Ian |
Topic | Author | Date |
Servomotor head version III | 01/01/70 00:00 | |
Nice Work | 01/01/70 00:00 | |
Manageing code and debugging | 01/01/70 00:00 | |
Divide into modules | 01/01/70 00:00 | |
multi tasking | 01/01/70 00:00 | |
IRRC routine are much longer | 01/01/70 00:00 | |
No waiting for IR | 01/01/70 00:00 | |
two mcu | 01/01/70 00:00 | |
Maybe this will help you | 01/01/70 00:00 | |
this is not IRQ save | 01/01/70 00:00 | |
RS232 | 01/01/70 00:00 | |
Design First | 01/01/70 00:00 | |
Design | 01/01/70 00:00 | |
Pardon![]() | 01/01/70 00:00 | |
Well done! | 01/01/70 00:00 | |
The "3.0" | 01/01/70 00:00 | |
Smart! | 01/01/70 00:00 | |
hardware | 01/01/70 00:00 | |
Mainland China | 01/01/70 00:00 | |
And Well done Kai! | 01/01/70 00:00 | |
My experinece | 01/01/70 00:00 | |
very impressive | 01/01/70 00:00 | |
Program and Code Structure | 01/01/70 00:00 | |
Spaghetti anyone ? | 01/01/70 00:00 | |
manually interpret machine code? | 01/01/70 00:00 | |
hand coded mechine language | 01/01/70 00:00 | |
Keep up the good work | 01/01/70 00:00 |