What do you think?
Rate this book
Embedded Systems: Architecture, Programming And Design by KAMAL RAJ
This book, equally applicable for a CSE or ECE course, gives an extensive account of Embedded Systems, keeping a balanced coverage of hardware and software concepts. Adhering to syllabus needs, this title is ‘microprocessor’ and ‘software design methodology’ specific, giving due weightage to architecture, programming and design aspects.
Mass Market Paperback
First published September 25, 2006
28 people are currently reading
445 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 4 of 4 reviews
May 2, 2015
I'm giving this 1 star because zero and negative numbers are sadly not accepted.
I've had the misfortune of having to read this book for my UG syllabus. Seriously, that's the worst thing I was forced to do in my entire life.
The book is classless, useless, piece of text that me and my Dad (An embedded systems professional for 30+ years) consider to be an absolute insult to all future engineers!!!
Let me tell you why I'm so fired up about this.
1. Stupid English. Dude, even Eighth graders can write better.
2. Stupid errors... Seriously TCP is Transmission Control Protocol, not Transport Control Protocol(pg 173)., PIC16xx/PIC18Fxx are 8 bit, not 16 bit Microcontrollers(page 9)....
The author is pathetic.. Does he know to use a computer, Google... What world does he live in?? eh?
3. Unwarranted Assumptions on everything...The author cooks up stupid jargons that even Google doesn't recognize. For instance, How are Microcontrollers and DSPs, Application Specific Instruction Set processors, ASIPs as he calls them. What in the difference between a microprocessor/microcontroller and an Embedded Microprocessor/Microcontroller???
4. Irrelevant Examples. He tries to explain his made-up concepts with his own cool (or not-so-cool) examples, that I doubt, even he can understand. However, I agree that the author has a wild sense of Imagination. He should be writing poetry, not technical books.
There is a way of explaining things and this is not it.
If you want to really understand and learn Embedded Systems, try these...
1. Embedded Software Primer - David Simon. Great explanation and great coverage on the basics of task scheduling. An invaluable tool for doing anything with embedded software.
2. Micro C/OS - II by Jean Labrosse. An amazing book. The introductory chapter on RTOS is the best text for understanding how RTOS works. Mr.Labrosse developed The RTOS, uC/OS all by himself and he knows what he is saying.
3. Try Embedded Systems Design by Steve Heath for the basics. The book is very good. However, I am not particularly fond of the processor examples he uses for discussion (Intel 80x86 and Motorola Power PC, 680xx) because they are very old and not very relevant today. However, It is an excellent book for the hardware concepts and the basics.
If you are student who is forced to read this book due to your syllabus, consult an astrologer, this might be a bad time for you. :)
If you are a professor, I humbly request you to recommend for the removal of the book from your university syllabus. Forcing your students to read this text is terrible injustice. Please, We implore you to give us a better fate. No one deserves to be forced to read this.
I've had the misfortune of having to read this book for my UG syllabus. Seriously, that's the worst thing I was forced to do in my entire life.
The book is classless, useless, piece of text that me and my Dad (An embedded systems professional for 30+ years) consider to be an absolute insult to all future engineers!!!
Let me tell you why I'm so fired up about this.
1. Stupid English. Dude, even Eighth graders can write better.
2. Stupid errors... Seriously TCP is Transmission Control Protocol, not Transport Control Protocol(pg 173)., PIC16xx/PIC18Fxx are 8 bit, not 16 bit Microcontrollers(page 9)....
The author is pathetic.. Does he know to use a computer, Google... What world does he live in?? eh?
3. Unwarranted Assumptions on everything...The author cooks up stupid jargons that even Google doesn't recognize. For instance, How are Microcontrollers and DSPs, Application Specific Instruction Set processors, ASIPs as he calls them. What in the difference between a microprocessor/microcontroller and an Embedded Microprocessor/Microcontroller???
4. Irrelevant Examples. He tries to explain his made-up concepts with his own cool (or not-so-cool) examples, that I doubt, even he can understand. However, I agree that the author has a wild sense of Imagination. He should be writing poetry, not technical books.
There is a way of explaining things and this is not it.
If you want to really understand and learn Embedded Systems, try these...
1. Embedded Software Primer - David Simon. Great explanation and great coverage on the basics of task scheduling. An invaluable tool for doing anything with embedded software.
2. Micro C/OS - II by Jean Labrosse. An amazing book. The introductory chapter on RTOS is the best text for understanding how RTOS works. Mr.Labrosse developed The RTOS, uC/OS all by himself and he knows what he is saying.
3. Try Embedded Systems Design by Steve Heath for the basics. The book is very good. However, I am not particularly fond of the processor examples he uses for discussion (Intel 80x86 and Motorola Power PC, 680xx) because they are very old and not very relevant today. However, It is an excellent book for the hardware concepts and the basics.
If you are student who is forced to read this book due to your syllabus, consult an astrologer, this might be a bad time for you. :)
If you are a professor, I humbly request you to recommend for the removal of the book from your university syllabus. Forcing your students to read this text is terrible injustice. Please, We implore you to give us a better fate. No one deserves to be forced to read this.
Currently reading
November 16, 2012great book to read before getting start
December 10, 2015
nice book.
Displaying 1 - 4 of 4 reviews