Paper Presentation & Seminar Topics: Beginning of Embedded Systems

Beginning of Embedded Systems

The need for embedded systems to collect and inform manufacturing accumulation on the corporate IT meshwork existed at metropolis Semiconductor long before the advent of the TINI chipset. The silicon process equipment utilised at metropolis often costs in excess of million per unit and must be utilised continuously -- and expeditiously -- to reassert the investment. Thus, metropolis required accurate, real-time reporting of its equipment position to refrain buying new equipment when a more economical ingest of existing equipment could be made. To this end, we matured an interface-device cipher titled the Natural Bridge, which prefabricated it doable to translate, or \"bridge,\" the control and position indicators of many pieces of semiconductor-fabrication equipment to the company-wide network.The Natural Bridge consisted of a diminutive journeying board with a microcontroller, lithium-backed nonvolatilisable memory, an Ethernet programme chip, an RS232C interface, and an programme to the metropolis Semiconductor 1-Wire network. We also matured a cooperative, multitasking operating grouping for the Natural Bridge. The Bridge Operating System (BOS), cursive in autochthonous code, provided entry points that could be called to designate accumulation to and from equipment by effectuation of the RS232 port and to transmit on the corporate meshwork using User Datagram Protocol, or UDP.Successful interior deployments of the Natural Bridge led us to consider what it would take to organisation a new version that we could deploy commercially on a super scale. We knew that the main limitations to distributed ingest of the original Natural Bridge were the proprietary OS, a restricted meshwork stack, and the requisite of developing every cipher in assembly language. Realizing that some OS that we matured or licensed would belike demand broad acceptance in the marketplace, we touched to a new organisation that employed an embedded Java programming environment.That solved our digit large problems. First, programmers would be healthy to program in the Java language instead of assembly. Second, they would be isolated from the details of the underlying OS. The new organisation also included a flooded TCP/IP stack, swollen I/O capabilities, and a higher-performance microprocessor. Once full implemented, this approach promises to overcome every the deficiencies in the earlier organisation and open the door to distributed commercial use.