DOCSLIB.ORG

A Native Transterpreter for the LEGO Mindstorms RCX CO620 Final Year Research Project

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Native Transterpreter for the LEGO Mindstorms RCX CO620 Final Year Research Project A Native Transterpreter for the LEGO MindStorms RCX CO620 Final Year Research Project Jon Simpson Computing Laboratory, University of Kent [email protected] The Big Three • Who? • Jon Simpson (undergraduate) • What? • A small and maximally concurrent occam-π operating environment for the LEGO MindStorms RCX robotics platform. • Why? • Interested in the use of concurrency for robotics. • Previously explored methodologies for designing concurrent robotics programs with occam-π on a large mobile robot platform. • J. Simpson, C. L. Jacobsen, and M. C. Jadud. Mobile Robot Control: #e Subsumption Architecture and occam-pi. In F. R. M. Barnes, J. M. Kerridge, and P. H. Welch, editors, Communicating Process Architectures 2006, pages 225–236. IOS Press, September 2006. • To gain experience with low-level hardware programming and C. • Get more involved with the Transterpreter project. 2 LEGO MindStorms RCX • 16 MHz, 16-bit Hitachi H8/300 CPU • 16kB of ROM • 32kB of RAM • RCX ‘executive’ loads into RAM from ROM at power on. • Once uploaded, programs and executive share space in RAM. • 3 input ports with A/D conversion • 3 output ports • Speaker • Timers • Infra-red port (used for program upload) 3 The Transterpreter (TVM) • A portable interpreter for the extended Transputer instruction set (occam-π) written in ANSI C. [1] • Support for: • Mac OS X (PowerPC, Intel) • Linux (x86, MIPS) • Windows (x86) • LEGO MindStorms (H8/300) • Existing support removed in late 2004, due to growing problems with memory space on the LEGO & keeping feature parity with the main version of the interpreter for all other platforms. • A renewed LEGO port of the TVM that solves these problems would facilitate continued concurrent robotics explorations with occam-π. 4 Space, the final frontier ROM 2k (RCX executive) ROM (16k) RAM (32k) 5 Space, the final frontier ROM ROM 2k use (RCX executive) (4k) ROM (16k) RAM (32k) 6 Space, the final frontier ROM ROM BrickOS 2k use (RCX executive) (12k) (4k) ROM (16k) RAM (32k) 7 Space, the final frontier ROM ROM BrickOS TVM 2k use (RCX executive) (12k) (4k) (8k) ROM (16k) RAM (32k) 8 Space, the final frontier ROM ROM BrickOS TVM Byte 2k use code (RCX executive) (12k) (4k) (8k) (3k) ROM (16k) RAM (32k) 9 Space, the final frontier ROM ROM BrickOS TVM Byte Free 2k use code (RCX executive) (12k) (4k) (8k) (3k) (3k) ROM (16k) RAM (32k) 10 The Problems of Space • #e small amount of available memory restricts the kinds of programs that can be written. • #e original port of the TVM supported occam 2.1, but the dynamism of occam-π [3] is desired. • #e dynamism introduced into occam-π is of limited use given so little free memory. • Free memory is reduced yet further by adding and including support for these extended π features of the language. 11 VM Growth • #e TVM is cross-platform and has many di$erent target applications (from embedded platforms, all the way up to MPI clustering) • As functionality has been added to cater for these applications, and been integrated into the main line of development, the interpreter size has increased. • Having to maintain a separate, limited branch of the VM for the LEGO would not be ideal. • Some of these new features are useful for robotics (e.g. BARRIERs) • From previous experience, space for future growth is important! • If we update the size of the virtual machine on the memory diagram to be current.. 12 VM Growth • TVM (late 2004) ROM BrickOS TVM Byte Free 2k use code (12k) (4k) (8k) (3k) (3k) RAM (32k) 13 VM Growth • TVM (late 2004) ROM BrickOS TVM Byte Free 2k use code (12k) (4k) (8k) (3k) (3k) RAM (32k) • TVM (February 2007) ROM BrickOS TVM Byte 2k use code (12k) (4k) (11k) (3k) RAM (32k) 14 Something’s got to go... • #ere’s absolutely no free space for this stack of so%ware to run. • Can’t do anything about the reserved and ROM function memory. • Need the TVM and bytecode. • BrickOS can go! • But it’s being used to interface with the hardware from the TVM. • We’ll need to create a new set of ‘OS’ services for the TVM to use when interacting with the hardware. 15 A Solution Appears ROM ROM Byte Free TVM code (RCX executive) 2k use (4k) (11k) (3k) (12k) Total ROM (16k) Total RAM (32k) • #e RCX executive in ROM contains &rmware functions for interacting with the hardware at a basic level, and they are available to us already. • #e functions in ROM are wrapped in a C library (librcx[2]), which can be used in the C code of the TVM. • Can access the C functions from occam-π through use of the Foreign Function Interface [4]. • #e RCX’s hardware is memory mapped, so we can PLACE variables at those addresses in occam code to manipulate it directly. 16 On Endianness • #e virtual machine is little-endian, but the RCX is a big-endian architecture. • Calls to C functions require their parameters to be byte-swapped in and out, if the values are to be read and written correctly on both ends. • #e values of memory addresses read or written directly from occam (via PLACEd variables) will need to be swapped. • #ere are some complications with arithmetic shi%s and possibly other operations. 17 New Requirements • BrickOS will no longer bring up and initialise the hardware, the TVM must now do it. • Including memory, the timers and any interrupts. • #e ROM &rmware functions provide much lower level functionality than BrickOS previously did to the TVM. • Interfaces to the Sensors, Motors, LCD, Buttons, Sound and Power status are required, for programming the RCX. • #e RCX Executive loads at power on, and will accept an initial &rmware image (the TVM, in this case) over IR. • Transputer bytecode can be compiled directly into the VM, and uploaded with the initial &rmware image. • Subsequent code uploading will have to be done in the TVM, as BrickOS no longer provides this functionality. 18 Maximally Concurrent • Using the FFI and PLACEd variables, we can write almost all of the the now missing functionality in occam, running inside the TVM. • A minimal initialisation in C brings up the VM, then the processes containing the operating environment are loaded & run. • Bene"ts • Uni&ed scheduler (as much processing inside the VM as possible). • Safe concurrency down to the hardware level, for writing these system level processes. • Makes it more straightforward to expose natural process and/ or channel interfaces for the hardware to the programmer. 19 The debug.man 20 Ground Up Concurrency: Advantage • Whilst writing small test programs, it was hard to see when the VM was running, or if it had crashed or deadlocked. • Ideally it would be good to signal to the user that the program is running. • #e RCX has a &gure on the display in the shape of a person, which can be either walking or standing. • Initially, a small test process (debug.man) which used this &gure had been written when debugging the timer. • Running this process in parallel with any other code that is running gives us an instant indicator that the VM is running, and scheduling processes correctly. • Doing this with C threads would have been prohibitively complex for this purpose. 21 Parallelism as a Debug Aid ... -- Display a running man with the segments of the display PROC debug.man () TIMER tim: INT t: SEQ tim ? t WHILE TRUE SEQ lcd.set.segment (LCD.STANDING) tim ? AFTER t PLUS (500 * MILLIS) tim ? t lcd.set.segment (LCD.WALKING) tim ? AFTER t PLUS (500 * MILLIS) tim ? t : -- Main PROC, must have the three top level channels PROC my.test.program (CHAN BYTE kyb?, scr!, err!) PAR debug.man() foo() -- Could be any number of processes being tested. : 22 Difficulties • Working through issues of endianness between the virtual machine and the hardware. • Blind debugging, no printf, just a 4 digit LCD display. • #ere are also many ways the RCX can crash that will leave no way to put debug output to the screen. 23 The High-level View FFI Here be occam-π dragons C 24 Endianness (C FFI) void ffi_function (int *w) { int value.location; value.location = SwapTwoBytes(w[0]); /* do something to value.location */ *(int *)SwapTwoBytes(w[3]) = SwapTwoBytes (value.location); } Getting this swapping right is HARD for complex functions, which may have any combination of arrays, VAL TYPE or TYPE parameters 25 Problems • If address values are swapped (or not) incorrectly, the resulting memory accesses will very likely cause crashes (hard to debug!). • Variables that go through the FFI to C and back multiple times (say, in a loop) must be properly returned to the occam environment each time. • Some values go into the FFI and are not returned, so they do not have to be swapped back. • #e solution to these problems would be a big endian interpreter for this platform, avoiding swapping. • One exists, but there are problems with the big endian bytecode generation. 26 Results • A working virtual machine port that runs without ROM ROM Byte Free any underlying support OSTVM, and prcodeovides a large (RCX executive) 2k use amount of free spac(4k)e for pr(1o1k)grams.(3k) (12k) Total ROM (16k) Total RAM (32k) • High-level occam processes for interfacing to all of the major hardware functionality (Sensors, Motors, LCD, Buttons, Sound) 27 Future Work (>1 Month) • Bytecode uploading to the running VM and execution along with operating system processes in a single virtual machine instance. • Design of the embedded OS network, and its process API for programmers. • Sample robot programs, OS and API documentation. prefix delta to.lcd lcd.out.int (n) upload.handler succ numbers TVM 28 Future Work • Introduction of subsumption architecture primitives.
Load more

Recommended publications
  • Life of Occam-Pi
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Kent Academic Repository Communicating Process Architectures 2013 293 P.H. Welch et al. (Eds.) Open Channel Publishing Ltd., 2013 © 2013 The authors and Open Channel Publishing Ltd. All rights reserved. Life of occam-Pi Peter H. WELCH School of Computing, University of Kent, UK [email protected] Abstract. This paper considers some questions prompted by a brief review of the history of computing. Why is programming so hard? Why is concurrency considered an “advanced” subject? What’s the matter with Objects? Where did all the Maths go? In searching for answers, the paper looks at some concerns over fundamental ideas within object orientation (as represented by modern programming languages), before focussing on the concurrency model of communicating processes and its particular expression in the occam family of languages. In that focus, it looks at the history of occam, its underlying philosophy (Ockham’s Razor), its semantic foundation on Hoare’s CSP, its principles of process oriented design and its development over almost three decades into occam-π (which blends in the concurrency dynamics of Milner’s π-calculus). Also presented will be an urgent need for rationalisation – occam-π is an experiment that has demonstrated significant results, but now needs time to be spent on careful review and implementing the conclusions of that review. Finally, the future is considered. In particular, is there a future? Keywords. process, object, local reasoning, global reasoning, occam-pi, concurrency, compositionality, verification, multicore, efficiency, scalability, safety, simplicity Introduction Let’s try a few questions to which the answer might be: “occam, obviously”.
    [Show full text]
  • Rmox: a Raw-Metal Occam Experiment
    Communicating Process Architectures – 2003 269 Jan F. Broenink and Gerald H. Hilderink (Eds.) IOS Press, 2003 RMoX: A Raw-Metal occam Experiment Fred BARNES†, Christian JACOBSEN† and Brian VINTER‡ † Computing Laboratory, University of Kent, Canterbury, Kent, CT2 7NF, England. {frmb2,clj3}@kent.ac.uk ‡ Department of Mathematics and Computer Science, University of Southern Denmark, Odense, Denmark. [email protected] Abstract. Operating-systems are the core software component of many modern com- puter systems, ranging from small specialised embedded systems through to large distributed operating-systems. This paper presents RMoX: a highly concurrent CSP- based operating-system written in occam. The motivation for this stems from the overwhelming need for reliable, secure and scalable operating-systems. The major- ity of operating-systems are written in C, a language that easily offers the level of flexibility required (for example, interfacing with assembly routines). C compilers, however, provide little or no mechanism to guard against race-hazard and aliasing er- rors, that can lead to catastrophic run-time failure (as well as to more subtle errors, such as security loop-holes). The RMoX operating-system presents a novel approach to operating-system design (although this is not the first CSP-based operating-system). Concurrency is utilised at all levels, resulting in a system design that is well defined, easily understood and scalable. The implementation, using the KRoC extended oc- cam, provides guarantees of freedom from race-hazard and aliasing errors, and makes extensive use of the recently added support for dynamic process creation and channel mobility. Whilst targeted at mainstream computing, the ideas and methods presented are equally applicable for small-scale embedded systems — where advantage can be made of the lightweight nature of RMoX (providing fast interrupt responses, for ex- ample).
    [Show full text]
  • Chapters 1-10 As a Single File (Pdf)
    Boldrin & Levine: Against Intellectual Monopoly, Chapter 1 Chapter 1: Introduction In late 1764, while repairing a small Newcomen steam engine, the idea of allowing steam to expand and condense in separate containers sprang into the mind of James Watt. He spent the next few months in unceasing labor building a model of the new engine. In 1768, after a series of improvements and substantial borrowing, he applied for a patent on the idea. August found Watt in London about the patent and he spent another six months working hard to obtain it. The patent was finally awarded in January of the following year. Nothing much happened by way of production until 1775. Then, with a major effort supported by his business partner, the rich industrialist Matthew Boulton, Watt secured an Act of Parliament extending his patent until the year 1800. The great statesman Edmund Burke spoke eloquently in Parliament in the name of economic freedom and against the creation of unnecessary monopoly – but to no avail. The connections of Watt’s partner Boulton were too solid to be defeated by simple principle. Once Watt’s patents were secured and production started, a substantial portion of his energy was devoted to fending off rival inventors. In 1782, Watt secured an additional patent, made “necessary in consequence of ... having been so unfairly anticipated, by [Matthew] Wasborough in the crank motion.” More dramatically, in the 1790s, when the superior Hornblower engine was put into production, Boulton and Watt went after him with the full force of the legal system. During the period of Watt’s patents the U.K.
    [Show full text]
  • Modelling with Cellular Automata: Problem Solving Environments and Multidimensional Applications
    UvA-DARE (Digital Academic Repository) Modelling with cellular automata: problem solving environments and multidimensional applications Naumov, L.A. Publication date 2011 Document Version Final published version Link to publication Citation for published version (APA): Naumov, L. A. (2011). Modelling with cellular automata: problem solving environments and multidimensional applications. General rights It is not permitted to download or to forward/distribute the text or part of it without the consent of the author(s) and/or copyright holder(s), other than for strictly personal, individual use, unless the work is under an open content license (like Creative Commons). Disclaimer/Complaints regulations If you believe that digital publication of certain material infringes any of your rights or (privacy) interests, please let the Library know, stating your reasons. In case of a legitimate complaint, the Library will make the material inaccessible and/or remove it from the website. Please Ask the Library: https://uba.uva.nl/en/contact, or a letter to: Library of the University of Amsterdam, Secretariat, Singel 425, 1012 WP Amsterdam, The Netherlands. You will be contacted as soon as possible. UvA-DARE is a service provided by the library of the University of Amsterdam (https://dare.uva.nl) Download date:05 Oct 2021 Modelling with Cellular Automata: Problem Solving Environments and Multidimensional Applications ACADEMISCH PROEFSCHRIFT ter verkrijging van de graad van doctor aan de Universiteit van Amsterdam op gezag van de Rector Magnificus prof. dr. D.C. van den Boom ten overstaan van een door het college voor promoties ingestelde commissie, in het openbaar te verdedigen in de Agnietenkapel op dinsdag 14 juni 2011, te 10:00 uur door Lev Alexandrovich Naumov geboren te Sint-Petersburg, Rusland Promotiecommissie Promotor: Prof.
    [Show full text]
  • Implementation of Kroc on Analog Devices' "SHARC"
    Proceedings of the 19 WoTUG Technical Meeting, 31 March- 3 April 1996, Nottingham, UK 179 Implementation of KRoC on Analog Devices’ "SHARC" DSP G.W. Otten, M.H. Schwirtz, R. Bruis, J.F Broenink and A.W.P. Bakkers Mechatronic Research Centre Twente and Control Laboratory, Department of Electrical Engineering, University of Twente, PO Box 217, 7500 AE Enschede, The Netherlands. Email: [email protected] Abstract: This paper summarises the experiences gained at the Control Laboratory of the University of Twente in porting the Kent Retargetable occam Compiler - KroC - to the Analog Devices’ ADSP21060 SHARC Digital Signal Processor. The choice of porting the KRoC to the DSP processor was in our view both a challenge and an absolute necessity because DSP processors are an important ingredient in modern day control systems. Currently, our implementation contains the most important occam primitives such as channel communication, PAR, ALT, and most of the integer arithmatic. Furthermore, a basic kernel was realised, providing channel- communication based scheduling only. This porting process, using quite straight- forward modifications of the SPARC KRoC-translator, was done within six weeks. A representative benchmark was constructed, showing that the 33Mhz SHARC-KRoC implementation is 40% faster than the the 25Mhz T800 using the INMOS D7205 Toolset. 1. Introduction Prospective control system design will inevitably be influenced by present day micro-processor developments. These developments are in brief: availability of (Digital Signal) Processors with built-in memory and equipped with external communication channels and a general trend in the development of micro processors with combined DRAM+CPU together with on-chip integrated fibre optic link drivers.
    [Show full text]
  • Rmox: a Raw-Metal Occam Experiment
    Communicating Process Architectures – 2003 269 Jan F. Broenink (Eds.) IOS Press, 2003 RMoX: A Raw-Metal occam Experiment Fred BARNES†, Christian JACOBSEN† and Brian VINTER‡ † Computing Laboratory, University of Kent, Canterbury, Kent, CT2 7NF, England. {frmb2,clj3}@kent.ac.uk ‡ Department of Mathematics and Computer Science, University of Southern Denmark, Odense, Denmark. [email protected] Abstract. Operating-systems are the core software component of many modern com- puter systems, ranging from small specialised embedded systems through to large distributed operating-systems. This paper presents RMoX: a highly concurrent CSP- based operating-system written in occam. The motivation for this stems from the overwhelming need for reliable, secure and scalable operating-systems. The major- ity of operating-systems are written in C, a language that easily offers the level of flexibility required (for example, interfacing with assembly routines). C compilers, however, provide little or no mechanism to guard against race-hazard and aliasing er- rors, that can lead to catastrophic run-time failure (as well as to more subtle errors, such as security loop-holes). The RMoX operating-system presents a novel approach to operating-system design (although this is not the first CSP-based operating-system). Concurrency is utilised at all levels, resulting in a system design that is well defined, easily understood and scalable. The implementation, using the KRoC extended oc- cam, provides guarantees of freedom from race-hazard and aliasing errors, and makes extensive use of the recently added support for dynamic process creation and channel mobility. Whilst targeted at mainstream computing, the ideas and methods presented are equally applicable for small-scale embedded systems — where advantage can be made of the lightweight nature of RMoX (providing fast interrupt responses, for ex- ample).
    [Show full text]
  • Synchronous Distributed Behaviours Using Occam
    Chapter 3 Synchronous distributed behaviours using Occam At this point, the installation of kroc, the Kent Research Occam Compiler should be con- sidered. The first section will detail how to proceed on a Linux installation. 3.1 Installing kroc The Occam compiler is developed at University of Kent, with its home page at http://projects.cs.kent.ac.uk/projects/kroc/trac/.. Two branches are proposed: out of the same compiler frontend: kroc i386 compiler which makes use of a code generator for x86, thus enabling • execution of programs on current multi-cores, Transterpreter Virtual Machine (TVM), which enables execution on micro-controllers. • The two branches are good targets for wireless sensor designs. The first is used to support concurrent simulation of networks, the second will support execution at sensor level in a portable way. In this chapter, the i386 execution of simulations is the main concern, and our guide is the web page provided by Kent (it would be sufficient to follow these steps). This section is just a check out of instructions provided at this location. 1. access installation page from /sl Information for users 2. check your system uname -a Linux MyLinuxBox 3.2.0-51-generic #77-Ubuntu SMP Wed Jul 24 20:18:19 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux I have a 64bits installation supporting concurrent execution. lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch Distributor ID: Ubuntu Description: Ubuntu 12.04.2 LTS Release: 12.04 Codename: precise This is Precise 12.04 LTS distribution of Ubuntu.
    [Show full text]
  • A Cell Transterpreter
    CORE Metadata, citation and similar papers at core.ac.uk Provided by Kent Academic Repository Communicating Process Architectures 2006 215 Peter Welch, Jon Kerridge, and Fred Barnes (Eds.) IOS Press, 2006 A Cell Transterpreter Damian J. DIMMICH, Christian L. JACOBSEN, Matthew C. JADUD Computing Laboratory, University of Kent, Canterbury, CT2 7NF, UK. {djd20 , clj3 , mcj4} @kent.ac.uk Abstract. The Cell Broadband Engine is a hybrid processor which consists of a Pow- erPC core and eight vector co-processors on a single die. Its unique design poses a number of language design and implementation challenges. To begin exploring these challenges, we have ported the Transterpreter to the Cell Broadband Engine. The Transterpreter is a small, portable runtime for concurrent languages and can be used as a platform for experimenting with language concepts. This paper describes a pre- liminary attempt at porting the Transterpreter runtime to the Cell Broadband Engine and explores ways to program it using a concurrent language. Keywords. CELL processor, Transterpreter, Portable run-time environments Introduction Multi-core processors are becoming commonplace in desktop computers, laptops and games consoles [Rat05,BDK+05,KAO05]. Traditionally programming such concurrent systems has been considered difficult [Lee06,Boe05]. We believe that creating and designing software that makes use of concurrency provided by hardware can be easy, given a language and runtime that provide support for concurrency. With a compiler that can check for certain errors in concurrent code, and a runtime that gracefully reports error conditions surrounding program deadlock, developing such software can become simpler. The Sony PlayStation III [Son06], a consumer games console which will be released at the end of 2006, is an example of a readily available and affordable multi-core system.
    [Show full text]
  • Native Code Generation Using the Transterpreter
    Communicating Process Architectures 2006 269 Peter Welch, Jon Kerridge, and Fred Barnes (Eds.) IOS Press, 2006 Native Code Generation Using the Transterpreter Christian L. JACOBSEN, Damian J. DIMMICH and Matthew C. JADUD Computing Laboratory, University of Kent, Canterbury, Kent, CT2 7NZ, England. {clj3 , djd20 , mcj4} @kent.ac.uk Abstract. We are interested in languages that provide powerful abstractions for con- currency and parallelism that execute everywhere, efficiently. Currently, the existing runtime environments for the occam-π programming language provide either one of these features (portability) or some semblance of the other (performance). We believe that both can be achieved through the careful generation of C from occam-π, and demonstrate that this is possible using the Transterpreter, a portable interpreter for occam-π, as our starting point. Keywords. Transterpreter, native code, GCC, occam-π Introduction The Transterpreter [1] is a virtual machine for CSP [2] and Pi-calculus [3] based languages. Intended as a platform for concurrent language design and research, it also fully supports the execution of programs written in the occam-π [4] language. To support our research goals, the Transterpreter was designed to be extensible and portable. This does mean that it is unlikely to be able to achieve the level of performance that could be obtained by compiling directly to native code. However, what the Transterpreter lacks in performance, it possesses in portability, and has enabled the execution of occam-π on platforms as diverse as the Mac OS X (PowerPC) and the LEGO Mindstorms (H8/300) [5]. Porting the Transterpreter to a POSIX compliant OS, such as Mac OS X, is no harder than recompiling 4000 lines of ANSI C.
    [Show full text]
  • Rmox – a Raw Metal Occam Experiment 1/30
    RMoX { A Raw Metal occam Experiment 1/30 RMoX: A Raw Metal occam Experiment Fred Barnes† ([email protected]) Christian Jacobsen† ([email protected]) Brian Vinter‡ ([email protected]) † Computing Laboratory, University of Kent ‡ Department of Maths and Computer Science, University of Southern Denmark RMoX { A Raw Metal occam Experiment 2/30 Contents • Introduction • Dynamic occam • Design: { the `kernel' { device drivers { ¯lesystems { networking { top-level and console • Implementation: { accessing hardware { real and user-mode RMoX • Conclusions RMoX { A Raw Metal occam Experiment 3/30 Motivation • Do we really need another OS ? • Most existing operating systems su®er: { from software error { from high overheads { a lack of scalability • We want an operating system that: { has a rigorous design { is free from software error { is fast! RMoX { A Raw Metal occam Experiment 4/30 Introduction • Raw Metal occam: { runs on the \raw" hardware { with some help from the UTAH Flux OSKit { and a modi¯ed KRoC run-time system • CSP design • Dynamic occam implementation RMoX { A Raw Metal occam Experiment 5/30 Dynamic occam RMoX extensively uses two of the new dynamic features of KRoC/occam: • mobile channel-bundle ends • dynamic process creation (fork) These support: • dynamic network expansion and re-con¯guration • scalable server farms RMoX { A Raw Metal occam Experiment 6/30 Mobile Data • Provides a movement semantics for assign- ment and communication • Implementation supports both static and dynamic mobiles • Unit-time assignment and communication
    [Show full text]
  • Download Programs to the LEGO As Well As Enable Line-Of-Sight Communi- Cation Between Robots
    Kent Academic Repository Full text document (pdf) Citation for published version Jacobsen, Christian L. and Jadud, Matthew C. (2004) The Transterpreter: A Transputer Interpreter. In: East, Ian R. and Duce, David and Green, Mark and Martin, Jeremy and Welch, Peter H., eds. Communicating Process Architectures 2004. Concurrent Systems Engineering Series, 62. IOS Press, Amsterdam pp. 99-106. ISBN 1-58603-458-8. DOI Link to record in KAR https://kar.kent.ac.uk/14104/ Document Version UNSPECIFIED Copyright & reuse Content in the Kent Academic Repository is made available for research purposes. Unless otherwise stated all content is protected by copyright and in the absence of an open licence (eg Creative Commons), permissions for further reuse of content should be sought from the publisher, author or other copyright holder. Versions of research The version in the Kent Academic Repository may differ from the final published version. Users are advised to check http://kar.kent.ac.uk for the status of the paper. Users should always cite the published version of record. Enquiries For any further enquiries regarding the licence status of this document, please contact: [email protected] If you believe this document infringes copyright then please contact the KAR admin team with the take-down information provided at http://kar.kent.ac.uk/contact.html Communicating Process Architectures 2004 99 Ian East, Jeremy Martin, Peter Welch, David Duce, and Mark Green (Eds.) IOS Press, 2004 The Transterpreter: A Transputer Interpreter Christian L. JACOBSEN [email protected] Matthew C. JADUD [email protected] Computing Laboratory, University of Kent, Canterbury, CT2 7NF, UK Abstract.
    [Show full text]
  • Document Version Publisher Pdf
    Kent Academic Repository Full text document (pdf) Citation for published version Brown, Neil C.C. and Welch, Peter H. (2003) An Introduction to the Kent C++CSP Library. In: Communicating Process Architectures 2003, SEP 07-10, 2003, UNIV Twente, Enschde, Nederlands. DOI Link to record in KAR http://kar.kent.ac.uk/13921/ Document Version Publisher pdf Copyright & reuse Content in the Kent Academic Repository is made available for research purposes. Unless otherwise stated all content is protected by copyright and in the absence of an open licence (eg Creative Commons), permissions for further reuse of content should be sought from the publisher, author or other copyright holder. Versions of research The version in the Kent Academic Repository may differ from the final published version. Users are advised to check http://kar.kent.ac.uk for the status of the paper. Users should always cite the published version of record. Enquiries For any further enquiries regarding the licence status of this document, please contact: [email protected] If you believe this document infringes copyright then please contact the KAR admin team with the take-down information provided at http://kar.kent.ac.uk/contact.html Communicating Process Architectures – 2003 139 Jan F. Broenink and Gerald H. Hilderink (Eds.) IOS Press, 2003 An Introduction to the Kent C++CSP Library Neil BROWN and Peter WELCH Computing Laboratory, University of Kent, Canterbury, Kent, CT2 7NF, England. [email protected], [email protected] Abstract. This paper reports on a CSP library for C++, developed over the past year at the University of Kent.
    [Show full text]