I have always liked writing. From an early age, I had an ambition to write a book. My first attempt, in my mid-teens, was a science fiction novel. It was not a success. I wrote about 100 pages and I may even still have the typescript. I remember being embarrassed last time I looked at it. One of the best days of my life was back in 1986, when a jiffy bag arrived in the mail containing a book with my name on the cover.<\/p>\n
Since then, I have never really stopped writing …<\/p>\n
With a few exceptions, just about everything I have written has been about electronics and\/or software. Until the last few years, much of my output has been in print – lots of collateral materials, countless magazine articles and another book. Nowadays, the vast majority of what I do is online. This blog is a prime example. I post frequently on a wide range of topics, but, to some extent, I feel rather constrained – both by time and space. It takes time to write a few thousand words and a blog post is necessarily quite brief. So, I welcome opportunities to get into more detail and explore a topic in more depth.<\/p>\n
I publish articles – many of which pick up on themes of blog posts – in a number of places. I have a “column” on embedded.com<\/a> – that means that they publish my pieces on a fairly regular basis. I realized that I do not do a very good job of publicizing those articles, so I figured that it might be useful to provide a guide to some of my recent work on that site:<\/p>\n Embedded software developers quite commonly need to think about individual bits. This is most commonly the case when working with CPU or peripheral device control registers. High level languages, like C, do not accommodate developers’ needs very well in this respect. This article outlines an approach whereby developers can code low level routines using binary in a natural, intuitive way.<\/p>\n It is generally believed that hand-written assembly language code, though time consuming and requiring significant skill, will always yield the best result. This article questions that belief and illustrates common coding situations where using a high level language, like C, with a modern compiler can consistently do better. It is partly a matter of understanding compiler optimization and code generation and partly a question of appreciating human nature.<\/p>\n <\/p>\n USB is widely deployed in embedded devices of all kinds, resulting in simple interconnectivity and interoperability. This simplicity comes at a cost: the internal functions of USB are quite complex. This is of no consequence to the user of a USB-enabled device, but the embedded software developer does need some understanding of USB internals. Even if a commercial USB stack is employed, an appreciation of how it works enables it to be used optimally. A decade and a half ago, the software industry in general, and the embedded software industry in particular, was in a state of near panic. The concern was that much software, that controlled critical systems, may have been designed some years previously and not be able to cope with the date roll-over from 1999 to 2000 – the “millennium bug”. This problem is now just a distant memory, if recalled at all. This article looks at the significance of that problem and whether similar problems may arise before 2099.<\/p>\n When developing embedded software, a key decision, that needs to be addressed, is “Make or buy?” It is common practice to utilize proven software IP, such as real time operating systems, in modern designs and the scope for licensing software components is expanding as time to market pressures make their use more attractive. The main concern of developers is the usability and quality of such IP. This article looks at the precautions that may be taken, the best practices for selecting IP, the role of standard validation suites and where open source fits in.<\/p>\nBinary Anyone?<\/a><\/h3>\n
Is Assembly Language Best?<\/a><\/h3>\n
USB 3 – An Introduction for Embedded Software Developers<\/a><\/h3>\n
\nIn this article, the history and internal operation of USB will be reprised. Then, the changes and enhancements that come along with USB 3 are reviewed.<\/p>\nThe Millennium Bug Revisited<\/a><\/h3>\n
Using Software IP<\/a><\/h3>\n