User Tools

Site Tools


making_embedded_systems

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
making_embedded_systems [2024/07/17 13:13]
sausage [Making Embedded Systems - A Reader's Review]
making_embedded_systems [2024/07/18 11:59] (current)
sausage
Line 1: Line 1:
 ====== Making Embedded Systems - A Reader'​s Review ====== ====== Making Embedded Systems - A Reader'​s Review ======
  
-{{:​embedded-systems:​making-embedded-systems.jpg?​nolink&400 |}}When I first heard that Making Embedded Systems 2nd Edition was up for pre-order, I jumped onto Amazon and handed over my dollars.+{{:​embedded-systems:​making-embedded-systems.jpg?​direct&400 |}}When I first heard that [[https://​www.oreilly.com/​library/​view/​making-embedded-systems/​9781098151539/?​utm_medium=affiliate&​utm_source=impact&​utm_campaign=new+release&​utm_content=making+embedded+systems+2e+20240618|Making Embedded Systems 2nd Edition]] was up for pre-order, I jumped onto Amazon and handed over my dollars.
  
 For a period of time, I have been self-training in a variety of areas of electronics and embedded systems development but in a reasonably random and not entirely organised fashion. For a period of time, I have been self-training in a variety of areas of electronics and embedded systems development but in a reasonably random and not entirely organised fashion.
Line 50: Line 50:
 But it didn't teach me any of the actual use of those protocols. That's not really the point of the book. Already having experience working with some of those protocols on my own, this chapter mainly provided a reinforcement of the availability and difference between so many serial protocols: their benefits and limitations,​ and things to consider as an engineer. But it didn't teach me any of the actual use of those protocols. That's not really the point of the book. Already having experience working with some of those protocols on my own, this chapter mainly provided a reinforcement of the availability and difference between so many serial protocols: their benefits and limitations,​ and things to consider as an engineer.
  
-DMA and Buffers were also welcome topics and another confirmation ​that I was on the right track with my learning.+DMA and Buffers were also welcome topics and another confirmation ​to feel I was on the right track with my learning.
  
 **Chapter Nine** takes us through getting ourselves into trouble and getting out of it again. It looks at debugging, at doing the basics first to solve an issue, problems that optimization can cause or mask, writing into memory that has fallen off a cliff, stack versus heap, registers and core dumps. ​ **Chapter Nine** takes us through getting ourselves into trouble and getting out of it again. It looks at debugging, at doing the basics first to solve an issue, problems that optimization can cause or mask, writing into memory that has fallen off a cliff, stack versus heap, registers and core dumps. ​
Line 60: Line 60:
 Function chains can take up more RAM and reduce speed for the sake of readability and easily maintainable code. Function chains can take up more RAM and reduce speed for the sake of readability and easily maintainable code.
  
-Map files are explained - something I have never used before. These help give an understanding of the breakdown of an executable: the library space, how variables and functions are stored. Using this tool, all sorts of issues can be uncovered, and resource ​allocation ​can be greatly improved.+Map files are explained - something I have never used before. These help give an understanding of the breakdown of an executable: the library space, how variables and functions are stored. Using this tool, all sorts of issues can be uncovered, and resource ​use can be greatly improved.
  
 Registers over variables is covered as a way of improving speed as is reducing the depth of function chains. Registers over variables is covered as a way of improving speed as is reducing the depth of function chains.
Line 79: Line 79:
    
 The safety of motors is covered and how you can add protection to your circuits. It's not hard to blow a MOSFET or your processor when a large motor suddenly stops. ​ The safety of motors is covered and how you can add protection to your circuits. It's not hard to blow a MOSFET or your processor when a large motor suddenly stops. ​
 +
 And that's where it ends. And that's where it ends.
  
Line 89: Line 90:
 In Chapter Seven, is the suggestion that Master/​Slave in MISO and MOSI are out-of-favour terms as an attempt to steer the reader towards "​safer"​ alternatives. I'll stick to the classic terms. In Chapter Seven, is the suggestion that Master/​Slave in MISO and MOSI are out-of-favour terms as an attempt to steer the reader towards "​safer"​ alternatives. I'll stick to the classic terms.
  
-Chapter Five's Interview Question strays into the area of diversity, a subject akin to a worn out recording. I am always happy to see this left out.+Chapter Five's Interview Question strays into that long worn area of diversity. I am always happy to see this left out.
  
-I will say, however, that the author treated the topic with more care and reason than most. Regardless, I don't need this in my materials.+I will say, however, that the author treated the topic with more care and reason than most. Regardless, I prefer to not have this in my materials.
  
  
 ===== Conclusions ===== ===== Conclusions =====
  
-This is a great book. It's not going to hold your hand, and it's not a book of tutorials. It will, however, become your closest companion to help guide your own learning path, giving you valuable insight into what skills and experience ​will be valuable ​for a career in embedded systems.+This is a great book. It's not going to hold your hand, and it's not a book of tutorials. It will, however, become your closest companion to help guide your own learning path, giving you valuable insight into key skills and experience for a career in embedded systems.
  
-I wouldn'​t call it a book for beginners. If you have been learning various aspects of embedded systems for some time then I think this is the sweet spot for this book to work well for you.+It acts as that friendly ​work mate who loves mentoring and who shares knowledge and experience.
  
-This book acts as that friendly ​work mate who loves mentoring and who shares knowledge and experience.+I wouldn'​t call it a book for beginners. If you have been actively learning various aspects of embedded systems then I think this is the sweet spot for it to work well for you
  
-So where to from here? Well, it's time to start overand to absorb each chapter more fully, especially ​that chapter on mathematics. ​+So where to from here? Well, it's time to start over and to absorb each chapter more fully. Especially ​that chapter on mathematics. ​
  
 Or maybe I'll just jump around this time. Or maybe I'll just jump around this time.
  
  
making_embedded_systems.1721222018.txt.gz ยท Last modified: 2024/07/17 13:13 by sausage