Beware that many things can seem "simple" (sic) only because you have failed to appreciate the complexities!


Do you mean that in works in the Keil Simulator; ie, running on a PC?

When something works in a simulator, but not in your real hardware, that means that your simulation fails to correctly model some aspect(s) of your real hardware.

By far the commonest such aspect is the timing constraints.

Other possibilities include:

* Faults in your real hardware;

* Design flaws and/or errors in your real hardware;

* False assumptions in interpreting the results of the simulation;

* Errors in the inputs provided to the simulation.


"Quick and dirty" often ends up as just plain dirty.

Time invested up-front in proper analysis & design is far more likely to yield a usable result in a quicker overall time.


So don't do it, then!


Unfortunately, the indentation seems to have gone completely haywire in your post!

This is probably because you have used TAB characters; the interpretation of TAB characters is totally non-portable.

Please re-post it, using only spaces - no TABs.