- Paperback: 301 pages
- Publisher: O'Reilly Media; 2 edition (October 1, 2006)
- Language: English
- ISBN-10: 0596009836
- ISBN-13: 978-0596009830
- Product Dimensions: 7 x 0.8 x 9.2 inches
- Shipping Weight: 1.2 pounds
- Average Customer Review: 14 customer reviews
Amazon Best Sellers Rank:
#1,462,513 in Books (See Top 100 in Books)
- #162 in Books > Computers & Technology > Hardware & DIY > Microprocessors & System Design > Computer Design
- #180 in Books > Computers & Technology > Hardware & DIY > Microprocessors & System Design > Embedded Systems
- #426 in Books > Computers & Technology > Programming > Languages & Tools > C & C++ > C
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Programming Embedded Systems: With C and GNU Development Tools, 2nd Edition 2nd Edition
Use the Amazon App to scan ISBNs and compare prices.
Customers who bought this item also bought
Customers who viewed this item also viewed
What other items do customers buy after viewing this item?
Thinking Inside the Box
About the Author
Michael Barr is a leading authority on the design of embeddedcomputer systems. He has provided expert testimony in court, appearedon the PBS show "American Business Review", and been quoted innewspaper articles. Barr is also the author of more than fortytechnical articles, co-author of the "Embedded Systems Dictionary",and a founder of EmbeddedGurus.net. For three and a half years heserved as editor-in-chief of Embedded Systems Programming magazine.Mr. Barr also founded Netrino, LLC. The firm helps product companiesdevelop embedded software faster in three ways: by teaching bestpractices, by consulting with system designers, and by outsourcingfirmware implementation. Netrino's engineers have designed ordeveloped software that runs millions of products worldwide, fromconsumer electronics to medical devices.Anthony Massa has over a decade of experience in embedded softwaredevelopment. He has worked on the architecture and development ofsoftware for several products in use today, including satellite andcable modems, wireless radios, set-top boxes, and head-endtransmission equipment. Anthony has written several articles inleading software development magazines focusing on embedded softwaredevelopment and is author of the book Embedded SoftwareDevelopment with eCos.Anthony is Chief Engineer of Software at Elintrix(http://www.elintrix.com), a provider of wireless networked and signalprocessing products. He holds a dual B.S./B.A. degree in electricalengineering from the University of San Diego.
Anthony Massa has over a decade of experience in embedded software development. He has worked on the architecture and development of software for several products in use today, including satellite and cable modems, wireless radios, set-top boxes, and head-end transmission equipment. Anthony has written several articles in leading software development magazines focusing on embedded software development and is author of the book Embedded Software Development with eCos.Anthony is co-founder and Chief Engineer of Software at Elintrix (http://www.elintrix.com), a provider of wireless networked and signal processing products. He holds a dual B.S./B.A. degree in electrical engineering from the University of San Diego.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
I was okay with this and called the dev kit manufacturer from the appendix - arcom and tried to purchase the hardware development kit so I could follow along with the book.
The Arcom distributor for my area indicated that the kit used by this book for this second edition was not only obsoleted but end of lifed and not available for purchase.
This made me quite sad since without the hardware development environment this book becomes practically useless. That is a real shame. Perhaps the authors simply need to locate a dev kit that is available to their readers and do an update?
As a previous embedded developer and hardware engineer I could probably go through the text and learn a handful of techniques, but embedded programming for me has always required some hardware platform.
This is such a shame....
After being a loyal Seattle Amazon customer for so many years, I felt so strongly that this is my very first review after literally dozens and dozens of Amazon purchases. This is the very first time I felt my money was unfortunately wasted.
I had quite some years of experience developing PIC/8051 firmware on Windwos platform, but did not had any experience on Unix. I found the book is particular useful in introducing building project on Unix platform, it is brief, but that's exactly what I wanted - short and simple.
Chapters on hardware, tool chain, memory, interrupts and RTOS are quite fundamental but could come handy to beginner in embedded world despite there are many other books that excel in these areas. However, I found Chapter 7 "Peripherals" is well written to teach you how to write a device driver. I believe this is something new to learn for engineers with either software or hardware background. Hardware engineers tend to access the hardware registers directly. On the other hand, softawre guys may not be familiar with low-level hardware. The authors talked about the device driver philosophy and elaborate on how to use struct and bitfield to provide hardware abstraction. Finally, a serial port device driver is presented as an example.
As a conclusion, this is a very good introductory book to 32-bit embedded programming, or better still if you use Unix/Linux/eCOS. For those who want to learn deeper about RTOS and hardware (say, how to write soft I2C, keypad/button debounce, LCD driver), you wouldn't gain much from this book.
Here in Australia, I am having hard-time finding the hardware board recommended by authors, namely Arcom VIPER-Lite. I do have a Beaglebone Black board (and I am really surprised authors didn't recommend this board when buying it is easier than buying a bottle of coke, at least here in Australia). Like the Arcom VIPER-Lite, the BBB board also has an ARM architecture, but the BBB has Texas Instrument processor clocked 1GHz (VIPER-Lite has Intel's PXA255 processors clocked at 200MHz). Other specs vary a bit, but I am guessing they are less of consequence.
So my question is this: how many percent examples given in the book can I successfully run on my BBB board? This question can be rephrased as: does embedded code depend on architecture (both boards have ARM) or it depends on processors (Texas Instruments vs Intel) or something else? Sorry if the question is stupid but I am learning this embedded coding just now.