THE OCULUS-F/64 FRAME GRABBER User's Manual

Recommendations

Info

Memory Map Size [ 1 ] 8K [ 2 ] 16K [ 3 ] 32K [ 4 ] 64K [ 5 ] 128K [ 6 ] 256K [ 7 ] 512K [ 8 ] 1Mb [ 9 ] 2Mb [ 10 ] 4Mb Enter Selection: 1 DOS MEMORY MAP SETUP EXAMPLE Oculus-F/64 DOS applications are able to use memory mapping in an unused upper memory block (below 1Mbyte) of the host computer. As an example, suppose you want to configure a 64k memory map size starting at address D0000. (Note that PC addressing is often described using the segment portion only, such as D000). The required steps are as follows: • Verify that your computer system BIOS does not shadow the upper memory block that you wish to use. In this example, the block from D0000 to DFFFF must not be shadowed. Please refer to your computer system manual for information on upper memory or adapter BIOS shadowing selection. Page 2-18 The OCULUS-F/64 User's Manual
• Configure your memory manager to not use the memory block you wish to use. As examples, various memory managers are described below. MS-DOS EMM386 (Expanded-Memory Emulator) Modify the command line by adding the exclude option: (i.e. device=EMM386.EXE x=D000-DFFF) 386MAX (Qualitas) Add the following line to the file 386max.pro: RAM = D000-DFFF QEMM-386 (Quarterdeck Expanded Memory Manager-386) Add the following command line option: x=D000-DFFF • Configure the Oculus-F/64 board to use memory mapping at starting address D0 and that the memory map size is 64k. Warning: Errors in memory mapped interfacing configuration can crash your computer system when executing Oculus-F/64 applications. WINDOWS MEMORY MAP SETUP EXAMPLE Oculus-F/64 windows applications such as F64PRO.EXE can utilize memory mapped interfacing, where the memory mapped block is located below the 1 Mbyte boundary or above. The requirements are defined below. Memory Mapping Below 1 Mbyte: In this case all of the setup requirements for DOS applications must be performed, as stated in the previous section. In addition, windows must be made aware of the memory range required, so as to prevent a conflict. For the same example as above where the required memory map block is D0000 to DFFFF, modify SYSTEM.INI (located in your windows directory), as shown below. In SYSTEM.INI under the section [386Enh] add the statement: EMMExclude=D000-DFFF Memory Mapping Above 1 Mbyte: In this case the constraints described for DOS and windows application for memory mapping below 1 Mbyte, do not exist. The only requirement is that there is no physical memory located in the address space that will be used for memory mapping. This includes system memory and memory located on other plug in boards. Additionally, the Oculus-F/64 has an upper limit for the start of the memory mapped block at FFE000 (8k below the 16 Mbyte address) and the memory mapped block can not go above 16 Mbyte. Note that the 16 Mbyte limitation is because the PC ISA 16 bit expansion slot can not address above that boundary. Coreco Inc., Installation and Configuration Page 2-19
Page 1 and 2: THE OCULUS-F/64 FRAME GRABBER User'
Page 3 and 4: Welcome Congratulations on the purc
Page 5 and 6: TABLE OF CONTENTS Welcome..........
Page 7 and 8: • • • • • • • • •
Page 9 and 10: 1.1 INTRODUCTION The Oculus-F/64 is
Page 11 and 12: 1.8 MEMORY The Oculus-F/64 incorpor
Page 13 and 14: The Oculus library of C-callable fu
Page 15 and 16: Part No. DESCRIPTION DRAM expansion
Page 17 and 18: • • • • • • • • •
Page 19 and 20: 2.1 INTRODUCTION This manual assume
Page 21 and 22: CONNECTING THE VGA FEATURE CABLE FO
Page 23 and 24: For simplicity, the following infor
Page 25 and 26: ITEM [ 1 ] CURRENT DEVICE The Curre
Page 27 and 28: Acquistion Sync Source [ 1 ] Camera
Page 29 and 30: SELECTION [ 5 ] DISPLAY VIDEO FORMA
Page 31 and 32: The Memory Format should equal or e
Page 33: I/O addressed communication is the
Page 37 and 38: VGA PassThrough Setup [ 1 ] VGA Mod
Page 39: 2.4 OCULUS INTELLIGENT CONFIGURATIO
Page 42 and 43: Page 3-2 The OCULUS-F/64 User's Man
Page 44 and 45: 3.2 INPUT DB9 1 2 3 4 (Diff) CS VS
Page 46 and 47: 3.2.4 OPTIONAL DIGITAL INPUT ADAPTE
Page 48 and 49: On Oculus-F/64 boards without the o
Page 50 and 51: The VGA Keyer manages the keying of
Page 58 and 59: A.4 CAMERA INPUTS A.5 PROCESSING Fo
Page 60 and 61: A.8 ENVIRONMENTAL CONDITIONS Temper
Page 64 and 65: 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2
Page 66 and 67: J10 - LATTICE FPGA DECODE PROGRAMMI
Page 68 and 69: Coreco Inc., OCULUS-F/64 Index Page
Page 70 and 71: C.2 Analog Video Output Connector P
Page 72 and 73: C.4 VGA Pass-Through Connector Pin
Page 74 and 75: Coreco Inc., OCULUS-F/64 Index Page
Page 78 and 79: E EIA-422 interface, 3-6 F F/64Pro,

THE OCULUS-F/64 FRAME GRABBER User's Manual

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?