Re: Books / Articles on Embedded SW Architecture

Steve at fivetrees wrote:
"Usenet Groups" <myusenetaccount@xxxxxxxxx> wrote in message news:449acfdb$0$11066$9b4e6d93@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm looking for information (good articles, books, websites) concentrating on SW architecture themes related to Embedded platforms.

Primarily SW architecture discussion seem almost solely devoted to the PC world and object orientated languages. I do find some of these topics also apply to the embedded world however I'm missing topics on issues like the list below.

:Multi-processor communication
:Multi-processor System Partitioning
:Protocol Handling
:POST (Power On Self Test)
:Distributing System events (i.e. power up)
:ISO Network Model
:Debug/Trace Strategies
:Error Handling
:How to benchmark sufficiently
:Event-Driven Systems
: ...

Which books do you use when tackling problems such as those mentioned? Which issues should be added to the list?

You missed the most important one:
- Designing demonstrably bug-free software and systems
Steve interesting but I think we should accept that with the tools/languages we use 'bug-free' isn't going to happen, except on trivial projects.

The desktop world has a level of quality *vastly* inferior to that demanded of embedded work, where "crash" == "broken", and maybe "lawsuits" and "closure of company". The mindset is quite, quite different. (And where it's not, it should be.)

This is not just a question of a chapter in a book. It really is a mindset, an attitude. It's the difference between "engineering" and "messing about with an erector set".
I agree totally here


To add just a little: robustness is always the key attribute. *Design* for zero errors; debugging is something that you do when you fail, so aim not to. The hack/debug approach must be seen for what it is: amateurish tinkering.
I don't accept that. We should build mechanisms into our systems in order to 'see' our systems in work. If you or someone in your team does happen to 'fail' then do you have the right tools/procedures for fixing that error? Logging tools, printing debug lines to stdout etc all have their usefulness and should be designed in from the ground up.

Of course you can always over design a system. The more non-functional modules you include, the more complex the system the more chances you have to fail. Like everything it's a balancing act.

I would be interested in techniques people use to debug their systems. Printing to a serial port is OK if you have a spare port but it also can be CPU intensive if the developers over do it with the debug lines.


Hmmm. If I add any more, I'd be in danger of writing a book. (Or possibly a sermon.)

Now there's a thought (the book, not the sermon).... ;)

Steve
http://www.fivetrees.com
http://www.sfdesign.co.uk


.

Relevant Pages

  • Re: Word 2003 Macro Runtime Error 5479
    ... Maybe instead of ActiveWindow ... "Steve W." ... Switch to Word and close the dialog box." ... > And a added Debug button if in debug mode. ...
    (microsoft.public.word.vba.general)
  • Re: Get contents of Immediate window?
    ... Steve Hudson - Word Heretic ... >> Dont debug print them, open a new doc and print to there instead. ... >> steve from wordheretic.com (Email replies require payment) ...
    (microsoft.public.word.vba.general)
  • Re: Old Lux Amp
    ... I have been told that these components do not fail - that is they never ever fail. ... They were replaced about 8-10 years ago when the amp was sounding quite sorry. ... Steve W ... I have to agree with Mark Zacharias, I've worked on many Hafler amps that use these same MOSFETS, and I've almost never had to replace them, it is almost always an input stage or feedback problem on the Haflers, when it is not a bad power switch or filter cap. ...
    (rec.audio.misc)
  • Re: OT:Does this kind of hypocrisy bother you?
    ... the comments in the post you responded to, you would not snip the way you ... Steve: grow a backbone and just try to show the list of the ... non-educational purposes that the Harvard endowment is designed to support. ... You always fail. ...
    (comp.sys.mac.advocacy)
  • Re: aspnet_regiis, VS.Net etc?
    ... Just to add to what Steve said, don't forget that there's a free trial ... > read memory' error). ... > with properties but can debug my 1.1 apps now. ... > tricky not really transparent. ...
    (microsoft.public.dotnet.framework.aspnet)