The MIPS32® 4KEm™ core from MIPS® Technologies is a member of the MIPS32 4KE™ processor core family. It is a
high-performance, low-power, 32-bit MIPS RISC core designed for custom system-on-silicon applications. The core is
designed for semiconductor manufacturing companies, ASIC developers, and system OEMs who want to rapidly integrate
their own custom logic and peripherals with a high-performance RISC processor. It is highly portable across processes, and
can be easily integrated into full system-on-silicon designs, allowing developers to focus their attention on end-user
products. The 4KEm core is ideally positioned to support new products for emerging segments of the digital consumer,
network, systems, and information management markets, enabling new tailored solutions for embedded applications.
FatFs06.rar
FatFs is a generic file system module to implement the FAT file system to small embedded systems. The FatFs is written in compliance with ANSI C, therefore it is independent of hardware architecture. It can be incorporated into cheap microcontrollers, such as 8051, PIC, AVR, SH, Z80, H8, ARM and etc..., without any change.
A UML Documentation for an Elevator System：This paper is a PhD project report for the course Distributed Embedded Systems at Carnegie Mellon University. Throughout this course, a distributed real-time system – an elevator control system– is specified, designed, built, and simulated. Object Oriented Analysis and Design methods, in specific the Unified Modeling Language (UML) are used when designing the system.
RTOS ThreadX
Real-Time Embedded
Multithreading:
Using ThreadX and ARM
Designations used by companies to distinguish their products are often claimed as trademarks. In all instances
where CMP is aware of a trademark claim, the product name appears in initial capital letters, in all capital
letters, or in accordance with the vendor鈥檚 capitalization preference. Readers should contact the appropriate
companies for more complete information on trademarks and trademark registrations. All trademarks and
registered trademarks in this book are the property of their respective holders.
Java technology is both a programming language and a platform. The Java programming language originated as part of a research project to develop advanced software for a wide variety of network devices and embedded systems. The goal was to develop a small, reliable, portable, distributed, real-time operating platform. When the project started, C++ was the language of choice. But over time the difficulties encountered with C++ grew to the point where the problems could best be addressed by creating an entirely new language platform. Design and architecture decisions drew from a variety of languages such as Eiffel, SmallTalk, Objective C, and Cedar/Mesa. The result is a language platform that has proven ideal for developing secure, distributed, network-based end-user applications in environments ranging from network-embedded devices to the World-Wide Web and the desktop
Introduction
Sometimes you may collide with the following problem: a third-party binary component or control embedded into your application displays windows (usually message boxes) that hang your code until they are closed.
If you do not have the source code of this binary and one does not have a good API to change one’s bad behaviour programmatically, it can be a real headache using the one. A famous example of such a binary is the WebBrowser control in .NET.
This document specifies a subset of the C programming language which is intended to be suitable
for embedded automotive systems up to and including safety integrity level 3 (as defined in the
MISRA Guidelines). It contains a list of rules concerning the use of the C programming language
together with justifications and examples.
The Embedded Configurable Operating System (eCos)start-to-finish guide to eCos solution building. Additional open source tools are included to configure a complete embedded software development environment.
describe the operation of theARMcore from a product developer鈥檚
perspective with a clear emphasis on software. Because we have written this book specifically
for engineers who are experienced with embedded systems development but who may be
unfamiliar with the ARM architecture, we have assumed no previous ARM experience.
