Be Prepared for Remote Work

What you’ll learn:

What are some of the remote test and development challenges?
How Green Hills Software was prepared to address the challenge of remote developers and testers.

Working remotely went from an occasional benefit to a mandatory situation for those who didn’t have to be in their workplace in person. There are still millions, from first responders to assembly line workers, who can’t work remotely, but there are even more who can do that, especially in the computer and electronics industry.

Still, it’s not simply a matter of using a smartphone to call in daily. In certain cases, a telephone or video-conferencing interface is all some need to get the job done. However, many need a bit more infrastructure. One company that had some of this infrastructure in place was Green Hills Software.

Robert Redfield, Director Business Development, Green Hills Software, said, “Green Hills Software has used an internet-connected Embedded Board Farm for decades. It’s an essential tool for developing and testing real-time operating systems and IDE, and optimizing C/C++ compilers. Before COVID, the Embedded Board Farm was essential for our globally distributed product and test engineers. Over the last 11 months during the pandemic, the offices have been closed, but engineers have used the boards from home without interruption.”

The company’s Embedded Board Farm (Fig. 1) consists of many racks of device-under-test (DUT) boards. Each board has one or more pieces of test equipment connected to it. A central system manages access and operation of each DUT. It has the ability to reset any unit and manages the recording of information as well as access for a remote debugger to take control of the DUT. Duplicates of popular platforms allow more tests or testers to use a particular platform.

1. Shown is one of several embedded board farms that Green Hills engineers remotely use for their product development and testing, connected through Ethernet and Green Hills Probes.

One of the test devices employed in the farm is the Green Hills Probe V4 (Fig. 2). It has an Ethernet interface like many other similar debug probes. There are even systems that have wireless connectivity. The Green Hills Probe functions within the TimeMachine Debugging Suite, which works with the Green Hills MULTI IDE. There’s an LCD status screen on the unit, but that’s not needed for remote operation.

2. These are the various power and connectivity options that the Green Hills Probe V4 supplies to an embedded processor board.

The system can handle multiple chips on a single JTAG scan chain as well as multicore chips. The probe provides programmable power to the board, which simplifies cabling. Power and Ethernet are the only connections needed for a DUT and probe.

Tracking all of these devices is where a lot of the upfront work helped. Developers have access to a Test Suite Dashboard interface (Fig. 3). The system is set up to run multiple tests for regression analysis as well as allow for debugging of individual DUTs.

3. The Test Suite Dashboard distills results from millions of test results per night, enabling the developer working from home to analyze the effects of code changes made during the day.

Any company or group of developers can easily create their own farm using probes like those available from Green Hills. The main issue is scope. Green Hills farm management is used internally and handles a very large number of devices.

Many companies have developed similar farms with custom software to manage the farm. The payoff for them has been significant given the COVID epidemic. It’s enabled movement of developers from the office to their home with almost no change to their use of the farm. Only a few people are involved in adding new hardware to the farm—this process was already set up.