View Single Post
  #6   Spotlight this post!  
Unread 11-22-2011, 02:25 PM
Ether's Avatar
Ether Ether is offline
systems engineer (retired)
no team
 
Join Date: Nov 2009
Rookie Year: 1969
Location: US
Posts: 8,003
Ether has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond repute
Re: [DFTH] We eat what we CAN, and what we can't, we CAN...

Quote:
Originally Posted by Hugh Meyer View Post
I hope this has been clear. If not I will gladly expand if you have specific questions.
I have a couple questions Hugh:

Quote:
We monitor the code run time by setting a digital output pin high at the start of our loop, setting it low at the end of the loop and a second pin is a toggle at the start of the loop. We monitor these signals with an oscilloscope to be sure the timing is what we expect.
The set hi/low is great way to observe the timing. What's the toggle for? To test for re-entrancy?


Quote:
The code does indeed block and waits for the communication to complete each cycle. This wastes most of the time just waiting. Based on our testing it always does this.
You said block waiting. Did you mean busy waiting?


Reply With Quote