STI Friendly Clock Recovery Techniques for Bit Banged Communication Protocols

dc.contributor.advisorDr. Alexander Dean, Committee Chairen_US
dc.contributor.advisorDr. Frank Mueller, Committee Co-Chairen_US
dc.contributor.advisorDr. Vincent Freeh, Committee Memberen_US
dc.contributor.authorThirumoolan, Sudhagaren_US
dc.date.accessioned2010-04-02T18:07:57Z
dc.date.available2010-04-02T18:07:57Z
dc.date.issued2004-05-19en_US
dc.degree.disciplineComputer Scienceen_US
dc.degree.levelthesisen_US
dc.degree.nameMSen_US
dc.description.abstractNowadays embedded communication networks are used in a number of applications. A majority of these networks use a shared medium for communication. Controllers for these shared medium protocols can be implemented in hardware or software. Protocol implementations in software using standard off the shelf microcontrollers have been found to be faster, easier and most cost effective. In an embedded communication network, it is essential that the protocol controllers are in synchrony with each other. A slight phase difference between the clocks of the protocol controllers can lead to errors in the data propagated between them. If the sender has a slight error in its clock frequency the receivers that are reading a message from the sender need to adapt to the clock of the sender by recovering the clock information from the data on the shared medium. This paper talks about the various existing techniques in hardware and software and compares a few proposed clock recovery techniques which can be used for software protocol implementations using STI. A good clock recovery technique must adapt to the sender as quickly as possible and maintain very little phase difference with the sender. It must consume very few computational cycles and the code blocks must remain as close together as possible to avoid fragmenting the idle time of the protocol implementation. In order to facilitate STI, a good primary thread implementation will need to have large chunks of idle time which can be merged with useful code from a secondary thread. It is also required that the primary thread should have fixed or almost fixed execution times for all its functions, in order to be able to recover as much idle time as possible. The proposed techniques have large chunks of idle time as well as try to catch up with the sender's clock as quickly as possible. Hence they are good candidates for being used in software protocol implementations using STI. However, the limitation of these techniques is the fixed number of cycles up to which they can recover in every bit interval when the receiver's clock is slower than the sender's.en_US
dc.identifier.otheretd-05142004-234421en_US
dc.identifier.urihttp://www.lib.ncsu.edu/resolver/1840.16/1822
dc.rightsI hereby certify that, if appropriate, I have obtained and attached hereto a written permission statement from the owner(s) of each third party copyrighted matter to be included in my thesis, dissertation, or project report, allowing distribution as specified below. I certify that the version I submitted is the same as that approved by my advisory committee. I hereby grant to NC State University or its agents the non-exclusive license to archive and make accessible, under the conditions specified below, my thesis, dissertation, or project report in whole or in part in all forms of media, now or hereafter known. I retain all other ownership rights to the copyright of the thesis, dissertation or project report. I also retain the right to use in future works (such as articles or books) all or part of this thesis, dissertation, or project report.en_US
dc.subjectThrinten_US
dc.subjectSoftware Protocol Controllersen_US
dc.subjectSTIen_US
dc.subjectClock Recovery Techniquesen_US
dc.subjectOversamplingen_US
dc.subjectSoftware Thread Integrationen_US
dc.subjectBit Banged Communication Protocolsen_US
dc.titleSTI Friendly Clock Recovery Techniques for Bit Banged Communication Protocolsen_US

Files

Original bundle

Now showing 1 - 1 of 1
No Thumbnail Available
Name:
etd.pdf
Size:
427.25 KB
Format:
Adobe Portable Document Format

Collections