Single-board microcontroller: Difference between revisions

Content deleted Content added
Gtoast21 (talk | contribs)
EPROM burning: Fixed date= error
Chi Loka (talk | contribs)
No edit summary
 
(23 intermediate revisions by 20 users not shown)
Line 1:
{{Short description|Microcontroller built onto a single printed circuit board}}
{{RefimproveMore citations needed|date=June 2011}}
{{Use dmy dates|date=JuneMay 20112020}}
[[Image:Mck glamor 320.jpg|thumb|right|The [[Make Controller Kit]] with an Atmel AT91SAM7X256 ([[ARM architecture|ARM]]) microcontroller.]]
A '''single-board microcontroller''' is a [[microcontroller]] built onto a single [[printed circuit board]]. This board provides all of the circuitry necessary for a useful control task: a [[microprocessor]], [[input/output|I/O circuits]], a [[clock generator]], [[RAM]], stored program memory and any necessary support [[integrated circuit|IC]]s. The intention is that the board is immediately useful to an application developer, without requiring them to spend time and effort to develop controller hardware.
 
As they are usually low-cost, and have an especially low capital cost for development, single-board microcontrollers have long been popular in education. They are also a popular means for developers to gain hands-on experience with a new [[processor family]].
Line 11 ⟶ 13:
|author=Peter Grigson
|author2=David Harris
|date=August-October August–October 1983
}}</ref> made it practical to build an entire controller on a single board, as well as affordable to dedicate a computer to a relatively minor task.
 
In March 1976, [[Intel]] announced a single-board computer product that integrated all of the support components required for their [[8080]] microprocessor, along with 1 [[kilobyte]] of RAM, 4 kilobytes of user-programmable ROM, and 48 lines of parallel digital I/O with line drivers. The board also offered expansion through a bus connector, but could be used without an expansion card cage when applications did not require additional hardware. Software development for this system was hosted on Intel's [[Intellec MDS]] microcomputer development system; this provided assembler and [[PL/M]] support, and permitted [[in-circuit emulation]] for debugging.<ref>[http://www.dvq.com/docs/brochures/intel_sbc_80_10.pdf Intel SBC 80/10 Single Board Computer brochure], 1976</ref>
 
Processors of this era required a number of support chips to be included outside of the processor. [[RAM]] and [[EPROM]] were separate, often requiring memory management or refresh circuitry for [[Dynamic random -access memory|dynamic memory]]. I/O processing might have been carried out by a single chip such as the [[Intel 8255|8255]], but frequently required several more chips.
 
A single-board microcontroller differs from a [[single-board computer]] in that it lacks the general-purpose user interface and mass storage interfaces that a more general-purpose computer would have. Compared to a [[microprocessor development board]], a microcontroller board would emphasize digital and analog control interconnections to some controlled system, whereas a development board might by have only a few or no discrete or analog input/output devices. The development board exists to showcase or train on some particular processor family and, therefore, internal implementation is more important than external function.
Line 25 ⟶ 27:
It was common to offer access to the internal bus through an expansion connector, or at least provide space for a connector to be soldered on. This was a low-cost option and offered the potential for expansion, even if it was rarely used. Typical expansions would be I/O devices or additional memory. It was unusual to add peripheral devices such as tape or disk storage, or a CRT display
 
Later, when [[#Single-chip microcontrollers|single-chip microcontroller]]s, such as the [[8048]], became available, the bus no longer needed to be exposed outside the package, as all necessary memory could be provided within the chip package. This generation of processors used a [[Harvard architecture]] with separate program and data buses, both internal to the chip. Many of these processors used a [[modified Harvard architecture]], where some write access was possible to the program data space, thus permitting in-circuit programming. None of these processors required, or supported, a Harvard bus across a single-board microcontroller. When they supported a bus for expansion of peripherals, a dedicated I/O bus, such as [[I2C|I<sup>2</sup>²C]], One[[1-wireWire]] or various [[serial busesbus]]es, was used.
 
== External bus expansion ==
Line 34 ⟶ 36:
Microcontroller systems provide multiple forms of input and output signals to allow application software to control an external "real-world" system. Discrete digital I/O provides a single bit of data (on or off). Analog signals, representing a continuous variable range, such as temperature or pressure, can also be inputs and outputs for microcontrollers.
 
Discrete digital inputs and outputs might be buffered from the microprocessor data bus only by an addressable latch, or might be operated by a specialized input/output IC, such as an [[Intel 8255]] or Motorola 6821 [[Peripheral Interface Adapter|parallel input/output adapter]]. Later single-chip micrcontrollersmicrocontrollers have input and output pins available. These input/output circuits usually do not provide enough current to directly operate devices like lamps or motors, so solid-state relays are operated by the microcontroller digital outputs, and inputs are isolated by [[signal conditioning]] level-shifting and protection circuits.
One or more analog inputs, with an analog multiplexer and common [[analog -to -digital converter]], are found on some microcontroller boards. Analog outputs may use a digital-to-analog converter or, on some microcontrollers, may be controlled by [[pulse-width modulation]]. For discrete inputs, external circuits may be required to scale inputs, or to provide functions like [[Wheatstone bridge|bridge]] excitation or [[cold junction compensation]].
 
To control component costs, many boards were designed with extra hardware interface circuits but without the components for these circuits installed, leaving the board bare. The circuit was added as an option on delivery, or could be populated later.
Line 43 ⟶ 45:
 
==Communications and user interfaces==
Communications interfaces vary depending on the age of the microcontroller system. Early systems might implement a [[serial port]] to provide [[RS-232]] or [[current loop]]. The serial port could be used by the application program or could be used, in conjunction with a monitor ROM, to transfer programs into the microcontroller memory. Current microcontrollers may support [[USB]], wireless networks ([[Wi-Fi]], [[ZigBeeZigbee]], or others), or provide an Ethernet connection. In addition, they may support a [[TCP/IP]] protocol stack. Some devices have firmware available to implement a Web server, allowing an application developer to rapidly build a Web-enabled instrument or system.
 
== Programming ==
Line 54 ⟶ 56:
|title=Universal EPROM Programmer
|author=Mike Bedford
|date=August-September August–September 1983
|pages=45–51, 37–39
}}</ref> This EPROM was then physically plugged into the board. As the EPROM would be removed and replaced many times during program development, it was common to provide a [[Zero Insertion Force|ZIF]] socket to avoid wear or damage. Erasing an EPROM with a [[ultraviolet|UV]] eraser takes a considerable time, and so it was also common for a developer to have several EPROMs in circulation at any one time.
 
Some microcontroller devices were available with on-board EPROM. These would also be programmed in a separate burner, then put into a socket on the target system.
Line 67 ⟶ 69:
When the single-board controller formed the entire development environment (typically in education), the board might also have included a simple [[hexadecimal]] keypad, calculator-style LED display, and a "monitor" program set permanently in ROM. This monitor allowed [[machine code]] programs to be entered directly through the keyboard and held in RAM. These programs were in machine code, not even in assembly language, and were often assembled by hand on paper before being inputted. It is arguable as to which process was more time-consuming and error prone: assembling by hand, or keying byte-by-byte.
 
Single-board "keypad and calculator display" microcontrollers of this type were very similar to some low-end microcomputers of the time, such as the [[KIM-1]] or the [[Microprofessor I]].<ref name="KIM 1">{{cite web |title=KIM 1 |url=http://www.old-computers.com/museum/computer.asp?c=149 |archive-url=https://web.archive.org/web/20210618184839/http://www.old-computers.com/museum/computer.asp?c=149 |archive-date=2021-06-18 |website=old-computers.com |publisher=Old Computers}}</ref> Some of these microprocessor "trainer" systems are still in production today, used as very low-cost introductions to microprocessors at the hardware programming level.<ref name="Microprofessor">{{cite web
|publisher = Flite Electronics International
|title=KIM 1
|title = Microprofessor Training System
|url=http://www.old-computers.com/museum/computer.asp?c=149
|url = http://flite.co.uk/microprofessor-mpf-1b-z80-training-system.htm
|publisher=[http://www.old-computers.com Old Computers.com]
|url-status = dead
}}</ref> Some of these microprocessor "trainer" systems are still in production today, used as very low-cost introductions to microprocessors at the hardware programming level.<ref name="Microprofessor" >{{cite web
|archiveurl = https://web.archive.org/web/20080509183609/http://www.flite.co.uk/microprofessor-mpf-1b-z80-training-system.htm
|publisher=Flite Electronics International
|archivedate = 9 May 2008}}</ref>
|title=Microprofessor Training System
|url=http://flite.co.uk/microprofessor-mpf-1b-z80-training-system.htm
}}</ref>
 
=== Hosted development ===
Line 84:
 
== Single-chip microcontrollers ==
[[Image:KL Intel D8749.jpg|thumb|A [[Intel 8048|8048]]-family microcontroller with an on-board UV [[EPROM]], the [[8749]] ]]
[[Image:Pickit1 devboard.jpg|thumb|right|A development board for a [[PIC microcontroller|PIC]] family device ]]
Single-chip microcontrollers, such as the Intel [[Intel 8048|8748]], combined many of the features of previous boards into a single IC package. Single-chip microcontrollers integrate memory (both RAM and ROM) on-package and, therefore, do not need to expose the data and address [[Bus (computing)|bus]] through the pins of the IC package. These pins are then available for I/O lines. These changes also reduce the area required on the printed circuit board and simplify the design of the single-board microcontroller. Examples of single-chip microcontrollers include:
Line 100:
== Single-board microcontrollers today ==
[[Image:DwengoBoard.jpg|thumb|right|[[Dwengo]] board]]
It is now cheap and simple to design circuit boards for microcontrollers. Development host systems are also cheap, especially when using [[Open-source software|open source]] software. Higher level programming languages [[Abstraction (computer science)|abstract]] details of the hardware, making differences between specific processors less obvious to the application programmer. Rewritable flash memory has replaced slow programming cycles, at least during program development. Accordingly, almost all development now is based on cross-compilation from personal computers and programs are downloaded to the controller board through a serial-like interface, usually appearing to the host as a USB device.
 
The original market demand for a simplified board implementation is no longer as relevant for microcontrollers. Single-board microcontrollers are still important, but have shifted their focus to:
 
* Easily accessible platforms aimed at traditionally "non-programmer" groups, such as artists, designers, hobbyists, and others interested in creating interactive objects or environments.<ref>[http://www.arduino.cc/ Arduino's home page]</ref> Some typical projects in 2011 included: the backup control of DMX stage lights and special effects, multi-camera control, autonomous fighting robots, controlling bluetooth projects from a computer or smart phone,<ref name="Dwengo" /> LEDs and multiplexing, displays, audio, motors, mechanics, and power control.<ref>Arduino [http://arduino.cc/forum/ User's forum]</ref> These controllers may be embedded to form part of a [[physical computing]] project. Popular choices for this work are the [[Arduino]],<ref name="Arduino, Project homepage">{{cite web |title=Project homepage |url=http://www.arduino.cc/ |access-date=2024-09-05 |website=arduino.cc |publisher=Arduino project}}</ref> [[Dwengo]]<ref name="Dwengo">{{cite web |title=Project homepage |url=http://www.dwengo.org/ |access-date=2024-09-05 |website=dwengo.org |publisher=Dwengo}}</ref><ref>
|title=Project homepage
|url=http://www.arduino.cc/
|publisher=[http://www.arduino.cc/ Arduino project]
}}</ref> [[Dwengo]]<ref name="Dwengo" >{{cite web
|title=Project homepage
|url=http://www.dwengo.org/
|publisher=[http://www.dwengo.org/ Dwengo]
}}</ref><ref>
Timothy L. Warner.
[https://books.google.com/books?id=3TUkAQAAQBAJ "Hacking Raspberry Pi"].
2013.
p. 12.
</ref> or [[Wiring (development platform)|Wiring]].<ref>Wiring.org's Wiring development platform [http://wiring.org.co/ home page]</ref><ref name="Wiring" >{{cite web |title=Wiring hardware. Overview |url=http://wiring.org.co/hardware/index.html |access-date=2024-09-05 |website=wiring.org.co |publisher=Wiring project}}</ref>
|title=Wiring: Hardware
|url=http://wiring.org.co/hardware/index.html
|publisher=[http://wiring.org.co/about.html Wiring project]
}}</ref>
* Technology demonstration boards for innovative processors or peripheral features:
** [[AVR Butterfly]]
** [[Parallax Propeller]]
 
<!--
== Programming single-board microcontrollers ==
Line 143 ⟶ 130:
== See also ==
{{Portal|Electronics}}
* [[Comparison of Singlesingle-board microcontrollers]]
* [[Single-board computer]]
* [[Comparison of single-board computers]]
* [[Microprocessor development board]]
* [[Embedded system]]
* [[Programmable Logiclogic Controller|PLCcontroller]]
* [[Arduino]]
* [[Make Controller Kit#Make Controller Kit|Make Controller Kit]]
Line 155 ⟶ 140:
* [[Raspberry Pi]]
* [[Asus Tinker Board]]
* [[Tinkerforge]]
 
== References ==
{{Reflist|30em}}
 
{{Use dmy dates|date=June 2011}}
 
{{Microcontrollers}}