How do embedded programmers ever get anything done? Every little thing feels like learning about an entire planetary civilization in order to figure out how to turn a door knob. And small errors will destroy the civilization. I’m
Conversation
Trying to orient using this book and the first chapter is full of dire warnings and ominous lines about how everything is very complex. The opposite of most tech books that assure you everything is easy and step by step.
Replying to
Problem solving process in embedded apparently:
Me “My hello world code won’t compile, the make file chokes”
Book: “In the beginning there was chaos and god created the AM335x universe”
2
31
In embedded, the dev environment is basically “civilization”
All the jank of millennia of civilization packed into a board designed to fit into an alt OODA can
2
2
32
Interesting autocorrect typo
Altoid but alt OODA is good too
1
7
Replying to
I think part of it is that getting good debug info out of embedded stuff as an amateur is just that much harder. You need actual test equipment. Also, you’re working way closer to the actual silicon than most PC/web programming, meaning hardware knowledge is really helpful.
Replying to
It's been this way forever and if it hasn't been fixed by now, there's a cultural reason.
A chimpanzee could design a better build system than GNU, but no vendor would adopt it.
Tradition is toxic.


