Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
06/13/03 01:51
Read: times


 
#48269 - RE: c=SBUF; what's going wrong?
Responding to: ???'s previous message
Strange!

I asked an associate who is familiar with C51 to cut&paste David's code. It behaved exactly as David described.

We added the statement to clear SM2, and things started working "normally" (c assumed hex value of keystrokes entered via serial window).

Now, repeating with original code, we can't duplicate original problem! c continues to assume value of keystrokes.

This has to be a debugger quirk!

-Ron




List of 11 messages in thread
TopicAuthorDate
c=SBUF; what's going wrong?            01/01/70 00:00      
   RE: c=SBUF; what\'s going wrong?            01/01/70 00:00      
      RE: c=SBUF; what\'s going wrong?            01/01/70 00:00      
   RE: c=SBUF; what\'s going wrong?            01/01/70 00:00      
   RE: c=SBUF; what's going wrong?            01/01/70 00:00      
      RE: c=SBUF; what's going wrong?            01/01/70 00:00      
   RE: c=SBUF; what's going wrong?            01/01/70 00:00      
      RE: c=SBUF; what's going wrong?            01/01/70 00:00      
   RE: c=SBUF; what's going wrong?            01/01/70 00:00      
      RE: c=SBUF; what's going wrong?            01/01/70 00:00      
      RE: c=SBUF; what's going wrong?            01/01/70 00:00      

Back to Subject List