#Electrical Interfaces

[wordacrosstime]

Programming Embedded Systems (with C and GNU Development Tools)

[Programming Embedded Systems (with C and GNU Development Tools). By Michael Barr & Anthony J Massa. 2nd Edition, 1 October 2006. Publisher: O'Reilly Media. Paperback: 301 pages, Dimensions: ‎ 17.78 x 1.98 x 23.34 cm. ISBN: 978-0-596-00983-0]

In the past 15 months or so I elected to expand my personal and professional skill set to include working with small computing systems, sometimes referred to as microcontrollers.  These devices have become virtually omnipresent, in everything from automobiles and bar-code scanners to toasters and doorbells.  If you operate a late-model vehicle, for instance, you may have as many as 70 (!) of these devices in the car controlling everything from the fuel mixture to emissions to anti-lock brakes and collision avoidance sensing.

I was interested in moving into this arena as part of my career, as there were many openings for people with a strong understanding of the imperatives attendant on both the software and hardware of embedded systems.  I knew a bit about the electronics side of things and I have done software development of one sort or another most of my 40+ years as a professional, but this arena poses unique challenges and opportunities.  I knew I needed to do some specialized self-teaching, and this book seemed like a great place to start.

To start with, what exactly is an embedded system?

As the name implies, it is a system - in this case a miniature computing device - that is a component of a larger framework.  This larger framework can take on myriad forms.  Some of the largest such frameworks are satellite networks.  The embedded system comprises hardware - a central processing unit, or CPU, along with some (minimal) on-board memory and one or more electrical interfaces (e.g. a USB or RJ45 jack) through which it can communicate with the outside world. 

Unlike the computers most of us are familiar with, such as Windows or MacOS-based laptops or Linux servers, these devices often do not have an operating system (WIndows, MacOS and Linux are all operating systems) that performs many of the low-level functions needed to keep the device running and useful. 

This keeps the device flexible in terms of how it can be used, but at the expense of more detailed and subtle development and maintenance requirements.  Thus, the "software" on an embedded system may be a very small bit of computer code that simply turns on the interfaces electrically and then waits for something to happen.

Programming software for these systems is intriguing but fraught with issues that an ordinary computer user never sees.

For example, given that the memory and interface resources on these devices tend to be rather modest, it's necessary for the programmer to take care of any bookkeeping that is necessary to keep the basic functions from colliding.  If one of the interfaces is used to provide a scanned barcode to a waiting receiver, it must pass that information through some on-board memory first.

The embedded software designer needs to be sure that this information can't be corrupted, or "clobbered", by a competing task that might be, for instance, putting the scanning laser into sleep mode to save power.  Moreover, there are cases where the same locations in memory need to be shared by tasks as a part of getting work done.

But what happens if one task is trying to write data to a specific memory location while another task is trying to read from it?  Is there always a specific order in which this happens?  What happens if either operation is incomplete for some reason?  Will the device recover and continue to operate, or will it lock up?  The aforementioned are but a tiny set of examples that the developer must bear in mind.

Messrs Barr and Massa have many decades of experience between the two of them in just these kinds of environments. I was delighted to see just how easy this book is to read and how thoroughly they cover all of the issues that accompany such a software development enterprise.  They are careful to create and explain examples that use commonly-available development kits (I use an STM32 ARM Cortex-M Development Board myself; there is a photo of one such system below) and free or nearly-free software tools to break down the barriers to entry in this field.

This book is really as much about operating system design as it is about microcontroller software development; if one is interested in what nearly every operating system must do, this volume talks all about it. 

Above and beyond this, it is a wealth of anecdotes, sample code, and general wisdom that will really ease the novice into this exciting world of programming and small-device control.

I highly recommend it to anyone who wants to get down on the bare metal with computers.  It is necessary to be at least familiar with the C programming language (almost all of the examples are coded in C) and it would be very helpful to have worked with at least one Assembly language as well.  Beyond that, the only requirement for getting the most out of the book is a willingness to experiment and be delighted.

Image Credits (from above down; with thanks to copyright owners): (1) STM32 ARM Cortex-M Development Board © Copyright Owner, date unknown (2) Book Cover © O'Reilly Media 11 October 2006 (3) Michael Barr © Barr Group 2012-2025. (Anthony J Massa, no photograph found)

Kevin Gillette

Words Across Time

4 February 2025

wordsacrosstime

[megabip-psd]

[thisisrealy2kok]

Electric Sheep in 2003

[forgottenbones]

Trent Reznor and Shinya Tsukamoto collaborate on a commercial for MTV Japan

[sanguine-tenshi]

Genuinely think that if you design a piece of technology that is user unfriendly you should be brought before a firing squad.

[dirtyoldmanhole]

i'm screenshotting the shit out of everything with this second rev playthrough for slowburn references (also hoping to keep pace with the fic as a very gentle way for it to nudge me into finishing fic chapters in order)

and like

i feel like this ^ is the kind of line that makes my headcanon of 'gunter being the security head of the whole northern fortress' pretty much textual canon? versus say like uhhh xander barking orders at everyone.

which has implications for Silas' (almost)-execution :')

[zenovatetech]

How Optical Probes for Meter Communication Are Revolutionizing Utility Management

In an age where everything from smartphones to homes is getting smarter, why should utility meters lag? The demand for efficient, accurate, and real-time data collection has never been higher. Traditional methods of meter reading—mOptical Probes for Meter Communicationanual logging, physical inspections, and wired connections—are becoming obsolete, often leading to errors, delays, and unnecessary operational costs. The future of metering lies in advanced technology that simplifies data retrieval while improving efficiency.

This is where Optical Probes for Meter Communication step in, transforming the way utility companies interact with meters. These compact yet powerful devices facilitate seamless data transfer between meters and external systems, eliminating the need for direct physical connections. Among the various types available, Bluetooth optical probes are emerging as the preferred choice due to their wireless capabilities, ease of use, and compatibility with multiple platforms. But what exactly makes them a game-changer? Let’s explore the key benefits.

Why Bluetooth Optical Probes Are the Future of Meter Communication?

Wireless Convenience for Effortless Data Collection

Gone are the days of carrying multiple cables and worrying about tangled connections. Bluetooth optical probes enable wireless data transfer, allowing technicians to access meter readings remotely without needing a direct wired connection. This reduces setup time and ensures hassle-free communication with meters, even in hard-to-reach locations.

Enhanced Mobility and Flexibility

With Bluetooth-enabled probes, professionals can move freely while collecting data. Whether accessing meters installed in tight spaces, industrial zones, or outdoor locations, users can connect to meters from a distance without compromising accuracy. This flexibility enhances operational efficiency and minimizes disruptions.

Improved Data Accuracy and Reliability

Wireless data transfer via Bluetooth minimizes the risk of human errors often associated with manual readings. With automated communication and real-time synchronization, Bluetooth optical probes ensure precise data collection, reducing inconsistencies and improving overall system accuracy.

As the demand for smarter utility management grows, Optical Probes for Meter Communication are proving to be indispensable tools for the industry. Bluetooth-enabled versions, in particular, offer a combination of convenience, accuracy, and efficiency, making them the ideal choice for seamless meter communication. With wireless connectivity, cross-platform compatibility, and enhanced security, these probes are not just an upgrade—they are the future of metering technology.

[aippals]

Factory Automation in pune | India

The total automation of the production process is what we mean when we talk about factory automation. Using technologies like robotic arms, hydraulic systems, and pneumatic systems to automate the construction of increasingly complicated systems is standard procedure in the manufacturing industry.

[sleepingangelmusic]

Synido Live Dock Pro AUDIO INTERFACE for Computers/ iPad and Phone/ Unbo...

[entertainment-and-you]

Finally! Mercedes Unleashes an Electric G-Wagon

Stuttgart, Germany – Mercedes-Benz is taking its legendary G-Wagon electric with the all-new G580. This marks a significant departure for the G-Class, which has remained largely unchanged since its debut in 1979. Electric Power Meets Off-Road Prowess The G580 features four electric motors, one at each wheel, paired with a two-speed transmission for exceptional off-road capability. This…

[micaelatrombini]

Las sustancias conductivas que se hallan presentes en el zumo de limones, kiwis y frutillas son monitoreadas por sensores específicos de plataforma de código abierto/Arduino ( sensores de conductividad, electroquímicos, de voltaje) contenidas en el interior de los tubos de ensayo.

Esta información (analógica-digital) relevada por los electrolitos en tiempo real son procesadas por el código en software de composición algoritmica, Supercollider, generando frecuencias del espectro del ruido rosa. Las frutas de esta manera, actúan como interfaces, generando distintas señales eléctricas por cantidad de carga contenida.

[tmms2jnes]

https://www.futureelectronics.com/p/semiconductors--memory--RAM--eeprom--i2c-interface-protocol/cat24c64wi-gt3-onsemi-8463176

Random Access Memory, what is an EEPROM, programmable EEPROM manufacturers, ROM

CAT24C64 Series 64 Kb (8K X 8) 1.8 - 5.5 V I2C CMOS Serial EEPROM - SOIC-8

[soysaucevictim]

Decided to do some dishes, cleaned up the kitchen countertops, and the stove top. Experimentally washed one of the burners and end cap (both detachable pieces, placed over the gas outlet).

Learned a lil more just how gas stoves work. I think the burner is pewter, it has that luster. it interfaces with the igniter that sends a spark though it to light the gas.

I was a little worried I messed something up, since it wasn't lighting and i was NOT about to gas myself here (turned on the vent). But ensuring i got the burner BONE DRY let it conduct the electricity well enough to light things up. :Ic

[pesoprima]

You should augment yourself,

NOW

TERU 

[radioactiverats]

Thoughts: Electric shock (Starscream x reader)

The first time it happens, you both react in comically similar fashions - with an ungainly yelp, cradling hand and servo respectively as you jump away from each other.

"What the frag was that?" Starscream hisses. "How is it that humans can generate charge?"

"Charge?" you mutter. You suppose the interpretation makes sense. "That was an electric shock. It happens a lot in winter." You almost laugh at the fact that you completely forgot about the inevitability of this. The bots are giant metal beings, after all.

Starscream scrutinizes you through suspicious, narrowed optics, maintaining a wary distance. He has to admit that it stirred the long-dormant scientific curiosity inside him, though. Cybertronians are no stranger to generating charge, but a charge of this scale only occurs during interface - and their partner, assuming they were cybertronian as well (Hmm. Interesting factor. Starscream files that away for later, if only out of morbid curiosity (lie)), would ordinarily have nullified the charge, in a sense. Either through rerouting, absorbing it into their EM field - grounders were particularly good at this, and had been highly sought after partners for a while. Starscream yanks his spiralling thoughts back with a snarl. Cybertronians had relative control over their EM field, able to project it to comfort, merge with others, achieve understanding with one another without the need for verbal communication. Starscream had considered this a mark of sophistication amongst his species - even if thoughts like these had belonged to a time before the war.

So humans had a primitive EM field, he'd known this for a while. If he reached out to touch your field, so weak it radiated only centimeters from your form (it's not like you knew he was doing that, it's not like you would realize he cared, god forbid anyone knew he cared.), he could feel the maelstrom of your puny human feelings and was all at once shaken by it. How could something so small, which existed for barely a blip of his existence, feel so much?

After some observation, he'd quickly established (with some disappointment) that you had no control over your EM field.

Pathetic, Starscream thought. Another reason that cybertronians are superior beings.

However, his little 'experiments' didn't stop. Unexpected and spontaneous generation of charge was simply not something that his kind did, even if he was loathe to admit his interest (purely scientific, of course).

Which begins a rather undignified exercise of him trying to poke you with a servo when you least expected it, to see if charge would generate - "Ow, FUCK - Starscream!"

You quickly resigned yourself to the fact that you had to fight fire with fire. Quietly approaching from your perch on his desk as he squinted and swore over a stack of datapads, you reach a hand out and slap it onto his arm.

Both of you screech at the same time as an audible SNAP crackles between you. Still, you can't stop your laughter as Starscream bolts upright to hurl every cybertronian profanity in the book at you.