Copyright © Philip M. Parker, INSEAD. Terms of Use.
Definition: Embedded |
EmbeddedAdjective1. Enclosed firmly in a surrounding mass; "found pebbles embedded in the silt"; "stone containing many embedded fossils"; "peach and plum seeds embedded in a sweet edible pulp". 2. Inserted as an integral part of a surrounding whole; "confused by the embedded Latin quotations"; "an embedded subordinate clause". Source: WordNet 1.7.1 Copyright © 2001 by Princeton University. All rights reserved. |
Date "embedded" was first used in popular English literature: sometime before 1550. (references) |
| Domain | Definition |
Transportation | Said of a piece which has been introduced into the body of another. Source: European Union. (references) |
Source: compiled by the editor from various references; see credits. | |
(From Wikipedia, the free Encyclopedia)
In mathematics, see Embedding.In computer engineering, see Embedded system.
Source: adapted by the editor from Wikipedia, the free encyclopedia under a copyleft GNU Free Documentation License (GFDL) from the article "Embedded."
(From Wikipedia, the free Encyclopedia)
An embedded system is a special-purpose computer system built into a larger device. An embedded system is typically required to meet very different requirements than a general-purpose personal computer.
Two major areas of differences are cost and power consumption. Since many embedded systems are produced in the tens of thousands to millions of units range, reducing cost is a major concern. Embedded systems often use a (relatively) slow processor and small memory size to minimize costs.
The slowness is not just clock speed. The whole architecture of the computer is often intentionally simplified to lower costs. For example, embedded systems often use peripherals controlled by synchronous serial interfaces, which are ten to hundreds of times slower than comparable peripherals used in PCs.
Programs on an embedded system often must run with real-time constraints. Usually there is no disk drive, operating system, keyboard or screen.
There are many different CPU architectures used in embedded designs. This in contrast to the desktop computer market, which as of this writing (2003) is limited to just a few competing architectures, chiefly Intel's x86, and the Apple/Motorola/IBM PowerPC, used in the Apple Macintosh.
One common configuration for embedded systems is the system on a chip, an application-specific integrated circuit, for which the CPU was purchased as intellectual property to add to the IC's design.
The software tools (compilers, assemblers and debugger) used to develop an embedded system can come from several sources:
They often have no operating system, or a real-time operating system, or the programmer is assigned to port one of these to the new system.
- Software companies that specialize in the embedded market
- Ported from the GNU software development tools
- Sometimes, development tools for a personal computer can be used if the embedded processor is a close relative to a common PC processor.
Debugging is usually performed with an in-circuit emulator, or some type of debugger that can interrupt the microcontroller's internal microcode.
The microcode interrupt lets the debugger operate in hardware in which only the CPU works. The CPU-based debugger can be used to test and debug the electronics of the computer from the viewpoint of the CPU. This feature was pioneered on the PDP-11.
Developers should insist on debugging which shows the high-level language, with breakpoints and single-stepping, because these features are widely available. Also, developers should write and use simple logging facilities to debug sequences of real-time events.
PC or mainframe programmers first encountering this sort of programming often become confused about design priorities and acceptable methods. Mentoring, code-reviews and egoless programming are recommended.
History
The first recognizably modern embedded system was the Apollo Guidance Computer, developed by Charles Draper and the MIT Instrumentation Laboratory. Each flight to the moon had two. They ran the inertial guidance systems of both the command module and LEM.
At the project's inception, the apollo guidance computer was considered the riskiest item in the apollo project.
The first mass-produced embedded system was the guidance computer for the minuteman missile. It also used integrated circuits, and was the first volume user of them. Without this program, integrated circuits might never have reached a usable price-point.
The crucial design features of the minuteman computer were that its guidance algorithm could be reprogrammed later in the program, to make the missile more accurate, and the computer could also test the missile, saving cable and connector weight.
Design of embedded systems
The electronics usually uses either a microprocessor or a microcontroller. Some large or old systems use general-purpose mainframe computers or minicomputers.
Start-up
All embedded systems have start-up code. Usually it disables interrupts, sets up the electronics, tests the computer (RAM, CPU and program), and then starts the application code. Many embedded systems recover from short-term power failures by skipping the self-tests if the software can prove they were done recently. Restart times under a 1/10 of a second are commonplace.
Many designers have found a software-controlled light useful to indicate errors. One common way to handle it is to have the electronics turn it off (which looks broken) at reset. The software turns it on at the first opportunity to prove the light works. After that, the code blinks it during normal operation, and maybe in patterns for errors. This reassures many users and technicians.
Types of embedded software architectures
There are several basically different types of software architectures in common use.
The control loop
In this design, the software simply has a loop. The loop calls subroutines. Each subroutine manages a part of the hardware or software. Interrupts generally set flags, or update counters that are read by the rest of the software.
A simple API disables and enables interrupts. Done right, it handles nested calls in nested subroutines, and restores the preceding interrupt state in the outermost enable. This is one of the simplest methods of creating an exokernel.
Typically, there's some sort of subroutine in the loop to manage a list of software timers, using a periodic real time interrupt. When a timer expires, an associated subroutine is run, or flag is set.
Any expected hardware event should be backed-up with a software timer. Hardware events fail about once in a trillion times. That's about once a year with modern hardware. With a million mass-produced devices, leaving out a software timer is a business disaster.
State machines are implemented with a function-pointer per state-machine (in C++, C or assembly, anyway). A change of state stores a different function into the pointer. The function pointer is executed every time the loop runs.
Many designers recommend reading each IO device once per loop, and storing the result so the logic acts on consistent values.
Many designers prefer to design their state machines to check only one or two things per state. Usually this is a hardware event, and a software timer.
Designers recommend that hierarchical state machines should run the lower-level state machines before the higher, so the higher run with accurate information.
Complex functions like internal combustion controls are often handled with multi-dimensional tables. Instead of complex calculations, the code looks up the values. The software can interpolate between entries, to keep the tables small and cheap.
Some designers keep a utility program to turn data files into code, so that they can include any kind of data in a program.
Most designers also have utility programs to add a checksum or CRC to a program, so it can check its program data before executing it.
One major weakness of this system is that it does not guarantee a time to respond to any particular hardware event. Another is that it can become complex to add new features.
The strength is that it's simple, and on small pieces of software the loop is usually so fast that nobody cares that it's unpredictable.
Another advantage is that this system guarantees that the software will run. There's no mysterious operating system to blame for bad behavior.
Careful coding can easily assure that nothing disables interrupts for long. Thus interrupt code can run at very precise timings.
Nonpreemptive multitasking
This system is very similar to the above, except that the loop is hidden in an API. One defines a series of tasks, and each task gets its own subroutine stack. Then, when a task is idle, it calls an idle routine (usually called "pause", "wait" or etc.).
An architecture with similar properties is to have an event queue, and have a loop that removes events and calls subroutines based on a field in the queue-entry.
The advantages and disadvantages are very similar to the control loop, except that adding new software is easier. One simply writes a new task, or adds to the queue-interpreter.
Preemptive timers
Take any of the above systems, but add a timer system that runs subroutines from a timer interrupt. This adds completely new capabilities to the system. For the first time, the timer routines can occur at a guaranteed time.
Also, for the first time, the code can step on its own data structures at unexpected times. The timer routines must be treated with the same care as interrupt routines.
Preemptive tasks
Take the above nonpreemptive task system, and run it from a preemptive timer or other interrupts.
Suddenly the system is quite different. Any piece of task code can damage the data of another task- they must be precisely separated. Access to shared data must be rigidly controlled, with message queues or semaphores.
Often, at this stage, the developing organization buys a real-time operating system. This can be a wise decision if the organization lacks people with the skills to write one, or if the port of the operating system to the hardware will be used in several products. Otherwise, be aware that it usually adds six to eight weeks to the schedule, and forever after programmers can blame delays on it.
Office-style operating Systems
These are popular for embedded projects that have no systems budget. In the opinion of at least one author of this article, they are usually a mistake. Here's the logic.
Operating systems are specially-packaged libraries of reusable code. If the code does something useful, the designer saves time and money. If not, it's worthless.
Operating systems for business systems lack interfaces to embedded hardware. For example, if one uses Linux to write a motor controller or telephone switch, most of the real control operations end up as numbered functions in an IOCTL call. Meanwhile, the normal read, write, fseek, interface is purposeless. So the operating system actually interferes with development.
Office style operating systems protect the hardware from user programs. That is, they interfere with embedded systems development profoundly.
Since most embedded systems do not perform office work, most of the code of an office operating systems is waste. For example, most embedded systems never use a file system or screen, so file system amd GUI logic is waste.
Operating systems must invariably be ported to an embedded system. That is, the hardware driver code must always be written anyway. Since this is the most difficult part of the operating system, little is saved by using one.
Last, the genuinely useful, portable features of operating systems are small pieces of code. For example, a basic TCP/IP interface is about 3,000 lines of C code. Likewise, a simple file system. So, if a design needs these, they can be had for less than 10% of the typical embedded system's development budget, without a royalty, just by writing them. Also, if the needed code is sufficiently generic, the back of embeded systems magazines typically have vendors selling royalty-free C implmentation.
A notable, beloved exception to all of these objections is DOS for an IBM-PC. If you use a single-card computer, the BIOS is done, thus no drivers. DOS permits code to write to hardware. Finally, DOS doesn't do much, so it's compact.
Exotic custom operating systems
Some systems require safe, timely, reliable or efficient behavior unobtainable with the above architectures. There are well-known tricks to construct these systems:
Hire a real system programmer. They cost a little more, but can save years of debugging, and the associated loss of revenue.
RMA, rate monotonic analysis, can be used to find whether a set of tasks can run under a defined hardware system. In its simplest form, the designer assures that the quickest-finishing tasks have the highest priorities, and that on average, the CPU has at least 30% of its time free.
Harmonic tasks optimize CPU efficiency. Basically, designers assure that everything runs from a heartbeat timer. It's hard to do this with a real-time operating system, because these usually switch tasks when they wait for an I/O device.
Systems with exactly two levels of priority (usually running, and interrupts-disabled) cannot have inverted priorities, in which a lower priority task waits for a higher-priority task to release a semaphore or other resource.
Systems with monitors can't have deadlocks. A monitor locks a region of code from interrupts or other preemption. If the monitor is only applied to small, fast pieces of code, this can work acceptably well.
This means that systems that use dual priority and monitors are safe and reliable because hey lack both deadlocks and priority inversion. If they use harmonic tasks, they can even be fairly efficient. However, RMA can't characterize these systems, and levels of priority had better not exist anywhere, including in the operating system.
User interfaces
User interfaces for embedded systems vary wildly, and thus deserve some special comment.
Designers recommend testing the user interface for usability at the earliest possible instant. A quick, dirty test is to ask an executive secretary to use cardboard models drawn with magic markers, and manipulated by an engineer. The videotaped result is likely to be both humorous and very educational. In the tapes, every time the engineer talks, the interface has failed: It would cause a service call.
Exactly one person should approve the user interface. Ideally, this should be a customer, the major distributor or someone directly responsible for selling the system. The decisionmaker should be able to decide. The problem is that a committee will never make up its mind, and neither will some people. Not doing this causes avoidable, expensive delays. A usability test is more important than any number of opinions.
Interface designers at PARC, Apple Computer, Boeing and HP minimize the number of types of user actions. For example, use two buttons (the absolute minimum) to control a menu system (just to be clear, one button should be "next menu entry" the other button should be "select this menu entry"). A touch-screen or screen-edge buttons also minimize the types of user actions.
Another basic trick is to minimize and simplfy the type of output. Designs should consider using a status light for each interface plug, or failure condition, to tell what failed. A cheap variation is to have two light bars with a printed matrix of errors that they select- the user can glue on the labels for the language that she speaks.
For example, Boeing's standard test interface is a button and some lights. When you press the button, all the lights turn on. When you release the button, the lights with failures stay on. The labels are in basic english.
For another example, look at a small computer printer. You might have one next to your computer. Notice that the lights are labelled with stick-on labels that can be printed in any language. Really look at it.
Designers use colors. Red means the users can get hurt- think of blood. Yellow means something might be wrong. Green means everything's OK.
Another essential trick is to make any modes absolutely clear on the user's display.
If an interface has modes, they must be reversible in an obvious way.
Most designers prefer the display to respond to the user. The display should change immediately after a user action. If the machine is going to do anything, it should start within 7 seconds, or give progress reports.
If a design needs a screen, many designers use plain text. It can be sold as a temporary expedient. Why is it better than pictures? Users have been reading signs for years. A GUI is pretty and can do anything, but typically adds a year from artist, approval and translator delays and one or two programmers to a project's cost, without adding any value. Often, a clever GUI actually confuses users.
If a design needs to point to parts of the machine (as in copiers), these are labelled with numbers on the actual machine, that are visible with the doors closed.
A network interface is just a remote screen. It needs the same caution as any other user interface.
One of the most successful general-purpose screen-based interfaces is the two menu buttons and a line of text in the user's native language. It's used in pagers, medium-priced printers, network switches, and other medium-priced situations that require complex behavior from users.
When there's text, there are languages. The default language should be the one most widely understood. Right now this is English. French and Spanish follow.
Most designers recommend that one use the native character sets, no matter how painful. People with peculiar character sets feel coddled and loved when their language shows up on machinery they use.
Text should be translated by professional translators, even if native speakers are on staff. Marketing staff have to be able to tell foreign distributors that the translations are professional.
A foreign organization should give the highest-volume distributor the duty to review and correct any translations in his native language. This stops critiques by other native speakers, who tend to believe that no foreign organization will never know their language as well as they.
Examples of embedded systems
See also real-time, real-time operating system, microprocessor
- automatic teller machines
- computer printers
- disk drives
- cellular telephones and telephone switches.
- inertial guidance systems for aircraft and missiles.
- medical equipments
- video game consoles
- industrial machinery use programmable logic controllers to handle automation and monitoring.
- engine control computers and antilock brake controllers for automobiles
- wristwatches
- household appliances, including microwave ovens, washing machines, television sets, DVD Players/Recorders
- home automation products, like thermostats, sprinkler, and security monitoring systems
- network equipment, including routers and firewalls
Source: adapted by the editor from Wikipedia, the free encyclopedia under a copyleft GNU Free Documentation License (GFDL) from the article "Embedded system."
(From Wikipedia, the free Encyclopedia)
In mathematics, an embedding is one instance of some mathematical object contained within another instance, such as a group that is a subgroup.In the geometry of manifolds, a manifold M given abstractly is considered as a candidate to be embedded in Euclidean space of given dimension n (at least dim M, naturally: see invariance of domain). That means we look for a submanifold of n-dimensional Euclidean space that is at least homeomorphic to M. If M is smooth we shall want a diffeomorphism; in the case of a Riemannian manifold an isometry (cf. Nash embedding theorem). The interest here is in how large n must be, in terms of the dimension m of M. The basic results of differential topology here concern the case n = 2m. For example the real projective plane of dimension 2 requires n = 4 for an embedding. The less restrictive condition of immersion applies to the Boy's surface - which has self-intersections.
In fact the occasion of the proof by Hassler Whitney of the embedding theorem for smooth manifolds is said (rather surprisingly) to have been the first complete exposition of the manifold concept (which had been implicit in Riemann's work, Lie group theory, and general relativity for many years); building on Hermann Weyl's book The Idea of a Riemann surface.
In domain theory, an embedding is a complete partial order F in [X -> Y] is an embedding if
("<=" is written in LaTeX as
- For all x1, x2 in X, x1 <= x2 <=> F x1 <= F x2 and
- For all y in Y, x | F x <= y is directed.
\\sqsubseteq).Based on an article from FOLDOC, used by permission.
Source: adapted by the editor from Wikipedia, the free encyclopedia under a copyleft GNU Free Documentation License (GFDL) from the article "Embedding."
Crosswords: Embedded |
| English words defined with "embedded": Alecithal ♦ breccia ♦ crustose thallus ♦ Embedment ♦ flintlock, fossilise, fossilize ♦ Ground mass, ground substance, groundmass ♦ ingrown hair, ingrown toenail, intercellular substance ♦ Joint bolt ♦ leatherjack, leatherjacket ♦ marang, matrix, Millefiore glass, Mudsill ♦ onyxis ♦ porphyritic rock, porphyry ♦ root ♦ slivery, splintery ♦ tooth root ♦ Wynnea sparassoides. (references) |
| Specialty definitions using "embedded": become embedded in/to ♦ Debugging and specification of Ada real time embedded systems ♦ Embedded housing unit, Embedded Lisp Interpreter, Embedded Mode, embedded system ♦ Incremental Prototyping Technology for Embedded Realtime Systems. (references) |
| Etymologies containing "embedded": Embed. (references) |
| Domain | Usage | |
Lyrics | Serve words with nerve embedded I said it word (Feel Me Flow; performing artist: Naughty By Nature) | |
Source: compiled by the editor from various references; see credits. | ||
| Domain | Title | ||
References | |||
Books | |||
Periodicals |
| ||
Music |
| ||
High Tech |
| ||
Consumer Goods | |||
Source: compiled by the editor from various references; see credits. | |||
| Thumbnail | Description & Credit | Thumbnail | Description & Credit |
 | Sections of tissue embedded in paraffin wax are sliced and floated on a hot-water bath in preparation for histological study. Credit: Unknown photographer/artist. |  | Tridacna Crocea - Giant clam embedded in coral Demonstrating variable zooxanthellae colorization in mantle. Credit: The Coral Kingdom. |
 | Figure 13. A clamshell type grab sampler - this device was meant to grab material from the upper layers of seafloor sediment for study of the embedded fauna. Credit: Sailing for Science - the NOAA Fleet Then and Now. |  | A look at the new Defense Department common access card. With an 32 kilobyte embedded computer chip, magnetic stripe and two bar codes, the "Smart Card" will eventually replace the standard military identification card. (File photo). |
 | View in the Civil War exhibit area, March 1980, showing the sternpost of USS Kearsarge with an unexploded shell from CSS Alabama embedded in it, a relic of the 19 June 1864 battle between those two ships. Other artificts visible include the Historical Data Plaque of USS Cushing (DD-797), immediately to the right of the Kearsarge sternpost. Photographed by PH3c F. Brownson. Credit: NAVY. | ||
Source: pictures compiled by the editor from various references; see picture credits. | |||
 |
| "Shell in the sand" by Tyniuz C. Commentary: "Shell embedded in the sand at the beach." |
Source: photographs selected by the editor, with permission from the photographers. |
| Subject | Topic | Quote |
Health | Embedded ticks should be removed using fine-tipped tweezers. (references) | |
The gateways to this new territory are the receptors, coil-shaped proteins embedded in neuron membranes. (references) | ||
Adult stages of Anisakis simplex or Pseudoterranova decipiens reside in the stomach of marine mammals, where they are embedded in the mucosa, in clusters. (references) | ||
Business | This service is available on phones equipped with a SIM card, which has an embedded micro-browser that functions like a PC web browser. (references) | |
The most popular diamond rings are of the embedded stud type, though solitaire engagement rings with a high quality diamond set in gold show strong potential for growth. (references) | ||
According to Asia Pacific Metalworking Equipment News, there are more than 38 million embedded devices used globally in cars, cell phones, digital cameras, dishwashers, refrigerators, telecommunication and data communication and industrial controls. (references) | ||
Economic History | Zimbabwe | Very high money supply growth rates in the first quarter of the year do not bode well for inflation reduction, as both monetary and cost-push factors are well embedded. (references) |
Taiwan | High-demand U.S.-origin software includes operation systems, Internet/networking software, EC/EB software, enterprise application software (CRM, ERP, SCM), knowledge management software, information security software, embedded software, and tools for workstations and workstation platforms. (references) | |
Worker Rights | Costa Rica | The Labor Ministry denied the reports but acknowledged that solidarity association culture is deeply embedded. (references) |
Source: compiled by the editor from ICON Group International, Inc.; see credits. | ||
| "Embedded" is generally used as a lexical verb (past participle) -- approximately 52.81% of the time. "Embedded" is used about 409 times out of a sample of 100 million words spoken or written in English. Its rank is based on over 700,000 words used in the English language. Some parts-of-speech are not covered due to the samples used by the British National Corpus. (note: percents less than one-hundredth of one percent have been omitted) |
| Parts of Speech | Percent | Usage per 100 Million Words | Rank in English |
| Lexical Verb (past participle) | 52.81% | 216 | 20,583 |
| Adjective (general or positive) | 30.07% | 123 | 28,925 |
| Lexical Verb (past tense) | 16.38% | 67 | 40,952 |
| Noun (proper) | 0.49% | 2 | 245,945 |
| Noun (common) | 0.24% | 1 | 339,140 |
| Total | 100.00% | 409 | N/A |
Source: compiled by the editor from several corpora; see credits.
| Country | Name |
| Germany | Kontron embedded computers AG |
| (more examples...) |
Source: compiled by the editor from Icon Group International, Inc.
Expressions using "embedded": become embedded in/to ♦ Debugging and specification of Ada real time embedded systems ♦ embedded cloud ♦ embedded costs exceeding market prices ♦ embedded fixed ♦ embedded Lisp Interpreter ♦ embedded loss ♦ embedded Mode ♦ embedded sentence ♦ embedded surrounded ♦ embedded system ♦ incremental Prototyping Technology for Embedded Realtime Systems. Additional references. | |
| Hypenated Usage | |
Ending with "embedded": part-embedded, practically-embedded, socially-embedded, status-embedded. | |
| Source: compiled by the editor from various references; see credits. | |
| The following statistics estimate the number of searches per day across the major English-language search engines as identified by various trade publications. Hyperlinks lead to commercial use of the expression at Amazon.com. |
| Language | Translations for "embedded"; alternative meanings/domain in parentheses. | |
Chinese | 埋置 (Embed, embedding, imbed, Imbedded, Imbedding). (various references) | |
Danish | lejret i, indstøbt (encapsulated), indlagt, indbygget (built-in, predefined). (various references) | |
Dutch | ingestort, ingebed (inserted). (various references) | |
Finnish | kiinnivalettu (cast-on). (various references) | |
French | encastré, noyé. (various references) | |
German | eingebettet (ingrained), bettete ein. (various references) | |
Greek | ενσωματωμένος (built-in, predefined). (various references) | |
Hebrew | מעורה (attached, integrated, rooted). (various references) | |
Hungarian | beágyazott felhõ (embedded cloud). (various references) | |
Italian | incastrato (inletted, let in), annegato (drowned). (various references) | |
Japanese Kanji | 埋め込み . (various references) | |
Japanese Katakana | うめこみ. (various references) | |
Korean | 끼워넣는 (Imbedded, telescoped). (various references) | |
Pig Latin | embeddeday.(various references) | |
Portuguese | engastado (inserted), embebido (impregnate, impregnated). (various references) | |
Russian | вставлять вложенный. (various references) | |
Serbo-Croatian | ugrađen (built in). (various references) | |
Spanish | empotrado (built in, set in), embutido (inlaid, inlay, inlaying, sausage), embebido, insertado (inserted), incrustado (inlaid). (various references) | |
Swedish | ingjuten (encapsulated), inbäddat, inbäddad. (various references) | |
| Source: compiled by the editor from various translation references. | ||
Misspellings | |
"Embedded" is suggested in spellcheckers for the following: embbeded, embeded, embeedded, embendded, embended, emedded, unbedded. (additional references) | |
| Source: compiled by the editor, based on several corpora (additional references). | |
| # of Phoneme Matches | Pronunciation | Word(s) rhyming with "embedded" (pronounced embe"dud) |
| 6 | -m b e" d u d | imbedded. |
| 5 | -b e" d u d | bedded. |
| 4 | -e" d u d | beheaded, breaded, leaded, dreaded, headed, shredded, threaded, unleaded, wedded. |
| 3 | -d u d | abounded, acceded, accorded, abided, added, afforded, aided, alluded, amended, appended, applauded, apprehended, ascended, astounded, attended, avoided, awarded, backhanded, banded, barricaded, beaded, bearded, befriended, bended, bladed, blended, blinded, blindfolded, blindsided, blockaded, blooded, boarded, bombarded, bonded, bounded, braided, branded, broadsided, brooded, candid, carded, cascaded, ceded, chided, clouded, coded, coincided, collided, colluded, commanded, commended, compounded, comprehended, conceded, concluded, confided, confounded, contended, corded, corresponded, corroded, crowded, decided, deeded, defended, defrauded, degraded, deluded, demanded, denuded, depended, derided, descended, disbanded, discarded, intruded, invaded, jaded, kidded, landed, larded, lauded, lightheaded, loaded, lopsided, disregarded, dissuaded, distended, divided, downgraded, downloaded, dumbfounded, eluded, encoded, ended, enshrouded, eroded, evaded, evenhanded, exceeded, excluded, expanded, expended, exploded, expounded, extended, extruded, exuded, faded, fended, feuded, fielded, flooded, folded, forwarded, founded, funded, gilded, glided, goaded, graded, grounded, guarded, guided, handed, hardheaded, heeded, heralded, herded, hoarded, homesteaded, hooded, hounded, impeded, imploded, impounded, included, intended, interceded, masterminded, melded, mended, minded, misguided, molded, muddleheaded, needed, nodded, offended, outmoded, overcrowded, overextended, overfunded, overloaded, padded, paraded, persuaded, pervaded, pleaded, plodded, pounded, preceded, precluded, prerecorded, presided, pretended, prided, proceeded, prodded, propounded, provided, raided, railroaded, rebounded, receded, recommended, recorded, redheaded, refunded, regarded, reloaded, remanded, reminded, remolded, reprimanded, rescinded, resided, responded, retarded, rewarded, rounded, safeguarded, sanded, scalded, scolded, seceded, secluded, seconded, seeded, serenaded, shaded, shepherded, shielded, shrouded, sided, skidded, sordid, sounded, spearheaded, speeded, splendid, stampeded, stranded, studded, subdivided, subsided, succeeded, superseded, surrounded, suspended, tended, traded, transcended, trended, unaided, unamended, unattended, unbounded, unbranded, undecided, underfunded, underhanded, undivided, unexploded, unfolded, unfounded, unfunded, unguarded, unheeded, unheralded, unimpeded, unintended, unloaded, unneeded, unrecorded, upbraided, upgraded, voided, wadded, waded, warded, weeded, welded, wielded, winded, wooded, worded, wounded, wrongheaded, yielded. |
Source: compiled by the editor (additional references); see credits. | ||
Scrabble® Enable2K-Verified Anagrams | |
| Words within the letters "b-d-d-d-e-e-e-m" | |
-2 letters: bedded, deeded, deemed. | |
-3 letters: embed. | |
-4 letters: deed, deem, deme, meed. | |
-5 letters: bed, bee, deb, dee, eme, med. | |
| Words containing the letters "b-d-d-d-e-e-e-m" | |
+2 letters: bemaddened. | |
| Source: compiled by the editor from various references; see credits. SCRABBLE® is a registered trademark. All intellectual property rights in and to the game are owned in the U.S.A and Canada by Hasbro Inc., and throughout the rest of the world by J.W. Spear & Sons Limited of Maidenhead, Berkshire, England, a subsidiary of Mattel Inc. Mattel and Spear are not affiliated with Hasbro. | |
| 1. Definition 2. Crosswords 3. Usage: Modern 4. Usage: Commercial | 5. Images: Slideshow 6. Images: Photo Album 7. Images: Digital Art 8. Quotations: Non-fiction | 9. Usage Frequency 10. Names: Company Usage 11. Expressions 12. Expressions: Internet | 13. Translations: Modern 14. Derivations 15. Rhymes 16. Anagrams | 17. Bibliography |
Copyright © Philip M. Parker, INSEAD. Terms of Use.
