ScanWorks® JTAG MDOC™ Programming            

Product Overview

The ScanWorks® mDOC™ Programming feature provides boundary-scan access to the mDOC G3 family of embedded flash drive devices from SanDisk®, which are also known as disk-on-chip devices. Embedded flash drives are typically used as high capacity, non-volatile flash drives in devices such as cameras, digital TVs, and hand-held terminals.

The mDOC feature enables you to include on-board programming operations with JTAG as part of the manufacturing test process or during the initial prototype bring up phase. The mDOC feature uses utilities provided by SanDisk to write information, retrieve information, and format the device to prepare it for programming. Using boundary scan to access the mDOC devices during manufacturing assembly and functional testing also provides a test of the connections between the mDOC device and the host processor and enables preliminary configuration data to be loaded even if the processor is not fully functional.

The ScanWorks mDOC Programming action integrates special routines to ensure proper read/write and formatting procedures are implemented. Although the mDOC devices are based on NAND flash technology, the procedures to access them are significantly different than stand-alone NAND flash devices, requiring a separate ScanWorks action to support them. The current mDOC action supports the mDOC G3 family of devices with models available from the ScanWorks on-line model library. Additional mDOC families may be supported, depending on customer requests.

Using mDOC Programming

The mDOC Programming action is implemented much like the other memory device programming actions in ScanWorks except it requires a separate action for read operations, write operations and the format operation. When creating the three actions, name each one appropriately to indicate the operation to be done.

The mDOC action includes many of the features supported by ScanWorks Flash Programming and NAND Flash Programming. You can target a specific scan path if multiple scan paths are available in your design and target a specific mDOC device on that scan path if more than one is used. When the action is first built ScanWorks attempts to automatically find access to the mDOC device from a boundary scan device. ScanWorks uses information from the available models of non-boundary-scan devices that may be in the path between the mDOC device and the boundary-scan device. If any access for any signal is not found, you can manually specify from where boundary scan access is available. If access is not available, programming the mDOC device with boundary scan may not be possible.

More than one source file can be loaded into the mDOC device with one write operation enabling you to fully load the device in one operation. You have access to the full functionality of the SanDisk utilities by specifying any of the supported parameters. The parameters are documented in the ScanWorks Help files and in the SanDisk Disk-On-Chip Software Utilities manual available from SanDisk.

Although each utility used must be in a separate action you can group the functionality from the different actions (including specifying their order) by creating a ScanWorks sequence.

Support for other mDOC Device Families

Support for other mDOC device families such as the H3 family requires a different set of supporting programs from SanDisk as well as a model for the specific devices. Implementing support for other families may require a one-time charge to cover the development costs in addition to the price of the mDOC Programming feature.