📄 00000009.htm
字号:
The text explains things in some detail that will permit the reader to <br />understand how and why things work and tips as to why some things may <br />not. <br /> <br />Embedded Systems Building Blocks 2ed by Jean J. Labrosse [Recommended] <br /> <br />Chris Hills writes: <br />A useful book, if you are using microC/OS-II and want a kick-start. <br /> <br />Embedded Systems Design by Steve Heath [Recommended] <br />Chris Hills writes: <br />This book was a breath of fresh air. It is written by a working <br />industrial embedded systems engineer, not an academic writing for <br />students or a book aimed at the hobby market. <br /> <br />Embedded Systems Programming in C and Assembly by John Forest Brown <br />[Recommended] <br />Derek Graham writes: <br />The book is well written, is easy to read and all the diagrams are clear <br /> and unambiguous. <br /> <br />Front Panel - Designing Software for Embedded User Interface by Niall <br />D Murphy [Recommended] <br />Chris Hills writes: <br />...the information and strategy for designing your own effective front <br />panel. <br /> <br />Industrial Control Handbook 3rd ed. by Andrew Parr [Recommended] <br />Chris Hills writes: <br />If you are in industrial control your company probably has this book <br />already. If it does not ask "why not?" <br /> <br />MicroC/OS-II - The Real Time Kernel by Jean J Labrosse [Highly <br />Recommended] <br />Chris Hills writes: <br />I completely recommend this book for MicroC/OS-II users; it will <br />become their bible. <br /> <br />Microcontroller Projects in C for the 8051 by Dogan Ibrahin [Recommended <br /> with Reservations] <br />Chris Hills writes: <br />Master these projects and you have the basic building blocks for most <br />8051 programs. <br /> <br />Microprocessor Architectures by Steve Heath [Recommended] <br />Chris Hills writes: <br />Students will undoubtedly find this book helpful. Lecturers should get a <br /> copy before their students do. Engineers working on Motorola designs <br />will also find that it should enhance their work. Recommended for <br />Motorola users. <br /> <br />PIC Your Personal Introductory Course by John Morton [Highly <br />Recommended] <br />Chris Hills writes: <br />Students and hobbyists have a gift in this book! At this price I would <br />not be surprised if Microchip start giving it away to students instead <br />of the standard data CD! <br /> <br />Programming Embedded Systems in C and C++ by Michael Barr <br />[Recommended] <br />Chris Hills writes: <br />If you wish to get into embedded programming this is a good book. I like <br /> it and would recommend it to students, home users or software engineers <br /> moving to embedded work. <br /> <br />Real Time Software Systems by J E Cooling [Recommended] <br />Chris Hills writes: <br />A must for all software engineering students who need to learn a <br />methodology and those at home who thought they could never afford a CASE <br /> tool. One book covers the lot. <br /> <br />Real-Time UML (2ed) by Bruce Douglass [Highly Recommended] <br />Chris Hills writes: <br />a sensible straightforward introduction to UML <br /> <br />Software Design for Real Time Systems by J E Cooling [Highly <br />Recommended] <br />Chris Hills writes: <br />I highly recommend this book to all embedded engineers. <br /> <br />Please note that opinions are those of the individual reviewers. <br /> <br /> <br />------------------------------------------------------------------------ <br />-------- <br />Embedded Systems by Chris Hills <br />Those of you who still have the old ACCU handbook from the era when I <br />was Hon Sec may note that my biography had the comment "Biggest mistake: <br /> Telling the ACCU Chair person that I had a good idea..." After making <br />some suggestions to The Editor about some things I would like to see <br />in C Vu I find myself agreeing to an Embedded Feature for C Vu! <br /> <br />I did put out a request for some support but this fell of deaf ears. <br />This is unusual as I am informed (by Adrian Gothard at his talk on <br />Embedded Systems at the ACCU Forum in Oxford) that embedded systems <br />out number desktop systems by 10 to 1! <br /> <br />However a lot of these are mass-market consumer products. For example <br />a team of 4 SW Engineers might turn out 4 embedded systems in a year <br />that go in a car that sells 20,000. (80,000 systems). Actually many cars <br /> have more than 4 systems. Then there are lifts and entry systems, <br />microwave cookers and washing machines, aircraft, ships, robots <br />(thousands of them that make cars, cookers, washing machines etc.) <br />radios, telephones and mobile phones (and additionally the SIM card in a <br /> mobile is an embedded system with a CPU in it's own right!) The list <br />goes on and on. <br /> <br />So you can see how embedded systems might outnumber desktop systems. <br />Then there is the philosophical problem that most desktop systems are <br />likely to contain one or two embedded systems... <br /> <br />What makes an embedded system different to a desktop system? Embedded <br />systems are usually but not always dedicated to a single task, have task <br /> specific IO and often only expect to communicate with another computer. <br /> Screens and [full QWERTY] keyboards are uncommon. The "software" is <br />often burnt in to an EPROM or PROM (and then called firmware) this makes <br /> code patches difficult and in some cases impossible. The systems tend <br />to have a minimum amount of memory and the 8bit CPU still rules. <br /> <br />Whilst some of the chips become dated as the leading edge moves on the <br />embedded world is the opposite of the desktop. One does not write SW <br />that will run on machines that are leading edge today and common <br />tomorrow. One has to use a CPU that is cost effective in 100,000 off <br />quantities today and in those quantities a 10p ($0.16) saved per CPU <br />by using an older model is ?0,000 ($16,000) in production. As the desk <br />top runs headlong to 64, 128... bit processing and beyond the majority <br />of the embedded world is still using 8-16 bit (and 4 bit is not <br />completely dead) 32 bit is only the high end though the proliferation of <br /> the i86 chips and (PC based) tools has brought their cost down. <br /> <br />Lastly embedded systems are expected not to crash and if they do, to get <br /> themselves out of the jam. What's more they are expected to be <br />fail-safe. I understand that Microsoft is planning to do an embedded <br />version of Windows... You can try Ctl-Alt-Del in the lift next time it <br />stops! <br /> <br />There is also another difference between "normal" and embedded systems <br />is that the tools tend to be a lot more expensive and specialised. One <br />Borland compiler will run on virtually any PC produce software for <br />almost any PC. Embedded tools run on a host that is separate to the <br />target. The targets tend to be unique and may or may not run an <br />operating system. The tools are usually tied to a specific CPU family; <br />occasionally a specific CPU in that family. Whilst there may be millions <br /> of embedded systems there may be only a few developers for each tool. <br />The 80,000 systems in the car cited earlier only had 4 developers who <br />may only have had 4 compilers and one ICE. <br /> <br /> <br /> <br /> <br />-- <br />执子之手,与子偕老。 <br /> <br /> <br />※ 来源:·BBS 水木清华站 smth.edu.cn·[FROM: 166.111.218.77] <br /><a href="00000009.htm">上一篇</a><a href="javascript:history.go(-1)">返回上一页</a><a href="index.htm">回到目录</a><a href="#top">回到页首</a></center><center><h1>BBS 水木清华站∶精华区</h1></center></body></html>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -