Kozio is the technology leader for embedded system verification and test software solutions. With over $17B of returned electronic consumer products in the US alone in 2010, the need for better design verification and functional test solutions is growing. Kozio is uniquely positioned to address this need with a core competency in the hardware / software interface area and years of embedded development experience. Kozio is based in Longmont, CO.

Kozio’s solutions are widely used by engineering and manufacturing teams developing 32-bit embedded systems. This unique multi-domain solution covers engineering, manufacturing, and field, providing a reusable solution that yields significant cost savings to our customers. Kozio’s customer base includes General Electric, Harris, Honeywell, HP, Motorola, Polycom, Raytheon, Texas Instruments, Cisco, Scientific Atlanta, and Thomson.

Many organizations do not fully verify their embedded designs for correctness and reliability. A verified design translates into higher manufacturing yields and customer satisfaction. Kozio created a special purpose OS called VTOS™ which acts as the foundation for a robust functional test suite and interactive verification environment. Combining these capabilities allow for rapid verification of correctness and reliability for embedded designs.

Design correctness entails verifying that the design is logically correct and that all parts of the design pass a robust set of functional tests. Design failures would manifest themselves in a repeatable peripheral functional test failure for memory, display, HDMI, wireless, etc.
A reliability failure can be described as only a portion of the prototype boards working leading to a lower production yield. Kozio provides an interactive environment where problems are easily debugged along with capabilities to effectively test power, clock and performance margins. Together these capabilities allow you to quickly resolve reliability failures that translate into lower manufacturing yields.

VTOS is Kozio’s special purpose OS for design verification and test. VTOS typically takes the place of an end-user OS ( e.g. Linux or Android) which is not well suited as a hardware interaction platform. VTOS provides OS services, but is architected for the purpose of direct hardware interaction. With VTOS running on the Device Under Test (DUT), you can quickly test and debug a new prototype board utilizing a robust functional test library.

VTOS can also be used in a production environment, providing for a consistent test strategy across engineering and production. VTOS can be modified with scripts to optimize for production oriented metrics such as test time versus coverage.

Kozio’s software tools can be considered part of the hardware design chain and come into play at the prototype delivery phase to facilitate board bring-up, ensure that prototype boards are operating correctly, and to verify that they adhere to design requirements. The engineer utilizes a user console to run functional tests at the click of a mouse or run specific commands. Tests can be easily looped or modified to localize problems.

Kozio provides a powerful scripting language where new tests can be created and parameters on existing tests are easily modified.

Kozio eliminates the hardware variable during software development. Firmware /Software engineers can be confident that the hardware has been verified and is operating as defined. Software engineers can use Kozio to peek and poke around the hardware with an easy to use tool.
Kozio’s built-in trace facility also provides register values and device initialization sequences to help speed up driver development and end-user OS porting.

Once the board enters production, test strategies utilized in development are easily transferred to manufacturing for test purposes. Targeted subsets of the engineering tests can be re tuned, and used on your or your contract manufacturer’s production line. For boards that fail one or more tests, detailed diagnostic information is available to help identify any necessary rework. Kozio can also be used to debug failures in the bone pile.

You can ship the same powerful diagnostics that were used for design verification and manufacturing test with each target system, to be run every time a board powers up or by user selection. End-customer problem identification, field support and return materials analysis all benefit from running the same diagnostics used throughout the entire product lifecycle.

The Verified! base package includes VTOS Builder* and Integration Workbench. Together these tools allow you to generate base level VTOS binaries (standard processor support and memory tests) for any supported processor, and communicate with them via Integration Workbench’s graphical user interface. The generated VTOS binaries include a boot manager, user accessible low-level commands to read and write registers and memory, a built-in test executive application, a test database, scripting language, and support for IP communications via SLIP (Serial Line Internet Protocol).

VTOS Builder options include peripheral device support ( e.g. display) and processor advanced functions (e.g. OMAP4). The easiest way to determine which peripheral packages are needed is to view a block diagram of your design. The peripheral blocks typically map to the optional packages. The Processor PLUS option is selected to add support for advanced buses and/or other features specific to a particular processor.

In the case that a device is not supported, Kozio offers Professional Services to create support for the device , or you have the option to use Kozio’s SDK (Software Development Kit) for in-house development. The device support or tests you create are compiled and incorporated into VTOS utilizing VTOS Builder. Kozio recommends that you license the appropriate peripherals packages to gain access to robust and fully supported tests, drivers, and example code.

Yes. Tests can be run interactively using Integration Workbench or a terminal emulator program. You may decide to run all of the tests included in the VTOS binary, by running the command "test.all". Alternatively, you might want to focus on, for example, debugging an SDRAM problem, in which case you can enter the command "test.sdram" at the interactive command prompt. You can create new test methods and assemble them into test suites, and save them for independent later use or for running multiple times in a loop.

Yes. You can create new tests interactively with any VTOS binary. Tests and test suites can be stored in Integration Workbench and run when you wish.

You can also write your own custom functions in C and integrate them into VTOS using the Verified! SDK (Software Development Kit) included as part of every base package. The SDK includes all needed libraries and header files, along with example code. You can compile your functions (using standard GNU tools) and link them into VTOS.

You can write your own custom test functions to access these chips, using the Verified! SDK which is included as part of the Verified! base package. This development kit uses the GNU compiler, linker, libraries, and source header files so that you can link your custom "C" function tests with our standard tests and generate binary images for your device. With the SDK you can create your own menu items, fully automated manufacturing tests, and custom tests using VTOS API’s, frameworks, and test primitives.

VTOS automatically allocates a memory region for your custom IC, allowing you to access all registers by default. A VTOS with the correct options also allows you to quickly transfer a binary image from a PC over your embedded system’s Ethernet or USB port, and load it into your FPGA.
Kozio Professional Services provides coaching and training on the use of the SDK, along with custom test code development.

Yes, Kozio offers Professional Services to build your VTOS and create additional device support. To create a VTOS for your system, we use a system block diagram and/or your board schematic. If your project restricts the distribution of this material, we use a 1-2 page questionnaire instead. Kozio does not require time from your engineering team in order to support your hardware, except for an occasional email question.

As you no doubt know, boundary scan and JTAG provide structural test methods, which work well for detecting assembly faults, such as opens, shorts or bridges. In essence, structural tests answer the question "are the components on this board connected as expected?" There are many situations, however, where the board can be correctly assembled, will be passed as good by structural test, and yet be faulty.

Verified!’s VTOS provides full-speed functional testing in comparison to the structural test method of boundary scan and JTAG. VTOS tests run at full processor speeds so they deliver an excellent solution for finding not just issues with functionality, but also the speed-sensitive or data-pattern-sensitive issues that you may possibly experience when accessing interfaces, buses, DDR, and memories at full operating speed.

The Verified! Licensing Agreement allows for the generated VTOS binaries to be shared with contract manufacturers so that they can run the tests and test suites you specify.

For more information on how VTOS compliments JTAG, get our technical paper on the subject at: Application Notes

Yes, of course. You can use the Verified! SDK to incorporate your standard tests into a VTOS binary. Your code will typically require some minor modifications. Kozio’s Professional Services group is available to provide coaching and training to your engineering team as necessary.
The Verified! SDK includes the Standard C library functions and APIs for thousands of function for initializing, configuring, and controlling various devices, memories, and interfaces, providing a good foundation of example material.

Not for the base level VTOS. Our customers using VTOS tell us they do not need source. Both Integration Workbench and VTOS provide a high degree of control and visibility into both the test process and execution of test commands. With each test you'll have access to all buses, memories, and bus connected devices. You can also use the built-in trace feature which allows you to display or dump test settings and test execution.

With the Verified! SDK you'll get libraries, header files, and example source code. This information supports modification of some configuration settings and rebuilding of binary applications for your custom board.

The VTOS Builder* Processor Plus and Peripherals add-on packages also include example source code, along with libraries and header files.

The processor and a serial port for the user console must be functional. If Flash or ROM is not working VTOS can execute directly out of RAM memory and test the Flash. You can also use Kozio’s Professional Services coaching service to help you set up DDR memory so you will quickly get to the VTOS command prompt. We have many customers that start out with non-working memory, and use VTOS to identify the failure cause.

You have the option to use a JTAG programmer to load a self-booting VTOS into ROM or RAM. Once VTOS is programmed into ROM or RAM, you can use it to transfer images from a PC, program any NAND or NOR flash devices, or program any programmable logic device such as EEPROMs or FPGAs. You can also use your boot loader to transfer and run VTOS from ROM or RAM.

No. VTOS provides a self-booting application that executes from either ROM or RAM. A loadable version is also provided. Here are the three image types that can be generated by VTOS Builder*:

• A self-booting application that is programmed into ROM
• A self-booting application that runs from RAM
• A bootable application that can be loaded and executed from a boot loader (Uboot, RedBoot, VxWorks, etc.)

Yes. The test methods built into VTOS send and receive packets across many different interfaces such as Ethernet, USB, IDE, SCSI, and SATA. The payload data can be altered and is validated - the actual data received is always checked against what was expected - after reception. In addition, performance characterization can be performed on supported interfaces, such as SATA.

Yes. VTOS supports a variety of tests that will stress various interfaces and controllers. When available on the processor, you can use DMA operations to provide further stress testing. All test suites can be run indefinitely to test a system during burn-in, in the environmental chamber or during design verification.

Yes, using a few very simple commands, you can execute counted loops, indefinite loops, or loop until failure testing. Using the interactive, scripted capabilities contained in every copy of VTOS, all commands or test suites can be looped, or nested in a conditional statement, even your newly created custom test suites and test commands.

Yes, VTOS can test 10/100/1000 Ethernet interfaces. It tests the entire path, in incremented steps, from the MAC, to the PHY, to the network and back. Using a variety of test commands you can quickly isolate data or control line issues, as well as PHY and network issues. For Gigabit Ethernet controllers the VTOS Builder* Networking Peripheral Package provides tests at 10/100 as well as Gigabit speeds, in order to isolate faulty gigabit control lines. VTOS test suites provide packet testing with the ability to change packet length, contents, duration, and looping. Also included is the ability to send ICMP (Ping) packets. All tests include full packet data validation.

Yes, and much more. For this issue, VTOS returns memory configuration and mapping data along with full bit error detection allowing you to locate data or address line issues. Our memory tests have discovered and helped resolve numerous memory issues that went undetected by other test methods. We have helped customers, around the world, debug memory problems in just a day or two.

Yes. VTOS can program any NOR or NAND flash device. For devices that support advanced programming features such as buffered programming, VTOS can program devices up to 3X faster than other programmers. Another benefit is that you can use your JTAG programmer to load VTOS into RAM and use it to transfer binary images over Ethernet and program them into any NAND or NOR device. This has proven to be a real time saver for some customers.

Yes. VTOS can be built as a self-booting binary that executes from the boot sector of Flash or ROM memory. VTOS-POST executes when the device is powered on, runs your test script, and then launches your boot loader. The only extra effort required is to relocate your boot loader to a new starting address in Flash memory. Kozio provides technical notes and support on how to perform this action.

The power-on self-test results obtained by VTOS-POST are stored in a memory location you specify via the POST script. Your application can read these results and act on them. The POST table is a list of error codes for all faults found during the power-on self-test. All error codes are documented in the VTOS Command.

If you can’t find information on a feature you are interested in on this site, complete the small web form below this FAQ, and someone from our Sales Engineering staff will contact you.

Some product names were changed in order to better communicate their functionality and value. Kozio has expanded from being a turnkey services oriented provider into offering a standard verification and test development platform. Turnkey solutions are still available through our Professional Services Group.

VTOS was previously known as kDiagnostics. The name was changed in order to emphasize the fact that VTOS is a special-purpose operating system, which includes a number of standard services found in other operating systems, along with a wide variety of verification and test features.

Integration Workbench was originally named Validation Assistant. The name was changed in order to emphasize the help that it provides to both hardware and software engineers during the prototype and software-hardware integration phases of a project.

vLink is the basic IP communications facility that was contained in a number of previous products and allowed them to communicate with the system under test. In speaking with customers we realized that it would be useful on its own, in situations where third party software products (such as test executives or terminal emulators) need to communicate with VTOS.

Linux and Android are multi-threaded operating systems with the benefit of isolating applications from the underlying hardware. This makes them excellent choices for running end-user applications, but they lack the direct hardware access to isolate memory problems and other hardware faults. The system stops running, but you can’t tell where or why.

In a verification and test operating system, single-threaded and direct access to the underlying hardware is paramount. VTOS is built on this basic premise without compromising many of the expected OS services. In addition, Verified! products are documented and supported specifically for this application.

Kozio provides a much broader and deeper range of tests that uncover design or assembly faults not found by other test methods. Hardware verification and test is all we do and we continue to expand our test coverage. VTOS provides a deterministic platform for testing, remote and automated capabilities, and the ability to create new test cases. Our test library is documented and supported by verification experts with knowledge of numerous microprocessors, memories, and controllers.

You are allowed under Kozio’s license terms to supply VTOS binaries you generate (or that Kozio generates for you) to your subcontractors for use in manufacturing, without royalties.

If you ship either VTOS or VTOS-POST binary copies in a product you sell to others, Kozio requires a small per copy royalty. A royalty buyout option is available that allows a one-time flat fee payment.