I2C is normally thought of as being a straightforward and easy-to-use interface, but there are some pitfalls that can catch the unwary. In this post I'm going to explain one of them and give some practical advice that will help you avoid being caught out. What is I2C? First of all, to re-cap: I2C
The ability to connect, communicate with, and remotely manage immense numbers of networked, automated devices via the internet has now permeated all areas of our lives. However, against a wider backdrop of increasing cyber fraud and online crime, our growing reliance on interconnected devices is raising serious concerns about security.
The importance of readability is not just about aesthetics and beautiful code – although that plays a part – but it relates directly to the overall lifecycle cost of software.
We're optimistic about the future of embedded design as a profession. As better tools become available, the demands on embedded system designers are growing equally as fast, or even faster.
Since its earliest days, one of the key features of Wind River's VxWorks real-time operating system has been its support for networking. But what happens when the target hardware doesn't support Ethernet?
As embedded software developers, keeping our skills up to date is a continuous challenge, but it's essential for us to exceed the needs of our customers. Here is a flavour of how we at Pebble Bay stay ahead of the curve.
Embedded software allows many of the advanced functions that are common in modern devices. Whilst embedded software can be very simple, it can also be very sophisticated in applications such as process control systems, military weaponry and airplanes.