Embedded Systems with ARM Cortex-M3 Microcontrollers in Assembly Language and C First Edition

When you are going into embedded system development using a cortex-M platform, there is a range of books available on amazon.com - I bought them all. This is the only book offering the complete foundation with supporting homepage with exercises, code templates, lab tests and errata doc. Yes, you might find typo's, like you will find typo's in other textbooks, but the auther has provided the reader with a detailed errate dococument. If you email the auther, he is also very keen to reply to help you. No book is perfect, but this one come very close !!!

For experienced engineers, it is still a good book to learn ARM cortex series M architecture. I know there is a 4th edition available. The 3'rd edition is still good enough to pick up many fundamental SOC knowledge.

I am not sure where does all these 5 stars come from. Maybe they are the author's friends?I have bought hundreds of books online and this is first book I feel obligated to give a one star. I am shocked by the irresponsibility by the author.Typos and mistakes are everywhere. Some times you can find more than ten typos in a page. In some sections every r2 is printed as r6. Some sections every '1' is printed as '2'. (I am not sure if the author is capable of counting from 0 to 9)To give you an example, let's see how the author solves the problem "counting the number of 1-bits in a 32 bit integer". Savor the masterpiece:// Count the number of ones in x// Result saved in counterint main(void) {unsigned int x=0xAAAAAAAA;unsigned int y, z;unsigned int counter = 0;counter = x >> 31;while(x > 0) {y = x << 2;z = y >> 31;if (x < y) {counter += z + 1;} else {counter += z;}x = y;}while(1)}I cannot tell you what's wrong with this program because I have no idea how the author's mind works. The author uses 2 pages to give you a detailed explanation of how that masterpiece generates a 16. Yes indeed 0xAAAAAAAA does have 16 ones in it. However the award winning piece also tells you 0xFFFFFFFF has 16 ones in it and 0x22222222 has 16 ones in it. Actually I would rather call this "program" a "16-generator".So I just want to give you an simple. Don't take it too serious. These kind of masterpieces is every in the book. I think it may take me 60-150 pages of A4 pages to list them all.This book is also "amazing" because the author can use two pages to explain something that can be explained by two lines, without giving you a clear idea what he is talking about. However, he can also use several characters to explain something that deserves some examples. To give you an example, here is how he teaches you the instruction STM:STM Rn, register_list store multiple wordsThat's it, the only place tell you the usage of STM in this book. (Maybe I am not smart enough but I really still don't know how STM works)I won't give you a vise-versa example because I don't want to type two pages in the comment.Also when I see a figure or table in a book I don't expect how nice it is. But I certainly don't want them to be upside down or mirrored. But..Anyways I am tired of typing now. It's your choice whether to buy this book. I know when readers buy a book the author gets money. Everyone likes money. But you should have the basic conscience when writing a book and doing anything.****************************************** Edit ******************************************I recently briefly checked out the second version of this book. Most of the issues I found in the first version has been fixed. And the explanation are more comprehensive than the first version. So changing from 1 star to 4 stars.

This is a great introduction to ARM Assembly. The book gives the reader the chance to work through high level concepts, and implement the low level programming behind it. The book is set up to make a smooth transition from C to assembly. It does have typos, but that should be fixed in the next update: Professor Zhu has a list of them compiled.Overall, a great textbook for the price. He could easily have charged 2x or 3x as much.

The above comment with the contents of the book is incomplete, below is the correct table of contents.Chapter 1. See a Program RunningChapter 2. Data RepresentationChapter 3. ARM Instruction Set ArchitectureChapter 4. Arithmetic and LogicChapter 5. Load and StoreChapter 6. Branch and Conditional ExecutionChapter 7. Structured ProgrammingChapter 8. SubroutinesChapter 9. 64-bit Data ProcessingChapter 10. Mixing C and AssemblyChapter 11. Fixed-point and Floating-point ArithmeticChapter 12. InterruptChapter 13. Instruction Encoding and DecodingChapter 14. Generic-purpose I/OChapter 15. General-purpose TimersChapter 16. Stepper Motor ControlChapter 17. Liquid-crystal Display (LCD)Chapter 18. Real-time Clock (RTC)Chapter 19. Direct Memory Access (DMA)Chapter 20. Analog-to-Digital ConverterChapter 21. Digital-to-Analog ConverterChapter 22. Serial Communication ProtocolsChapter 23. MultitaskingAppendix A: Cortex-M3 16-bit Thumb-2 Instruction EncodingAppendix B: Cortex-M3 32-bit Thumb-2 Instruction EncodingAppendix C: HID Codes of a KeyboardBibliographyIndex

I would recommend looking for another book.I have been reading this book for the last couple days for my class and find myself more confused after reading it. I can't count how many mistakes I have found in the example code (for example, the example code that turns an LED on and off with a button, claims that bit 6 of GPIOB_ODR is used for the RED LED, when in fact it is bit 2)The other sections of example code use countless variables and definitions that have been defined SOMEWHERE, but not in the section of code being presented (and rarely in the section on the topic!) I am working with the SPI interfaces and the section of the book dedicated to SPI never once mentions what values things like SPI_CR1_BIDIMODE or SPI_CR1CRC_EN should be! It just presents them and assumes the reader should know the memory map of the device by heart!Of all the textbooks I've used for my engineering classes (undergrad and grad) this is one of the hardest to understand, and it's not because the material is complicated.

It's a great book, has many examples and has a excellent explanations and comments of codes. Has a very good entry to architecture and most basic things of embedded systems and many more things. Really it's a great book.