VTOS Scan™ User Manual
Contents
1. and other tools To install the software run the latest VTOS Tools installer The installer creates a program icon for launching the software under your Windows Start menu and places an icon on your desktop It also installs software resources and DUT firmware to a home directory in your User Profile directory See Understanding the VTOS Scan Home Directory for further details 3 VTOS Scan Icon Configuring the Software The first time you launch VTOS Scan it will guide you through a couple steps to configure the software for your system Installing a License VTOS Scan software requires a valid license for full activation and for communications with a target device A single license enables one instance of the software to be connected to a target for a specific embedded system architecture Contact sales kozio com to obtain a license for your use To install a license launch VTOS Scan From the File menu click Install License Use the file selection dialog to select your license file VTOS Scan will install and validate the selected license Creating a New Configuration VTOS Scan requires a board configuration which is used to store board initialization information pin mux information device test information and command actions You must create a new configuration in order to store device test information A different configuration file is created for each processor and option selection Available options include creating2. Writes a single character form the UART specified and display the value if selected UART PutC Writes a single character to the UART specified UART Writestring Write string to the UART specified Understanding Device Tests UART GetC VTOS Scan provides a number of device tests for all supported device types You can learn more about individual device tests in this section The list of tests available for adding to your test sequence varies based on your chosen processor architecture and VTOS Scan option Below is a list of all possible test some of which may not be available for your current configuration Device Test Description Ethernet PHY Exists Test Execute a test to verify that the specified Ethernet PHY can be accessed correctly proving that it exists Ethernet PHY Verify Test Execute a test to verify that the specified Ethernet PHY can be accessed and its identification information matches what the user 6 Copyright Kozio Inc 2015 18 b XKOZIO VTOS Scan User Manual pee OU Loopback internally in the Ethernet controller or MAC Media Access Control Tests the internal operation of the Ethernet controller and does not exercise any signaling on the board Loopback internally at the Ethernet PHY Tests the MII data path connection between the Ethernet controller and the Ethernet PHY Loopback externally using a loopback plug Tests the full data path including the Ethernet controller Ethe
3. User Manual v Click on the desired channel node Use the right mouse pop up menu option to select one of the available Scan amp Add menu options You must be connected to a target in order to use this option successfully This option runs a scan command on the embedded device and uses the results to automatically add discovered devices 0 I2C Group Bie 01 Add Device Exists Test H 50 Verify Test 6 UART Run Run Scan Run Scan amp Add Device Exists Test Run Scan amp Add Verify Test Select an option and a scan is performed and a new device test is added for all discovered devices Click on one of the devices added and click on the Config Mode tab to edit the properties of that device test View Options Use the View menu options to expand or collapse the configuration tree view Expand All fully expands the configuration tree view Expand All With Children expands all nodes that have devices tests or operations Collapse All fully collapses the configuration tree view Configuring Connections Use the Configure Connections dialog to configure parameters required for the Run Mode and to specify target connection information Obtain access to this dialog by selecting the tool bar Connections button 0c or the File Connections menu item M Configure Connection Configure and choose your target connections Processor Connection Settings GenQP5ox CodeWa
4. MMC Device Exists Test SDMMC 0x44 0001 0 SD MMC Verify Test SDMMC 0x44 0x00D1 SD MMC Device Exists Test SDMMC 0x45 0x00D1 lt 6 SD MMC Verify Test SDMMC 0x74 0x4A45 File Tools View Connections PI Connect Run HM Disconnect Status o GPIO7 I2C Group Ici 9 I2C Device Exists Test Address 0xDE 20 Verify Test Address 0xDE lt Add Test o 2 e 3 SPI Group SPI SPIFlash Device Exists Test SPI Flash Verify Test SPI Device Exists Test lt Add Tes H SPI2 H SPI3 SPM B SPB gt gt Ethernet PHY Group E UARTI UART2 E UART3 UART4 E UARTS J Ethernet PHY Group f UARTI UART2 H UART3 H UART4 UART5 SD MMC SDIO Group 3i uSDHC1 dj uSDHC2 J uSDHC3 SD MMC Checksum Test 100 lt Add Test 5 uSDHC4 9 SD MMC Checksum Test 100 i Add Test Current configuration C Users Kozio VTOS_Scan imx6 sabre lite demo xml 6 Copyright Kozio Inc 2015 b IKOZIO VTOS Scan User Manual v Title Bar The title bar runs across the top of the screen It displays the product name and revision Main Menu The main menu runs horizontally below the title bar Main menu items are displayed with their hot key shown to the right of the item Tool Bar The tool bar is just below the main menu and provides several single click s
5. Scan Actions VTOS Scan Actions expose the commands that are provided through the VTOS Scan firmware and can be executed during a test sequence These actions were designed to allow the addition of special configuration actions required on a per device basis If you have an I2C device that requires a GPIO signal to be driven high before use or requires a register write before use you can add new actions before or after a group or device test Actions can also be used to create troubleshooting steps or special tasks required during regression or production testing 6 Copyright Kozio Inc 2015 15 44 IKOZIO VTOS Scan M User Manual v Tip If a particular list of actions gets too long to easily maintain through the VTOS Scan GUI you can also store you list of actions in a script file and use the Run Command to include and execute your unique set of actions Action Types Two types of actions are provided Setup Actions that are executed before a group or device test and Cleanup Actions that are executed after a group or device test Every node in the configuration tree except the Configuration and Board nodes have Setup Actions and Cleanup Actions Tip A brief view of the list of actions added is visible when you select a node and view the Config Mode panel Accessing Actions Actions are added deleted or modified through the Configure Actions dialog Click on the desired node in the configuration tree and then click on the Conf
6. can load directly into NI s TestStand File Tools 0 fe New Ctri N P Run Bl Disconnect Status Done Open Ctrl O Save 5 Save As Export ld Kozio Script File T Settings NI TestStand Sequence EJ Exit Alt F4 6 Copyright Kozio Inc 2015 24 b XKOZIO VTOS Scan User Manual v Note Once you have your new sequence file loaded into TestStand each new export will cause TestStand to prompt you that the file has changed Running VTOS Scan and TestStand side by side provides a very efficient test development environment Contact Information For technical support questions please email support kozio com For sales or other information Kozio Inc 1 303 776 1356 x1 sales kozio com www kozio com About Kozio Inc Kozio Inc is a software technology company focused on providing superior embedded tools solving a variety of challenges during the design production and support of embedded devices With its wide range of embedded tools Kozio offers solutions to aerospace automotive consumer industrial military medical networking and wireless markets Kozio has been crafting embedded software since 2003 and has served the needs of thousands of engineers working for hundreds of companies from the smallest to the largest Kozio s line of embedded tools include everything you need to configure test and tune DDR memory identify interconnect faults and component placement problems on your printed ci
7. test configurations for Base GPIO I2C SPI UART Ethernet PCI CAN and USB To create a new configuration select File then New from the main menu Tip You can use Ctrl N to launch the Product Selector and create a new board configuration 6 Copyright Kozio Inc 2015 5 VTOS Scan User Manual Option Base Ethernet PCI USB 2 0 Device USB 2 0 Host Notes ForSitara AM335x 5005 supportis included for GPIO I2C SPI and UART Select a processor and option based on your processor type 4 KOZIO v Product Selector Sitara AM3359 Description Create tests and special action commands for working with GPIO I2C SPI and UART controllers and devices From the Product Selector dialog choose a Processor The available options will vary based on those options released for that processor A description is presented along with notes particular to that option for the processor selected Click on OK to create a new configuration Understanding the Main Screen The main screen has nine regions title bar main menu tool bar status bar configuration tree config mode panel x run mode panel device button bar and current configuration data Config Mode RunMode 000000 SDMMC 0x44 0x00D1 0x03 0x5344 15523840 lt Add Actions gt lt Add Actions gt Name Manufacturer Id OEM Id Capacity Setup Actions Cleanup Actions Name Name of the selected item f SD
8. the entire test sequence from top to bottom Run e Board Run everything o Click on the Board node and use the right mouse Run option This will run the entire test sequence since it runs the Board node and all of its child nodes e Pin Configuration Run only the pin mux file o Click on the Pin Configuration node and use the right mouse Run option This will run the Pin Configuration setup actions the pin mux file and then the Pin Configuration cleanup actions e SOC Run the SOC and all of its children o Click on the SOC node and use the right mouse Run option This will run the SOC setup options run all SOC child nodes and then the SOC cleanup actions e Group Run a group and all of its children o Click on any one of the bus group nodes and use the right mouse Run option This will run the group s setup options run all of the group s child nodes and then the group s cleanup actions e Channel Run a group s channel and all of its children o Click on any one of the channel nodes and use the right mouse Run option This will run the channel s setup options run all of the channel s child nodes and then the channel s cleanup actions 6 Copyright Kozio Inc 2015 2d 44 KOZIO VTOS Scan User Manual Ww 6 Device Test Run a single device test o Click on any one of the device tests and use the right mouse Run option This will run the device test setup options run the device test and then the device test cleanup act
9. Inc 2015 44 XKOZIO VTOS Scan User Manual v This dialogue varies based on the Connection type chosen For a CodeWarrior connection you will need to specify a TAP Identifier Select your TAP Type from the pull down and enter your TAP Identifier You can also enter the fully qualified TAP Identifier such as cwtap 00 04 9F 03 AE CO and the TAP Type will be updated automatically If you are having connection issues you can alter the JTAG TCK clock frequency value This value is in Kilohertz Slowing down the JTAG TCK can overcome connection issues Using a faster JTAG TCK setting can result in faster transmissions You can experiment with different settings by adjusting this value then connecting and running tests to see if the current clock frequency works If you are running on a processor that uses the Reset Configuration Words you can select True for RCW Override and then fill in the sixteen 16 32 bit RCW values When set to True an additional step is taking when loading firmware to first override the default RCW and use the filled in settings This is often a very useful step when working with brand new boards Once the RCW is overridden you can then use VTOS Program to program new RCW values into the defined RCW source For Serial connections type in a COM port or Scan and select from a pull down list The list is populated after the Scan button is clicked on Click on Scan to refresh the list of availab
10. Scan 21 R n Mode Steps OTT U 21 EE E OE E EE EOE EES 24 Exporting your Test Configuration to a Kozio Script File eeeoosssssececccsssseeccccsssesececcssssseccocssssscceccssssssecocosssssececssssssee 24 Exporting your Test Configuration to a TestStand 77 24 Coniaci 100000 aE 25 A DOU KIO TO EEA EE NEE ENE E ETEA EAEE ATEA EA 25 Copyright 0210 Inc 2015 2 44 XKOZIO VTOS Scan User Manual Introduction to VTOS Scan VTOS Scan provides everything you need to configure and validate the hardware interfaces of your board design including GPIO I2C SPI UART USB Ethernet PCI Express CAN SD MMC and SDIO VTOS Scan is a standalone verification tool that integrates with Kozio s vAccess for automated test System Overview The standalone VTOS Scan system is comprised of two major components VTOS Scan host software and VTOS Scan firmware These components communicate with each other through a communication channel such as a serial port or JTAG connection The VTOS Scan firmware runs from the on chip memory of your embedded system allowing you to fully test hardware buses and devices using the embedded processor The firmware provides a rich set of capabilities for configuring testing and troubleshooting your hardware board design The VTOS Scan host software runs on a Windows PC and provi
11. Scan will parse the file to determine what type of file you selected A dialog box prompts you with the information discovered Pin Mux Importer X Converting Sitara pin mux file convening sarap If the file type is unsupported a dialog indicates that no converter is available for the selected file type Click OK to continue Once the import is complete you will be prompted to save the file Note The input file name is used with a new extension of ksc Kozio uses the ksc extension to indicate the file is a Kozio script file After entering a filename and clicking on OK a pin mux import report is displayed 0 202 lines were generated from your pin mux file wu Input File C Users PinMuxDesignState_AM335x_Beagle dat Output File C Users PinMuxDesignState_AM335x_Beagle dat ksc Copyright Kozio Inc 2015 10 b XKOZIO VTOS Scan User Manual v Click OK and you are returned to the original Pin Mux File Selector Click OK to save your changes Clicking on Cancel will discard your changes but not the newly converted file Once a pin mux file is specified you are ready to add device tests Adding Device Tests Device tests provide the core of a test configuration You add device tests through the configuration tree Expand the desired group and channel to expose the Add Test node There are three ways to add new devices tests through the Add Test node through the channel menu an
12. VTOS Scan User Manual December 11 2015 02 02 hb KOZIO VTOS Scan User Manual v Table of Contents TO 3 OVOP VIC Wy EEA 3 MESS CESSISSE UU T e 3 BEES CECIDIT E 4 V TOS Scan Software 5 Using ME ENENYETIENTI In ricMCTC 5 OG CUMIN SEAR CCO ME 5 Und rstandme he onliguratlon TER 2 8 Addme a Board Imitrabzdton Step 9 Adding Pin Di uisi Pic 9 P XII DISC MC T T m T 11 blc 8 12 6 wir COMME CHONG PTT T DTE 12 ric u E OSGI ETT TINI UL QU I T I TTL 14 Understanding the VTOS Scan Home 15 P M NP UI NEM ssteess I5 EY VCS 16 16 CC AG 2949 22002 08 239 240400 00 82200 0022 0222 08 44300101 TE ER a DAN RI EUIS QUIS 20100 a Venn DEDI HEATED ANGE 16 ACTIONS 8016 17 Understanding Device TOSS E ii 18 The VIO vi 222 ates casas 10150222 o050089 0035022 caidas sn scesed sant E E E eo Poe does oo or see o eda 20 Loading and Running V FOS
13. by VTOS Scan email details about the new tool and an example pin mux file to support kozio com Copyright Kozio Inc 2015 9 VTOS Scan User Manual OZIO 44 c Import a Pin Mux File After clicking on Import you are prompted to select your existing pin mux file The file generated by the XML Document KSC File XML Document XML Document DAT File KSC File DAT File DAT File C File KSC File Date modified 8 26 2014 9 53 AM 6 4 2015 5 10 PM 5 7 2015 5 31 PM 8 26 2014 9 53 AM 2 21 2014 4 40 PM 6 4 2015 5 09 PM 2 21 2014 4 40 PM 2 21 2014 4 40 PM 8 26 2014 9 53 AM 5 27 2015 12 38 PM 8 26 2014 9 53 AM processor manufacturer s tool Name i MX6DQ Sabre AI RevA lomuxDesign xml 1 i MX6DQ Sabre AI RevA lomuxDesign xml ksc i MX6DQ Sabre Lite RevAIoMuxDesign xml i MX6SDL WandBoard AO0 IoMuxDesign xml PinMuxDesignState AM335x Beagle dat PinMuxDesignState AM335x Beagle dat ksc PinMuxDesignState AM335x Rev 2 x BBBlack dat PinMuxDesignState AM3358 TMDSSK dat ps7 init c i ps7 init c ksc ee Computer OS C Users gt Organize v JL CCS Library Nov 201 Libraries Documents Music Pictures amp videos a8 Homegroup Computer amp OS C ps7 init micro c C File Hi M All files Y Cancel 5 t gt Dell USB Portable H _ File name PinMuxDesignState AM335x Beagle dat VTOS
14. con as their identifier Copy Delete Up f Down Copyright 0210 Inc 2015 7 44 XIKOZIO VTOS Scan User Manual v Current Configuration Data The current configuration data runs across the bottom of the screen It displays the current configuration opened The file name will be blank if you created a new configuration but have not saved it Current configuration C Users example xml Understanding the Configuration Tree The configuration tree maintains a pin mux file a list of device tests and test actions The tree is organized as a single Configuration node which contains a single Board node Each node can be expanded or collapsed The Board node contains a Pin Configuration node and SOC node The SOC node contents varies based on processor architecture and VTOS Scan option chosen but will contain one or more groups The group nodes in turn contain one or more channels Configuration Board Pin Configuration SOC GPIO Group 26 Group 1 5 0 DEAE l I2C Device Exists Test Address 0xA0 i lt Add Test o 1 e 2 lt 6 26 Verify Test Address 0x72 ffg 26 Verify Test Address 0xA8 lt 6 26 Verify Test Address 0xAA 6 26 Verify Test Address OxAC 4 C Verify Test Address xEE lt Add Test SPI Group UART Group is Device tests are added at the channel level Setup Actions and Cleanup Actions can be added for all no
15. cript may disable a watchdog timer configure GPIO signals enable clocks configure power or other board specific steps If this step is enabled the board initialization script will be executed once a new connection is established Pin Mux File The next step is to specify which pin mux file you will be using for your custom circuit board design VTOS Scan allows you to import a pin mux files that was generated by another tool a pin mux tool commonly distributed by processor manufacturers Device Tests For each bus group the configuration tree will contain one or more channels This varies based on the processor architecture For each channel you add as many device tests as desired For certain busses such as I2C and PCI you can use the scan and add feature to automatically add a device test for every device discovered Special Actions If your embedded system design requires special operations such as driving a GPIO signal low before communicating with an I2C device you can add actions All nodes of the tree except for the Configuration and Board nodes have the option to add Setup Actions and Cleanup Actions A special dialog allows you to add as many setup and cleanup actions as desired The list of possible actions will vary based on processor architecture and tool option Run Command VTOS Scan also allows you to run your test sequence to validate it In order to run your test sequence you must update VTOS Scan connecti
16. d through the scan and add option The type and number of device tests available vary based on device type See Understanding Device Tests for more information Tip You can delete a device test by clicking on it and using the right mouse Delete Device menu option When prompted to confirm you wish to delete the node you can press the spacebar to confirm and delete Add Test Node Option Click on the Add Test node Using the right mouse pop up menu select a device test to add UART Group 5 UARTO H 1 Add Device Exists Test H UART2 di UART3 Add Loopback Test H UART4 Add Verify Test UART5 Add Bluetooth Device Exists Test Add Bluetooth Verify Test Select an option and a new device test is added to that channel Click on the Config Mode tab to edit the properties of that device test Channel Menu Option Click on the desired channel node Use the right mouse pop up menu option to select a new device test to add 5 6 UART Group wA Add Device Exists Test H UART 3 UARTZ Add Loopback Test 4 UARTZ Add Verify Test H UART4 H UARTE Add Bluetooth Device Exists Test Add Bluetooth Verify Test Run Select an option and a new device test is added to that channel Click on the Config Mode tab to edit the properties of that device test Scan amp Add Option Note This option is not available for all channel types 6 Copyright Kozio Inc 2015 1 44 IKOZIO VTOS Scan
17. des except the Configuration and Board nodes Selecting a node in the configuration tree with the Config Mode tab selected displays all of the properties available for that node Use the Config Mode panel to update the value of a given property for the highlighted node Tip To determine which option you choose for a given configuration file click on the Configuration node The current Configuration Type is a read only property that displays the program name and option chosen Config Mode Run Mode Configuration Type VTOS Scan Base Example Tip To determine the processor you choose for a given configuration file click on the SOC node The current SOC Type is a read only property that displays the processor architecture chosen Copyright 0210 Inc 2015 8 44 XIKOZIO VTOS Scan User Manual v Config Mode SOC Type Sitara AM3359 Name BeagleBone Setup Actions Add Actions Cleanup Actions gt Actions Is Adding a Board Initialization Step The Board Initialization node includes a property specifying the board initialization script file that you want to use for this configuration This script will be executed once after a successful connection A board initialization file is optional and this step will be skipped if no file is specified A board initialization script file is useful for taking required steps for proper board operation Some examples include disabling a watchdog timer enabling certain power rai
18. des two main functions a tool for configuring and verifying new test sequences and a tool for exporting test sequences for automatic use with various test executives The VTOS Scan firmware can also be driven programmatically from an automated production test framework using Kozio s vAccess DLL VTOS Scan Operation The primary purpose of VTOS Scan is to create a board test sequence interactively validate the sequence and export the sequence for automated testing Each board test sequence is stored in a separate configuration file and is linked to a processor architecture and a particular option VTOS Scan uses various options so that the embedded firmware accompanying that option is small enough to fit into on chip memory A current list of options are Base which includes GPIO I2C SPI and UART CAN Ethernet PCI USB 2 0 Device USB 2 0 Host and USB 3 0 Host New Configuration To start a new project create a new configuration a process that will prompt you to select the correct processor architecture and option A new license may be required for each processor architecture and option A new Copyright Kozio Inc 2015 3 b XKOZIO VTOS Scan User Manual v configuration contains a tree structure with a board board initialization pin configuration and one or more bus groups Board Initialization The next step is to specify if you want to run a script file that prepares the board for proper operation This s
19. e provides a user interface for creating test sequences that are performed by the VTOS Scan firmware running on your embedded device Copyright 0210 Inc 2015 20 b XKOZIO VTOS Scan User Manual v Use the Run Mode to validate that your device tests are configured properly Using the Run Mode requires a valid connection a working communications channel to your embedded device and the VTOS Scan firmware running on your embedded device Note You can use the VTOS Scan software to create new test sequences without having to interact with VTOS Scan firmware running on your embedded device In this mode you create a configuration and export it for testing with a test executive such as vAccessTest exe or TestStand Loading and Running VTOS Scan Firmware The VTOS Scan firmware must be loaded and running on your embedded device To load the VTOS Scan firmware use a JTAG programmer your boot loader processor specific boot methods USB SD Card Serial or similar process The VTOS Scan firmware images are installed in the VTOS Scan home directory on your host PC See Understanding the VTOS Scan Home Directory for further details Please see the appropriate Application Note for your system architecture for details on how to load and execute the VTOS Scan firmware image on your board These application notes are available on ww kozio com under Resources Application Notes Note Many of the application notes were written to c
20. e window to a file See Configure Logging Exporting Test Configurations One of the primary values of the VTOS Scan GUI is to create a test configuration and export it for automated testing Two export options are provided export to a Kozio script file and export to a NI TestStand Sequence Exporting your Test Configuration to a Kozio Script File To export your entire test sequence to a Kozio script file click on File Export Kozio Script File This step will traverse your test configuration data and create a Kozio script file The output is an ASCII file that you can view in any text editor File Tools fe New Ctrl N P Run Bl Disconnect Status Done Open 0 Save Ctrl S Save As Kozio Script File Settings NI TestStand Sequence EJ Exit Alt F4 Note You can use vAccessTest exe to execute your exported test sequence vAccessTest exe is a simple example program provided to demonstrate vAccess dll features vAccessTest exe has a command line option and is described in greater detail in the vAccess User Manual v AccessTest exe is provided free of charge through the VTOS Tools installer Exporting your Test Configuration to a TestStand Sequence File To export your entire test sequence to a TestStand sequence file click on File Export NI TestStand Sequence This step will traverse your test configuration data and create a sequence file The output is a binary file that you
21. g initial test development run this command once and the correct values will be displayed to the user Execute a test to calculate an MD5 checksum over a specified block count The user specifies Start Block Block Count the correct 32 19 MAC Loopback Test PHY Loopback Test External Loopback Test GPIO Loopback Test GPIO Verify Test I2C Bus Scan I2C Device Exists Test 120 Verify PCI Device Exists Test PCI Verify SDIO Device Exists Test SDIO Verify Test SDMMC Device Exists Test SDMMC Verify Test SDMMC Checksum Test 6 Copyright Kozio Inc 2015 VTOS Scan User Manual character MD5 checksum value anda Verify Checksum flag During initial test development set the verify flag to false and the test will return the correct 32 character MD5 checksum value Execute a test to write to a SPI device and verify that data can be read from that device Execute a test to write bytes to a SPI device read data from that device and verify that the correct bytes and number of bytes were read Tip set data verify to FALSE to display the current JEDEC ID information returned by the serial flash device Execute a test to verify that a Serial Flash device exists Execute a test to verify the Manufacturer Id Memory Type and Memory Capacity of a Serial Flash device Verifies the JEDEC ID from a SPI serial flash device The returned JEDEC ID is compared against the specified manufacturer and memory
22. hortcuts for commonly used tasks 7 Connections PI Connect Run LJIsconnect Status Bar The status bar displays status along with a spinner that only appears when connecting or running commands Status Running Configuration Tree The configuration tree is the panel on the left just below the tool bar Your board configuration data is displayed in the configuration tree The configuration tree in conjunction with the Config Mode panel is used to specify a pin mux file add and modify device tests and add and modify actions Config Mode Panel The configuration mode panel is visible when the Config Mode tab is clicked This panel has a top section and bottom section The top section displays all available fields for the node selected in the configuration tree The bottom section displays additional information about the field selected Some fields display an additional pop up dialog button or pull down list when clicked on Run Mode Panel The run mode panel is visible when the Run Mode tab is clicked This panel is a console window VTOS Scan output 15 displayed in the console window See Using the Run Mode once you are familiar with creating test configurations Device Button Bar The device button bar provides several shortcut buttons to aide in creating and adjusting your desired programming sequence Use the buttons to copy delete move up or move down the selected device node All device nodes use the same i
23. ig Mode panel To add an action click on either the Setup Action or Cleanup Action field Once selected a new ellipses button appears along the rightmost edge of the field Click on the button to access the Configure Actions dialog Config Mode Mame Pin Mux File CEHMEE MH a Add Actions EJ Cleanup Actions zAdd Actions gt Configure Actions Dialog Use the Configure Actions dialog to add delete modify or reorder your list of actions The actions are executed in the order presented from top to bottom The Configure Actions dialog has three main regions Actions Available Actions to Perform and Action Properties Actions Available Actions to Perform Action Properties Bit Set Bit Set 0x40360CAQ 32 7 Memory Address 0x40360000 Bit Clear Bit Clear 0x40360CA0 32 1 32 bits Command Timeout GPIO Write 1 21 High Value 80 Delay Ms Delay 5 Memory Write 0x40360000 32 0x00000800 User Notes GPIO Read GPIO Write I2C Read I2C Write I2C Dump Memory Read Memory Write Memory Dump Run Command SDMMC Set Width UART Configure UART GetC UART PutC UART WriteString Access Width The memory access width to use for the operation au Supported values are 8 16 32 cane Copyright Kozio Inc 2015 16 b XKOZIO VTOS Scan User Manual v Actions Available This section provides a list of actions that can be added to your configurat
24. ion They will be executed before or after the node you originally selected in the configuration tree To add a new action click on your choice and click on the Add Action button Tip Double click on an action to automatically add it Actions to Perform This section provides a list of actions that will be executed from top to bottom Click on an action to select it Once selected the Action Properties panel is updated To move an action up or down after you have added at least two actions click on the action and then click on the up arrow or down arrow buttons The reorder buttons are located to the right of this panel To remove an action click on the action and then click on the Remove Action button Tip You can also use the delete key to delete the highlighted action Action Properties This panel display the properties of an action and allows you to edit those properties The field at the bottom of this panel provides additional information regarding the highlighted property Saving Your Actions To save your updates click the OK button Clicking on the Cancel button will discard all modifications Actions Available The list of actions available for adding to your test sequence varies based on your chosen processor architecture and VTOS Scan option Below is a list of all possible actions some of which may not be available for your current configuration Sets a bit within an S bit 16 bit or 32 bit value in memor
25. ions After executing a run sequence the Run Mode console window is selected and the console window is updated with output received from the VTOS Scan firmware Some common run etrors are e 13 VACCESS EXECUTE COMMAND FAILURE The command failed to execute properly e 14 VACCESS EXECUTE COMMAND ABORT The command was aborted e 16 VACCESS_ EXECUTE COMMAND TIMEOUT The command timed out This will occur when the firmware is not loaded or running Disconnect This option 18 only available after you have successfully connected This step will disconnect your from vAccess and free up your license Use the Tools menu option to run the Disconnect command You can also use the Disconnect button on the tool bar B Disconnect Note You can Connect and Disconnect as many times as desired Understanding the Run Mode Console Window After executing a run sequence the Run Mode tab is selected and the console window is updated with output received from the VTOS Scan firmware Config Mode Run Mode i2c bus speed set I2C Set Bus Speed TT 100 0 lt 210 kozio gt 0 0x48 8 0x00000000 8 0x00000000 O0 i2c device test Address 0x48 Device Exists Test 0 0x48 I2C Device ID Scan Test I2C bus 0 address 0x48 offset 0x00 data 0xf2 PASSED kozio gt 0 OxAO 8 Ox00000000 8 0x00000000 O0 i2c device test Address OxA0 Device Exists Test 0 I2C Device ID Scan Test I2C bus 0 address 0xa0 offset 0x00 data 0xaa PASSED k
26. le serial ports or TAP connections Click on Save to save all modifications and return to the Configure Connections dialogue The Run Mode option uses the currently selected connection which is indicated by the highlighted radio button In the screen capture above the selected configuration is for VTOS Program running on an QorlIQ processor using a CodeWarrior connection specifically cwtap 00 04 9F 03 AE CO Note For non Serial connection types additional information is provided in the product s release notes Serial baud settings are not required for Seral connections since these are determined automatically by the host software and target firmware Tip You can define many connections and then select which connection also called fixture number to use for your various test setups Click on the Save button to store all connections This information is stored in a file on your computer Clicking on Cancel will not save any changes made Configure Logging Use the Configure Logging dialog to specify a file to which all console output will be saved Obtain access to this dialog by selecting the File Logging menu item Capture all console output to a log file Log File C temp vtos scan console log Browse View Cancel Save Copyright 0210 Inc 2015 14 b XKOZIO VTOS Scan User Manual v You can capture VTOS Scan console output to a log file Adding a filename will captu
27. ls or configuring a CLPD This file is an ASCII file that can be edited by hand Adding Pin Configuration Data The Pin Configuration node includes a property specifying the pin mux file that you want to use for this board configuration A pin mux file is a Kozio script file that configures the pins for your circuit board design This file is an ASCII file that can be edited by hand or generated When a file is entered that file will be included and used when executing your test configuration Note Device tests will often fail without a proper pin mux file specified and included Config Made Name BeagleBone rev A4 C Users USER Kozio VTOS_Scan scan testam335 Setup Actions zAdd Actions Cleanup Actions lt Add Actions You must use the Pin Mux File Selector to choose which file you want to use You cannot edit the filename field directly To select a new pin mux file click on the Pin Mux File property and then click on the ellipses button Pin Mux File C Users USER Kozio VTOS_Scan scan testam335 ksc Browse Import Ca Sak Use the Browse button to select an existing Kozio pin mux file Use the Import button to generate a new Kozio script file from an existing pin mux file created through a third party utility Most processor manufacturers provide a free pin mux utility and VTOS Scan will automatically convert that file into a Kozio script format Tip If you are using a new pin mux tool not currently supported
28. make sure they are set properly These are configured automatically by the installer so it 18 possible to re install VTOS Scan to set them up again e 5 VACCESS INI FILE ERROR Check to make sure you INI file is formatted correctly An example file is distributed with the VTOS Tools Installer e 6 VACCESS LICENSE ERROR Check to make sure you are not running more copies of VTOS Scan than you have licenses for Also check you license file or license server Note It 1s critical that the firmware running on your device matches the firmware file specified in your Connections settings If not some commands may report failures Run This option is only available after you have successfully connected There are several different ways to run your test configuration The ways vary from running all test configuration steps to only running a single device test command Note There are two Tools menu options to display the VTOS PC Version and also the VTOS DUT Version These are useful tests to verify communications with vAccess and the VTOS Scan firmware respectively Note There is also a Tools menu option to Read Console Data This command will read any pending console data but in most cases will not display anything if there is no console data This command may be useful for debugging when commands time out or fail The available run modes are e All Run everything o Use the Tools menu option Run or tool bar Run button This option will run
29. ons to specify device connection information The connection information is stored in a vaccess ini file that specifies one or more fixtures and for each fixture which firmware you have running on your embedded target and the communications channel Lastly you must have that firmware image loaded and running on your embedded device The remainder of this user manual provides step by step instruction on completing all of the tasks associated with creating testing and exporting your own test sequences for your custom embedded system VTOS Scan Suggestions Name Field Every node of the VTOS Scan configuration tree contains a Name field You can use this field to store labels that help you identify your particular board configuration information For device test nodes the Name label is also included as a comment in the test command being executed When exporting to a Kozio script file the Name label will appear in the console output after the command is run When exporting to a TestStand sequence the Name label will appear in the label TestStand displays for each command 6 Copyright Kozio Inc 2015 4 b XKOZIO VTOS Scan User Manual v VTOS Scan Software Requirements e Microsoft Windows XP 7 8 e Serial port or other supported communication device Using VTOS Scan Software Getting Started Installing the Software VTOS Scan is included with the VTOS Tools installer which installs VTOS Scan VTOS DDR vAccess
30. over loading VTOS DDR firmware but they still apply to loading all firmware types Run Mode Steps The Run Mode has three main steps that must be executed in order The steps are Connect Run and Disconnect Connect Use the Tools menu option to run the Connect command You can also use the Connect button on the tool bar b Connect This step requires a run time vAccess license One license is provided with a VTOS Scan purchase This step uses the connection information specified under Configuring Connections This step will attempt to establish a connection with the vAccess dll and launch a process that communicates with the VTOS Scan firmware This step can succeed even if you do not have a target connected but you will not be able to successfully run any test commands Once you are connected this button is greyed out and the Run and Disconnect options become available If you connection attempts fails a failure message is displayed in the status portion of the tool bar The error code displayed is taken from the vAccess header file vAccess h Additional information on the failure may be obtained from this header file Some common connection errors are e 2 VACCESS CONFIGURATION ERROR Check you connection settings and your communications channel 6 Copyright Kozio Inc 2015 21 b XKOZIO VTOS Scan User Manual v e 4 VACCESS ENV ERROR Check your KOZIO USER HOME and KOZIO VTOS TOOLS environment variables to
31. ozio gt 1 100 i2c bus speed set I2C Set Bus Speed 1 kozio gt 2 100 i2c bus speed set I2C Set Bus Speed 2 kozio gt 2 0x72 8 0x00000000 8 0x00000000 0 i2c device test Address 0x72 Device Exists Test 2 0x72 I2C Device ID Scan Test I2C bus 2 address 0x72 offset 0x00 data 0x00 PASSED kozio gt 2 OxA8 8 Ox00000000 8 0x00000000 O0 i2c device test Address OxA8 Device Exists Test d I2C Device ID Scan Test I2C bus 2 address O0xa8s offset 0x00 data 0x4c PASSED kozio gt 2 OxAA 8 0x00000000 8 0x00000000 0 i2c device test Address OxAA Device Exists Test 2 I2C Device ID Scan Test I2C bus 2 address Oxaa offset 0x00 data 0xaa PASSED kozio gt OxAC 8 0x00000000 8 0x00000000 O0 i2c device test Address OxAC I2C Device Exists Test 2 OxAC Interpreter stack underflow Check usage for command I2C DEVICE TEST kozio gt 2 OxEE 8 0x00000000 8 0x00000000 O0 i2c device test Address OxEE I2C Device Exists Test 2 OxEE I2C Device ID Scan Test I2C bus 2 address Oxee offset 0x00 data 0x00 PASSED Copyright Kozio Inc 2015 25 b XKOZIO VTOS Scan User Manual A scroll bar becomes available once the number of lines added to the console window is larger than the display area Right mouse menu options are available to copy selected test copy all select all and to clear all Copy Ctrl C Copy All Select All Ctrl A Clear All Tip You can also log the contents of the consol
32. part information Execute a test to write bytes to a UART device and read bytes from the same UART device The test passes is the number of bytes read matches the expected count of bytes read Execute a test to write data to a UART device read data from the same UART device and verify the data values Execute a test to write bytes to a UART device and read bytes from the same UART device The test passes is the number of bytes read matches the expected count of bytes read and a data compare of the bytes also matches the specified read compare bytes Queries the BD ADDR of the Bluetooth controller on the speorried channel The returned BD ADDR is displayed on the console Note The serial port parameters are automatically setup to match the Bluetooth specification 8 data bits no parity 1 stop bit 0 0750 flow control Queries the local version information for the Bluetooth controller connected to the specified UART channel The returned version information is optionally compared against the specified version information Tip set data verify to FALSE to display the current version information returned by the Bluetooth controller 44 KOZIO v SPI Device Exists Test SPI Verify Test SPL Flash Device Exists Test SPI Flash Verify Test UART Device Exists Test UART Loopback Test UART Verify Test UART Bluetooth Device Exists Test UART Bluetooth Verify Test Using the Run Mode The VTOS Scan softwar
33. rcuit board and program on board devices such as NAND Flash NOR Flash eMMC FPGAs and other programmable devices Kozio s tools are reusable across a family of SoC based designs and reusable across teams O 2015 Kozio Inc All rights reserved worldwide Kozio and the Kozio logo are registered trademarks of Kozio Inc VTOS VTOS Scan VTOS Scan VTOS Program and vAccess are trademarks of Kozio Inc All other trademarks are the property of their respective owners 6 Copyright Kozio Inc 2015 25
34. re all text written to the console window to that file The log is an ASCII text file Use the Browse button to browse to an existing file Use the View button to bring the log file up in your default text editor Tip You can directly edit the filename in the Log File text field Understanding the VTOS Scan Home Directory The installer creates a VTOS Scan home directory in your User profile directory The home directory contains software and firmware resources for the VTOS Scan system The location of the home directory is stored in the oKOZIO USER HOME 6 environment variable The VTOS Scan directory is located at o KOZIO USER HOME oN TOS Scan Tip To quickly navigate to the home directory open Windows Explorer and paste o KOZIO USER HOME 9eNVTOS Scan in as your new path location Firmware Images VTOS Scan firmware images are stored in the VI OS Scan directory VTOS Scan firmware images adhere to the following naming convention vtos system architecture scan elf ELF object file Compatible with a wide variety of loaders including many JTAG based loaders vtos system architecture scan img U Boot compatible vtos system architecture scan srec Motorola S Record vtos system architecture scan bin MLO TI self booting binary file Example Files A few sample configuration files are stored in the VTOS Scan directory VTOS Scan configuration files are stored as XML files with an xml extension Using VTOS
35. rnet PHY and the copper fiber transceivers Execute a test that drives a signal on an out pin and verifies that the signal is received on an pins 1 Execute a test that reads a signal on a user specified pin and compares that value against a user specified expected value Non destructive scan of all possible addresses on a specified I2C bus Usage lt bus gt i2c bus scan Where lt bus gt is the 120 bus number Specify 1 to scan all buses Execute a test to verify that the specified 120 device can be accessed correctly proving that it exists Execute a test to read a data value from the I2C device and compare it against a user specified value Execute a test to verify that the specified PCI device can be accessed correctly proving that it exists Execute a test to read the vendor id and device is from the PCI device and compare it against a user specified values Execute a test to verify that the SDIO device on a configured channel can be accessed correctly proving that it exists Execute a test to verify that the specified SDIO device can be accessed and its identification information matches what the user provided Execute a test to verify that the SD MMC device on a configured channel can be accessed correctly proving that it exists Execute a test to read the Manufacturer Id OEM Id and Capacity from a configured SD MMC device and verify that it matches the values provided by the user Durin
36. rrior cwtap 00 04 9F 03 AE CO 9 Program P Dox CodeWarrior cwtap 00 04 9F 03 AE CO VTOS Scan Base Goria P2020 CodeWarrior v utap 08390702 VTOS Scan PCI v Zyng 7000 v Serial Y COM94 Cancel Save Use this dialog to add remove or alter target connection settings This dialog is used to specify how the host software will communicate with the target firmware Follow the steps below to create delete or modify target connections 6 Copyright Kozio Inc 2015 12 VTOS Scan User Manual This button adds a new blank target connection You must fill in the four options for Product Processor Connection and Settings This option determines which firmware image the host and target will use for communications Each product is installed with different firmware images If this setting is incorrect target command execution errors will be reported This option also determines which firmware image the host and target will use for communications Each processor is installed with different firmware images If this setting is incorrect target command execution errors will be reported This option determines the type of connection used for host to target communications The Settings option is tied dirctly to this setting Changes made to Connection will also change Settings Click on a Settings pull down or u
37. se the right mouse menu to access the Configure Comm Settings dialogue The new dialogue is used to update connection specific details Click here to remove a target connection You cannot remove a connection when only one connection remains VTOS DDR VTOS Program VTOS Scan Base Processor Stara avosse o iMX6 Kinetis K6x MPC83xx MPC85xx QorlQ P4xxx QorlQ P 5x Sitara AM437x Zynq 7000 CodeWarrior VarioTAP XJlink XY 1000 Settings cwtap 00 04 9F 03 AE CO cwtap 00 04 9F 03 AE CO utap 08390702 COM94 44 IKOZIO Click on the Add button Select a Product Select a Processor Select a Connection Select or enter Settings Click on the Delete icon Use the Configure Comm Settings dialogue to specify the details of the communications port you have chosen M Configure Comm Setting CodeWarrior TAP Connection cwtap 00 04 9F 03 AE CO 10000 True 0x10540000 0x00000000 0x1C1C1800 0x00440000 0x00000000 0x00000000 OxFES00000 0x01000000 Ox00000000 0x00000000 0x00000000 0x000 70000 0x00000000 O0x00000000 0x00000000 0x00000000 13 General TAP Type TAP Identifier JTAG TCK RCW Override Reset Control Word RCW RCW 1 RCW 2 RCW 3 RCW 4 RCW 5 RCW 6 RCW 7 RCW 8 RCW 9 RCW 10 RCW 11 RCW 12 RCW 13 RCW 14 RCW 15 RCW 16 TAP Type The CodeWarrior TAP connection type This selection is used when scanning for new TAPs Copyright Kozio
38. y Clears a bit within an S8 bit 16 bit or 32 bit value in memory 6 Copyright Kozio Inc 2015 17 b XKOZIO VTOS Scan User Manual Performs a read operation to an 120 device Returns the 8 bit data value read from the 120 device at the specified offset and displays the value if selected Read data is returned as a single parameter onto the data stack For multiple byte reads data is packed in big endian format T2C Read Performs an I2C write to the I2C device specified Data written is specified by the Data and Data Width fields I2C Write Reads data from the specified device address and displays the data to the console I2C Dump Performs a read operation to a memory location Returns the data value read from the memory location and displays the value if selected Memory Read Performs a memory write to the location specified Data written is Specified by the Value field Memory Dump Reads data from the specified address and displays the data Memory Write Runs any Kozio script command available You can use include script file to include new command definitions and test sequences Run Command SDMMC Set Width Sets the SD MMC SDIO bus width The user specifies the channel and desired bus width 1 4 or 8 This action is useful to testing all possible bus widths UART Configure Configures a UART device Specify channel number baud rate data bits parity Stop bits and flow control
Download Pdf Manuals
Related Search