Using DiskOnChip with VxWorks
Contents
1. printf n 6 Modify the file Tornado target config all bootConfig c by adding the following code after the line define INCLUDE_DISKONCHIP to the routine boot Load ifdef INCLUDE_FD 0 int type 0 int drive 0 2 return ERROR else amp type OK Oxsx n errno return ERROR return OK tendit INCLUDE_FD ifdef INCLUDE_IDE 0 91 SR 005 38 7L Rev 1 3 35 LL M Systems ms Flash Disk Pioneers 0 0 int type int drive 3 return ERROR else amp type OK errno return return endif ifdef INCLUDE_ATA if int ctrl ERROR OK IDE INCLUDE _ strncemp params bootDev ata 0 0 params bootDev int drive Lf strlen 3 ERROR recurn else sscanf if ataLoad printErr errno return return fendif ifdef INCLUDE_PCMCIA params bootDev params bootDev ctrl drive nError loading file ERROR OK INCLUDE_ATA xy pcmcia 6 init PCMCIA Lib pemcialInit if strncmp 91 SR 005 38 7L Rev 1 3 Sk 386 Cbde csd params bootFile errno Using DiskOnChip with VxWorks amp drive OK CEEL pEntry Oxsx n 362. INCLUDE_DISKONCHIPTFFS to the helpMsg in the routine f A0 vxWorks endif INCLUDE_FD ifdef INCL LDE IDE ideO vxWorks ifdef boot device endif INCLUI INCLUDE_ATA ifdef boot device endif INCLUDE ata ctrl driv DE ATA INCLUDE_PCMCI pemcia sock file name ifdef boot device INCL UDE_D tffisO vxworks endif INCLUDE_D Boot flags wee U tffs drive removabl ISKONCHI Ds fil ata0 vxWorks nam A pemcia0 vxWorks _PCMCIA ISKONCHI P frr nam P Z 5 Modify the file Tornado target config all bootConfig c by adding the following code after the line define INCLUDE_DISKONCHIP to the routine bootHelp INCLUDE_FD printi d fendif INCLUDE_FD ifdef INCLUDE_IDE printf ide endif INCLUDE_IDE ifdef INCLUDE_ATA 91 SR 005 38 7L Rev 1 3 34 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks printf ata tendit INCLUDE_ATA ifdef INCLUDE_DISKONCHIP printf thes endif INCLUDE_DISKONCHIPTFFS ifdef INCLUDE_TFFS printf tfts tendit INCLUDE_TFFS
3. INCLUDE_FD EA INCLUDE_TFFS DE_ATA f seconds to wait for spinup INCLUI defined 37 LL M Systems ms Flash Disk Pioneers 8 the following cod before the rou ifdef ifdef extern endif Tru extern extern Using DiskOnChip with VxWorks P just Modify the file Tornado target config all bootConfig c by adding after the line define INCLUDE_DISKONCHI tine usrRoot INCLUDE_DISKONCHIP __cplusplus nom ifndef _ASMLANGUAGE eFFS driver s configuration variables unsigned char flUse8bit unsigned char flUseNFTLCache extern extern extern else extern extern endi Tt _ STI endif int fl_useDebug if defined __STDC void tffsSe STATUS __STI void STATUS DG 2 ty ay All tup tffisDrv tfftsSetup tffsDrv DEL _ASMLANGUAGE ifdef _ cplusplus endif endift INCL UDR D code after the line define Ef ifdef x ES ifdef INCLUI INCLUI ISKONCHI void D int diskonchips EP xy ISKONCHI DE IDE DE_ 91 SR 005 38 7L Rev 1 3 defined __ cplusplus long addressRange Modify the file Tornado target config all bootConfig c by adding the following INCLUDE _ P just before the routine usrRoot
4. 91 SR 005 38 7L Rev 1 3 16 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks struct tffsDevFormatParams format_params TFFS_STD_FORMAT_PARAMS format the first DiskOnChip tffsDevFormat 0 int amp format_params skip the second DiskOnChip tffsDevFormat 1 int amp format_params format the third DiskOnChip tffsDevFormat 2 int amp format_params 7 Data Integrity on the DiskOnChip The data structures on the DiskOnChip can be divided into low level data structures and file system data structures The low level data structures are M Systems proprietary flash specific data structures that are maintained by the TrueFFS driver The file system data structures are maintained by VxWorks dosF s filesystem and basically consist of the FAT root directory and so on The flash management algorithms that are used inside the TrueFFS driver have been carefully designed to keep the low level format consistent at any given moment of time and guarantee the integrity of the low level data structures even after a power failure or an unexpected system shutdown Data integrity on the file system level is the responsibility of the OS and not the TrueFFS driver By default VxWorks dosFs file system does not immediately write data onto the storage device i e DiskOnChip but instead caches data in RAM While this increases the I O performance of the
5. 38 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks R ER ifdef INCLUDE_ATA IMPORT ATA_RESOURCE ataResources ATA_RESOURCE pAtaResource for ix 0 ix lt ATA MAX CTRLS ix pAtaResource amp ataResources ix if pAtaResource gt ctrlType IDE_LOCAL ataDrv ix pAtaResource gt drives pAtaResource gt intVector pAtaResource gt intLevel pAtaResource gt configType pAtaResource gt semTimeout pAtaResource gt wdgTimeout ifdef INCLUDE_SHOW_ROUTINE ataShowInit install ATA IDE show routine endif INCLUDE_SHOW_ROUTINES endif INCLUDE_ATA ifdef INCLUDE_LPT IMPORT LPT_RESOURCE lptResources lptDrv LPT_CHANNELS amp lptResources 0 init LPT parallel driver endif INCLUDE_LPT ifdef INCLUDE_PCMCIA ifdef INCLUDE_SHOW_ROUTINE pemciaShowInit install PCMCIA show routines endif INCLUDE_SHOW_ROUTINES pemciaInit init PCMCIA Lib endif INCLUDE_PCMCIA 91 SR 005 38 7L Rev 1 3 39 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks ifdef INCLUDE_DISKONCHIP Call tffsSetup as appropriate for your application u If you want to change the settings of the driver s configuration variables flU_use8bit flUseNFTLCache_useUCac
6. BLK_DEV that has been returned by the preceding call to t fsDevCreate The routine dosfsDeviInit returns a pointer of type DOS_VOL_DESC which must be saved by the application for later use Example 2 If there is only one DiskOnChip in the system the following code section names it t f fs0 and associates it with the dosFs file system include fldrvvxw h DOS_VOL_DESC tffs_dosFs_vol dosFsDeviInit tffs0 tffs_blk_ dev NULL In a system containing three DiskOnChips the code fragment is as follows include fldrvvxw h DOS_VOL_DESC tffs_dosFs_vol 3 NULL NULL NULL tffs_dosFs_vol 0 dosFsDevinit tffs0 tffs_blk_dev 0 NULL tffs_dosFs_vol 1 dosFsDevinit tffsl tffs_blk_dev 1 NULL tffs_dosFs_vol 2 dosFsDevinit tffs2 tffs_blk_dev 2 NULL 3 5 Configuring dosFs File System M Systems guarantees that the low level format of the DiskOnChip never becomes corrupted by unexpected power shutdowns Unfortunately the default configuration of VxWorks dosFs file system is aimed at providing high I O performance by caching user data in RAM rather than immediately writing it onto the disk If unexpected power shutdowns are likely this data will be lost To minimize the risk it is possible to eliminate data caching by dosFS This can be achieved by calling the routine dosFsVolOptionsSet refer
7. return error if ioctl fd2 FL_IOCTL_GET_INFO int amp out ERROR return error sectors2 long out info logicalSectors if sectorsl gt sectors2 return error Copy source TrueFFs volume to the target Sector are zero based for iSect 0 iSect lt sectorsl iSect read the sector from the source volume rwReq in firstSector iSect hiddenSectors rwRegq in numberOfSectors long 1 rwReg in buf buf if ioctl fdl FL_IOCTL_READ_SECTORS int amp rwRegq ERROR return error if rwReq out numberOfSectors 1 rwReq out status f10K return error write the sector to the target volume 91 SR 005 38 7L Rev 1 3 27 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks rwReq in firstSector iSect hiddenSectors rwRegq in numberOfSectors long 1 rwReg in buf buf if ioctl fd2 FL_IOCTL_WRITE_SECTORS int amp rwReq ERROR return error if rwReq out numberOfSectors 1 rwReq out status f10K return error XI void close fal void close fd2 Note The IOCTL calls FL_IOCTL_READ_SECTORS and FL_IOCTL_WRITE_SECTORS use an atypical sector numbering scheme They assume that the sector numbers are zero based and map sector 0 to the starting sector of the FAT partition i e VxWork
8. LL M Systems ms Flash Disk Pioneers int if return else sscanft ate return fall let s a endif INC sock strlen ERROR pcmciaLoad OK through if the PC card is not a block device thernet devic NONE params boot params bootDev sock params boot 6s c d Using DiskOnChip with VxWorks amp sock tFile pEntry OK try to boot it from an LUI A DE__PCMC ifdef INCLU DE DISKONCHIP ISE int int strlen return else sscanft amp drive if print errno return re turn endif strncmp drive removable tffsLoad CErr INCLUI params bootDev 0 U params boot Dev ERROR params bootDev amp removable drive 0 U nError loading file HRE TS params bootFile 4 Sk Asskcede csd pEntry OK errno Oxsx n ERROR OK DE_DISKONCHIP 7 Modify the file Tornado target config all bootConfig c by adding the line define INCLUI P as follows DISKONCH if defined defined defined DE NCL NCL NCL UI UI UI I I I DE SCS IDE _BOOT defined ISKONCHIPTFES DE D DE define SPI XJ Nes UP_TIMEOUT 45 max o 91 SR 005 38 7L Rev 1 3 defined
9. _ STDC__ endif _ASMLANGUAGE ifdef _ cplusplus endif forward declarations ifdef_ STDC__ void devSplit char fullFileName char devName else void devSplit endif _ STDC__ extern unsigned noOfDrives STATUS usrTffsConfig int drive drive number of TFFS int removable 0 non removable flash media char filename mount point BLK_DEV pBootDev char bootDir BOOT_FILE LEN if UINT drive gt noOfDrives printErr Drive is out of range 0 d n NoOfDrives 1 return ERROR 91 SR 005 38 7L Rev 1 3 31 LL M Systems m Flash Disk Pioneers wE Using DiskOnChip with VxWorks Create a block device spanning the entire disk non destructive T pBootDev tffsDevCreate drive 0 NULL printErr tffsDevCreate failed n return ERROR Split off boot device from boot file devSplit fileName bootDir Initialize the boot block device as a dosFs device named lt bootDir gt if dosFsDevinit bootDir pBootDev NULL NULL printErr dosFsDeviInit failed n return ERROR return OK LOCAL STATUS tffsLoad int drive int removable char fileName FUNCPTR pEntry int fd TFFS drive number 0 noOfDrives
10. ms Flash Disk Pioneers Using DiskOnChip with VxWorks status ioctl fd FL_IOCTL_DEFRAGMENT int amp ioctl_req if status ERROR printf O0x x error in ioctl n int errno void close fd check out the ioctl_req out status printf status 0x x n int ioctl_req out status reply data is in ioctl_reg out actualNoOfSectors Note The TrueFFS driver also provides the routine t ffsRecycle which can be used instead of the FL_IOCTL_DEFRAGMENT IOCTL call Refer to Section 8 for further details 9 4 FL_IOCTL_WRITE_PROTECT The code sample below describes how to software write protect on the DiskOnChip Note Before executing the code fragment below ensure that the DiskOnChip has been unmounted by a call to the routine dosFsVolUnmount When write protecting the DiskOnChip please be aware of the fact that ALL the attempts to write data onto the DiskOnChip will be rejected including the write requests which are generated by the filesystem internally for it s own purposes include lt ioLib h gt include lt dosFsLib h gt include lt stdlib h gt include lt stdio h gt include lt errno h gt include fldrvvxw h include flioctl h typedef union flWriteProtectInput in flOutputStatusRecord out flWriteProtectReq 91 SR 005 38 7L Rev 1 3 22 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxW
11. used because of the application s size The DiskOnChip supports both the network boot and the one step boot and there is no need to make any changes to the VxWorks boot code The two step boot requires some minimal changes to the following VxWorks files s BSP configuration H file i e Tornado target config pc486 config h incase of pc486 BSP e Tornado target config all bootConfig c e Tornado target config all usrConfig c 91 SR 005 38 7L Rev 1 3 12 LL M Systems m Flash Disk Pioneers Using DiskOnChip with VxWorks The procedures outlined in Sections 4 2 4 3 are common to all three boot scenarios When using the two step boot follow the extra procedures outlined in Appendix 1 Note The procedures described in Sections 4 2 4 3 are typically done only once on the very first DiskOnChip you use Once you have successfully gone through one of these procedures it is possible to copy the binary image of the DiskOnChip to other DiskOnChips i e cloning the first DiskOnChip 4 2 Requirements for Installation of the DiskOnChip into VxWorks In order to prepare the DiskOnChip to boot VxWorks the following software tools are required e DiskOnChip DOS utilities diskette The utilities can also be found on M Systems website WWW m sys com s DiskOnChip firmware file DOC121 EXB file where 121 is the firmware version Any firmware version higher than 121 will do This file can be found on the DOS
12. application s linking process either statically or dynamically One possible way to accomplish this is to copy the file MSYSVXW o to the directory Tornado target 1ib and then add it to the existing Vx Works I80486 object library as follows ar386 cru libI80486gnuvx a MSYSVXW o fldrvvxw h Include file for the TrueFFS driver that must be included by the application in order to access the driver s API Furthermore make sure it is on the compiler s INCLUDE path flioctl h Extended functionality include file This file must be included by the application in order to be able to access the Extended functionality API 3 3 Customizing the TrueFFS Driver 3 3 1 Setting the Address Range The initialization routine of the TrueFFS driver scans the host address space for the DiskOnChip s By default the driver will look for a single DiskOnChip in the address range 0xc8000 0xe0000 In most x86 architecture scanning the default address range will be sufficient but in certain cases there might be a need to change it Changing the area to be scanned can be accomplished by calling the routine tffsSetup Note The routine tf fsSetup must be called only once before the call to the initialization routine tffsDrv Normally this is done from usrRoot The routine t sSetup can be found in the header file 1drvvxw h and has the following declaration extern void tffsSetup int diskonchips long addressRange where d
13. assuming it is dev tffs0 fd open dev tffs0 O_RDWR 0 if fd ERROR printf Ox x error in open n int errno return issue IOCTL call to the driver status ioctl fd FL_IOCTL_GET_INFO int amp out if status ERROR printf ORs error in ioctl n int errno void close fd check out the out status printf status 0x x n int out status reply data is in out info 91 SR 005 38 7L Rev 1 3 20 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks 9 3 FL_IOCTL_DEFRAGMENT The following code sample describes how to perform a short cycle of the garbage collection process on the DiskOnChip include lt ioLib h gt include lt dosFsLib h gt include lt stdlib h gt include lt stdio h gt include lt errno h gt include fldrvvxw h include filveck lsh typedef union flDefragInput in flDefragOutput out flDefragReq flDefragReq ioctl_regq int fd int status request minimal garbage collection iloctl_req in requiredNoOfSectors long 1 open the DiskOnChip raw device assuming it is dev tffs0 fd open dev tffs0 O_RDWR 0 if fd ERROR printf Ox x error in open n int errno return issue IOCTL call to the driver 91 SR 005 38 7L Rev 1 3 21 LL M Systems
14. 1 0 non removable flash media file name to download Call tffsSetup as appropriate for your application If you want to change the settings of the driver s configuration variables flUse8bit 91 SR 005 38 7L Rev 1 3 32 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks flUseNFTLCache and fl_useDebug do it here and if tffsDrv OK printErr Could not initialize n return ERROR printf Attaching to TFFS dosFsInit NUM_DOSFS_ FILES initialize DOS FS if usrTffsConfig drive 0 fileName ERROR printErr usrTffsConfig failed n return ERROR printErr done n load the boot file printErr Loading s fileName if fd open fileName O_RDONLY 0 ERROR printErr nCannot open Ss n fileName return ERROR if bootLoadModule fd pEntry OK goto tffsLoadErr close fd return OK tffsLoadErr printErr nError loading file status 0x x n errnoGet close fd return ERROR 91 SR 005 38 7L Rev 1 3 33 LL M Systems m Flash Disk Pioneers endif INCLUDE_D code after the line define bootHelp ifdef INCLUDE_FD Using DiskOnChip with VxWorks ISKONCHIP Modify the file Tornado target config all bootConfig c_ by adding the following
15. ENT Background garbage collection FL_IOCTL_WRITE_PROTECT Software write protection of the DiskOnChip FL_IOCTL_BDK_OPERATION Accessing Binary Partition of DiskOnChip Read virtual sectors from DiskOnChip FL_IOCTL_READ_SECTORS Write virtual sectors to DiskOnChip FL_IOCTL_WRITE_SECTORS Note All the data structures in the file flioct1 h are assumed to be packed i e all the members of these data structures are NOT aligned in any way For instance the function sizeof f1DiskInfoOutput should return 55 Sections 9 2 to 9 6 provide sample codes on how an application can issue IOCTL calls to the TrueFFS driver For more information on accessing the Binary Partition on the DiskOnChip refer to Application Note AP DOC 020 Boot Developers Kit 3 For more information on IOCTL calls refer to Application Note AP DOC 046 Extended functions of TrueFFS driver for DiskOnChip 91 SR 005 38 7L Rev 1 3 19 LL M Systems m Flash Disk Pioneers Using DiskOnChip with VxWorks 9 2 FL_IOCTL_GET_INFO The following code sample shows how to obtain general information on the DiskOnChip s flash array include lt ioLib h gt include lt dosFsLib h gt include lt stdlib h gt include lt stdio h gt include lt errno h gt include fldrvvxw h include flioctl h f1DiskInfoOutput out int fd int status open the DiskOnChip raw device
16. LL M Systems m Flash Disk Pioneers Using DiskOnChip with VxWorks 5 3 Configuring RAM Usage By default the TrueFFS driver is configured to store the internal mapping and translation tables in RAM allowing fast I O performance to the DiskOnChip However for high capacity DiskOnChip s the amount of RAM taken by these tables can be significant To minimize RAM usage set the configuration variable flUseNFTLCache_useSCache to zero extern unsigned char flUseNFTLCache Minimize RAM usage flUseNFTLCache 0 U Note The configuration variable 1UseNFTLCache is not related to the issue of unexpected power shutdowns The settings of this variable is purely a matter of I O performance vs RAM usage 5 4 Built in Diagnostics The TrueFFS driver provides built in diagnostics allowing messages issued at critical points of the DiskOnChip operation to be logged into an internal buffer By default the diagnostics feature is disabled but can be enabled by setting the configuration variable f1_useDebug to any non zero value as follows extern int fl_useDebug Enable built in diagnostics fl_useDebug 4 The size of the allocated buffer in KBytes is equal to the numerical value of the 1_useDebug variable in the example above the buffer size will be 4KB The diagnostics buffer will contain C style zero terminated strings that can either be viewed using the debugger or printed on the console at a
17. LL M Systems mma Flash Disk Pioneers Installation Manual IM DOC 022 Using DiskOnChip with VxWorks Written by Esther Spanjer SEP 2000 91 SR 005 38 7L REV 1 3 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks Limited Warranty a M Systems warrants that the Licensed Software prior to modification and adaptation by Licensee will conform to the documentation provided by M Systems M Systems does not warrant that the Licensed Software will meet the needs of the Licensee or of any particular customer of Licensee nor does it make any representations whatsoever about Licensed Software that has been modified or adapted by Licensee b Subsection a above sets forth Licensee s sole and exclusive remedies with regard to the Licensed Software M SYSTEMS MAKES NO OTHER WARRANTIES EXPRESS OR IMPLIED WITH RESPECT TO THE LICENSED SOFTWARE INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE THERE ARE NO OTHER WARRANTIES WITH RESPECT TO THE LICENSED SOFTWARE ARISING FROM ANY COURSE OF DEALING USAGE TRADE OR OTHERWISE IN NO EVENT SHALL M SYSTEMS BE LIABLE TO LICENSEE FOR LOST PROFITS OR OTHER INDIRECT SPECIAL OR CONSEQUENTIAL DAMAGES WHETHER UNDER THIS AGREEMENT IN TORT OR OTHERWISE c Licensee shall not make any promise representation warranty or guaranty on behalf of M Systems with respect to the Licensed Software except as expressly set forth her
18. Tornado target lib lt CPU gt gnuvx a or the BSP object directory Tornado target obj lt CPU gt gnuvx contain the following object modules and if so delete them tffsDrv o nftllite o tffsLib o flflash o dosformt o nfdc2148 0 fatlite o reedsol o Ele L 6 flsocket o flbase o Example To check the contents of the pc486 BSP library 1ib18048 6gnuvx a use the following command ar386 tv libI80486gnuvx a Example To delete the module f1t1 o from the BSP library 1ibI80486gnuvx a use the following command ar386 dv libI80486gnuvx a fltl o Ensure that the BSP configuration H file Tornado target config pc486 config h in case of pc486 BSP excludes the following VxWorks components undef INCLUDE_TFFS include TrueFFS driver for Flash undef INCLUDE _PCMCIA include PCMCIA driver 3 2 Contents of TrueFFS Driver Package The distribution of the TrueFFS driver for VxWorks on x86 compatible platforms consists of the following files MSYSVXW o x86 binary of the TrueFFS driver for VxWorks fldrvvxw h TrueFFS driver s include file flioctl h Extended functionality include file Readme Readme file 91 SR 005 38 7L Rev 1 3 7 LL M Systems m Flash Disk Pioneers Using DiskOnChip with VxWorks MSYSVXW o The object module MSYSVXW o contains the x86 binaries of the TrueFFS driver for VxWorks This object module should be added to the
19. Works If you wish to follow the two step standalone boot scenario refer to Appendix A 5 TrueFFS Driver Run time Configuration Options 5 1 Introduction The TrueFFS driver provides a number of run time configuration options The default settings of these options are adequate for most applications However in some situations it may be required to change these settings All the driver s configuration options are described in detail in Sections 5 2 to 3 3 Note All the configuration variables must be set to the desired values before the initialization routine t ffsDrv 1 is called The value of the configuration variables must NOT be changed after the call to tffsDrv 5 2 8 Bit 32 Bit Access to the DiskOnChip By default the TrueFFS driver accesses the DiskOnChip in 32 bit mode Most platforms are capable of breaking down a single 32 bit cycle into correct sequences of 8 bit access cycles to the DiskOnChip However there are some platforms that don t support this mode and accessing the DiskOnChip in 8 bit mode is required To configure the TrueFFS driver to access the DiskOnChip in 8 bit mode set the configuration variable 1Use8bit to l in your application extern unsigned char flUse8bit Access the DiskOnChip in 8 bit mode filUse8bit 1 Note The DiskOnChip I O performance decreases by 10 20 depending on the platform when the TrueFFS driver is configured to run in 8 bit mode 91 SR 005 38 7L Bav 1 3 AE
20. eeceeeceeeeeeenaeeneeeeaeeneeenseenseessenseeesenseeneeeneseneesees 41 Howto Gontact US ssi cic aR ieee ane ees ee es oe ae A ee ees 42 91 SR 005 38 7L Rev 1 3 1 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks 1 Introduction M Systems DiskOnChip is a family of high performance flash disk DiskOnChip provides a flash disk in several standard form factors s DiskOnChip 2000 Standard 32 pin DIP package single chip flash disk e DiskOnChip Millennium Standard 32 pin DIP package or standard TSOP II 32 pin package single die flash disk s DiskOnChip DIMM2000 Standard 144 pin Small Outline DIMM Dual In line Memory Module flash disk When used under VxWorks the DiskOnChip is managed by TrueFFS True Flash File System a technology based device driver attached to VxWorks dosFS file system Most of VxWorks disk oriented calls including all ANSI C file I O facilities work correctly with the DiskOnChip This installation manual is intended for system integrators designing with the DiskOnChip 2000 DiskOnChip Millennium or DiskOnChip DIMM2000 and describes how the DiskOnChip can be installed as an additional disk or as a boot device under VxWorks In this manual all of the devices described above will be referred to as DiskOnChip A single TrueFFS driver is capable of supporting up to 4 DiskOnChip devices possibly of different types and capacities in parallel The driver is fully re entrant a
21. ein Note The Licensed Software is not warranted to operate without failure Accordingly in any use of the Licensed Software in life support systems or other applications where failure could cause injury or loss of life the Licensed Software should only be incorporated in systems designed with appropriate and sufficient redundancy or back up features 91 SR 005 38 7L Rev 1 3 2 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks Contents DEVE OCU CUN OI oct oa soe os casa eek Ses cae Sepa ect E dees aeons needle cae 5 Hardware Requirements for the DiSKONCHID cccccesseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeneeeeeneeeeeneees 6 Installing the TrueFFS Driver into VXWOPKS cceeeeeeseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeneeneeeeeees 7 3 1 Preparing VXWORKS teseecactarts oct che a aula ua abel ated Wa E E caine 7 3 2 Contents of TrueFFS Driver Package sss eee ee eee 7 3 3 Customizing the TrueFFS Driver cc sese eee 8 3 4 Creating a device for the DiskKONCHiID eee eee eee eee 10 3 5 Configuring dosFs File SySte Ms eee eee eee eee 11 4 Booting VxWorks from the DiskOnChip on an x86 PlatfOrm ccccccesssseeeeeeeeeeeseeeeeeees 12 AN ROO eleien 12 4 2 Requirements for Installation of the DiskKOnChip into VSWOKS eee eee eee 13 4 3 Preparing the DiskOnChip to boot VXWOorkS xes eee eee 13 5 TrueFFS Driver Run time Configuration Options cccccccsseessseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeese
22. he and fl_useDebug do it here RY ELESDEV 3 endif INCLUDE _DISKONCHIPTFEFS ifdef INCLUDE_FORMATTED_IO E 10 Recompile the BOOTROM SYS and copy it to the root directory of the first DiskOnChip Also copy the VxWorks application itself to the DiskOnChip Unless you have a defined DEFAULT_BOOT_LINE different from the one described in step 2 the application should be called vxWorks and it should be located in the root directory of the first DiskOnChip 91 SR 005 38 7L Rev 1 3 40 LL M Systems Using DiskOnChip with VxWorks ms Flash Disk Pioneers Additional Information and Tools Additional information about the DiskOnChip including application notes can be found at http www m sys com Additional tools and documents are listed in the following table Document Tool AP DOC 010 Description Designing with the DiskOnChip DIP AP DOC 020 AP DOC 030 AP DOC 031 AP DOC 039 AP DOC 040 AP DOC 042 AP DOC 046 DiskOnChip 2000 Data Sheet DiskOnChip Millennium Data Sheet DiskOnChip DIMM2000 Data Sheet DiskOnChip Utilities DiskOnChip DIP EVB DiskOnChip GANG Boot Developers Kit Designing with the DiskOnChip Millennium in a RISC Environment Designing with the DiskOnChip Millennium in a PC Environment Programming of the DiskOnChip Millennium TSOP II Programming DiskOnChip Millennium TSOP Using a Bed of Nails Designing the DiskOnChip
23. iskonchips is the number of DiskOnChip devices installed in the system and addressRange is an array of address pairs that restricts the area of scanning Example 1 For instance if the platform allows an installation of up to three DiskOnChips and the regions to search for the DiskOnChips are as follows Oxc8000 Oxd0000 Ist DiskOnChip Oxd0000 Oxd2000 2nd DiskOnChip 91 SR 005 38 7L Rev 1 3 8 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks Oxd2000 0xd4000 3rd DiskOnChip Then the following code fragment should be included in the application include fldrvvxw h address ranges to search for the DiskOnChip long tffsAddresses 0xc8000 Oxd0000 lst DiskOnChip Oxd0000 Oxd2000 2nd DiskOnChip Oxd2000 Oxd4000 3rd DiskOnChip Configure the driver to detect up to three DiskOnChips tffsSetup 3 tffsAddresses In some cases when the DiskOnChip is located at a known address it is required to prevent the TrueFFS driver from performing its scanning routine In such cases both the upper and lower boundary of the search range can be set to the exact DiskOnChip address Example 2 If the DiskOnChip is always installed at address 0xd0000 then the application can instruct the TrueFFS driver to look for the DiskOnChip at that particular address by executing the following code fragments include fldrvvxw h single address to look for a DiskOnChi
24. nChip which is done by calling the routine tffsDevCreate The routine t fsDevCreate can be found in the header file fldrvvxw h and has the following declaration extern BLK_DEV tffsDevCreate int tffsDriveNo int removableMediaFlag where t sDriveNo is the DiskOnChip sequential number zero based The argument removableMediaFlag must always be zero The routine tf fsDevCreate routine returns a pointer of type BLK_DEV which must be saved by the application for later use Example 1 If there is only one DiskOnChip in the system the application should include the following code fragment include fldrvvxw h BLK_DEV tffs_blk_dev tffsDevCreate 0 0 In a system containing three DiskOnChips the code fragment is as follows 91 SR 005 38 7L Rev 1 3 10 LL M Systems m Flash Disk Pioneers Using DiskOnChip with VxWorks include fldrvvxw h BLK DEV tffs_blk_dev 3 NULL NULL NULL L tffs_blk_dev 0 tffsDevCreate 0 0 1st DiskOnChip tffs_blk_dev 1 tffsDevCreate 1 0 2nd DiskOnChip tffs_blk_dev 2 tffsDevCreate 2 0 3rd DiskOnChip Once the devices have been created for every DiskOnChip they must be given names and associated with the file system dosF s This is accomplished by calling the routine dosFsDevInit refer to the VxWorks Reference Manual The parameter that is passed to this routine is a pointer of type
25. nd takes care of all issues related to a multitasking environment thus freeing an application from this task It is assumed that the reader is familiar with the Operating System in use The hardware requirements of the DiskOnChip will be briefly discussed The main part of this installation manual is related to software installation This will include basic driver installation and boot issues 91 SR 005 38 7L Rev 1 3 5 77 E M Systems m Flash Disk Pioneers Using DiskOnChip with VxWorks 2 Hardware Requirements for the DiskOnChip Originally designed for PC environments the DiskOnChip can also be used in different hardware environments The minimum requirements are a 12 bit address bus an 8 bit data bus and three active low control signals CE OE WR Figure 1 below is a drawing of the DiskOnChip and its pins For more detailed information of the DiskOnChip hardware environment refer to the following Application Notes e AP DOC 010 Designing with the DiskOnChip DIP e AP DOC 030 Designing with the DiskOnChip Millennium in a RISC Environment e AP DOC 031 Designing with the DiskOnChip Millennium in a PC Environment Active Low Chip Enable Active Low Output Enable Active Low Write Figure 1 DiskOnChip Pin out 91 SR 005 38 7L Rev 1 3 6 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks 3 Installing the TrueFFS Driver into VxWorks 3 1 Preparing VxWorks Verify that the BSP library
26. neees 14 Diets Tas sle CT ON cae Fes ace Saale ccs pwede ns es ace akan eae ack E EE es ean hoe at ela dat EEES 14 5 2 8 Bit 32 Bit Access to the DiSkKONCHID sss eee eee 14 5 3 Configuring RAM Usage aie tetera ride eee 15 5 4 Built in DIAG OSG Sari 2a acct ea dane eee 15 5 5 Yielding the CPU During Long Flash Operation sese essere eee eee eee 15 6 Formatting the DiskOnChip Under VxWOKKS eceeeeesseeeeeeeeeeeeeeeeaeeeeeeeeeeeeeeesaneeeeeeeees 16 7 Data Integrity on the DiskOnChip sssssseeeessssssseeeeeeessssssereeeeeessssnere resen enen 17 amp Garbage Collectio A ani eira aha t ae Se ck aa a cance daha cc ec eel weno ee ctteecwentee denen 17 9 IOCTL calls to the TrueFFS rivel cccccccsssseeeeeeeeeeeeeesseseeeeeeneeeeeessssseeeeeeeeeseesseeseeeneees 19 Gott ROCUGTION Nc s den Gisecttertes Oi Oe ett lh cht ele Rte che Bed Gries ie Steele ee 19 92 VEL HOC TE GET UNFO T 20 9 3 FL IOCTL DEFRAGMENT asz ee TR REES NRT teak Qeasieh oldies cae esd TET eral 21 9 FE OG HHA TR n PRO TE G see de cy con ead gts goi ce mec erie a a 22 961PE OGTEJBDK OPERATION T 24 9 6 FL_IOCTL_READ_SECTORS and FL_IOCTL_WRITE_SECTORS 91 SR 005 38 7L Rev 1 3 3 LL M Systems m Flash Disk Pioneers Using DiskOnChip with VxWorks 10 Known Problem a a a he A 29 Appendix I Two Step Stand Alone Boot ccccccccsseceeseeneeeeeeeeeeeeeeeeeeeeeeeeesaeeeeeeeeeeeeeeeessneeeeneeees 29 Additional Information and TOols cccccsecccecccecece
27. ny time A pointer to the start of the diagnostics buffer is returned by the routine t sViewDebugLog see fldrvvxw h Note In most cases a value of 2 for the variable 1_useDebug thus allocating 2KB for the diagnostic buffer will suffice 5 5 Yielding the CPU During Long Flash Operation Inherent to flash technology is the need to erase the flash media before new data is written to it The erase operation is done on the fly whenever available media becomes scarce taking typically 91 SR 005 38 7L Rev 1 3 15 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks around 4 milliseconds to complete During an erase operation by default the TrueFFS driver polls the DiskOnChip waiting for the erase operation to complete Alternatively the TrueFFS driver can suspend itself during the erase operation allowing other tasks to use the CPU s resources To instruct the TrueFFS driver to always release the CPU right after starting the erase operation set the configuration variable 1Delay to non zero value extern unsigned char flDelay flDelay unsigned char 1 Note Suspending the TrueFFS driver for a certain amount of clock ticks can affect the write performance of the DiskOnChip This may occur when the TrueFFS driver is not given the CPU right after the specified number of clock ticks but rather be put at the end of the queue of tasks that are waiting for the CPU resource the write perfo
28. orks flWriteProtectReq ioctl_req int EQ int status specify type of operation ioctl_req in type unsigned char FL_UNPROTECT replace the password below with your own iloctl_req in password 0 0x11223344 joctl_regq in password 1 0x55667788 open the DiskOnChip raw device assuming it is dev tffs0 fd open dev tffs0 O_RDWR 0 if fd ERROR printf Ox x error in open n int errno return issue IOCTL call to the driver status ioctl fd FL_IOCTL_WRITE_PROTECT int amp ioctl_regq if status ERROR printf Ox x error in ioctl n int errno void close fd check out the ioctl_regq out status printf status Ox x n int ioctl_req out status 91 SR 005 38 7L Rev 1 3 23 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks 9 5 FL_IOCTL_BDK_OPERATION The code sample below shows how to access the Binary BDK Partition on the DiskOnChip Note For further details on the Binary Partition of the DiskOnChip and its usage refer to Application Note AP DOC 020 Boot Developers Kit include lt ioLib h gt include lt dosFsLib h gt include lt stdlib h gt include lt stdio h gt include lt errno h gt include fldrvvxw h include flioctl h typedef union flBDKOperationInput Thi flOutputStatusRecord out 1BDKOpera
29. ows define DEFAULT _BOOT_LINE tffis 0 0 0 0 host tffs0 vxworks h 90 0 0 3 e 90 0 0 50 u target Note The above code instructs the BOOTROM SYS to look for an application named vxWorks located in the root directory of the device t f fs0 i e first DiskOnChip If it is required to name the application differently or to place it in a different location other than the root directory of the first DiskOnChip change the respective fields in the code 3 Modify the file Tornado target config all bootConfig c by adding the following code after the line define INCLUDE_DISKONCHIP just before the routine usrInit ifdef INCLUDE_DISKONCHIP ifdef _ cplusplus extern C endif ifndef _ASMLANGUAGE include blkIo h TrueFFS driver configuration variables See Section 4 for details extern unsigned char flUse8bit extern unsigned char flUseNFTLCache extern int fl_useDebug if defined __STDC__ defined __cplusplus extern void tffsSetup int diskonchips long addressRange extern STATUS tffsDrv void 91 SR 005 38 7L Rev 1 3 30 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks extern BLK _ DEV tffsDevCreate int tffsDriveNo int removableMediaFlag else _ STDC extern void tffsSetup extern STATUS tffsDrv extern BLK DEV tffsDevCreate endif
30. p long tffsAddresses Oxd0000 Oxd0000 TL configure the driver to detect a single DiskOnChip tffsSetup l tffsAddresses 91 SR 005 38 7L Rev 1 3 9 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks 3 3 2 Configuring the TrueFFS Driver The TrueFFS driver provides configuration options that are described in detail in Section 4 Most applications can use the default settings for these options If it is required to change some of the driver s configuration options you should do so at this stage Example To enable the TrueFFS driver s built in diagnostics refer to Section 5 4 include the following code fragment include fldrvvxw h enable built in diagnostics and allocate 4KB for logging diagnostics messages fl_useDebug 4 Note All the driver s configuration options must be set to the desired values before calling the initialization routine tffsDrv Once the routine t fsDrv has been called the configuration options must NOT be changed 3 4 Creating a device for the DiskOnChip Before a device for each physical DiskOnChip installed in the system can be created the TrueFFS driver must be initialized This is done through a call to the routine t ffsDrv Note The routine t fsDrv should be called only once after the call to routine t fsSetup Normally this is done from usrRoot The next step is to create a device for each DiskO
31. p At the same time it shouldn t be too low as it could effectively block the access to the DiskOnChip for a long time if it is pre empted by other tasks while running Note The garbage collection task should be started after the application has called all the routines mentioned in Section 3 91 SR 005 38 7L Rev 1 3 18 LL M Systems m Flash Disk Pioneers Using DiskOnChip with VxWorks Note The TrueFFS driver performs all the necessary synchronization between multiple tasks that access the DiskOnChip concurrently This means that there is no need for the application to synchronize the garbage collection task with all the other tasks that access the DiskOnChip 9 IOCTL calls to the TrueFFS driver 9 1 Introduction Version 4 1 of the TrueFFS driver for VxWorks allows the user to implement the following new features of the DiskOnChip software e Obtain information on DiskOnChip e Software write protection e Run garbage collection in the background e Access the Binary Partition allowing the user to boot VxWorks on BIOS less systems e Bypass the file system and access the DiskOnChip at virtual sector level These new features are accessible through standard VxWorks IOCTL calls to the TrueFFS driver provided by the API given in the file lioct1 h The following IOCTL calls are supported IOCTL call Usage FL_IOCTL_GET_INFO Obtain information on DiskOnChip FL_IOCTL_DEFRAGM
32. rmance is reduced Furthermore the duration of a clock tick in VxWorks usually 10 msec or 2 5 times longer than the erase operation provides poor granularity for suspending the TrueFFS driver 6 Formatting the DiskOnChip Under VxWorks It is possible to format the DiskOnChip under VxWorks instead of using the standard DiskOnChip DOS utilities DFORMAT EXE In order to format the DiskOnChip under VxWorks the routine t f sDevFormat is called The routine t sDevFormat can be found in the header file 1drvvxw h and has the following declaration extern STATUS tffsDevFormat int tffsDriveNo int arg where t sDriveNo is the DiskOnChip sequential number zero based and arg is a pointer type casted to int tothe struct tffsDevFormatParams containing the parameters of the format call Note A brief description of the fields inthe struct tffsDevFormatParams can be found in the header file fldrvvxw h In most cases the struct tffsDevFormatParams can be initialized using the define TFFS_STD_FORMAT_PARAMS see fldrvvxw h as shown below struct tffsDevFormatParams format_params TFFS_STD_FORMAT_PARAMS Example If there are three DiskOnChips present in the system the application can format each DiskOnChip separately The following code sample formats the first and third DiskOnChip available in the system include fldrvvxw h use standard format parameters
33. s bootsector To access the sectors located before the starting sector of the FAT partition for instance the Master Boot Record the application needs to specify negative sector numbers The code fragment above illustrates how to read the Master Boot Record It sets the parameter rwReq in firstSector tothe 0 hiddenSectors ie negative value 91 SR 005 38 7L Rev 1 3 28 NL M Systems mm Flash Disk Pioneers Using DiskOnChip with VxWorks 10 Known Problem Version 4 1 and up of the TrueFFS driver for VxWorks contains the following known problem e The VxWorks routine dosFsMkfs is incompatible with the original MS DOS FAT volume formats Use the t fsDevFormat routine instead refer to Section 5 TrueFFS Driver Run time Configuration Options for creating dosFs file system structures on the DiskOnChip Refer to Appendix I Two Step Stand Alone Boot 91 SR 005 38 7L Rev 1 3 29 LL M Systems mmm Flash Disk Pioneers Using DiskOnChip with VxWorks Appendix I Two Step Standalone Boot To boot VxWorks two step standalone from the DiskOnChip perform the following 1 Add the following line to the BSP configuration H file i e Tornado target config pc486 config h incase of pc486 BSP define INCLUDE_DISKONCHIP M SYSTEMS TFFS 2 Change the define DEFAULT_BOOT_LINE in the BSP configuration H file i e Target target config pc486 config h incase of pc486 BSP as foll
34. sing DiskOnChip with VxWorks 9 6 FL_IOCTL_READ_SECTORS and FL_IOCTL_WRITE_SECTORS The code sample below demonstrates how to read virtual sectors from a source DiskOnChip and then write these virtual sectors to a target DisknChip include lt ioLib h gt include lt dosFsLib h gt include lt stdlib h gt include lt stdio h gt include lt errno h gt include fldrvvxw h include flioctl h define FL_SECT_SIZE 512 typedef union flReadWritelInput in flReadWriteOutput out flReadWriteReq Assuming char fromVolName is the name of the source TrueFFS volume char toVolName is the name of the target TrueFFS volume E int fdly td2 long sectorsl sectors2 iSect hiddenSectors f1DiskInfoOutput out flReadWriteReg rwReq char buf FL_SECT_SIZE sector buffer 91 SR 005 38 7L Rev 1 3 26 LL M Systems mmm Flash Disk Pioneers Using DiskOnChip with VxWorks get the number of sectors on the source and target TrueFFS volumes Abort is target is smaller then the source X fdl open fromVolName O_RDONLY 0 if fdl ERROR return error if ioctl fdl FL_IOCTL_GET_INFO int amp out ERROR return error sectorsl long out info logicalSectors hiddenSectors long out info sectors fd2 open toVolName O_RDWR 0 if fd2 ERROR
35. system it also becomes more vulnerable to corruption in cases of power failure or unexpected system shutdown It is possible to prevent dosF s from caching the data in RAM by using the option DOS_OPT_CHANGENOWARN refer to Section 3 5 Unfortunately the risk of data corruption at file system level due to power failures or an unexpected system shutdown cannot be reduced to zero Repair of corrupted data structures on file system level such as broken FAT chains or corrupted directory entries can be done by tools similar to CHKDSK in DOS Please contact WindRiver Systems regarding the availability of similar tools for VxWorks 8 Garbage Collection Inherent to flash technology is the need to erase flash media before new data is written to it The process of erasing previously used blocks of flash is known as garbage collection The TrueFFS driver automatically performs a garbage collection whenever there is not enough free space on the media available to complete the write operation This implies that at random times the write operation is delayed due to garbage collection that needs to be performed The result is that the time it takes to write a certain amount of data varies 91 SR 005 38 7L Rev 1 3 17 LL M Systems m Flash Disk Pioneers Using DiskOnChip with VxWorks For most applications it is of minor concern that the length of a write operation varies However there are certain applications that have special req
36. tionReq f1BDKOperationReq ioctl_req int fd int status unsigned char but 522 buffer to read BDK data to write from switch bdkOperation case BDK_WRITE ioctl_req in type unsigned char BDK_WRITE ioctl_reg in bdkStruct bdkBuffer buf loctl_req in bdkStruct length sizeof buf place your BDK data to buf break case BDK_READ 91 SR 005 38 7L Bev 1 3 24 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks iloctl_req in type unsigned char BDK_READ loctl_req in bdkStruct bdkBuffer buf ioctl_reg in bdkStruct length sizeof buf break default add other BDK operations here return open the DiskOnChip raw device assuming it is dev tffs0 fd open dev tffs0 O_RDWR 0 if fd ERROR printf Ox x error in open n int errno return issue IOCTL call to the driver status ioctl fd FL_IOCTL_BDK_OPERATION int amp ioctl_regq if status ERROR printf O0x x error in ioctl n int errno void close fd check out the ioctl_req out status status printf status 0x x n int ioctl_req out status if bdkOperation BDK_READ the returned BDK data is in buf 91 SR 005 38 7L Rev 1 3 25 LL M Systems ms Flash Disk Pioneers U
37. to the VxWorks Reference manual as follows include fldrvvxw h 91 SR 005 38 7L Rev 1 3 11 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks dosFsVolOptionsSet tffs_dosFs_vol tffs_dosFs_vol gt dosvd_options DOS_OPT_CHANGENOWARN where t s_dosFs_vol is a pointer returned by the routine dosFsDevInit Refer to Section 3 4 More detailed information on unexpected power shutdowns can be found in Chapter 7 Note Disabling the file system cache reduces the I O performance of the DiskOnChip 4 Booting VxWorks from the DiskOnChip on an x86 Platform 4 1 Boot Options There are three basic VxWorks boot options supported by the TrueFFS driver s Network boot e One step standalone boot s Two step standalone boot Network boot The bootfile BOOTROM SYS that is located on the DiskOnChip acts as a secondary program loader and uses the network connection to download the VxWorks application from the remote host This scenario is usually used during application development debugging stage One step standalone boot The bootfile BOOTROM SYS includes the application itself This scenario is used for relatively small applications that fit entirely into the first 640KB of RAM Two step standalone boot The bootfile BOOTROM SYS acts as a secondary program loader and loads the application from the DiskOnChip This scenario is used with large VxWorks applications where a one step boot cannot be
38. uirements regarding the write operation s timing In these cases it is possible to provide a separate garbage collection task that runs at a relatively low priority when the system is idle The sole purpose of this task is to perform a garbage collection on the DiskOnChip and guarantee that there will be enough free media available for the next write operation The routine t fsRecycle that provides the garbage collection task can be found in the header file ldrvvxw h and has the following declaration extern STATUS tffsRecycle int volNo int mode where vo1No is the DiskOnChip sequential number zero based and mode is the mode of recycling 0 for single quick garbage collection action and 1 for long full recycling of all dirty flash memory regions Note The second parameter of the routine t ssRecycle has been changed from the number of flash KBytes to recycle to the mode of recycling 0 or 1 from version 4 2 Example If there is only one DiskOnChip in the system then the garbage collection task can be implemented include fldrvvxw h void garbageCollectionTask void while 1 quick recycle action on the first DiskOnChip if tffsRecycle 0 0 OK break sleep for a while 5 ticks taskDelay 5 The priority of the garbage collection task should be slightly lower than the priorities of all the tasks that write read data to from the DiskOnChi
39. utilities diskette or can be downloaded from the M Systems website s Standard VxWorks VXSYS utility e VxWorks bootfile BOOTROM SYS s DOS bootable floppy 4 3 Preparing the DiskOnChip to boot VxWorks If you wish to boot VxWorks from the DiskOnChip either using the network boot the one step standalone or two step standalone boot option follow the steps as described below 1 Boot DOS on the target board from a DOS diskette 2 Reformat the DiskOnChip by running the DOS utility DRORMAT EXE as shown below DFORMAT WIN address S firmware FIRST Y 3 where address is the base address of the DiskOnChip i e D000 D400 and so on and firmware is the DiskOnChip firmware file DOC110 EXB DOC121 EXB and so on 4 Reboot the target system from the DOS diskette and check that the driver letter C was assigned to the DiskOnChip dir C 5 At the DOS prompt run WindRiver s VXSYS utility to write the VxWorks bootstrap code onto the DiskOnChip VXSYS C Another solution to copy the binary image of the DiskOnChip to various target DiskOnChip is through the usage of the GANG programmer For further details refer to DiskOnChip GANG programmer User Manual or contact M Systems 91 SR 005 38 7L Rev 1 3 13 LL M Systems ms Flash Disk Pioneers Using DiskOnChip with VxWorks 6 Copy the file BOOTROM SYS to the root directory of the DiskOnChip At this point the DiskOnChip is ready to boot Vx
40. with Hyundai ARM720 CPU Extended Functions of TrueFFS Driver for DiskOnChip DiskOnChip 2000 Data Sheet DiskOnChip Millennium Data Sheet DiskOnChip DIMM2000 Data Sheet DiskOnChip Utilities User Manual DiskOnChip Evaluation Board DiskOnChip GANG Programmer 91 SR 005 38 7L Rev 1 3 41 LL M Systems m Flash Disk Pioneers How to Contact Us Internet E mail USA Office M Systems Inc 8371 Central Ave Suite A Newark CA 94560 Phone 1 510 494 2090 Fax 1 510 494 5545 Taiwan Office Room B 13th floor No 133 Min Sheng East Road Taipei Taiwan R O C Phone 886 2 87706226 Fax 886 2 87706295 Using DiskOnChip with VxWorks http www m sys com info m sys com Japan Office M Systems Japan Inc Arakyu Bldg 5F 2 19 2 Nishi Gotanda Shinagawa ku Tokyo 141 0031 Phone 81 3 5437 5739 Fax 81 3 5437 5759 U K Office M Systems UK Ltd PO Box 20 Chalgrove SPDO OX44 7YP Phone 44 1865 891 123 Fax 44 1865 891 391 Israel Office M Systems Ltd Atidim Industrial Park P O B 58036 Tel Aviv 61580 Phone 972 3 647 7776 Fax 972 3 647 6668 M Systems assumes no responsibility for the use of the material described in this document Information contained herein supersedes previously published specifications on this device from M Systems M Systems reserves the right to change this document without notice 91 SR 005 38 7L Rev 1 3 42
Download Pdf Manuals
Related Search