VTOS Tools Release 2.0.7

Version 2.0.7

Release date: 22-jul-2016

What’s New

  • VTOS Scan ADC for TI Sitara AM335x. Provides improvements to ADC channel testing.
  • VTOS DDR performance improvements for the march test.
  • VTOS DDR improvements for the tuning on QorIQ based platforms.

VTOS Tools

  • No specific changes in this release, see VTOS Tools for general product updates.

VTOS DDR

  • Issue: corrected operation of the DDR march test on QorIQ platforms.
  • Feature: Performance improvement for the DDR march test.   On high-performance QorIQ platforms (T1xxx, P4xxx, P5xxx) the march test now takes about 6 seconds per megabyte and 1.75 hours per gigabyte.  On value-performance QorIQ platforms (P1xxx, P2xxx), the march test takes 8 seconds per megabyte and 2.25 hours per gigabyte.
  • Issue: corrected a VTOS DDR crash that occurred when running the DDR tuning.
  • Feature: improved DDR tuning on QorIQ platforms to better handle boards with ECC memory.

VTOS Program

  • No specific changes in this release, see VTOS Tools for general product updates.

VTOS Scan

  • Issue: Driver updates for VTOS Scan ADC and new commands.
    • [device] [channel] ADC.RAW – Returns raw digital value from the ADC Channel. Add “.dec” after ADC.RAW to display value read in decimal format.
    • [device] [channel] ADC.CONVERT – Returns a converted value in microvolts from the ADC Channel. Add “.dec” after ADC.CONVERT to display value read in decimal format.
    • [device] ADC.DUMP – Reads a single value from all available channels and prints that value in raw digital format and microvolts.
    • [device] [channel] [count] ADC.SAMPLE – Reads [count] values from the selected channel and prints the value reads in raw digital format and microvolts.

vAccess

  • No specific changes in this release, see VTOS Tools for general product updates.
Posted in General, Hardware Interface Testing | Leave a comment

Pre-OS Hardware Testing

Kozio’s latest line of circuit board test software allows engineers to validate circuit board designs before any boot loader or operating system runs. This provides several advantages to engineering teams; including: validating all boot devices before loading and running a bulky operating system, running circuit board tests before a boot loader and OS is ported to the custom hardware, running test automatically and quickly with no constraints on the latest application release, and running hardware tests with minimal working hardware.

Kozio has been producing embedded functional test software for thirteen years. Our products are composed of three main ingredients that allow design engineers and test engineers to quickly validate custom circuit board designs.

(1) Kozio provides embedded firmware with the key feature of being able to run on any processor in a given family. The user interface provides the board specific information needed to customize a test sequence to a custom circuit board. No porting, code modification, and builds are required to start using Kozio firmware on your custom circuit board design.

(2) Kozio provides a user interface that simplifies and automates the process of creating new test configurations for custom circuit boards. Features such as “Scan and Add” automatically scan a “golden” board and add device tests for each device discovered. Features such as interpreted scripting and multiple low-level commands make it easy to create, test, and build custom sequences without compiling and power cycling the target device.

(3) Kozio integrates with various hardware vendors and tools to ease the hassle of loading firmware onto a circuit board. Kozio works with JTAG and Boundary Scan providers to automate the task of loading VTOS firmware onto a circuit board.

vtos-scan-banner

VTOS Scan™ is a product group name for our software solution used to test circuit board electronics before the boot loader or operating system run. This product is available in several models. Click on any model to read more about that particular product line.

VTOS Scan Plus (for Flash, MMC, I2C, etc.)
VTOS Scan USB (for USB enumeration testing)
VTOS Scan Ethernet (for Ethernet packet testing)
VTOS Scan PCI (for PCI Express bus/device testing)
VTOS Scan ADC (for Analog to Digital testing)

The solution uses firmware running on your circuit board design to functionally test the bus and validate connected devices. A graphical user interface simplifies creating new test sequences. Use a “golden” board and many tests are automatically created using a discovery process. Export the configuration for automated manufacturing test using the test executive of your choice – even custom ones.

If you would like to try a VTOS Scan product out, please email sales@kozio.com and we can send an evaluation license. Everything is downloaded and activated over the internet.

If you have other circuit board testing needs, please contact us.

Posted in Hardware Interface Testing | Leave a comment

Introducing VTOS Scan Plus

VTOS Scan Plus is a new addition to Kozio’s line of embedded software tools for circuit board testing. VTOS Scan Plus provides tests for a number of hardware interfaces allowing you to validate a circuit board design before the boot loader or OS run. VTOS Scan Plus includes tests and commands for GPIO, I2C, SPI, UART, Ethernet PHY, NOR Flash, SD/MMC, and SDIO.

VTOS Scan Plus provides functional tests that run from the processor. The VTOS Scan firmware is loaded and runs on any circuit board device without porting or modification. A graphical user interface is provided for test configuration. All test configuration data can be exported for automated testing of one or more devices in parallel.

The VTOS Scan product line provides the ability to test your hardware with no development effort, a very small learning curve, and the ability to test before the boot loader or operating system are running. All products are designed for automated testing with a small integration effort.

Here is a diagram of the setup used for this example.

vtos-scan-plus-demo

Here is a photograph of VTOS Scan Plus running on the SABRE Lite reference board.

vtos-scan-sabrelite-sm

The VTOS Scan Plus firmware can be loaded onto your target device using a JTAG interface, or other interfaces supported by that processor. For example, Kozio provides an example configuration file for the SABRE Lite reference board with a NXP i.MX6 Quad processor. The VTOS Scan Plus firmware can be loaded onto the i.MX6 using the USB interface and the SB Loader tool (a free tool from NXP and Boundary Devices). Kozio provides an image file that can be loaded onto any i.MX6 board design without modification. The VTOS Scan Plus firmware boots nearly instantaneously.

vtos-scan-plus-sbloader

The VTOS Scan GUI is used to create a new VTOS Scan Plus test configuration.

With the firmware loaded and running, the VTOS Scan GUI is used for creating your desired test sequence. VTOS Scan Plus provides a number of tests including: PHY Exists and PHY Verify Test, BlueTooth (BT) Exists and BT Verify tests, I2C Device Exists and I2C Device Verify tests, SD/MMC Device Exists and SD/MMC Device Verify tests, NOR Flash Device Exists and NOR Flash Device Verify tests, SPI Device Exists and SPI Device Verify tests, UART Device Exists, Verify, and Loopback tests, and GPIO tests.

The very first step is to load the VTOS Scan firmware onto the target and then use the Connections button in the tool bar to establish a connection. For this example, we used a serial connection to the target board. Click on Connections and then select the options: VTOS Scan Plus, i.MX6, Serial, and the discovered COM port.

If you load and run the VTOS Scan Firmware after you have established a connection in the GUI, you will see the VTOS Scan firmware boot messages, which starts with “DUT ready”.

vtos-scan-plus-1

For the i.MX6 processor we are required to include and run a pin configuration, or pin mux, file. A pin configuration file can be automatically imported from an NXP pin mux file, which is created using the NXP pin mux utility. Once the pin mux is configured, a number of busses can be automatically scanned. Use the right-mouse menu option to “Run Scan”. This command will attempt to discover all devices on the interface. You can also use additional menu options to scan and automatically add tests.

vtos-scan-plus-2

For certain devices, it may be required to write to memory or toggle a GPIO line. All VTOS Scan tools provide low-levels commands that can be added to any test sequence. Every node in the configuration tree has a place to add Setup Actions and Cleanup Actions. Click on a node in the configuration tree, then click on the setup or cleanup actions to expose a button (on the far right of the GUI) which will launch the Configure Actions dialogue box. You use this dialogue to add any and all special commands as needed for your custom board configuration.

vtos-scan-plus-4

After you have added all desired test cases, you can use the tool bar Run button to run the entire test sequence from top to bottom.

vtos-scan-plus-3

This example configuration was saved and is available when you install the Kozio VTOS Tools package. All example configuration files are stored under the “boards” folder and then the appropriate processor folder.

As a next step, click on File / Export to export this configuration to a Kozio script file or to an NI TestStand sequence (*.seq) file. More export options will be added as we work with new test executives. The exported test configuration is used for automatic testing during long regression test runs or during manufacturing test.

Here are screen shots of running the two exported files. There are two screen shots of using Kozio’s free vAccessTest.exe and one of using NI’s TestStand.

vtos-scan-plus-auto-1vtos-scan-plus-auto-2

vtos-scan-plus-teststand

If you would like to try VTOS Scan Plus out, please email sales@kozio.com and we can send an evaluation license. Everything is downloaded and activated over the internet.

If you have other circuit board testing needs, please contact us.

Posted in Hardware Interface Testing | Leave a comment

Introducing VTOS Scan USB

VTOS Scan USB is a new addition to Kozio’s line of embedded software tools for USB enumeration and functional testing of USB interfaces and connected devices. This product provides firmware that is loaded and run on your custom circuit board device without porting or modification. A graphical user interface is provided for test configuration. All test configuration data can be exported for automated testing of one or more devices in parallel.

The VTOS Scan product line provides the ability to test your hardware with no development effort, a very small learning curve, and the ability to test before the boot loader or operating system are running. All products are designed for automated testing with a small integration effort.

The VTOS Scan USB firmware can be loaded onto your target device using a JTAG interface, or other interfaces supported by that processor. For example, Kozio provides an example configuration that runs on the BeagleBone Black reference board, sporting a TI Sitara AM3358 processor. The VTOS Scan USB firmware can be loaded onto that device using an SD Card, UART, or JTAG programmer. The firmware image is very small and loads in seconds and boots nearly instantaneously.

With the firmware loaded and running, the VTOS Scan GUI is used for creating your desired test sequence. VTOS Scan USB provides two built-in tests: 1) a test to enumerate the USB interface and communicate with a USB device to verify it exists, and 2) a test to enumerate the USB interface and communicate with a USB device to verify that vendor id and product id match, as well as verifying the port speed.

Here is an example of running VTOS Scan USB on a BeagleBlack reference board. The Kozio flash drive is used for this test case so that a device can be discovered and verified.

vtos-scan-usb-bbb

The VTOS Scan GUI is used to create a new USB test configuration. Click on the USB1 node in the configuration tree and use the right-mouse menu option to Run Scan. The available menu options for the USB1 node also include the ability to Run Scan and automatically add tests for all discovered devices. In our case below, a single USB device (the Kozio flash drive) is discovered and we automatically added two tests for that device.

vtos-scan-usb-1

This example configuration was saved and is available when you install the Kozio VTOS Tools package. Click on the Run button in the tool bar to run all configured tests.

vtos-scan-usb-2

As a next step, click on File / Export to export this configuration to a Kozio script file or to an NI TestStand sequence (*.seq) file. More export options will be added as we work with new test executives. The exported test configuration is used for automatic testing during long regression test runs or during manufacturing test.

In addition, VTOS Scan USB provides several low-level commands that can be used for additional test setup and troubleshooting. Our products are very flexible and use a scripting interface to allow you to create custom test commands or interactively troubleshoot hardware.

vtos-scan-usb-3

If you would like to try VTOS Scan USB out, please email sales@kozio.com and we can send an evaluation license. Everything is downloaded and activated over the internet.

If you have other circuit board testing needs, please contact us.

Posted in Hardware Interface Testing | Leave a comment

Introducing VTOS Scan ADC

VTOS Scan ADC is a new addition to Kozio’s line of embedded software tools for functional testing of analog-to-digital converter (ADC) channels. This product provides firmware that is loaded and run on your custom circuit board device without porting or modification. A graphical user interface is provided for test configuration. All test configuration data can be exported for automated testing of one or more devices in parallel.

The VTOS Scan product line provides the ability to test your hardware with no development effort, a very small learning curve, and the ability to test before the boot loader or operating system are running. All products are designed for automated testing with a small integration effort.

The VTOS Scan ADC firmware can be loaded onto your target device using a JTAG interface, or other interfaces supported by that processor. For example, Kozio provides an example configuration that runs on the BeagleBone Black reference board, sporting a TI Sitara AM3358 processor. The VTOS Scan ADC firmware can be loaded onto that device using an SD Card, UART, or JTAG programmer. The firmware image is very small and loads in seconds and boots nearly instantaneously.

With the firmware loaded and running, the VTOS Scan GUI is used for creating your desired test sequence. VTOS Scan ADC provides three built-in tests: 1) a test to read a channel value and compare it against a user-specified value, 2) a test to read a channel value and compare it against a user-specified range, and 3) a test to sample N channel values and compare all read values against a user-specified range.

vtos-scan-adc-1

In addition, VTOS Scan ADC provides several low-level commands that can be used for additional test setup and troubleshooting. Our products are very flexible and use a scripting interface to allow you to create custom test commands or interactively troubleshoot hardware.

vtos-scan-adc-2

As a next step, click on File / Export to export this configuration to a Kozio script file or to an NI TestStand sequence (*.seq) file. More export options will be added as we work with new test executives. The exported test configuration is used for automatic testing during long regression test runs or during manufacturing test.

If you would like to try VTOS Scan ADC out, please email sales@kozio.com and we can send an evaluation license. Everything is downloaded and activated over the internet.

If you have other circuit board testing needs, please contact us.

Posted in Hardware Interface Testing | Leave a comment

VTOS Tools Release 2.0.6

Version 2.0.6

Release date: 24-jun-2016

What’s New

  • VTOS Scan USB for TI Sitara AM335x. USB device enumeration and validation.
  • VTOS Scan ADC for TI Sitara AM335x. ADC channel testing.
  • Updates to VTOS Tool Command Reference.

VTOS Tools

  • Issue: Corrected the I/O exception handling when a Script File is not found during the loading of a configuration file.

VTOS DDR

  • No specific changes in this release, see VTOS Tools for general product updates.

VTOS Program

  • No specific changes in this release, see VTOS Tools for general product updates.

VTOS Scan

  • Feature: Added VTOS Scan USB for Sitara AM335x. This feature includes USB discovery testing with automatic adding of Device Exists and Device Verify tests.
    • Errata: There is a known issue trying to discover devices through a USB hub.
  • Feature: Added VTOS Scan ADC for Sitara AM335x. This feature includes three tests that can be performed on any and all ADC channels. The current list of tests included are:  ADC Compare Value Test (compares a user-specified value against a value read from the channel for an exact match), ADC Compare Range Test (compares a user-specified value against a value read from the channel to ensure it is within a desired range), and ADC Sample Values Test (compares a user-specified value against multiple values read from the channel to ensure that all sampled values are within a desired range).
    • Errata: Need to add ADC commands to the VTOS Tools Command Reference document.
    • Notes: Additional capabilities and control options are possible. Please provide feedback on desired features, such as sampling rates and capture modes.

vAccess

  • No specific changes in this release, see VTOS Tools for general product updates.
Posted in General, Hardware Interface Testing | Leave a comment

VTOS Tools Release 2.0.5

Version 2.0.5

Release date: 13-jun-2016

What’s New

  • VTOS Scan Ethernet for QorIQ T1xxx. This includes DPAA support and ethernet packet testing.
  • VTOS Scan Plus for TI Sitara AM335x.
  • Kozio CCS Tool. This tool attempts to find an optional JTAG clock setting when working with VTOS Tools and a CodeWarrior TAP (JTAG probe). See http://www.kozio.com/user-manuals for details.

VTOS Tools

  • Issue: Corrected the storing of the Scripts / Custom Command into the configuration file and now allow the user to type in any command.
  • Feature: Additional enhancements for returning to previous folder with browsing for files.
  • Issue: The Board Initialization file and DDR Initialization file are only executed when Connecting, never when executing a Run command.
  • Feature: Allow ENV variables when typing in full file paths.
  • Feature: For those products that use DDR memory for execution, there is a new Import from VTOS DDR button on the Edit DDR Initialization File dialogue.
  • Issue: Corrected a pin mux file import issue when handling Sitara AM335x pin configuration files.

VTOS DDR

  • Issue: fixed thread exception when DDR Configuration Setting was set to “Automatic” on Kinetis K6x/K7x projects.
  • Feature: Added example Kinetis K6x DDR project file for the TWR-K70F120M platform from NXP.
  • Feature: Added new DDR Tuning command for i.MX6 designs to find the best read latency/write latency setting.
  • Issue: Corrected the configuration of Zynq board designs that use a 16-bit wide DDR data bus.
  • Feature: Added DDR4 register values for QorIQ T1xxx designs.
  • Issue: Corrected the handling of importing #OSC.CLOCK, #ODS.FULL_STRENGTH, and #ODS.REDUCED_STRENGTH from Kozio script files.
  • Feature: Removed the DDR March Test from the list of interactive tests. This test command is still available to Export or to run through the Run Command option.

VTOS Program

  • No specific changes in this release, see VTOS Tools for general product updates.

VTOS Scan

  • Feature: Added DDR Initialization node for QorIQ T1xxx processors for VTOS Scan Ethernet.  Only MII, GMII, and RGMII interface types are supported in this release.
  • Feature: Added Scan Plus for Sitara AM335x, which includes testing for GPIO, I2C, SPI, UART, Ethernet PHY, Bluetooth, SD/MMC.

vAccess

  • No specific changes in this release, see VTOS Tools for general product updates.
Posted in General | Leave a comment

Multi-Board Programming with VTOS Tools™

Introduction

It is often desirable when manufacturing circuit boards to program several boards in parallel. This entry describes a process for programming multiple circuit boards in parallel using Kozio’s VTOS Tools™. The goal of this simple example is to program two different files into NOR Flash on multiple circuit boards, with the programming process running independently for each unique circuit board. The first file programmed will vary for each circuit board and the second file will remain the same for all circuit boards. Using VTOS Program™, you can program as many files as you like, this examples only uses two.

Process Overview

The configuration used for this example runs on a PC which is connected to a USB hub. One circuit board is connected through JTAG to a CodeWarrior TAP. That TAP is connected to the PC using a USB connection. This is identified as Fixture 1. A second identical setup is configured for a second circuit board and identified as Fixture 2.

kozio-example-configuration

This example uses Kozio’s freely available tool vAccessTest.exe to execute a programming sequence. The call flow is to use a batch file (test.bat) to launch two separate command windows. Each command window in turn runs a batch file (dut1_test.bat and dut2_test.bat) that programs a circuit board attached to its fixture.

There are several possible ways of creating a programming test sequence to program unique data for a circuit board. Unique data in this example is a board’s serial number and two MAC addresses. Here are a couple examples:

  • One solution is to store the unique data in a file and then program that file to a specified location in Flash memory. This solution requires that the data file always have the same file name so that the programming script never changes. This method produces a new serial number and overwrites the same data file for each new circuit board.
  • Another solution is to create a unique file using a separate process and then generate a programming script file on the fly. This solution provides a way to change the file name of the data file being programmed and capture that information in a log. The process flow is essentially the same for each new circuit board, except the call to program the data file changes each time with the new file name.

For this example, we will demonstrate the first method.

Looking at the flow of the DUT batch file more closely, we will see that the process initializes variables for a serial number and two MAC addresses. A call is then made to another batch file (create-board-sn-file.bat) to create a unique text file using the current serial number and MAC addresses. The name of text file created is always the same, but stored in a separate folder for DUT1 and DUT2. In a real production environment, these values would typically be pulled from a database. Once the unique file is created, a call is made to vAccessTest.exe specifying the fixture number and script file to run. This step performs the steps needed to erase the flash and then program both files.

The call to vAccessTest actually requires several parameters.

  • The first parameter is an INI file that defines one or more fixtures along with connection data. This INI file is created and modified using the VTOS Program GUI. Simply launch VTOS Program and click on Connections to modify this file. The Connections dialogue allows you to create one or more connections. These connections are numbered from top to bottom starting at one (1). The first connection is the information needed for Fixture 1, the second connection is the information needed for Fixture 2, etc.
  • The second parameter passed to vAccessTest is the numeric fixture number.
  • The third parameter passed to vAccessTest is the script file that will be executed to program both files into Flash memory. This script file (multi-board-programming.ksc) is also created with the VTOS Program GUI. Launch VTOS Program and create a new configuration, add a Flash part, add programming operations, and then export the file to a Kozio script file. The script produced for this example erases two separate areas of the Flash memory and runs a Blank Test to verify that they are erased. The data file is then programmed and a call is made to dump out the contents of Flash memory so that a record of the programmed data is logged. A one (1) MiB file is then programmed and a Checksum Test is used to verify the programming. The second file is used to simulate programming the same application image to all circuit boards.

kozio-mbp-vtos-program-gui-1kozio-mbp-vtos-program-gui-2

This method was executed for 6 loops and the output files are provided as examples. The process is started from one cmd.exe window by calling “test.bat 6”.

kozio-mbp-desktop

The process creates a unique serial number file (dut1-sn.txt and dut2-sn.txt) in separate DUT folders. Here is a screen capture of one version of this file in a hex editor. Since the programming sequence dumps the bytes in hex and ASCII, its also good to see them in a hex editor.

kozio-mbp-hex-editor

The output for each fixture is stored as a text file in the same folder that contains the script file. Here is an example of the output for DUT1: multi-board-programming.txt. Below are a couple screen shots of an output file.

kozio-mbp-output-1 kozio-mbp-output-2

Summary

Programming multiple circuit boards is fairly straightforward with VTOS Program, vAccess, and vAccessTest. This example provides the files and a description of those files as one example of programming two files into Flash memory and doing so in parallel. If you would like see a live demonstration of this process, or receive further information, please contact us.

Posted in In-System Device Programming, Industry Trends, Test Automation | Leave a comment

VTOS Tools Release 2.0.4

VTOS Tools Release

Version 2.0.4

What’s New

  • VTOS DDR updates for AM437x and LPDDR2 memories.

VTOS Tools

  • Issue: Corrected an issue when activating multiple node-locked activation keys. Before this fix, it was possible that the automatically created license file became corrupted with extra characters. The result was that although a license file was created, the user could not check out the license.

  • Feature: All user interfaces were updated to automatically switch to Config Mode when you select a node in the configuration tree. The only exceptions are the Configuration and Board nodes, which do not automatically switch.

  • Issue: Added checking to require that a valid CodeWarrior TAP Type is selected.

  • Feature: Added an option to Cancel when prompted with unsaved modification.

  • Feature: New tips are displayed for configuration nodes when the mouse hovers over that node.

  • Issue:  Corrected the Scan feature for CodeWarrior TAP connections  to recall all previously entered TAP Ids. Clicking on the Scan button will recall previously entered values.

  • Issue: Enhanced the handling of connection errors when using DDR memory.

  • Issue: Corrected FIXTURE_IN_USE error when running vAccessTest and any VTOS Tools GUI.

  • Feature: New feature to recall previous directories when opening, saving, or selecting files.

VTOS DDR

  • Feature: The DDR Exported Tests node was enhanced to allow adding all available tests. For example, you can now export the Walk 0 Test, Walk 1 Test, etc.

  • Feature: Added default board specific values for DDR PHY settings for LPDDR2 memories on Sitara AM437 boards.

  • Issue: “Update DDR Settings from Tuning Results” was not working for Sitara AM335 projects.

  • Issue: Change the link address for Sitara AM437 firmware for compatibility with loading firmware images over a serial port.

VTOS Program

  • No specific changes in this release, see VTOS Tools for general product updates.

VTOS Scan

  • No specific changes in this release, see VTOS Tools for general product updates.

vAccess

  • Error code changes:

    • VACCESS_FILE_ERROR was renamed to VACCESS_FW_FILE_ERROR

    • New VACCESS_FATAL_DUT_ERROR (25)

    • New VACCESS_TEST_FATAL (105)

Kozio, Inc.
202 Main Street, Suite 2
Longmont, CO 80501 USA
www.kozio.com
info@kozio.com

If you no longer wish to receive these emails, Unsubscribe here.

© 2003-2016 Kozio, Inc. All rights reserved.

Posted in General | Leave a comment

VTOS Tools Release 2.0.3

VTOS Tools Release

Hello everyone. We are starting a new process to keep you informed about Kozio’s product releases. We are sending this update to all current customers and partners. Since this is a new process, the release notes for 2.0.0 through 2.0.3 are included. The most recent release is first, followed by earlier releases.

Version 2.0.3

Release date: 09-may-2016

What’s New

  • VTOS Scan Plus – New Bluetooth (BT) group with Controller Exists and Controller Verify tests.
  • VTOS Program – New Read To File and Image Blank Test operations.

VTOS Tools

  • Feature: New connection validation to ensure tool, processor, configuration, and connection data all line up.
  • A number of Actions were updated to use 32-bits and also use pull-downs for value selection. Actions updated are: GPIO Write, I2C Read, I2C Write, I2C Dump, SDMMC Set Width, and UART Configure.

VTOS DDR

  • Update to NXP PowerQUICC II MPC82xx DDR Test support.
  • Issue: Resolved an issue on Kinetis K6x/K7x architectures where the DDR controller was not getting enabled.  This caused all memory tests to fail even when using known good DDR controller settings.
  • Issue: fixed the configured drive strength for DDR I/O pads on the Kinetis K6x/K7x to match the DDR type.
  • Enhancement: DDR tuning for QorIQ based architectures (include P1xxx, P2xxx, P5xxx, and T1xxx) now tune the WRLVL_START parameter separately for each configured byte lane.
  • Added DDR test configuration file for the T1023 RDB reference board.

VTOS Program

  • New Read To File feature. This new program operation will read from a flash device and write the contents to a file on your personal computer. Specify a device to read from, a starting offset, a byte count, and a file to write the contents to. The previous file contents will be overwritten without prompting.  This feature is only supported when using the Codewarrior TAP JTAG connection type.
  • New Image Blank Test feature. This new program operation will read from a flash device and verify that all bytes are blank. The flash driver takes into account the blank value based on the device type. You specify the flash device, a starting offset, and a byte count.
  • Issue: Resolved an issue with Programming from Device to Device.

VTOS Scan

  • For VTOS Scan Plus, new Bluetooth (BT) group and Controller Exists and Controller Verify tests.
  • NXP PowerQUICC II MPC82xx Scan Base support.

vAccess

  • No changes in this release.

Version 2.0.2

Release date: 21-apr-2016

What’s New

  • NXP PowerQUICC II MPC82xx DDR Test support.
  • New VTOS Tools Command Reference document. Check under Start / All Programs / Kozio.
  • Updated User Manuals for all products.

VTOS Tools

  • Issue: Corrected the generation of NI TestStand Sequence files to match the new vAccess API prototypes for ConnectVTOS, ExecuteCommand(), and DisconnectVTOS().
  • Issue: Corrected exception when trying to write connections and %KOZIO_HOME% is not defined.

VTOS DDR

  • New VTOS DDR 2.0 User Manual.
  • NXP PowerQUICC II MPC82xx DDR Test support.
  • SDRAM and DDR4 memory part support.
  • New memory part added for Micron SDRAM MT48LC16M16A2-75.
  • New DDR Test and DDR Tune configuration files for P1025TWR and P1024RDB.
  • Issue: Corrected exception with VTOS DDR when no config file is loaded.

VTOS Program

  • Updated VTOS Program User Manual.
  • Added example project for NXP MPC8360EA MDS-PB reference board. This includes DDR settings and program operations to erase, program, and verify.
  • Issue: corrected gross timeout errors for AMD compatible flash devices when multiple flash devices are connected to the same local bus chip select.
  • Added RCW Override support for MPX83xx. Only the first two RCW words are used, the first (or top-most) is for LOW and the second word is for HIGH.

VTOS Scan

  • Updated VTOS Scan User Manual.

vAccess

  • Updated vAccess User Manual.
  • Released a new vAccessTest.exe. This 2.0.2 release has a new icon and makes use of the console callback so that all console data is printed to the screen in real time.
  • Updated vAccess.h to include a typedef for the RegisterConsoleCallback function.
  • Issue: Corrected VACCESS_FIXTURE_IN_USE_ERROR issue.
  • Issue: Corrected an issue with dropped console characters if the DUT firmware generated too much console data in a single command.

Version 2.0.1

Release date: 31-mar-2016

What’s New

  • New VTOS Program support for the NXP PowerQUICC II Pro MPC83xx  architecture.
  • New support for using DDR memory with VTOS Program.
  • New programming support for devices using the Intel command set.

 

VTOS Tools

  • New DDR Initialization File configuration node allows the user to enter board specific DDR settings. This new configuration item is made available for support SoCs only.

VTOS DDR

  • No changes in this release.

VTOS Program

  • Added support for board designs using the NXP PowerQUICC II Pro MPC83xx  architecture.
  • Added support for DDR initialization using a NXP CodeWarrior TAP JTAG probe.
  • Example configuration provided for the MPC8347XE-RDB, including working DDR settings.
  • Updated VTOS Program User Manual.

VTOS Scan

  • No changes in this release.

vAccess

  • No changes in this release.

Version 2.0.0

Release date: 28-mar-2016

What’s New

  • New graphical user interface for the VTOS DDR application.  This interface replaces the text-based user interface provided in previous releases.
  • Major update to licensing registration and activation.  See the Kozio License Instructions (AN134) document for instructions on activating licenses.  This document is installed with VTOS Tools. This release requires a new license file. If you are under maintenance, Kozio will email you a new license file without cost. Please email sales@kozio.com to obtain a new license.
  • New support for the QorIQ T1xxx architecture for the VTOS DDR Tune and VTOS Scan Plus products.
  • New handling for custom commands and custom scripts – tutorial included.

VTOS Tools

  • This release has includes major restructuring of files. It is recommended that you uninstall you last release and resinstall this version. All firmware files have been moved to a new sub-folder labeled fw.
  • New licensing capabilities have been added through a Licensing main menu item.
  • A new boards folder is used to track processor specific reference board configuration files. These files provide good examples of various configuration options.
  • A new Scripts node has been added allowing the user to add custom commands to their configuration. A scripts tutorial and scripts template is installed with all VTOS Tools. See %KOZIO_HOME%\examples.

VTOS DDR

  • New graphical interface
  • Added support for the QorIQ T1xxx architecture from NXP.  Only DDR3 memories are supported in this release.  There is not yet support for DDR4 memories.
  • Improved tuning of DDR settings for QorIQ architectures.  Tuning of the WRLVL_START parameter is now performed separately for each byte lane.
  • Bugfix for Sitara AM335: the test extent was not getting set correctly for the DDR Full Byte and DDR Full Word tests.  This resulted in these individual tests failing on the Sitara AM335 architecture only.

VTOS Program

  • No changes in this release

VTOS Scan

  • VTOS ScanPlus support added for the QorIQ T1xxx processor family.  Supported interfaces include local bus, Ethernet PHY, GPIO, I2C, NOR Flash, SD/MMC, SPI (including serial Flash), and UART.

vAccess

  • Improved command timeout detection for a non-responsive DUT (device under test).
  • New API function RegisterConsoleCallback() for registering a callback that handles console data (output messages produced by the firmware).
  • New vAccess error codes:
    • VACCESS_USAGE_ERROR
    • VACCESS_FILE_ERROR
    • VACCESS_BUFFER_ERROR
    • VACCESS_DEBUG_LOG_MUTEX_ERROR
    • VACCESS_DEBUG_LOG_FILE_ERROR

Kozio, Inc.
202 Main Street, Suite 2
Longmont, CO 80501 USA
www.kozio.com
info@kozio.com

If you no longer wish to receive these emails, simply response with Unsubscribe in the body of your  email.

© 2016 Kozio, Inc. All rights reserved.

Posted in General | Leave a comment