The book is ideal for software developers already familiar with developing code for PC or Unix-workstation execution, but wishing to know how to retarget code for execution on an embedded processor based system. This requires a more complex development, and in particular debug, environment. Additionally, managers new to the embedded product development phases will learn the pitfalls to be avoided. There are many decisions to be made in leading a successfully embedded project.
This book will help you make the right ones and accelerate the acquisition of your project management skills. There are a number of significant pressures affecting currently embedded projects: The drive for shorter product development times; The use of higher performance processors; Increased software complexity and interoperability; The desire to restrain project tool and manpower costs.
The book does a good job at covering these issues. The traditional or established methodologies are covered as well as the latest trends and likely future directions. The Embedded Systems Design is ordered much like a real embedded project.
First, there is the selection process. This includes the processor itself. But this cannot occur in isolation of the software development toolchain; and other critical components, such as a real-time operating system.
The balancing of these sometimes-conflicting requirements is very important and present with the clarity of a veteran campaigner. The Embedded Systems Design book moves on to deal with hardware-software portioning — not something the typical PC software developer has to resolve. Similarly, the construction of the embedded run-time environment is explained. This is followed by an explanation of development tool operation; In particular, the all-too-often challenge of embedded software debug — This topic is particularly well explained.
The book moves on to deal with hardware-software portioning — not something the typical PC software developer has to resolve. Specialized software topics, such as interrupt processing and low-level hardware manipulation are, as you would expect, covered. Finally, there is a section on testing, and an exploration of future trends. It might have been something as simple as the need to turn off optimizations during testing, and the bug was not able to revise the make-file to turn the optimizations back on.
The key takeaway here is that these performance issues need to be resolved sooner rather than later. In fact, all the compiler issues should be part of the internal specification document that will define the development environment of the project. While clearly not the same as missing trace on a PCB, a project decision having to do with the poor choice of a vendor for a critical part can have the same level of schedule impact as trying to chase down an elusive hardware glitch.
My next favorite defect is the hardware bug workaround. This typically occurs later in the process when hardware and software are brought together for the first time. If the hardware is an FPGA, then it is generally a nonissue. If it is a custom ASIC, then it is a big problem. Berger] , Date: July 24, ,Views: Copyright Disclaimer: This site does not store any files on its server.
We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately. Popular ebooks.
0コメント