Follow these instructions to mark an SD Card partition as Active on Windows 7.
- Plug your SD card into your PC. We use a USB to SD Card adapter that supports many different SD card sizes and types.
- Open a Command Prompt window (cmd.exe). Select Start button , and in the Search programs and files text box, type CMD and press Enter.
- At the command prompt shell, enter the follow sequence of commands:
- Type DISKPART and press Enter
- Type LIST DISK and press Enter
- For this example, two disks are listed. The C: drive is Disk 0 and 149 GB. The SD Card is Disk 2 and listed as 1858 MB. This is just under the advertised capacity of 2000 MB of the SD Card used. Note: It is critical to pick the correct disk!
- Type SELECT DISK 2 and press Enter
- Type LIST PARTITION and press Enter
- The SD Card only has one partition.
- Type SELECT PARTITION 1 and press Enter
- Type ACTIVE and press Enter
- Type EXIT and press Enter
When using Kozio’s VTOS DDR software:
- Using the Automatic or Timing option, the typical time is 30-60 minutes.
- Using the Manual or Register option, the typical time is 3 days or longer depending on user experience. The register settings can also be exported from a customer’s application software, or boot loader, and imported into VTOS DDR in about 30 minutes.
- The Automatic option requires a memory part file which can be created in 15 minutes. Kozio creates and releases memory part files for any customer, just email email@example.com with the memory part number and speed grade.
NOR – Yes, all CFI compliant devices.
NAND – Yes, all ONFI compliant devices.
SPI – Yes all devices are supported.
QSPI – Yes all devices are supported.
MMC – Yes all devices that conform to the MCC specification, including eMMC and SD Cards.
Some DDR memory controllers support built-in error checking code (ECC), providing automatic correction for single-bit data errors and automatic detection of double-bit data errors.
When this feature is enabled, the board design or DIMM module adds one or more extra memory chips that save the generated ECC data. During writes to DDR, the memory controller calculates a new ECC byte for the new data bytes. During reads from DDR, the memory controller recalculates the ECC for the read data and compares this against the saved ECC byte. When a mismatch occurs, the memory controller generates an exception indicating the type of error (single-bit correctable or multiple-bit uncorrectable).
Software running on the processor does not have direct visibility to the memory chips used to store ECC. However, when your board design enables ECC support, the extra memory chip is thoroughly tested simultaneously during all the memory tests built into VTOS DDR. Any single-bit ECC errors that are detected and corrected are logged by VTOS DDR. Any double-bit ECC errors are also logged, but also cause memory test failures (because the data error could not be automatically fixed by the memory controller). If more than two bits of data are corrupted, the ECC algorithm is not guaranteed to detect the failure, but the VTOS DDR memory tests will detect and log these data errors.
VTOS DDR also provides tests for injecting single-bit and multiple-bit ECC errors. The Kozio ECC tests verify that the memory controller’s hardware-based ECC generation and checking feature is fully functional.
The free trial software is full featured with no feature limitations. The software license is simply limited to the specified number of days.
Once a license is purchased, you can continue to use the software without interruption. All of your configuration data is saved and usable.
VTOS is an innovative software suite that enables functional circuit board testing, fast flash programming, and automated DDR optimization and verification of complex embedded electronics.
VTOS is an acronym for Verification and Test Operation System. VTOS is delivered to customers as a binary image that is ready to be loaded onto a circuit board design and executed by the embedded processor. VTOS comes pre-built with drivers, tests, troubleshooting commands, programming commands, flash support, and reporting.
VTOS uses standard interfaces (JTAG, Serial) for communicating between the processor run control firmware provided by Kozio and the PC user interface provided by Kozio. VTOS requires no special hardware or interfaces on your circuit board design.
Kozio’s mission is to reduce manufacturing costs through faster circuit board test and faster flash programming, and to reduce design costs through easy to use tools for creating more reliable circuit board designs.
Yes. Support is included for all products with an active license.
Support includes all new releases, bug fixes, documentation updates, email support, and phone support.
If you purchased a term license, support is included during the active term.
If you purchased a permanent license, support is included for the first 12 months. Support can then be purchased for additional 12 months for a small percentage of the original cost. The original license and software will continue to function but you cannot download new releases unless you have active support.
On-site support can be purchased for an additional cost based on time and trip expenses. Hardware troubleshooting and support, specific to a custom circuit board design, can be purchased on an hourly basis.
If you have U-Boot setup on your board, you can dump out the DDR registers and send the data to Kozio. This is useful for helping a customer debug DDR configuration issues. The register values can be fed into VTOS DDR for testing DDR memory using your settings versus the optimized ones determined by VTOS DDR tuning.
Use the U-Boot “md” command to dump out the DDR registers and email the results to Kozio. The DDR register offsets for your processor can be found in the processor reference manual.
Here is an example using a base address of 0xFFE0_0000 for the NXP QorIQ P1 processor family. For this processor, the DDR registers are at offsets: 0x2000, 0x2100, 0x2B00, 0x2E00 from the base address. The command “bdinfo” should display the configured base address.
=> md 0xFFE02000
=> md 0xFFE02100
=> md 0xFFE02B00
=> md 0xFFE02E00