Frequently Asked Questions (FAQ)
|
|
 |
|
What do you need from us to configure your software for our board? |
| |
 |
|
Kozio uses your block diagram and schematics. If your project restricts the distribution of this material, we use a 1-2 page questionnaire instead. Kozio does not require time from your engineers in order to support your hardware, except for an occasional email question. Kozio works directly with most IC vendors to obtain required datasheets. A benefit of this process is that Kozio provides a review of your hardware from a software perspective.
|
| |
|
|
|
Do you deliver source code? |
| |
|
|
Not entirely. Delivered are libraries, header files, example source code, and examples scripts that are part of the kDiagnostics™ development kit. The development kit does allow you to modify some configuration settings and rebuild the binary applications for your custom board. The target application allows access to all busses, 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. We also provide low-level drivers in source form to help our customers setup and configure their driver software
|
| |
|
|
|
Does kDiagnostics™ require a boot loader? |
| |
|
|
No. The kDiagnostics™ delivery provides a self-booting application that executes from ROM or RAM. A loadable version is also provided. Here are the three image types provided:
- 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.).
|
| |
|
|
|
How do you handle custom devices like FPGAs and ASICs? |
| |
|
|
We deliver a development kit that includes the GNU compiler, linker, 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 this kit you can create your own menu-items, fully automatic manufacturing tests, and custom tests using our API, framework, and test primitives.
kDiagnostics™ automatically allocates a memory region for your custom IC allowing you to access all registers by default. Also provided is a means to load images into FPGAs. Very quickly you can use kDiagnostics™ to transfer a binary image from a PC and load it into the FPGA. As a service, Kozio provides custom test code development.
|
| |
|
|
|
Can we use our own diagnostic tests?? |
| |
|
|
Yes. Your custom test code can be added to kDiagnostics™ using the standard development kit. Your code may require some modifications to work with the kDiagnostics™ libraries, but those changes may be very minimal depending on what your codes requires. The kDiagnostics™ test environment include the Standard C library functions and thousands of functions for initializing, configuring, and controller various devices, memories, and interfaces.
|
| |
|
|
|
How do your tests compare to those provided with u-boot or RedBoot ? |
| |
|
|
Kozio provides a much broader range of tests that uncover design or assembly faults not found by other test methods. Hardware validation is all we do and we continue to expand our test coverage. kDiagnostics™ provides a deterministic platform for testing, remote and automated capabilities, and the ability to create new test cases on the fly. Our test library is documented and supported by validation experts with knowledge of numerous microprocessors, memories, and controllers. |
| |
|
|
|
Can your product program NAND flash? |
| |
|
|
Yes. kDiagnostics™ can program any NOR or NAND flash device.
For devices that support advanced programming features such as buffered programming, kDiagnostics can program devices up to 3X faster than other programmers. Another benefit is that you can use your JTAG programmer to load kDiagnostics 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. |
| |
|
|
|
Do you test beyond the board edge? |
| |
|
|
Yes. Our test suites 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 after reception.
In addition, performance characterization can be performed on supported interfaces, such as SATA. |
| |
|
|
|
How do I get your software onto my board? |
| |
|
|
For first use, you use a JTAG programmer to program the self-booting kDiagnostics into ROM or RAM. Once kDiagnostics 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 kDiagnostics from ROM or RAM. |
| |
|
|
|
What needs to be working on the board in order for your software to run? |
| |
|
|
We need the processor and a serial port for the user console. If Flash or ROM is not working we can execute directly out of RAM memory and test the Flash. Our tech support also helps you set up DDR memory so you will quickly get to the Kozio command prompt. We have many customers that start out with non-working memory. |
| |
|
|
|
How do I buy your software? |
| |
|
|
With a block diagram and/or device list we can provide a quote. With schematics and a purchase order (PO) we deliver kDiagnostics and the development kit, in 2 to 10 days. They can be ready and waiting for your board to come out of assembly. All of our software comes with a 60 day guarantee. kDiagnostics™ and kPOST™ are licensed per board design with no royalties. The automation tools are licensed per test station.
Discounts are available for board families. |
| |
|
|
|
How does your product compliment boundary scan and JTAG testing? |
| |
|
|
We provide functional testing in comparison to the structural test methods. Our tests run at full processor speeds so we have an excellent solution for finding high-speed issues with interfaces, busses, DDR, and memories. Our solution ships as a power-on self-test application and easily deploys to your contract manufacturer. We also provide software that can help a team get application code working faster on the new board design. |
| |
|
|
|
Do you provide stress testing? |
| |
|
|
Yes. kDiagnostics runs a variety of tests that will stress various interfaces and controllers. When available on the microprocessor, 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 validation. |
| |
|
|
|
Can I loop a test? |
| |
|
|
Yes, using a few simple commands, you can execute counted loops, indefinite loops, or loop until failure testing. All commands or test suites can be looped, or nested in a conditional statement, even your newly created custom test suites and test commands.
|
| |
|
|
|
Do you test Ethernet interfaces? |
| |
|
|
Yes, we test 10/100/1000 interfaces. We test 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 we provide tests in 10/100 as well as Gigabit speeds to isolate faulty gigabit control lines. Our 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. |
| |
|
|
|
Can your memory tests isolate data and address line issues? |
| |
|
|
Yes. Our product displays 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 revolve numerous memory issues undetected by other test methods. We have helped customers, around the world, debug memory problems in just a day or two. |
| |
|
|
|
Will kPOST™ work with my boot loader, operating system and application? |
| |
|
|
Yes. Kozio delivers a self-booting binary that executes from the boot sector of Flash or ROM memory. kPOST™ 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 on how to perform this action. |
| |
|
|
|
How are POST results stored? |
| |
|
|
The POST results 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 kDiagnostics™ Command Reference document provided with product delivery.
|
Company