Home

HUNT ENGINEERING API for Windows Installation and User Manual

Contents

1. Direct I O on MSDOS Windows 95 or VxWorks In this case the Board Number is associated with the Base Address the Board has been configured to use Windows 95 VxD The first board Board 0 is the first one identified in the Device Manager whatever base address you have set it to Windows NT Kernel Mode Drivers Board 0 is the first Board identified in the Registry N B The current revision of the API does not support more than one Board on Windows NT VME The current release of the API can only support one VME system which can be many cards but only one of them can be accessed by the host Hence the board number is always 0 N B If you have more than one board in your system or you wish to change the default settings for a board install them one after the other Use the board specific chapters as a guideline hwo to install the individual boards 37 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL HEPC2E Installation amp Confidence Check Windows NT Installation The API supports Windows NT V4 0 It has been tested with Service Pack 3 and 4 and without a Service pack but it should work on all varations To install 1 Log in as Administrator onto your NT machine 2 Insert the HUNT ENGINEERING CD 3 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 4 Next sel
2. Go to the Registry gt HEPC2E entry You should see a window that allows you to select Base Address IRQ and DoJtag Set the DoJtag field to No Click OK Reboot the machine and try the confidence checks Note that if this does make the driver load it has not removed the problem of the address clash merely identified what it is You must still find a way to avoid the address clash or else your system may not function correctly Some PCI BIOS have options of whether to reserve IRQs for legacy ISA slots These options are different for different BIOS makes and versions Some BIOSes allocate all IRQ s to PCI slots and none to ISA Change the BIOS setting so that at least 1 IRQ is allocated or reserved for ISA use Or if you have more than 1 ISA board ensure that you have an equivalent number of IRQ s reserved for ISA use If the BIOS allows you to reserve a particular IRQ value for ISA use make sure the value corresponds with the inter rupt jumper setting on the HEPC2E Usually you can access BIOS settings by pressing DEL or F2 very soon after a reboot far 41 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL before the operating system starts to run You would see a message at the bottom of the screen saying something like press DEL to go to setup Please refer to your motherboard s manual if necessaty In the BIOS there is frequently also an option PnP OS Make sure this
3. RING gt Confidence checks and start up the confidence check program Go to Registry If there is a UseMasterMode field or something similar set it to No Click OBR If the program tells you to reboot do so On the HEPC3 HEPC4 HECPCI1 Master Mode is only supported on Comport A One quick way to see if a problem is due to Master Mode is to try a program using Comport B If the program works on Comport B but not on Comport A the problem is probably due to Master Mode If Comport A functions with this set to No and fails with it set to Yes then the problem is confirmed to be related to Master Mode and the PC BIOS should be checked for settings related to Master Mode To find a free IRQ or I O address range in Windows you can use the Start gt Settings gt Control Panel gt System gt Device Manager and double click on computer The various pages then show what resources Windows thinks are being used Again you must be aware that there might be some hardware in the system that Windows does not know about for some reason such as there being no VxD installed If you have any ISA cards in your system if there s no driver installed for that board then Windows doesn t know about the card The ISA card s IRQ and or address may overlap with the TIM 40 carrier s IRQ and or address range Remove unused ISA cards and then try to run the confidence checks again If the ISA card s driver is insta
4. There are three main development tools that are supported by HUNT ENGINEERING which are described in the following sections With a very few exceptions these tools use the API which provides two important benefits They can co exist and rely upon the API to assist in preventing interference New module carriers are automatically supported without any additional work required from the tools provider In addition to those DSP development tools the API can itself be used as a development tool for your system as it provides an easy way to interface programs on your Host computer with programs on your DSPs 3L C4x Parallel C The C4x Parallel C compiler from 3L is based upon the TI C compiler for C4x but provides a system that uses a kernel and loader program to support multiple communicating sequential processes on single or multi processor systems The server provides access to the resources of the host machine via STDIO libraries HUNT ENGINEERING Server Loader The HUNT ENGINEERING Server Loader provides a means to load single sequential programs onto each processor in a system The code can be generated using the TI C compiler assembler Access to the Host machine resources via a STDIO library is provided to the C4x that is connected directly to the host via a comport GO DSP Code Composer The C4x Code Composer product from GO DSP a TI company is an integrated development and debug environment for multiple C4x system
5. This option will open a window that allows you to enter bitstream filenames and FPGA programming options Unconditional Mode Disable Prompting This box is usually ticked If not the hrn_fpga program that is used to do the actual bistream programming will ask you again the slot number board number and bitstream file name Verbose Mode If you want the hrn_fpga program to display verbose information while programming the FPGA click this box Reset the board after FPGA load On some boards eg HEPC9 after programming the FPGA the bitstream will only start to run after a system reset This option tells confchk to do a reset automatically after programming a bit stream if ticked Never use Compressed Format to send bitstream HUNT ENGINEERING supports a compressed bitstream format called Hunt engineering Compressed Bitstream HCB Some typically the latest newer HERON IO and HERON FPGA modules support this format in native mode ie data from the bistream can be sent to the module in HCB format others not typically older or legacy modules If for any reason the FPGA programming using HCB format fails this option allows you to program the FPGA using non compressed data from the bitstream Configure HEART after programming the FPGA Use the following network file Select a network file that you want to run after all FPGAs have been programmed Typically you specify HEART connections between FPGAs in this network fi
6. a Services and Applications Description HEPCS Board address OxDFFEFOOO irg 11 Shared Returning to the previous picture if you find that there is no HUNT ENGINEERING Class or no driver entries hepc9 hepc8 or hepc3 verify if the drivers were copied properly look in c winnt system32 drivers look for hep9awdm sys hep8awdm sys ot hep3bwdm sys If there are no driver files present un install reboot and then re install the HUNT ENGINEERING API If you do find entries in the right hand panel in Computer Management double click on the entry Check that the Device Status is set 22 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL to This device is working properly If not then there is some sort of resource problem that may or may not show up in the event log It may also be that the HERON carrier board is not inserted properly or maybe the gold fingers of the PCI interface are dirty unlikely the case for new boards though In the PC BIOS you may have an ECSD setting Electronic Configuration Setup Data If it exists it must be cleared Clearing this field gives you one 1 chance to install a new board After 1 reboot this ECSD reverts to being set So each time you want to install or re install or re arrange PCI boards you need to clear this ECSD switch again Usually you can access BIOS settings by pressing DEL or F2 very soon after a reboot far
7. etc If this doesn t work remove the associated drivers as well If you still have no progress try to un install the API reboot and re install the API If even this doesn t work try a different PC and or a different operating system if you have any available Uninstall 1 Insert the HUNT ENGINEERING CD 2 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 3 Next select UnInstall Follow the instructions Alternatively you can uninstall via Windows Go to Start gt Settings gt Control Panel then double click on Add Remove Programs Select HUNT ENGINEERING APT and click the Add Remove button Follow the instructions If you want to re install the API first reboot 45 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL HEPC3 HEPC4 HECPCI1 Installation amp Confidence Check Windows XP Installation The API supports Windows XP installing WDM drivers API versions before 1 9 would have installed legacy NT 4 0 drivers It is important to first un install any previous API versions you may have installed To install 1 Log in as Administrator onto your Windows XP machine 2 Windows XP may tell you it has found new hardware Click cancel and do not install the API using Windows hardware wizard for now 3 Insert the HUNT ENGINEE
8. 0 0x280 Board 1 0x320 Board 2 0x340 Board 3 Manually Installing Device Drivers under Windows NT ntapi_setup hep2dkdd registry The ntapi_setup program prompts you to select the following BaseloAddress which can be set to 0x150 0x200 and 0x300 Only these three options are supported by the address jumpers on the HEPC2 M The choice given to ntapi_setup must be the same as the IO address jumper settings on the board Use JTAG which can be set to Y for yes or N for no The yes option is the usual one but the no option can be used to perform some troubleshooting of the Kernel Device Driver loading See the troubleshooting section for instructions BaseJtagAddress which can be set to 0x240 0x280 0x320 or 0x340 The choice given to ntapi_setup must be equal to the JTAG address jumper setting on the board Beware there are several blocks of I O address space that are used for the XDS510 compatible JTAG software as follows Jumper Range 1 Jtag Range 2 Jtag Range 3 Jtag 240 0x240 0x25f 0x640 0x64f 0xa40 0xa4f 280 0x280 0x29f 0x680 0x68f Oxa80 Oxa8f 320 0x320 0x33f 0x720 0x72f 0xb20 0xb2f 340 0x340 0x35f 0x740 0x74f 0xb40 0xb4f Irq which can be set to be 12 or 15 The choice given to ntapi_ setup must be the same as the INT jumper setting on the board Manually Installing Device Drivers under Windows 95 The HEPC2 M cannot be auto detected by Windows 95 so you should 1 Without the board inserted in the machine
9. 33 E UE 34 UNINSTALL a niisiis vice TEELE O vc devtovcves doles SEENEN ee 36 CAN BOARDS INSTALLATION amp CONFIDENCE TEST ccecssssssssssesees 3 7 EN KH GEN LCE 37 BOGE Number eher eet 37 HEPC2E INSTALLATION amp CONFIDENCE CHECK 38 Windows e erennere EE NEE E 38 Windows 2000 Installation ccccccccccccsccccscccsseccescecssesesseeesssecseceessecuseeessseceseeeessecsseeessseeesseeseseesaeeees 38 Windows 95 98 ME Installation ccccccccccccccccsecccscecssecsescessseeccsececsseceeeecseesuseeeessessseseessecsssesessaeesseeees 38 4 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL DOSIS ANA A es 39 The Windows Confidence Check Program 40 TVOUDICSNOOLN EE Ee Ee ENEE 40 Uninstall urna listada tato do A ed hth eat reido 45 HEPC3 HEPC4 HECPCI1 INSTALLATION amp CONFIDENCE CHECK 46 Windows XP EE 46 Windows 2000 Installation cccccccccccccscccccccccssesssccscceceessesssssesccscsessasssscescsesssnsssscceccsssesssasseseceseeseass 46 Windows NT Installation a ii a EE a dei ina 47 Windows 95 98 ME Installation ccccccccccccccccsscsscsccceccsssssscessesccecsesssassesccsesessssssesceseeesessssussesceeseenees 47 DOS ANSTO EE 47 The Windows Confidence Check Program 48 Troubleshooting eent Attert EES ita its 48 Uninstall A d 59 WRITING PROGRAMS THAT USE THE API ccccccscscscscccccccccccccccccescsesereres OO WHEN TO USE THE API gt ii iaa 60 EE 60 INCLUDE SE 60 COMPILE PARAMETER Sra 60 LI
10. C C s include field Compile parameters The HUNT ENGINEERING API library is a multi threaded library Therefore the compiler has to be notified to use multi threading support For example in Visual C C there s a field in Settings where you can select a multi threaded run time library 60 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Libraries The HUNT ENGINEERING API library is a dynamic link library DLL There s one for use with Microsoft Visual C C hendrv dll hendrv lib and Borland C C hebdrv dll hebdrv lib To use the libraries the dll must be in the Windows system directory this will have been done by the installation program You must link your program with the LIB file hendrv lib for Microsoft C C hebdrv lib for Borland 61 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL implementation Issues General The HUNT ENGINEERING API is currently supported on Microsoft PC based Operating systems using the standard Microsoft 32 bit compilers and the Borland 32 bit compiler For legacy systems C4x there s also support for the 16 bit Microsoft compiler Naming Convention In summary the following is a map of the component names heapi h The main API include file heddrv lib MSDOS library hendrv dl1 hendrv lib Win32 Dynamic Link Library DLL Microsoft hebdrv dll hebdrv lib Win32 Dynamic Link Library DLL Borland xxx
11. Code Composer Studio When you are using the Standard PC HAL you may find that Windows will not turn off the power of your PC when you shutdown the system To change this you need to enable Advanced Power Management APM Go to Start gt Control Panel click Performance and Maintenance then Power Options then click the APM tab at the top If your system can support APM you will have the option to enable APM at the Advanced Power Management support tick box If ACPP is not enabled move on to the text below The most common of resource allocation problems on Windows 2000 is interrupts IRQs It is very easy to run out of available interrupts in a PC configuration so the interrupt availa bility may also be a problem for one of the other board types With Windows XP booted you can use Computer Management start gt control panel click on Performance and Maintenance then Administrative Tools Double click Computer Management Open Device Manager then select View gt Resources by type then select the Interrupt request IRQs entry to look at IRQs that are already used If you have any ISA cards in your system if there s no driver installed for that board then Windows XP doesn t know about the card The ISA catd s IRQ and or address may over lap the HERON carrier s IRQ and or address range Remove unused ISA cards and then try to run the confidence checks again If the
12. ENGINEERING APT and click the Add Remove button Follow the instructions If you want to re install the API first reboot 59 HUNT ENGINEERING API WINDOWS Installation User MANUAL Writing Programs that use the API When to use the API The HUNT ENGINEERING API offers a platform independent target independent way of accessing a HUNT ENGINEERING board You can write your own programs that use the API to boot DSP programs onto a board However the Server Loader may provide all functionality you need and you may not have to develop API applications The Server Loader is a HUNT ENGINEERING tool that can boot a network of DSP processors The Server Loader uses a network file that describes what processors must be booted with what file A network file is a simple and short ASCII file ASCII files can be created with for example edit on MS DOS or notepad on Windows In cases where you want the Server Loader to only boot the network and process messages from your DSP application yourself you can use the Server Loader library Please refer to the Server Loader manual for more information Basics The basic principle of the interface to the API is that you gain access to a device that is correctly identified by its board type board number and device type using the HeOpen function This function is the only function that needs to know which device you are accessing so you should provid
13. FOR MS WINDOWS 95 98 ME USING A DOS DON 85 TOOLS FOR MS WINDOWS NT escri GEET ek Sead iia eatin 86 HUNT ENGINEERING Rerver Logder nono nnnnnn nn nono roca nann nono nero cnnaannnes 86 GO DSP Code Composer eessen eiii baste a e i iaa 86 HUNTENCINEERINCGAB E A E E E E AE Ee 86 TOOLS FOR MS WINDOWS NT USING THE DOS BO 86 APPENDIX 4 C4X DEVELOPMENT TOOLS oocconccoooocccononinnonoconcnnnnnannoniscoccnnnns OF Sl OF boos Para EE 87 HUNT ENGINEERING Rerver Logder once nero cnnnnn nono nero ra nana nn none rccnanannnos 87 GC EA e Eeer ha ole su a Sebati ai E 87 HUNT ENGINEERING AB ox cep Betis E EE ee dee EAT 87 BT RCARPOVAIICL EE 87 HUNT ENGINEERING Rerver Logder cnn nono cnnnna nono noc r on anna nn nn nero canaannnos 88 GODSP Codes COM POSEP sini ecb A A A A AA AA 88 HUNTENGINEERINGABES xD ia Se os 88 FOOLS FORMS WINDOWS Ocasion iaa dEede dd Ceg 88 IL CARP AAU Cl EE EE 8 HUNT ENGINEERING Rerver Logder 9 GO DSP Code COMPOST 5 205 toss toe BiB SEE GR EEE aah es hed oe Laz ees ech EE 89 HUNT ENGINEERING APE E ae eiii 9 TOOLS FOR MS WINDOWS 95 USING A DOS BON 89 TOOLS FOR MS WINDOWS NT cccciooosconcissirica nn rie E E dadas 89 ET e ie 9 HUNT ENGINEERING Rerver Logder 90 GO DSP Code COMPOSEr cli edad ege en ege 90 HUNT ENGINEERING APE ox eru ENEE ENEE ENEE 90 TOOLS FOR MS WINDOWS NT USING THE DOS BO 90 6 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL HERON Carriers Installation amp Confiden
14. ISA card s driver is installed it may also be that the hardware IRQ setting on that ISA board is different from the IRQ used by the ISA card s driver Some PCI BIOS have options of whether to allocate IRQs to the PCI slots These options are different for different BIOS makes and versions First it is important to check that the motherboard BIOS has interrupts enabled for the slot the board is in beware the slot num ber is not always obvious Some BIOS require you to allocate a fixed IRQ number in which case you must check that it is an available IRQ that you choose In the BIOS there is frequently also an option PnP OS For a non ACPI system this must have been set to no For ACPI enabled PC s this must have been set to yes If all this fails you have to consider the possibility that there s a clash with another board Remove boards that are not immediately needed such as sound cards network cards etc If this doesn t work remove the associated drivers as well If you still have no progress try to un install the API reboot and re install the API If even this doesn t work try a different PC and or a different operating system if you have any available If you have more than 1 HERON module swap this with the module in slot 1 make sure the boot jumpers are set to boot from FIFO 0 Windows 2000 Just to be sure first verify that the HUNT ENGINEERING API drivers for Windows NT have been copied and h
15. a board type a board number because systems can have more than one board of that type and a device number on that board because a board can have multiple devices associated with it e g ComportA ComportB JTAG Board Number In general boards are numbered starting from 0 but the ordering can be different for different bus types PCI HEPC3 HEPC4 HECPCI1 The order of boards on the PCI Bus is dependent on the PC Motherboard BIOS and Operating System PCI slots are geographically addressed that is the position on the motherboard determines the slot number that is allocated by the system The system may find the board furthest away from the CPU or the one closest to the CPU as the first board NO assumptions can be made based on slot number only that board 1 is the next one after board 0 The reset test program supplied as part of the API is provided to allow the user to identify a particular board by watching its reset LED On the CD in the software api heapi utils directory there is a DOS version of this program apireset exe and a Win32 version called apireset32 exe Run the correct one from a DOS prompt Once the board number is discovered it will stay the same for that particular PC Motherboard BIOS and Operating System combination If the number of boards of the same type fitted to the system is changed the board numbering will have to be re established ISA There are 3 different circumstances for ISA cards
16. amp User MANUAL The rest of the setup process Processor Configuration is as usual At Processor Configuration specify the DSP processors that are on the board Board Properties E 2 x Board Name amp Data File Board Properties Processor Configuration Startup GEL File s Available Processors Processors On Board Init Order TMS320C6x0x gt CPU 1 a TMS 320C6x1 x Add Single SES _ Add Multiple _ Add Multiple _ Bemove Processor Name CPU_2 Identify processors on your board by selecting a processor type from Available Processors changing the Processor Name as required and then select Add Single or Add Multiple Repeat for all processors on your board Next gt Cancel In the final panel Startup GEL File s you can leave all fields empty ax Board Name amp Data File Board Properties Processor Configuration Startup GEL File s CPU Startup GEL File P Cancel Click Finish and the configuration is completed 19 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Manual Configuration of Multiple Boards To configure multiple boards manually simply repeat the Manual Configuration process for each board that you want to debug Code Composer Studio will identify each DSP by a concatenation of board name and DSP name so it is not necessary to use different CPU names for each board Manual Configuration Naming Boards The name you use f
17. and the driver installation is successful then setup will not need to reboot the PC This would be the typical case In case the board is not inserted yet or there s some other such problem setup will reboot once After a reboot the find new hardware wizard will be activated again But this can be very slow In fact setup may continue before new hardware is detected Please make sure not to continue setup while the found new hardware wizard hasn t done its job yet If the new hardware wizard cannot find a driver point to software api on your CD drive After the drivers were installed successfully which may be after a reboot the setup program will confidence check the installation If you upgrade from an earlier API version first un install the old API installation Then reboot the machine Then follow the instructions above Windows NT Installation The API supports Windows NT V4 0 It has been tested with Service Pack 3 and 4 and without a Service pack but it should work on all varations To install 1 Log in as Administrator onto your NT machine 2 Insert the HUNT ENGINEERING CD 3 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 4 Next select Install or Upgrade 5 The InstallShield setup program will now start Follow the directions given by setup The setup progra
18. application with the DOS API all you need to do is copy the files heddrv lib and heapi h from the software api directory on the HUNT ENGINEERING CD into your development directory The Windows Confidence Check Program The setup program will automatically have done a number of confidence checks You can do the confidence checks manually also The Windows Confidence check program is instal led automatically on any Windows version It is started up as follows Start gt Programs gt HUNT ENGINEERING gt Confidence checks As the program starts up it is initialised to access the board defined by the HEAPIJTAG environment variable The setup program has set this variable If you have only 1 board installed Confidence Check will always start initialised to access that 1 board Please refer to the HERON Carriers installation section for a full description of the Confidence Check Program The program works the same regardless of Windows version and board type But note that with the HEPC2E the File gt Interrupt Test entry won t work as this feature is not supported by the HEPC2E hardware Also entries under menu item Registry will now include HEPC2E x This will denote an entry for a HEPC2E driver x 0 1 2 gt H gt Troubleshooting General for all Windows versions If the confidence checks fail please first verify the following 1 The interrupt jumper must be set to the same value you configured the driv
19. boards You can select what boards are in the group using the Group Tools gt Boards in Group menu entry By default confchk puts all automatically detected boards in the group 13 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Boards in Group Select here what boards should be part of the Board Group You can only choose from boards that have been automatically detected Menu entries such as Group Tools gt Reset Group Tools gt JTAG Reset and Code Composer gt AutoConfigure Group use a Board Group as selected defined here Registry This menu is a dynamic menu It finds all the device drivers installed and lets you change the driver options such as Use Master Mode Use Interrupts etc It will show all drivers even those where the accompanying board isn t inserted anymore So be careful Refresh Since the Registry menu is dynamic you may sometimes want to refresh the menu e g after you deleted drivers using the Registry Editor Refresh will search again for all installed drivers HEPC9 x This will denote an entry for a HEPC9 driver x 0 1 2 HEPC8 x This will denote an entry for a HEPC8 driver x 0 1 2 Code Composer AutoConfigure Single This option will try to configure Code Composer Studio Instead of starting Code Composer Studio Setup and adding boards and processors manually this option will try to do this work for you It will work with Code Composer Studio version 1 2 a
20. cancel request immediately However the situation when the drivers are able to continue transferring without enabling interrupts is handled in one of the following two ways Drivers written for fast devices will ignore the cancellation request assuming that the I O will complete quickly However if the application is transferring a large block of data this may be a false assumption which will cause the termination to take a long time to complete In this case the Windows I O manager may complain about the time that is taken Drivers written for slow devices recognise that the time to terminate even a small transfer may be unacceptable so the driver checks for the termination message before each transfer This is inefficient in terms of the transfer but as it is for a slow device the time taken to check for the message each time has little effect on performance Master Mode The HEPC9 support Master Mode Via an option in the confchk program this can be enabled or disabled The install program by default tries to enable Master Mode Sometimes a PC won t work well with the HEPC9 Master Mode The install program will have disabled Master Mode in that case Master Mode transfers can be considerably faster than non Master Mode transfers so Master Mode is something you usually want to have enabled Another advantage of Master Mode is that the CPU is not needed for the actual transfers Thus it is available for other work reduci
21. doesn t work try swapping the TIM 40 carrier board with other PCI boards For the HEPC3 HEPC4 HECPCI1 MasterMode can be set to either enabled or disabled It is enabled by default You can check if the confidence checks work with MasterMode set to disabled You can use start gt programs gt HUNT ENGINEE RING gt Confidence checks and start up the confidence check program Go to Registry If there is a UseMasterMode field or something similar set it to No Click OK Now reboot and run the confidence checks For the HEPC3 HEPC4 HECPCI1 Master Mode is only supported on Comport A One quick way to see if a problem is due to Master Mode is to try a program using Comport B If the program works on Comport B but not on Comport A the problem is probably due to Master Mode If Comport A functions with this set to N and fails with it set to Y then the problem is confirmed to be related to Master Mode and the PC BIOS should be checked for settings related to Master Mode With previous API versions before 1 9 we found that ACPI settings could sometimes be a factor Changing the ACPI settings made a difference for some users but not for all It is too early to say if changing ACPI settings will make any difference with the new WDM drivers that are part of the current API 1 9 and above If you have tried all the above and nothing made any difference try disabling ACPI if you can
22. entries hepc9 hepc8 or hepc3 verify if the drivers were copied properly look in c winnt system32 drivers look for hep9awdm sys hep8awdm sys or hep3bwdm sys If there are no driver files present un install reboot and then re install the HUNT ENGINEERING API If you do find entries in the right hand panel in Computer Management double click on the entry Check that the Device Status is set to This device is working properly If not then there is some sort of resource problem that may or may not show up in the event log It may also be that the TIM 40 carrier board is not inserted properly or maybe the gold fingers of the PCI interface are dirty unlikely the case for new boards though In the PC BIOS you may have an ECSD setting Electronic Configuration Setup Data If it exists it must be cleared Clearing this field gives you one 1 chance to install a new board After 1 reboot this ECSD reverts to being set So each time you want to install or re install or re arrange PCI boards you need to clear this ECSD switch again Usually you can access BIOS settings by pressing DEL or F2 very soon after a reboot far before the operating system starts to run You would see a message at the bottom of the screen saying something like press DEL to go to setup Please refer to your motherboard s manual if necessaty One of the other things to try is another PCI slot Different PCI s
23. event viewer part of Computer Management we just opened above In the System log you find HUNT ENGINEERING driver entries hep9awdm for HEPC9 or hep8awdm for HEPC8 or hep3bwdm for HEPC3 HEPC4 or HECPCI1 Double click on such entries to see what it says If all is well you will only find 2 to 5 entries telling you at what IRQ and memory address es the board has been installed Computer Management El File Action View Window Help e aa E 2 m Computer Management Local CH System Tools E E Event Viewer fa Application H Security Event Properties E System Event E Shared Folders SI Local Users and Groups DEDEN Performance Logs and Alerts Date USAPAN Source hepSawdm z Time 10 35 09 Category None Device Manager Type Information EventID 32796 E Sy Storage 3 Information 3 Information 08 10 2002 10 35 09 hep9awdm 08 10 2002 10 35 09 hep9awdm E Removable Storage User N A os Disk Defragmenter Computer APPLYXP Disk Management EN e Services and Applications Description HEPCS Board address OxDFFEFOOO irq 11 Shared Returning to the previous picture if you find that there is no HUNT ENGINEERING 49 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Class or no driver entries hepc9 hepc8 or hepc3 verify if the drivers were copied properly look in c winnt syst
24. event log to see if the driver has managed to write any problem information there You can find the event log in the event viewer part of Computer Management we just opened above In the System log you find HUNT ENGINEERING driver entries heb2awdm for HERON BASE2 Double click on such entries to see what it says If all is well you will only find 3 entries Computer Management action view e gt om e nle Tree Information 7 6 2005 10 27 38 4M heb2awdm 8 i System Tools G Information 7 6 2005 10 27 38 AM hebZawdm E a Event Viewer Information 7 6 2005 10 27 38 AM hebZawdm 3 Application Event Properties 2 Security Oh System Computer Management Local Event 7 System Information Date 7 6 2005 Source hebZawdm E Zei Performance Logs and Alerts H Shared Folders Time 10 27 Category None Device Manager Type Information EventID 32811 SI Local Users and Groups User NA 7 y Storage Computer CHERRYW2KSP Disk Management Be Disk Defragmenter Description Gi Logical Drives HEBASE2 Board switch 0 SS Removable Storage Ea Services and Applications Returning to the previous picture if you find that there is no HUNT ENGINEERING Class or no driver entries heb2a verify if the drivers were copied properly look in c winnt system32 drivers look for heb2awdm sys If there are no driver files present un install reboot and then re install
25. has been set to no If all this fails you have to consider the possibility that there s a clash with any other board Remove boards that are not immediately needed such as sound cards network cards etc If this doesn t work remove the associated drivers as well If you still have no progress try to un install the API reboot and re install the API If even this doesn t work try a different PC and or a different operating system if you have any available Windows 2000 Just to be sure first verify that the HUNT ENGINEERING API drivers for Windows NT have been copied and have been started To verify that they started start gt settings gt control panel gt Administrative Tools Double click Computer Management Open the System Tools tree and select Device manager Then go to the View menu and make sure that Show hidden devices is enabled Now go the right hand side pane and open Non Plug and Play Drivers Look for an entry like hep2ekda If there are no such entries there at all verify if the drivers have been copied into c winnt system32 drivers look for hep2ekdd sys If there are no driver files present un install reboot and then re install the HUNT ENGINEERING API If you do find entries in the right panel in Computer Management double click on the entry Check that the Device Status is set to This device is working properly If not
26. plugged in properly To be sure take the carrier board out of the PC then remove the slot 1 module and te insert Now te insert the carrier board in your PC and try again Windows XP Just to be sure first verify that the HUNT ENGINEERING API drivers for Windows NT have been copied and have been started To verify that they started start gt control panel click on Performance and Maintenance then Administrative Tools Double click Computer Management Open the System Tools tree and select Device manager On the right hand side you should now see a HUNT ENGINEERING Class entry Open this entry If there are any problems with the driver you ll see a red cross exclamation mark or so over the icon that represents a driver If all is fine you ll just see a diamond shaped icon You will only see the drivers for the boards you installed In the picture on the next page top 3 drivers have been installed for 3 different HUNT ENGINEERING boards 21 HUNT ENGINEERING API WINDOWS Installation User MANUAL Computer Management m Fie Action view Window Help e Am e EI Computer Management Local E E System Tools E E Event Viewer Shared Folders Local Users and Groups g Performance Logs and Alerts a Computer See Disk drives 2 Display adapters 13 DYD CD ROM drives Floppy disk controllers H Floppy disk drives He el e Device
27. re install Windows XP If ACPI is disabled most of the problem solving methods discussed further below may work To verify if ACPI is enabled Use Computer Management as shown before Click Device Manager to view what is listed under the Computer branch The following is the list of supported computer types Possible values for the HAL under Standard computers include ACPI Multiprocessor PC ACPI Uniprocessor PC Advanced Configuration and Power Interface ACPI PC MPS Multiprocessor PC 50 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL MPS Uniprocessor PC Standard PC If you find you ate using any of the first 3 entries then ACPP is enabled on your Windows XP installation The API installation may work if you disable ACPI Unfortunately you cannot just disable AC DU in Windows XP you will need to re install Windows XP To re install Windows XP with ACPI disabled please refer to Microsoft Knowledge Base article Q299340 Related articles are Q197055 Q314088 Q232824 To find to the Microsoft Knowledge Base go to http www microsoft com then select support know ledge Base from the top menu Before you re install Windows check your BIOS for the PNP OS INSTALLED setting Set it to NO or DISABLED If ACPI is enabled Windows XP will use one IRQ usually 9 sometimes 11 for all PCI and all onboard devices in your system IRQ sharing generally is not a big problem fo
28. remove the associated drivers as well If you still have no progress try to un install the API reboot and re install the API If even this doesn t work try a different PC and or a different operating system if you have any available Windows 95 98 ME To check the installation of the HUNT ENGINEERING API related VxD use the Start gt Settings gt Control Panel gt System gt Device Manager to see the entry for Hunt EngClass Clicking on the will show all HuntEngClass VxDs that are loaded Double clicking on one allows you to see if there are any problems which are usually also shown by a yellow mark over the board picture next to the entry If the statement This device is working properly is shown in the general window then the VxD is probably working However do not assume that it is really OK as there may be devices in the machine that do not have VxDs loaded so Windows does not know about them It has also been seen that some devices with VxDs use some resources that they do not declare to Windows In the PC BIOS you may have an ECSD setting Electronic Configuration Setup Data If it exists it must be cleared Clearing this field you one 1 chance to install a new board After 1 reboot this ECSD reverts to being set So each time you want to install or re install or re arrange PCI boards you need to clear this ECSD switch again Usually you can access BIOS settings by pressing DEL or F2 very soon
29. settings gt Control Panel gt system gt device manager gt HuntEngClass to see the entry for HEPC3 Rev B C Clicking on that allows you to select options where you can choose DoMasterMode which can be set to yes or no This selects whether the Kernel Device Driver will attempt to use PCI Master Mode on Comport A The yes option is the usual one but the no option can be used to perform some troubleshooting of the Kernel Device Driver loading See the troubleshhoting section for instructions DoJtag which can be set to yes or no This option is not really of any use in the case of the HEPC3 as the Plug and Play will already have allocated addresses to the JTAG device UseVxd which can be set to yes or no This is useful for tracking down interrupt problems ad the Vxd will ALWAYS use interrupts and the direct access provided by the DLL will NEVER use interrupts See the troubleshhoting section for instructions 80 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL HEV40 4 with Xycom 486 Series VME PC Cards Board Type and Device Number Board Name xahev Devices ComportA Jtag I O Address Order Only 1 device supported at Memory window 0xE000 or where the Environmental variable HEV_OPTIONS points to JTAG Address Order As for I O Address HEV40 4 with Xycom Pentium Series VME PC Cards Board Type and device number Board Name xbhev Devices ComportA Jtag I O Address Order On
30. sure the boot jumpers are set to boot from FIFO 0 Windows 2000 Just to be sure first verify that the HUNT ENGINEERING API drivers for Windows NT have been copied and have been started To verify that they started start gt settings gt control panel gt Administrative Tools Double click Computer Management Open the System Tools tree and select Device manager On the right hand side you should now see a HUNT ENGINEERING Class entry Open this entry If there are any problems with the driver you ll see a red cross exclamation mark or so over the icon that represents a driver If all is fine you ll just see a diamond shaped icon me Action View e Tree E E APPLYWZK Computer F e CD drives f Display adapters zi fa Event Viewer T 5 BE ao Z i Performance Logs and Alerts r wee d Shared Folders Floppy disk drives Device Manager Zi HUNT ENGINEERING Class device Manager i e en e hepc3 Local Users and Groups Y So lt p hepc8 y Storage hepco Disk M f ut a See 3 IDE ATAJATAPI controllers You will only see the drivers for the boards you installed In the above picture 3 drivers have been installed for 3 different HUNT ENGINEERING boards If you find that a driver icon has something superimposed on top of i
31. the HEPC9 if the above doesn t work try if disabling master mode works You can use start gt programs gt HUNT ENGINEERING gt Confidence checks and start up the confidence check program Go to Registry Then go to the HEPC9 0 If there is a Use MasterMode field or something similar set it to No Click OK If the program tells you to reboot do so For the HEPC8 MasterMode must always be set to disabled The most common of resource allocation problems on Windows NT is interrupts IRQs It is very easy to run out of available interrupts in a PC configuration so the interrupt availabi lity may also be a problem for one of the other board types With Windows NT booted you can use the start gt programs gt Administrative tools gt Windows NT Diagnostics to look at the IRQs that are already used If you have any ISA cards in your system if there s no driver installed for that board then Windows NT doesn t know about the card The ISA card s IRQ and or address may ovet lap the HERON carrier s IRQ and or address range Remove unused ISA cards and then try to run the confidence checks again If the ISA card s driver is installed it may also be that the hardware IRQ setting on that ISA board is different from the IRQ used by the ISA card s driver Some PCI BIOS have options of whether to allocate IRQs to the PCI slots These options are different for different BIOS ma
32. the bitstream s file name for the FPGA you want to program You may select either the standard un compressed format rbt or a compressed format hcb 15 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Browse button Use this to browse to the RBT or HCB file of your choice Program FPGA Press this button to ask confchk to program the FPGA with the bit stream that you selected in the RBT File field The hrn_fpga program will be used to actually do the FPGA programming The Detect Detect Group Clear All and Create Configuration File from the above 8 entries all work with all 8 entries Detect Detect all FPGA modules on the current default board Any FPGA modules detected will create an entry filling in the Board No and Slot fields If a previous entry is found with the same Board No and Slot fields the bitstream defined for that entry will be re used Detect Group Detect all FPGA modules on all boards in the Board Group as defined in Group Tools gt Boards in Group Any FPGA modules detected will create an entry filling in the Board No and Slot fields If a previous entry is found with the same Board No and Slot fields the bitstream defined for that entry will be re used Clear All Clear all fields of all 8 entries Create Configuration Description File from the above 8 entries In case you w
33. the first things to try is another PCI slot Different PCI slots may have different resoutces assigned to them Move the HERON carrier board to another unused PCI slot If that doesn t work try swapping the HERON carrier board with other PCI boards For the HEPC9 if the above doesn t work try if disabling master mode works You can use start gt programs gt HUNT ENGINEERING gt Confidence checks and start up the confidence check program Go to Registry Then go to the HEPC9 0 If there is a Use MasterMode field or something similar set it to No Click OR If the program tells you to reboot do so For the HEPC8 MasterMode must always be set to disabled If you have any ISA cards in your system if there s no driver installed for that board then Windows doesn t know about the card The ISA card s IRQ and or address may overlap the HERON carriers IRQ and or address range Remove unused ISA cards and then try to run the confidence checks again If the ISA card s driver is installed it may also be that the hardware IRQ setting on that ISA board is different from the IRQ used by the ISA card s driver Some PCI BIOS have options of whether to allocate IRQs to the PCI slots These options 29 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL are different for different BIOS makes and versions First it is important to check that the motherboard BIOS has interrupts enabled for
34. the slot the board is in beware the slot num ber is not always obvious Some BIOS require you to allocate a fixed IRQ number in which case you must check that it is an available IRQ that you choose In the BIOS there is frequently also an option PnP OS If it s yes try setting it to no or auto If it s no try setting it to yes or auto If all this fails you have to consider the possibility that there s a clash with another board Remove boards that are not immediately needed such as sound cards network cards etc If this doesn t work remove the associated drivers as well If you still have no progress try to un install the API reboot and re install the API If even this doesn t work try a different PC and or a different operating system if you have any available If you have more than 1 HERON module swap this with the module in slot 1 make sure the boot jumpers are set to boot from FIFO 0 Uninstall 1 Insert the HUNT ENGINEERING CD 2 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 3 Next select UnInstall Follow the instructions Alternatively you can uninstall via Windows Go to Start gt Settings gt Control Panel then double click on Add Remove Programs Select HUNT ENGINEERING APT and click the
35. threads will only retry for a limited number of attempts and then stall Once stalled in this way they consume little CPU overhead 64 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL As interrupts are not available the threads will only restart if caused to do so by the application This can happen in one of two ways 1 A call to HeTestIo will detect the corresponding thread is stalled and restart it if the I O is still unable to make progress it will stall again The actual sequence of events is e Test for I O completion e if complete return HE_OK e if not complete restart the I O and return HE_IoInProgress 2 A call to HeWaitForlo will keep restarting the thread every 100ms until the I O is complete Note If for some reason the C40 is not sending receiving data then HeWaitForIo will continue to re awaken the polling loop there is no way to avoid a CPU overhead under these conditions Underlying Models for Windows NT Kernel Mode drivers A few general comments can be made about the Windows NT kernel mode drivers supplied for the use of HUNT ENGINEERING module carriers with the HUNT ENGINEERING API Polled Mode Most boards will use polled mode at some time This is usually done as follows Write a Is there any space in the FIFO if yes go to C b decrease retry counter currently set at 100 go to A c Any space in the FIFO if not go to F d How much space is in the FIFO this depends on
36. to write any problem information there You can find the event log in the event viewer part of Computer Manegement we just opened above In the System log you find HUNT ENGINEERING driver entries hep9awdm for HEPC9 or hep8awdm for HEPC8 or hep3bwdm for HEPC3 HEPC4 or HECPCI1 Double click on such entries to see what it says If all is well you will only find 2 to 5 entries telling you at what IRQ and memory address es the board has been installed Action view gt 0m ele Tree Computer Management Local A Information 08 10 2002 08 46 39 hepSawdm 8 System Tools G Information 08 10 2002 08 46 39 hep9awdm E E Event Viewer Event Properties 8 Application Security Event fi System System Information Date 08 10 2002 Source hep3awdm Z i Performance Logs and Alert Time 08 46 Category None Shared Folders Type Information EventID 32796 A Device Manager User NAA 1 S Local Users and Groups Computer APPLYW2K E ey Storage A Disk Management Description BE Disk Defragmenter ite Board address OxDFFEFOOO irq 9 Shared 33 Logical Drives Returning to the previous picture if you find that there is no HUNT ENGINEERING Class or no driver entries hepc9 hepc8 or hepc3 verify if the drivers were copied properly look in c 1winntlsystem321 drivers look for hep9awdm sys hep8awdm sys 25 HUNT ENGI
37. use the start gt settings gt Control Panel gt system gt device manager and double click on computer The various pages then show what resources Windows 95 thinks are being used You must be aware that there might be some hardware in the system that Windows 95 does not know about for some reason such as there being no VxD installed so some resources may be used even if they appear to be free here 2 Set the board jumpers to use some free resources in your PC 71 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL 3 Power down the PC fit the HEPC2 M and reboot 4 After the machine has booted run the setup program in the software api directory on the HUNT ENGINEERING CD to install the DLLs Under Windows 95 the HEPC2 M never uses VxDs and hence does not require any interrupts The address setting of the Comport devices are selected by the board number parameter as follows 160 0x160 0x179 0 200 0x200 0x219 1 300 0x300 0x319 2 The address setting of the JTAG devices are selected by the board number parameter as follows Jumper Range 1 Jtag Range 2 Jtag Range 3 Jtag Board Number 240 0x240 0x25f 0x640 0x64f Oxa40 0xa4f 0 280 0x280 0x29f 0x680 0x68f Oxa80 Oxa8f 1 320 0x320 0x33f 0x720 0x72f Oxb20 Oxb2f 2 340 0x340 0x35f 0x740 0x74f 0xb40 0xb4f 3 72 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL HEPC2E Board Type and Device Number Board Name h
38. used for installing the drivers This time select the w install option Note that you still have to run ntapi_setup exe for each driver as shown above Manually Installing Device Drivers under Windows 95 The HEPC3 can be auto detected by Windows 95 so you should 1 Power down the PC fit the HEPC3 HEPC4 HECPCI1 and reboot 2 As the machine boots it should say that it has detected new hardware and ask where the drivers are Direct the Windows 95 software to software api directory on the HUNT ENGINEERING CD If the installation complains about not being able to find the file hep3bui dll check that the path shown in blue is software api of the CD and choose OK The file should be found OK the second time 75 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL 3 After the machine has booted run the software api setup program from the HUNT ENGINEERING CD and choose to install the DLLs that are required Choose to install the Microsoft or Borland versions you may install both if required When the drivers ate installed you can use the start gt settings gt Control Panel gt system gt device manager gt HuntEngClass to see the entry for HEPC3 Rev B C Clicking on that allows you to select options where you can choose DoMasterMode which can be set yes or no This selects whether the Kernel Device Driver will attempt to use PCI Master Mode on Comport A The yes
39. you have any available If you have more than 1 HERON module swap this with the module in slot 1 make sure the boot jumpers are set to boot from FIFO 0 Windows NT Just to be sure first verify that the HUNT ENGINEERING API drivers for Windows NT have been copied and have been started To verify that they started start gt settings gt control panel gt devices Look for an entry like hep3bkd If there are no such entries there at all verify if the drivers have been copied into c winnt system32 drivers look for hep3bkdd sys If there are no driver files present un install reboot and then re install the HUNT ENGINEERING API If you do find entries in the Devices panel see what Status and Startup are set to If Startup is not set to Automatic click the StartUp button and select Automatic then click OK Next start the HUNT ENGINEERING device by clicking the Start button If Status is set to Started then the driver is working If not then there is some sort resource problem Or the board is not inserted properly In the PC BIOS you may have an ECSD setting Electronic Configuration Setup Data If it exists it must be cleared Clearing this field you one 1 chance to install a new board After 1 reboot this ECSD reverts to being set So each time you want to install or re install or re arrange PCI boards you need to clear this ECSD switc
40. API installation Then reboot the machine Then follow the instructions above Windows NT Installation The API supports Windows NT V4 0 It has been tested with Service Pack 3 and 4 and without a Service pack but it should work on all varations To install 1 Log in as Administrator onto your NT machine 2 Insert the HUNT ENGINEERING CD 3 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 4 Next select Install or Upgrade 5 The InstallShield setup program will now start Follow the directions given by setup The setup program will try to reboot the PC once After the reboot the setup program will confidence check the installation If you upgrade from an earlier API version first un install the old API installation Then reboot the machine Then follow the instructions above Windows 95 98 ME Installation 1 Insert the HUNT ENGINEERING CD 2 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 3 Next select Install or Upgrade 4 The InstallShield setup program will now start Follow the directions given by setup The setup program will try to reboot the PC once After the reboot the setup program will confidence check the ins
41. Add Remove button Follow the instructions If you want to re install the API first reboot 30 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL HERON BASE2 Installation Confidence Test Installation The HUNT ENGINEERING CD install program will install and confidence check the API for Windows 2000 and XP installations If for any reason you experience problems with installation or confidence checking use this section for a step by step installation check Windows XP Installation The API supports Windows XP installing WDM drivers It is important to first un install any previous API versions you may have installed To install 1 Log in as Administrator onto your Windows XP machine 2 Connect the HERON BASE2 board to the USB cable 3 Windows XP may tell you it has found new hardware Click cancel and do not install the API using Windows hardware wizard for now 4 Insert the HUNT ENGINEERING CD 5 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 6 Next select Install or Upgrade 7 The InstallShield setup program will now start Follow the directions given by setup If the setup program finds the hardware and the driver installation is successful then setup will not need to reboot the PC This would be the typical case In case the bo
42. Address which can be set to 0x200 0x160 and 0x300 Only these 3 options are supported by the address jumpers on the HEPC6A The choice given to ntapi_ setup exe must be the same as the IO address jumper settings on the board Beware there are several blocks of I O address space that are used for the XDS510 compatible JTAG software as follows 200 0x200 0x219 0x240 0x25f 0x640 0x64f Oxa40 Oxa4f 160 0x160 0x179 Ox1a0 Ox1bf Ox5a0 Ox5af 0x9a0 0x9af 300 0x300 0x319 0x340 0x35f 0x740 0x74f 0xb40 0xb4f Use JTAG which can be set to Y for yes or N for no The yes option is the usual one but the no option can be used to perform some troubleshooting of the Kernel Device Driver loading See the Troubleshooting section for instructions Irq which can be set to be 10 11 12 or 15 The choice given to ntapi_setup exe must be the same as the INTS jumper setting on the board 83 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Manually Installing Device Drivers under Windows 95 The HEPCG6A cannot be auto detected by Windows 95 so you should 1 Without the board inserted in the machine use the start gt settings gt Control Panel gt system gt device manager and double click on computer The various pages then show what resources Windows 95 thinks are being used You must be aware that there might be some hardware in the system that Windows 95 does not know about for some reason suc
43. BRARIES naci n 61 IMPLEMENTATION ISSUES 0 ccscscscscscscscscscscscscscscscscscscscscsccscecesesscessescscecsseee D I GENER ATS eene Eeer 62 NAMING CONVENTION A A A EE N EE EAN EE AEAEE 62 IMPLEMENTATION crure E ee ear nee O ee een eee ee 62 ELE E AAA AAA eer eee 62 Windows II ISIME 242 as A ta eebe 62 Windows NT2000 XP Een it tdi Eege lie Mies tbe Ee SE 63 MSDOS E 24 DA E EE 63 IMPLEMENTATION OF ASYNCHRONOUS UO 63 AYDI IATA ANET EE e Ee 63 IC GE 64 UNDERLYING MODELS FOR WINDOWS NT KERNEL MODE DRIVERS 65 Poll EE 65 Interrupts cde Mite e ee e ee Reese MA 65 CONCCHOADIS O Bh ENEE 66 Master MOd Cen i vein Ee biodata tina i 66 THE C6X HOST API EXAMPLE PROGRAMS onnmcccocnconnsnosnncsnccncanocanccanccnacanccnos O7 THE C4X HOST API EXAMPLE PROGRAMS cscsssscssesssessrssscssesssesseesseses OS TECHNICAL SUPPORT egener deeg eege egeree OD APPENDIX 1 C4X BOARD SPECIFIC INFORMATION ses ssresseessrsseee 70 BOARD NUMBER erri cil R E EE il ai tas 70 HEP Ee tse ae eset ose eee eet a Added setae 71 Board Type and Device Number sesiis asrnane e a E EE S EENES 71 Manually Installing Device Drivers under Windows NIT 71 Manually Installing Device Drivers under Windows H 71 HEPC PE cts asnscraeabuced dans T ANEO E O E TNE ON AOE ENTO 73 Board Type and Device AMaumber crac enn enana rain nin 73 Manually Installing Device Drivers under Windows NIT 73 Manually Installing Device Drivers under Windows 03 73 HEP G3 RE
44. CD Added VxDs for Win 95 Several Bug fixes including asynchronous I O fixes for Pll C Winserver Installation completely changed and troubleshooting options added API ver 1 3 VxWorks Support added HEPC6 support added Installation made to use uncompressed files API ver 1 4 HERON support added Board specific information moved to appendices API ver 1 5 HERON VxWorks support added LINUX support added API Doc rev B Complete re organisation of manual for easier navigation API ver 1 6 Support for Serial Bus added API ver 1 7 Support for RTOS 32 added User manual re structured API ver 1 8 Support for HEPC9 added API ver 1 9 Support for Windows 2000 and XP added WDM drivers API ver 1 95 Confidence Checks program update CCS drivers manual install added API ver 1 99 Support for HERON BASE2 added 3 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL TABLE OF CONTENTS REVISION HISTORY EE 3 HERON CARRIERS INSTALLATION amp CONFIDENCE TEST eessen 7 EN VE GEN LEE H Windows E 7 Windows 2000 Installation cccccccccccsccccscecssecesssesssecessceeessessseeeessecesesecsseseseesesseseeeeeesseessseeessesseeeesies Z RE A AAE ETE one decae Cates ec ee A 8 Windows 95 98 ME Installation ccccccccccccccccsccccssesseceescessseccesseeessessseeeessecsseeeessesssesessesssasesesseenseeesies 8 DOSTAS UA A A e e dad 0 9 WINDOWS CONFIDENCE CHECK PROGRAM sssssssseesseessteseeseestsssttsstsstesseessese
45. E Use the other ISA card s manual to find out its IRQ and address range settings If you find an overlap change the IRQ and or address setting on the HEPC2E so that the overlap disappears Be sure to also update the HEPC2E driver with changed the IRQ or address Some PCI BIOS have options of whether to reserve IRQs for legacy ISA slots These options are different for different BIOS makes and versions Some BIOSes allocate all IRQ s to PCI slots and none to ISA Change the BIOS setting so that at least 1 IRQ is allocated or reserved for ISA use Or if you have more than 1 ISA board ensure that you 44 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL have an equivalent number of IRQ s reserved for ISA use If the BIOS allows you to reserve a particular IRQ value for ISA use make sure the value corresponds with the inter rupt jumper setting on the HEPC2E Usually you can access BIOS settings by pressing DEL or F2 very soon after a reboot far before the operating system starts to run You would see a message at the bottom of the screen saying something like press DEL to go to setup Please refer to your motherboard s manual if necessaty In the BIOS there is frequently also an option PnP OS Make sure this has been set to no If all this fails you have to consider the possibility that there s a clash with any other board Remove boards that are not immediately needed such as sound cards network cards
46. HUNT ENGINEERING y mmer e t Chestnut Court Burton Row treme UH Brent Knoll Somerset TA9 4BP UK Tel 44 0 1278 760188 Fax 44 0 1278 760199 Email sales hunteng co uk www hunteng co uk www hunt dsp com HUNT ENGINEERING API for Windows Installation and User Manual Document Rev A API software Rev 1 99 P Warnes J Thie 15 07 05 COPYRIGHT This documentation and the product it is supplied with are Copyright HUNT ENGINEERING 1999 2002 All rights reserved HUNT ENGINEERING maintains a policy of continual product development and hence reserves the right to change product specification without prior warning WARRANTIES LIABILITY and INDEMNITIES HUNT ENGINEERING warrants the hardware to be free from defects in the material and workmanship for 12 months from the date of purchase Product returned under the terms of the warranty must be returned carriage paid to the main offices of HUNT ENGINEERING situated at BRENT KNOLL Somerset UK the product will be repaired ot replaced at the discretion of HUNT ENGINEERING Exclusions If HUNT ENGINEERING decides that there is any evidence of electrical or mechanical abuse to the hardware then the customer shall have no recourse to HUNT ENGINEERING ot its agents In such circumstances HUNT ENGINEERING may at its discretion offer to repair the hardware and charge for that repair Limitations of Liability HUNT ENGINEERING makes no warranty as to the fitness of the prod
47. Installing Device Drivers under Windows NT ntapi_setup hep3bkdd registry ntapi_setup hep4akdd registry ntapi_setup hcpclkdd registry Please note that all three of these choices will install the hep3bkdd sys driver The PCI interfaces of the HEPC3B HEPC4A and HECPCI1 boards are identical and thus the same Kernel Mode Driver can be used The ntapi_setup program prompts you to select the following DoMasterMode which can be set to be Y for yes or N for no This selects whether the Kernel Device Driver will attempt to use PCI Master Mode on Comport A The yes option is the usual one but the no option can be used to perform some troubleshooting of the Kernel Device Driver loading See the troubleshhoting section for instructions After running ntapi_ setup you will be asked to reboot the system This is a good point to power down the machine and insert the HUNT ENGINEERING module carrier Although it s perfectly OK if the board was inserted earlier on If you wish to un install a Kernel Mode Driver simply run ntapi_setup driver remove where driver is hep2dkdd hep2ekdd hep3bkdd hep4akdd hcpclkdd or hep akdd This will remove the entry in the Registry for that driver You need to reboot for any changes to take effect Note that the actual Kernel Mode Drivers are still present e g in your system s winnt systems32 drivers directory To remove all drivers at once you can use the setup exe program on the CD the same as
48. LED setting Set it to NO or DISABLED If ACPI is enabled Windows 2000 will use one IRQ usually 9 sometimes 11 for all PCI and all onboard devices in your system IRQ sharing generally is not a big problem for modern PCI devices However it always affects the performance This is especially noticeable with the JTAG eg with Code Composer Studio When you are using the Standard PC HAL you may find that Windows will not turn off the power of your PC when you shutdown the system To change this you need to enable Advanced Power Management APM Go to Start gt Settings gt Control Panel click Power Management then Power Options then click the APM tab at the top If your system can support APM you will have the option to enable APM at the Advanced Power Management support tick box If ACPT is not enabled move on to the text below The most common of resource allocation problems on Windows 2000 is interrupts IRQs 54 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL It is very easy to run out of available interrupts in a PC configuration so the interrupt availa bility may also be a problem for one of the other board types With Windows 2000 booted you can use the Start gt Programs gt Accessories gt System Tools gt System Information open the tree at Hardware Resources then select the IRQs entry to look at the IRQs that are already used If you have any ISA cards in your sy
49. Manager Go E Storage Vv HUNT ENGINEERING Class Removable Storage YH hepc3 Disk Defragmenter hepc8 Disk Management lt hepco If you find that a driver icon has something superimposed on top of it a red cross an exclamation mark or something else have a look in the event log to see if the driver has managed to write any problem information there You can find the event log in the event viewer part of Computer Management we just opened above In the System log you find HUNT ENGINEERING driver entries hep9awdm for HEPC9 or hep8awdm for HEPC8 or hep3bwdm for HEPC3 HEPC4 or HECPCI1 Double click on such entries to see what it says If all is well you will only find 2 to 5 entries telling you at what IRQ and memoty address es the board has been installed E Computer Management ml Fie Action View Window Help e OB Type Date Time Source 3 Information 08 10 2002 10 35 09 hep9awdm Computer Management Local E CH System Tools E Event viewer G Information 08 10 2002 10 35 09 hep9awdm Application Security Event Properties Hf System Event Date Tale Source hepSawdm Time 10 35 09 Category None Type Information EventID 32796 Shared Folders 2 Local Users and Groups Performance Logs and Alerts z Device Manager E y Storage Removable Storage User NA Sm Disk Defragmenter Computer APPLYXP Disk Management
50. NEERING API WINDOWS Installation amp User MANUAL or hep3bwdm sys If there are no driver files present un install reboot and then re install the HUNT ENGINEERING API If you do find entries in the right hand panel in Computer Management double click on the entry Check that the Device Status is set to This device is working properly If not then there is some sort of resource problem that may or may not show up in the event log It may also be that the HERON carrier board is not inserted properly or maybe the gold fingers of the PCI interface are dirty unlikely the case for new boards though In the PC BIOS you may have an ECSD setting Electronic Configuration Setup Data If it exists it must be cleared Clearing this field gives you one 1 chance to install a new board After 1 reboot this ECSD reverts to being set So each time you want to install or re install or re arrange PCI boards you need to clear this ECSD switch again Usually you can access BIOS settings by pressing DEL or F2 very soon after a reboot far before the operating system starts to run You would see a message at the bottom of the screen saying something like press DEL to go to setup Please refer to your motherboard s manual if necessaty One of the other things to try is another PCI slot Different PCI slots may have different resoutces assigned to them Move the HERON carrier board to another unused PCI slot If t
51. Ox2c Reserved Area should be 00000000x 0 0x30 Expansion ROM base address Oxffbdf800 0x34 Reserved Area should be 00000000x 0 0x38 Reserved Area should be 00000000x 0 Ox3c MAX LAT 0 MIN GNT Oxff Int Pin 0x1 Int Line IRQ 10 58 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Points to watch for are 1 It does not identify a board at all in which case it will report Device not found 2 There are not distinct regions for the IO Base address registers or they overlap this is typically a problem with the PCI BIOS on the PC usually on old systems 3 There should be an IRQ identified that is not used anywhere else on the system Note that some of these parameters are configured by the PC s PCI BIOS The Plug amp Play software on Windows 95 98 ME or the Windows NT I O manager software may te configure these to a different address value They will however be correct for the MSDOS versions of the confidence test and example programs Uninstall 1 Insert the HUNT ENGINEERING CD 2 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 3 Next select UnInstalP Follow the instructions Alternatively you can uninstall via Windows Go to Start gt Settings gt Control Panel then double click on Add Remove Programs Select HUNT
52. PI Uniprocessor PC Advanced Configuration and Power Interface ACPI PC MPS Multiprocessor PC MPS Uniprocessor PC Standard PC If you find you ate using any of the first 3 entries then ACPP is enabled on your Windows 2000 installation The API installation may work if you disable ACPI Unfortunately you cannot just disable AC DU in Windows 2000 you will need to re install Windows 2000 To re install Windows 2000 with ACPI disabled please refer to Microsoft Knowledge 26 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Base article Q237556 Related articles are Q197055 Q216573 Q232824 To find to the Microsoft Knowledge Base go to http www microsoft com then select support know ledge Base from the top menu Before you re install Windows check your BIOS for the PNP OS INSTALLED setting Set it to NO or DISABLED If ACPI is enabled Windows 2000 will use one IRQ usually 9 sometimes 11 for all PCI and all onboard devices in your system IRQ sharing generally is not a big problem for modern PCI devices However it always affects the performance This is especially noticeable with the JTAG eg with Code Composer Studio When you are using the Standard PC HAL you may find that Windows will not turn off the power of your PC when you shutdown the system To change this you need to enable Advanced Power Management APM Go to Start gt Settings gt Control Panel click Power Manage
53. RING CD 4 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 5 Next select Install or Upgrade 6 The InstallShield setup program will now start Follow the directions given by setup If the setup program finds the hardware and the driver installation is successful then setup will not need to reboot the PC This would be the typical case In case the board is not inserted yet or there s some other such problem setup will reboot once After a reboot the find new hardware wizard will be activated again But this can be very slow In fact setup may continue before new hardware is detected Please make sure not to continue setup while the found new hardware wizard hasn t done its job yet If the new hardware wizard cannot find a driver point to software api on your CD drive After the drivers were installed successfully which may be after a reboot the setup program will confidence check the installation If you upgrade from an earlier API version first un install the old API installation Then reboot the machine Then follow the instructions above Windows 2000 Installation The API supports Windows 2000 installing WDM drivers API versions before 1 9 would have installed legacy NT 4 0 drivers It is important to first un install any previous API versions you may have installed T
54. SB 4 if the module has JTAG support 5 if it s a 16 or 32 bit module Register Register with Hunt Engineering This menu entry will attempt to start your email program and prepare a message It will ask Hunt Engineering to add your email address to sr This is an email list that we keep to update users of technical information For example when a new host API or HERON API is released a message will be sent to verybody on the list Options Board Type If you have more than 1 different HUNT ENGINEERING board in your system use this menu item to change the board that you want to test Board Number If you have more that 1 identical HUNT ENGINEERING board in your system use this menu item to change the board number of the board that you want to test Fifo Select here the FIFO or Comport you want to use The HEPC8 has only 1 FIFO FIFO A So if you choose any other FIFO all tests will fail The HEPC9 has 6 FIFOs A to F Slot Select here the slot number you want to do a test on 1 to 4 If there were no module in the slot or not the appropriate module such a test would fail On the HEPC 8 as there s only 1 FIFO connection between the PCI interface and a slot slot 1 Your choice must always be slot 1 Else the confidence tests will always fail With an HEPC9 your choices are 1 to 4 R W Settings With this menu item you can change the parameters of the Reads and Writes test Both the Reads and Writes test use blocks o
55. V BORG ee eene Een 75 Board Type and Device Number eege inicias 75 Manually Installing Device Drivers under Windows NIT 75 Manually Installing Device Drivers under Windows H 75 HEPC4 REVA OR EE 77 5 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Board Type Ind device HUMbDE A AE ESE 77 Manually Installing Device Drivers under Windows NIT 77 Manually Installing Device Drivers under Windows 03 77 TIE CP EE E EG 79 Board Type and device number 79 Manually Installing Device Drivers under Windows NIT 79 Manually Installing Device Drivers under Windows 03 79 HEV40 4 WITH XYCOM 486 SERIES VME PC Capmg 81 Board Type and Device Maumber den e erii i iia beea EE EE EA EEE E Ea 81 HEV40 4 WITH XYCOM PENTIUM SERIES VME PC Capmg 81 Board Type and device number 81 PEOn VME ACCESS duinte ele il lt hip 8l APPENDIX 2 HEPC6 BOARD SPECIFIC INFORMATION ccccccscsssoseee OS TIE PCO REV Aicascces sees Ee Ee osa 83 Board Type and Device Number 83 Manually Installing Device Drivers under Windows NIT 3 Manually Installing Device Drivers under Windows 03 84 APPENDIX 3 C6X DEVELOPMENT TOOLS o ccononcococcccnononsoniscononnnnnonaonincconcnno OD TOOLS FOR MS WINDOWS 95 98 ME scccsseesseessesseeseeeecnsceceaecaeecaeeeseeeeececeeeeseensecesecaeenaecaecseecaeeenes 85 HUNT ENGINEERING Server Logder cnn no a a nono c ron nnnn ah 85 GO DSP EELER 85 HUNT ENGINEERING APE ite ett deent tad ita A3 TOOLS
56. V1 1 it works best with this version 1 3 HUNT ENGINEERING Server Loader There is a Win32 console mode version of the HUNT ENGINEERING Server Loadet which uses the Win32 API Also the Win32 library version of the Server Loader which uses the Win32 API can be linked against a Win32 application In either case this uses the Win32 API which must be installed as described in the installation sections GO DSP Code Composer HUNT ENGINEERING have ported GO DSP s Code Composer NT to theWin32 API and this is the means of supporting Code Composer for Windows NT This uses the Win32 API which must be installed as described in the installation sections HUNT ENGINEERING API For systems running under Windows NT the API provides a stub library file that links with your application to provide that application with all of the standard API interface When your Win 32 application actually runs the Operating system automatically loads a Dynamic Link Library DLL that calls a Kernel Mode Device Driver Kdd for the board you have specified in the HeOpen call If later in the life of your system you choose to change the host board type you simply change the board type identifier given to the HeOpen function You then need to re run the setup program to install the Kdd for that board type if you didn t do so originally and the ntapi_setup program to configure that Kdd If you choose a newly released host board you simply
57. after a reboot far before the operating system starts to run You would see a message at the bottom of the screen saying something like press DEL to go to setup Please refer to your motherboard s manual if necessaty To find a free IRQ or I O address range in Windows you can use the Start gt Settings gt Control Panel gt System gt Device Manager and double click on computer The various pages then show what resources Windows thinks are being used Again you must be aware that there might be some hardware in the system that Windows does not know about for some reason such as there being no VxD installed Similarly the VxDs will try and configure I O address ranges for the JTAG device The installation for the HEPC2E will allow you to select whether you wish to attempt to install the JTAG device This allows you to test if it is one of the JTAG address ranges conflicting by choosing not to install the JTAG device If the VxD is correctly loaded then this proves the problem is a JTAG address conflict If you have any ISA cards in your system if there s no driver installed for that board then Windows NT doesn t know about the card The ISA card s IRQ and or address may over lap the HEPC2E s IRQ and or address range Remove unused ISA cards and then try to run the confidence checks again If the other ISA card s driver is installed it may still be that the hardware settings on that ISA board clash with the HEPC2
58. always obvious Some BIOS require you to allocate a fixed IRQ number in which case you must check that it is an available IRQ that you choose In the BIOS there is frequently also an option PnP OS Make sure this has been set to no With PCI devices they might support Master Mode transfers which can also require careful setting of the PCI BIOS parameters If all this fails you have to consider the possibility that there s a clash with another board Remove boards that are not immediately needed such as sound cards network cards etc If this doesn t work remove the associated drivers as well If you still have no progress try to un install the API reboot and re install the API If even this doesn t work try a different PC and or a different operating system if you have any available If you have more than 1 TIM 40 module swap this with the module in slot 1 Windows 95 98 ME To check the installation of the HUNT ENGINEERING API related VxD use the Start 56 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL gt Settings gt Control Panel gt System gt Device Manager to see the entry for Hunt EngClass Clicking on the will show all HuntEngClass VxDs that are loaded Double clicking on one allows you to see if there are any problems which are usually also shown by a yellow mark over the board picture next to the entry If the statement This device is working properly is sho
59. anagement Zb E m Fie Action view Window Help e gt i B Type Date Time Source D Information 15 07 2005 10 18 26 heb2awdm Se G Information 15 07 2005 10 18 26 heb2awdm BEER QD information 15 07 2005 10 18 26 hebZawdm 5 Security E System Event Properties Shared Folders ERA Local Users and Groups 2 Performance Logs and Alert Date 15 07 2005 Source heb2awdm 3 Device Manager Time 10 18 26 Category None Computer Management Local E i System Tools 2 Ell Event Viewer CH sy Storage Type Information EventID 32811 Removable Storage 8 Disk Defragmenter User N A Disk Management Computer CHERRYWXP Services and Applications Bees E A Description Gee Board switch 10 Returning to the previous picture if you find that there is no HUNT ENGINEERING Class or no driver entries heb2a verify if the drivers were copied properly look in c winnt system32 drivers look for heb2awdm sys If there are no driver files present un install reboot and then re install the HUNT ENGINEERING API If you do find entries in the right hand panel in Computer Management double click on the entry Check that the Device Status is set to This device is working properly If not then there is some sort of resource problem that may or may not show up in the event log Windows 2000 Just to be sure first verify t
60. ard is not connected yet or there s some other problem setup will reboot once After a reboot the find new hardware wizard will be activated again But this can be very slow In fact setup may continue before new hardware is detected Please make sure not to continue setup while the found new hardware wizard hasn t done its job yet If the new hardware wizard cannot find a driver point to software api on your CD drive After the drivers were installed successfully which may be after a reboot the setup program will confidence check the installation The install program will install two drivers for the HERON BASE2 It is possible that you see a Found New Hardware window appear while you install the software Click the Cancel button in the Found New Hardware window if that happens If you upgrade from an earlier API version first un install the old API installation Then reboot the machine Then follow the instructions above Windows 2000 Installation The API supports Windows 2000 installing WDM drivers It is important to first un install any previous API versions you may have installed To install 1 Log in as Administrator onto your Windows 2000 machine 31 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL 2 Connect the HERON BASE2 board to the USB cable 3 Windows 2000 may tell you it has found new hardware Click cancel and do not install the API using Windows hardware wizard for now 4 Insert t
61. ave been started To verify that they started start gt settings gt control panel gt Administrative Tools Double click Computer Management Open the System Tools tree and select Device manager On the right hand side you should now see a HUNT ENGINEERING Class entry Open this entry If there are any 24 HUNT ENGINEERING API WINDOWS Installation User MANUAL problems with the driver you ll see a red cross exclamation mark or so over the icon that represents a driver If all is fine you ll just see a diamond shaped icon Action view e gt am e Tree APPLYW2K Ml Computer Computer Management Local E Disk drives E 5 System Tools E al Event Viewer QJ System Information Zei Performance Logs and Alerts Shared Folders A Device Manager Local Users and Groups E Sy Storage pod Disk Management BE Disk Defranmenter EM Display adapters 23 DYDICD ROM drives 3 Floppy disk controllers amp Floppy disk drives Vv HUNT ENGINEERING Class X hepc3 lt p hepc lt p hepco IDE ATAJATAPI controllers D D You will only see the drivers for the boards you installed In the above picture 3 drivers have been installed for 3 different HUNT ENGINEERING boards If you find that a driver icon has something superimposed on top of it a red cross an exclamation mark or something else have a look in the event log to see if the driver has managed
62. aviour is more general Windows 95 also allows I O and application execution to be overlapped whether the I O is blocked or not This implementation is on two levels Threads Each Read or Write operation is carried out in a separate thread The data for the thread is stored in the structure associated with the HE _IOSTATUS handle and there is a 1 1 correspondence between the number of threads and the number of HE _IOSTATUS handles The thread is not started until the first read or write is initiated but remains until program termination or until HeClose is called for that device When a device is closed any outstanding threads will be terminated If there is I O in progress it will be stopped In order to maintain performance the stop flag is only checked when in the wait loop for the interface If data is always available or being received then the test will not be made The HeClose routine will wait for a time currently 1 minute before timing out and will generate a HE_ThreadTerminationError status code for the close routine If this happens no attempt will be made to terminate any other threads gracefully but they will be deleted by the Operating System on program exit A device should not be closed with active outstanding I O unless there is an error condition e g the processor on the target board has stopped responding In this case the thread will be in the wait loop and will detect the terminate command Retry Limit The
63. before the operating system starts to run You would see a message at the bottom of the screen saying something like press DEL to go to setup Please refer to your motherboard s manual if necessaty One of the first things to try is another PCI slot Different PCI slots may have different resoutces assigned to them Move the HERON carrier board to another unused PCI slot If that doesn t work try swapping the HERON carrier board with other PCI boards For the HEPC9 if the above doesn t work try if disabling master mode works You can use start gt programs gt HUNT ENGINEERING gt Confidence checks and start up the confidence check program Go to Registry Then go to the HEPC9 0 If there is a Use MasterMode field or something similar set it to No Click OK If the program tells you to reboot do so For the HEPC8 MasterMode must always be set to disabled With previous API versions before 1 9 we found that ACPI settings could sometimes be a factor Changing the ACPI settings made a difference for some users but not for all It is too early to say if changing ACPI settings will make any difference with the new WDM drivers that ate part of the current API 1 9 and above If you have tried all the above and nothing made any difference try disabling ACPI if you can re install Windows XP If ACPI is disabled most of the problem solving methods discussed further below may work To v
64. board inserted in the machine use the start gt settings gt Control Panel gt system gt device manager and double click on computer The various pages then show what resources Windows 95 thinks are being used You must be aware that there might be some hardware in the system that Windows 95 does not know about for some reason such as there being no VxD installed so some resources may be used even if they appear to be free here 2 Set the board jumpers to use some free resources in your PC 3 Power down the PC fit the HEPC2E and reboot 4 After the machine has booted run the setup program in the software api directory 73 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL on the HUNT ENGINEERING CD Use the start gt settings gt Add New Hardware menu to select don t search and other devices then HUNT ENGINEERING then HEPC2E Rev B C Notice that there is an option here of HEPC2E Rev B C without JTAG which can be used to diagnose problems with address clashes in the machine See troubleshhoting section for instructions Choose Have Disk and point to software api of the CD Reboot the machine as instructed and then use the start gt settings gt Control Panel gt system gt device manager then click on HuntEngClass and double click on HEPC2E Rev B C Set up the resources menu to reflec
65. ce Test Installation The HUNT ENGINEERING CD install program will install and confidence check the API for Windows 95 98 ME NT W2K and XP installations If for any reason you experience problems with installation or confidence checking use this section for a step by step installation check Windows XP Installation The API supports Windows XP installing WDM drivers API versions before 1 9 would have installed legacy NT 4 0 drivers It is important to first un install any previous API versions you may have installed To install 1 Log in as Administrator onto your Windows XP machine 2 Windows XP may tell you it has found new hardware Click cancel and do not install the API using Windows hardware wizard for now 3 Insert the HUNT ENGINEERING CD 4 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 5 Next select Install or Upgrade 6 The InstallShield setup program will now start Follow the directions given by setup If the setup program finds the hardware and the driver installation is successful then setup will not need to reboot the PC This would be the typical case In case the board is not inserted yet or there s some other such problem setup will reboot once After a reboot the find new hardware wizard will be activated again But this can be very sl
66. cks Note that if this does make the driver load it has not removed the problem of the address clash merely identified what it is You must still find a way to avoid the address clash or else your system may not function correctly Some PCI BIOS have options of whether to reserve IRQs for legacy ISA slots These options ate different for different BIOS makes and versions Some BIOSes allocate all IRQ s to PCI slots and none to ISA Change the BIOS setting so that at least 1 IRQ is allocated or reserved for ISA use Or if you have more than 1 ISA board ensure that you have an equivalent number of IRQ s reserved for ISA use If the BIOS allows you to reserve a particular IRQ value for ISA use make sure the value corresponds with the inter rupt jumper setting on the HEPC2E Usually you can access BIOS settings by pressing DEL or F2 very soon after a reboot far before the operating system starts to run You would see a message at the bottom of the screen saying something like press DEL to go to setup Please refer to your motherboard s manual if necessaty 43 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL In the BIOS there is frequently also an option PnP OS Make sure this has been set to no If all this fails you have to consider the possibility that there s a clash with any other board Remove boards that are not immediately needed such as sound cards network cards etc If this doesn t work
67. ct to use the driver with an extra configuration file then specify the hepod510 cfe configuration file this is located in the c ti drivers directory assuming that you installed CCS into ch 17 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Board Properties 3 Aux Board Name amp Data File Board Properties Processor Configuration Startup GEL File s Board Name ES hep3a 0 Auto generate board data file with extra configuration file y hla aaa C thchiversthepod510 cfa Device Driver Location lc tivdrivers tixds6000 dvr Next gt Cancel When done click the Next button to move to the next panel The I O Port value in this window is used by the HUNT drivers to identify the type and number of the board you use Board Properties TE Board Name amp Data File Board Properties Processor Configuration Startup GEL File s Property Value 0x0 Change property value as necessary in the right column If the board is an HEPC9 with the board switch set to 0 I O port is 0x0 If the board is an HEPC9 with the board switch set to 1 I O port is 0x1 And so on If the board is an HEPC8 with the board switch set to 0 I O port is 0x10 If the board is an HEPC8 with the board switch set to 1 I O port is 0x11 And so on In the picture above a HEPC9 with board switch 0 is shown configured 18 HUNT ENGINEERING API WINDOWS Installation
68. e JTAG wats edit box The value will be used in the Tools gt JTAG Reset menu item Select Driver The default driver to use is the Multi Board driver This is based on the SEPK2 package from Texas Instruments This driver works with Code Composer Studio 2 0 and higher and support debugging multiple boards Other drivers are listed so that if there are any problems with the Multi Board driver there s another CCS driver you can fall back on The Single Board driver will not work with Code Composer Studio 2 2 and higher though You also need to define some environment variables when using the Single Board driver AutoConfig will try to do all the work for you but you do have to make some choices Select a Virtual Port the choices are OxA to OxF Ports OxE and OxF ate typically free and OxA to OxD are typically used by Code Composer Studio Port OxF is the default choice Three drivers are used The first one is pod510 dll which is the HUNT ENGINEERING driver that actually accesses the hardware Secondly there is tixds6000 dvr which is the Texas Instruments CCS driver Third is xdsfast2 dll this interfaces between the other two For Code Composer Studio 1 0 and higher use the bottom entry EM2 Cable Here you can select what 2 channels you use for the File gt EM2 Self Test A cable is used to connect one channel to another in order to create a loop back to itself Data going out from one channel is input
69. e a simple way to alter the details it uses so that a different device can easily be selected if the system requires it This function will not allow you access to a device that is already in use or does not exist If it succeeds then it provides you with a unique handle which you use to identify the device in all future uses Once you have ownership of an open device you can perform reset write and read type accesses to that device The read and write functions use buffers of memory that the data is passed through and there are some memory management issues Allocation and locking that are aided by some API functions The read and write operations are asynchronous that is you start them with a function call which will complete even if the transfer has not completed The API then provides you with some status functions to allow you to track the progress of the transfer This allows but does not force your host based application to overlap the transfer of data with the processing or storage of data Include file All API applications must include lt heapi h gt in all source files that call API functions This include file is located in the root of the API installation directory The install program will have created an environment variable HEAPI_DIR that points to your installation directory Therefore to make sure that the compiler knows where to find heapi h please add this path to Visual C C s or Borland
70. e that connects FIFO out with FIFO in of the same channel self test Data is sent out over FIFO 0 and read back from the same FIFO Four tests are done A bit test where all 32 bits are tested indidually An alternating bit test where buffers with pattern 0x55555555 OxAAAAAAAA 0x55555555 etc are used A byte test where all values in byte 0 1 2 and 3 of a 32 bit word are tested And finally a buffer with random patterns is tested SL Test This test tries to use the Server Loader library to run a simple Server Loader test It parses a default network file resets loads and runs a test Server Loader program on 1 DSP and then tries to serve the test Server Loader program that is running on the DSP The Sever Loader program does some printfs freads fwrites and some other rather standard stdio calls a program might typically want to do Idrom Test This test will work only for C4x boards that have a C4x TIM module inserted THAT HAS AN IDROM This test will fail on HEQUAD modules as they have no IDROM The output of this test is a dump of the IDROM contents Detect Slots This menu entry will list what confchk thinks is in the carrier board s slots It can t know precisely what module is there It can only find out the following 1 if there s a module 10 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL fitted in a slot 2 if the module in a slot is a processor module 3 if the module has a serial bus H
71. ect Install or Upgrade 5 The InstallShield setup program will now start Follow the directions given by setup The setup program will try to reboot the PC once After the reboot the setup program will confidence check the installation If you upgrade from an earlier API version first un install the old API installation Then reboot the machine Then follow the instructions above Windows 2000 Installation The API supports Windows 2000 installing the NT V4 0 drivers as legacy drivers to install 1 Log in as Administrator onto your Windows 2000 machine 2 Insert the HUNT ENGINEERING CD 3 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 4 Next select Install or Upgrade 5 The InstallShield setup program will now start Follow the directions given by setup The setup program will try to reboot the PC once After the reboot the setup program will confidence check the installation If you upgrade from an earlier API version first un install the old API installation Then reboot the machine Then follow the instructions above Windows 95 98 ME Installation 1 Insert the HUNT ENGINEERING CD 2 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click o
72. ection for a full description of the Confidence Check Program The program works the same regardless of Windows version and board type But note that with the HEPC3 HEPC4 HECPCI1 the File gt Interrupt Test entry won t work as this feature is not supported by the HEPC3 HEPC4 HECPCI1 hardware Also entries under menu item Registry will now include HEPC3 x This will denote an entry for a HEPC3 HEPC4 HECPCI1 driver x 0 1 2 gt gt gt Troubleshooting General for all Windows versions If the confidence checks fail please first verify the following 1 Make sure that there is a TIM 40 processor module in slot 1 2 The TIM 40 module in slot 1 must not be a HEQUAD module This module has no IDROM and the confidence checks will fail This is no indication of a problem Also ensure that the TIM 40 module in slot 1 is plugged in properly To be sure take the TIM 40 cartier board out of the PC then remove the slot 1 module te attach the module and re insert the board After re insert verify that the TIM 40 module is still attached to the carrier board properly It is quite common for a non bolted TIM 40 module to loosen whilst the carrier board is being inserted Now restart the PC and try again Windows XP Just to be sure first verify that the HUNT ENGINEERING API drivers for Windows XP have been copied and have been started To verify that they started start gt control panel click on P
73. em32 drivers look for hep9awdm sys hep8awdm sys or hep3bwdm sys If there are no driver files present un install reboot and then re install the HUNT ENGINEERING API If you do find entries in the right hand panel in Computer Management double click on the entry Check that the Device Status is set to This device is working properly If not then there is some sort of resource problem that may or may not show up in the event log It may also be that the TIM 40 cartier board is not inserted properly or maybe the gold fingers of the PCI interface ate dirty unlikely the case for new boards though In the PC BIOS you may have an ECSD setting Electronic Configuration Setup Data If it exists it must be cleared Clearing this field gives you one 1 chance to install a new board After 1 reboot this ECSD reverts to being set So each time you want to install or re install or re arrange PCI boards you need to clear this ECSD switch again Usually you can access BIOS settings by pressing DEL or F2 very soon after a reboot far before the operating system starts to run You would see a message at the bottom of the screen saying something like press DEL to go to setup Please refer to your motherboard s manual if necessaty One of the first things to try is another PCI slot Different PCI slots may have different resources assigned to them Move the TIM 40 carrier board to another unused PCI slot If that
74. ep2e Devices ComportA ComportB Jtag I O Address Order 0x200 Boatd 0 0x160 Board 1 0x300 Board 2 JTAG Address Order As Above since JTAG is a fixed offset from I O Base N B The reason that 0x200 is Board 0 is because 0x200 is the default address setting Manually Installing Device Drivers under Windows NT ntapi_setup hep2ekdd registry The ntapi_setup program prompts you to select the following BaseloAddress which can be set to 0x200 0x160 and 0x300 Only these 3 options are supported by the address jumpers on the HEPC2E The choice given to ntapi_ setup exe must be the same as the IO address jumper settings on the board Beware there are several blocks of I O address space that are used for the XDS510 compatible JTAG software as follows 200 0x200 0x219 Ox 240 0x 25f 0x 640 0x 64f 0x a40 0x a4f 160 0x160 0x179 Ox 1a0 0x 1bf 0x 5a0 Ox 5af Ox 920 0x 9af 300 0x300 0x319 Ox 340 0x 35f 0x 740 0x 74f 0x b40 0x b4f Use JTAG which can be set to Y for yes or N for no The yes option is the usual one but the no option can be used to perform some troubleshooting of the Kernel Device Driver loading See the troubleshooting section for instructions Irq which can be set to be 10 11 12 or 15 The choice given to ntapi_setup exe must be the same as the current INTS jumper setting on the board Manually Installing Device Drivers under Windows 95 The HEPC2E cannot be auto detected by Windows 95 so you should 1 Without the
75. er with 2 The address jumpers must be set to the same value you configured the driver with 3 The TIM 40 module in slot 1 must not be a HEQUAD module This module has no IDROM and the confidence checks will fail This is no indication of a problem Make sure that the board is plugged in properly Also ensure that the TIM 40 module in slot 1 is plugged in properly To be sure take the TIM 40 carrier board out of the PC remove the slot 1 module then te attach and re insert the carrier board After re insert verify that the TIM 40 module is still attached to the carrier board properly It is quite common for a non bolted TIM 40 module to loosen while the carrier board is being inserted Now restart the PC and try again Windows NT Just to be sure first verify that the HUNT ENGINEERING API drivers for Windows NT have been copied and have been started To verify that they started Start gt Settings gt Control Panel gt Devices Look for an entry like hep2ekdd If there are no such entries there at all verify if the drivers have been copied into c winnt system32 drivers look for hep2ekdd sys If there are no driver files present un install reboot and then re install the HUNT ENGINEERING API If you do find entries in the Devices panel see what Status and Startup are set to If Startup is not set to Automatic click the StartUp button and select Automatic then click OK Next start t
76. erformance and Maintenance then Administrative Tools Double click Computer Management Open the System Tools tree and select Device manager On the right hand side you should now see a HUNT ENGINEERING Class entry Open this entry If there are any problems with the driver you ll see a red cross 48 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL exclamation mark or so over the icon that represents a driver If all is fine you ll just see a diamond shaped icon You will only see the drivers for the boards you installed In the picture on the next page top 3 drivers have been installed for 3 different HUNT ENGINEERING boards m Computer Management m Fie Action view Window Help e Mm amp EI Computer Management Local E ii System Tools ES Computer E Event Viewer ep Disk drives Shared Folders EI Display adapters 2 Local Users and Groups 4 DVD CD ROM drives E z Performance Logs and Alerts 4 Floppy disk controllers 2 Device Manager 4 Floppy disk drives E y Storage E Vv HUNT ENGINEERING Class E Removable Storage hepc3 Disk Defragmenter vy hepc8 Disk Management hepcd If you find that a driver icon has something superimposed on top of it a red cross an exclamation mark or something else have a look in the event log to see if the driver has managed to write any problem information there You can find the event log in the
77. erify if ACPI is enabled Use Computer Management as shown before Click Device Manager to view what is listed under the Computer branch The following is the list of supported computer types Possible values for the HAL under Standard computers include ACPI Multiprocessor PC ACPI Uniprocessor PC Advanced Configuration and Power Interface ACPI PC MPS Multiprocessor PC MPS Uniprocessor PC Standard PC If you find you ate using any of the first 3 entries then ACPP is enabled on your Windows XP installation The API installation may work if you disable ACPI Unfortunately you cannot just disable AC DU in Windows XP you will need to re install Windows XP To re install Windows XP with ACPI disabled please refer to Microsoft Knowledge Base article Q299340 Related articles are Q197055 Q314088 Q232824 To find to the Microsoft Knowledge Base go to http www microsoft com then select support know ledge Base from the top menu Before you re install Windows check your BIOS for the PNP OS INSTALLED setting Set it to NO or DISABLED 23 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL If ACPI is enabled Windows XP will use one IRQ usually 9 sometimes 11 for all PCI and all onboard devices in your system IRQ sharing generally is not a big problem for modern PCI devices However it always affects the performance This is especially noticeable with the JTAG eg with
78. f Ox 640 0x 64f Ox a40 Ox a4f 160 0x160 0x179 Ox 1a0 0x 1bf Ox 5a0 Ox 5af Ox 9a0 0x 9af 300 0x300 0x319 Ox 340 0x 35 0x 740 0x 74f Ox b40 0x b4f Interrupt Request which can be set to be 10 11 12 or 15 The choice give to this program MUST be the same as the current INTS jumper setting on the board The Options menu offers UseVxd which can be set to yes or no This is useful for tracking down interrupt problems as the VxD will ALWAYS use interrupts and the direct access provided by the DLL will NEVER use interrupts See the troubleshooting section for instructions DoJtag which can be set to yes or no The yes option is the usual one the zo option can be used to perform some troubleshooting of the VxD loading See the troubleshooting section for instructions 84 HUNT ENGINEERING API WINDOWS Installation User MANUAL Appendix 3 C6x Development tools There are three main development tools that are supported by HUNT ENGINEERING which are described in the following sections With a very few exceptions these tools use the API which provides two important benefits They can co exist and rely upon the API to assist in preventing interference New module carriers are automatically supported without any additional work required from the tools provider In addition to those DSP development tools the API can itself be used as a development tool for your system as it provides an easy way to interface programs on you
79. f data that are transferred between the DSP processor and the host PC First a block of size Start is transferred Then a block of size Start Increment Then Start 2 Increment And so on until End is reached The blocks are send sub divided in smaller blocks of size Block Size Therefore Start Increment and End must all be multiples of Block Size Show JTAG regs When doing a JTAG reset Tools gt JTAG Reset there is an option of showing the JTAG registers This can be helpful verifying that JTAG interface works properly To switch on this option enable Show JTAG registers upon reset It is disabled by default Timing When doing the Confidence Checks in the File menu the program uses a timeout to decide when it s about time the DSP should have read or written data Use this menu item to change the timeout settings C4x Select Select what C4x processor type you wish to use in a test You can choose between a C40 which has 6 comports or a C44 which has 4 comports You can also tell confchk that you wish to use AutoSelect Then confchk will first query the module in slot 1 whether it is a C40 or a C44 AutoSelect will not work on a HEQUAD module In such cases deselect AutoSelect and tick the C44 button 11 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL HERON Select Select here what HERON type you have At the time of writing there s t
80. fer data If after a number of retries the device is unable to transfer data then the routine will save the current I O context and return HE _IoInProgress At this time the poll operation is suspended Subsequent calls to HeTestIo will restart the I O operation and will either return HE OK if it is able to complete the I O or HE_IoInProgress if it also reaches the retry limit again Every subsequent call to HeTestIo will repeat this A call to HeWaitForIo will restart the I O every time it reaches the retry limit and will ONLY return when the I O is complete or there is an error This technique allows the application developer to wait for ever for I O to complete or have the opportunity of carrying out other tasks and retrying the operation later Note If the retry limit is never reached because the device is able to keep up with the I O requests then the HeWrite or HeRead operation will continue to do I O Le this is not true asynchronous behaviour only application execution and blocked I O are overlapped This technique satisfies most requirements for asynchronous behaviour Windows 95 On Windows 95 if there is no VxD installed correctly or if the API is instructed not to use a VxD the API will perform direct I O to the board In this case the API does not use interrupts so it is necessary to use a poll loop waiting for I O to be available Although the Windows 95 implementation of asynchronous beh
81. function You then need to re run the setup program to install the VxD for that board type if you did not do so originally If you choose a newly released host board you simply install the new API version and the DLL is updated and the VxD installed for you ready for the application to use Tools for MS Windows 95 using a DOS box Under Windows 95 the DOS box can operate in the same way as described under the MSDOS section of this manual However care must be taken when using tools or applications that access the Module carrier directly as conflict can occur between a program using direct access and any other program accessing the Module carrier Note The Windows 95 DOS box is used for both DOS programs and Win32 Console mode applications If you are using both DOS applications and Win32 console mode applications then you should ensure there is no confusion as to which type is used Tools for MS Windows NT This section is considering Win32 programs when running under Windows NT 3L C4x Parallel C 3L have ported the Win32 version of their TIS server to the HUNT ENGINEERING API 89 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL This uses the Win32 API which must be installed as described in the installation sections Refer to the relevant 3L technical note for instructions on its installation and use with your Module carrier but do not be concerned about the fact that the 3L options menu says API
82. h again Usually you can access BIOS settings by pressing DEL or F2 very soon after a reboot far before the operating system starts to run You would see a message at the bottom of the screen saying something like press DEL to go to setup Please refer to your motherboard s manual if necessaty Different PCI slots may have different resources assigned to them One thing to try is to 55 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL move the carrier board to other unused PCI slots If that doesn t work you can try swapping the carrier board with other PCI boards If a PCI driver appears to be loaded correctly but one of the programs described in the example programs section fails then it could be related to Master Mode being incorrectly set up For the HEPC3 HEPC4 HECPCI1 MasterMode can be set to either enabled or disabled It is enabled by default You can check if the confidence checks work with MasterMode set to disabled You can use start gt programs gt HUNT ENGINEE RING gt Confidence checks and start up the confidence check program Go to Registry If there is a UseMasterMode field or something similar set it to No Click OK Now reboot and run the confidence checks For the HEPC3 HEPC4 HECPCI1 Master Mode is only supported on Comport A One quick way to see if a problem is due to Master Mode is to try a program using Comport B If the p
83. h as there being no VxD installed so some resources may be used even if they appear to be free here Set the board jumpers to use some free resources in your PC Power down the PC fit the HEPC6A and reboot After the machine has booted run the setup program in the software api directory on the HUNT ENGINEERING CD Use the start gt settings gt Add New Hardware menu to select don t search and other devices then HUNT ENGINEERING then HEPC6A Rev A Notice that there is an option here of HEPCG6A Rev A without JTAG which can be used to diagnose problems with address clashes in the machine See the troubleshooting section for instructions Choose Have Disk and point to software api of the CD Reboot the machine as instructed and then use the start gt settings gt Control Panel gt system gt device manager then click on HuntEngClass and double click on HEPC6A Rev A Set up the resources menu to reflect your hardware settings as follows The Base address of the HEPC6A which can be set to 0x200 0x160 and 0x300 The choices given to this program MUST be the same as the current IO address jumper settings on the board Beware there ate several blocks of I O address space that are used for the XDS510 compatible JTAG software as follows Jumper Rangel Base I O Range 2 Jtag Range 3 Jtag Range 4 Jtag 200 0x200 0x219 Ox 240 0x 25
84. happens only once once you run the FPGA test a local copy of the bitstream is kept in the c heapi directory HEART Test With this test the confchk program will program HEART to create a loop Data is sent out over a FIFO and read back from the same FIFO Four tests are done A bit test where all 32 bits are tested indidually An alternating bit test where buffers with pattern 0x55555555 OxXAAAAAAAA 0x55555555 etc are used A byte test where all values in byte 0 1 2 and 3 of a 32 bit word are tested And finally a buffer with random patterns is tested EM2 Self Test With this test the confchk program will program HEART to create a loop a loop via an EM2 assuming a cable that connects 2 channels Via Options gt EM2 cable you can specify the out channel and the in channel Due to the way the EM2 cables are made you cannot send to and receive from the same channel Data is sent out over channel FIFO X and read back from channel FIFO Y where X is not equal to Y and X Y A F Four tests are done A bit test where all 32 bits are tested indidually An alternating bit test where buffers with pattern 0x55555555 OxAAAAAAAA 0x55555555 etc are used A byte test where all values in byte 0 1 2 and 3 of a 32 bit word are tested And finally a buffer with random patterns is tested EM1 Self Test With this test the confchk program will program HEART to create a loop a loop via the EM1 assuming a cabl
85. hat doesn t work try swapping the HERON carrier board with other PCI boards For the HEPC9 if the above doesn t work try if disabling master mode works You can use start gt programs gt HUNT ENGINEERING gt Confidence checks and start up the confidence check program Go to Registry Then go to the HEPC9 0 If there is a Use MasterMode field or something similar set it to No Click OR If the program tells you to reboot do so For the HEPC8 MasterMode must always be set to disabled With previous API versions before 1 9 we found that ACPI settings could sometimes be a factor Changing the ACPI settings made a difference for some users but not for all It is too early to say if changing ACPI settings make any difference with the new WDM drivers that are part of the current API 1 9 and above If you have tried all the above and nothing made any difference try disabling ACPL if you are in the position that you can re install Windows 2000 If ACPP is enabled most of the problem solving methods discussed further below will work To verify if ACPI is enabled Go to Start gt Settings gt Control Panel gt System Click the Hardware tab and then click Device Manager to view what is listed under the Computer branch The following is the list of supported computer types Possible values for the HAL under Standard computers include ACPI Multiprocessor PC AC
86. hat the HUNT ENGINEERING API drivers for Windows 2K have been copied and have been started To verify that they started start gt settings gt control panel gt Administrative Tools Double click Computer Management Open the System Tools tree and select Device manager On the right hand side you should now see a HUNT ENGINEERING Class entry Open this entry If there are any problems with the driver you ll see a red cross exclamation mark or so over the icon that represents a driver If all is fine you ll just see a diamond shaped icon 34 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL You will only see the drivers for the boards you installed In the picture below 2 drivers have been installed for 2 different HUNT ENGINEERING boards Action View e et am 2 EI Tree a OC MM Computer Management Local i 2 ae sd i Disk drives E ES System Tools ig Jr Pi Evenk Viader Display adapters ES i 9 224 DYD CD ROM drives QJ System Information i En Floppy disk controllers E Zi Performance Logs and Alerts d Floppy disk drives Shared Folders Ts Ely HUNT ENGINEERING Class a Device Manager gt is lt p hebase2 7 Local Users and Groups Kb henco al Sa Sknrane Y epc If you find that a driver icon has something superimposed on top of it a red cross an exclamation mark or something else have a look in the
87. he HERON1 and the HERON4 But more may be added such as an HERON2 Mote typically however it is usual to use the AutoSelect feature This will ask confchk to use the serial bus HSB to query the module The module will then supply information what type it is Older modules may not support HSB and in such cases this option may be useful Use dma The standard DSP test programs are very simple programs They use direct I O access with the FIFO s and fit fully in internal DSP memory This is on purpose The confidence tests are solely to test whether the drivers are installed properly and work as expected But once this stage is past it may be useful to try a DSP BIOS program In addition what can be tested is whether a DSP program running using cache and external memory can be booted and will work whether the HERON API works with the host FIFO and what kind of I O speeds can be achieved using a DSP BIOS program Show Errors This menu item serves to help when you encounter data errors when doing the Reads test By default the Reads only tells you it succeeded or it failed But with this menu item in the case of data errors you can configure Reads to show what data was erroneous where JTAG wait Some PC s are too fast The JTAG accesses are simple accesses without the possibility to check whether JTAG data is valid The only option if accesses are too fast is to insert a small wait loop before the access Specify a wait period in th
88. he HUNT ENGINEERING device by clicking the Start button If Status is set to Started then the driver is working 40 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL If not then there is some sort resource problem Or the board isn t inserted properly In the PC BIOS you may have an ECSD setting Electronic Configuration Setup Data If it exists it must be cleared Clearing this field you one 1 chance to install a new board After 1 reboot this ECSD reverts to being set So each time you want to install or re install or re arrange PCI boards you need to clear this ECSD switch again Usually you can access BIOS settings by pressing DEL or F2 very soon after a reboot far before the operating system starts to run You would see a message at the bottom of the screen saying something like press DEL to go to setup Please refer to your motherboard s manual if necessaty The most common of resource allocation problems on Windows NT is interrupts IRQs It is very easy to run out of available interrupts in a PC configuration so the interrupt availabi lity may also be a problem for one of the other board types With Windows NT booted you can use the Start gt Programs gt Administrative Tools gt Windows NT Diagnostics to look at the IRQs that are already used If you have any ISA cards in your system if there s no driver installed for that board then Windows NT doesn t know about t
89. he HUNT ENGINEERING CD 5 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 6 Next select Install or Upgrade 7 The InstallShield setup program will now start Follow the directions given by setup If the setup program finds the hardware and the driver installation is successful then setup will not need to reboot the PC This would be the typical case In case the board is not connected yet or there s some other problem setup will reboot once After a reboot the find new hardware wizard will be activated again But this can be very slow In fact setup may continue before new hardware is detected Please make sure not to continue setup while the found new hardware wizard hasn t done its job yet If the new hardware wizard cannot find a driver point to software api on your CD drive After the drivers were installed successfully which may be after a reboot the setup program will confidence check the installation The install program will install two drivers for the HERON BASE2 The first driver is installed automatically the Hardware Wizard will install the second driver During installation the install program will halt and ask you to press a button when the Hardware Wizard has completed In some cases the Hardware Wizard may run so fast that you hardly see the window at all but i
90. he Watcom compiler This is not on the HUNT CD but we can provide it via our technical support Windows Confidence Check Program The setup program will automatically have done a number of confidence checks You can do the confidence checks manually also The Windows Confidence check program is instal led automatically on any Windows version It is started up as follows Start gt Programs gt HUNT ENGINEERING gt Confidence checks As the program starts up it is initialised to access the board defined by the HEAPIJTAG or HEAPIHSB environment variable The setup program has set this variable If no SDK is installed only HEAPIHSB is defined The confchk program will use this variable If the SDK is also installed HEAPIJTAG is also defined The confchk program will then use this variable If you have only 1 board installed Confidence Check will start initialised to access that 1 board What follows is an explanation of the different menu items of the program File Menu Interrupt Test On HERON boards the Interrupt Test has four possible results Interrupts work fine Interrupts disabled Interrupt test failed or interrupt test failed due to a driver problem The first two results indicate that the API works properly When you receive an Interrupt test failed message please refer to the Troubleshooting section on how to solve such problems The fourth message indicates that the API was not installed prope
91. he card The ISA card s IRQ and or address may over lap the HEPC2E s IRQ and or address range Remove unused ISA cards and then try to run the confidence checks again If the other ISA card s driver is installed it may still be that the hardware settings on that ISA board clash with the HEPC2E Use the other ISA card s manual to find out its IRQ and address range settings If you find an overlap change the IRQ and or address setting on the HEPC2E so that the overlap disappears Be sure to also update the HEPC2E driver with changed the IRQ or address To do this you must run the confidence check program supplied as part of the HUNT ENGINEERING API Start gt Programs gt HUNT ENGINEERING gt Confidence checks Go to the Regis try gt HEPC2E entry You should see a window that allows you to select Base Address IRQ and DoJtag Set the Base Address and IRQ fields as required Click OK Reboot the machine and try the confidence checks The HEPC2E requires a large range of I O addresses when configured with JTAG device enabled this can prevent the driver from loading if there is an I O addtess clash It is easy to test if this is the problem as you can configure the Windows NT driver to disable JTAG access to see if the driver then loads To do this you must run the confidence check program supplied as part of the HUNT ENGINEERING API Start gt Programs gt HUNT ENGINEERING gt Confidence checks
92. he relevant 3L technical note for instructions on its installation and use with your Module carrier but don t be concerned about the fact that the 3L options menu says API V1 1 it works best with this version 1 3 88 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL HUNT ENGINEERING Server Loader There is a Win32 console mode version of the HUNT ENGINEERING Server Loadet which uses the Win32 API Also the Win32 library version of the Server Loader which uses the Win32 API can be linked against a Win32 application In either case this uses the Win32 API which must be installed as described in the installation sections GO DSP Code Composer HUNT ENGINEERING have ported GO DSP s Code Composer NT to the Win32 API and this is the recommended version of Code Composer for Win95 This uses the Win32 API which must be installed as described in the installation sections HUNT ENGINEERING API For systems running under Windows 95 the API provides a stub library file that links with your application to provide that application with all of the standard API interface When your Win 32 application actually runs the Operating system automatically loads a Dynamic Link Library DLL that tries to call a VxD driver for the board you have specified in the HeOpen call If later in the life of your system you choose to change the host board type you simply change the board type identifier given to the HeOpen
93. ice Driver and it will be used by hendrv d11 to provide support for the board to the application The application program must not access the VxD directly This DLL is the same one as used on Windows XP 2000 and NT and detects if Windows 95 or Windows NT or Windows 2000 XP is being used 62 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Windows NT 2000 XP The are two categories of support on Windows NT native WIN32 applications and DOS programs Windows NT is available on a number of hardware platforms Intel MIPS PowerPC and Alpha AXP Only the Intel version of Windows NT is currently supported Windows NT WIN32 Applications must be linked with hendrv d11 either by calling the DLL directly or by linking the application against hendrv lib There is a Windows NT 2000 XP Kernel Mode Driver supplied for each of the HUNT ENGINEERING board types supported by this release of the API The Kernel Mode Driver is used by hendrv dll to provide support for the board to the application The application program must not access the driver directly MSDOS In this case we are talking about standard MSDOS 6 x not a DOS box on Windows 95 or Windows NT It may be that those platforms will allow the DOS program to execute but this is not the recommended way of using the API on those platforms Support for MSDOS is in the form of a library heddrv lib which is linked with the MSDOS program Only legacy boards ate supported 1e C4x
94. ing any of the first 3 entries then ACPP is enabled on your Windows 2000 installation You could try if the API works with ACPI disabled Unfortunately you 42 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL cannot just disable AC DU in Windows 2000 you will need to re install Windows 2000 To re install Windows 2000 with ACPI disabled please refer to Microsoft Knowledge Base article Q237556 Related articles are Q197055 Q216573 Q232824 To find to the Microsoft Knowledge Base go to http www microsoft com then select support know ledge Base from the top menu The most common of resource allocation problems on Windows 2000 is interrupts IRQs It is very easy to run out of available interrupts in a PC configuration so the interrupt availa bility may also be a problem for one of the other board types With Windows 2000 booted you can use the Start gt Programs gt Accessories gt System Tools gt System Information open the tree at Hardware Resources then select the IRQ entry to look at the IRQs that are already used If you have any ISA cards in your system if there s no driver installed for that board then Windows NT doesn t know about the card The ISA card s IRQ and or address may over lap the HEPC2E s IRQ and or address range Remove unused ISA cards and then try to run the confidence checks again If the other ISA card s driver is installed it may still be
95. install the new API version and the DLL is updated and the Kdd installed for you ready for the application to use Tools for MS Windows NT using the DOS box Under Windows NT the DOS box is used for both DOS programs and Win32 Console mode applications Win32 console mode applications should be built using the Win32 API DOS applications linked against the MSDOS version of the API will NOT work under Windows NT though they do on Windows 95 90 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL
96. is correct If the value in the Setting column is different select the Change Setting button and choose a value that equals the interrupt jumper setting on your HEPC2E Then select the next field in the Resource type column Input Output Range If the first value of the range in the Setting column equals the jumper settings for the address on the HEPC2E then the setting is correct click OK to complete If not then click the Change Setting button and find the range that corresponds with the address jumper set ting on your HEPC2E Do the same with the other 2 address range entries Click OK To verify range settings please have a look at the HEPC2E table in Appendix The setup program will try to reboot the PC once After the reboot the setup program will confidence check the installation If you upgrade from an earlier API version first un install the old API installation Then reboot the machine Then follow the instructions above DOS Installation The API supports DOS 6 x systems by providing a 1ib file to directly link an application to Although applications using this support can work in DOS windows and Windows 95 this is not the recommended way 39 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL There is no installation program for DOS support to use an application that is already linked to the DOS API you do not need to install anything If you wish to link an
97. ish to create 1 file with all the FPGA s listed that you want to program press this button The file is just an ASCII file that you can edit in any ASCII compatible editor on Windows for example NotePad or on LINUX for example vi A Configuration Description File is useful if you have more than 8 FPGA modules you need to program This button helps you start set up such a file Use Configuration Description File You can choose between two programming styles Program Direct or Use Configuration Description File With the Program Direct style you program each FPGA individually With the Configuration Description File you list in an ASCII file all the FPGA s you want to program Browse Use this to browse and select an existing Configuration Description File Edit Use this to edit an existing or create a new Configuration Description File Program FPGA This will use hrn_fpga to program each FPGA entry in the selected Configuration Description File HEART Configure HEART This option will start a window that allows you to select and execute up to 4 different con figurations A HEART configuration is an ASCII file where you list all FIFO links between the different modules on a HEART board such as the HEPC9 A HEART configuration file is essentially a Server Loader network file except that any processors will not be booted by the heartconf utility that is used to actually do the HEART configuration Config
98. kes and versions First it is important to check that the motherboard BIOS has interrupts enabled for the slot the board is in beware the slot num ber is not always obvious Some BIOS require you to allocate a fixed IRQ number in which case you must check that it is an available IRQ that you choose In the BIOS there is frequently also an option PnP OS Make sure this has been set to no 28 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL If all this fails you have to consider the possibility that there s a clash with another board Remove boards that are not immediately needed such as sound cards network cards etc If this doesn t work remove the associated drivers as well If you still have no progress try to un install the API reboot and re install the API If even this doesn t work try a different PC and or a different operating system if you have any available If you have more than 1 HERON module swap this with the module in slot 1 make sure the boot jumpers are set to boot from FIFO 0 Windows 95 98 ME To check the installation of the HUNT ENGINEERING API related VxD use the Start gt Settings gt Control Panel gt System gt Device Manager to see the entry for Hunt EngClass Clicking on the will show all HuntEngClass VxDs that are loaded Double clicking on one allows you to see if there are any problems which are usually also shown by a yellow mark over the board
99. lation section for a full description of the Confidence Check Program The program works the same regardless of Windows version and board type Troubleshooting General for all Windows versions If the confidence checks fail you can try the following 1 Disconnect the USB cable wait 5 seconds or so then reconnect 2 Disconnect the USB cable power down the HERON BASE2 wait a little power the board back on and reconnect the USB cable If you have multiple USB connectors on your PC try another connector 4 Make sure that you have a module inserted in at least 1 HERON BASE2 slot If you use multiple HERON BASE2 boards make sure all have a different red switch setting If you find that the bandwidth performance is lower than you expected say less than 4 Mb s make sure that you use a proper USB 2 0 port If the HERON BASE2 is connected to a USB 1 1 port the bandwidth will be much lower Windows XP Just to be sure verify that the HUNT ENGINEERING API drivers for Windows XP have been copied and have been started To verify that they started start gt control panel click on Performance and Maintenance then Administrative Tools Double click Computer Management Open the System Tools tree and select Device manager a Computer Management B Fie Action view Window Help e zl EN Computer Management Local E System Tools al Event Viewer Shared Folders E Local Users and Group
100. le Use the Browse button to select an existing network file and or use Edit to create a new template network file or view a current one You can run HeartConf in verbose mode by ticking the Verbose HeartConf check box Program Direct You can choose between two programming styles Program Direct or Use Configuration Description File With the Program Direct style you program each FPGA individually With the Configuration Description File you list in an ASCII file all the FPGA s you want to program There are 8 entries where you can define bitstreams Each entry has 4 fields that you must select They are board type Board board number No slot number Slot and bitstream Board Select board type Rotate through supported boards by clicking on the button At the moment of writing supported boards are the HEPC9 hep9a and HEPC8 hep8a Note that with the Detect button and Detect Group button below you can let confchk fill in this field for you No Type here the board number ie red switch value of the board where the FPGA module is located Note that with the Detect button and Detect Group button below you can let confchk fill in this field for you Slot Type here the slot number of the board where the FPGA module is located Note that with the Detect button and Detect Group button below you can let confchk fill in this field for you RBT or HCB File Fill in here
101. leshooting of the Kernel Device Driver loading See the troubleshhoting section for instructions After running ntapi_ setup you will be asked to reboot the system This is a good point to power down the machine and insert the HUNT ENGINEERING module carrier Although it s perfectly OK if the board was inserted earlier on If you wish to un install a Kernel Mode Driver simply run ntapi_setup driver remove where driver is hep2dkdd hep2ekdd hep3bkdd hep4akdd hcpclkdd or hep akdd This will remove the entry in the Registry for that driver You need to reboot for any changes to take effect Note that the actual Kernel Mode Drivers are still present e g in your system s winnt systems32 drivers directory To remove all drivers at once you can use the setup exe program on the CD the same as used for installing the drivers This time select the w install option Note that you still have to run ntapi_setup exe for each driver as shown above Manually Installing Device Drivers under Windows 95 The HEPCI1 can be auto detected by Windows 95 so you should 1 Power down the PC fit the HEPC3 HEPC4 HECPCI1 and reboot 2 As the machine boots it should say that it has detected new hardware and ask where the drivers are Direct the Windows 95 software to software api directory on the HUNT ENGINEERING CD If the installation complains about not being able to find the file hep3bui d11 check that the path shown in blue is software a
102. lled it may also be that the hardware IRQ setting on that ISA board is different from the IRQ used by the ISA card s driver Some PCI BIOS have options of whether to allocate IRQs to the PCI slots These options are different for different BIOS makes and versions First it is important to check that the motherboard BIOS has interrupts enabled for the slot the board is in beware the slot num 57 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL ber is not always obvious Some BIOS require you to allocate a fixed IRQ number in which case you must check that it is an available IRQ that you choose In the BIOS there is frequently also an option PnP OS If it s yes try setting it to no or quenty p Y y g auto If it s no try setting it to yes or auto If all this fails you have to consider the possibility that there s a clash with another board Remove boards that are not immediately needed such as sound cards network cards etc If this doesn t work remove the associated drivers as well If you still have no progress try to un install the API reboot and re install the API If even this doesn t work try a different PC and or a different operating system if you have any available If you have more than 1 TIM 40 module swap this with the module in slot 1 hep3diag The hep3diag program is run from a simple DOS prompt i e not from a Windows NT DOS window and it does the f
103. lled you can use the start gt settings gt Control Panel gt system gt device manager gt HuntEngClass to see the entry for HEPC3 Rev B C Clicking on that allows you to select options where you can choose DoMasterMode which can be set yes or no This selects whether the Kernel Device Driver will attempt to use PCI Master Mode on Comport A The yes option is the usual one but the no option can be used to perform some troubleshooting of the Vxd loading See the troubleshhoting section for instructions DoJtag which can be set to yes or no This option is not really of any use in the case of the HEPC3 as the Plug and Play will already have allocated addresses to the JTAG device UseVxd which can be set to yes or no This is useful for tracking down interrupt problems ad the Vxd will ALWAYS use interrupts and the direct access provided by the DLL will NEVER use interrupts See the troubleshhoting section for instructions When the drivers are installed you can use the start gt settings gt Control Panel gt system gt device manager gt HuntEngClass to see the entry for HEPC3 Rev B C Clicking on that allows you to select options where you can choose DoMasterMode which can be set to yes or no This selects whether the Kernel Device Driver will attempt to use PCI Master Mode on Comport A The yes option is the usual one but the no
104. llow the user to identify a particular board by watching its reset LED On the CD in the software api heapi utils directory there is a DOS version of this program apireset exe and a Win32 version called apireset32 exe Run the correct one from a DOS prompt Once the board number is discovered it will stay the same for that particular PC Motherboard BIOS and Operating System combination If the number of boards of the same type fitted to the system is changed the board numbering will have to be re established There are 3 different circumstances for ISA cards Direct I O on MSDOS Windows 95 or VxWorks In this case the Board Number is associated with the Base Address the Board has been configured to use Windows 95 VxD The first board Board 0 is the first one identified in the Device Manager whatever base address you have set it to Windows NT Kernel Mode Drivers Board O is the first Board identified in the Registry N B The current revision of the API does not support more than one Board on Windows NT The current release of the API can only support one VME system which can be many cards but only one of them can be accessed by the host Hence the board number is always 0 70 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL HEPC2 M Board Type and Device Number Board Name hep2d Devices ComportA Jtag I O Address Order 0x150 Board 0 0x200 Boatd 1 0x300 Board 2 JTAG Address Order 0x240 Board
105. lots may have different resoutces assigned to them Move the TIM 40 cartier board to another unused PCI slot If that doesn t work try swapping the TIM 40 carrier board with other PCI boards For the HEPC3 HEPC4 HECPCI1 MasterMode can be set to either enabled or disabled It is enabled by default You can check if the confidence checks work with MasterMode set to disabled You can use start gt programs gt HUNT ENGINEE RING gt Confidence checks and start up the confidence check program Go to Registry If there is a UseMasterMode field or something similar set it to No Click OK Now reboot and run the confidence checks 53 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL For the HEPC3 HEPC4 HECPCI1 Master Mode is only supported on Comport A One quick way to see if a problem is due to Master Mode is to try a program using Comport B If the program works on Comport B but not on Comport A the problem is probably due to Master Mode If Comport A functions with this set to N and fails with it set to Y then the problem is confirmed to be related to Master Mode and the PC BIOS should be checked for settings related to Master Mode With previous API versions before 1 9 we found that ACPI settings could sometimes be a factor Changing the ACPI settings made a difference for some users but not for all It is too early to say if changing ACPI settings make an
106. ly 1 device supported at Memory window 0xE000 or where the environmental variable HEV_OPTIONS points to JTAG Address Order As for I O Address PC on VME Access Using one of the Xycom PC on VME cards or one from another manufacturer that handles the VME interface in a similar way it is possible to use the API to access the HEV40 4 PC operating systems do not have any standard support for VME busses so the PC on VME cards have to implement their own method of allowing access to the VME address space HUNT ENGINEERING have tested the API with two types of PC on VME cards from Xycom as follows 486 series These boards provide some registers that allow you to map a 64Kbyte page of the VME address space into the memory map of the PC HUNT ENGINEERING provides a utility xahevset exe which allows you to configure a memory window to access the HEV40 4 For information on how to use this software see the readme file in the software boards hev404 xycom directory of the HUNT ENGINEERING CD Pentium series These boards interface to the VME bus using a PCI to VME bridge chip Universe that provides a window onto the VME bus using PCI accesses HUNT ENGINEERING provide a utility xbhevset exe which allows you to configure a memory window to access the HEV40 4 For information on how to use this software see the readme file in the software boards hev404 xycom directory of the HUNT ENGINEERING CD The HEV40 4 cannot be auto detected b
107. ly released host board you simply install the new API version and the DLL is updated and the VxD installed for you ready for the application to use Tools for MS Windows 95 98 ME using a DOS box Under Windows 95 the DOS box can operate in the same way as described under the MSDOS section of this manual However care must be taken when using tools or applications that access the Motherboard directly as conflict can occur between a program using direct access and any other program accessing the Module carrier 85 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Note The Windows 95 DOS box is used for both DOS programs and Win32 Console mode applications If you are using both DOS applications and Win32 console mode applications then you should ensure there is no confusion as to which type is used Tools for MS Windows NT This section is considering Win32 programs when running under Windows NT HUNT ENGINEERING Server Loader There is a Win32 console mode version of the HUNT ENGINEERING Server Loader which uses the Win32 API Also the Win32 library version of the Server Loader which uses the Win32 API can be linked against a Win32 application In either case this uses the Win32 API which must be installed as described in the installation sections GO DSP Code Composer HUNT ENGINEERING have ported GO DSP s Code Composer WIN32 drivers to the Win32 API and this is the means of supporting Code Composer for Wind
108. m will try to reboot the PC once After the reboot the setup program will confidence check the installation If you upgrade from an earlier API version first un install the old API installation Then reboot the machine Then follow the instructions above Windows 95 98 ME Installation 1 Windows may tell you it has found new hardware Click cancel and do not install the API using Windows hardware wizard for now 2 Insert the HUNT ENGINEERING CD 3 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 4 Next select Install or Upgrade 8 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL 5 The InstallShield setup program will now start Follow the directions given by setup The setup program will try to reboot the PC once After the reboot the setup program will confidence check the installation If you upgrade from an earlier API version first un install the old API installation Then reboot the machine Then follow the instructions above DOS Installation There is no DOS support for HERON Carriers The current HERON carriers are all accessed via high memory highest quartile in a 4Gb address space and cannot be accessed with MS DOS You would need a DOS extender to reach that range of addresses We have some experimental DOS extender support using DOS4GW and t
109. ment then Power Options then click the APM tab at the top If your system can support APM you will have the option to enable APM at the Advanced Power Management support tick box If ACPT is not enabled move on to the text below The most common of resource allocation problems on Windows 2000 is interrupts IRQs It is very easy to run out of available interrupts in a PC configuration so the interrupt availa bility may also be a problem for one of the other board types With Windows 2000 booted you can use the Start gt Programs gt Accessories gt System Tools gt System Information open the tree at Hardware Resources then select the IRQs entry to look at the IRQs that are already used If you have any ISA cards in your system if there s no driver installed for that board then Windows 2000 doesn t know about the card The ISA card s IRQ and or address may over lap the HERON carrier s IRQ and or address range Remove unused ISA cards and then try to run the confidence checks again If the ISA card s driver is installed it may also be that the hardware IRQ setting on that ISA board is different from the IRQ used by the ISA card s driver Some PCI BIOS have options of whether to allocate IRQs to the PCI slots These options are different for different BIOS makes and versions First it is important to check that the motherboard BIOS has interrupts enabled for the slot the board is in beware the slot
110. n DSP_CD 3 Next select Install or Upgrade 4 The InstallShield setup program will now start Follow the directions given by setup After installing the software and installing the driver vxd setup will ask you to configure the driver After clicking yes the System Properties window appears 38 HUNT ENGINEERING API WINDOWS Installation User MANUAL System Properties Nx View devices by type O View devices by connection y CDROM amp Disk drives O Display adapters 3 Floppy disk controllers 3 Hard disk controllers ER HuntEngClass 3 Keyboard Modem BI Monitors SD Mouse E Network adapters 4 Ports COM amp LPT m System devices Universal serial bus controller Properties Refresh Remove Print Click on the Device Manager tab and open HuntEngClass if it isn t open yet You should see a HEPC2E Rev B C entry The entry should have a yellow circled exclama tion mark on it Open the entry by double clicking on it This should open the HEP2E Rev B C Properties window Select Resources Click Set Configuration Manually First in the Resource type column select Interrupt Request If Setting shows a value that equals the interrupt jumper setting on your HEPC2E then the setting
111. n other cases it may take quite a while until the Hardware Wizard starts to run The Hardware Wizard should run automatically you shouldn t have to point to a directory If for any reason the Hardware Wizard does ask for a directory point to the software api directory on the HUNT ENGINEERING CD If you upgrade from an earlier API version first un install the old API installation Then reboot the machine Then follow the instructions above Windows NT Installation There is no Windows NT support for the HERON BASE2 as there is no standard Windows USB support available on Windows NT Windows 95 98 ME Installation There is no Windows 95 98 ME support for the HERON BASE2 DOS Installation There is no DOS support for the HERON BASE2 The Windows Confidence Check Program The setup program will automatically have done a number of confidence checks You can do the confidence checks manually also The Windows Confidence check program is instal 32 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL led automatically on any Windows version It is started up as follows Start gt Programs gt HUNT ENGINEERING gt Confidence checks As the program starts up it is initialised to access the board defined by the HEAPIJTAG environment variable The setup program has set this variable If you have only 1 board installed Confidence Check will always start initialised to access that 1 board Please refer to the HERON Carriers instal
112. nd higher If you have both version 1 2 and 2 0 installed it will try to setup both versions AutoConfigure Group This option will try to configure Code Composer Studio for a group of boards Instead of starting Code Composer Studio Setup and adding boards and processors manually this option will try to do this work for you A Board Group as defined with Group Tools gt Boards in Group is used for this The board group may be any combination of HEPC9 and HEPC8 or other HERON PCI boards Reset Plug in This menu item allows you to register and un register the Reset plug in This is implemen ted only to comply with TI plug in compliance You should usually not register or un regis ter Hunt Engineering plug ins This is normally done by Hunt Engineering SDK install Project Plug in This menu item allows you to register and un register the Create New HERON API project plug in This is implemented only to comply with TI plug in compliance You should usual ly not register or un register Hunt Engineering plug ins This is normally done by Hunt Engineering SDK install Server Loader Plug in This menu item allows you to register and un register the Server Loader plug in This is implemented only to comply with TI plug in compliance You should usually not register or un register Hunt Engineering plug ins This is done by Hunt Engineering SDK install 14 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL FPGA Program FPGA
113. ng the workload of the PC On the legacy board HEPC3 HEPC4 HECPCI1 we have used the AMCC 5933 PCI controller chip This chip will carry out PCI Master Mode transfers between its internal FIFOs and the Host Computer s memory over the PCI bus Once the transfer has been set up this has no impact on the Host CPU providing a more responsive system see comments on Polled mode above The Master Mode can only transfer to a Physical address This means that the driver needs to ensure that the buffer being used is locked in physical memory In Windows there is a maximum size of 64KBytes of a user buffer that can be locked into Physical memory at one time This forces the driver to break a Master Mode transfer of a large user buffer into a number of 64KByte transfers This may have the unfortunate side effect that a system that does not use Master Mode may achieve higher transfer rates but will load the processor more as the processor has to do all of the transfers to and from the device itself For C4x boards HEPC3 HEPC4 HECPCI1 the use of Master Mode is not much slower but allows the processor to perform other tasks For small transfers lt 64Kbytes the Master Mode transfers will not be any slower 66 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL The C6x Host API Example Programs The HUNT ENGINEERING CD has a number of examples that show how you could use the API The examples are located on the CD in software example
114. nsure of details please refer to http www hunteng co uk for the list of current re sellers HUNT ENGINEERING technical support can be contacted by emailing support hunteng demon co uk calling the direct support telephone number 44 0 1278 760775 or by calling the general number 44 0 1278 760188 and choosing the technical support option 69 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Appendix 1 C4x Board Specific Information When an API device is opened the device to be opened is identified by the combination of a board type a board number because systems can have more than one board of that type and a device number on that board because a board can have multiple devices associated with it e g ComportA ComportB JTAG Board Number In general boards are numbered starting from 0 but the ordering can be different for different bus types PCI ISA VME HEPC3 HEPC4 HECPCI1 The order of boards on the PCI Bus is dependent on the PC Motherboard BIOS and Operating System PCI slots ate geographically addressed that is the position on the motherboard determines the slot number that is allocated by the system The system may find the board furthest away from the CPU or the one closest to the CPU as the first board NO assumptions can be made based on slot number only that board 1 is the next one after board 0 The reset test program supplied as part of the API is provided to a
115. nt un install reboot and then re install the HUNT ENGINEERING API If you do find entries in the Devices panel see what Status and Startup are set to If Startup is not set to Automatic click the StartUp button and select Automatic then click OK Next start the HUNT ENGINEERING device by clicking the Start button If Status is set to Started then the driver is working If not then there is some sort resource problem It may also be that the HERON carrier board is not inserted properly In the PC BIOS you may have an ECSD setting Electronic Configuration Setup Data If it exists it must be cleared Clearing this field you one 1 chance to install a new board After 1 reboot this ECSD reverts to being set So each time you want to install or re install or re arrange PCI boards you need to clear this ECSD switch again Usually you can access BIOS settings by pressing DEL or F2 very soon after a reboot far before the operating system starts to run You would see a message at the bottom of the screen saying something like press DEL to go to setup Please refer to your motherboard s manual if necessary One of the first things to try is another PCI slot Different PCI slots may have different resoutces assigned to them Move the HERON carrier board to another unused PCI slot If that doesn t work try swapping the HERON carrier board with other PCI boards For
116. num ber is not always obvious Some BIOS require you to allocate a fixed IRQ number in which case you must check that it is an available IRQ that you choose In the BIOS there is frequently also an option PnP OS For a non ACPI system this must have been set to no For ACPI enabled PC s this must have been set to yes If all this fails you have to consider the possibility that there s a clash with another board Remove boards that are not immediately needed such as sound cards network cards etc If this doesn t work remove the associated drivers as well If you still have no progress try to un install the API reboot and re install the API If even this doesn t work try a different PC and or a different operating system if you have any available If you have more than 1 HERON module swap this with the module in slot 1 make sure the boot jumpers are set to boot from FIFO 0 27 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Windows NT Just to be sure first verify that the HUNT ENGINEERING API drivers for Windows NT have been copied and have been started To verify that they started start gt settings gt control panel gt devices Look for an entry like hep8akdd or hep9akdd If there are no such entries there at all verify if the drivers have been copied into c winnt system32 drivers look for hep8akdd sys or hep9akdd sys If there are no driver files prese
117. o install 1 Log in as Administrator onto your Windows 2000 machine 2 Windows 2000 may tell you it has found new hardware Click cancel and do not install the API using Windows hardware wizard for now 3 Insert the HUNT ENGINEERING CD 4 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 5 Next select Install or Upgrade 6 The InstallShield setup program will now start Follow the directions given by setup 46 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL If the setup program finds the hardware and the driver installation is successful then setup will not need to reboot the PC This would be the typical case In case the board is not inserted yet or there s some other such problem setup will reboot once After a reboot the find new hardware wizard will be activated again But this can be very slow In fact setup may continue before new hardware is detected Please make sure not to continue setup while the found new hardware wizard hasn t done its job yet If the new hardware wizard cannot find a driver point to software api on your CD drive After the drivers were installed successfully which may be after a reboot the setup program will confidence check the installation If you upgrade from an earlier API version first un install the old
118. ograms gt HUNT ENGINEERING gt Confidence checks If you have a processor module in slot 1 there are 3 tests that must be successful They are File gt Interrupt Test File gt Reads Test and File gt Writes Test If you have an FPGA module in slot 1 then there are 2 tests that must be successful File gt Interrupt Test and File gt FPGA test Once you find that these test s pass successfully you can restart the install program either from the CD front end DSP_CD or via Windows Explorer The install program will then re try the confidence checks it will not re install the software or drivers If successful it will then move on to a next stage SDK install if you have processor modules HEPC9 If the confidence checks fail please first verify the following 1 The board switch the red one must be set to 0 2 Make sure that there is a HERON processor module or FPGA module in slot 1 Also ensure that the module in slot 1 is plugged in properly To be sure take the carrier board out of the PC then remove the slot 1 module and re insert Now te insert the carrier board in your PC and try again HEPC8 If the confidence checks fail please first verify the following 1 The boot jumpers of the module in slot 1 must be set to boot from FIFO 0 2 The board switch the red one must be set to 0 3 Make sure that there is a HERON processor module or FPGA module in slot 1 Also ensure that the module in slot 1 is
119. ollowing checks to see if the PC motherboard supports PCI devices checks to see if the PC motherboard has detected the PCI device prints out the configuration that the PC has programmed into the configuration registers of the HEPC3 HEPC4 HECPCI1 To run hep3diag type hep3diag Command board number The command is an optional switch that can be v for verbose or p for probe all PCI devices The board number can be used to printout the data for a particular board in a multi board installation Note the first board is board 0 and this board number is not relevant with the p switch as it prints data about all PCI devices in the PC This program is located in the software api heapi utils directory and can either be run from that location or copied to your hard drive The output should be similar to that below HEPC3 is Reset Dumping Configuration Registers O Device ID 0x809c Vendor ID 0x10e8 0x4 Status 0 Command 0x107 0x8 Class Code 0 Rev Id 0 Oxc BIST 0 Header Type 0 Latency Timer 0x20 Cache Line Size 0 0x10 IO Base for Operations Register Oxfe80 0x14 IO Base for Pass Thru 0 Comport B Data Oxfd80 0x18 IO Base for Pass Thru 1 Comport A Control Oxfd00 Oxlc IO Base for Pass Thru 2 Comport B Control OxfccO 0x20 IO Base for Pass Thru 3 JTAG Oxf800 0x24 IO Base for Unavailable Region 0 0x28 Reserved Area should be 00000000x 0
120. onfig gt Master Board gt Set to hep9a x Where x is the board number of the current default board To set the current default board to stand alone select JTAG Config gt Stand Alone To verify what the current master and slave settings are select JTAG Config gt Show Current Master and slave settings are done with registry entries hejtagmaster and hejtagslave The Host API and CCS drivers will recognize these registry entries and handle accordingly Default Board The entry allows you to select a current default board At program startup confchk will try to automatically detect installed boards PCI When selecting Default Board you can choose from any board that was automatically detected Some boards cannot be detected like ISA boards and with Default Board gt Other Board you can specify any board including boards that have not been automatically detected With Default Board gt Refresh you ask confchk to again try to automatically detect boards Note that if a PCI board is not detected but is definitely inserted powering down the PC and re inserting the board usually helps Group Tools Group Board Reset This option does a reset on a group of boards You can select what boards are in the group using the Group Tools gt Boards in Group menu entry By default confchk puts all automatically detected boards in the group Group JTAG Reset This option does a JTAG reset on a group of
121. option can be used to perform some troubleshooting of the Kernel Device Driver loading See the troubleshhoting section for instructions DoJtag which can be set to yes or no This option is not really of any use in the case of the HEPC3 as the Plug and Play will already have allocated addresses to the JTAG device UseVxd which can be set to yes or no This is useful for tracking down interrupt problems ad the Vxd will ALWAYS use interrupts and the direct access provided by the DLL will NEVER use interrupts See the troubleshhoting section for instructions 78 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL HECPCI1 revA Board Type and device number Board Name hcpc1 Devices ComportA ComportB Jtag I O Address Order As Per PCI Bus JTAG Address Order As Per PCI Bus Manually Installing Device Drivers under Windows NT ntapi_setup hep3bkdd registry ntapi_setup hep4akdd registry ntapi_setup hcpcikdd registry Please note that all three of these choices will install the hep3bkdd sys driver The PCI interfaces of the HEPC3B HEPC4A and HECPCI1 boards are identical and thus the same Kernel Mode Driver can be used The ntapi_setup program prompts you to select the following DoMasterMode which can be set to be Y for yes or N for no This selects whether the Kernel Device Driver will attempt to use PCI Master Mode on Comport A The yes option is the usual one but the no option can be used to perform some troub
122. option is the usual one but the no option can be used to perform some troubleshooting of the Vxd loading See the troubleshhoting section for instructions DoJtag which can be set to yes or no This option is not really of any use in the case of the HEPC3 as the Plug and Play will already have allocated addresses to the JTAG device UseVxd which can be set to yes or no This is useful for tracking down interrupt problems ad the Vxd will ALWAYS use interrupts and the direct access provided by the DLL will NEVER use interrupts See the troubleshhoting section for instructions When the drivers are installed you can use the start gt settings gt Control Panel gt system gt device manager gt HuntEngClass to see the entry for HEPC3 Rev B C Clicking on that allows you to select options where you can choose DoMasterMode which can be set to yes or no This selects whether the Kernel Device Driver will attempt to use PCI Master Mode on Comport A The yes option is the usual one but the no option can be used to perform some troubleshooting of the Kernel Device Driver loading See the troubleshhoting section for instructions DoJtag which can be set to yes or no This option is not really of any use in the case of the HEPC3 as the Plug and Play will already have allocated addresses to the JTAG device UseVxd which can be set to yes or no This is useful for tracking down interrupt problem
123. or a manually configured board is significant Board Name on the Board Name amp Data File tab see picture on page 15 When doing AutoConfigure or AutoConfigure Group from the Confidence Checks the board name is always hep9a x where x is the board switch number or hep8a x where x is the board switch number For CCS it doesn t matter what the name of the boards is but you do want to have some naming that indicates what board it is to yourself However for the plugins the board name is significant The plugins can t see what a board is they can only see a board s name The plugins will only understand descriptions hep9a x hepc9 x hep8a x and hepc8 x where x is a number indicating the red board switch value If you use any other name the plugins will not understand what board you use The plugins will ask you though in the case a board name isn t understood When using AutoConfigure or AutoConfigure Group this isn t an issue as automatically the correct board name is used 20 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Troubleshooting General for all Windows versions The install program will try to do some confidence checks If it fails install will exit and you cannot proceed to the next stage ie SDK install in case you use any processor modules To try to fix installation problems use the confidence check program from the Start menu Start gt Pr
124. or some boards it also supports direct access to the module carrier Use of the API is always the recommended way to use the HUNT ENGINEERING Server Loader GO DSP Code Composer Code Composer is not supported under DOS please contact your supplier as there may be alternative debugging options available for your module carrier HUNT ENGINEERING API For systems running under DOS the API provides a library file that links with your application to provide that application with all of the standard API interface If later in the life of your system you choose to change the host board type you simply change the board type identifier given to the HeOpen function If the board you choose was supported by the same version of the API there is nothing else to do if you choose a newly released host board you simply re link your application against the new library Tools for MS Windows 95 This section is considering Win32 programs when running under Windows 95 3L C4x Parallel C 3L have ported the Win32 version of their TIS server to the HUNT ENGINEERING API however if you do not have the API installed then it can be configured to use some module carriers directly If you have the API then DO NOT use the direct support as conflicts can occur between different tools applications if the board is accessed without using the API This uses the Win32 API which must be installed as described in the installation sections Refer to t
125. ow In fact setup may continue before new hardware is detected Please make sure not to continue setup while the found new hardware wizard hasn t done its job yet If the new hardware wizard cannot find a driver point to software api on your CD drive After the drivers were installed successfully which may be after a reboot the setup program will confidence check the installation If you upgrade from an earlier API version first un install the old API installation Then reboot the machine Then follow the instructions above Windows 2000 Installation The API supports Windows 2000 installing WDM drivers API versions before 1 9 would have installed legacy NT 4 0 drivers It is important to first un install any previous API versions you may have installed To install 1 Log in as Administrator onto your Windows 2000 machine 2 Windows 2000 may tell you it has found new hardware Click cancel and do not install the API using Windows hardware wizard for now 7 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL 3 Insert the HUNT ENGINEERING CD 4 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 5 Next select Install or Upgrade 6 The InstallShield setup program will now start Follow the directions given by setup If the setup program finds the hardware
126. ows NT Win 95 98 ME This uses the Win32 API which must be installed as described in the installation sections HUNT ENGINEERING API For systems running under Windows NT the API provides a stub library file that links with your application to provide that application with all of the standard API interface When your Win 32 application actually runs the Operating system automatically loads a Dynamic Link Library DLL that calls a Kernel Mode Device Driver Kdd for the board you have specified in the HeOpen call If later in the life of your system you choose to change the host board type you simply change the board type identifier given to the HeOpen function You then need to re run the setup program to install the Kdd for that board type if you didn t do so originally and the ntapi_setup program to configure that Kdd If you choose a newly released host board you simply install the new API version and the DLL is updated and the Kdd installed for you ready for the application to use Tools for MS Windows NT using the DOS box Under Windows NT the DOS box is used for both DOS programs and Win32 Console mode applications Win32 console mode applications should be built using the Win32 API DOS applications linked against the MSDOS version of the API will NOT work under Windows NT though they do on Windows 95 86 HUNT ENGINEERING API WINDOWS Installation User MANUAL Appendix 4 C4x Development Tools
127. pi of the CD and choose OK The file should be found OK the second time 79 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL 3 After the machine has booted run the software api setup program from the HUNT ENGINEERING CD and choose to install the DLLs that are required Choose to install the Microsoft or Borland versions you may install both if required When the drivers ate installed you can use the start gt settings gt Control Panel gt system gt device manager gt HuntEngClass to see the entry for HEPC3 Rev B C Clicking on that allows you to select options where you can choose DoMasterMode which can be set yes or no This selects whether the Kernel Device Driver will attempt to use PCI Master Mode on Comport A The yes option is the usual one but the no option can be used to perform some troubleshooting of the Vxd loading See the troubleshhoting section for instructions DoJtag which can be set to yes or no This option is not really of any use in the case of the HEPC3 as the Plug and Play will already have allocated addresses to the JTAG device UseVxd which can be set to yes or no This is useful for tracking down interrupt problems ad the Vxd will ALWAYS use interrupts and the direct access provided by the DLL will NEVER use interrupts See the Troubleshooting section for instructions When the drivers are installed you can use the start gt
128. picture next to the entry If the statement This device is working properly is shown in the general window then the VxD is probably working However do not assume that it is really OK as there may be devices in the machine that do not have VxDs loaded so Windows does not know about them It has also been seen that some devices with VxDs use some resources that they do not declare to Windows To find a free IRQ or I O address range in Windows you can use the Start gt Settings gt Control Panel gt System gt Device Manager and double click on computer The various pages then show what resources Windows thinks are being used Again you must be aware that there might be some hardware in the system that Windows does not know about for some reason such as there being no VxD installed In the PC BIOS you may have an ECSD setting Electronic Configuration Setup Data If it exists it must be cleared Clearing this field you one 1 chance to install a new board After 1 reboot this ECSD reverts to being set So each time you want to install or re install ot re arrange PCI boards you need to clear this ECSD switch again Usually you can access BIOS settings by pressing DEL or F2 very soon after a reboot far before the operating system starts to run You would see a message at the bottom of the screen saying something like press DEL to go to setup Please refer to your motherboard s manual if necessaty One of
129. r Host computer with programs on your DSPs Tools for MS Windows 95 98 ME This section is considering Win32 programs when running under Windows 95 HUNT ENGINEERING Server Loader There is a Win32 console mode version of the HUNT ENGINEERING Server Loadet which uses the Win32 API Also the Win32 library version of the Server Loader which uses the Win32 API can be linked against a Win32 application In either case this uses the Win32 API which must be installed as described in the installation sections GO DSP Code Composer HUNT ENGINEERING have ported GO DSP s Code Composer NT to the Win32 API and this is the recommended version of Code Composer for Win95 This uses the Win32 API which must be installed as described in the installation sections HUNT ENGINEERING API For systems running under Windows 95 the API provides a stub library file that links with your application to provide that application with the entire standard API interface When your Win 32 application actually runs the Operating system automatically loads a Dynamic Link Library DLL that tries to call a VxD driver for the board you have specified in the HeOpen call If later in the life of your system you choose to change the host board type you simply change the board type identifier given to the HeOpen function You then need to re run the setup program to install the VxD for that board type if you did not do so originally If you choose a new
130. r modern PCI devices However it always affects the performance This is especially noticeable with the JTAG eg with Code Composer Studio When you are using the Standard PC HAL you may find that Windows will not turn off the power of your PC when you shutdown the system To change this you need to enable Advanced Power Management APM Go to Start gt Control Panel click Performance and Maintenance then Power Options then click the APM tab at the top If your system can support APM you will have the option to enable APM at the Advanced Power Management support tick box If ACPP is not enabled move on to the text below The most common of resource allocation problems on Windows XP is interrupts IRQs It is very easy to run out of available interrupts in a PC configuration so the interrupt availa bility may also be a problem for one of the other board types With Windows XP booted you can use Computer Management start gt control panel click on Performance and Maintenance then Administrative Tools Double click Computer Management Open Device Manager then select View gt Resources by type then select the Interrupt request IRQs entry to look at IRQs that are already used If you have any ISA cards in your system if there s no driver installed for that board then Windows XP doesn t know about the card The ISA card s IRQ or address may overlap the TIM 40 car
131. rier s IRQ or address range Remove unused ISA cards and then try to run the confidence checks again If the ISA card driver is installed it may also be that the hardware IRQ setting on that ISA board is different from the IRQ used by the ISA card s driver Some PCI BIOS have options of whether to allocate IRQs to the PCI slots These options are different for different BIOS makes and versions First it is important to check that the motherboard BIOS has interrupts enabled for the slot the board is in beware the slot num ber is not always obvious Some BIOS require you to allocate a fixed IRQ number in which case you must check that it is an available IRQ that you choose In the BIOS there is frequently also an option PnP OS For a non ACPI system this must have been set to no For ACPI enabled PC s this must have been set to yes If all this fails you have to consider the possibility that there s a clash with another board Remove boards that are not immediately needed such as sound cards network cards etc If this doesn t work remove the associated drivers as well If you still have no progress try to un install the API reboot and re install the API If even this doesn t work try a different PC and or a different operating system if you have 51 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL any available If you have more than 1 HERON module swap this with the module in slot 1 make
132. rly or that the board isn t installed or that the board wasn t addressed properly e g you try to access board number 1 while there s only a board 0 Reads Test This test verifies if the API can read data sent by the processor in slot 1 of a board The program on the processor sends a stream of known data and the API test program will both try to read the data and verify that the data equals the expected known data Writes Test This test verifies if the API can write data to the processor in slot 1 of a board Sometimes this test will succeed even if the reads test fails This is because there are situations where the read test fails but writes appears to succeed simply because it s impossible for writes to detect certain errors Therefore writes can only be considered to succeed if and only if the reads test also succeeds 9 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL FPGA Test This test verifies if the API can read from and write to an FPGA in slot 1 of the board The confchk program will first boot the FPGA with a bitstream The bitstream will differ depending on the actual FPGA or HERONIO module you have The confchk program will use the HSB bus to ask the module to identify itself The information gathered is then used to select the correct bitstream The bitstreams are always taken from the CD from the examplel directory of a particular module eg cd fpgalfpga3v1lexamplel for an FPGA3 module This
133. rogram works on Comport B but not on Comport A the problem is probably due to Master Mode If Comport A functions with this set to N and fails with it set to Y then the problem is confirmed to be related to Master Mode and the PC BIOS should be checked for settings related to Master Mode The most common of resource allocation problems on Windows NT is interrupts IRQs It is very easy to run out of available interrupts in a PC configuration so the interrupt availabi lity may also be a problem for one of the other board types With Windows NT booted you can use the start gt programs gt Administrative tools gt Windows NT Diagnostics to look at the IRQs that are already used If you have any ISA cards in your system if there s no driver installed for that board then Windows NT doesn t know about the card The ISA card s IRQ and or address may ovet lap the TIM 40 carrier s IRQ and or address range Remove unused ISA cards and then try to run the confidence checks again If the ISA card s driver is installed it may also be that the hardware IRQ setting on that ISA board is different from the IRQ used by the ISA catd s driver Some PCI BIOS have options of whether to allocate IRQs to the PCI slots These options are different for different BIOS makes and versions First it is important to check that the motherboard BIOS has interrupts enabled for the slot the board is in beware the slot num ber is not
134. s It requires the JTAG interface of the C4x but as it can be used in conjunction with the TI C compiler assembler the HUNT ENGINEERING server loader or 3L Parallel C it could also require one or more of the host ports HUNT ENGINEERING API In addition to providing the advantages of platform and target board independence to the DSP development tools supplied by HUNT ENGINEERING fot your system the API itself can be used as a development tool for those systems that require programs on the host computer to communicate with or transfer data to or from the DSP system All programs of this type should use the API as the interface so that those systems will not be affected by any changes in the host interface board 3L C4x Parallel C 3L have ported the command line DOS version of their TIS server directly to HUNT 87 HUNT ENGINEERING API WINDOWS Installation User MANUAL ENGINEERING Module carriers and hence it does not require the HUNT ENGINEERING API Refer to the relevant 3L technical note for instructions on its installation and use with the relevant Module carrier WARNING As MSDOS is single tasking this Direct I O will not conflict with other tools using the API If you are using some form of multi tasking MSDOS then you will need to observe the same precautions as when using Parallel C with direct I O in a Windows DOS box HUNT ENGINEERING Server Loader HUNT ENGINEERING have ported their Server Loader to use the API f
135. s Performance Logs and Alerts z Device Manager Storage Removable Storage Disk Defragmenter d Computer amp Disk drives EI Display adapters 2 DVD CD ROM drives 2 Floppy disk controllers e H Floppy disk drives Q HUNT ENGINEERING Class lt p hebase2 lt p hepc9 Des G On the right hand side you should now see a HUNT ENGINEERING Class entry 33 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Open this entry If there are any problems with the driver you ll see a red cross exclamation mark or so over the icon that represents a driver If all is fine you ll just see a diamond shaped icon You will only see the drivers for the boards you installed In the picture on the previous page 2 drivers have been installed for 2 different HUNT ENGINEERING boards If you find that a driver icon has something superimposed on top of it a red cross an exclamation mark or something else have a look in the event log to see if the driver has managed to write any problem information there You can find the event log in the event viewer part of Computer Management we just opened above In the System log you find HUNT ENGINEERING driver entries heb2awdm for HERON BASE2 Double click on such entries to see what it says If all is well you will only find 3 entries Computer M
136. s ad the Vxd will ALWAYS use interrupts and the direct access provided by the DLL will NEVER use interrupts See the troubleshhoting section for instructions 76 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL HEPC4 rev AorB Board Type and device number Board Name hep4a Devices ComportA ComportB Jtag I O Address Order As Per PCI Bus JTAG Address Order As Per PCI Bus Manually Installing Device Drivers under Windows NT ntapi_setup hep3bkdd registry ntapi_setup hep4akdd registry ntapi_setup hcpclkdd registry Please note that all three of these choices will install the hep3bkdd sys driver The PCI interfaces of the HEPC3B HEPC4A and HECPCI1 boards are identical and thus the same Kernel Mode Driver can be used The ntapi_setup program prompts you to select the following DoMasterMode which can be set to be Y for yes or N for no This selects whether the Kernel Device Driver will attempt to use PCI Master Mode on Comport A The yes option is the usual one but the no option can be used to perform some troubleshooting of the Kernel Device Driver loading See the troubleshhoting section for instructions After running ntapi_ setup you will be asked to reboot the system This is a good point to power down the machine and insert the HUNT ENGINEERING module carrier Although it s perfectly OK if the board was inserted earlier on If you wish to un install a Kernel Mode Driver simply run ntapi_setup dri
137. s host_api_examples c6x There will be PDF files in the example directories that explain how the examples work Each example directory has a number of sub directories each sub directory dedicated to a certain operating system In sub directory win32 you will find a PDF file that explains how to compile and build the example for Windows using the Microsoft Visual C C or Borland C Builder compiler 67 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL The C4x Host API Example Programs The HUNT ENGINEERING CD has a number of examples that show how you could use the API The examples are located on the CD in software examples host_api_examples c4x There will be PDF files in the example directories that explain how the examples work Each example directory has a number of sub directories each sub directory dedicated to a certain operating system In sub directory win32 you will find a PDF file that explains how to compile and build the example for Windows using the Microsoft Visual C C or Borland C Builder compiler 68 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Technical Support Technical support for HUNT ENGINEERING products should first be obtained from the comprehensive Support section http www hunteng co uk support support htm on the HUNT ENGINEERING web site This includes FAQs latest product software and documentation updates etc Or contact your local supplier if you are u
138. stem if there s no driver installed for that board then Windows 2000 doesn t know about the card The ISA card s IRQ and or address may over lap the TIM 40 carrier s IRQ and or address range Remove unused ISA cards and then try to run the confidence checks again If the ISA card s driver is installed it may also be that the hardware IRQ setting on that ISA board is different from the IRQ used by the ISA catd s driver Some PCI BIOS have options of whether to allocate IRQs to the PCI slots These options are different for different BIOS makes and versions First it is important to check that the motherboard BIOS has interrupts enabled for the slot the board is in beware the slot num ber is not always obvious Some BIOS require you to allocate a fixed IRQ number in which case you must check that it is an available IRQ that you choose In the BIOS there is frequently also an option PnP OS For a non ACPI system this must have been set to no For ACPI enabled PC s this must have been set to yes If all this fails you have to consider the possibility that there s a clash with another board Remove boards that are not immediately needed such as sound cards network cards etc If this doesn t work remove the associated drivers as well If you still have no progress try to un install the API reboot and re install the API If even this doesn t work try a different PC and or a different operating system if
139. systems Typically this library provides the lowest level of support for any particular board no support for interrupts no support for DMA polled mode I O only The MSDOS Poll Loop Without interrupts the MSDOS library needs to poll the ready bit of the interface to determine if it can continue with its read write operation The poll loop will retry an I O operation a number of times until it reaches a retry limit currently 256 it will then store its current state of progress and return HE_loInProgress Subsequent calls to HeTestIo or HeWaitForlo will restart the I O and in the case of HeTestIo will either run until completion or the retry limit store the current status and again return HE_IoInProgress Implementation of Asynchronous UO Some Operating System platforms naturally implement asynchronous behaviour e g Windows NT Kernel Mode drivers For the other platforms it is the API s responsibility to overlay asynchronous behaviour on top of the normal model There are currently two solutions to this MSDOS On MSDOS the API does not use interrupts this means that it has to enter a poll loop waiting for I O to be available when it is unable to complete a read write operation In otder to provide asynchronous behaviour the following strategy is used 63 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL HeRead or write will poll the ready flags of the module carrier and trans
140. t a red cross an exclamation mark or something else have a look in the event log to see if the driver has managed to write any problem information there You can find the event log in the event viewer part of Computer Management we just opened above In the System log you find HUNT ENGINEERING driver entries hep9awdm for HEPC9 or hep8awdm for HEPC8 or hep3bwdm for HEPC3 HEPC4 or HECPCI 52 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Computer Management Computer Management Local G Information 08 10 2002 08 46 39 hep9awdm i System Tools Ai Information 08 10 2002 08 46 39 hep9awdm E Event viewer Event Properties Application S Security Event fil System e OR System Information Date 08 10 2002 Source hepSawdm Zi Performance Logs and Alert Time 08 46 Category None Shared Folders Type Information EventID 32796 A Device Manager User Local Users and Groups Computer APPLYw2K E Sy Storage 3 Disk Management Description BS Disk Defragmenter EE Board address OxDFFEFOOO itq 9 Shared 3 Logical Drives Double click on such entries to see what it says If all is well you will only find 2 to 5 entries telling you at what IRQ and memory address es the board has been installed Returning to the previous picture if you find that there is no HUNT ENGINEERING Class or no driver
141. t your hardware settings The Base address of the HEPC2E which can be set to 0x200 0x160 and 0x300 The choices given to this program MUST be the same as the current IO address jumper settings on the board Beware there ate several blocks of I O address space that are used for the XDS510 compatible JTAG software as follows Jumper Rangel Base I O Range 2 Jtag Range 3 Jtag Range 4 Jtag 200 0x200 0x219 Ox 240 0x 25f Ox 640 0x 64f Ox a40 0x a4f 160 0x160 0x179 Ox 1a0 0x 1bf Ox 5a0 0x 5af 0x 9a0 0x 9af 300 0x300 0x319 Ox 340 0x 35f Us 740 0x 74f 0x b40 0x b4f Interrupt Request which can be set to be 10 11 12 or 15 The choice given to this program MUST be the same as the current INTS jumper setting on the board The Options menu offers UseVxd which can be set to yes or no This is useful for tracking down interrupt problems as the VxD will ALWAYS use interrupts and the direct access provided by the DLL will NEVER use interrupts See the troubleshhoting section for instructions DoJtag which can be set to yes or no The yes option is the usual one the zo option can be used to perform troubleshooting of the VxD loading See the troubleshhoting section for instructions 74 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL HEPC3 rev B or C Board Type and Device Number Board Name hep3b Devices ComportA ComportB Jtag I O Address Order As Per PCI Bus JTAG Address Order As Per PCI Bus Manually
142. tallation If you upgrade from an earlier API version first un install the old API installation Then reboot the machine Then follow the instructions above DOS Installation The API supports DOS 6 x systems by providing a 1ib file to directly link an application 47 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL to Although applications using this support can work in DOS windows and Windows 95 this is not the recommended way There is no installation program for DOS support to use an application that is already linked to the DOS API you do not need to install anything If you wish to link an application with the DOS API all you need to do is copy the files heddrv lib and heapi h from the software api directory on the HUNT ENGINEERING CD into your development directory The Windows Confidence Check Program The setup program will automatically have done a number of confidence checks You can do the confidence checks manually also The Windows Confidence check program is instal led automatically on any Windows version It is started up as follows Start gt Programs gt HUNT ENGINEERING gt Confidence checks As the program starts up it is initialised to access the board defined by the HEAPIJTAG environment variable The setup program has set this variable If you have only 1 board installed Confidence Check will always start initialised to access that 1 board Please refer to the HERON Carriers installation s
143. testtsstessttsstesseesseeseseeeseesset 9 UCI eni erna reg 9 L 11 LOOSE A A A He da AA Pe a 13 Group Tr sa 13 LE 14 COde EE 14 Eeer PR SR Se Eee 15 LEAR ege eher ele sede case UES AS 16 EE ETS IED AR Bee ET eR TAS TEA SET 17 CODE COMPOSER STUDIO CONFIGURATION cocooocccococonnnonnnoconnnonnnoconononn noc e eNe noc ne nino Eaa 17 Automatic Configuration at metal 17 Automatic Configuration on Demand 17 Automatic Configuration of Multiple Boards oooonnnninninninnnnonnnnconccnncaccrnccnnnnrrnnrrnnrrn ran 17 EE 17 Manual Configuration of Multiple Boorde tees tees tens cc aesacecaeeeaeeeseesseeeseeteeeeeaes 20 Manual Configuration Naming Boorde ooo 20 CIA NA E E T E EE E E AT 21 General for all Windows vereions canaria 21 WARD OWS AP Eege 21 Windows LOO cvs cases jas A E VES ERE ARE ERR BR ES 24 WANG ET 28 Windows EE di eebe vhs Boa Rha ithe baie bin es Ria ines is HAs ib Heese e 29 TUNINS TAL Des enger ee EEE OEE EET E ta 30 HERON BASE 2 INSTALLATION amp CONFIDENCE TEST eessen Al INSTALLATION ina ile a 31 Windows EE 31 Windows 2000 Installation AAN 31 Windows Ne teen eeh adh O hn a eR OR si 32 Windows 95 98 ME Installation ccccccccccccccccseccsscessseceescecseeceecessseceeeecssesseeeessecsseseessecssseeeeseeenseeees 32 ee 32 THE WINDOWS CONFIDENCE CHECK PROGRAM 32 TROUBLESHOOTING ioppo E EEE cect ee SEENEN Ae 33 General for all Windows vereions caca nn nn nn 33 WANG OWS DOP aah ia A ara cn dal o des dead o e ee de o e e IB
144. that the hardware settings on that ISA board clash with the HEPC2E Use the other ISA card s manual to find out its IRQ and address range settings If you find an overlap change the IRQ and or address setting on the HEPC2E so that the overlap disappears Be sure to also update the HEPC2E driver with changed the IRQ or address To do this you must run the confidence check program supplied as part of the HUNT ENGINEERING API Start gt Programs gt HUNT ENGINEERING gt Confidence checks Go to the Regis try gt HEPC2E entry You should see a window that allows you to select Base Address IRQ and DoJtag Set the Base Address and IRQ fields as required Click OK Reboot the machine and try the confidence checks The HEPC2E requires a large range of I O addresses when configured with JTAG device enabled this can prevent the driver from loading if there is an I O address clash It is easy to test if this is the problem as you can configure the Windows NT driver to disable JTAG access to see if the driver then loads To do this you must run the confidence check program supplied as part of the HUNT ENGINEERING API Start gt Programs gt HUNT ENGINEERING Confidence checks Go to the Registry gt HEPC2E entry You should see a window that allows you to select Base Address IRQ and DoJtag Set the DoJtag field to No Click OK Reboot the machine and try the confidence che
145. the Flags we have available varies in out and by comport transfer that much in one go or the amount left to transfer If more to do go to A e Finished I O signal IloCompletion exit f Enable a suitable interrupt g On receipt of the interrupt go to A A similar process takes place on read This means that the drivers generally always return HE_IoInProgress and it is necessary to wait for IoCompletion This is the required programming model under the API Interrupts The design of the NT drivers means that interrupts are ALWAYS required It is essential that the module carrier is configured correctly with interrupts enabled If the data is arriving leaving fast enough then interrupts will never be used Clearly in this circumstance there is a CPU overhead during the transfer the effect of this becomes more 65 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL noticeable with larger transfers Also the slower the device the greater the impact for example it takes longer to perform an I O operation on an ISA bus than on a PCI bus Cancellable I O Whenever a process is unexpectedly terminated e g when a user presses Control C or a program that exits without calling HeClose the NT I O Manager will attempt to cancel any outstanding I Os by sending a cancellation request message to the driver If a driver has enabled an interrupt and is waiting for that interrupt in order to continue the driver will accept a
146. the HUNT ENGINEERING API If you do find entries in the right hand panel in Computer Management double click on the entry Check that the Device Status is set to This device is working properly If not then there is some sort of resource problem that may or may not show up in the event log 35 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Uninstall 1 Insert the HUNT ENGINEERING CD 2 A new window should now appear Select Install Drivers amp Tools If the window doesn t appear use Windows Explorer and browse to your CD drive Then double click on DSP_CD 3 Next select UnInstalP Follow the instructions Alternatively you can uninstall via Windows Go to Start gt Settings gt Control Panel then double click on Add Remove Programs Select HUNT ENGINEERING APT and click the Add Remove button Follow the instructions If you want to re install the API first reboot 36 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL C4x boards Installation amp Confidence Test Installation The HUNT ENGINEERING CD install program will install and confidence check the API for Windows 95 98 NT and DOS installations If for any reason you experience problems with installation or confidence checking use this section for a step by step installation check When an API device is opened the device to be opened is identified by the combination of
147. then there is some sort of resource problem It may also be that the HEPC2E is not inserted properly In the PC BIOS you may have an ECSD setting Electronic Configuration Setup Data If it exists it must be cleared Clearing this field you one 1 chance to install a new board After 1 reboot this ECSD reverts to being set So each time you want to install or re install or re arrange PCI boards you need to clear this ECSD switch again Usually you can access BIOS settings by pressing DEL or F2 very soon after a reboot far before the operating system starts to run You would see a message at the bottom of the screen saying something like press DEL to go to setup Please refer to your motherboard s manual if necessaty With Windows 2000 see if ACPI is enabled We have seen installations that would only work after ACPI was disabled But we have also seen installations that happily worked with ACPI enabled To verify if ACPDP is enabled Go to Start gt Settings gt Control Panel gt System Click the Hardware tab and then click Device Manager to view what is listed under the Computer branch The following is the list of supported computer types Possible values for the HAL under Standard computers include ACPI Multiprocessor PC ACPI Uniprocessor PC Advanced Configuration and Power Interface ACPI PC MPS Multiprocessor PC MPS Uniprocessor PC Standard PC If you find you are us
148. to another channel of the same EM2 module The EM2 Cable window allows you to specify what 2 channels you use 12 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Tools Board Reset This option does a reset on the board under test JTAG Reset This option does a JTAG reset on the board under test With the Options gt Show JTAG regs you can dump the contents of the JTAG registers after reset which may be useful when verifying the JTAG access works properly JTAG Config With this option you can select whether the current default board should be used as slave master or stand alone With a JTAG cable available from HUNT ENGINEER ING you can debug a system of 2 HEPC9 compatible boards as one One board is then designated to be the master the other board the slave The two boards don t necessarily need to be in one PC The master board typically will be the current PC the slave board could be in the same PC be embedded or be in some other PC But note that the Auto Configure Plugin cannot recognize a board if it s not in the current PC so that in such cases you must do some additional work in CCS Setup to configure Code Composer Studio To set the current default board to slave select JTAG Config gt Slave Board gt Set to hep9a x Where x is the board number of the current default board To set the current default board to master select JTAG C
149. uct for any particular purpose In no event shall HUNT ENGINEERING S liability related to the product exceed the purchase fee actually paid by you for the product Neither HUNT ENGINEERING nor its suppliers shall in any event be liable for any indirect consequential or financial damages caused by the delivery use or performance of this product Because some states do not allow the exclusion or limitation of incidental or consequential damages or limitation on how long an implied warranty lasts the above limitations may not apply to you TECHNICAL SUPPORT Technical support for HUNT ENGINEERING products should first be obtained from the comprehensive Support section http www hunteng co uk support support htm on the HUNT ENGINEERING web site This includes FAQs latest product software and documentation updates etc Or contact your local supplier if you are unsure of details please refer to http www hunteng co uk for the list of current re sellers HUNT ENGINEERING technical support can be contacted by emailing support hunteng demon co uk calling the direct support telephone number 44 0 1278 760775 or by calling the general number 44 0 1278 760188 and choosing the technical support option 2 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Revision History API ver 1 0 Pre release version internal release only API ver 1 1 First release version API ver 1 2 First release to be put on HUNT ENGINEERING
150. udio if the number of DSP modules has changed or the board number has changed or the board type has changed Automatic Configuration of Multiple Boards With the new CCS drivers introduced in API 1 9 3 you can now debug more than 1 board at once This is done via the PDM Parallel Debug Manager where the DSP s on the different board are accessible via the PDM s File menu Code Composer Studio does not support multiple instances ie you cannot start a separate session of CCS per board To debug multiple boards you need to configure Code Composer Studio and tell it about all boards that you want to debug You can configure automatically using the Confidence Checks Tools gt AutoConfigure Group menu item Group refers to a group of boards You can select boards in the group via the GroupTools gt Boards in Group menu item Manual Configuration If you wish to configure Code Composer Studio manually start CC Setup Use the HUNT ENGINEERING API driver in the middle pane or if not present use TPs tixds6000 dvr driver This has different names with different Code Composer Studio versions but in the right hand pane of CC Setup you can see what the underlying driver is Drag the driver from the middle to the left pane This will create a new instance for a board to be accessed via the selected driver The board instance must be directed to access the board via the HUNT ENGINEERING driver hepod510 dll To do this sele
151. ure This button will activate heartconf and ask it to configure HEART using the network file you selected Browse Browse and select a network file Edit Allows you to edit the network file that you selected If no network file is selected it will ask you whether you want to create a new network file A new network file will be created with some example contents template 16 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Verbose Select this box if you want heartconf to display verbose information Help About Displays some useful information what confchk version this is Version Shows the version number of the currently installed API amp Tools and of the different constituent parts Help Starts a help screen where can can read the above once more but perhaps differently Code Composer Studio Configuration Automatic Configuration at install The setup program will have tried to automatically configure Code Composer Studio That is if Code Composer Studio was installed before the HUNT ENGINEERING API Automatic Configuration on Demand At any time you can re configure Code Composer Studio With the Confidence Checks program use Code Composer gt AutoConfigure Single and the program will try to configure Code Composer Studio assuming the default board You can change the default board selected via the Tools gt Default Board menu item Typically you want to re configure Code Composer St
152. ver remove where driver is hep2dkdd hep2ekdd hep3bkdd hep4akdd hcpclkdd or hep akdd This will remove the entry in the Registry for that driver You need to reboot for any changes to take effect Note that the actual Kernel Mode Drivers are still present e g in your system s winnt systems32 drivers directory To remove all drivers at once you can use the setup exe program on the CD the same as used for installing the drivers This time select the w install option Note that you still have to run ntapi_setup exe for each driver as shown above Manually Installing Device Drivers under Windows 95 The HEPC4 can be auto detected by Windows 95 so you should 1 Power down the PC fit the HEPC3 HEPC4 HECPCI1 and reboot 2 As the machine boots it should say that it has detected new hardware and ask where the drivers are Direct the Windows 95 software to software api directory on the HUNT ENGINEERING CD If the installation complains about not being able to find the file hep3bui d11 check that the path shown in blue is software api of the CD and choose OK The file should be found OK the second time 77 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL 3 After the machine has booted run the software api setup program from the HUNT ENGINEERING CD and choose to install the DLLs that are required Choose to install the Microsoft or Borland versions you may install both if required When the drivers ate insta
153. wn in the general window then the VxD is probably working However do not assume that it is really OK as there may be devices in the machine that do not have VxDs loaded so Windows does not know about them It has also been seen that some devices with VxDs use some resources that they do not declare to Windows In the PC BIOS you may have an ECSD setting Electronic Configuration Setup Data If it exists it must be cleared Clearing this field you one 1 chance to install a new board After 1 reboot this ECSD reverts to being set So each time you want to install or re install ot re arrange PCI boards you need to clear this ECSD switch again Usually you can access BIOS settings by pressing DEL or F2 very soon after a reboot far before the operating system starts to run You would see a message at the bottom of the screen saying something like press DEL to go to setup Please refer to your motherboard s manual if necessaty Different PCI slots may have different resources assigned to them One thing to try is to move the TIM 40 carrier board to other unused PCI slots If that doesn t work you can try swapping the TIM 40 carrier board with other PCI boards For the HEPC3 HEPC4 HECPCI1 MasterMode can be set to either enabled or disabled It is enabled by default You can check if the confidence checks work with MasterMode set to disabled You can use Start gt Programs gt HUNT ENGINEE
154. xxkdd sys Windows NT Kernel mode device driver for xxxxx xxxxxwdm sys Windows 2000 XP Kernel mode device driver XXXXXVXdA vxd Windows 95 Virtual Device Driver for xxxxx Implementation HEAPI H This file is central to using the API it must be included Hinclude heapi h in ANY program module using any part of the APLI It defines not only the Library routine calls but also the platform independent data types These can should be used even when the library is not required as they make it simple to support multiple platforms in a manner compatible with the API The include file is designed to be the only part of an application that needs conditional compilation to provide platform independence It should not be modified otherwise the behaviour of the rest of the API components is unpredictable Windows 95 98 ME Here we are looking at WIN32 applications i e 32 bit programs Applications should be linked with hendrv d11 either by calling the DLL directly or by linking the application against hendrv lib Due to incompatibilities between Microsoft and Borland lib file format it was necessary to supply a modified version of hendrv lib hebdrv 1ib For this release of the API there is also a separate DLL hebdrv dl1 any references to hendrv in the following text should be substituted by hebdrv if you are using the Borland tools There may be a Windows 95 VxD supplied for the board being used A VxD is the Windows 95 equivalent of a Dev
155. y Windows 95 so you should 81 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Set the board jumpers to use some free resources in your VME rack Power down the VME rack fit the HEV40 4 and reboot After the machine has booted run the setup program in the software api directory on the HUNT ENGINEERING CD to install the DLLs which access the board directly Install the address mapping utility from the software boards hev404 xycom directory of the HUNT ENGINEERING CD 82 HUNT ENGINEERING API WINDOWS Installation amp User MANUAL Appendix 2 HEPC6 Board Specific Information For specific details of the HEPC6 please refer to the HEPC6 user manual When an API device is opened the device to be opened is identified by the combination of a board type a board number because systems can have more than one board of that type and a device number on that board because a board can have multiple devices associated with it e g ComportA ComportB JTAG HEPC6 revA Board Type and Device Number Board Name hep6a Devices ComportA Jtag I O Address Order 0x200 Boatd 0 0x160 Boatd 1 0x300 Board 2 JTAG Address Order 0x240 Board 0 0x280 Board 1 0x320 Boatd 2 0x340 Board 3 N B The reason that 0x200 is Board 0 is because 0x200 is the default address setting Manually Installing Device Drivers under Windows NT ntapi_setup hep6akdd registry The ntapi_setup program prompts you to select the following Baselo
156. y difference with the new WDM drivers that are part of the current API 1 9 and above If you have tried all the above and nothing made any difference try disabling ACPI if you are in the position that you can re install Windows 2000 If ACPP is enabled most of the problem solving methods discussed further below will work To verify if ACPI is enabled Go to Start gt Settings gt Control Panel gt System Click the Hardware tab and then click Device Manager to view what is listed under the Computer branch The following is the list of supported computer types Possible values for the HAL under Standard computers include ACPI Multiprocessor PC ACPI Uniprocessor PC Advanced Configuration and Power Interface ACPI PC MPS Multiprocessor PC MPS Uniprocessor PC Standard PC If you find you ate using any of the first 3 entries then ACPP is enabled on your Windows 2000 installation The API installation may work if you disable ACPI Unfortunately you cannot just disable AC DU in Windows 2000 you will need to re install Windows 2000 To re install Windows 2000 with ACPI disabled please refer to Microsoft Knowledge Base article Q237556 Related articles are Q197055 Q216573 Q232824 To find to the Microsoft Knowledge Base go to http www microsoft com then select support know ledge Base from the top menu Before you re install Windows check your BIOS for the PNP OS INSTAL

Download Pdf Manuals

Related Search

Related Contents

FX5650 Series User`s Quick Reference  Installation instructions and user guide  Manuale di uso e manutenzione    norme di sicurezza  HI-5000/7000 Instruction Manual  Scarica la rivista  Sirius User Guide.book  商品の情報はホームページでご確認ください。 SumaLpanas。nic-jp』  Français (Opens in new window)  

Copyright © All rights reserved. Failed to retrieve file