RTOS pioneer James F. Ready passes away - Embedded.com

RTOS pioneer James F. Ready passes away

I always aim to start a new year in a positive way – looking forward, not back. Sadly, this year will be an exception, as, a few days ago, I heard of the death, just before Christmas, of my old friend and colleague, Jim Ready. It is fair to say the Jim essentially invented the commercial real-time operating system (RTOS). This technology has been a cornerstone of my career, so his death, apart from being a cause of sadness, also marks the end of an era in embedded systems.

In the 1980s, Jim was co-founder of Hunter & Ready, the developers of VRTX – the first commercially available RTOS. This was initially available for 8-bit processors, but was quickly implemented on 16- and 32-bit devices, as they became more popular. VRTX32 was available just as high-end microprocessors were becoming mainstream. In due course, the structure of the product changed and, instead of being distributed on a ROM chip, the software was supplied in a more conventional form as a library. This was VRTXsa. Other variants, like VRTXmc and VRTXoc, were developed subsequently. Unsurprisingly, it took me just a few moments to put my finger of a VRTX manual in my archive. In due course, Hunter & Ready became Ready Systems, with Jim as CEO.

I heard the sad news of Jim’s death from another old friend, Bob Monkman, who reminded me about another aspect of Jim’s influence on the world of embedded software: “In the lates 80’s, a small consulting concern, called Wind River, wrapped a BSD TCP/IP stack and some tools around VRTX and called it VxWorks (i.e. VRTX Works). There was a thin shim layer of APIs on top of VRTX. Due to a business disagreement at a technology crossroads, Wind River designed out VRTX with their own wind kernel, written by John Fogelin, and the suite evolved into Tornado. So, you could say that Jim inspired VxWorks and Tornado in this way.”

Another significant RTOS of the 1990s was pSOS. There were rumors that this OS has some technical “relationship” with VRTX. However, rumors are rumors and this was 20+ years ago, but, again, we see Jim’s influence is manifest.

In the early 1990s, Ready Systems was acquired by Microtec Research, where I worked, which is how I got to know Jim. We were acquired a couple of years later by Mentor Graphics, which leads to where I am right now. I always found Jim to be interesting and, often, inspirational company. I clearly recall sitting in his office as he explained that Linux was the future for embedded systems. Not so long after that, he left to found Montavista, which pioneered embedded Linux.

Jim moved on eventually to become a senior technical advisor on embedded software at Cadence. The last time I met him was in his office there, where he was excitedly talking about new technologies that would change the world.

The world of embedded software – or actually the world as a whole – needs more innovators like Jim Ready. I think that they broke the mold when they made him. RIP Jim.

4 thoughts on “RTOS pioneer James F. Ready passes away

  1. “I had a gig at HP in the 90's. Their instruments used pSOS. Fantastic RTOS. Clean. I was the one who got the mpu when /reset was de-asserted.. Easy to setup tasks, fifo queues, etc.”

    Log in to Reply
  2. “Thank you Colin for honouring your colleague, mentor and friend James Ready. I was active in embedded r/t control systems during the early '80s (in Australia) for mainly 6800/09 mpu targets. I would be interested to know if James Ready was involved dire

    Log in to Reply
  3. “@Mark54 – I am not aware that Jim had any involvement with those OSes. RMX came out of Intel, IIRC; OS9 was a bit of an outlier, but quite popular in its day.”

    Log in to Reply
  4. “I had the pleasure of spending time with Jim at a conference in Shenzhen China. I was at the time based in Sydney, Australia, a FAE supporting the VRTX RTOS and Microtec's embedded development toolchain.nnJim was always so passionate about the state of

    Log in to Reply

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.