Paper Details

@InProceedings{VugtBakkers00,
  title = "{A} {C}ruise {C}ontrol in occam based on an {I}mplementation of {KR}o{C} on the {P}hilips 8051 {M}icrocontroller",
  author= "Vugt, Frank T. M. van and Bakkers, Andr\`{e} W. P.",
  editor= "Welch, Peter H. and Bakkers, Andr\`{e} W. P.",
  pages = "121--136",
  booktitle= "{C}ommunicating {P}rocess {A}rchitectures 2000",
  isbn= "1 58603 077 9",
  year= "2000",
  month= "sep",
  abstract= "This paper summarises the results of the realisation of a
     Cruise Control system in occam using an implementation of
     the Kent Retargettable occam Compiler (KRoC) on the Philips
     8051 microcontroller. The increase in complexity of systems
     designed comes with difficulties that can probably be
     overcome using concurrent programming languages. occam is
     such a language, originally developed for use with
     transputers. The KRoC initiative allows one to translate the
     transputer assembly produced from a program written in occam
     into the assembly of another processor. In this case, it was
     implemented for the Philips 8051 microcontroller, which is
     an 8-bits processor. The design and realisation in occam of
     the Cruise Control system of Yourdon demonstrate its proper
     functioning. The generated code is tested using a real-time
     in-circuit 8051 emulator and special hardware to represent
     car and interface. The design process using occam is
     compared to a regular solution using a language like C.
     Since this port is the first of its kind inasmuch as it is
     not targeting 'large' processors like the SPARC, important
     conclusions can be drawn regarding the power of the
     CSP-concept. The port is not complete yet, future work on it
     is recommended."
}

If you have any comments on this database, including inaccuracies, requests to remove or add information, or suggestions for improvement, the WoTUG web team are happy to hear of them. We will do our best to resolve problems to everyone's satisfaction.

Copyright for the papers presented in this database normally resides with the authors; please contact them directly for more information. Addresses are normally presented in the full paper.