Home

Server/Loader User Manual

1. In some applications you may already have 1 or more handles open to devices such as a fifo or HSB As the Server Loader may also access those same devices you would have to close all devices before calling a Server Loader function 35 HUNT ENGINEERING Server Loader USER MANUAL An alternative is offered by the handle functions int serverloader HE HANDLE uDevice int n int argc char argv int serverloader HE HANDLE uDevice int n char options char network With the handle functions you tell the Server Loader what devices you have opened already via the uDevice parameter which is a pointer to an array of API handles of opened devices and parameter n is the number of API handles of opened devices in the uDevice array Before opening any device the Server Loader will first check if a device is already opened by checking the list of open devices uDevice If so the handle you provided will be used If not then the Server Loader will try to open the device itself To emphasise this you don t need to open all possible devices You simply tell the heartconf handle functions what devices you already have open The Server Loader will use handles from the list as it needs to and if a device is not in the list it will open the device itself So you don t need to supply a list of all devices that the Server Loader might use you only list the handles of devices that you happen to have opened alread
2. 97 HUNT ENGINEERING Server Loader USER MANUAL fread size t fread void ptr size t size size_t nobj FILE stream TI C4x Library stdio xx lib TI C6x Library stioxxxx lib fread reads nobj objects each of size characters in length from the specified stream to the location pointed to by ptr It returns the number of characters successfully read Zero is returned if end of file is encountered or if an error occurs NOTE The size of C4x objects may vary from the size of objects on the host machine C4x types are all 32bits in size floats are 40 bits in size and therefore the size of an int or a character is 4 bytes freopen FILE freopen char filename char mode FILE stream TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib freopen replaces the already open stream with the file specified It returns the original value of the stream and closes the original stream The function returns NULL if filename can not be accessed This function can be used to attach the streams stdin stdout and stderr to the specified stream fscanf int fscanf FILE stream char format TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib fscanf reads characters from the specified stream interpreting the characters as specified in the format string The interpreted characters are written to the variables pointed to by the arguments that follow the format argument The format string is regarded as a sequence of
3. EM2 GDIO and PCIF But note that this is not a full list and in future more node types may be added If the node identified by nodeid is a valid node 0 is returned and nname is set to the name of that node If nodeid does not identify a valid node and upon error a value of 2 or higher is returned Example c6 0 MODa ROOT 1 0x02 module2 out fpga 0 io2v2 normal 0x04 rbtfile rbt em2 0 ibe normal 0x06 With the above network file definitions GetNodeName 0 amp nname will return 0 and MODa will be written to nname GetNodeName 1 amp nname will return 0 and io2v2 will be written to nname GetNodeName 2 amp nname will return 0 and ibc will be written to nname And GetNodeName 3 amp nname will return an error because there s no fourth node definition Include include hesl h Return value GetNodeName will return a value of O if the node identified by node index nodeid is defined in the network file nname is then set to the name of that node The function will return a value of 2 or higher if nodeid is an invalid node id and upon error int hesl GetNodeRstAccessId int nodeid int bdid i GetNodeRstAccessId is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information
4. Error 3882 Unable to HSB access slave board od Das master board is not a HEPC9 Internal error When trying to zap HEART on a slave board it was found that the slave board has a master board via which to access the slave board that is not a HEPC9 or HECPCI9 Please contact support and send your network file Error 3900 Error reading ELF file s os error Yod There was an error reading the PowerPC executable file as specified The function used was the standard C fread and the os error shown is errno Error 3901 File s is not an ELF file The PowerPC executable file as specified is not a proper PowerPC executable file Perhaps it is corrupted or the wrong file was specified in the network file Error 3902 File s is not 32 bit ELF x The PowerPC executable file as specified is not a proper 32 bit PowerPC executable file Perhaps it is corrupted or the wrong file was specified in the network file The code in brackets is the object type as found in the file s header 179 HUNT ENGINEERING Server Loader USER MANUAL Error 3903 File s is not little endian ELF x The PowerPC executable file as specified is not a proper little endian 32 bit PowerPC executable file Perhaps it is corrupted or the wrong file was specified in the network file The code in brackets is the endian type as found in the file s header Error 3910 Error reading ELF file s os error Yod There was an error reading t
5. So you will be fine if for the heron id you simply write the slot number In the above the software will update heron id 0x05 to the correct heron id 0x15 automatically Error 0200 Line d Node s says it s on board d but there s no such HERON carrier The board number used in a PCIF node statement does not refer to a valid board Valid boards are defined by BD statements Board number 0 refers to the first BD statement board number 1 to the second BD statement and so on BD API hep9a 1 0 board number 0 122 HUNT ENGINEERING Server Loader USER MANUAL PCIF 1 mynode normal 0x15 In the above board number 1 refers to a second BD statement but there s only one board defined The board number should be 0 referring to BD API hep9a 1 0 BD API hep9a 1 0 board number 0 PCIF 0 mynode normal 0x15 Error 0220 Line d Expected link number in HOSTLINK TOHOST FROMHOST statement The parser reached the end of file after processing HOSTLINWR TOHOST or FROMHOST A FIFO or Comport number was expected This FIFO or Comport identifies via what device the ROOT node is connected to the host PC HOSTLINK AN Error 0221 Line d Missing after s in HOSTLINK TOHOST FROMHOST statement The parser detects a missing closing bracket after an optional node name in a host statement after parsing HOSTLINB TOHOST or FROMHOST HOSTLINK xxx
6. this is board 1 EM2 0 em2a normal 0x56 BOOTLINK 0 0 1 0 The BOOTLINK definition defines a link between board 0 and board 1 but board 0 has no inter board module defined Error 0331 HSB more than once connects to board od Please use NOHSB in one or more BDCONN BDLINK statements to remove the loop n Connections created between inter board modules may also create HSB propagation paths You must be careful not to create loops that is each board must at most be accessed via one HSB path For example if you define two connections between two boards HSB can reach the second board via two paths Use the NOHSB keyword to select which connection will no propagate HSB BDCONN emia 0 em1b 0 BDCONN em1a 1 em1b 1 nohsb Error 0332 HSB more than once connects to board od Please use NOHSB in one or more BDCONN BDLINK statements to remove the loop n Connections created between inter board modules may also create HSB propagation paths You must be careful not to create loops that is each board must at most be accessed via one HSB path For example if you define two connections between two boards HSB can reach the second board via two paths Use the NOHSB keyword to select which connection will no propagate HSB BDCONN em2a 0 em2b 0 BDCONN em2a 1 em2b 1 nohsb You also need to be careful with more than 2 boards as you can create loops even while not using multiple links between any two
7. BD statement in the network file a board number 1 refers to the second BD statement in the network file and so on C6 x nw Error 0073 Line d Expected node name in C6 statement The parser reached the end of file after processing C6 lt n gt in a node statement A node name was expected C6 0 AN Error 0074 Line d Expected node type in C6 statement The parser reached the end of file after processing C6 lt n gt lt nodename gt in a node statement A node type ROOT or NORMAL was expected C6 0 mynode Error 0075 Line d Node s uses invalid node type s The parser expected to find a node type ROOT or NORMAL after parsing 111 HUNT ENGINEERING Server Loader USER MANUAL C6 lt n gt lt nodename gt in a node statement but found a text string that is not a valid node type i e the type string is not ROOT and is not NORMAL C6 0 mynode xxxx Error 0076 Line d Expected heron id in C6 statement The parser reached the end of file after processing C6 lt n gt lt nodename gt lt type gt in a node statement A heron id was expected C6 0 mynode normal N Error 0077 Line d Missing Di after Code Composer node id s for node s The parser detects a missing closing bracket after a Code Composer Studio id in a node statement after parsing C6 lt n gt lt nodename gt lt type gt ccid C6 0 mynode
8. BDCONN emnodea 0 xxxx Error 0379 Line d Node s says it s on board d but there s no such HERON carrier The parser successfully parses the node name in a BDCONN statement and finds that this node is an inter board module EM2 EM1 or EM1c But the board switch used in the inter board definition doesn t match any defined board BD API hep9a 5 0 this is board 0 BD API hep9a 2 0 this is board 1 EM2 0 em2a normal 0x56 EM2 1 em2b normal 0x36 BDCONN em2a 0 em2b The em2b inter board module is defined to have a board switch 0x36 suggesting a board with the red switch set to 3 But there is no HEPC9 defined with a red board switch set to 3 Error 0380 Line od BDCONN statement uses a node s that is not an inter board module The parser successfully parses the node name in a BDCONN statement but finds that this node is not an inter board module EM2 EM1 or EM1c FPGA 0 fpganode normal 0x02 myfile out BDCONN emnodea 0 fpganode Error 0381 Line od Expected fifo number in BDCONN statement The parser reached the end of file after processing BDCONN lt modname gt lt fifo gt lt modname gt in a BDCONN statement A fifo number was expected BDCONN emnodea 0 emnodeb AN Error 0382 Line d BDCONN statement uses invalid fifo number s The parser expected to find a fifo number after processing BDCONN lt modname gt lt fifo gt lt modname gt in a BDCONN statement but found a te
9. Boot network then run API application Server Loader executable DOS box The easiest way is to run the Server Loader executable in a DOS box and not use the Server Loader to do any serving Running the Server Loader without the s option will cause the Setver Loader to boot load and configure HEART connections only After the Server Loader exits your API program can then be started API application rules Note that in your API code you must not execute HeReset if you do you will reset the system and all booted programs and all HEART fifo connections will disappear It is not necessary to run HeartConf because the Server Loader will have configured all fifo connection you defined in the network file Example On the HUNT ENGINEERING CD you will find an example of using the Server Loader executable in a DOS box and then running a separate API application after that It s in software examples server_loader_examples c6x sl_api batch Boot network amp run API code in one application Server Loader library Alternatively you could use the library form of the Server Loader Similar to running the Server Loader executable in a DOS box just run the serverloader function of the hes class without the al option or use the loader function of the hes class After the serverloader or loader call completes your API code can be executed API application rules Note that in your API code
10. FIFONOBLOCK AN Error 0516 Line d FIFONOBLOCK statement od uses invalid heron id or node s The parser successfully parses the node name in a FIFONOBLOCK statement but finds that this node is not defined earlier in the network file FIFONOBLOCK xxxx Error 0517 Line d FIFONOBLOCK statement od uses non HERON node s The parser successfully parses the node name in a FIFONOBLOCK statement and finds that this node is defined earlier in the network file but the node is not a HERON node FIFONOBLOCK c4x Error 0518 Line d Expected fifo number in FIFONOBLOCK statement od The parser reached the end of file after processing FIFONOBLOCK lt nodename gt in a FIFONOBLOCK statement A fifo number was expected FIFONOBLOCK nodea AN Error 0519 Line od FIFONOBLOCK statement od uses invalid fifo number The parser expected to find a fifo number after processing FIFONOBLOCK lt nodename gt in a FIFONOBLOCK statement but found a text string instead FIFONOBLOCK nodea xxxx Error 0520 Line od FIFONOBLOCK statement d uses invalid fifo number od The parser successfully found and parsed a fifo number after processing FIFONOBLOCK lt nodename gt lt fifo gt in a FIFONOBLOCK statement but the fifo number is not a valid fifo number It must be a number from 0 to 5 FIFONOBLOCK nodea 7 N Error 0521 Line d Expected IN or OUT in FIFONOBLOCK statement od The parser reach
11. Some of these directories have sub directories as follows bin win32 Contains the Server Loader executable for 32 bit Windows bin vxworks Contains the Server Loader executable for VxWorks bin rtos32 Contains the Server Loader executable for RTOS 32 lib win32 Contains the Server Loader library amp DLL for 32 bit Windows lib vxworks Contains the Server Loader library for VxWorks lib rtos32 Contains the Server Loader library for RTOS 32 etc c4x idrom Contains source for the idrom out initialisation routine etc c4x examples Contains example programs for C4x systems etc c6x eeprom Contains source for the eeprom62 67 out view routine etc c6x examples Contains example programs for C6x systems Please note that for LINUX systems there is no bin directory Instead both the executable and the shared library of the Server Loader are in the src directory where a Makefile takes care of the installation this is used in the installme and uninstallme scripts Installation of the Server Loader Library The Setver Loader library is a set of functions that allows you to write your own Server Loader starting from what is already there the HUNT ENGINEERING Server Loader The library is all of the HUNT ENGINEERING Sertver Loader in DLL and 1ib 12 HUNT ENGINEERING Server Loader USER MANUAL format Windows 95 98 Windows NT and so format LINUX The API amp Tools installation should have copied the Server Loader libr
12. in a BDCAST statement but found a text string or found an invalid value for the UMI value use only values 0 to OxF 15 BDCAST bbc nodea 0 umi Oxff Error 0470 Line d Expected broadcast name in LISTEN statement d The parser reached the end of file after processing LISTEN in a LISTEN statement A broadcast name was expected LISTEN A Error 0471 Line od LISTEN statement d listens to unknown BDCAST s The parser successfully parses the broadcast name in a LISTEN statement but finds that this broadcast is not defined earlier in the network file by a BDCAST statement LISTEN xxxx Error 0472 Line d Expected node name in LISTEN statement d The parser reached the end of file after processing LISTEN lt broadcast gt in a LISTEN statement A node name was expected LISTEN bbc AN Error 0473 Line d LISTEN statement od uses invalid heron id or node s The parser successfully parses the node name in a LISTEN statement but finds that this node is not defined earlier in the network file LISTEN bbc xxxx Error 0474 Line d LISTEN statement od uses non HERON node s The parser successfully parses the node name in a LISTEN statement and finds that this node is defined earlier in the network file but the node is not a HERON node LISTEN bbc c4x Error 0475 Line d Expected fifo number in LISTEN statement d 140 HUNT ENGINEERING Server Loader USER MANUAL The parser reac
13. lt fifo gt lt nodename gt lt fifo gt lt v gt in a HEART statement but found a text string ot found an invalid value for the timeslot must be 0 to 0x3F HEART nodea 0 nodeb 0 v 255 AN Error 0416 Line d Expected timeslot value after t in HEART statement d The parser reached the end of file after processing HEART lt nodename gt lt fifo gt lt nodename gt lt fifo gt lt t gt in a HEART statement A timeslot was expected HEART nodea 0 nodeb 0 t N Error 0417 Line od HEART statement od in network file uses invalid time slot value s The parser expected to find a timeslot after processing HEART lt nodename gt lt fifo gt lt nodename gt lt fifo gt lt t gt in a HEART statement but found a text string ot found an invalid value for the timeslot use only values 0 to 5 137 HUNT ENGINEERING Server Loader USER MANUAL HEART nodea 0 nodeb 0 t 1 7 Error 0418 Line d Expected umi value in HEART statement d The parser reached the end of file after processing HEART lt nodename gt lt fifo gt lt nodename gt lt fifo gt lt tslot gt lt umi gt in a HEART statement A UMI number was expected HEART nodea 0 nodeb 0 2 umi AN Error 0419 Line od HEART statement od in network file uses invalid umi value Dias The parser expected to find a UMI value after processing HEART lt nodename gt lt fifo gt lt nodename gt lt fifo gt lt tslot gt lt umi
14. new operation Error 3440 Cannot open find file s Unable to open the PowerPC out file specified Error 3441 Out of memory creating ELF object Out of memory when trying to create an object for loading the PowerPC out file The function used was the new operation Error 3442 Cannot load ELF file onto HEPC6 C6x Error 3443 Cannot load ELF file onto HEPC6 C6x The HEPC6 only supports one C6x Please amend your network file Error 3450 Target_node is NULL Internal error An internal pointer points to NULL whereas it should be pointing to the node to be booted Please contact support and send your network file Error 3451 Incorrect data read from IDROM packet_type Error 3452 Incorrect data read from IDROM destination Error 3453 IDROM sends packet 0x x dwords larger than packetsize 0x x The Server Loader has booted the C6x module with the IDROM reader but the data returned is not correct possibly because the data has been corrupted Error 3500 Board s node os Unable to load node Cannot load a C4x out file C6x out file PowerPC file or bitstream onto an inter board connector module Error 3510 Board s node s Unable to load node Cannot load a C4x out file C6x out file PowerPC file or bitstream onto a host device PCIF Error 3520 Board s node Y os Unable to load node Cannot load a C4x out file C6x out file PowerPC file or bitstream onto GDIO module
15. Error 5000 Unable to HSB access slave board od os no master board found Internal error When trying to zap HEART on a slave board it was found that the slave board has no master board via which to access the slave board Please contact support and send your network file Error 5001 Unable to HSB access slave board od Das master board is not of type API Internal error When trying to program HEART on a slave board it was found that the slave board has a master board via which to access the slave board that is not of type BD APP Please contact support and send your network file Error 5002 Unable to HSB access slave board od s master board is not a HEPC9 Internal error When trying to program HEART on a slave board it was found that the slave board has a master board via which to access the slave board that is not a HEPC9 or HECPCI9 Please contact support and send your network file Error 5003 Can t find switch setting of board od 181 HUNT ENGINEERING Server Loader USER MANUAL Internal error When trying to find the red switch setting of a valid board an error occurred Please contact support and send your network file Error 5004 Internal error No node information HEART statement d Error 5005 Internal error No node information HEART statement d Internal error A node pointer used in a HEART statement points to NULL Please contact support and send your network file Er
16. TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib fseek sets the file position for the specified stream The new position is at the signed distance offset characters from the location specified with origin The following macros are provided for specifying the origin SEEK_SET start of the file SEEK CUR current file position SEEK_END end of the file fseek undoes any effects due to the function ungetc That is any characters pushed back into a stream will be not be read and reading will proceed from the new position in the file If fseek completes successfully the function returns zero else it returns 1 ftell long ftell FILE stream TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib ftell returns the current offset in characters from the beginning for the specified stream 99 HUNT ENGINEERING Server Loader USER MANUAL fwrite size_t fwrite void ptr size_t size size_t nobj FILE Sei TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib fwrite writes nobj objects each of size characters in length from the memory pointed to by ptr to the specified stream It returns the number of characters successfully written Zero is returned if end of file is encountered or if an error occurs NOTE The size of C4x objects may vary from the size of objects on the host machine C4x types are all 32bits in size floats are 40 bits in size and therefore the size of an int or a character is 4 bytes g
17. The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was taskSpawn and the error EGAIN Error 7317 Cannot start thread for board d s invalid argument Internal error The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was taskSpawn and the error EINVAL Contact support and send your network file Error 7318 Cannot start thread for board od s unknown error Yd Internal error The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was taskSpawn and the error as specified Contact support and send your network file Error 7320 Cannot start thread for board d s too many threads The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was taskSpawn and the error EGAIN Error 7321 Cannot start thread for board d s invalid argument Internal error The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was taskSpawn and the error EINVAL Contact support and send your network file Error 7322 Cannot start thread for board d s unknown error od Internal error The Server Loader encountered an error when trying a start a threa
18. bdsw will identify the board via which reset for the node nodeid can be accessed Note that GetNodeRstAccessSw will write a character string to dev so parameter dev must be an character array or point to an allocated memory area Note that this function works like GetNodeBoardId retrieving the board index of the board that the node is on followed by GetBoardRstAccessSw which finds the board via which reset can be accessed on the first board Note that GetNodeRstAccessSw is identical to GetNodeRstAccessId but that the access board is identified with dev and bdsw in GetNodeRstAccess Sw but with id in GetNodeHsbAccessId Nodes can be identified with a node id nodeid In your network file the very first node definition will define a node with index 0 the second node definition will define a node with id 1 and so on Examples of node definitions are C6 FPGA EM2 GDIO and PCIF But note that this is not a full list and in future more node types may be added Upon error the function returns a value of 2 or higher Otherwise it will return 0 and dev and bdsw will be set to the board via which reset for node nodeid can be accessed Example BD API hep9a 3 0 BD API hep9a 5 0 remote c6 0 MODa ROOT 1 0x02 module2 out fpga 1 io2v2 normal 0x14 rbtfile rbt em2 0 em2a normal 0x06 em2 1 em2b normal 0x16 BDCONN EM2a 0 EM2b 0 With the ab
19. console and read from the stdin console Parameters whichfie selects a server function In hesl h you can find a list of server functions that may be replaced by your own For example USER_SRV_FWRITE selects the fwrite function Note that the printf function is executed by a call to fwrite using a file parameter stdout 1 see stdioc60 h fie is a pointer to function that implements the selected server activity The function is supplied by you and uses a pointer to a structure as parameter The structure SRVFIEPARAMS is defined in hesl h The structure s fields are buf pointer to a buffer of data blks number of blocks 92 HUNT ENGINEERING Server Loader USER MANUAL elts number of elements Fd file descriptor bdname board name e g hep9a bdno board switch fifo fifo The last three parameters will indicate what server thread the request came from board type bdname board number bdno and fifo Parameter Fd will tell you the file handle Fd 0 for stdin Fd 1 for stdout and Fd 2 for stderr All other file handles are processed by the Server and you cannot redirect or replace this The buf parameter points to a string buffer and blks elts is the size These are the parameters as used by fwrite and fread The other functions use the same parameters although the parameter naming will not indicate the intended use We will now discus
20. has two possible values 0 and 1 Parameters The two nodes are identified with node id s fromid and toid In your network file the very first node declaration e g ND Co FPGA EM2 will define a node with id 0 the second node declaration will define a node with id 1 and so on If a fifo connection exists for connection index idx then the fifo on the from node is returned in from fifo and the fifo on the to node is returned in to fifo and the function returns the value 0 If there is no fifo connection for connection index idx the function returns 1 Upon error the function returns a value of 2 or higher The two nodes may be on different boards If there are fifo connections between the two nodes that pass inter board connectors FindNodeConn will return such a connection with the right idx parameter Example Modules on board 0 c6 0 MODa ROOT 1 0x01 modulel out fpga 0 MODb normal 0x02 bitstream rbt gdio 0 MODc normal 0x03 c6 0 MODd normal 0 0x04 module2 out HEART MODa 2 MODd 1 With the above network file definitions FindNodeConn 0 3 amp f amp tf 0 will return 0 ff will be set to 2 and tf to 1 But FindNodeConn 1 0 amp ff amp t 0 will return 1 because there s no fifo connection from node MODd to MODa FindNodeConn 5 0 amp f amp t 0 will return an error because there s no node with id 5 Include inclu
21. reports an error while trying to halt Debug gt Halt a node in the system Error 8515 HaltFirst Exception s The Server Loader plugin or the Server Loader executing with the g option reports an error while trying to halt Debug gt Halt a node in the system Error 8530 Run Exception s The Setrver Loader plugin or the Server Loader executing with the g option reports an error while trying to run Debug gt Run a node in the system Error 8541 Unable to load file Y od s The Setver Loader plugin or the Server Loader executing with the g option reports an error while trying to load the symbols of an executable file File gt Load Symbols for a node in the system Error 8550 LoadProgram Exception s The Server Loader plugin or the Server Loader executing with the g option reports an error while trying to load the executable file File gt Load Program for a node in the system Error 8570 LoadSymbols Exception s The Server Loader plugin or the Server Loader executing with the g option reports an error while trying to load the symbols of an executable file File gt Load Symbols for a node in the system Error 8600 Problem doing RunFree The Server Loader plugin or the Server Loader executing with the g option reports an error while trying to execute RunFree Debug gt Run Free for a node in the system Error 8601 Problem s when prepari
22. t Use out files Release Debug Source radio boxes v n Not implemented c n Not implemented ipath Not implemented d Not implemented w Not implemented g You re already in debugging mode k Property Page Use Packets check box k n Property Page Packet Size X Property Page Automatic Matching check box g n Property Page Wait Factor j Property Page Use boot jumpers check box S L exe P Soemhunt apil Sshesl bin win32 wing2sl Browse Network file c oemhuntapil S hesl etc c6s examples stdtest Browse S L exe Default Network file Default Packet Size f1024 I Use Packets Wait Factor f V Automatic Matching of Heron ID s with Code Composer objects Load system using Code Composer Studio J Use boot jumpers HEPC9 only I Keep LOG of actions Cancel Apply 26 HUNT ENGINEERING Server Loader USER MANUAL The bootloader Function What is the bootloader Function and How do I use it The Server Loader loads processors behind the root processor using a boot loader function on all processors The bootloader function forwards packets of code between the processors until the destination processor is reached A packet typically consists of a header plus raw data i e chunks of code to be loaded onto the target processor The processor next to the processor to be loaded will strip the header off and boot the target processor To ensure this process wo
23. 57 HUNT ENGINEERING Server Loader USER MANUAL Server Loader and a separate API application in parallel Two DOS boxes You could run the executable Server Loader in a DOS box in parallel with an API based application running in another DOS box Open a DOS box run the executable Server Loader with your network file Open another DOS box and run your API application there In the network file you will have defined host module fifo connections for use by your API application using NOSERVE to reserve the connections for use by your API application And of course you will have defined bi directional host module fifo connections for all processor nodes that you wish to be served by the Server Loader API application rules Note that in your API application you must not execute HeReset if you do you will reset the system and all booted programs and all HEART fifo connections will disappear It is not necessary to tun HeartConf because the Server Loader will configure all fifo connections you defined in the network file Synchronisation You may need to care about the synchronisation between the Server Loader and the API application While booting loading the processor nodes and configuring HEART the Server Loader will use fifo 0 and HSB The API application should not open those devices until the Server Loader has completed the boot load process and configured HEART As in this case you run the Server Loader in a DOS box
24. HeartConf also has its own library functions As with serverloader and loader there are 4 shapes int heartconf int heartconf int heartconf int heartconf int argc char argv char options char network HE HANDLE uDevice int n int argc char argv HE HANDLE uDevice int n char options char netwrk LE SE ee oe The top heartconf entry has two parameters an argc parameter that is the number of argv arguments and the argv parameter itself which is an array of character string pointers This is identical to the arguments used by main in a console program However HeartConf accepts fewer arguments than the Server Loader only r reset 38 HUNT ENGINEERING Server Loader USER MANUAL v verbose z no zap and b0 1 2 3 are accepted Example int main int argc char argv hesl sl int r sl heartconf argc argv The second heartconf entry allows all options to be specified in one string and the network file in another string For example int r sl heartconf r network In some applications you may already have 1 or more handles open to devices such as a fifo or HSB As HeartConf may also access those same devices you would have to close all devices before calling HeartConf An alternative is offered by the handle functions int heartconf HE HANDLE uDevice int n int argc char argv int heartconf HE HANDLE uDev
25. IS 90 HUNT ENGINEERING Server Loader USER MANUAL The serverloader function will reset boot configure HEART start and serve a system of Cox FPGA and other types of nodes as per the network file that it is asked to process Include include hesl h Parameters options is a pointer to a character string that holds Server Loader options for example rlsv for a full list of options please refer to Invoking the command line Server Loader on page 14 Parameter network is a pointer to a character string that represents the path and name of the network file Return value serverloader will return 0 upon success and return 2 or higher upon error Use get lasterr of the hesl class for a description of the error int hesl serverloader HE HANDLE uDevice int n int argc char argv The serverloader function will reset boot start configure HEART and serve a system of C6x FPGA and other types of nodes as per the network file that it is asked to process Include Hinclude hesl h Parameters argv is an array of pointers to character strings and argc is the number of entries in the argv array Each character string should represent a Server Loader option for example r for reset for a full list of options please refer to Invoking the command line Server Loader on page 14 One character string would represent the path and name of the network file Parameter uDe
26. It s a bit unclear how much time is sufficient and per machine it will differ How to solve this properly Sleep net GetFactor 1000 if vr 0 r net open Open all the boards if r 0 r net reset Reset all the boards Sleep 100 cc MatchHeronId2CCid amp net match CCid with HeronId Sleep 100 52 HUNT ENGINEERING Server Loader USER MANUAL if r 0 r net load load all the nodes Sleep net GetFactor 1000 now all nodes are running in bootloader cc PrepareDebugging amp net set breakpoints ona Sleep net GetFactor 1000 specific point in exit of bootloader if r 0 r net run O run all the nodes we ll hit breakpoint Collect all the breakpoint hits of all tasks cc OnHitBreakpoint amp net Move from our breakpoint to the line after bootloader cc StartDebugging amp net CoUninitialize Done using CCS if r 0 net serfit if you need the server net close Legacy build The network common and ccif classes are now a legacy interface and will be obsoleted in future Please use the hes class as described in earlier sections in this Chapter for new projects The network common and ccif classes will remain supported for some time to support existing applications If you have a look in the network h file you ll find that there are a number of environment variables WIN32 CCSTUDIO CMDLINE and
27. It should be used in place of exit as the latter does not guarantee proper termination of the Server Loadet The status argument is used to inform the operating system of the exit status of the program This value is passed to the host operating system after program termination This function call never returns 102 HUNT ENGINEERING Server Loader USER MANUAL srv_system int srv_system char str TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib srv_system passes the string str to the host command line interpreter for execution as if it were a host command The string str should be a valid host command If the system command is successfully executed the function returns zero otherwise a non zero value is returned The return value of the host command is not returned to the caller Note The backslash character NV used in MS DOS is an escape character in C string literals and must therefore be written as AN sscanf int sscanf char str char format TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib sscanf reads input from the string str interpreting it according to the specified format The results of each successfully interpreted element of the format string are written to the locations pointed to by the arguments following the format string The meaning of the format argument is identical to that for the function fscanf If the end of the string is encountered before any successful conversion i
28. Please use NOHSB in one or more BDCONN BDLINK statements to remove the loop Error 1501 HSB more than once connects to board d Please use NOHSB in one or more BDCONN BDLINK statements to remove the loop Connections between inter board connector modules on different boards transport control signals reset HSB when the boards are configured as master and slave s But there may only be one control path between a master and a slave or between successive slave boards Use the NORESET and NOHSB keywords to select what inter board connection should carry the control signals For example BD API hep9a 0 0 BD API hep9a 1 0 slave BD API hep9a 2 0 slave BDLINK 0 0 1 0 BDLINK 1 1 20 BDLINK 01 21 In this case both slave boards can be reached by the master board via two paths For hep9a 1 0 this can be via BDLINK 0 0 1 0 or via the other board first via BDLINK 0 1 2 1 then BDLINK 1 1 2 0 You must break the circular connections between the boards by ensuring there s only one control path to any board For example BD API hep9a 0 0 BD API hep9a 1 0 slave BD API hep9a 2 0 slave BDLINK 0 0 1 0 BDLINK 1 1 20 BDLINK 0 1 21 NORESET NOHSB Error 1502 BDCONN BDLINK statement cannot connect to non HEART board God You can only connect HEPC9 boards with a BDCONN BDLINK statement as only HEPC9 s can have an inter board connector module e g EM2 or EM1 Error 1510 RESET more than once connects to board
29. The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was pthread_create and the error EINVAL Contact support and send your network file Error 7311 Cannot start thread for board od s unknown error Yd Internal error The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was pthread_create and the error as specified Contact support and send your network file Error 7313 Cannot start thread for board od s too many threads The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was pthread_create and the error EGAIN Error 7314 Cannot start thread for board d s invalid argument Internal error The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was pthread_create and the error EINVAL Contact support and send your network file Error 7315 Cannot start thread for board od s unknown error od Internal error The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was pthread_create and the error as specified Contact support and send your network file Error 7316 Cannot start thread for board d s too many threads
30. UMIRESET nodea 7 N Error 0506 Line d Expected IN or OUT in UMIRESET statement od The parser reached the end of file after processing UMIRESET lt nodename gt lt fifo gt in a UMIRESET statement An IN or OUT keyword was expected UMIRESET nodea 0 AN Error 0507 Line d Expected IN or OUT in UMIRESET statement od The parser successfully found and parsed a string after processing UMIRESET lt nodename gt lt fifo gt in a UMIRESET statement but the string is not the expected string it must be IN or OUT UMIRESET nodea 0 xxxx Error 0508 Line d Expected umi value in UMIRESET statement d The parser reached the end of file after processing UMIRESET lt nodename gt lt fifo gt lt umi gt in a UMIRESET statement A UMI number was expected UMIRESET nodea 0 in umi AN Error 0509 Line od UMIRESET statement od in network file uses invalid umi line s The parser expected to find a UMI value after processing UMIRESET lt nodename gt lt fifo gt lt umi gt in a LISTEN statement but found a text string or found an invalid value for the UMI value use only values 0 to OxF 15 UMIRESET nodea 0 umi Oxff 142 HUNT ENGINEERING Server Loader USER MANUAL Error 0515 Line d Expected node name in FIFONOBLOCK statement od The parser reached the end of file after processing FIFONOBLOCK in a FIFONOBLOCK statement A node name was expected
31. and the os error shown is errno Error 3931 Unable to allocate memory d bytes while reading ELF file There was an error trying to allocate temporary memory The function used was the standard C malloc Error 3932 Error reading ELF file s os error Yod There was an error reading the PowerPC executable file as specified The function used was the standard C fread and the os error shown is errno Error 3940 No section headers can t read string table ELF file s When processing the PowerPC executable file as specified it was found that the file header contains no section headers Perhaps the file is corrupted or you specified the wrong file in the network file Error 3941 No retrievable string table in ELF file s index Yod max d When processing the PowerPC executable file as specified it was found that the string table section looks unusable Perhaps the file is corrupted or you specified the wrong file in the network file 180 HUNT ENGINEERING Server Loader USER MANUAL Error 3942 Error seeking ELF file s sh offset Yod os error d There was an error seeking the PowerPC executable file as specified The function used was the standard C fseek and the os error shown is errno Error 3943 Unable to allocate memory od bytes while reading ELF file There was an error trying to allocate temporary memory The function used was the standard C malloc Err
32. bdid is NULL in GetBoardHsbAccesslId Error 1720 Parameter bdid is NULL in GetBoardRstAccesslId The second parameter supplied to GetBoardHsbAccessId or GetBoardRstAccessId is a NULL pointer Error 1721 Internal Error board d found to be NULL boards d The first parameter supplied to GetBoardHsbAccessId or GetBoardRstAccessId is valid board index yet it is found it points to NULL Please contact support and send the network file Error 1722 Cannot find board id for switch od 161 HUNT ENGINEERING Server Loader USER MANUAL Internal error Found the master board for the specified board first parameter of GetBoardHsbAccessId or GetBoardRstAccessId but unable to find the board index for this board Error 1723 Internal Error hsb master board was not a BD API board slave d Internal error Found the master board for the specified board first parameter of GetBoardHsbAccessId or GetBoardRstAccessId but the board is not of type BD APP Only BD APP type boards can be slave or master boards Error 1724 Internal Error hsb master board was found to be NULL slave d Internal error There is no master board for the specified board first parameter of GetBoardHsbAccessId or GetBoardRstAccessId This is an internal error as slave boards without a master board should be been caught when the network file gets parsed and processed Error 1725 Board od is not a BD API board GetBoardHsbAccessId or GetBoar
33. but there s only one board defined The board number should be 0 referring to BD API hep9a 1 0 BD API hep9a 1 0 board number 0 FPGA 0 mynode normal 0x11 myfile out Error 0130 Parsing s Too many nodes maximum is d For each node defined in the network file ND C6 C4 FPGA GDIO PCIF etc an internal object is created Because only so many objects can be stored in the array that the Server Loader and HeartConf software uses there is a maximum number of nodes that can be processed This error is returned when in your network file you define more nodes than the software can process maximum of 256 nodes Error 0131 Line d Expected board number in GDIO statement The parser reached the end of file after processing GDIO in a node statement A board number referring to a BD statement was expected GDIO AN Error 0132 Line d Node od uses invalid board number s The parser expected to find a board number after parsing GDIO in a node statement but found a text string instead A valid board number is a digit that indicates what board statement the node is on The number must refer to a BD statement e g a board number 0 refers to the first BD statement in the network file a board number 1 refers to the second BD statement in the network file and so on GDIO x Error 0133 Line od Expected node name in GDIO statement
34. net open if r 0 r net reset if r 0 r net load if r 0 r net run if r 0 net serfit net close D reset system yes load system yes serve system yes verbose yes argv 1 is network file Open all the boards Reset all the boards load all the nodes von all the nodes serve all the nodes legacy Class network interface parameters The network class is now a legacy interface and will be obsoleted in future Please use the hes class as described in earlier sections in this Chapter for new projects The network class will remain supported for some time to support existing applications Typically you would want a little bit more control over the execution of the Server Loader library The network class allows you to set the same parameters as on the Server Loader command line such as r v and so on The functions are char void void void void void void void void void void void void void void void void void AddIncludePath char s AddNetworkFileName char s SetResetSwitch int r SetLoadSwitch int r SetRunSwitch int r SetServeSwitch int r SetVerboseSwitch int r SetDebugSwitch int r SetFactor ant C SetUsePackets int r SetPacketSize ant zk SetDualSwitch int r SetpgFlashSwitch int r SetFlashSwitch int r SetAutoCCSwitch int r SetWait Period eat a SetSkipFPGA int
35. or NORMAL was expected PCIF 0 mynode N Error 0195 Line d Node s uses invalid node type s The parser expected to find a node type ROOT or NORMAL after parsing PCIF lt n gt lt nodename gt in a node statement but found a text string that is not a valid node type i e the type string is not ROOT and is not NORMAL PCIF 0 mynode xxxx Error 0196 Line od Expected heron id in PCIF statement The parser reached the end of file after processing PCIF lt n gt lt nodename gt lt type gt in a node statement A heron id was expected PCIF 0 mynode normal AN 121 HUNT ENGINEERING Server Loader USER MANUAL Error 0197 Line Yod Node s uses invalid heron id s The parser expected to find a heron id a decimal or hexidecimal number after parsing PCIF lt n gt lt nodename gt lt nodetype gt in a node statement but found a text string instead Precede a hexidecimal number with Ox PCIF 0 mynode normal xxxxx Error 0198 Line d Node s uses invalid heron id s nHost PC interface slot number is 5 so its heron id must be 0x05 0x15 0x25 etc The parser has found and parsed a heron id after parsing PCIF lt n gt lt nodename gt lt nodetype gt lt heronid gt in a node statement but the heron id is not a valid number Bits 7 6 5 4 identify the board switch of the board the module in on and bits 3 2 1 0 identify the slot A val
36. tfifo to 0 FindIBCLink 1 1 amp tnode amp tfifo will return 0 but tnode and tfifo will be set to 1 as nothing is connected to em2a channel 1 FindIBCLink 0 0 amp tnode amp tfifo will return an error because the node with id 0 i e MODa is not an inter board module Include include hes h Return value FindIBCLink will return a value of 2 or higher upon error and 0 if no error was encountered When no connection was found to fnode_id channel ffifo tnode_id and tfifo are set to 1 If a connection was found tnode_id is the node id of the inter board module connected to and t fifo is the channel on that inter board module connected to 64 HUNT ENGINEERING Server Loader USER MANUAL int hes1 FindNodeConn int fromid int toid int fro fifo int to fifo int idx i FindNodeConn is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file FindNodeConn checks whether two nodes have a FIFO connection As there can possibly be more than 1 such connection parameter idx identifies a connection index Use FindNodeConnCount to retrieve the number of connections between the two nodes If there are for example 2 fifo connections between the two nodes parameter idx
37. the two nodes that pass inter board connectors FindNodeConnCount will count such a connection Example c6 0 MODa ROOT 1 0x01 modulel out fpga 0 MODb normal 0x02 bitstream rbt gdio 0 MODc normal 0x03 c6 0 MODda normal 0 0x04 module2 out HEART MODa 2 MODd 1 HEART MODa 3 MODd 4 With the above network file definitions FindNodeConnCount 0 3 amp cnt will return 0 and cnt will be set to 2 FindNodeConnCount 5 0 amp cnt will return an error because there s no node with id 5 Include include hesl h Return value FindNodeConnCount will return a value of 2 or higher upon error and 0 if no error was encountered Paramater count will be set to the number of fifo connections found between the two nodes void hesl FlagMeServerUp HANDLE s For Operating Systems other than Windows the parameter type is different void FlagMeServerUp SEM ID s VXWORKS void FlagMeServerUp sem t s LINUX void FlagMeServerUp RTKSemaphore s RTOS32 FlagMeServeruUp takes a semaphore as a parameter and when a network file is loaded successfully the semaphore is flagged Its purpose is with multi threaded programs where one thread executes the Server Loader and another thread must wait until the Server Loader has loaded all nodes before it starts communicating with one or more nodes in the network 66 HUNT ENGINEERING Server Loader USER MANUAL The semaphore will only be flagged when the Server Loader is cal
38. there is no binary backward compatibility A C4x application developed for Server Loader 2 7 or earlier would need re compilation and re linking with a version 3 1 3 2 3 3 library Please note that this version of the Server Loader supports using Code Composer Studio with the personalised Server Loader for WIN32 This support made it necessary to add some new fields in the network class making the win32sl dll libraries of 3 0 vs 3 1 3 2 3 3 non compatible Compatibility still remains on a source level re compile and re link your Server Loader 3 0 projects and they ll work with the 3 1 3 2 3 3 library win32sl dll But make very sure that you use the new version 3 2 3 3 network h common h and ccif h include files and define the new CCSTUDIO pre processor variable Two functions have been added to make combined Server Loader Hunt Engineering API programs a bit easier They are members of the network class char GetDevName int brdno int GetBoardNo int brdno int GetComport int brdno GetDevName will return the name of the board as described in the network file GetBoardNo will return the board number and GetComport the comport number Together the 3 functions will return the information needed to start an API program e g hep8a 0 a The brdno mentioned as parameter is the board definition line as it is described in the network file If you have a network file as follows for example BD API hep8a 2 0 BD API hep8a 3 0
39. 0x300 Please correct the relevant BD statement in your network file Error 2611 Invalid device Yoc cannot open HEPC2E direct access HEPC2E boards can only use ComportA 0 or ComportB 1 Please correct the relevant BD statement in your network file Error 2620 Invalid board address 0x x cannot open HEPCO6A direct access HEPC6 boards can only have addresses 0x160 0x200 or 0x300 Please correct the relevant BD statement in your network file Error 2621 Invalid device c cannot open HEPC6A direct access HEPC6 boards can only use ComportA 0 Please correct the relevant BD statement in your network file Error 2622 Dual switch option d cannot be used with HEPC6 as there is only one device HEPC6 boards can only use ComportA 0 Therefore dual operation Cd option is not possible In dual operation 2 host fifo s are used one to send communications to the ROOT node and another to recetve communications from the ROOT node Error 2700 Cannot close board s s Error 2701 Cannot close board s s Error 2702 Cannot close board s s The HUNT ENGINEERING API software reports that an error occurred when trying to reset the specified device The error code in brackets is the API error code Error 3001 Cannot find base node of s The Server Loader HeartConf is not able to find a path from the host to the node specified Add BOOTLINK sta
40. 44 0 1278 760775 ot by calling the general number 44 0 1278 760188 and choosing the technical support option 105 HUNT ENGINEERING Server Loader USER MANUAL Appendix A Error Codes Error 0002 Failed to open network file Y s Unable to find or open the network file specified Verify that the file exists and that the file s security settings permit reading by the current user Error 0003 Network file s declares too many boards maximum is d For each board defined in the network file BD statement an internal object is created Because only so many objects can be stored in the array that the Server Loader and HeartConf software uses there is a maximum number of boards that can be processed This error is returned when in your network file you define more boards BD statement than the software can process maximum of 16 boards Error 0011 Line d Expected board type in BD statement The parser reached the end of file after processing a BD statement A board type such as APT was expected BD AN Error 0012 Line d Unknown board type s in BD statement After the keyword BD in a board statement a board type is expected The board type must be the text string APP This error indicates that a text string was found specifying a board type that was not recognised BD xxxx The Server Loader and HeartConf software also have legacy support where certain boards are ac
41. After a successful call to load all booted processors are executing the bootloader routine waiting for a command to start executing the rest of the main routine The run function does exactly this Upon success 0 is returned any other value denotes some error If you need to use the Server Loader s serve capability now execute the serfit routine This will execute stdio requests coming in from the network As soon as a srv_exit is executed on the ROOT DSP the serfit function will terminate The srv_exit tells it so do so Upon success 0 is returned any other value denotes some error In case more than 1 processor uses the server HEPC9 serfit will wait until all processors that use the server have called srv_exit Note that any processor with a duplex connection to the PC is deemed to be served and must do a srv_exit Finally call close This will close the boards opened with the open function 48 HUNT ENGINEERING Server Loader USER MANUAL Example The essence of using the Server Loader library is in the following code snippet include include include include include lt stdio h gt lt stdlib h gt lt string h gt heapi bn network bn int main int argc char argv int network net gt SetResetSwitch TRUE net gt SetLoadSwitch TRUE net gt SetServeSwitch TRUE net gt SetVerbose TRUE r net parse input file argv 1 if r 0 r
42. BOOTLINK mynode 1 othernode 0 BOOTLINK mynode 2 othernode 0 126 HUNT ENGINEERING Server Loader USER MANUAL Error 0293 Line d Link d on s used at least twice in BOOTLINK statements You have used the same FIFO or Comport two times or more in BOOTLINK statements But each FIFO or Comport can only be connected to once BOOTLINK mynode 0 othernode 1 BOOTLINK mynode 0 othernode 2 Error 0294 Line d NOBLOCK may only be used in BOOTLINK statements using HERON BASE2 modules The NOBLOCK keyword used with a BOOTLINK or BOOTPATH statement is only supported for modules on a HERON BASE2 carrier board BOOTLINK mynode 0 othernode 0 noblock Node mynode or othernode are not modules on a HERON BASE2 Error 0295 UMI may only be used in BOOTLINK statements using HERON BASE2 modules The UMI keyword used with a BOOTLINK or BOOTPATH statement is only supported for modules on a HERON BASE2 carrier board BOOTLINK mynode 0 othernode 0 umi 1 Node mynode or othernode are not modules on a HERON BASE2 Error 0296 Line d Expected umi value in BOOTLINK statement The parser reached the end of file after processing BOOTLINK lt nodename gt lt fifo gt lt nodename gt lt fifo gt lt umi gt in a BOOTLINK BOOTPATH statement A UMI number was expected BOOTLINK mynode 0 othernode 0 umi AN Error 0297 Line od BOOTLINK statement uses invalid umi value s The parser expected to find a UMI
43. HEPC6A direct access The network file uses a BD hepc6 with a device other than FifoA The HEPC6 only has one fifo device FifoA Error 3700 Invalid device Yoc cannot write HEPC2E direct access Error 3701 Invalid device c cannot read HEPC2E direct access Error 3708 Invalid device oc cannot read HEPC2E direct access The network file uses a BD hepc2e with a device other than FifoA or FifoB The HEPC2E only has two fifo devices FifoA and FifoB Error 3800 HERON id 0x x doesn t match any HEPC9 board switch Cannot boot node When trying to create HEART connections a HERON ID as specified was found that doesn t match any defined boards in the network file Bits 7 4 of the HERON ID are the red switch setting of a carrier board such as e g HEPC9 or HERON BASE2 177 HUNT ENGINEERING Server Loader USER MANUAL Error 3820 Failed to program IBC on board s Error 3822 Failed to program IBC on board s Internal error When trying to create HEART connections HeartConf was unable to find the configuration code for programming an IBC inter board connector Please contact support and send your network file Error 3824 Failed to close HSB board od s There was an error when trying to close HSB The error description in brackets is from the HUNT ENGINEERING API HeOpen function The error code in brackets is an API error code Error 3840 HERON id 0x x doesn t match any HEPC9 board sw
44. Internal error Cannot find board switch for board od HeartConf cannot find the red board switch setting of a board definition BD API This is an internal error Pleaes contact support and send the network file 150 HUNT ENGINEERING Server Loader USER MANUAL Error 1308 No inter board module defined for board od A HEART statement defines a connection between two modules on different boards but one of the boards doesn t have an inter board connector module such as EM1 or EM2 defined therefore the required connection cannot be configured Error 1309 You cannot use inter board module EM1 C s for board to board connections Use an EM1 or EM2 for that or define two systems connected by the EM1 C The EM1 C inter board connector module can only be used between two stand alone systems You cannot use HEART statements to connect modules on boards that are connected via EM1 C s Error 1310 Internal error Cannot find board switch for board od HeartConf cannot find the red board switch setting of a board definition BD API This is an internal error Pleaes contact support and send the network file Error 1311 No inter board module defined for board d A HEART statement defines a connection between two modules on different boards but one of the boards doesn t have an inter board connector module such as EM1 or EM2 defined therefore the required connection cannot be configured Error 1312 You cannot use
45. It is implemented as a macro See set vbuf below setvbuf int setvbuf FILE stream char buf int mode size t size TI C4x Library stdio xx lib TI C6x Library stioxxxx lib setvbuf is used before any input or output operation is done on an opened stream to change the mode of buffering The mode argument determines how the stream should be buffered and should be one of the following macros _IOFBF The stream is fully buffered _IOLBF The stream is line buffered _IONBF The stream is unbuffered If the argument buf is a null pointer then the originally allocated buffer is used The size argument specified the size of the buffer The function returns zero if successful else non zero is returned sprintf int sprintf char str char format TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib sprintf writes formatted output to the string str according to the specified format The meaning of the format string is identical to that for fprintf The output string is terminated with a NUL character The function returns the number of characters written to str not including the NUL terminating character srv exit void srv exit int status TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib srv_exit is the normal way of terminating the program execution on the root node It is required to guarantee the correct shut down of the Server Loader on the host as well as for terminating program execution on the root node
46. JTAG chain minus 1 In a case you want to force the Server Loader not to do the automatic matching use the x option For HERON systems using automatic matching is the default and the Code Composer Studio IDs in the network file are ignored unless you use the x switch Embedded HEART programming There are situations where you don t want or cannot employ HeartConf or the Server Loader but you still need to program HEART to create fifo connections It is possible to ask HeartConf and or the Server Loader to create a file that when executed will program HEART When you execute HeartConf or the Server Loader with the b0 option a C file will be written for use with a host program which when executed will program HEART according to the network file you used to produce the file When you use the b1 option a VHDL file fit for use with a Spartan device will be generated When you use the b2 option a VHDL file fit for use with a Virtex II device will be generated And when you use the b3 option a C file fit for use with Code Composer Studio and HERON API will be generated The generated VHDL files are really only initialising a buffer in block ram and you need some HIL VHDL to actually execute the parameters stored in the buffer The C code generated is in the shape of a function The Confidence Checks program implements a Windows front end to the bh feature Goto HEART gt Configure HEART Then select network file and pr
47. Line od Expected out filename in ND or C4 statement The parser reached the end of file after processing ND lt n gt lt nodename gt lt type gt lt ccid gt lt gbcw gt lt Ibew gt lt iack gt in a node statement A filename was expected The filename would be a C4x out file usually preceded by idrom out ND 0 mynode normal 0 00000000 00000000 002f 800 AN Error 0070 Parsing s Too many nodes maximum is d For each node defined in the network file CND C6 C4 FPGA GDIO PCIF etc an internal object is created Because only so many objects can be stored in the array that the Server Loader and HeartConf software uses there is a maximum number of nodes that can be processed This error is returned when in your network file you define more nodes than the software can process maximum of 256 nodes Error 0071 Line d Expected board number in C6 statement The parser reached the end of file after processing C6 in a node statement A board number referring to a BD statement was expected C6 AN Error 0072 Line d Node od uses invalid board number s The parser expected to find a board number after parsing C6 in a node statement but found a text string instead A valid board number is a digit that indicates what board statement the node is on The number must refer to a BD statement e g a board number 0 refers to the first
48. The parser reached the end of file after processing GDIO lt n gt in a node 116 HUNT ENGINEERING Server Loader USER MANUAL statement A node name was expected GDIO 0 AN Error 0134 Line od Expected node type in GDIO statement The parser reached the end of file after processing GDIO lt n gt lt nodename gt in a node statement A node type ROOT or NORMAL was expected GDIO 0 mynode Error 0135 Line d Node s uses invalid node type s The parser expected to find a node type ROOT or NORMAL after parsing GDIO lt n gt lt nodename gt in a node statement but found a text string that is not a valid node type i e the type string is not ROOT and is not NORMAL GDIO 0 mynode xxxx Error 0136 Line od Expected heron id in GDIO statement The parser reached the end of file after processing GDIO lt n gt lt nodename gt lt type gt in a node statement A heron id was expected GDIO 0 mynode normal nw Error 0137 Line d Node s uses invalid heron id s The parser expected to find a heron id a decimal or hexidecimal number after parsing GDIO lt n gt lt nodename gt lt nodetype gt in a node statement but found a text string instead Precede a hexidecimal number with Ox GDIO 0 mynode normal xxxxx Error 0138 Line Yod Node s uses incorrect heron id 0x x Bits 0 3 must be slot 1 2 3 or 4 The parser has
49. _VXW_ It is very important to set these variables to the correct values This depends on your platform OS and compiler If you build for a WIN32 platform with a 32 bit Microsoft Visual C C compiler then WIN32 CCSTUDIO CMDLINE must all exist and be 1 while _VXW_ must not be defined or be 0 if it is defined If you omit one or more there will be a mismatch between the Server Loader library and the network common class If you build for a WIN32 platform with a 32 bit Borland C C compiler then WIN32 and CMDLINE must all exist and be 1 while CCSTUDIO and _VXW_ must not be defined Also do not include the ccif h include file For VxWorks CMDLINE and _VXW_ must be defined and be 1 while WIN32 and CCSTUDIO must not be defined Also do not include the ccif h include file For all other platforms including RTOS 32 and LINUX platform with the 32 bit GNU compiler then CMDLINE must exist and be 1 while WIN32 CCSTUDIO and _VXW_ must not be defined Also do not include the ccif h include file Linking with Legacy Libraries With a 32 bit Microsoft Visual C C compiler you should link with the win32s1 1lib library To run your application make sure that the win32s1 d11 file is located in the system directory of your operating system Windows 95 98 c windows system and in Windows NT W2K c winnt system32 SDK install should have done this for you With a 32 bit Borland C C compiler you should link with the win32b1 1ib libr
50. a EER EREE ANE E OR Ra Re 18 THE SERVER HANDLING STANDARD J O ssescsesecsssscscccceceessosoccoccsesssssooceseese 19 GENERAL DESCRIPTION arer aA a E aE EL E A ATEA A A 19 SERVER LOADER RUN TIME LIBRARIES EEN 19 Phe Stand ated Der de ee 19 The Stand alone Library for normal ode 20 CONCURRENCY ISSUES HEPC9 ott 21 SERVER LOADER LIBRARY FONCTION 21 The Input Output FUNCHONS siiin eaa oin a a a a a aA 22 Server Loader Specific Fwngeiione 24 Remarks Concerning fread and fwrite cccccccccccccccecscsceesseseeteseceecusecesesaeeseeeseeeseeeseeeseesseeeseeneeeaeenas 24 SERVER LOADER PLUG IN CODE COMPOSER STUDIO sccssssssrees 25 WHAT IS THE SERVER LOADER PLUG IN EE 25 PLUG IN PARAMETERS aoa cures ovatuvevntauverecoccuvestedveeeUscusenvodvon tevesneures dues teva sheutuelenigedesunertes deueesdesnnverty 25 THE BOOTLOADER FUNCTION ccscssssssssrorccccccscsssssscscccccscssssssssscsccsscsscsses 27 WHAT IS THE BOOTLOADER FUNCTION AND HOW DO I USE IT assseeessessseesreereresssrsrsrerrssresrsrserrrees 27 3 HUNT ENGINEERING Server Loader USER MANUAL DSP BIOS AND BOOTLOADER 6 ei ccscveesvecsncevssicvsncdusstceduecevsss0eccdsvsiatenessesdeventeedurtesveccesdeessersestdseheedesteese 27 USING THE HETFLASH ccccssccsssccssssccneccssscesneccssscvsnsccsseecnecessseecnaccssseecnacessceecacessseecsaceesseecnacessseens 28 PREPARING A SERVER LOADER PROGRAM FOR HETFLASH ssssnsnnssnnssensseosseosreessesoeseesseessee
51. a request to the Server Loader to stop serving the processor node The function has one parameter The DSP program will continue to run after the srv_exit call if parameter EXIT_SERVER is used If the parameter is any other value the DSP will loop forever within srv_exit after having told the Server Loader to stop serving the processor node Example srv_exit EXIT_SERVER a 67 will be executed but srv_exit 0 a 67 will never reach here Note that you cannot use any stdio functions any more after a stv_exit call 61 HUNT ENGINEERING Server Loader USER MANUAL Example Programs C6x Examples Accompanying the Server Loader libraries and Server Loader utility are a number of example directories found on the HUNT ENGINEERING CD in the cd software examples server_loader_examples directory The examples in the c6x sub directory work unchanged with a HEPC9 board For other boards e g HEPC8 you might need to make a few changes most notably in the network file s The examples in the c4x sub directory work unchanged with a HEPC3 board For other C4x boards e g HEPC2E you might need to make a few changes most notably in the network file s At the time of writing the following examples are supplied Stdtest Contains the example program stdio c which demonstrates the use of host I O with the Server Loader This example can be run with a single node 2heron Contains an example p
52. an error when reading the out file while booting a C4x module There was a problem reading or processing the relocation symbols from the C4x out file Error 3326 Function mem_write returned FALSE while reading COFF file s There was an error when reading the out file while booting a C4x module The Server Loader was unable to send data over the comports to the C4x node Error 3327 Relocation entry rules violated in COFF file s There was an error when reading the out file while booting a C4x module There was a problem reading or processing the relocation symbols from the C4x out file Error 3328 COFF file s s endiannes conflicts with target There was an error when reading the out file while booting a C4x module All HUNT ENGINEERING TIM 40 modules are little endian but the out file you try to load is for big endian or the out file has been corrupted Error 3329 Unknown load error while reading COFF file s There was an error when reading the out file while booting a C4x module Something went wrong but it s unclear what Possibly the C4x out file is corrupted Error 3340 Cannot open file os Unable to open the C4x out file specified Error 3341 Out of memory creating C4x object Out of memory when trying to create an object for loading the C4x out file The function used was the new operation Error 3400 Target_node is NULL Internal error An internal pointer points to NULL whereas it shoul
53. boards it was found that the master board has no inter board connector module defined Error 2178 Can t find switch setting of board s Internal error When trying to configure board control HSB between boards it was not possible to retrieve the red switch setting of the master board Please contact support and send your network file Error 2179 Board s is not of type API When trying to configure board control HSB between boards it was found that the slave board is not of type BD APP Only boards of type BD APY can be defined as master and slave boards Error 2180 Board s is not an HEPC9 When trying to configure board control HSB between boards it was found that the slave board is not of type BD API Only boards of type BD APY can be defined as master and slave boards Error 2181 Board us has no IBC Inter Board Module When trying to configure board control HSB between boards it was found that the slave board has no inter board connector module defined Error 2182 Can t find switch setting of board s 168 HUNT ENGINEERING Server Loader USER MANUAL Internal error When trying to configure board control HSB between boards it was not possible to retrieve the red switch setting of the slave board Please contact support and send your network file Error 2183 Don t know how to program IBC on slave board od An EMIC EM1 or an unknown inter board connector module was used to connect mast
54. can be identified with a node id nodeid In your network file the very first node definition will define a node with index 0 the second node definition will define a node with id 1 and so on Examples of node definitions are C6 FPGA EM2 GDIO and PCIF But note that this is not a full list and in future more node types may be added The board is identified with a board id bdid In your network file the very first BD declaration will define a board with id 0 the second BD declaration will define a board with id 1 and so on Don t confuse the board id with the red switch Upon error the function returns a value of 2 or higher Otherwise it will return 0 and bdid will be set to the board via which HSB for node nodeid can be accessed Example BD API hep9a 3 0 BD API hep9a 4 0 remote c6 D MODa ROOT 1 0x02 module2 out fpga 1 io2v2 normal 0x14 rbtfile rbt em2 0 em2a normal 0x06 em2 1 em2b normal 0x16 BDCONN EM2a 0 EM2b 0 With the above network file definitions GetNodeHsbAccessId 0 amp i will return 0 and i will be set to 0 because HSB for node MODa can be accessed via board 0 hep9a 3 GetNodeHsbAccessId 1 amp i will return 0 and i will be set to 0 because HSB for node io2v2 can be accessed via board 0 hep9a 3 GetNodeHsbAccessId 4 amp i will return an error because there s no node with id 4 De there s no fifth
55. class will remain supported for some time to support existing applications The ccif class can only be used on Win32 platforms with a Microsoft Visual C C compiler It implements an interface with Code Composer Studio so that the g option can be used just like with the standard Server Loader The only thing you need to do is include the header file ccif h there is no additional library you need to link with The basic functions defined are Finds amp starts CC Studio void RunFree on all proc s network net Matches HERON to CCS id int StartCodeComposer yy bey i network net Load symbols set bpt PS E int RunFree void MatchHeronId2CCid int PrepareDebugging int OnHitBreakpoint void StartDebugging char spath network net Event handler network net Zeie Aal ee ee Sa The ccif class is not a class you can use at will Basically you must use it as it is used in the example program supplied on the HUNT ENGINEERING CD cd examples server _loader_examples c6x examples mysl and sl _ api This is because the functions supplied are very specific to the way the standard Server Loader works This specific way is explained below First we try to find and start up Code Composer Studio Start CodeComposer function Once this succeeds the DSP system will be under Code Composer Studio control via the JTAG In the Server Loader we use the node class to represent each node in the network This node is not nec
56. devices you happen to have open the Server Loader will then use handles you provide instead of trying to open a device If a device is not listed the Server Loader will open the device itself Parameter n is the number of open devices handles that you have listed in the array that uDevice points at Return value loader will return 0 upon success and return 2 or higher upon error Use get lasterr of the hesl class for a description of the error int hesl parse network file char networkfile 1 89 HUNT ENGINEERING Server Loader USER MANUAL Functions such as loader serverloader and heartconf do their own parsing and there would not appear to be any reason to have a separate parse network file function However it may sometimes be useful to just test if a network file parses correctly Also once a network file is parsed you can use the information functions to retrieve board or node information without there being a need to reset load or configure HEART as you may have to when using the loader serverloader or heartconf functions Include include hesl h Parameters networkfile is a pointer to a character string that represents the path and name of the network file Return value parse_network_ file will return 0 upon success and return 2 or higher upon error Use get lasterr of the hes class for a description of the error int hesl server void The server fu
57. follows struct server function parameters unsigned char buf int blks int elts int Fd char bdname 128 int bdno int fifo Ke typedef server _function_parameters SRVFIEPARAMS The last three parameters will indicate what server thread the request came from board type bdname board number bdno and fifo Parameter Fd will tell you the file handle Fd 0 for stdin Fd 1 for stdout and Fd 2 for stderr All other file handles are processed by the Server and you cannot redirect or replace this The buf parameter points to a string buffer and blks x elts the size These are the parameters as used by fwrite and fread The other functions use the same parameters although the parameter naming will not indicate the intended use gt You may wonder why there s no printf entry A printf is actually executed by fwrite but with an Fd parameter being 1 stdout We will now discuss each function s parameters relating to the SRVFIEPARAMS structure 44 HUNT ENGINEERING Server Loader USER MANUAL fclose USER_SRV_FCLOSE This function only uses the Fd parameter for the filehandle Example unsigned long myfclose const SRVFIEPARAMS p return fclose p gt Fd fread USER SRV FREAD This function uses the first 4 parameters as its naming suggests Example unsigned long myfread const SRVFIEPARAMS p d fwrite USER SRV FWRITE return fread p
58. gt in a HEART statement but found a text string or found an invalid value for the UMI value use only values 0 to OxF HEART nodea 0 nodeb 0 2 umi Oxff Error 0440 Line od Expected broadcast name in BDCAST statement od The parser reached the end of file after processing BDCAST in a BDCAST statement A broadcast name was expected BDCAST AN Error 0441 Line d Expected node name in BDCAST statement d The parser reached the end of file after processing BDCAST lt broadcast gt in a BDCAST statement A node name was expected BDCAST bbc N Error 0442 Line d BDCAST statement od uses invalid heron id or node s The parser successfully parses the node name in a BDCAST statement but finds that this node is not defined earlier in the network file BDCAST bbc xxxx Error 0443 Line d BDCAST statement od uses non HERON node s The parser successfully parses the node name in a BDCAST statement and finds that this node is defined earlier in the network file but the node is not a HERON node BDCAST bbc c4x Error 0444 Line d Expected fifo number in BDCAST statement od The parser reached the end of file after processing BDCAST lt broadcast gt lt nodename gt in a BDCAST statement A fifo number was expected BDCAST bbc nodea AN Error 0445 Line od BDCAST statement d uses invalid fifo number 138 HUNT ENGINEERING Server Loader USER MANUAL The parser exp
59. gt lt nodetype gt lt ccid gt in a node statement but found a text string instead ND 0 mynode normal 0 xxxxx Error 0051 Line od Expected Local Bus Control Word in ND or C4 statement The parser reached the end of file after processing ND lt n gt lt nodename gt lt type gt lt ccid gt lt gbcw gt in a node statement A global bus control word was expected ND 0 mynode normal 0 00000000 Error 0052 Line od s invalid Local Bus Control Word for node s The parser expected to find a Lobal Bus Control Word a hexidecimal number after parsing ND lt n gt lt nodename gt lt nodetype gt lt ccid gt lt gbcw gt in a node statement but found a text string instead ND 0 mynode normal 0 00000000 xxxxx Error 0053 Line d Expected IACK address in ND or C4 statement The parser reached the end of file after processing ND lt n gt lt nodename gt lt type gt lt ccid gt lt gbcw gt lt Ibew gt in a node statement An IACK address was expected ND 0 mynode normal 0 00000000 00000000 AN Error 0054 Line od s invalid ACK address for node s The parser expected to find an IACK address a hexidecimal number after parsing ND lt n gt lt nodename gt lt nodetype gt lt ccid gt lt gbcw gt in a node statement but 110 HUNT ENGINEERING Server Loader USER MANUAL found a text string instead ND 0 mynode normal 0 00000000 00000000 xxxxx Error 0055
60. have created one or more threads that implement API code Function server in the hesl class does just that The server function will complete if all server threads complete A server thread completes if the processor node that it serves executes the srv_exit function So all processor nodes that are served by the Server Loader would need to execute srv_exit and only then the serve function of the hes class running on the host PC would complete Depending on your application your API thread or threads may still want or need to continue running even when the server function has completed Extracting board information from the network file The above will all work fine but in the API code we still need to hard code board name board number and fifo Wouldn t it be nice if we could get such information from the network file and achieve some level of device independence The hesl class offers a number of functions that allow you to extract certain types of network file information For this example we just want to extract board name and number Assuming we have just one board we could use char bstr 1024 int boardno int device r sl GetBoardName 0 bstr if r is not 0 process error r sl GetBoardSw 0 amp boardno if r is not 0 process error r sl GetBoardFifo 0 amp device if r is not 0 process error 59 HUNT ENGINEERING Server Load
61. implemented as a macto reads a line from the stdin stream writes a single character to the stdout stream implemented as a macto writes a single character to the stdout stream implemented as a macro wtites a string to the stdout stream writes a character to a file buffer leaves the file positioned before the character Direct Input Output Functions fread fwrite reads a specified number of items from the file wtites a specified number of items to a file File Positioning Functions fseek ftell rewind places the file pointer at a specified character offset relative to the beginning the end of the file or the current location g 8 gt returns the current character offset from the beginning of the file places the current location to the beginning of the file implemented as a macro Error Handling Functions feof tests for the end of file indicators HUNT ENGINEERING Server Loader USER MANUAL ferror returns a non zero integer if an error occurs during read or write operations perror writes the most recent error encountered to the stderr stream Server Loader Specific Functions The previous section has outlined the functions available in the run time libraries for performing I O operations In addition to the I O functions available there are three other functions that are provided for communicating with the environment and handling network loading requirements Communication with the Envi
62. in future more node types may be added If the node identified by nodeid is a valid node 0 is returned and bdid is set to the board index of the board that the node is on If not and upon error a value of 2 or higher is returned Note that GetNodeBoardlId is identical to GetNodeBoardSw but that the board the node is on is identified with id in GetBoardNodelId but with dev and bdsw in GetNodeBoardSw Example BD API hep9a 0 3 BD API hep9a 2 4 c6 0 MODa ROOT 1 0x01 modulel out c6 0 MODa ROOT 1 0x02 module2 out c6 1 MODa ROOT 1 0x21 module3 out With the above network file definitions GetNodeBoardId 0 amp bdid will return 0 and bdid will be set to 0 GetNodeBoardId 1 amp bdid will return 0 and bdid will be set to 0 GetNodeBoardId 2 amp bdid will return 0 and bdid will be set to 1 And GetNodeBoardId 3 amp bdid will return an error because there s no fourth node definition Include Hinclude hesl h 74 HUNT ENGINEERING Server Loader USER MANUAL Return value Get NodeBoardId will return a value of 0 if the node identified by node index nodeid is defined in the network file dig is then set to the board index of the board the node is on The function will return a value of 2 or higher if nodeid is an invalid node id and upon error int hes1 GetNodeBoardSw int nodeid char dev int bdsw i Get NodeBoardSw is an information
63. int nodeid 80 HUNT ENGINEERING Server Loader USER MANUAL int modtype E GetNodeModType is an information function After a function such as loader heart conf serverloader or parse network file has been executed you can use this function to extract certain information from the network file GetNodeModType will tell you what is the module type of the node with node index nodeid The module type is an integer number A list of module types is defined in hesl h they are the definitions starting with MOD_ Note that more module types may be added in future versions of the Server Loader Nodes can be identified with a node id nodeid In your network file the very first node definition will define a node with index 0 the second node definition will define a node with id 1 and so on Examples of node definitions are C6 FPGA EM2 GDIO and PCIF But note that this is not a full list and in future more node types may be added If the node identified by nodeid is a valid node 0 is returned and modt ype is set to the module type for that node If nodeid does not identify a valid node and upon error a value of 2 or higher is returned Example c6 0 MODa ROOT 1 0x02 module2 out fpga 0 io2v2 normal 0x04 rbtfile rbt em2 0 ibe normal 0x06 With the above network file definitions GetNodeModType 0 amp t will return 0 and t w
64. is a maximum number of nodes that can be processed This error is returned when in your network file you define more nodes than the software can process maximum of 256 nodes Error 0161 Line d Expected board number in EM1C EM1 EM2 statement The parser reached the end of file after processing EMx x 2 1 1c in a node statement A board number referring to a BD statement was expected EM2 AN Error 0162 Line d Node od uses invalid board number s The parser expected to find a board number after parsing EMx x 2 1 1c in a node statement but found a text string instead A valid board number is a digit that indicates what board statement the node is on The number must refer to a BD statement e g a board number 0 refers to the first BD statement in the network 118 HUNT ENGINEERING Server Loader USER MANUAL file a board number 1 refers to the second BD statement in the network file and so on EM2 x Error 0163 Line d Expected node name in EM1C EM1 EM2 statement The parser reached the end of file after processing EMx lt n gt x 2 1 1c in a node statement A node name was expected EM2 0 N Error 0164 Line d Expected node type in EM1C EM1 EM2 statement The parser reached the end of file after processing EMx lt n gt lt nodename gt x 2 1 1c in a node statement A node type ROOT or NORMAL was expected EM2 0 mynode AN E
65. module defined for that slot 0 is returned Upon error a value of 2 or higher is returned Nodes can be identified with a node id nodeid In your network file the very first node definition will define a node with index 0 the second node definition will define a node with id 1 and so on Examples of node definitions are C6 FPGA EM2 GDIO and PCIF But note that this is not a full list and in future more node types may be added Example BD API hep9a 3 0 BD API hep9a 5 0 c6 0 MODa ROOT 1 0x02 module2 out fpga 1 io2v2 normal 0x04 rbtfile rbt em2 0 ibe normal 0x06 With the above network file definitions GetNodeId hep9a 3 1 amp nid will return 1 because there s no module defined for slot 1 on board hep9a 3 But GetNodeId hep9a 3 2 amp nid will return 0 and nid will be set to 0 node MODa GetNodeId hep9a 5 4 amp t will return 0 and nid will be set to 1 node io2v2 But GetNodeId hep9a 0 1 0 will return an error because fourth parameter is a NULL pointer Include include hesl h Return value GetNodeId will return a value of 0 if in the network file a node is defined for slot slot of board dev board switch bdsw and nodeid is set to the node index of the node found GetNodeId will return 1 if there s no node defined for that slot Upon error 2 or higher is returned int hesl GetNodeModType
66. network file Error 3864 You cannot use a EM1 C inter board module to connect 2 HEPC9 s x and x When trying to create IBC inter board connector connections it was found that the module to connect two boards was an EM1C However this module cannot be used to create BDLINK BDCONN connections Error 3865 EM1 module s only has 1 FIFO 0 but you use FIFO d When trying to create IBC inter board connector connections it was found that the module to connect two boards was an EM1 A fifo other than 0 is defined to be used but an EM1 module has only one connection fifo 0 FifoA Error 3866 Please select a proper type eg EM1 EM2 for IBC s When trying to create IBC inter board connector connections it was found that the module to connect two boards was not a supported type i e EM1C EM1 or EM2 178 HUNT ENGINEERING Server Loader USER MANUAL Error 3867 You cannot use a EM1 C inter board module to connect 2 HEPC9 s x and x When trying to create IBC inter board connector connections it was found that the module to connect two boards was an EM1C However this module cannot be used to create BDLINK BDCONN connections Error 3868 EM1 module s only has 1 FIFO 0 but you use FIFO d n When trying to create IBC inter board connector connections it was found that the module to connect two boards was an EM1 A fifo other than 0 is defined to be used but an EM1 module has only one connection fi
67. network files and to load and serve the network The common class implements a common error routine and verbose routine that you may redirect to a different routine For win32 systems Windows 95 98 Windows NT and Windows 2000 there is an additional interface that you can elect to use the ccif class this interfaces to Code Composer Studio when the g option is used Serverloader functions There ate 4 serverloader functions implemented by the hes class All of them offer a generic interface with the same options as offered by the Server Loader executable There are 4 varieties so that you can choose the one that is most convenient for your situation int serverloader int serverloader int serverloader int serverloader int argc char argv char options char network HE HANDLE uDevice int n int argc char argv ji HE HANDLE uDevice int n char options char network G AE a The top serverloader entry has two parameters an argc parameter that is the number of argv arguments and the argv parameter itself which is an array of character string pointers This is identical to the arguments used by main in a console program Example int main int argc char argv hesl sl int r sl serverloader argc argv The second serverloader entry allows all options to be specified in one string and the network file in another string For example int r sl serverloader rlsv network
68. node definition Include Hinclude hesl h Return value GetNodeHsbAccessId will return a value of 2 or higher upon error and 0 if no error was encountered Parameter bdid will be set to the board via which HSB for the node with node index nodeid can be accessed 78 HUNT ENGINEERING Server Loader USER MANUAL int hesl GetNodeHsbAccessS amp w int nodeid char dev int bdsw JI GetNodeHsbAccessSw is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file When using certain inter board modules such as the EM2 HSB connections may be created between multiple boards Using such inter board modules it is possible to access all of a board fifo s hsb reset via another board connected to it A board that is to be accessed via another board is specified with the remote keyword in a BD API definition This way boards that are not inserted in the PC can still be booted and accessed via another board which is inserted in a PC GetNodeHsbAccessS amp w tells you via what board HSB can be accessed to reach the node with node id nodeid If the node can be accessed directly that is via the board the node is on then dev and bdsw will identify the same board as the board that node nodeid is on If th
69. note that the c option cannot be used with the HEPC9 carrier board Debug Option g The debug option g works only if you have Code Composer Studio installed and works for C6x processors only The debug option will setup Code Composer Studio for use with 17 HUNT ENGINEERING Server Loader USER MANUAL the Server Loader Code Composer Studio will be started up and then the Server Loader will prepare everything for a debug session load all processors with debug symbols and it will run each C6x program until the first C code line after boot loader It works for any number of C6x processors but you must have prepared Code Composer Studio to work with exactly that number of processors using Code Composer Studio Setup Code Composer Studio ID Matching x In the example network files you will see entries for the Code Composer Studio ID in the node declarations Usually Code Composer Studio will use different IDs for the nodes than the Server Loader does With HERON systems the Server Loader can find out what nodes have what Code Composer Studio IDs But on non HERON systems it cannot The Code Composer Studio IDs are to be used on non HERON systems or in cases where the automatic matching of HERON ID with Code Composer Studio ID failed Code Composer Studio IDs are related to the JTAG the last processor in the queue has ID 0 the one closest to the host interface the highest ID equal to the number of processors in the
70. of 2 or higher is returned Example c6 0 MODa ROOT 1 0x02 module2 out fpga 0 io2v2 normal 0x04 rbtfile rbt em2 0 ibe normal 0x06 With the above network file definitions GetNodeFile 0 amp fname will return 0 and module2 out will be written to fname GetNodeFile 1 amp fname will return 0 and tbtfile rbt will be written to fname GetNodeFile 2 amp fname will return 0 and will be written to fname And GetNodeFile 3 amp fname will return an error because there s no fourth node definition Include include hesl h 76 HUNT ENGINEERING Server Loader USER MANUAL Return value GetNodeFile will return a value of 0 if the node identified by node index nodeid is defined in the network file fname is then set to the filename defined for that node The function will return a value of 2 or higher if nodeid is an invalid node id and upon error int hesl GetNodeHeronId int nodeid int heronid IR GetNodeHerontd is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file GetNodeHeronId will tell you what heron id is defined for the node with node index nodeid Nodes can be identified with a node id nodeid In your network file the very first node definition will define a nod
71. or EM1 Error 1520 BDCAST statement od uses module ox on an undefined board with switch x The heron ID used in a BDCAST statement doesn t match any of the defined boards red switch setting Bits 7 4 of the heron ID indicate the red switch of the board that the module is inserted in Error 1521 LISTEN statement od uses module Dias on an undefined board with switch x The heron ID used in a LISTEN statement doesn t match any of the defined boards red switch setting Bits 7 4 of the heron ID indicate the red switch of the board that the module is inserted in Error 1522 HEART statement od uses module x on an undefined board with switch x Error 1523 HEART statement od uses module x on an undefined board with switch x The heron ID used in a HEART statement doesn t match any of the defined boards red switch setting Bits 7 4 of the heron ID indicate the red switch of the board that the module is inserted in Error 1530 There s no node with index d maximum d FindIBCLink error A node has an index that isn t in the list of nodes the index is smaller than 0 or higher than the number of nodes defined in the network file Error 1531 Internal error Node d of d nodes is NULL Internal error A node with a valid index in the list of nodes points to nothing Please contact support and send your network file Error 1540 Parameter fnode is NULL in FindIBCConnect Internal error A node with a val
72. process Include include hesl h Parameters options is a pointer to a character string that holds Server Loader options for example rlv for a full list of options please refer to Invoking the command line Server Loader on page 14 option s will be ignored by this function though Parameter network is a pointer to a character string that represents the path and name of the network file Return value loader will return 0 upon success and return 2 or higher upon error Use get lasterr of the hesl class for a description of the error int hes1 loader HE HANDLE uDevice int n int argc char argv i The loader function will reset boot configure HEART and start but not serve a system of C6x FPGA and other types of nodes as per the network file that it is asked to process 88 HUNT ENGINEERING Server Loader USER MANUAL Include Hinclude hesl h Parameters argv is an array of pointers to character strings and argc is the number of entries in the argv array Each character string should represent a Server Loader option for example r for reset for a full list of options please refer to Invoking the command line Server Loader on page 14 option s will be ignored by this function though One character string would represent the path and name of the network file Parameter uDevice is a pointer to an array of open device handles You don t need t
73. root Out ND 0 NODE2 NORMAL 1 1E4A4000 1E4A4000 002ff800 idrom out nodl out ND 0 NODE3 NORMAL 0 1E4A4000 1EF78000 002ff800 idrom out nod2 out This example assumes a HET40S in slot 1 a HET40 in slot 2 and a HET40SD in slot 3 You have to decide where in what slot you want to insert the HETFLASH It can be placed anywhere as long as there is a comport connection between any C4x processor and the HETFLASH In the case of the example above slot 4 would be a good location to put the HETFLASH The ROOT processor in this case now becomes the processor in slot 3 as a boot stream originating from the HETFLASH boots this processor first Therefore you must change your network file to identify the proper ROOT processor Node type ccid GBCR LBCR lack program s ND 0 NODEO NORMAL 2 1EF78000 1EF78000 002ff800 idrom out root Out ND 0 NODE2 NORMAL 1 1E4A4000 1E4A4000 002ff800 idrom out nodl out ND 0 NODE3 ROOT 0 1E4A4000 1EF78000 002ff800 idrom out nod2 out Please keep in mind that there must be exactly one ROOT processor Finally you must tell the Server Loader to create a flash rom file and then to upload this flash rom file onto the HETPLASH Changing the BD line into a FLASH line will do this For example if the network file declares BD API hepc4 0 0 then this should be changed to FLASH API hepc4 0 0 All in all preparing a Server Loader application for HETFLASH programming involves changing the network file of your applicat
74. text string instead HEART nodea 0 nodeb xxxx Error 0411 Line d HEART statement d in network file uses invalid fifo number od The parser successfully found and parsed a fifo number after processing HEART lt nodename gt lt fifo gt lt nodename gt lt fifo gt in a HEART statement but the fifo number is not a valid fifo number It must be a number from 0 to 5 HEART nodea 0 nodeb 7 Error 0412 Line d Expected timeslot in HEART statement d The parser reached the end of file after processing HEART lt nodename gt lt fifo gt lt nodename gt lt fifo gt in a HEART statement A timeslot was expected HEART nodea 0 nodeb 0 AN Error 0413 Line od HEART statement od uses invalid time slot value s The parser expected to find a timeslot after processing HEART lt nodename gt lt fifo gt lt nodename gt lt fifo gt in a HEART statement but found a text string or found an invalid value for the timeslot must be 0 to 5 HEART nodea 0 nodeb 0 7 Error 0414 Line d Expected timeslot value after v in HEART statement od The parser reached the end of file after processing HEART lt nodename gt lt fifo gt lt nodename gt lt fifo gt lt v gt in a HEART statement A timeslot was expected HEART nodea 0 nodeb 0 v AN Error 0415 Line od HEART statement d uses invalid time slot value s The parser expected to find a timeslot after processing HEART lt nodename gt
75. that is not a valid node type i e the type string is not ROOT and is not NORMAL ND 0 mynode xxxx Error 0046 Line d Expected Global Bus Control Word in ND or C4 statement The parser reached the end of file after processing ND lt n gt lt nodename gt lt type gt in a node statement A global bus control word was expected ND 0 mynode normal AN 109 HUNT ENGINEERING Server Loader USER MANUAL Error 0047 Line d Missing Di after Code Composer node id s for node s The parser detects a missing closing bracket after a Code Composer Studio id in a node statement after parsing ND lt n gt lt nodename gt lt type gt ccid ND 0 mynode normal x Error 0048 Line od Invalid Code Composer node id s for node Ys The parser expected to find a Code Composer Studio id after parsing ND lt n gt lt nodename gt lt nodetype gt in a node statement but found a text string instead ND 0 mynode normal x Error 0049 Line d Expected Global Bus Control Word in ND or C4 statement The parser reached the end of file after processing ND lt n gt lt nodename gt lt type gt lt ccid gt in a node statement A global bus control word was expected ND 0 mynode normal 0 Error 0050 Line od s invalid Global Bus Control Word for node s The parser expected to find a Global Bus Control Word a hexidecimal number after parsing ND lt n gt lt nodename
76. the Server Loader This means that these classes all have a common error print verbose print and debug print functions The basic functions defined here are void vprint char mess void eprint char mess void dprint char mess The vprint function will only print if some level of verbose is defined The dprint function will only print if debug is defined for that class The eprint is the standard error print function Currently all 3 functions are implemented as printf functions Legacy Class Common Interface parameters The common class is now a legacy interface and will be obsoleted in future Please use the hes class as described in earlier sections in this Chapter for new projects The common class will remain supported for some time to support existing applications A few parameters can be defined in the common class void SetVerbose int 1 void SetDebug void SetInfoLevel int a 50 HUNT ENGINEERING Server Loader USER MANUAL The Set Verbose function sets the verbose level for a certain class SetDebug is only used when debugging SetInfoLevel is used with the c option of the Server Loader Relating to the network class the functions you might use are SetInfoLevel and SetVerbose Legacy Class Ccif Interface basics The ccif class is now a legacy interface and will be obsoleted in future Please use the hes class as described in earlier sections in this Chapter for new projects The ccif
77. though there s no third board defined i e no error value is returned Include include hesl h Return value IsBoardRemote will return a value of 1 if the board specified by bdi is defined as remote in the network file It returns 0 in all other cases even if the bdid identifies an invalid node int hesl heartconf int argc char argv 1 The heartconf function will configure HEART and optionally reset a system as per the network file that it is asked to process Include include hesl h Parameters argv is an array of pointers to character strings and argc is the number of entries in the argv array Each character string should represent a HeartConf option r reset v verbose z no zap or b0 1 2 3 for an explanation of these options please refer to Invoking the command line Server Loadet on page 14 One character string would represent the path and name of the network file Return value heart conf will return 0 upon success and return 2 or higher upon error Use getlasterr of the hesl class for a description of the error int hesl heartconf char options char network 1 The heartconf function will configure HEART and optionally reset a system as per the network file that it is asked to process Include include hesl h Parameters options is a pointer to a character string that holds a combination of possible Heart on
78. to HeartConf it was found that an unknown option was used fVZ A Error 8089 Parsing Options s or s Confusion in name of network file When parsing options passed to HeartConf it was found that the network file was specified two times or more Note that all arguments without in front are interpreted as network filenames Error 8090 Parsing Options No network file specified When parsing options passed to HeartConf no network file was found Arguments that don t start with 7 in front are interpreted as network files Error 8095 Parsing Options Too many handles max od The array of open devices passed to a Server Loader or HeartConf library function is larger than the software can handle The maximum number of open handles that you can supply in the parameter array is 96 Error 8501 Cannot find bootloader breakpoint Are you sure this is a Server Loader 190 HUNT ENGINEERING Server Loader USER MANUAL application The Server Loader plugin or the Server Loader executing with the g option successfully booted the system but now cannot find the call to bootloader in one of the node s executable code The project from which the node s executable code out file has been built was perhaps not created for the Server Loader or the call to pootloader is missing Error 8510 Halt Exception s The Server Loader plugin or the Server Loader executing with the g option
79. value after processing BOOTLINK lt nodename gt lt fifo gt lt nodename gt lt fifo gt lt umi gt in a BOOTLINK BOOTPATH statement but found a text string or found an invalid value for the UMI value use only values 0 to Us BOOTLINK mynode 0 othernode 0 umi Oxff Error 0310 Line d Expected node name in BOOTSLOT statement The parser reached the end of file after processing BOOTSLOT in a BOOTSLOT statement A node name was expected BOOTSLOT AN Error 0311 Line d BOOTSLOT statement uses undefined node s The parser successfully parses the node name in a BOOTSLOT statement but finds 127 HUNT ENGINEERING Server Loader USER MANUAL that this node is not defined earlier in the network file BOOTSLOT xxxx Error 0312 Line Yd BOOTSLOT statement uses non C6x PPC node s The parser successfully parses the node name in a BOOTSLOT statement and this node is defined earlier in the network file but the node is not a C6x or a PPC node Nodes defined in BOOTSLOT statements must be C6x or PPC nodes because a BOOTSLOT statement tells the software via what timeslot FIFO 0 the node is to be booted ND 0 mynode normal 0 00000000 00000000 002ff800 idrom out app out BOOTSLOT mynode Error 0313 Line d BOOTSLOT statement uses non processor node s The parser successfully parses the node name in a BOOTSLOT statement and this node is defined earlier in the network file but the node is not a proce
80. x The parser expected to find a timeslot after processing BDCAST lt broadcast gt lt nodename gt lt fifo gt lt v gt in a BDCAST statement but found a text string or found an invalid value for the timeslot must be 0 to 0x3F BDCAST bbc nodea 0 v 255 nw Error 0451 Line d Expected timeslot value after t in BDCAST statement d The parser reached the end of file after processing BDCAST lt broadcast gt lt nodename gt lt fifo gt lt t gt in a BDCAST statement A timeslot was expected BDCAST bbc nodea 0 t AN Error 0452 Line od BDCAST statement d in network file uses invalid time slot value x The parser expected to find a timeslot after processing BDCAST lt broadcast gt lt nodename gt lt fifo gt lt t gt in a BDCAST statement but found a text string or 139 HUNT ENGINEERING Server Loader USER MANUAL found an invalid value for the timeslot use only values 0 to 5 BDCAST bbc nodea 0 t 1 7 N Error 0453 Line d Expected umi value in BDCAST statement Dad The parser reached the end of file after processing BDCAST lt broadcast gt lt nodename gt lt fifo gt lt umi gt in a BDCAST statement A UMI value was expected BDCAST bbc nodea 0 umi AN Error 0454 Line od BDCAST statement d in network file uses invalid umi value s The parser expected to find a UMI value after processing BDCAST lt broadcast gt lt nodename gt lt fifo gt lt umi gt
81. 0x06 em2 1 em2b normal 0x16 BDCONN EM2a 0 EM2b 0 72 HUNT ENGINEERING Server Loader USER MANUAL With the above network file definitions GetBoardRstAccessSw 0 dev amp bs will return 0 hep9a will be written to dev and bs will be set to 0 because the reset device on hep9a 0 can be accessed via the same board hep9a 0 GetBoardRstAccessSw 1 dev amp bs will return 0 hep9a will be written to dev and bs will be set to 0 because reset on hep9a 1 can be accessed via board hep9a 0 i e board 0 GetBoardRstAccessSw 2 dev amp bs will return an error because there s no board with id 2 i e there s no third BD definition Include include hesl h Return value Get BoardRstbAccessSw will return a value of 2 or higher upon error and 0 if no error was encountered Parameters dev and bdsw will be set to the board via which reset on board bdid can be accessed int hes1l GetBoardSw int bdid int bdsw i GetBoardSw is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file GetBoardSw will tell you what the red board switch is of a board with board index bdid Boards can be identified with a board id bdid In your network file the very first B
82. 1 em2b normal 0x16 BDCONN EM2a 0 EM2b 0 With the above network file definitions GetBoardRstAccessId 0 amp i will 71 HUNT ENGINEERING Server Loader USER MANUAL return 0 and i will be set to 0 because reset on hep9a 0 can be accessed via the same board hep9a 0 GetBoardRstAccessId 1 amp i will return 0 and i will be set to 0 because reset on hep9a 1 can be accessed via board hep9a 0 ie board 0 GetBoardRstAccessId 2 amp i will return an error because there s no board with id 2 i e there s no third BD definition Include include hesl h Return value GetBoardRstAccessId will return a value of 2 or higher upon error and 0 if no error was encountered Parameter id will be set to the board via which reset on board bdid can be accessed int hesl GetBoardRstAccessSw int bdid char dev int bdsw E GetBoardRstAccessSw is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file When using certain inter board modules such as the EM2 reset connections may be created between multiple boards Using such inter board modules it is possible to access all of a board fifo s hsb reset via another board connected to it A board that is to be accessed via another board is speci
83. 1708 No board with id d root d found There is no board in the list of defined boards with index specified first parameter of GetBoardName The index must be between 0 and the number of boards defined in the network file minus one Error 1709 The board with id d is not a BD API type board The GetBoardName function can only be used for boards of the BD APT type Error 1710 Parameter sw is NULL in GetBoardSw The second parameter supplied to GetBoardSw is a NULL pointer Error 1711 No board with id d found Error 1712 Cannot find ROOT node on board with id od Error 1713 No board with id d root d found There is no board in the list of defined boards with index specified first parameter of GetBoardSw The index must be between 0 and the number of boards defined in the network file minus one Error 1714 The board with id d is not a BD API type board The GetBoardName function can only be used for boards of the BD APT type Error 1715 Parameter fifo is NULL in GetBoardFifo The second parameter supplied to GetBoardFifo is a NULL pointer Error 1716 No board with id d found Error 1717 Cannot find ROOT node on board with id od Error 1718 No board with id d root d found There is no board in the list of defined boards with index specified first parameter of GetBoardFifo The index must be between 0 and the number of boards defined in the network file minus one Error 1720 Parameter
84. 2 In the mysl sl_api batch and sl_api exe examples in addition you also have to create a new project and build the PC application When done you can run the example using the my32 bat batch files But you probably have to check within these batch files that the path to the exe file you created is correct 62 HUNT ENGINEERING Server Loader USER MANUAL C4x Examples Accompanying the Server Loader libraries and Server Loader utility are a number of example directories found on the HUNT ENGINEERING CD in the cd examples server loader _examples c4x directory These default to using a HEPC3 HEPC4 HECPCI1 board For other boards you might need to make a few changes most notably in the network file s At the time of writing the following examples are supplied Stdtest Contains the example program stdio c which demonstrates the use of host I O with the Server Loader This example can be run with a single node Hequad Contains an example program that shows use a HEQUAD module Ldtest Contains an example program that shows how to run a 3 processor network ldtest2 Contains an example program that shows how to run a 3 processor network It is similar to ldtest but uses 2 one directional comports rather than 1 bi directional comport as is usual to demonstrate dual comport capability sl_api Contains 2 sample directories that demonstrate how API and Server Loader can be combined successfully easily and smoothly batch U
85. 3 Tells the Server Loader to create a file that can be used by another tool to program HEART Use b0 to create a CPP file for use with Microsoft C C or Borland C C and the host API Use b1 to create a VHDL file for Spartan devices Use b2 to create a VHDL file for use with Virtex II devices Use b3 to create a C file for use with Code Composer Studio and HERON API Examples win32sl win32sl win32sl win32sl rls network Resets loads and serves a system described by network rlscv 2 network Resets loads and serves a system described by network Shows module information and detailed verbose loading information rlsg 2 network Resets loads and serves a system described by network Starts up Code Composer Studio and prepares for debugging The decoupling time is 2 seconds rlsvk network Resets loads and serves a system described by network using packets This allows booting of systems with e g a GD7 between modules with packet mode selected on the GD7 Search Directory Option i This option adds additional search paths to the Server Loader When loading programs the Server Loader will also search these paths for program files If you use eeprom62 out eeprom67 out C67 or idrom out C4x this option allows you to tell the Setver Loader to look in the hes1 1ib directory to look for those files Examples win32sl i lib rlsv network Win32 bit server search
86. 4 C6 FPGA GDIO PCIF EM2 EM1 EMIC and so on statements The first node statement in a network file defines a node with id 0 the second node statement defines a node with id 1 and so on int GetNodeCount int GetNodelId int GetNodeModType int GetNodeBoardId int GetNodeBoardSw int GetNodeName void char dev int bdsw int slot int nodeid int nodeid int modtype int nodeid int bdid int nodeid char dev int bdsw nt nodeid char nname 5 5 Hr ct int GetNodeType nt nodeid int ntype int GetNodeHeronId int nodeid int heronid int GetNodeFile int nodeid char fname int GetNodeAccessHsbId int GetNodeAccessRstId int GetNodeAccessHsbSw int GetNodeAccessRstSw int nodeid int bdid int nodeid int bdid int nodeid char dev int bdsw int nodeid char dev int bdsw Use GetNodeCount to get the number of nodes in the network file Using a node id you can extract node name like hep9a using GetNodeName extract the node type using GetNodeType normal or root extract the node s heronid using GetNodeHeron1Id and extract the filename or bit stream used in a node statement using GetBoardFile Function GetNodeBoardId will give you the board id of the board on which the node is located The alternative GetNodeBoardSw works identically but instead of a board id gives you a board s name e g hep9a and board number The GetNodeModType function tells you the
87. 426 There are reset paths from d master boards to remote board od Please use NORESET to specify what links not to use for reset Error 1427 There are d reset paths from master boards to remote board od Please use NORESET to specify what links not to use for reset Connections between inter board connector modules on different boards transport control signals reset HSB when the boards are configured as master and slave s But there may only be one control path between a master and a slave or between successive slave boards Use the NORESET and NOHSB keywords to select what inter board connection should carry the control signals For example BD API hep9a 0 0 BD API hep9a 1 0 slave BDLINK 0010 BDLINK 0111 Here there are two inter board connections between hep9a 0 0 and hep9a 0 1 You must choose which of the two is to carry the control signals To select the first BDLINK connection for the control signals use BD API hep9a 0 0 155 HUNT ENGINEERING Server Loader USER MANUAL BD API hep9a 1 0 slave BDLINK 0010 BDLINK 0111 NORESET NOHSB Error 1428 Unknown HEPC9 extension module ox Cannot continue An inter board connector module other than the currently supported EM2 EM1 or EM1 C was defined Note that if you used the legacy keyword IBC this keyword is no longer defining an inter board connector module use EM2 EM or EM1C Error 1500 HSB more than once connects to board d
88. 543 Unable to open s for writing errno 0x x Error 2544 Unable to open s for writing errno 0x x Error 2545 Unable to open s for writing errno 0x x When trying to open a file for writing with the specified name an error occurred The errno displayed at the end is the errno of the standard C library the function used is the fopen function Error 2546 Internal error PROM buffer is NULL First do net gt open Error 2547 Internal error PROM buffer is NULL First do net gt open Internal error Please contact support and send your network file Error 2600 Cannot open s device A s Error 2601 Cannot open s device B s Error 2602 Cannot open s device Yod s The HUNT ENGINEERING API software reports that an error occurred when trying to open the specified device The error code in brackets is the API error code 170 HUNT ENGINEERING Server Loader USER MANUAL Error 2603 Unknown API board s Internal error Please contact support and send your network file Error 2604 Cannot init read structure on s s Error 2605 Cannot init write structure on Y s s The HUNT ENGINEERING API software reports that an error occurred when trying to initialise an HE_IOSTATUS object HelnitIoStatus The error code in brackets is the API error code Error 2610 Invalid board address 0x x cannot open HEPC2E direct access HEPC2E boards can only have addresses 0x160 0x200 or
89. 7 HUNT ENGINEERING API VS DIRECT UO 7 VERSION 3 0 COMPARED WITH 2 7 ANDEARUER 7 VERSION ere ere gedd geval A ENTES 8 KA RE 8 ERSTEN H MERSION E H REVISION EL H VERSION DE H REVISION MANUA Don insira e E ERA EE 9 NERSTON DEE 9 VERSIONA Tl nonen e EES A e e 10 VERSION 4 EE 10 VERSION Ee EE aA 10 e NR LEE 11 Installation under Windows 95 98 Windows NT Windows 2000 11 Installation under RedHat Linux 6 1 m II Installation under VxWorks ccccccccccceceesceeeceesesceeseeeseeeseesssesecesecesecsaecsaesscecaeeeseeeseeeseenseeeseenaeenaeenes 11 Installation under RTS 37 12 Completed Installation eegen ys cveses cecal ee ege en Age eege Magee eal 12 INSTALLATION OF THE SERVER LOADER LIBRARY csscsssseeseeecseeseceseeeceaecatesecaeesecuaeeceaeeeeesesateaeeneeates 12 THE LOADER LOADING CODE uu ccccssssssscsreccccccsssssssssscccccsscssssssssssscssssssses 14 INVOKING THE COMMAND LINE SERVER LOADER s ssesssesisteetstssstststttiststsssstststtetstseststetisestsseseseerrees 14 Command Line ONtiOns sareen ces coves Ss aeons sae acetal aves oh ls Godhead ead ace naai 15 Search Directory Opn iosstecvaes secveteraesked Zeg ze eet degen er e e evades elves ees 16 Packetised Loading Option AK eessen edge tee tag evista de ee cag oan ete is AERA 17 Show Module Information Option Gel 17 Debut Opon Eeer 17 Code Composer Studio ID Matching Cl 18 Embedded HEART programming 18 THE NETWORK DESCRIPTION FILE sereget ier e are
90. 98 with 32 bit applications Windows NT and Windows 2000 the Server Loader does not provide any support for direct I O and all boards are supported via the HUNT ENGINEERING API Under Redhat Linux 6 1 amp up there is no support for direct I O and all boards are supported via the HUNT ENGINEERING API NOTE If using the API with the Server Loader it is important to ensure that the API components for your board and Host Operating system have been installed as well Version 3 0 compared with 2 7 and earlier Version 3 0 of the Server Loader added a number of new features in order to support the new HERON architecture They are The network file has a new node declaration using C6 instead of ND 7 HUNT ENGINEERING Server Loader USER MANUAL C6 entries in the network file don t use LBCW GBCW IACK The bootloader function has changed if you used HEPC6 before you need to re compile HEPC6 DSP programs to get them to work on a HEPC8 The Server Loader host library interface has changed radically Version 3 x is written in C and the network class now implements the Server Loader library interface However please note that version 3 0 has no C4x support this was introduced in version 3 1 and C4x users would still use version 2 7 or earlier Version 3 1 Version 3 1 of the Server Loader added full C4x support But as the network booting mechanism which proceeds via the bootloader calls is completely different
91. A ERS R EA ia 46 FLOW TO BUILD EE 47 LINKING WITH LIBRARIES eis Seege eege dE Seege ee hh AR 47 LEGACY CLASS NETWORK INTERFACE Basics 48 LST 49 LEGACY CLASS NETWORK INTERFACE PARAMETERS 49 EOIN PLC ivcz est tote etathd ees ergi ed Mattel be Mel va ee Meter Ne Teal e bi Meter ebe sier Toasts 50 LEGACY CLASS COMMON INTERFACE BASCH 50 LEGACY CLASS COMMON INTERFACE PARAMETERS 50 LEGACY CLASS CCIF INTERFACE BASICS sssessssseesseseesseeessseesseseossereesseeessseesseeeossereesstesseseessereesseeese 51 LEGACY CLASS CCIF INTERFACE PARAMETERS snssssssssssessseesseseesseresssteesereessereessrressstessestessereessreesse 52 Example supporting the Lg option 52 LEGACY BUILD EE 53 LINKING WITH LEGACY LIBRARIES ccccccessscecessseeecseeceeeeseeecsesaeeecseeeeceesuececseaaeeeceeeeesssueeecsesaeeseneeeees 53 Examples eebe erter cases dual Sers A A Beet ege erleedegt Neen 54 MIXING SERVER LOADER AND API APPLICATIONS sccccccssssssscsreeeeees DD CBR EEN LEE 55 BOOT NETWORK THEN RUN API APPLICATION sssssssessssessseesssseseserssssssererersssseserersesssseeoeessssesesersesse 55 BOOT NETWORK amp RUN API CODE IN ONE APPLICATION ssssesesesseseesseetereteseteessreessteesereessereesseessse 55 BOOT NETWORK SERVE NODES amp RUN API CODE AT THE SAMRBTIME 56 SERVERITHREADS EE 56 NOSERVE KEY WORD i ee ENEE ERE TRAR SEE RE TREERE SEEE Ee 57 SERVER LOADER AND A SEPARATE API APPLICATION IN DARALLEL 58 SERVER LO
92. A brdno 0 refers to BD API hep8a 2 0 brdno 1 refers to BD API hep8a 3 0 GetDevName 0 would return hep8a GetBoardNo 0 would return 2 and GetComport 0 would return 0 GetDevName 1 would return hep8a GetBoardNo 1 would return 3 and Get Comport 0 would return 0 Version 3 2 Compared to version 3 1 version 3 2 has two features added The first is the use of a new faster server protocol between the ROOT node and the host PC The Server Loader remains backward compatible with the old server protocol This means that you can still run DSP programs compiled for Server Loader 3 0 or 3 1 with Server Loader 3 2 without a re compile and a re link However the Server Loader C6 libraries are compiled to use the new server protocol and a re compile re link of previous projects will make your out file use the new server protocol 8 HUNT ENGINEERING Server Loader USER MANUAL The other difference between version 3 1 and 3 2 is that the C6 DSP libraries now always use the HERON API for any communications To ensure that the Server Loader is not tied to a particular HERON API version the Server Loader C6x libraries use pointers to HERON API functions In your projects you must then initialise these pointers to functions A file called stub c is included in the distribution that will do the initialisation for you The file is present in all the example directories The file can be used either by including it in a source file Hinclude stu
93. ADER amp API CODE IN ONE APPLICATION s ssssssnsseesseesseosseosetrseeorsttssttsstesseesresstesressresseesse 58 COMPLETION oiae ai ooh enee Seet Ae eR EE AE 61 4 HUNT ENGINEERING Server Loader USER MANUAL ENEE tee esche Eet Ae eet eeh eene ee eeh 62 RUNNING THE COX EXAMPLES ENNEN 62 IR E DININ EE 63 RUNNING THE C4X EXAMPLES nans ni eeest siana pet su aa an he nn ora ana OAE aiarar NAE On i r iE a AAE anaa S hb iNGS 63 COMPILING THE CAX EXAMPLES aasien n EE 63 COMPILING ON LINUX VXWORKS OR RO 372 63 SERVER LOADER LIBRARY FUNCTIONS e esossssesoecesossssssossossssssssosoesossssssoso 64 LIST OF RUN TIME FUNCTIONS seess EEN 96 TECHNICAL SUPPORT svisicrssisooisissoivessrareescsssssvssioecosssarsoove sisa ors sosova sios sioe va ss 105 APPENDIX A ERROR CODES cccccsssccscccccsssssvssccccecccsccssesescsccsceseescesesssccces 106 5 HUNT ENGINEERING Server Loader USER MANUAL Introduction The Server Loader software provides HUNT ENGINEERING motherboard users with a simple means to use the TI C and assembler development tools The Server Loader can be e used as a stand alone program the command line Server Loader that DSP network and then provides standard I O stdio services to the root processor e linked in with an application program which can use its functionality under program control e used as a plug in with Code Composer Studio Scope The current version of the Server Loader v4 0 support
94. ANUAL PCIF etc an internal object is created Because only so many objects can be stored in the array that the Server Loader and HeartConf software uses there is a maximum number of nodes that can be processed This error is returned when in your network file you define more nodes than the software can process maximum of 256 nodes Error 0191 Line od Expected board number in PCIF statement The parser reached the end of file after processing PCIF in a node statement A board number referring to a BD statement was expected PCIF AN Error 0192 Line d Node od uses invalid board number s The parser expected to find a board number after parsing PCIF in a node statement but found a text string instead A valid board number is a digit that indicates what board statement the node is on The number must refer to a BD statement e g a board number 0 refers to the first BD statement in the network file a board number 1 refers to the second BD statement in the network file and so on PCIF x Error 0193 Line od Expected node name in PCIF statement The parser reached the end of file after processing PCIF lt n gt in a node statement A node name was expected PCIF 0 AN Error 0194 Line od Expected node type in PCIF statement The parser reached the end of file after processing C6 lt n gt lt nodename gt in a node statement A node type ROOT
95. API error code This function HeTestInputAvailable is only supported for Windows 95 98 ME for all boards except the HEPC9 HEPC8 and HERON BASE2 Error 3609 Unable to retrieve board information x There was an error when trying to retrieve board information The error code in brackets is the API error code returned by the HUNT ENGINEERING API HeGetBoardInfo function Error 3610 Unknown API board s The BD APP board as specified uses an unknown boardtype Examples of supported boardtypes are hep8a hep9a and heb2a 176 HUNT ENGINEERING Server Loader USER MANUAL Error 3611 Cannot open HSB on board s Yox s There was an error when trying to open HSB The error description in brackets is from the HUNT ENGINEERING API HeOpen function The error code in brackets is an API error code The typical reason for this error is when another thread in your application or another program has also opened HSB on the same board Error 3612 Cannot send HSB message via board s to slot Yox x s There was an error when trying to send a message over HSB The error description in brackets is from the HUNT ENGINEERING API HeHSBSendMessage function The error code in brackets is an API error code The typical reason for this error is when Code Composer Studio is running or has run and no Debug gt RunFree has been executed on the module in the slot specified Other reasons for this error can be that the slo
96. B amp FifoADev if Status HE OK printf Open error x n Status return 0 Status HeOpen hep9a 0 FifoA S amp HSBDev if Status HE OK printf Open error x n Status return 0 39 HUNT ENGINEERING Server Loader USER MANUAL Use devices But suppose now you wish to run HeartConf And you don t want to close those devices Wi HE HANDLE hDevice 2 hDevice 0 FifoADev hDevice 1 HSBDev r sl heartconf hDevice 2 argc argv The return value for each of the 4 heartconf functions is 0 upon success Upon error a value other than 0 is returned With the getlasterr function you can retrieve a description of the error encountered by Heart ont Example int main int argc char argv i int Ky char errstr hesl sl r sl heartconf rv argv 1 if r errstr sl getlasterr if errstr errstr 0 0 printf SL reports error d n r printf errstr return r Termination There may be instances where you want to kill the Server Loader loader or the server threads One way of doing this is by closing the device handles However these are not visible to you as they are used internally to the Server Loader In that case you can use the terminate function Typically it is used in a separate thread from the Server Loader and either you have access to the hesl class instance via a pointer or
97. B The error description in brackets is reported by HUNT ENGINEERING API s HeHSBSendMessageDataEx function The error code in brackets is an API error code Error 3604 Board s Failed to end HSB message x s There was an error when trying to send data to a module over HSB The error description in brackets is from the HUNT ENGINEERING API HeHSBEndOfSendMessageEx function The error code in brackets is an API error code Error 3605 Cannot open HSB device on board s s There was an error when trying to open HSB The error description in brackets is from the HUNT ENGINEERING API HeOpen function The error code in brackets is an API error code The typical reason for this error is when another thread in your application or another program has also opened HSB on the same board Error 3606 Unknown API board s The BD APP board as specified uses an unknown boardtype Examples of supported boardtypes are hep8a hep9a and heb2a Error 3607 Cannot close HSB on board s s There was an error when trying to close HSB The error description in brackets is from the HUNT ENGINEERING API HeOpen function The error code in brackets is an API error code Error 3608 Cannot snoop board s s There was an error when trying to detect if any data was available on the fifo The error description in brackets is from the HUNT ENGINEERING API HeTestInputAvailable function The error code in brackets is an
98. BDCAST statement cannot use timeslot 5 Error 1201 HEART routing Unbroken HEART statement line d fixed This is an internal error HEART connections from one board to another board are supposed to have been broken up to one board only connections from the nodes to their inter board connectors EM1C EM1 or EM2 Please contact support and send your network file Error 1202 HEART routing Cannot place HEART statement d HeartConf has tried to fit your HEART connection but found that the timeslot s to be used have already been taken by a different connection HEART oodea 0 nodeb 0 t 4 5 HEART nodea 1 nodec 0 t 5 In the above the nodea to nodeb connections uses timeslots 4 and 5 The HEART statement cannot use timeslot 5 Error 1203 HEART routing Cannot place BDCAST s HeartConf has tried to fit your connections but found there were not enough resoutces timeslots to place a BDCAST statement which is a connection from a node onto a HEART fifo HEART nodea 0 nodeb 0 6 BDCAST noise nodea 1 1 t 5 In the above the nodea to nodeb connections takes 6 timeslots There is no timeslot left for use with the BDCAST statement for nodea fifo 1 Error 1204 HEART routing Unbroken HEART connection line od Error 1205 HEART routing Unbroken HEART connection line od This is an internal error HEART connections from one board to another board are supposed to have been broken up to one board only connecti
99. D declaration will define a board with id 0 the second BD declaration will define a board with id 1 and so on Don t confuse the board id with the red switch If a board with board id bdid is defined in the network file O is returned and bdsw is set to the red board switch value The function will return 2 or higher if no such board is found and upon error Finally note that this function will only work with BD APT definitions in the network file References to board definitions that are BD but not BD API will result in an error being returned Example BD API hep9a 3 0 BD API hep8a 2 0 With the above network file definitions GetBoardSw 0 amp sw will return 0 and sw will be set to 3 GetBoardSw 1 amp sw will return 0 and sw will be set to 2 And GetBoardSw 2 amp sw will return an error because there s no third BD APT statement Include include hesl h Return value GetBoardSw will return a value of 0 if a board with board index bdno is defined in the network file sw is then set to that BD API definition s red board switch value In all other cases a value of 2 or higher is returned char hesl getlasterr void 73 HUNT ENGINEERING Server Loader USER MANUAL The getlasterr function will return a pointer to a string that describes the last error encountered by the Server Loader The pointer returned may possibly be NULL or a NULL
100. D hepc2ea xxxx Error 0026 Line d Unknown board type 0x x flash only supported for BD API Only FLASH API statements are supported legacy FLASH lt boardname gt statements are not supported with this version of Server Loader Error 0027 Line d Unknown board type 0x x flash only supported for BD API Only FLASHTEST API statements are supported legacy FLASHTEST lt boardname gt statements are not supported with this version of Server Loadet Error 0028 Line d Unknown board type 0x x The board type you specified after BD in a board statement is not actually supported for direct access with this version of Server Loader and HeartConf Use a BD API statement instead BD hepc8a Error 0029 Line d Unknown reset device s The parser expected a valid reset device after processing BD API lt boardname gt lt n gt lt n gt reset Valid reset devices ate a b c d C or F BD API hep3b 0 0 reset x 108 HUNT ENGINEERING Server Loader USER MANUAL Error 0040 Parsing s Too many nodes maximum is Yd For each node defined in the network file CND C6 CAT FPGA GDIO PCIF etc an internal object is created Because only so many objects can be stored in the array that the Server Loader and HeartConf software uses there is a maximum number of nodes that can be processed This error is returned when in your network fi
101. Error 0021 Line d IRQ is already defined but found a second keyword 11 The parser has already found and parsed IRQ settings in a BD API board statement but then finds another IRQ keyword 11 Only one IRQ keyword 10 11 12 or 15 was expected BD API hep2e 0 0 12 11 107 HUNT ENGINEERING Server Loader USER MANUAL Error 0022 Line d IRQ is already defined but found a second keyword 12 The parser has already found and parsed IRQ settings in a BD API board statement but then finds another IRQ keyword 12 Only one IRQ keyword 10 11 12 or 15 was expected BD API hep2e 0 0 10 12 Error 0023 Line d IRQ is already defined but found a second keyword 15 The parser has already found and parsed IRQ settings in a BD API board statement but then finds another IRQ keyword 15 Only one IRQ keyword 10 11 12 or 15 was expected BD API hep2e 0 0 12 15 Error 0024 Line d Expected API board type in BD statement The parser reached the end of file after processing BD lt boardname gt A board address e g 200 hexadecimal value was expected BD hepc2ea Error 0025 Line od Invalid address os in BD statement The parser expected to find a board address after parsing BD lt boardname gt but instead found a text string A board address e g 200 hexadecimal value was expected B
102. Error 1015 No ROOT node defined for board x A ROOT node connects to the host PC Non HEART boards such as the HEPC8 and HERON BASE2 must have exactly one ROOT node defined Only when no DSP modules are used is there no need for a ROOT module A ROOT node is the DSP module that connects via a fifo to the host and via which other nodes can be booted Error 1063 With EM1 C inter board module s you can only use FIFO 0 but you use FIFO d In one of the BDCONN BDLINK or BDPATH statements in your network file you use a FIFO other than 0 with an EM1C inter board module With an EM1C you can only use FIFO 0 EMI1C 0 em1ca normal 0x06 EMIC 1 emtcb normal 0x16 BDCONN em1ca 0 em1cb 1 Error 1063 With EM1 inter board module s you can only use FIFO 0 but you use FIFO od In one of the BDCONN BDLINK or BDPATH statements in your network file you use a FIFO other than 0 with an EM1 inter board module With an EM1 you can only use FIFO 0 EM1 0 em1a normal 0x06 EM1 1 em1b normal 0x16 BDCONN em1a 0 em1b 1 Error 1065 With EM1 C inter board module s you cannot use no blocking mode In one of the BDCONN BDLINK or BDPATH statements in your network file you use no block mode with an EM1C inter board module With an EM1C you cannot use no block mode FPGA 0 node normal 0x03 myfile out EMIC 0 emica normal 0x06 HEART node 0 emica 0 1 noblock Error 1065 With EM1 inter board module s you cannot use no blocking mode
103. Error 3530 Board s node os Unable to load node Cannot load a C4x out file C6x out file PowerPC file or bitstream onto an EM1 inter board connector module Error 3540 Board s node Y os Unable to load node Cannot load a C4x out file C6x out file PowerPC file or bitstream onto an EM2 inter board connector module Error 3550 Board s node os Unable to load node Cannot load a C4x out file C6x out file PowerPC file or bitstream onto an EM1C inter board connector module Error 3600 Error writing board s s Error when trying to send data to a board via a host fifo or comport The error description in brackets is reported by the HUNT ENGINEERING API HeWrite function The error code in brackets is an API error code 175 HUNT ENGINEERING Server Loader USER MANUAL Error 3601 Error reading board s s Error when trying to read data from a board via a host fifo or comport The error description in brackets is reported by the HUNT ENGINEERING API HeWrite function The error code in brackets is an API error code Error 3602 Board s Failed to start HSB message x s Error when trying to send data to a module over HSB The error description in brackets is reported by HUNT ENGINEERING APIs HeHSBStartSendMessageEx function The error code in brackets is an API error code Error 3603 Board s Failed to send HSB message x s Error when trying to send data to a module over HS
104. HEART is used Comment this statement out or use the optional receiver node in a host statement for example HOSTLINK mynode 0 where the host PC connects to node mynode FIFO 0 Error 0225 Line d HOSTLINK specifies invalid link number s The parser expected to find a link number in a HOSTLINK TOHOST FROMHOST statement but found a text string instead HOSTLINK xxxx or HOSTLINK mynode xxxx Error 0226 Line d HOSTLINK specifies invalid link number d The parser successfully found and parsed the link number in a HOSTLINK TOHOST FROMHOST statement but the link number is not a valid FIFO or Comport for the ROOT node or for the first or specified node C6 0 mynode root 0 0x01 myfile out HOSTLINK 8 or C6 0 mynode root 0 0x01 myfile out HOSTLINK mynode 8 For example a C6x node has 6 FIFOs so valid values are 0 1 2 3 4 and 5 Similarly C4x nodes have 6 Comports and valid values are 0 1 2 3 4 and 5 Error 0250 Line d Expected link number in FLASHLINK statement The parser reached the end of file after processing FLASHLINK A FIFO or Comport number was expected This FIFO or Comport identifies via what device the ROOT node is connected to the host PC PLASHLINK AN Error 0251 Line d FLASHLINK specifies invalid link number s The parser expected to find a link number in a FLASHLINK statement but found a text string instead FLASHLINK xxxx AN Error 0252 Line d FLAS
105. HLINK specifies invalid link number od The parser successfully found and parsed the link number in a FLASHLINK statement but the link number is not a valid FIFO or Comport for the ROOT node or for the first or specified node ND 0 mynode root 00000000 00000000 002ff800 idrom out myfile out FLASHLINK 8 124 HUNT ENGINEERING Server Loader USER MANUAL For example C4x nodes have 6 Comports and valid values are 0 1 2 3 4 and 5 Error 0280 Line d Expected node name in BOOTLINK statement The parser reached the end of file after processing BOOTLINK in a BOOTLINK statement A node name was expected BOOTLINK AN Error 0281 Line d BOOTLINK statement uses undefined node s The parser successfully parses the node name in a BOOTLINK statement but finds that this node is not defined earlier in the network file BOOTLINK xxxx Error 0282 Line d BOOTLINK statement uses non processor node s The parser successfully parses the node name in a BOOTLINK statement and this node is defined earlier in the network file but the node is not a processor node Nodes defined in BOOTLINK statements must be processor nodes because a BOOTLINK statement tells the software via what FIFOs or Comports processor nodes can be booted FPGA 0 fpganode normal 0x02 myfile out BOOTLINK fpganode Error 0283 Line d Expected link number in BOOTLINK statement The parser reached the end of file after processing BOOTLINK lt node
106. HUNT ENGINEERING laa este Chestnut Court Burton Row treme AD E Brent Knoll Somerset TA9 4BP UK Tel 44 0 1278 760188 Fax 44 0 1278 760199 Email sales hunteng co uk http www hunteng co uk http www hunt dsp com HUNT ENGINEERING SERVER LOADER TOOL for DSP Module Carriers USER MANUAL Software Version 4 13 Document Rev H J Thie 25 07 05 COPYRIGHT This documentation and the product it is supplied with are Copyright HUNT ENGINEERING 1999 All tights 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
107. In one of the BDCONN BDLINK or BDPATH statements in your network file you use no block mode with an EM1 inter board module With an EM1 you cannot use no block mode FPGA 0 node normal 0x03 myfile out EM1 Oemtla normal 0x06 HEART node 0 emia 0 1 noblock Error 1100 Parsing s HEART statement od uses slot d but slot must be in 0 5 In a HEART statement you used a node with HERON ID that encodes a slot other than 1 2 3 4 5 or 6 slot 5 identifies an inter board module slot 6 the host 147 HUNT ENGINEERING Server Loader USER MANUAL interface The error may also occur if you use HERON IDs rather than node names ina HEART statement HEART 80 20 1 Error 1101 Parsing os HEART statement d uses fifo Yod but fifo must be in 0 5 In a HEART statement you used a FIFO that is not 0 to 5 HEART nodea 0 nodeb 7 1 Error 1102 Parsing s HEART statement d uses board id od but board id In a HEART statement you used a node with a HERON ID that encodes a red board switch that is not 0 15 The error may also occur if you use HERON IDs rather than node names in a HEART statement HEART 0x1000 20 1 Error 1103 Parsing s HEART statement d uses fifo d of node 0x x which is already used The same FIFO of a node is used at least twice Each FIFO on a node can be used only once one out one in HEART nodea 0 nodeb 0 1 HEART nodea 0 nodec 0 1 Error 1104 Parsing s HEART statem
108. M1C you can only use FIFO 0 EM1 0 em1a normal 0x06 EM1 1 em1b normal 0x16 BDCONN em1a 0 em1b 1 Error 1009 Parsing s Two nodes Ys and s defined but only one can be used In your network file more than one inter board module EM2 EM1 or EMI1C is defined for a board But per board there can be only one inter board module at most EM2 0 emla normal 0x06 EM2 defined for board 0 EM2 0 em1b normal 0x06 EM2 defined for board 0 In the above example board 0 has two EM2s defined for it But carrier boards only support up to one inter board module Error 1010 Parsing s Node s can only be used with HEART carriers such as the HEPC9 In your network file you define an inter board module EM2 EM1 or EM1C for a 145 HUNT ENGINEERING Server Loader USER MANUAL carrier board that doesn t support inter board modules BD API hep8a 0 0 board 0 EM2 0 emia normal 0x06 AN In the above example board 0 is an HEPC8 and this doesn t support an inter board module such as the EM2 as in the example Error 1011 Parsing s Node s can only be used with HEART carriers such as the HEPC9 In your network file you define an inter board module EM2 EM1 or EM1C for a carrier board that doesn t support inter board modules BD API hep2e 0 0 board 0 EM2 0 emia normal 0x06 AN In the above example board 0 is an HEPC2E and this doesn t support inter board modules such as the EM2 as in t
109. N EM2a 0 EM2b 0 With the above network file definitions GetNodeHsbAccessSw 0 dev amp b will return 0 hep9a will be written to dev and b will be set to 3 because HSB for node MODa can be accessed via the first board listed which is hep9a 3 GetNodeHsbAccessSw 1 dev amp b will alsoreturn 0 hep9a will be written 79 HUNT ENGINEERING Server Loader USER MANUAL to dew and b will be set to 3 because HSB for node io2v2 can be accessed via board hep9a 3 GetNodeHsbAccessSw 4 dev amp b will return an error because there s no node with id 4 i e there s no fifth node definition Include Hinclude hesl h Return value GetNodeHsbAccessSw will return a value of 2 or higher upon error and 0 if no error was encountered Parameters dev and bdsw will be set to the board via which HSB for node nodeid can be accessed int hes1l GetNodelId char dev int bdsw int slot int nodeid i GetNodeld is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file Gert Node td will tell you what is the node index is for a module in slot slot of a board dev with switch set to bdsw If no module is defined for that slot 1 is retutned If in the network file there is a
110. NEERING Server Loader USER MANUAL was found Please contact support and send your network file Error 1768 Node od is not a valid node Internal error When searching through the list of nodes a node with an unknown node type was found Please contact support and send your network file Error 1770 Parameter nname is NULL in GetNodeName The second parameter supplied to GetNodeName is a NULL pointer Error 1771 Internal Error node d was found to be NULL nodes d Internal error When searching through the list of nodes a node pointing to NULL was found Please contact support and send your network file Error 1772 Node od is not a valid node Internal error When searching through the list of nodes a node with an unknown node type was found Please contact support and send your network file Error 1775 Parameter ntype is NULL in GetNodeType The second parameter supplied to GetNodeType is a NULL pointer Error 1776 Internal Error node od was found to be NULL nodes d Internal error When searching through the list of nodes a node pointing to NULL was found Please contact support and send your network file Error 1777 Node d is not a valid node Internal error When searching through the list of nodes a node with an unknown node type was found Please contact support and send your network file Error 1780 Parameter heronid is NULL in GetNodeHeronld The second parameter supplied to GetNodeHeronld is
111. NT ENGINEERING Server Loader USER MANUAL Error 1571 Internal error Node d of d nodes is NULL Internal error A node with a valid index in the list of nodes points to nothing Please contact support and send your network file Error 1572 There s no node with index d maximum d FindNodeConnCount error A node has an index that isn t in the list of nodes the index is smaller than 0 or higher than the number of nodes defined in the network file Error 1573 Internal error Node d of d nodes is NULL Internal error A node with a valid index in the list of nodes points to nothing Please contact support and send your network file Error 1580 Can t use fifo Yd on a HERON BASE2 board x With a HERON BASE2 board HERON modules can only use fifo 0 FifoA Error 1581 Node s uses incorrect heron id 0x x Bits 0 3 must be slot 1 or 2 With a HERON BASE2 board there are 2 possible slots The HERON ID you specified was not slot 1 or slot 2 Error 1582 Can t use fifo d for TOHOST HOSTLINK for module x With a HERON BASE2 board the host PC can only access FifoA connected to slot 1 and FifoB connected to slot 2 But in a TOHOST HOSTLINK you have specified a fifo other than FifoA 0 or FifoB 1 Error 1583 Can t use fifo d for FROMHOST HOSTLINK for module x With a HERON BASE2 board the host PC can only access FifoA connected to slot 1 and FifoB connected to slot 2 But in a FROMHOST HOSTLINK you have spe
112. PORT ND NAME PORT ee ee ee ee eee BOOTLINK NODEO 5 NODE1 2 BOOTLINK NODE1 1 NODE2 4 Heaps eeh E eeneg E Number of the link connected to the host system HOSTLINK PORT HOSTLINK 3 The things that have changed are shown in italic bold Please note that whilst the node types change from NORMAL to ROOT or vice versa the comport connections between the nodes haven t changed The HOSTLINK declaration also hasn t changed but you should be aware that it is not possible to use Server Loader stdio functions like printf fwrite fread on any of the C4x processing nodes when using the HETFLASH Programming the HETFLASH Now that we have a network fit for use with a HETFLASH it s time to program the HET FLASH module To do so power down the PC and strip the motherboard of all modules Then insert the HETFLASH in slot 1 fit the PRGEN jumper but not the BOOTEN jumper Now restart the PC After the reboot start up a DOS box and change directory to where your application is 30 HUNT ENGINEERING Server Loader USER MANUAL Now tun the Server Loader as usual but use the network file that was changed to be used for HETFLASH programming For example if your HETFLASH programming network file is called flash we could run the Server Loader as follows C hesl bin win32 win32sl Ic hesl lib rl flash This assumes that your Server Loader installation is in c hesl Please note that you should not use the s option The s opt
113. PP BDLINK BDCONN statements can only be used with boards of type BD APY Error 2101 Board s is not an HEPC9 board When processing BDLINK BDCONN connections it was found that a board used was not a HEPC9 or HECPCI9 BDLINK BDCONN statements can only be used with HEPC9 boards or HECPCI9 boards Error 2102 Board s has no IBC Inter Board Module When processing BDLINK BDCONN connections it was found that a board used did not have an inter board connector module defined Connections between boards 165 HUNT ENGINEERING Server Loader USER MANUAL can only proceed via inter board connectors such as the EM1C EM1 and EM2 and when using BDLINK BDCONN you must define an inter board connector module for each board used in the BDLINK BDCONN statements Error 2103 Can t find switch setting of board s Internal error Unable to find the red switch setting for a valid board in the array of boards defined in the network file Error 2104 Board s is not an API type board When processing BDLINK BDCONN connections it was found that a board used was not of type BD APP BDLINK BDCONN statements can only be used with boards of type BD APY Error 2105 Board s is not an HEPC9 board When processing BDLINK BDCONN connections it was found that a board used was not a HEPC9 or HECPCI9 BDLINK BDCONN statements can only be used with HEPC9 boards or HECPCI9 boards Error 2106 Board s has no IBC Inter Bo
114. RT configuration data is larger than 1024 bytes and will not fit in the BLOCK RAM You may be able to fix this by removing one or more HEART BDCAST or LISTEN statements or by splitting a network file that defines multiple board systems up into separate network files Error 2523 Too many HEART messages Cannot store all of them into VHDL RAM With Spartan devices HEART configuration data is stored in BLOCK RAM with a size of 256 bytes But the total amount of HEART configuration data is larger than 256 bytes and will not fit in the BLOCK RAM You may be able to fix this by removing one or more HEART BDCAST or LISTEN statements or by splitting a network file that defines multiple board systems up into separate network files Error 2524 Internal error PROM buffer is NULL Call net gt open first Error 2525 Internal error PROM buffer is NULL Call net gt open first Internal error Please contact support and send your network file Error 2540 PrepareProm board d is not a HEPC9 Option bx x 0 1 2 or 3 to create a HEART configuration table for PROM can only be used with network files in which only HEPC9 or HECPCI9 boards are defined Error 2541 PrepareProm board d is not API accessed Option bs x 0 1 2 or 3 to create a HEART configuration table for PROM can only be used with network files in which only boards of type BD APT are defined Error 2542 Unable to open s for writing errno 0x x Error 2
115. TFLASH to the system exactly in that slot that makes the ROOT processor in your flash network file adjacent to the HETFLASH Make sure that the PRGEN jumper is not fitted and that the BOOTEN jumper is fitted Verifying the HETFLASH After re assembling your system and adding the HETFLASH power up your PC Probably the best way to verify that the HETFLASH has properly initialised your system is to use Code Composer and view all processor nodes and check the right program is loaded and running properly If your code de activates the config line on all C4x processors then looking at the config LED on your C4x motherboard quickly tells you if the HETFLASH has booted you system or not the config LED should go off 31 HUNT ENGINEERING Server Loader USER MANUAL Troubleshooting HETFLASH The most likely causes for problems are You haven t correctly identified the ROOT processor This processor must be next to the HETFLASH The HETFLASH outputs the boot stream over comport 3 The HETFLASH jumper settings weren t correct To program the HETFLASH the BOOTEN jumper must not be fitted the PRGEN jumper must be fitted To use the HETFLASH to boot a system this reverses the BOOTEN jumper must be fitted but the PRGEN jumper must not be fitted If you leave the PRGEN jumper on while being deployed in a system please be aware that any stream of data into the HETFLASH will cause it to be re programmed With the PRGEN jumper fitted you
116. TH defines a two way duplex connection The BDLINK or BDPATH definition specifies how two boards are connected via an EM2 EM1 or EM1c module so really the fifo number identifies the channel number used on the EM module Error 0370 Line d Expected inter board module in BDCONN statement The parser reached the end of file after processing BDCONN in a BDCONN statement An inter board module name was expected BDCONN AN Error 0371 Line d BDCONN statement uses undefined node s The parser successfully parses the node name in a BDCONN statement but finds 132 HUNT ENGINEERING Server Loader USER MANUAL that this node is not defined earlier in the network file BDCONN xxxx Error 0372 Line d Node s says it s on board d but there s no such HERON carrier The parser successfully parses the node name in a BDCONN statement and finds that this node is an inter board module EM2 EM1 or EM1c But the board switch used in the inter board definition doesn t match any defined board BD API hep9a 5 0 this is board 0 BD API hep9a 2 0 this is board 1 EM2 0 em2a normal 0x16 EM2 1 em2b normal 0x36 BDCONN em2a The em2a inter board module is defined to have a board switch 0x16 suggesting a board with the red switch set to 1 But there is no HEPC9 defined with a red board switch set to 1 Error 0373 Line d BDCONWN statement uses a node s that is not an inter board module The parser su
117. The 4 byte packet was received successfully but has encoded in it a request that isn t supported Most likely the data in the packet was corrupted or perhaps the DSP executable out file used a Server Loader library of a different version that the host PC executable win32sl exe or PC library win32sl dll Error 7114 Server failed to allocate memory for incomming buffer The Server Loader tries to execute a user send request with a large buffer size It tries to allocate memory to receive the buffer data but encounters an out of memory error Error 7213 Server encountered unknown primary tag od The Server Loader while serving reads packets of 4 bytes in which a node encodes a request for example a fread or printf request After receiving a 4 byte packet the Server Loader will execute the node s request The 4 byte packet was received successfully but has encoded in it a request that isn t supported Most likely the data in the packet was corrupted or perhaps the DSP executable out file used a Server Loader library of a different version that the host PC executable win32sl exe or PC library win32sl dll Error 7214 Failed to allocate memory for incoming buffer The Server Loader tries to execute a user send request with a large buffer size It 185 HUNT ENGINEERING Server Loader USER MANUAL tries to allocate memory to receive the buffer data but encounters an out o
118. VFIEPARAMS p return fseek p gt buf p gt blks p gt elts Dell USER_SRV_FTELL This function only uses the Fd parameter for the filehandle Example unsigned long myftell const SRVFIEPARAMS p return ftell p gt Fd feof USER_SRV_FEOF This function only uses the Fd parameter for the filehandle Example unsigned long myfeof const SRVFIEPARAMS p return feof p gt Fd ferror USER_SRV_FERROR This function only uses the Fd parameter for the filehandle Example unsigned long myferror const SRVFIEPARAMS p return ferror p gt Fd Error handling For all functions the return value is 0 upon success A return value of larger than 1 means some error was encountered A return value of 1 is used to indicate failure Failure doesn t mean error for example if you ask if a board is remote replying no means the board isn t remote not that an error has occurred If an error has occurred use the getlasterr function to retrieve a descriptive string of the error The function should always return a non NULL non zero length string but to be sure you would want to verify that before attempting to display the string Version Information The hes class has the option of retrieving version information This may be helpful for detecting features or functions introduced in later versions of the Server Loader Example int major minor Char verstr NULL hesl h h vers
119. _FPGA program Please define HEAPI_DIR The Server Loader was unable to find the fpga programmer hrn_fpga exe because the environment variable HEAPI_DIR is undefined If you have just installed the API amp Tools software rebooting the PC might help Error 3201 Board s node s FPGA programming only supported when using API The fpga programmer hrn_fpga exe can only be used with boards that are defined as type BD APY Error 3220 Board s node s Unable to execute s Are you sure you have loaded the FPGA programmer VxWorks only Tried to execute the fpga programmer hrn_fpga but VxWorks has returned an error Possibly the hrn_fpga executable has not been loaded Please load hrn_fpea first then try again Error 3266 There s no hrn_fpga dll library installed Cannot run hrn_fpga When trying to load the fpga programmer library hrn_fpga dll Windows reported an error When installing the API amp Tools software you must have installed the FPGA Developet s Pack which contains the required software Error 3300 Target_node is NULL Internal error An internal pointer points to NULL whereas it should be pointing to the node to be booted Please contact support and send your network file Error 3311 Incorrect data read from IDROM packet_type Error 3312 Incorrect data read from IDROM destination Error 3313 IDROM sends packet 0x x dwords larger than p
120. a NULL pointer Error 1781 Internal Error node d was found to be NULL nodes d Internal error When searching through the list of nodes a node pointing to NULL was found Please contact support and send your network file Error 1782 Node d is not a valid node Internal error When searching through the list of nodes a node with an unknown node type was found Please contact support and send your network file Error 1785 Parameter fname is NULL in GetNodeFile The second parameter supplied to GetNodeFile is a NULL pointer Error 1786 Internal Error node od was found to be NULL nodes d Internal error When searching through the list of nodes a node pointing to NULL was found Please contact support and send your network file Error 1787 Node d is not a valid node Internal error When searching through the list of nodes a node with an unknown node type was found Please contact support and send your network file Error 1790 Parameter bdid is NULL in GetNodeHsbAccessld Error 1790 Parameter bdid is NULL in GetNodeRstAccessId 164 HUNT ENGINEERING Server Loader USER MANUAL The second parameter supplied to GetNodeHsbAccessId or GetNodeRstAccessId is a NULL pointer Error 1791 Internal Error node d was found to be NULL nodes d Internal error When searching through the list of nodes a node pointing to NULL was found Please contact support and send your network file Error 1792 Node od is n
121. acketsize 0x x The Server Loader has booted the C4x module with the IDROM reader but the data returned is not correct possibly because the data has been corrupted Note that QUAD modules have no IDROM so in the network file you should only specify the out file to be loaded not also an IDROM file idrom out Error 3320 Error reading COFF file os There was an error when reading the out file while booting a C4x module The error 172 HUNT ENGINEERING Server Loader USER MANUAL indicates that fread didn t succeed Error 3321 Wrong magic number in COFF file s Expected a C4x COFF file There was an error when reading the out file while booting a C4x module The file to be booted is not a valid C4x out file Error 3322 COFF file s is not relocatable There was an error when reading the out file while booting a C4x module The file to be booted must be a valid relocatable C4x out file Error 3323 Function load_syms returned FALSE while reading COFF file s There was an error when reading the out file while booting a C4x module There was a problem reading or processing the symbols from the C4x out file Error 3324 Cannot allocate enough memory to read COFF file os There was an error when reading the out file while booting a C4x module The Server Loader wasn t able to allocate enough memory Error 3325 Function set_reloc_amount returned FALSE while reading COFF file s There was
122. aiting for the nodes to hit a breakpoint When starting the software first it will try to do a Run Free on all nodes and boot the system according to the network file It halts the free running nodes loads the executable file symbols for each node and places a breakpoint at bootloader and makes each node tun again Debug gt Run This has all succeeded but there are problems with hitting the breakpoints Either the software times out the breakpoints are never hit ot the software was halted by the user Error 8700 Error when trying to execute GEL_Runf Yd s The Server Loader plugin or the Server Loader executing with the g option reports an error while trying to execute RunFree Debug gt Run Free for a node in the system The error code and description are attached towards the end of the error message 8700 192 HUNT ENGINEERING Server Loader USER MANUAL
123. an use this function to extract certain information from the network file When using certain inter board modules such as the EM2 HSB connections may 77 HUNT ENGINEERING Server Loader USER MANUAL be created between multiple boards Using such inter board modules it is possible to access all of a board fifo s hsb reset via a board connected to it A board that is to be accessed via another board is specified with the remote keyword in a BD API definition This way boards that are not inserted in the PC can still be booted and accessed via another board which is inserted in a PC GetNodeHsbAccessId tells you via what board HSB can be accessed to reach the node with node id nodeid If the node can be accessed directly that is via the board the node is on then id will be set to the board index of the board that the node is on If the node can be accessed only via a remote board then id will be set to the board id of the board via which HSB for node nodeid can be accessed Note that this function works like GetNodeBoardId retrieving the board index of the board that the node is on followed by GetBoardHsbAccessId which finds the board via which HSB can be accessed on the first board Note that GetNodeHsbAccesslId is identical to GetNodeHsbAccessSw but that the access board is identified with id in GetNodeHsbAccessId and with dev and bdsw in GetNodeHsbAccessSw Nodes
124. ard 0 BD API hep9a 2 0 this is board 1 BDLINK 005 AN In the above there is no board 5 Specify board 0 or board 1 only Error 0347 Line d Expected fifo number in BDLINK statement The parser reached the end of file after processing BDLINK lt bdnumber gt lt fifo gt lt bdnumber gt in a BDLINK or BDPATH statement A fifo number was expected BDLINK 001 N Error 0348 Line d BDLINK statement uses invalid fifo number s The parser expected to find a fifo number after processing BDLINK lt bdnumber gt lt fifo gt lt bdnumber gt in a BDLINK or BDPATH statement but found a text string instead BDLINK 0 0 1 xxxx Error 0349 Line d BDLINK statement uses invalid link number od The parser successfully found and parsed a fifo number after processing BDLINK lt bdnumber gt lt fifo gt lt bdnumber gt in a BDLINK or BDPATH statement but the fifo number is not a valid fifo number BDLINK 0018 The BDLINK or BDPATH definition specifies how two boards are connected via an EM2 EM1 or EM1c module so really the fifo number identifies the channel number used on the EM module 131 HUNT ENGINEERING Server Loader USER MANUAL Error 0350 Line d Fifo od on board d used at least twice in BDLINK statements The parser successfully parsed at least two BDLINK or BDPATH statements but it finds that a receiving fifo is used twice BDLINK 0 0 10 BDLINK 2 0 10 In the above fifo 0 of board 1
125. ard Module When processing BDLINK BDCONN connections it was found that a board used did not have an inter board connector module defined Connections between boards can only proceed via inter board connectors such as the EM1C EM1 and EM2 and when using BDLINK BDCONN you must define an inter board connector module for each board used in the BDLINK BDCONN statements Error 2107 Can t find switch setting of board s Internal error Unable to find the red switch setting for a valid board in the array of boards defined in the network file Error 2110 Don t know how to program IBC on slave board od An EMIC EM1 or an unknown inter board connector module was used to connect master and slave boards Only boards with an EM2 inter board connector module can be used to define master and slave boards Error 2125 Board s is not an API type board When trying to configure board control reset signal between boards it was found that the master board is not of type BD API Only boards of type BD APP can be defined as master and slave boards Error 2126 Board s is not an HEPC9 board When trying to configure board control reset signal between boards it was found that the master board is an HEPC9 or HECPCI9 Only HEPC9 or HECPCI9 boards can be defined as master and slave boards Error 2127 Board s has no IBC Inter Board Module When trying to configure board control reset signal between boards it was fo
126. ard connector module was used to connect master and slave boards Only boards with an EM2 inter board connector module can be used to define master and slave boards Error 2150 Board s is not of type API When trying to configure board control HSB between boards it was found that the master board is not of type BD API Only boards of type BD APPT can be defined as master and slave boards Error 2151 Board s is not an HEPC9 When trying to configure board control HSB between boards it was found that the master board is an HEPC9 or HECPCI9 Only HEPC9 or HECPCI9 boards can be defined as master and slave boards Error 2152 Board s has no IBC Inter Board Module When trying to configure board control HSB between boards it was found that the master board has no inter board connector module defined Error 2153 Can t find switch setting of board s Internal error When trying to configure board control HSB between boards it was not possible to retrieve the red switch setting of the master board Please contact support and send your network file Error 2154 Board s is not of type API When trying to configure board control HSB between boards it was found that the slave board is not of type BD APP Only boards of type BD API can be defined as master and slave boards Error 2155 Board s is not an HEPC9 167 HUNT ENGINEERING Server Loader USER MANUAL When trying to configure board contr
127. art host 0 first 0 1 heart first 0 host 0 1 heart host 1 first 1 1 NOSERVE heart first 2 host 1 1 NOSERVE Now we know for certain that the second bi directional fifo connection is not used by the Server Loader and thus our API program can use that connection for itself Note that it is not necessary to use fifo 0 for the Server Loader We could just as well have used node declarations pcif 0 host normal 0x05 c6 0 first root 1 0x01 modl out fifo connections heart host 0 first 0 1 NOSERVE heart first 0 host 0 1 NOSERVE heart host 1 first 1 1 heart first 1 host 1 1 The API program would now use the first bi directional fifo connection Note that if you used NOSERVE for all bi directional connections for example node declarations pcif 0 host normal 0x05 c6 0 first root 1 0x01 modl out fifo connections heart host 0 first 0 1 NOSERVE heart first 0 host 0 1 NOSERVE heart host 1 first 1 1 NOSERVE heart first 1 host 1 1 NOSERVE then the processor node first would not be served at all Also note that you may use NOSERVE for any fifo connection whether it s bi directional or not and whether a fifo connection connects to the host or not It s not going to make any difference in such cases but in a network file it may textually be clearer at your preference
128. ary To run your application make sure that the win32b1 d11 file is located in the system 53 HUNT ENGINEERING Server Loader USER MANUAL directory of your operating system Windows 95 98 c windows system and in Windows NT W2K c winnt system32 SDK install should have done this for you With LINUX you should link with 1iblinuxs1 so which should have been deposited in ust local lib by the installation script With VxWorks there s no need to link with a library if the vxwsl o has already been loaded separately onto the system If this is not the case either link with vxwsl o or vxwsllib o With RTOS 32 you should link with rtossl lib which should be in hesl lib rtos32 of your API amp Tools installation directory Examples Three worked out examples are available on the HUNT ENGINEERING CD cd examples server_loader_examples c6x examples mys1l cd examples server_loader_examples c6x examples sl_api batch cd examples server_loader_examples c6x examples sl_api exe The first example mysl is the simplest example It shows you how to create your own Server Loader using the Server Loader library The other 2 examples in sl_api show how you can combine the Server Loader with the API use the Server Loader to boot a multi processor system then use the API to communicate with it In the sl_api example there are 2 sub directories exe and batch In the batch example the DSP system is booted using the sta
129. ary into your Windows system directory There are 2 files win32sl d11 for Microsoft C C applications and win32slb1 d11 for Borland C C applications Linux Server Loader Library For LINUX systems the liblinuxsl so library needs to be installed in usr local 1lib The installme script will have done this for you VxWorks Server Loader Library In the hesl sub directory you find a VxWorks Server Loader executable in bin vxworks and the Server Loader library in lib vxworks However in the vxworks sub directory of your installation directory default c heapi there is already a vxwsl o file This file combines the Server Loader executable library and the HeartConf utility In most cases it is easier to use this combined file RTOS 32 Server Loader Library In the hesl sub directory you find an RTOS 32 Server Loader executable in bin rtos32 and the Server Loader library in lib rtos32 13 HUNT ENGINEERING Server Loader USER MANUAL The Loader Loading Code The Setver Loader is a utility to boot multiple DSP processors FPGA devices and for programming HEART The Server Loader uses a network description file to describe the network For example it will describe what DSP must be loaded with what program and how the DSP processors are connected with each other The network description file is then passed to the Server Loader as a command line argument The network description file is an ASCII file and can be written edit
130. ay the full HERON or IDROM information found ipath Search directory path for required programs eeprom62 out or eeprom67 out if the c option is used for C6x or idrom out for C4x always used k n Use packets when loading the network Default packet size is 1024 byte suitable for use with the GD7 But can be altered to any value e g k 128 This option is not supported for the HEPC9 yet Run in Double Comport Host Interface mode C4x systems only Don t match Module ID with Code Composer Studio ID This is only used on C6x HERON systems where the automatic matching of HERON IDs with the Code Composer Studio IDs doesn t work for any reason You would only use this option as a last resort trouble shooting option Skip FPGA programming If you have any FPGA nodes defined in your network file using a will tell the Server Loader to skip programming the FPGA nodes that you defined in the network file As it can take quite a while to load an FPGA node and an FPGA s contents don t disappear on reset you may want to skip programming FPGA s once they re programmed With HEPC9 boards you can choose whether to boot the network using the HERON modules boot jumpers or let the Server Loader program HEART so as to create a boot link The default is to use boot jumpers Using j means that all boot jumpers are ignored and the Server Loader will create its own boot links using HEART Also bo
131. b c or by adding it to your project In the latter case be sure to include the proper heronx h file in stub c Finally please note that versions 3 0 and 3 1 support only HERON1 modules whereas versions 3 2 and higher support any HERON module HERON1 HERON etc This is because communications now proceed via the HERON API and the actual HERON API version and type used is selected only when you link your application Version 3 3 The difference between this new version 3 3 and the previous version 3 2 is the addition of HETFLASH support for C4x systems The HETFLASH is a TIM 40 module that contains flash memory The HETFLASH is used to boot stand alone C4x systems Version 4 0 The difference between this new version 4 0 and the previous version 3 3 is the addition of HEPC9 support and support for programming FPGA or HERONIO devices HEPC9 support includes features such as HEART programming and new statements to declare non dsp nodes to be used with HEART programming Revision F manual Network file syntax split off in a separate manual The network file is used by more tools than just the Server Loader It thus merits its own manual and the network file syntax can be seen mote like a standard used by more than 1 tool currently Server Loader and HeartConf but there may be mote in the future Version 4 08 With version 4 08 a new library interface is introduced hesl h The old interface network h will b
132. bAccess6 amp w tells you via what other board HSB can be accessed for the board with board id bdid If the board s HSB can be accessed directly then dev and bdsw will identify the same board as the board with index bdid If the board is remote then dev and bdsw will identify the board via which HSB on board bdid can be accessed Note that it will write a character string to dev so parameter dev must be an character array or point to an allocated memory area Parameters The board is identified with a board id bdid In your network file the very first BD declaration will define a board with id 0 the second BD declaration will define a board with id 1 and so on Don t confuse the board id with the red switch Note that GetBoardHsbAccessS amp w is identical to Get BoardHsbAccessId but that the access board is identified with dev and bdsw in GetBoardHsb AccessS amp w but with id in GetBoardHsbAccessId Example BD API hep9a 0 0 BD API hep9a 1 0 remote em2 0 em2a normal 0x06 em 1 em2b normal 0x16 BDCONN EM2a 0 EM2b 0 With the above network file definitions GetBoardHsbAccessSw 0 dev amp bs will return 0 hep9a will be written to dev and bs will be set to 0 because the HSB device on hep9a 0 can be accessed via the same board hep9a 0 GetBoardHsbAccessSw 1 dev amp bs will return 0 hep9a will be writt
133. boards For example BDCONN em2a 0 em2b 0 BDCONN em2b 0 em2c 0 BDCONN em2c 1 em2a 1 Here you can see that HSB propagates from em2a to em2b to em2c But then HSB propagates back to em2a and this is not allowed Again use the nohsb keyword to break the HSB propagation loop Error 0333 RESET more than once connects to board d Please use NORESET in one ot more BDCONN BDLINK statements to remove the loop n Connections created between inter board modules may also create Reset propagation paths You must be careful not to create loops that is each board must at most be accessed via one Reset path For example if you define two connections between two boards Reset can reach the second board via two paths Use the NORESET keyword to select which connection will no propagate Reset BDCONN emia 0 em1b 0 BDCONN em1a 1 em1b 1 noreset Error 0334 RESET more than once connects to board d Please use NORESET in one or more BDCONN BDLINK statements to remove the loop n 129 HUNT ENGINEERING Server Loader USER MANUAL Connections created between inter board modules may also create Reset propagation paths You must be careful not to create loops that is each board must at most be accessed via one Reset path For example if you define two connections between two boards Reset can reach the second board via two paths Use the NORESET keyword to select which connection will no p
134. bsolutely sure that both instances of printf can never be called at the same time only then can you try it The same is true for all the other stdio functions It is our intention to add task and thread safe stdio functions in the future Server Loader Library Functions The runtime libraries discussed in the previous sections provide a large subset of the ANSI C standard I O functions as well as functions to handle network loading In order to keep the DSP libraries as compact as possible a subset of the ISO C stdio h functions have been implemented as functions that translate into calls to the server and a certain number of structures reside on the server itself rather than on the DSP processor like stat structures fread and fwrite buffers 21 HUNT ENGINEERING Server Loader USER MANUAL There is one main requirement placed on the use of the run time libraries in that the call to the network loading function boot loader is essential for the application to run This call must be the first operation done in main in every single executable unit Note The mechanism for passing command line arguments to the arguments of main has not been implemented in this version of the Server Loader The run time library functions are used in the same manner as a user defined function In using a library function a program needs to declare the function with its associated arguments So that the function declaration is correct it has been supp
135. by making the hesl class instance a global variable The terminate function will close all open handles and free all memory allocated by the Server Loader Parsing the network file With the serverloader loader server and heartconf functions there s no need for a separate parse network function However the hesl interface implements a number of network file information functions In some cases you may only want or need to parse the network file in order to extract some information That s when this function can be used 40 HUNT ENGINEERING Server Loader USER MANUAL Example int main int argc char argv hesl sl r sl parse_network file network If E errstr sl getlasterr if errstr errstr 0 0 printf SL reports error d n r else printf errstr Retrieving network file information Board information Board information can be retrieved using a board id This refers to a boards defined with BD API statements The first BD API defines a board with id 0 the second BD API statement defines board with id 1 and so on int GetBoardCount int GetBoardId int GetBoardName int GetBoardSw bdid int bdsw void int GetBoardFifo bdid int fifo G char dev int bdsw int bdid bdid char bdname 2 ab nt nt int int IsBoardRemote int bdid int GetBoardHsbAccessId int bdid int id int GetBoardRstAccessId int bd
136. ccessfully parses the node name in a BDCONN statement but finds that this node is not an inter board module EM2 EM1 or EM1c FPGA 0 fpganode normal 0x02 myfile out BDCONN fpganode Error 0374 Line d Expected fifo number in BDCONN statement The parser reached the end of file after processing BDCONN lt modname gt in a BDCONN statement A fifo number was expected BDCONN emnodea AN Error 0375 Line d BDCONN statement uses invalid fifo number s The parser expected to find a fifo number after processing BDCONN lt modname gt in a BDCONN statement but found a text string instead BDLINK emnodea xxxx fei Error 0376 Line d BDCONN statement uses invalid fifo number od The parser successfully found and parsed a fifo number after processing BDCONN lt nodename gt lt fifo gt in a BDCONN statement but the fifo number is not a valid fifo number It must be a number from 0 to 5 BDLINK emnodea 7 Error 0377 Line d Expected inter board module in BDCONN statement The parser reached the end of file after processing BDCONN lt nodename gt 133 HUNT ENGINEERING Server Loader USER MANUAL lt fifo gt ina BDCONN statement An inter board module name was expected BDCONN emnodea 0 AN Error 0378 Line d BDCONN statement uses undefined node s The parser successfully parses the node name in a BDCONN statement but finds that this node is not defined earlier in the network file
137. cessed directly i e bypassing the HUNT ENGINEERING API In this case instead of APT a text string identifying the board is used This functionality is legacy support for Windows 95 98 ME and should not be used for new projects Valid text strings at the time of writing are hev40 hev40m hepc2m hesb40 pcev404 hepc2ea hepc2eb hepc6a hepc8a hepc9a But note that the HEPC6 HEPC8 and HEPC9 don t actually have direct access support implemented Error 0013 Line od Expected API board type in BD statement The parser reached the end of file after processing BD API A board type such as hep8a hep9a etc was expected BD API AN Error 0014 Line d Expected board number in BD statement The parser reached the end of file after processing BD API lt boardname gt A board number red switch setting in the case of HEPC8 or HEPC9 was expected BD API hep9a Error 0015 Line d Invalid board_id s in BD statement The parser expected a board number after processing BD API lt boardname gt but 106 HUNT ENGINEERING Server Loader USER MANUAL found a text string instead BD API hep9a x Error 0016 Line od Expected device id in BD statement The parser reached the end of file after processing BD API lt boardname gt lt n gt A device id FifoA 0 FifoB 1 etc was expected BD API hep9a 0 Error 0017 Line od Invalid device_id s in BD state
138. cessor node Nodes defined in BOOTLINK statements must be processor nodes because a BOOTLINK statement tells the software via what FIFOs or Comports processor nodes can be booted FPGA 0 fpganode normal 0x02 myfile out BOOTLINK mynode 0 fpganode Error 0289 Line d Expected link number in BOOTLINK statement The parser reached the end of file after processing BOOTLINK lt nodename gt lt n gt lt nodename gt in a BOOTLINK statement A FIFO or Comport number was expected BOOTLINK mynode 0 othernode AN Error 0290 Line d BOOTLINK statement uses invalid link number s The parser expected to find a link number after processing BOOTLINK lt nodename gt lt n gt lt nodename gt in a BOOTLINK statement but found a text string instead BOOTLINK mynode 0 othernode xxxx Error 0291 Link d BOOTLINK statement uses invalid link number id The parser successfully found and parsed a FIFO or Comport number after processing BOOTLINK lt nodename gt lt n gt lt nodename gt in a BOOTLINK statement but the link number is not a valid FIFO or Comport C6 0 mynode root 0 0x1 myfile out BOOTLINK mynode 0 othernode 8 For example C6x nodes have 6 FIFOs and valid values are 0 1 2 3 4 and 5 Error 0292 Line d Link d on s used at least twice in BOOTLINK statements You have used the same FIFO or Comport two times or more in BOOTLINK statements But each FIFO or Comport can only be connected to once
139. cified a fifo other than FifoA 0 or FifoB 1 Error 1600 HEART statement od uses module s on an undefined board with switch x A node used in a HEART statement has a HERON ID that doesn t match any of the defined boards in the network file Bits 7 4 of the HERON ID indicate the red switch setting of the board that the module is on Error 1601 HEART statement od uses host fifo d but this is already used When processing HEART statements to connect nodes to the host it was found that the host fifo specified is used also by another node connected to the host Error 1602 HEART statement d uses module s on an undefined board with switch x A node used in a HEART statement has a HERON ID that doesn t match any of the defined boards in the network file Bits 7 4 of the HERON ID indicate the red switch setting of the board that the module is on Error 1603 HEART statement d uses host fifo od but this is already used When processing HEART statements to connect nodes to the host it was found that the host fifo specified is used also by another node connected to the host Error 1604 Node s is connected to 2 different host boards Cannot serve such nodes Use nosetve to not serve this node or use identical FIFO s A node is connected to two different hosts Select what host should serve the node 159 HUNT ENGINEERING Server Loader USER MANUAL by using NOSERVE with HEART statements describing the fifo conn
140. claration will define a board with id 0 the second BD declaration will define a board with id 1 and so on Don t confuse the board id with the red board switch Use Get BoardCount to find the number of boards in a network file Example BD API hep9a 0 3 BD API hep9a 2 5 With the above network file definitions GetBoardFifo 0 amp f will return 0 and f will be set to 3 fifo D GetBoardFifo 1 amp f will return 0 and f will be set to 5 fifo F GetBoardFifo 2 amp f will return an error because there s no board with id 2 i e there s no third BD definition Include include hesl h 67 HUNT ENGINEERING Server Loader USER MANUAL Return value Get BoardFifo will return a value of 2 or higher upon error and 0 if no error was encountered Paramater fifo will be set to the fifo of the board definition BD selected int hesl GetBoardHsbAccessId int bdid int id i GetBoardHsbAccess Id is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file When using certain inter board modules such as the EM2 HSB connections may be created between multiple boards Using such inter board modules it is possible to access all of a board fifo s hsb reset via a board connected to it A board tha
141. comportts it uses are all conventional bi directional comports It or boot loader 2 is required by every node in the network A call to boot loader or boot loader2 must be present at the top of main before as the first operation in main Failure to include this function will result in the application failing fclose int fclose FILE stream TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib fclose causes any buffers for the specified stream to be flushed and closes the file fclose returns non zero if the stream is not associated with an output file or if buffered data cannot be transferred to the file to be closed feof int feof FILE stream TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib feof returns non zero if an end of file is encountered on the specified stream Otherwise zero is returned ferror int ferror FILE stream TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib ferror returns non zero if an error has occurred when reading the specified stream The error indication remains until the stream is closed fflush int fflush FILE stream TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib fflush writes any buffered data to the specified stream If the stream is not associated with an output file or if the buffered data cannot be written EOF is returned fgetc int fgetc FILE stream TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib fgetc returns the nex
142. converted to decimal notation CO The unsigned int argument is converted to unsigned octal u The unsigned int argument is converted to unsigned decimal x X The unsigned int argument is converted to unsigned hexadecimal f The double argument is converted to decimal notation in the form ddd ddd e E The double argument is converted to decimal notation in the form d ddde dd g G The double argument is converted to style e or f If the exponent is less than 4 or greater than or equal to the precision then style e is used Else style f is used The int argument is converted to unsigned char The argument is taken to be a string The value of the pointer argument is printed as a hexadecimal number No output is done The number of characters that have been output is placed in the int variable which the argument points to Print a character Ste na d i fprintf returns the number of characters output or returns less than zero if an error occurred fputc int fputc int c FILE stream TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib fputc writes the character c to the specified stream It returns EOF if an error occurs fputs int fputs char str FILE stream TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib fputs copies the string str to the specified output stream It does not append the NUL character at the end of the string It does not append a newline to the output
143. ctors Use the optional NOSERVE keyword at the end of HEART statements to tell the Server Loader you that don t want such connections to be used by the Server Per C6x node that is connected to a host the Server Loader will select 1 connection to be used for serving that node This is a random choice For each node that is to be served the Server Loader creates a separate thread Example int main int argc char argv hesl sl int r r sl loader argc argv if r printf error d n r retum 0 r sl server FlagMeServerUp There are cases where you may want to use both the Server and your own API program each accessing a node via a different connection Your API program may need to know when it s safe to access the node because the HEART connections may not have been made or the server cannot handle serve requests yet as it s still busy setting up threads For such situations the FlagMeServerUp function can be asked to flag a semaphore The semaphore gets flagged when the Server Loader has completed all the work and is now ready to accept server stdio requests from all nodes it serves It can be used in conjunction with the server function or with the serverloader function used with the server option s If the server isn t used nothing breaks but the semaphore will never get flagged HeartConf functions HeartConf is a program using the same soutces library as the Server Loader
144. d Internal error The Server Loader detected that at least 1 module on a non HEART board needs to be served but the ROOT module found is on a board whose object pointer is NULL Please contact support and send the network file Error 7306 Cannot start thread for board d s too many threads The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was _beginthread and the error EGAIN Error 7307 Cannot start thread for board d s invalid argument Internal error The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was _beginthread and the error EINVAL Contact support and send your network file Error 7308 Cannot start thread for board d s unknown error Yd Internal error The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was _beginthread and the error as specified Contact support and send your network file Error 7309 Cannot start thread for board d s too many threads The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was pthread_create and the error EGAIN Error 7310 Cannot start thread for board d s invalid argument 186 HUNT ENGINEERING Server Loader USER MANUAL Internal error
145. d Please use NORESET in one ot more BDCONN BDLINK statements to remove the loop Error 1511 RESET more than once connects to board ad Please use NORESET in one ot more BDCONN BDLINK statements to remove the loop Connections between inter board connector modules on different boards transport control signals reset HSB when the boards are configured as master and slave s But there may only be one control path between a master and a slave or between successive slave boards Use the NORESET and NOHSB keywords to select what inter board connection should carry the control signals For example 156 HUNT ENGINEERING Server Loader USER MANUAL BD API hep9a 0 0 BD API hep9a 1 0 slave BD API hep9a 2 0 slave BDLINK 0 0 1 0 BDLINK 1 1 20 BDLINK 01 21 In this case both slave boards can be reached by the master board via two paths For hep9a 1 0 this can be via BDLINK 0 0 1 0 or via the other board first via BDLINK 0 1 2 1 then BDLINK 1 1 2 Um You must break the circular connections between the boards by ensuring there s only one control path to any board For example BD API hep9a 0 0 BD API hep9a 1 0 slave BD API hep9a 2 0 slave BDLINK 0 0 1 0 BDLINK 1 1 20 BDLINK 0 1 2 1 NORESET NOHSB Error 1512 BDCONN BDLINK statement cannot connect to non HEART board od You can only connect HEPC9 boards with a BDCONN BDLINK statement as only HEPC9 s can have an inter board connector module e g EM2
146. d that was meant to serve one node The function used was taskSpawn and the error as specified Contact support and send your network file Error 7323 No ROOT node found 187 HUNT ENGINEERING Server Loader USER MANUAL Internal error The Server Loader detected that at least 1 module on a non HEART board needs to be served but then cannot find the ROOT node of the board Please contact support and send the network file Error 7324 ROOT board not found searched for a board with ID d Internal error The Server Loader detected that at least 1 module on a non HEART board needs to be served but the ROOT module found is on a board whose object pointer is NULL Please contact support and send the network file Error 7325 Cannot initialise thread semaphore for board od s The Server Loadet tried to initialise a RTOS32 semaphore but encountered an error The function used was RTKCreateSemaphore Error 7326 Cannot start thread for board d s The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was RTKRTLCreateThread Error 7327 ROOT board not found searched for a board with ID d Internal error The Server Loader detected that at least 1 module on a non HEART board needs to be served but the ROOT module found is on a board whose object pointer is NULL Please contact support and send the network file Error 7328 Cannot initialise th
147. d and started with the loader or serverloader when not using the s option function earlier Include include hesl h Return value server will return 0 upon success and return 2 or higher upon error Use get lasterr of the hesl class for a description of the error void hes1 version int major int minor char verstr ie Parameters the version function will store the major version of the Server Loader into the integer pointed at by parameter major For example a Server Loader version of 4 12 will store the value of 4 into the integer pointed at by major The version function will store the minor version of the Server Loader into the integer pointed at by parameter minor For example a Server Loader version of 4 12 will store the value of 12 into the integer pointed at by minor Parameter verstr will be pointed at a version string The version string is a character string within the hesl object You must not manipulate or change the contents of this buffer For example a Server Loader version 4 12 will set verstr to point at a string 4 12 Include include hesl h Return value none 95 HUNT ENGINEERING Server Loader USER MANUAL List of Run Time Functions bootloader void bootloader void TI C4x Library stdio_xx lib amp stdr_xx lib TI Ces Library stioxxxx lib amp stdrxxxx lib boot loader handles network booting for all nodes below it in the network as long as the
148. d be pointing to the node to be booted Please contact support and send your network file 173 HUNT ENGINEERING Server Loader USER MANUAL Error 3401 Incorrect data read from IDROM packet_type Error 3402 Incorrect data read from IDROM destination Error 3403 IDROM sends packet 0x x dwords larger than packetsize 0x x The Server Loader has booted the C6x module with the IDROM reader but the data returned is not correct possibly because the data has been corrupted Error 3410 Error reading COFF file s There was an error when reading the out file while booting a Cox module The error indicates that fread didn t succeed Error 3411 Wrong magic number in COFF file s Expected a C6x COFF file There was an error when reading the out file while booting a Cox module The file to be booted is not a valid C6x out file Error 3412 COFF file s is not relocatable There was an error when reading the out file while booting a Cox module The file to be booted must be a valid relocatable C6x out file Error 3413 Function load_syms returned FALSE while reading COFF file s There was an error when reading the out file while booting a Cox module There was a problem reading or processing the symbols from the C6x out file Error 3414 Cannot allocate enough memory to read COFF file s There was an error when reading the out file while booting a Cox module The Server Loader wasn t able to allocate
149. dRemote int bdid JI IsBoardRemote is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file IsBoardRemote will tell if board with board id bdid is remote or not When using certain inter board modules such as the EM2 reset and HSB connections may be created between multiple boards Using such inter board modules it is possible to access all of a board fifo s hsb reset via another board connected to it A board that is to be accessed via another board is specified with the remote keyword in a BD API definition This way boards that are not inserted in the PC can still be booted and accessed via another board which is inserted in a PC Boards can be identified with a board id bdid In your network file the very first BD declaration will define a board with id 0 the second BD declaration will define a board with id 1 and so on Don t confuse the board id with the red switch If the board identified with bdid is remote 1 is returned else 0 is returned Example 85 HUNT ENGINEERING Server Loader USER MANUAL BD API hep9a 0 3 BD API hep9a 2 4 remote With the above network file definitions IsBoardRemote 0 will return 0 and IsBoardRemote 1 will return 1 Note that IsBoardRemote 2 will return 0 even
150. dRstAccessId can be used only with boards of type BD API Error 1726 Board d is not a valid board There is no board in the list of defined boards with index specified first parameter of GetBoardHsbAccessSw or GetBoardRstAccessSw The index must be between 0 and the number of boards defined in the network file minus one Error 1730 Parameter deel is NULL in GetBoardHsbAccessSw Error 1730 Parameter dev is NULL in GetBoardRstAccessSw The second parameter supplied to GetBoardHsbAccessSw or GetBoardRstAccessSw is a NULL pointer Error 1731 Parameter bdno is NULL in GetBoardHsbAccessSw Error 1731 Parameter bdno is NULL in GetBoardRstAccessSw The third parameter supplied to GetBoardHsbAccessSw or GetBoardRstAccessSw is a NULL pointer Error 1732 Internal Error board d found to be NULL boards d The first parameter supplied to GetBoardHsbAccessSw or GetBoardRstAccessSw is valid board index yet it is found it points to NULL Please contact support and send the network file Error 1733 Internal Error hsb master board was not a BD API board slave d Internal error Found the master board for the specified board first parameter of GetBoardHsbAccessSw or GetBoardRstAccessSw but the board is not of type BD APP Only BD APP type boards can be slave or master boards Please contact support and send the network file Error 1734 Internal Error hsb master board was found to be NULL slave d Inte
151. de hesl h Return value GetNodeRstAccessId will return a value of 2 or higher upon error and 0 if no error was encountered Parameter bdid will be set to the board via which reset for the node with node index nodeid can be accessed int hesl GetNodeRstAccessSw int nodeid char dev int bdsw i GetNodeRstAccessSw is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file When using certain inter board modules such as the EM2 HSB connections may be created between multiple boards Using such inter board modules it is possible to access all of a board fifo s hsb reset via another board connected to it A board that is to be accessed via another board is specified with the remote keyword in a BD API definition This way boards that are not inserted in the PC can still be booted and accessed via another board which is inserted in a PC GetNodeRstAccessS amp w tells you via what board reset can be accessed to reach the node with node id nodeid If the node can be accessed directly that is via the 83 HUNT ENGINEERING Server Loader USER MANUAL board the node is on then dev and bdsw will identify the same board as the board that node nodeid is on If the board is remote then dev and
152. de hesl h Return value FindNodeConn will return a value of 2 or higher upon error 1 if no fifo connection with index idx was found and 0 if a fifo connection with index idx was found If a connection was found then the fifo on the from node is returned in from_fifo and the fifo on the to node is returned in to_fifo 65 HUNT ENGINEERING Server Loader USER MANUAL int hes1 FindNodeConnCount int fromid int toid int count IR FindNodeConnCount is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file FindNodeConnCount checks whether two nodes have fifo connections and returns the number of fifo connections in parameter count Parameters The two nodes are identified with node id s Eromid and toig In your network file the very first node declaration e g C6 FPGA EM2 will define a node with id 0 the second node declaration will define a node with id 1 and so on Upon error the function returns a value of 2 or higher Otherwise it will return 0 and count will be set to the number of connections found Use FindNode Conn to find the fifo s used in a fifo connection between the two nodes The two nodes may be on different boards If there are fifo connections between
153. directives that are used to interpret the input The function tries to match each directive with the input it reads When a directive is reached that cannot be matched fscanf returns There are three types of directive white space which matches any amount of white space in the input stream a conversion specification and a character that directly matches the next input character The conversion specification begins with a character Following this a character can be optionally used to indicate the converted value is not to be stored Following this a field width integer can be supplied optionally which specifies the maximum allowable width of the input field Following this a prefix character can be optionally used to specify the type of the associated argument Finally one of the conversion specifiers shown below must be present The following specifiers are recognised d Matches a decimal integer The argument should be a pointer to int i Matches an integer with a format such as that used by the strtol function with a base value of 10 That is a string starting with Ox or OX is interpreted as a hexadecimal number a string starting with 0 is interpreted as an octal number and all others are interpreted as decimal The argument should be a pointer to int CO Matches an octal integer The argument should be a pointer to int 98 HUNT ENGINEERING Server Loader USER MANUAL u Matches a decimal i
154. directory 1ib linuxsl i hesl lib rlsv network LINUX server search directory hes1 1ib Using multiple i options more than one path may be specified 16 HUNT ENGINEERING Server Loader USER MANUAL Packetised Loading Option k Without the k option the Server Loader assumes that there are no restraints on the size of packets Each node runs bootloader routine which forwards load packets from one node to the other until the node to be booted is reached However when for example a GD7 is used in a system packets do have restraints The GD7 can be used in a mode that sends and receives data in amounts of 1024 bytes This mode allows the GD7 to check and correct data sent from one GD7 to the other GD7 The k switch tells the Server Loader to make packets of size 1024 bytes Such packets will travel without problem between GD7 connected modules Loading using the k switch will be slower than without the k switch This is because with the k option enabled packets often will have to be filled with something just to top up data to reach 1024 bytes The k switch can also be used with packet sizes other than 1024 bytes This can be defined by selecting k as follows for example for a packet size of 1024 bytes k 1024 Loading with the k option will also work without any GD7 in the system Please note that this option is not yet supported for the HEPC9 Show Module Information Option c This optio
155. dressing system and the old protocol particularly suits this On the C6x the smallest addressable unit is a byte and in general its architecture more closely resembles today s mainstream processors This allows for a simpler server protocol and functions fread and fwrite are implemented by simply executing exactly that function with parameters on the host PC 24 HUNT ENGINEERING Server Loader USER MANUAL Server Loader Plug In Code Composer Studio What is the Server Loader Plug In Code Composer Studio offers a new range of powerful features One such new feature is the possibility to add a plug in Simply said a plug in is a third party program that is embedded in in this case a Code Composer Studio menu Not only can the third party program be easily invoked via a Code Composer Studio menu it also has full access to all functions within Code Composer Studio e g the plug in can issue Run and Halt commands just as you would do yourself via the Debug menu This powerful new technology has allowed Hunt Engineering to integrate the Server Loader very tightly with Code Composer Studio One way is by using the Server Loadet s g option The other is by using the Server Loader Plug In Before Code Composer Studio using the Server Loader with Code Composer was not immediately straightforward First you would start Code Composer then load the debug symbols on all processors and then do a RunFree Next you would start the Se
156. e include hesl h Return value the number of nodes in a network file int hesl GetNodeFile int nodeid char fname GetNodeFile is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file GetNodeFile will tell you what filename is defined for the node with node index nodeid Note that it will write a character string to fname so parameter fname must be an character array or point to an allocated memory area For nodes that have no filename defined such as PCIF or GDIO the filename will be set to the empty string Nodes can be identified with a node id nodeid In your network file the very first node definition will define a node with index 0 the second node definition will define a node with id 1 and so on Examples of node definitions are C6 FPGA EM2 GDIO and PCIF But note that this is not a full list and in future more node types may be added If the node identified by nodeid is a valid node 0 is returned and fname is set to the filename of the file defined for that node If no file is defined for the node the empty string will be written to fname the return value is still 0 If nodeig does not identify a valid node and upon error a value
157. e that if the heron id as used in the network file uses a board switch of 0 but the board number uses a red switch value other then 0 then the heron id is updated to the correct value BD API hep9a 1 0 board number 0 FPGA 0 mynode normal 0x21 myfile out In the above the board number 0 next to FPGA refers to BD API hep9a 1 0 so the board number says that the node is situated on a board with the red switch 115 HUNT ENGINEERING Server Loader USER MANUAL setting set to 1 But the heron id 0x21 implies a red switch setting of 2 BD API hep9a 1 0 board number 0 FPGA 0 mynode normal 0x01 myfile out But when using heron id 0x01 the heron id is automatically updated to a heron id with the correct board switch as derived from the board number 0 So you will be fine if for the heron id you simply write the slot number In the above the software will update heron id 0x01 to the correct heron id 0x11 automatically Error 0112 Line d Node s says it s on board d but there s no such HERON carrier The board number used in a FPGA node statement does not refer to a valid board Valid boards are defined by BD statements Board number 0 refers to the first BD statement board number 1 to the second BD statement and so on BD API hep9a 1 0 board number 0 FPGA 1 mynode normal 0x11 myfile out In the above board number 1 refers to a second BD statement
158. e Server Loader When writing a TI C application the following operations must be performed to ensure correct operation 1 All modules that will be using the Server Loader either in full on the root or just for loading on the other node must ensure that the Server Loader Standard I O header file stdioc60 h for C6x nodes stdioc40 h for C4x nodes is included 2 Add a call to the function bootloader as the very first operation in main This function call is essential for the Server Loader to be able to correctly boot DSP network It must be present in all of the programs loaded into the network both the root and the normal nodes After these steps have been followed the source can be compiled and linked The resulting out can then be booted on to the network HUNT ENGINEERING API vs Direct I O The HUNT ENGINEERING API implements a standard interface to all HUNT ENGI NEERING boards and is the recommended way to communicate with boards The Server Loader supports some boards on some operating systems using direct I O as well Direct I O means bypassing the API accessing a board directly without using any drivers Support for direct I O is a legacy and will be removed in the future On the 16 bit PC platforms i e those running MSDOS Windows 3 1 Windows 95 with 16 bit applications the Server Loader supports some boards via direct I O and all boards via the HUNT ENGINEERING API On the 32 bit PC platforms i e Windows 95
159. e board is remote then dev and bdsw will identify the board via which HSB for the node nodeid can be accessed Note that GetNodeHsbAccessSw will write a character string to dev so parameter dev must be an character array or point to an allocated memory area Note that this function works like GetNodeBoardId retrieving the board index of the board that the node is on followed by GetBoardHsbAccessSw which finds the board via which HSB can be accessed on the first board Note that GetNodeHsbAccessSw is identical to GetNodeHsbAccessId but that the access board is identified with dev and bdsw in GetNodeHsb AccessSw but with id in GetNodeHsbAccessId Nodes can be identified with a node id nodeid In your network file the very first node definition will define a node with index 0 the second node definition will define a node with id 1 and so on Examples of node definitions are C6 FPGA EM2 GDIO and PCIF But note that this is not a full list and in future more node types may be added Upon error the function returns a value of 2 or higher Otherwise it will return 0 and dev and bdsw will be set to the board via which HSB for node nodeid can be accessed Example BD API hep9a 3 0 BD API hep9a 5 0 remote c6 D MODa ROOT 1 0x02 module2 out fpga 1 io2v2 normal 0x14 rbtfile rbt em2 0 em2a normal 0x06 em2 1 em2b normal 0x16 BDCON
160. e no BDCONN BDLINK connections to it A board can be a slave only if it is connected via inter board connector modules such as EM2 or EM1 but not the EM1 C to another board Access to a slave board s reset HSB and fifo s will be via a master board Error 1409 Out of memory while trying to find master slave path between boards Memory allocation failed when trying to allocate enough space to store a master slave path of boards Error 1410 Cannot find a master board to support slave board od there are no BDCONN BDLINK connections for HSB towards a master board A slave board must have a master board It is possible to have multiple slaves and one master but without a master board slave boards cannot be accessed HeartConf has not found a master board to go with the slave board indicated Error 1411 There are d HSB paths from master board od to remote board d Please use NOHSB to specify what links not to use for HSB Error 1412 There are HSB paths from d master boards to remote board od Please use NOHSB to specify what links not to use for HSB Error 1413 There are od HSB paths from master boards to remote board od Please use NOHSB to specify what links not to use for HSB Connections between inter board connector modules on different boards transport control signals reset HSB when the boards are configured as master and slave s But there may only be one control path between a master and a sla
161. e obsolete in future Also support for multiple IBC connected boards was added Revision H manual Added chapter explaining all HESL functions Version 4 10 With version 4 10 a PROM option was added This option generates a file with HEART 9 HUNT ENGINEERING Server Loader USER MANUAL configuration data that cane be used in embedded or stand alone systems Version 4 11 With version 4 11 of the Server Loader Code Composer Studio version 3 x support was added Version 4 12 With version 4 12 BDCAST LISTEN statements no longer reserve a whole ring Version 4 13 With version 4 13 support for the HERON BASE2 has been added and a new appendix error codes 10 HUNT ENGINEERING Server Loader USER MANUAL Installation Installation on PCs Installation under Windows 95 98 Windows NT Windows 2000 The setup program that installs the HUNT ENGINEERING API will also ask you if you wish to install the Software Developet s Pack SDP The Server Loader will be installed as part of this installation The SDP is installed to the HUNT ENGINEERING API directory and the Server Loader in a sub directory hes thereof Please be aware that the SDP is passworded The setup program will ask for a password If you purchased the SDP HUNT ENGINEERING will have provided you with a password The password is usually renewed per every major revision Installation under RedHat Linux 6 1 amp up On the HUNT ENGINEERING CD you w
162. e root processor with a communication protocol handled by low level routines on both sides The root processor initiates transfers as the client with the server receiving a translated call to perform an I O operation On the HEPC9 I O requests from processors other than the ROOT node can be handled provided that a duplex HEART connection exists between the host interface and the DSP A separate Windows thread will be started up for each processor that has a bi directional link with the host The Server Loader will automatically find such connections in the list of HEART definitions and automatically start a server thread for each Use the optional NOSERVE keyword at the end of a HEART definition if you don t want that host node connection the be served by the Servet Server Loader Run Time Libraries The I O resources available on the host machine are available to the root node in the DSP network Consequently there are 2 run time libraries The first library includes standard I O routines and as such is only available to the root node The second library is a reduced library and contains only routines necessary for handling network loading Non root nodes should use this second library On the HEPC9 as long as a duplex HEART connection exists between the PC interface and the DSP you can link the application for that DSP with the full library The Standard UO Library The standard I O library is available in several versions Th
163. e with index 0 the second node definition will define a node with id 1 and so on Examples of node definitions are C6 FPGA EM2 GDIO and PCIF But note that this is not a full list and in future more node types may be added If the node identified by nodeid is a valid node 0 is returned and heronid is set to the heron id defined for that node Else a value of 2 or higher is returned Example c6 0 MODa ROOT 1 0x02 module2 out fpga 0 102v2 normal 0x04 rbtfile rbt em2 0 ibe normal 0x06 With the above network file definitions GetNodeHeronId 0 amp h will return 0 and h will be set to 2 GetNodeHeronId 1 amp h will return 0 and h will be set to 4 GetNodeHeronId 2 amp h will return 0 and h will be set to 6 And GetNodeHeronId 3 amp h will return an error because there s no fourth node definition Include include hesl h Return value Get NodeHeronlId will return a value of 0 if the node identified by node index nodeid is defined in the network file heronid is then set to the heron id defined for that node The function will return a value of 2 or higher if nodeid is an invalid node id and upon error int hesl GetNodeHsbAccessId int nodeid int bdid Ne GetNodeHsbAccessId is an information function After a function such as loader heartconf serverloader or parse network file has been executed you c
164. ected to find a fifo number after processing BDCAST lt broadcast gt lt nodename gt in a BDCAST statement but found a text string instead BDCAST bbc nodea xxxx Error 0446 Line od BDCAST statement od uses invalid fifo number d The parser successfully found and parsed a fifo number after processing BDCAST lt broadcast gt lt nodename gt lt fifo gt in a BDCAST statement but the fifo number is not a valid fifo number It must be a number from 0 to 5 BDCAST bbc nodea 7 Error 0447 Line d Expected timeslot in BDCAST statement d The parser reached the end of file after processing BDCAST lt broadcast gt lt nodename gt lt fifo gt in a BDCAST statement A timeslot was expected BDCAST bbc nodea 0 Error 0448 Line d BDCAST statement d in network file uses invalid time slot value Vous The parser expected to find a timeslot after processing BDCAST lt broadcast gt lt nodename gt lt fifo gt in a BDCAST statement but found a text string or found an invalid value for the timeslot must be 0 to 5 BDCAST bbc nodea 0 7 Error 0449 Line d Expected timeslot value after v in BDCAST statement od The parser reached the end of file after processing BDCAST lt broadcast gt lt nodename gt lt fifo gt lt v gt in a BDCAST statement A timeslot was expected BDCAST bbc nodea 0 v AN Error 0450 Line od BDCAST statement d in network file uses invalid time slot value
165. ection with the host not to be served Error 1605 Node s has no in server board Error 1606 Node s has no out server board Internal error When processing HEART statements to connect nodes to the host it was found that board information for the specified node is not present Please contact support and send your network file Error 1607 Node s is connected to 2 different host FIFO s Cannot serve such nodes Use noserve to not serve this node or use identical FIFO s A node is connected to two different host fifos Select what host fifo should be used to serve the node by using NOSERVE with HEART statements describing the fifo connection which should not be used Error 1608 Node s has no in server fifo Error 1609 Node s has no out server fifo Internal error When processing HEART statements to connect nodes to the host it was found that host fifo information for the specified node is not present Please contact support and send your network file Error 1620 Cannot find board number to boardswitch d Error 1640 Cannot find board number to boardswitch d A node used in a HEART statement has a HERON ID that doesn t match any of the defined boards in the network file Bits 7 4 of the HERON ID indicate the red switch setting of the board that the module is on Error 1660 A HEART statement uses a non existing EM1C fifo od An EMIC node used in a HEART statement uses a fifo number that doesn t exist
166. ed for board d A HEART statement defines a connection between two modules on different boards but one of the boards doesn t have an inter board connector module such as EM1 or EM2 defined therefore the required connection cannot be configured 151 HUNT ENGINEERING Server Loader USER MANUAL Error 1318 You cannot use inter board module EM1 C s for board to board connections Use an EM1 or EM2 for that or define two systems connected by the EM1 C The EM1 C inter board connector module can only be used between two stand alone systems You cannot use HEART statements to connect modules on boards that are connected via EM1 C s Error 1319 Unable to route HEART connection from node s to s Error 1320 Unable to route HEART connection from slot 0x 02x to node s Error 1321 Unable to route HEART connection from node s to slot 0x 02x Error 1322 Unable to route HEART connection from slot 0x 02x to 0x 02x HeartConf cannot find a route between the two nodes trying to find a path via inter board connector modules such as the EM1 or EM2 Error 1323 BDCAST statement d uses module x on an undefined board with switch x The heron ID used in a BDCAST statement doesn t match any of the defined boards red switch setting Bits 7 4 of the heron ID indicate the red switch of the board that the module is inserted in Error 1324 BDCAST s cannot be routed to listener s HeartConf cannot find a route betwee
167. ed in future versions of the Server Loader Nodes can be identified with a node id nodeid In your network file the very first node definition will define a node with index 0 the second node definition will define a node with id 1 and so on Examples of node definitions are C6 FPGA EM2 GDIO and PCIF But note that this is not a full list and in future more node types may be added If the node identified by nodeid is a valid node 0 is returned and ntype is set to the node type for that node If nodeid does not identify a valid node and upon error a value of 2 or higher is returned Example c6 0 MODa ROOT 1 0x02 module2 out fpga 0 io2v2 normal 0x04 rbtfile rbt em2 0 ibe normal 0x06 With the above network file definitions GetNodeType 0 amp t will return 0 and CT will be set to MOD_ROOT 1 GetNodeType 1 SC will return 0 and t will be set to MOD_NORMAL 2 GetNodeType 2 amp t will return 0 and t will be set to MOD NORMAL 2 And GetNodeType 3 SC will return an error because there s no fourth node definition Include include hesl h Return value GetNodeType will return a value of 0 if the node identified by node index nodeid is defined in the network file nt ype is then set to the node type of that node The function will return a value of 2 or higher if nodeid is an invalid node id and upon error int hesl IsBoar
168. ed the end of file after processing FIFONOBLOCK lt nodename gt lt fifo gt in a FIFONOBLOCK statement An IN or OUT keyword was expected FIFONOBLOCK nodea 0 N Error 0522 Line d Expected IN or OUT in FIFONOBLOCK statement d The parser successfully found and parsed a string after processing FIFONOBLOCK lt nodename gt lt fifo gt in a FIFONOBLOCK statement but the string is not the 143 HUNT ENGINEERING Server Loader USER MANUAL expected string it must be IN or OUT FIFONOBLOCK nodea 0 xxxx Error 0530 Line d Unrecognised keyword s The parser found a keyword it doesn t recognise A keyword is one of the words used at the start of a statement such as BD API ND or C6 Error 1000 Parsing s Board d has d ROOT nodes while at most 1 is allowed n In non HEART boards C4x carrier boards HEPC8 there can be only one ROOT node The ROOT node is the node through which all other nodes get booted It is a node that is connected to the host with a direct FIFO or Comport connection Error 1001 Parsing s No ROOT nodes declared while at least one is required In non HEART boards C4x carrier boards HEPC8 there must be exactly one ROOT node The ROOT node is the node through which all other nodes get booted It is a node that is connected to the host with a direct FIFO or Comport connection Error 1002 Parsing s Node s declared for non existen
169. ed using a simple text editor In addition to being able to boot a C6x or C4x the Server Loader can also execute stdio requests from the root DSP in the system The root DSP is the processor that has a direct connection to the host PC For example the program on the root DSP can execute printf scanf and fwrite functions This section describes how to use the command line Server Loader program and how the C6x or C4x applications can interact with it In a later section it is explained how to use the Server Loader library This library allows you to incorporate Server Loader functionality into your own program Invoking the command line Server Loader Because there are different versions of the Server Loader that may be installed on the same platform e g DOS and Win32 on the same PC the Server Loader utility has different names depending on its intended use win32sl exe located in hes1 bin win32 32 bit Server Loader for use in a DOS box on Windows 95 98 Windows NT 2000 linuxsl located in hes1 src 32 bit Server Loader for use with LINUX console vxws1 part of vxwsl o in c heapi vxworks 32 bit Server Loader for use with VxWorks console rtossl located in c hesl bin rtos32 32 bit Server Loader for use with RTOS 32 console The Server Loader is invoked as follows win32sl options network for the Win32 bit server linuxs1 options network for the LINUX server vxwsl options network fo
170. en to dev and bs will be set to 0 because HSB on hep9a 1 can be accessed via board hep9a 0 GetBoardHsbAccessSw 2 dev amp bs will return an error because there s no board with id 2 i e there s no third BD definition Include include hesl h Return value Get BoardHsbAccessSw will return a value of 2 or higher upon error and 0 if no error was encountered Parameters dev and bdsw will be set to the board via which HSB on board bdid can be accessed 69 HUNT ENGINEERING Server Loader USER MANUAL int hesl GetBoardId char dev int bdsw int bdid 1 GetBoardId is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file Get BoardId will tell you what the board id is of a board specified by a board type parameter dev and the red board switch parameter bdsw Boards can be identified with a board id bdid In your network file the very first BD declaration will define a board with id 0 the second BD declaration will define a board with id 1 and so on Don t confuse the board id with the red switch Example BD API hep9a 0 3 BD API hep9a 2 4 With the above network file definitions GetBoardId hep9a 0 amp bdid will return 0 and bdid
171. en to have open HeartConf will then use handles you provide instead of trying to open a device If a device is not listed HeartConf will open the device itself Parameter n is the number of open devices handles that you have listed in the array that uDevice points at Return value heartconf will return 0 upon success and return 2 or higher upon error Use getlasterr of the hesl class for a description of the error int hesl heartconf HE HANDLE uDevice Int n Char options Char network 1 The heartconf function will configure HEART and optionally reset a system as per the network file that it is asked to process Include include hesl h Parameters options is a pointer to a character string that holds a combination of possible Heart ont options for example rv Possible Heart ont options are t reset v verbose z no zap and b0 1 2 3 For an explanation of these options please refer to Invoking the command line Server Loader on page 14 Parameter network is a pointer to a character string that represents the path and name of the network file Parameter uDevice is a pointer to an array of open device handles You don t need to open any device specifically for use by HeartConf The uDevice list allows you to tell HeartConf what devices you happen to have open HeartConf will then use handles you provide instead of trying to open a device If a device i
172. enough memory Error 3415 Function set_reloc_amount returned FALSE while reading COFF file s There was an error when reading the out file while booting a Cox module There was a problem reading or processing the relocation symbols from the C6x out file Error 3416 Function mem_write returned FALSE while reading COFF file s There was an error when reading the out file while booting a C6x module The Server Loader was unable to send data over the fifos to the C6x node Error 3417 Relocation entry rules violated in COFF file os There was an error when reading the out file while booting a Cox module There was a problem reading or processing the relocation symbols from the C6x out file Error 3418 COFF file s s endiannes conflicts with target There was an error when reading the out file while booting a C6x module All HUNT ENGINEERING C6x modules are little endian but the out file you try to load is for big endian or the out file has been corrupted Error 3419 Unknown load error while reading COFF file s Out of memory when trying to create an object for loading the C6x out file The function used was the new operation Error 3430 Cannot open find file s Unable to open the C6x out file specified Error 3431 Out of memory creating C6x object 174 HUNT ENGINEERING Server Loader USER MANUAL Out of memory when trying to create an object for loading the C6x out file The function used was the
173. ent od uses slot d but slot must be in 0 5 In a HEART statement you used a node with HERON ID that encodes a slot other than 1 2 3 4 5 or 6 slot 5 identifies an inter board module slot 6 the host interface The error may also occur if you use HERON IDs rather than node names ina HEART statement HEART 20 80 1 Error 1105 Parsing s HEART statement d uses fifo od but fifo must be in 0 5 In a HEART statement you used a FIFO that is not 0 to 5 HEART nodea 0 nodeb 7 1 Error 1106 Parsing s HEART statement od uses board id od but board id In a HEART statement you used a node with a HERON ID that encodes a red board switch that is not 0 15 The error may also occur if you use HERON IDs rather than node names in a HEART statement HEART 20 0x1000 1 AN Error 1107 Parsing s HEART statement d uses fifo Dad of node 0x x which is already used The same FIFO of a node is used at least twice Each FIFO on a node can be used 148 HUNT ENGINEERING Server Loader USER MANUAL only once one out one in HEART nodea 0 nodeb 0 1 HEART nodec 0 nodeb 0 1 Error 1200 HEART routing Cannot place BDCAST s HeartConf has tried to fit your BDCAST connection but found that the timeslot s to be used have already been taken by a different connection HEART oodea 0 nodeb 0 t 4 5 BDCAST noise nodea 1 rh In the above the nodea to nodeb connections uses timeslots 4 and 5 The
174. er Loader while serving reads packets of 4 bytes in which a node encodes a request for example an fread or printf request After receiving a 4 byte packet the Server Loader will execute the node s request This error indicates that an error occurred while trying to receive a 4 byte packet The error occurred in a call to HUNT ENGINEERING API function HeRead Error 7001 d GetMsg x Server protocol error system sends 0x x bytes but can accept only 0x x The Server Loader while serving reads packets of 4 bytes in which a node encodes a request for example an fread or printf request After receiving a 4 byte packet the Server Loader will execute the node s request The packet of 4 bytes has been successfully received but control information encoded in the packet is incorrect Typical reasons are a node sending garbage this may happen when e g a HERON2 is 183 HUNT ENGINEERING Server Loader USER MANUAL booted with HERON4 code Other causes can be a node program not calling the bootloader routine in its main function Error 7002 d GetMsg Error reading body of incoming message The Server Loader while serving reads packets of 4 bytes in which a node encodes a request for example an fread or printf request After receiving a 4 byte packet the Server Loader will read an optional additional amount of data and will then execute the node s request This error indicates that an error occ
175. er Loader tries to decode a rename request from a node but finds that the file name parameter 1 is longer than the buffer size The file name is longer than 512 bytes or the information sent in a rename request was corrupted Error 7110 Server Loader protocol error in rename The Server Loadet tries to decode a rename request from a node but finds that the file name parameter 2 is longer than the buffer size The file name is longer than 512 bytes or the information sent in a rename request was corrupted Error 7111 Server protocol error in getenv The Server Loader tries to decode a getenv request from a node but finds that the environmental variable s name is longer than the buffer size The environmental variable s name is longer than 512 bytes or the information sent in a getenv request was corrupted Error 7112 Server protocol error in system The Server Loader tries to decode a system request from a node but finds that the command string parameter 1 is longer than the buffer size The command string is longer than 512 bytes or the information sent in a system request was corrupted Error 7113 Server encountered unknown primary tag ox The Server Loader while serving reads packets of 4 bytes in which a node encodes a request for example an fread or printf request After receiving a 4 byte packet the Server Loader will execute the node s request
176. er USER MANUAL The parameter 0 in the GetBoardxxxx functions refers to the first BD API entry in the network file Here we assume we just have 1 board but if there are more BD APP entries you can retrieve the number of boards ie BD APP entries with the GetBoardCount function If an invalid board entry is given in the GetBoardxxxx functions an error will be returned return value not 0 Assuming that our API thread now uses bstr instead of a hard coded board name if we would change our network file from for example BD API hep8a 0 0 to for example BD API hep9a 0 0 then the API thread would also automatically open hep9a instead of hep8a Similarly assuming that our API thread uses boardno instead of a hard coded board number if we would change our network file from for example BD API hep9a 0 0 to for example BD API hep9a 1 0 then the API thread would also automatically open hep9a 1 instead of hep9a 0 For this to work in the API thread we would have to use something like status HeOpen bstr boardno device amp hDevice instead of hard coded parameters for example like status HeOpen hep9a 0 0 amp hDevice Using the hesl class s serverloader We could also use the hes class s serverloader function We want to run the server as well so we would need to create an API thread before executing the ser
177. er and slave boards Only boards with an EM2 inter board connector module can be used to define master and slave boards Error 2200 Cannot open s device d s The HUNT ENGINEERING API software reports that an error occurred when trying to open the specified device The error code in brackets is the API error code Error 2201 Cannot reset board s s The HUNT ENGINEERING API software reports that an error occurred when trying to reset the specified device The error code in brackets is the API error code Error 2202 Cannot close board s s The HUNT ENGINEERING API software reports that an error occurred when trying to close the specified device The error code in brackets is the API error code Error 2203 Cannot reset board s s Error 2204 Cannot reset board s s The HUNT ENGINEERING API software reports that an error occurred when trying to reset the specified device The error code in brackets is the API error code Error 2500 PrepareProm board s is not a HEPC9 Option bs x 0 1 2 or 3 to create a HEART configuration table for PROM can only be used with network files in which only HEPC9 or HECPCI9 boards are defined Error 2501 PrepareProm board s is not an API board Option bs x 0 1 2 or 3 to create a HEART configuration table for PROM can only be used with network files in which only boards of type BD APT are defined Error 2502 Cannot allocate 1024 bytes fo
178. error When trying to send run messages to DSP modules it was found that the board via which the messages were to be sent was not of type BD APP Please contact support and send your network file Error 5102 Internal error To tell DSP s to run via HSB the board specified must be HEPC9 Board specified s Internal error When trying to send run messages to DSP modules it was found that the board via which the messages were to be sent was not an HEPC9 Please contact support and send your network file Error 6000 This function should be overridden in a derived class Internal error The SetIdromName function is not implemented for one of the node types used in the network file Please contact support and send your network file Error 6001 This function should be overridden in a derived class Internal error The check_link function is not implemented for one of the node 182 HUNT ENGINEERING Server Loader USER MANUAL types used in the network file Please contact support and send your network file Error 6002 Unsupported function for module used Internal error The ResetPropagation function is not implemented for one of the node types used in the network file Please contact support and send your network file Error 6003 Unsupported function for module used Internal error The HSBPropagation function is not implemented for one of the node types used in the network file Please con
179. ese libraries are located in the lib directory With the TI compiler tools there are a number of memory models that can be used Other than the small memory model there is a m10 m11 m12 and m13 memory model used by the C6x TI compiler In the small memory model both code and data are expected to be within a 32 kbyte area If this is not the case you must use one of the m1 options The C4x TI compiler uses 4 different models with 2 parameters big and small memory model and register stack parameter passing It is important to note that linking an application with compilation units that have been 19 HUNT ENGINEERING Server Loader USER MANUAL compiled for a different memory model will result in the application failing Therefore ensure that when building each individual executable output the library that is used matches the compiler options that were used for the memory model The following table indicates which libraries correspond with which models I O Library for C62xx Memory Model stio62s lib Standard library compiled for the small memory model stio6210 lib Standard library compiled for the ml0 memory model stio6211 lib Standard library compiled for the ml1 memory model stio6212 lib Standard library compiled for the ml2 memory model stio6213 lib Standard library compiled for the ml3 memory model I O Library for C67xx Memory Model stio67s lib Standard library compiled for the small memory model stio6710 lib Standard lib
180. ess PROM button The Network Description File This file holds a precise description of the target system The Network Description File is an ASCII file and may be created with tools such as NotePad WritePad Visual C C etc on Windows and tools such as vi on LINUX For more information on the network file please refer to the separate network file syntax document Accessible via the HUNT CD front end web site or else look for networkspec pdf 18 HUNT ENGINEERING Server Loader USER MANUAL The Server Handling Standard UO The second role of the Server Loader is to provide an I O server for the root node in the network Host resources such as keyboard disc and screen are made accessible to the root node through calls to the host The I O requests from the root node are translated to a call through the host link to the host machine Once the loader module of the Server Loader has loaded the network the server module is invoked to receive and process the I O requests sent from the root node General Description Once the loader has booted the network the server is invoked to handle the requests of the client that is the requests of the root node in the network If the s option is not used with the server command then the Server Loader will terminate after the network is loaded and consequently will not be able to respond to the requests of the client A client server dialogue is set up between the server utility and th
181. essarily the same as the node objects Code Composer Studio keeps Therefore we need to identify what Code Composer Studio object corresponds with what Server Loader node class object This is done simply by having Code Composer Studio reading the HERON ID encoded at a certain address in C s memory space implemented with the MatchHeronId2Ccid function For now we re finished with Code Composer Studio and want to release JTAG control We do this by asking Code Composer Studio to RunFree the DSP system Now we can use the Server Loader functions to reset and load all processors in the network However we don t actually do a run yet ensuring that all processors are looping within the bootloader function The PrepareDebugging function is now executed This function will first load all nodes with the debug symbols Then Code Composer Studio is asked to bring the system under JTAG control again by issuing a Hal request The PrepareDebugging routine will now insert a breakpoint right at the end of the run request in the bootloader function Now Code Composer Studio is asked to run all DSP processors in the system The Server Loader will now issue the run command this is a different run from the 51 HUNT ENGINEERING Server Loader USER MANUAL Code Composer Studio run The bootloader routines will now execute towards completing the routine and the breakpoints we set earlier will be hit The breakpoint hits are handled by the OnHitB
182. etc int getc FILE stream TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib getc returns the next character from the specified stream It is implemented as a macro It returns EOF is an end of file is encountered or if a read error occurs getchar int getchar void TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib getchar is identical to getc stdin It returns the next character from the stdin stream It is implemented as a macro It returns EOF if an end of file is encountered or if a read error occuts gets char gets char s TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib gets reads a string from stdin stream to str The string read is terminated by a newline character which is replaced in str by a NUL character If an end of file is encountered or an error occurs the function returns NULL else it returns its argument perror void perror char str TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib perror prints a textual message to the stderr stream according to the value of the global vatiable errno The string argument str is first printed if it is not a null pointer and is then followed by a colon and a space The output is then appended by a message that corresponds to the value of errno printf int printf char format TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib printf writes output to the stdout stream It returns the number of characters which ha
183. f for the heron id you simply write the slot number In the above the software will update heron id 0x00 to the correct heron id 0x16 automatically Error 0170 Line d Node s says it s on board d but there s no such HERON carrier The board number used in an EMx x 2 1 1c node statement does not refer to a valid board Valid boards are defined by BD statements Board number 0 refers to the first BD statement board number 1 to the second BD statement and so on BD API hep9a 1 0 board number 0 EM2 1 mynode normal 0x16 In the above board number 1 refers to a second BD statement but there s only one board defined The board number should be 0 referring to BD API hep9a 1 0 BD API hep9a 1 0 board number 0 EM2 0 mynode normal 0x16 Error 0171 Internal error unknown node type ox There are currently 3 types of inter board modules EM2 EM1 EM1C Although these were parsed correctly when the software wants to create an object for them it finds that an inter board module other than EM2 EM1 ot EM1C is selected Somehow the variable used to hold the inter board type has been corrupted between the parsing of the EMx x 2 1 1c statement and the creation of the EMx object Error 0190 Parsing os Too many nodes maximum is d For each node defined in the network file CND C6 CAT FPGA GDIO 120 HUNT ENGINEERING Server Loader USER M
184. f memory error Error 7300 No ROOT node found Internal error The Server Loader detected that at least 1 module on a non HEART board needs to be served but then cannot find the ROOT node of the board Please contact support and send the network file Error 7301 ROOT board not found searched for a board with ID d Internal error The Server Loader detected that at least 1 module on a non HEART board needs to be served but the ROOT module found is on a board whose object pointer is NULL Please contact support and send the network file Error 7302 Cannot start thread for board d s too many threads The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was _beginthread and the error EGAIN Error 7303 Cannot start thread for board d s invalid argument Internal error The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was _beginthread and the error EINVAL Contact support and send your network file Error 7304 Cannot start thread for board d s unknown error Yd Internal error The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was _beginthread and the error as specified Contact support and send your network file Error 7305 ROOT board not found searched for a board with ID
185. fied with the remote keyword in a BD API definition This way boards that are not inserted in the PC can still be booted and accessed via another board which is inserted in a PC Get BoardRstAccess6 amp w tells you via what other board reset can be accessed for the board with board id bdid If the board s reset can be accessed directly then dev and bdsw will identify the same board as the board with index bdid If the board is remote then dev and bdsw will identify the board via which reset on board bdid can be accessed Note that it will write a character string to dev so parameter dev must be an character array or point to an allocated memory area The board is identified with a board id bdid In your network file the very first BD declaration will define a board with id 0 the second BD declaration will define a board with id 1 and so on Don t confuse the board id with the red switch Note that GetBoardRstAccessSw is identical to Get BoardRstAccessId but that the access board is identified with dev and bdsw in GetBoardHsb AccessSw but with id in GetBoardHsbAccessId Upon error the function returns a value of 2 or higher Otherwise it will return 0 and dev and bdsw will be set to the board via which reset on board bdid can be accessed Example BD API hep9a 0 0 BD API hep9a 1 0 remote em2 0 em2a normal
186. fo 0 FifoA Error 3869 Please select a proper type eg EM1 EM2 for IBC s When trying to create IBC inter board connector connections it was found that the module to connect two boards was not a supported type i e EM1C EM1 or EM2 Error 3870 Internal error Board d from is not an API HEPC9 board Internal error When trying to create IBC inter board connector connections a board was not a BD APP type or was not a HEPC9 or HECPCI9 Only HEPC9s of type BD APT can be used for inter board connectors such as EM2 or EM1 Error 3871 Internal error Board od has index higher than boards od Internal error When trying to create IBC inter board connector connections a board index was used that was larger than the number of defined boards in the network file Please contact support and send your network file Error 3880 Unable to HSB access slave board od os no master board found Internal error When trying to zap HEART on a slave board it was found that the slave board has no master board via which to access the slave board Please contact support and send your network file Error 3881 Unable to HSB access slave board od Das master board is not of type API Internal error When trying to zap HEART on a slave board it was found that the slave board has a master board via which to access the slave board that is not of type BD API Please contact support and send your network file
187. found and parsed a heron id after parsing GDIO lt n gt lt nodename gt lt nodetype gt lt heronid gt in a node statement but the heron id is not a valid number Bits 7 6 5 4 identify the board switch of the board the module in on and bits 3 2 1 0 identify the slot As valid slots for C6 nodes are 1 2 3 or 4 a heron id with bits 3 2 1 0 set to anything else is invalid GDIO 0 mynode normal 7 Error 0139 Line d Node s has HERON id 0x x ie board 0x x slot 0x x but its HERON carrier has a switch set to 0x x The heron id used in a GDIO node statement indicates that the node is situated on one board but the board number used in the same GDIO node statement indicates that the node is situated on a different board The heron id is a number made up of the board switch bits 7 6 5 4 and slot bits 3 2 1 0 The board switch encoded in the heron id should match the board switch as used in the BD API statement as indicated by the board number used in the GDIO node statement However note 117 HUNT ENGINEERING Server Loader USER MANUAL that if the heron id as used in the network file uses a board switch of 0 but the board number uses a red switch value other then 0 then the heron id is updated to the correct value BD API hep9a 1 0 board number 0 GDIO 0 mynode normal 0x21 In the above the board number 0 next to C6 refers to BD API hep9a 1 0 so the board number says that the node is situa
188. from the network file When using certain inter board modules such as the EM2 HSB connections may be created between multiple boards Using such inter board modules it is possible to access all of a board fifo s hsb reset via a board connected to it A board that is to be accessed via another board is specified with the remote keyword in a BD API definition This way boards that are not inserted in the PC can still be booted and accessed via another board which is inserted in a PC GetNodeRstAccessId tells you via what board reset can be accessed to reach the node with node id nodeid If the node can be accessed directly that is via the board the node is on then id will be set to the board index of the board that the node is on If the node can be accessed only via a remote board then id will be set to the board id of the board via which reset for node nodeid can be accessed Note that this function works like GetNodeBoardId retrieving the board index of the board that the node is on followed by GetBoardRstAccessId which finds the board via which reset can be accessed on the first board Note that GetNodeRstAccesslId is identical to GetNodeRstAccessSw but that the access board is identified with id in GetNodeRstAccessId and with dev and bdsw in GetNodeRstAccessSw 82 HUNT ENGINEERING Server Loader USER MANUAL Nodes can be identified with a node id nodeid I
189. function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file GetNodeBoardSw will tell you what the board name and red board switch value is of the board that the node is defined to be on in the network file Note that it will write a character string to dev so parameter dev must be an character array of point to an allocated memory area Nodes can be identified with a node id nodeid In your network file the very first node definition will define a node with index 0 the second node definition will define a node with id 1 and so on Examples of node definitions are C6 FPGA EM2 GDIO and PCIF But note that this is not a full list and in future more node types may be added Note that GetNodeBoardS amp w is identical to GetNodeBoardId but that the board the node is on is identified with dev and bdsw in Get NodeBoardSw but with id in GetBoardNodeld Example BD API hep9a 0 3 BD API hep9a 8 4 c6 0 MODa ROOT 1 0x01 modulel out c6 0 MODa ROOT 1 0x02 module2 out c6 1 MODa ROOT 1 0x21 module3 out With the above network file definitions GetNodeBoardSw 0 dev amp bdid will return 0 hep9a will be written to dev and parameter bdsw will be set to 0 GetNodeBoardSw 1 dev amp bdid will also retu
190. g else is invalid EM2 0 mynode normal 7 AN 119 HUNT ENGINEERING Server Loader USER MANUAL Error 0169 Line d Node s has HERON id 0x x ie board 0x x slot 0x x but its HERON carrier has a switch set to 0x x The heron id used in a EMx x 2 1 1c node statement indicates that the node is situated on one board but the board number used in the same EMx node statement indicates that the node is situated on a different board The heron id is a number made up of the board switch bits 7 6 5 4 and slot bits 3 2 1 0 The board switch encoded in the heron id should match the board switch as used in the BD API statement as indicated by the board number used in the EMx node statement However note that if the heron id as used in the network file uses a board switch of 0 but the board number uses a ted switch value other then 0 then the heron id is updated to the correct value BD API hep9a 1 0 board number 0 EM2 0 mynode normal 0x26 In the above the board number 0 next to EM2 refers to BD API hep9a 1 0 so the board number says that the node is situated on a board with the red switch setting set to 1 But the heron id 0x21 implies a red switch setting of 2 BD API hep9a 1 0 board number 0 EM2 0 mynode normal 0x06 But when using heron id 0x00 the heron id is automatically updated to a heron id with the correct board switch as derived from the board number 0 So you will be fine i
191. gt buf p gt blks p gt elts p gt Fd This function uses the first 4 parameters as its naming suggests Example unsigned long myfwrite const SRVFIEPARAMS p return fwrite p gt buf p gt blks p gt elts p gt Fd ungetc USER _SRV_FUNGETC This function uses the Fd and blks denoting a character parameters Example unsigned long myungetc const SRVFIEPARAMS p d fgets USER _SRV_ FGETS return ungetc p gt blks p gt Fd This function uses the Fd blks for size and buf parameters The elts parameter is actually set to 1 so blks elts would also denote the correct size Example unsigned long myfgets const SRVFIEPARAMS p return fgets p gt buf p gt blks p gt Fd fputs USER SRV _FPUTS This function uses the Fd and buf parameters The blks parameter is set to the size of the buf string and the elts parameter is set to 1 Example unsigned long myfputs const SRVFIEPARAMS p d fflush USER_SRV_FFLUSH return fputs p gt buf p gt Fd This function only uses the Fd parameter for the filehandle Example unsigned long myfflush const SRVFIEPARAMS p return fflush p gt Fd 45 HUNT ENGINEERING Server Loader USER MANUAL fseek USER_SRV_FSEEK This function uses the Fd blks for offset and elts for whence parameters Example unsigned long myfseek const SR
192. he HERON API used in the Server Loader In version 3 3 and later of the Server Loader the HERON API is used for all communications This includes the boot loader function as well as all server functions printf fwrite etc The bootloader functions use solely the HeronReadWord and HeronWriteWord functions From version 4 0 of the Server Loader most of the HSB functions in the HERON API are used as well in bootloader The server functions implementation uses the HeronOpen HeronRead HeronWrite HeronWaitIo and HeronClose functions What is init_io_functions The Server Loader doesn t do direct function calls to HERON API functions but instead uses pointers to HERON API functions The reason for this is that this makes the Server Loader C6x libraries independent of the HERON API version It does mean however that these functions must be initialised by you to point to the proper HERON API functions To help you a file called stubx c has been included with the Server Loader distribution In the example directory you ll find an instance in every sub directory How do use stubx c There ate two ways you can use the stubx c file First use the Create New HERON API Project plug in Upon the question whether to create the project for the Server Loader answer yes This will include a file which name xxxxx_stub c where xxxxx is the name of your project The file should have the proper heron i
193. he PowerPC executable file as specified The function used was the standard C fread and the os error shown is errno Error 3911 File s is not for PowerPC but for x s The PowerPC executable file as specified is not a proper PowerPC executable file Perhaps it is corrupted or the wrong file was specified in the network file The code in brackets is the file header s target architecture field Error 3912 Unsupported byte swap width of od bytes little gt big endian When processing a PowerPC executable file an unsupported item width was used when doing a byte swap Supported sizes are 1 2 and 4 bytes Error 3920 Error seeking ELF file Ys ph offset d os error Yod There was an error seeking the PowerPC executable file as specified The function used was the standard C fseek and the os error shown is errno Error 3921 Unable to allocate memory d bytes while reading ELF file There was an error trying to allocate temporary memory The function used was the standard C malloc Error 3922 Error reading ELF file s os error Yod There was an error reading the PowerPC executable file as specified The function used was the standard C fread and the os error shown is errno Error 3930 Error seeking ELF file s sh offset Yod os error od There was an error seeking the PowerPC executable file as specified The function used was the standard C fseek
194. he boot path is found by examining all BOOTLINK and BOOTPATH statements in your network file ND 0 nodea root 0 00000000 00000000 002ff800 idrom out a out ND 0 nodeb normal 0 00000000 00000000 002f 800 idrom out b out ND 0 nodec normal 0 00000000 00000000 002f 800 idrom out c out BOOTLINK nodea 0 nodeb 1 In the above example there is a path from the ROOT node nodea to the second node nodeb via Comport 0 on nodea But there is no path from the ROOT node nodea to the third node nodec Error 1006 Parsing s ROOT s not connected to host There is a ROOT node defined in your network file but it appears that it is not connected to the host PC Check that you have a HOSTLINK statement in your network file or both a TOHOST and FROMHOST statement The Server Loader needs a bi directional connection between the host PC and the ROOT node Error 1007 Parsing Ys EM1C can only use FIFO 0 but you use d in a BDCONN BDLINK statement In one of the BDCONN BDLINK or BDPATH statements in your network file use use a FIFO other than 0 with an EMIC inter board module With an EM1C you can only use FIFO 0 EMIC 0 emica normal 0x06 EMIC 1 em1cb normal 0x16 BDCONN emtica 0 emtcb 1 AN Error 1008 Parsing s EM1 can only use FIFO 0 but you use d in a BDCONN BDLINK statement In one of the BDCONN BDLINK or BDPATH statements in your network file use use a FIFO other than 0 with an EM1C inter board module With an E
195. he example Error 1012 Parsing s Node s declared for non existent board od In your network file you define an inter board module EM2 EM1 or EM1C for a carrier board that is not defined BD API hep9a 2 0 board 0 EM2 2 emia normal 0x06 AN In the above example board 0 is an HEPC9 with the red switch set to 2 but the EM2 inter board module is defined to exist on board 2 which is not defined Error 1013 Parsing s Board s cannot be remote because an EM1C doesn t propagate HSB and reset In your network file two boards are connected via an EM1C EMIC connection This is fine but neither board can be a remote slave board because EM1C modules don t propagate HSB and Reset necessary for a board to function remotely BD API hep9a 0 0 board 0 BD API hep9a 1 0 remote board 1 EMIC 0 emica normal 0x06 EMIC 1 em1cb normal 0x16 BDCONN emtica 0 emtcb 0 Error 1014 Parsing s Board s cannot be remote because an EM1 doesn t propagate HSB and reset In your network file two boards are connected via an EM1 EM1 connection This is fine but neither board can be a remote slave board because EM1 modules don t propagate HSB and Reset necessary for a board to function remotely BD API hep9a 0 0 board 0 BD API hep9a 1 0 remote board 1 EM1 0 em1a normal 0x06 146 HUNT ENGINEERING Server Loader USER MANUAL EM1 1 em1b normal 0x16 BDCONN em1a 0 em1b 0
196. he same time Operations on Files remove remove a file from the file system rename rename a file File Access Functions fclose closes a file fflush writes out any buffered information to the file fopen opens a file freopen reassigns the address of a FILE structure and reopens the file setbuf associates a buffer with an input or output file implemented as a macro setvbuf determines how a stream will be buffered Formatted Input Output Functions fprintf performs formatted output to a file 22 HUNT ENGINEERING Server Loader USER MANUAL fscanf printf scanf sprintf sscanf vfprintf vprintf vsprintf performs formatted input from a file performs formatted output to the stdout stream performs formatted input from the stdin stream performs formatted output to a character string in memory performs formatted input from memory similar to fprintf but with a single argument instead of an argument list similar to printf but with a single argument instead of an argument list similar to sprintf but with a single argument instead of an argument list Character Input Output Functions fgetc fgets fputc fputs getc getchar gets putc putchar puts ungetc returns the next character from a file reads a line from a file wtites a single character to a file wtites a string to a file returns the next character from a file implemented as a macro returns the next character from the stdin stream
197. hed the end of file after processing LISTEN lt broadcast gt lt nodename gt in a LISTEN statement A fifo number was expected LISTEN bbc nodea AN Error 0476 Line od LISTEN statement od uses invalid fifo number The parser expected to find a fifo number after processing LISTEN lt broadcast gt lt nodename gt in a LISTEN statement but found a text string instead LISTEN bbc nodea xxxx AN Error 0477 Line d LISTEN statement d uses invalid fifo number d The parser successfully found and parsed a fifo number after processing BDCAST lt broadcast gt lt nodename gt lt fifo gt in a LISTEN statement but the fifo number is not a valid fifo number It must be a number from 0 to 5 LISTEN bbc nodea 7 AN Error 0478 Line d Expected umi value in LISTEN statement d The parser reached the end of file after processing LISTEN lt broadcast gt lt nodename gt lt fifo gt lt umi gt in a LISTEN statement A UMI number was expected LISTEN bbc nodea 0 umi AN Error 0479 Line d LISTEN statement d in network file uses invalid umi value s The parser expected to find a UMI value after processing LISTEN lt broadcast gt lt nodename gt lt fifo gt lt umi gt in a LISTEN statement but found a text string or found an invalid value for the UMI value use only values 0 to OxF 15 LISTEN bbc nodea 0 umi Oxff Error 0500 Line d Expected node name in UMIRESET statemen
198. ice int n char options char netwrk With the handle functions you tell HeartConf what devices you have opened already via the uDevice parameter which is a pointer to an array of API handles of opened devices and parameter n is the number of API handles of open devices in the uDevice array Before opening any device HeartConf will first check if a device is already opened by checking the list of open devices uDevice If so the handle you provided will be used If not then HeartConf will try to open the device itself To emphasise this you don t need to open all possible devices You simply tell the heartconf handle functions what devices you already have open HeartConf will use handles from the list as it needs to and if a device is not in the list it will open the device itself So you don t need to supply a list of all devices that the Server Loader might use you only list the handles of devices that you happen to have opened already Parameter uDevice is an array of handles HE_HANDLE and parameter n is to specify the number of valid handles open devices in the uDevice array It depends on the network file and the options used what devices HeartConf will try to open Please note that HeartConf may use multiple handles for example both Fifo A and HSB Example int main int argc char argv hesl sl HE DWORD Status int r HE HANDLE FifoADev NULL HSBDev NULL Status HeOpen hep9a 0 HS
199. id int id nt bdid char dev int bdsw nt int GetBoardHsbAccessSw i bdid char dev int bdsw int GetBoardRstAccessSw i Use GetBoardCount to get the number of BD API boards in the network file Using a board id you can extract board name like hep9a using GetBoardName extract the board number using GetBoardSw and extract the device used in a BD API using GetBoardFifo Boards may be defined as being remote boards Use IsBoardRemote to find such board information If it is a remote board you may want to know what board can be used to access the remote board Function Get BoardHsbAccessId will give you the board id of the board through which the remote board s HSB can be accessed The alternative Get BoardHsbAccessSw works identically but instead of a board id gives you the board s name and board number Function GetBoardRstAccessId will give you the board id of the board through which a remote board can be reset The alternative GetBoardHsbAccessSw works identically but instead of a board id gives you the board s name and board number Finally use the GetBoardId function to give you the board id of a board whose name and board switch you know The return values for all functions are 0 upon success 1 upon failure and larger than 1 41 HUNT ENGINEERING Server Loader USER MANUAL upon error Node information Node information can be retrieved using a node id This refers to nodes defined with ND C
200. id index in the list of nodes points to nothing Please contact support and send your network file Error 1541 Node s is not an Inter Board Module 157 HUNT ENGINEERING Server Loader USER MANUAL FindIBCLink error The specified node is not an inter board connector module Error 1542 Internal error Inter Board Module s is on non existing board index d in od boards Internal error A node has a board index that isn t in the list of boards the board index is smaller than O or higher than the number of boards defined in the network file Please contact support and send your network file Error 1543 Internal error Board index od of d boards is NULL Internal error A node with a valid board index in the list of boards points to nothing Please contact support and send your network file Error 1544 Internal error Inter Board Module s is on non existing board index d in od boards Internal error A node has a board index that isn t in the list of boards the board index is smaller than 0 or higher than the number of boards defined in the network file Please contact support and send your network file Error 1545 Internal error Board index Yod of d boards is NULL Internal error A node with a valid board index in the list of boards points to nothing Please contact support and send your network file Error 1546 Internal error Inter Board Module is NULL on board od of d boards In
201. id slot for host inerfaces is 5 only a heron id with bits 3 2 1 0 set to anything else is invalid PCIF 0 mynode normal 7 Error 0199 Line d Node s has HERON id 0x x ie board 0x x slot 0x x but its HERON carrier has a switch set to 0x x The heron id used in a PCIF node statement indicates that the node is situated on one board but the board number used in the same PCIF node statement indicates that the node is situated on a different board The heron id is a number made up of the board switch bits 7 6 5 4 and slot bits 3 2 1 0 The board switch encoded in the heron id should match the board switch as used in the BD API statement as indicated by the board number used in the PCIF node statement However note that if the heron id as used in the network file uses a board switch of 0 but the board number uses a red switch value other then 0 then the heron id is updated to the correct value BD API hep9a 1 0 board number 0 PCIF 0 mynode normal 0x25 In the above the board number 0 next to PCIF refers to BD API hep9a 1 0 so the board number says that the node is situated on a board with the red switch setting set to 1 But the heron id 0x25 implies a red switch setting of 2 BD API hep9a 1 0 board number 0 PCIF 0 mynode normal 0x05 But when using heron id 0x05 the heron id is automatically updated to a heron id with the correct board switch as derived from the board number 0
202. ill be set to MOD_C6X 2 GetNodeModType 1 amp t will return 0 and t will be set to MOD_FPGA 8 GetNodeModType 2 amp t will return 0 and t will be set to MOD_EM2 7 And GetNodeModType 3 amp t will return an error because there s no fourth node definition Include Hinclude hesl h Return value Get NodeModType will return a value of 0 if the node identified by node index nodeid is defined in the network file modt ype is then set to the module type of that node The function will return a value of 2 or higher if nodeid is an invalid node id and upon error int hesl GetNodeName int nodeid char nname i GetNodeName is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file GetNodeName will tell you the name of the node with node index nodeid Note that it will write a character string to nname so parameter nname must be an character array or point to an allocated memory area Nodes can be identified with a node id nodeid In your network file the very first node definition will define a node with index 0 the second node definition will define a node with id 1 and so on Examples of node definitions are C6 81 HUNT ENGINEERING Server Loader USER MANUAL FPGA
203. ill find a tar file called slxx tar xx deno ting the latest version eg sl31 tar in directory mnt cdrom software sl linux Depending on your system setup the CD will have been mounted automatically or you will have to mount it manually To install the tar file create a directory where you want to install the Server Loader then un tar it For example mkdir hesl cd hesl tar xvf mnt cdrom software sl linux sl131 tar After un tarring the file there will be an install script in the hes1 directory To run this script you must be the root user Simply type installme This will copy the Server Loader executable linuxs1 to usr local bin the shared library liblinuxsl1 so to usr local lib the include files to usr local include To uninstall simply run the uninstall script uninstallme Installation under VxWorks The file that you will need is located in the software api vxworks directory on the HUNT ENGINEERING CD The file is vxwsl o and it contains the Server Loader executable the HeartConf utility and the Server Loader library interface To use the library you will need an include file this can only be installed via the HUNT CD setup The installation program on the CD can create an installation for Windows with VxWorks attached to it You can use the CD setup program to install SDP which includes the Server Loader for both Windows and VxWorks at the same time But you can also install just for Windows
204. imum is d For each node defined in the network file CND C6 CAT FPGA GDIO PCIF etc an internal object is created Because only so many objects can be stored in the array that the Server Loader and HeartConf software uses there is a maximum number of nodes that can be processed This error is returned when in your network file you define more nodes than the software can process maximum of 256 nodes Error 0101 Line d Expected board number in FPGA statement The parser reached the end of file after processing FPGA in a node statement A board number referring to a BD statement was expected FPGA N Error 0102 Line d Node od uses invalid board number s The parser expected to find a board number after parsing FPGA in a node statement but found a text string instead A valid board number is a digit that indicates what board statement the node is on The number must refer to a BD statement e g a board number 0 refers to the first BD statement in the network file a board number 1 refers to the second BD statement in the network file and so on FPGA x Error 0103 Line od Expected node name in FPGA statement The parser reached the end of file after processing FPGA lt n gt in a node statement A node name was expected FPGA 0 AN Error 0104 Line od Expected node type in FPGA statement The parser reached the end of file af
205. in on and bits 3 2 1 0 identify the slot As valid slots for C6 nodes are 1 2 3 or 4 a heron id with bits 3 2 1 0 set to anything else is invalid FPGA 0 mynode normal 7 Error 0109 Line od Expected bit stream filename in FPGA statement The parser reached the end of file after processing FPGA lt n gt lt nodename gt lt type gt lt heronid gt in a node statement A filename was expected The filename would be a bit stream rbt or hcb file FPGA 0 mynode normal 0x1 AN Error 0110 Line d Expected bit stream filename in FPGA statement The parser found the start of a new statement after processing FPGA lt n gt lt node name gt lt type gt lt heronid gt in a node statement A filename was expected The filename would be a bit stream rbt or hcb file FPGA 0 mynode normal 0x1 AN FPGA Error 0111 Line d Node s has HERON id 0x x ie board 0x x slot 0x x but its HERON carrier has a switch set to 0x x The heron id used in a FPGA node statement indicates that the node is situated on one board but the board number used in the same FPGA node statement indicates that the node is situated on a different board The heron id is a number made up of the board switch bits 7 6 5 4 and slot bits 3 2 1 0 The board switch encoded in the heron id should match the board switch as used in the BD API statement as indicated by the board number used in the FPGA node statement However not
206. ink checks whether an inter board module s channel is connected to another inter board module s channel as defined in the network file An inter board module is for example a PC9 EM2 CPCI9 EM2 PC9 EM1 or PC9 EMIC and is used to connect two HERON boards together using cables Parameters The inter board module is identified with fnode_id In your network file the very first node declaration e g ND C6 FPGA EM2 will define a node with id 0 the second node declaration will define a node with id 1 and so on The channel on the node is identified with parameter ffifo Thus FindIBCLink will check what inter board module is connected to channel ffifo of an inter board module with node id fnode_id If FindIBCLink finds that there is a connection the node id of the inter board module it is connected to is returned in mode Ad and the fifo it is connected to is returned in parameter tfifo and the function returns 0 If there is no connection tnode_id and tfifo will both be set to 1 and FindIBCLink returns 0 FindIBCLink will return a value of 2 or larger upon error Example Nodes on board 0 c6 0 MODa ROOT 1 0x01 modulel out em2 0 em2a normal 0x06 Nodes on board 1 c6 1 MODb ROOT 0 0x01 module2 out em2 1 em2b normal 0x06 BDCONN EM2a 0 EM2b 0 With the above network file definitions FindIBCLink 1 0 amp tnode amp t fifo will return 0 tnode will be set to 3 and
207. inter board module EM1 C s for board to board connections Use an EM1 or EM2 for that or define two systems connected by the EM1 C The EM1 C inter board connector module can only be used between two stand alone systems You cannot use HEART statements to connect modules on boards that are connected via EM1 C s Error 1313 Internal error Cannot find board switch for board od HeartConf cannot find the red board switch setting of a board definition BD API This is an internal error Please contact support and send the network file Error 1314 No inter board module defined for board od A HEART statement defines a connection between two modules on different boards but one of the boards doesn t have an inter board connector module such as EM1 or EM2 defined therefore the required connection cannot be configured Error 1315 You cannot use inter board module EM1 C s for board to board connections Use an EM1 or EM2 for that or define two systems connected by the EM1 C The EM1 C inter board connector module can only be used between two stand alone systems You cannot use HEART statements to connect modules on boards that are connected via EM1 C s Error 1316 Internal error Cannot find board switch for board od HeartConf cannot find the red board switch setting of a board definition BD API This is an internal error Pleaes contact support and send the network file Error 1317 No inter board module defin
208. ion You can very well use two files for example a proper network file called network and a network file flash for HETFLASH writing As a full example an example network file as below Siete Waele Slee ee Steele a le eS ee E SE e SB ben SS SO eee Be eee Board description BD API Board_type Board_Id Device Id EE BD API hep3b 0 0 EE Nodes description nb NAME Type CC id GBCW LBCW TACK Program s CPEE EE E OE E ett a ea ee E T ND 0 NODEO ROOT 2 00000000 00000000 002ff800 idrom out root out ND 0 NODE1 NORMAL 1 00000000 00000000 002ff800 idrom out nod1 out ND 0 NODE2 NORMAL 0 00000000 00000000 002ff800 idrom out nod2 out Bootpath description BOOTLINK ND NAME PORT ND NAME PORT BOOTLINK NODEO 5 NODE1 2 29 HUNT ENGINEERING Server Loader USER MANUAL BOOTLINK NODE1 1 NODE2 4 Number of the link connected to the host system HOSTLINK PORT HOSTLINK 3 Should change to EE Board description BD API Board_type Board_Id Device Id a E a de EE E A GEES ee EE dE E flash API hep3b 0 0 EE EE Ee a EE EE dh SE EE EE e Ed EE E Nodes description nb NAME Type CC id GBCW LBCW TACK Program s aia ENEE E he Eeer ee ea ice ete fete ote ND 0 NODEO NORMAL 2 1EF78000 1EF78000 002ff800 idrom out root out ND 0 NODE2 NORMAL 1 1E4A4000 1E 4A4000 002ff800 idrom out nodl out ND 0 NODE3 ROOT 0 1 4A4000 1EF78000 002ff800 idrom out nod2 out Bootpath description BOOTLINK ND NAME
209. ion amp major amp minor amp verstr if verstr NULL 46 HUNT ENGINEERING Server Loader USER MANUAL printf SL version s n verstr else printf SL version d d n major minor How to build In the inc directory of the Server Loader directory typically c heapi hesl if you installed into the default c heapi directory there is an include file hesl h This file uses some definitions from the API so usually you would need to include both files as follows include heapi h include hesl h The Server Loader library is multi threaded and you must set the proper switches in your project For example in Microsoft C C you go to Project gt Options gt C C gt Code Generation set field use run time library to multi threaded The heapi h file has definitions that may be different between different platforms or even between different compilers Environment Compiler variables are used to select the proper definitions If you build for a WIN32 platform with a 32 bit Microsoft Visual C C compiler then no specific environment compiler options need to be set If you build for a WIN32 platform with a 32 bit Borland C C then no specific environment compiler options need to be set However some Server Loader examples are slightly different based on what compiler you use For those examples you will need to define a _BL directive This is all further explained in the relevan
210. ion employs the server and this functionality cannot be used when programming the HETFLASH If you do accidentally use the s option the Server Loader may still program the HETFLASH correctly but it will most likely complain about a bad connection with the ROOT processor If all goes well you should see progress information as follows Flash programmer Write bootstream to file flash rom Make sure that the HETFLASH is in slot 1 Also make sure that PRGEN is fitted and that BOOTEN is not fitted Filelength 40932 bytes Write size 10233 to HETFLASH Write block of size 8192 bytes to HETFLASH Write block of size 8192 bytes to HETFLASH Write block of size 8192 bytes to HETFLASH Write block of size 8192 bytes to HETFLASH Write block of size 8164 bytes to HETFLASH Done Please re fit the BOOTEN jumper before use As you can see the Server Loader writes to a file flash rom It then immediately uses this file and writes its contents to the HETFLASH The flash rom file can be deleted but you may perhaps want to use it for your own custom HETFLASH programming The Server Loader also has a verbose option It will then show in detail what is being stored in the flash rom file This option can be used to help finding problems The HETFLASH programming is done Power down the machine get the C4x mother board out Remove the HETFLASH from the board and replace your system as described by the network file Now add the HE
211. iple boards Using such inter board modules it is possible to access all of a board fifo s hsb reset via a board connected to it A board that is to be accessed via another board is specified with the remote keyword in a BD APT definition This way boards that are not inserted in the PC can still be booted and accessed via another board which is inserted in a PC GetBoardRstAccessId tells you via what other board reset can be accessed for the board with board id bdid If the board s reset can be accessed directly then ig will be set to the same value as bdid If the board is remote then id will be set to the board id of the board via which reset on board bdid can be accessed Note that GetBoardRstAccessId is identical to Get BoardRstAccessS w but that the access board is identified with id in Get BoardRstAccessId and with dev and bdsw in GetBoardRstAccessSw The board is identified with a board id bdid In your network file the very first BD declaration will define a board with id 0 the second BD declaration will define a board with id 1 and so on Don t confuse the board id with the red switch Upon error the function returns a value of 2 or higher Otherwise it will return 0 and id will be set to the board via which reset on board bdid can be accessed Example BD API hep9a 0 0 BD API hep9a 1 0 remote em2 0 em2a normal 0x06 em2
212. is used twice The BDLINK or BDPATH definition specifies how two boards are connected via an EM2 EM1 or EM1c module so really the fifo number identifies the channel number used on the EM module Error 0351 Line d Fifo od on board od used at least twice in BDLINK statements The parser successfully parsed at least two BDLINK or BDPATH statements but it finds that a sending fifo is used twice BDLINK 0 0 10 BDLINK 0 0 2 0 In the above fifo 0 of board 0 is used twice The BDLINK or BDPATH definition specifies how two boards are connected via an EM2 EM1 or EM1c module so really the fifo number identifies the channel number used on the EM module Error 0352 Line od Fifo od on board d used at least twice in BDLINK statements The parser successfully parsed at least two BDLINK or BDPATH statements but it finds that a receiving fifo is used twice BDLINK 2000 BDPATH 0010 In the above fifo 0 of board 1 is used twice BDPATH defines a two way duplex connection The BDLINK or BDPATH definition specifies how two boards are connected via an EM2 EM1 or EM1c module so really the fifo number identifies the channel number used on the EM module Error 0353 Line d Fifo od on board d used at least twice in BDLINK statements The parser successfully parsed at least two BDLINK or BDPATH statements but it finds that a sending fifo is used twice BDLINK 1020 BDPATH 0010 In the above fifo 0 of board 1 is used twice BDPA
213. it is usually obvious reading verbose text or printPd text from the console when the Server Loadet is ready Example On the HUNT ENGINEERING CD you will find an example of using the Server Loader executable in a DOS box and an API application in another DOS box in parallel It s in software examples server_loader_examples c6x sl_api parallel Server Loader amp API code in one application Server Loader library You can also use the Server Loader library When serving the Server Loader call would not complete until all served processor nodes have executed srv_exit so any API code will have to run in a separate thread or threads In the network file you will have defined host module fifo connections for use by your API application using NOSERVE to reserve the connections for use by your API application And of course you will have defined bi directional host module fifo connections for all processor nodes that you wish to be served by the Server Loader API code rules Note that in your API code you must not execute HeReset if you do you will reset the system and all booted programs and all HEART fifo connections will disappear It is not necessaty to run HeartConf because the Server Loader will configure all fifo connection you defined in the network file 58 HUNT ENGINEERING Server Loader USER MANUAL Synchronisation While booting loading the processor nodes and configuring HEART the Server Loader
214. itch Cannot boot node When trying to create HEART connections a HERON ID as specified was found that doesn t match any defined boards in the network file Bits 7 4 of the HERON ID are the red switch setting of a carrier board such as e g HEPC9 or HERON BASE2 Error 3860 Internal error Board od from is not an API HEPC9 board Internal error When trying to create IBC inter board connector connections a board was not a BD APP type or was not a HEPC9 or HECPCI9 Only HEPC9s of type BD APT can be used for inter board connectors such as EM2 or EM1 Error 3861 Internal error Board id d is outside array range od Internal error When trying to create IBC inter board connector connections a board index was used that was larger than the number of defined boards in the network file Please contact support and send your network file Error 3862 Internal error Board d to is not an API HEPC9 board Internal error When trying to create IBC inter board connector connections a board was not a BD APP type or was not a HEPC9 or HECPCI9 Only HEPC9s of type BD APP can be used for inter board connectors such as EM2 or EM1 Error 3863 Internal error Board id od is outside array range d Internal error When trying to create IBC inter board connector connections a board index was used that was larger than the number of defined boards in the network file Please contact support and send your
215. le you define more nodes than the software can process maximum of 256 nodes Error 0041 Line d Expected board number in ND or C4 statement The parser reached the end of file after processing ND in a node statement A board number referring to a BD statement was expected ND N Error 0042 Line d Node od uses invalid board number Tas The parser expected to find a board number after parsing ND in a node statement but found a text string instead A valid board number is a digit that indicates what board statement the node is on The number must refer to a BD statement e g a board number 0 refers to the first BD statement in the network file a board number 1 refers to the second BD statement in the network file and so on ND x N Error 0043 Line d Expected node name in ND or C4 statement The parser reached the end of file after processing ND lt n gt in a node statement A node name was expected ND 0 AN Error 0044 Line d Expected node type in ND or C4 statement The parser reached the end of file after processing ND lt n gt lt nodename gt in a node statement A node type ROOT or NORMAL was expected ND 0 mynode Error 0045 Line d Node s uses invalid node type s The parser expected to find a node type ROOT or NORMAL after parsing ND lt n gt lt nodename gt in a node statement but found a text string
216. led with the s option or when the Server only function hes class s server function is called and the loading and serve setup phase have proceeded successfully Parameters s is the semaphore that you want to be flagged Include include hesl h Return value none int hesl GetBoardCount void GetBoardCount is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file GetBoardCount returns the number of boards defined in a network file Every BD definition represents one board Example BD API hep9a 0 0 BD API hep9a 1 0 With the above network file definitions GetBoardCount will return 2 Include include hesl h Return value the number of boards BD entries in a network file int hesl GetBoardFi fo int bdid int fifo i GetBoardFifo is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file GetBoardFifo will set the fifo parameter to the fifo used in a BD API board definition in the network file Parameters The board is identified with a board id bdid In your network file the very first BD de
217. lied in the header file stdioC60 h c6x nodes or stdioc40 h c4x nodes All that is then required by the programmer is the inclusion of the header file using the C include statement before the functions are used The header files stdioc60 h and stdioc40 h can be found in the hes1 inc directory The Input Output Functions The Input Output functions included with the C4x Server Loader run time libraries consist of a large subset of the ANSI stdio functions The functions range from file operations and file access to formatted input and output character input and output and error handling functions There are five ANSI C functions not supported These are tmpfile tmpnam fgetpos fsetpos and clearerr The output stream stdout and the input stream stdin are provided as well as the stderr stream These streams are automatically opened at the beginning of program execution and are connected to the shell in which the Server Loader utility is executed All other file streams require the user to open a path to the file stream by calling the fopen function before the file can be accessed A successful call to the fopen function returns a file pointer that must be used for all subsequent operations on that file After performing I O on an open file the path to the file can be closed with the fclose function Files should be closed when no longer required and at the end of a program There is a limit on the number of files which may be open at t
218. ll C4x processors in the system In the network file update all ND entries to have the correct GBCR and LBCR as determined in the previous step In the network file you must alter a BD entry into a FLASH entry In the network file you must change the ROOT processor to the one processor that will be connected to the HETFLASH via a comport For example in a HEPC4 there could be processor modules in slot 1 2 and 3 while the HETFLASH will be in slot 4 Thus the ROOT processor will be the processor in slot 3 To find out what the global bus control register GBCR and local bus control register LBCR values are you could use the Server Loader with the yet unaltered network file and use the vc option The Server Loader will then output GBCR and LBCR information which it has retrieved from the respective IDROMs on the different modules The proper values for GBCR and LBCR are also listed in a TIM 40 module s manual Typically node entries in a network file are as follows Node type ccid GBCR LBCR lack program s ND 0 NODEO ROOT 2 00000000 00000000 002ff800 idrom out root out ND 0 NODE2 NORMAL 1 00000000 00000000 002ff800 idrom out mod out ND 0 NODE3 NORMAL 0 00000000 00000000 002ff800 idrom out nod2 out 28 HUNT ENGINEERING Server Loader USER MANUAL You would need to change the GBCR and LBCR entties in all lines Node type ccid GBCR LBCR tack program s ND 0 NODEO ROOT 2 1EF78000 1EF78000 002ff800 idrom out
219. llows you to tell the Server Loader what devices you happen to have open the Server Loader will then use handles you provide instead of trying to open a device If a device is not listed the Server Loader will open the device itself Parameter n is the number of open devices handles that you have listed in the array that uDevice points at Include Hinclude hesl h Return value serverloader will return 0 upon success and return 2 or higher upon error Use get lasterr of the hesl class for a description of the error void hesl set_user vprint USER_VBSFUNC fie i The sert user vprint function will replace the default function that prints verbose strings with a function that you supply The default verbose print function is simply the printf function printing verbose strings to the stdout console Parameters fie is a pointer to function that prints displays verbose information The function is supplied by you and takes a verbose string as input parameter Please refer to hesl h for a type definition for USER_VBSFUNC Include include hesl h Return value none set_user_vprint always succeeds int hesl set_ user Ciel USER_SRVFUNC fie int whichfie i The set_user_fie function will replace the selected default server function with a function that you supply The default server functions assume that the Server Loader is used in a DOS box and the default server functions write to the stdout
220. may accidentally overwrite your application You cannot use Server Loader stdio functions on any of the C4x nodes Using stdio functions does not necessarily cause problems but it is likely that stdio calls initiate some unexpected communications to neighbouring C4x nodes Use the v verbose option when programming the HETFLASH to get information about what is put into the flash rom file It might give you a hint what the problem is There is a flash testing option that might help with troubleshooting This is explained in the next section FLASH testing option When programming a HETFLASH the Server Loader will create a flash rom file and then write it to the HETFLASH in slot 1 First the Server Loader will send 4 bytes representing the size of all the data in words then the full contents of the flash rom file In testing mode you would not have the HETFLASH in slot 1 but your normal system In testing mode the Server Loader pretends to be the HETFLASH and sends the flash rom file as a boot stream You cannot do the same thing in flash mode because we need to send the size to the HETFLASH as the first 4 bytes but the size shouldn t be sent to an actual system Therefore you need to connect host port A i e the bus interface comport to a comport of the C4x that would be next to the HETFLASH The HETFLASH may or may not be in the system but should at the very least not try to boot the system i e the BOOT EN jumper i
221. mber 0 C6 0 mynode normal 0 0x21 myfile out In the above the board number OUT next to C6 refers to BD API hep9a 1 0 so the board number says that the node is situated on a board with the red switch setting set to 1 But the heron id 0x21 implies a red switch setting of 2 BD API hep9a 1 0 board number 0 C6 0 mynode normal 0 0x01 myfile out But when using heron id 0x01 the heron id is automatically updated to a heron id with the correct board switch as derived from the board number 0 So you will be fine if for the heron id you simply write the slot number In the above the software will update heron id 0x01 to the correct heron id 0x11 automatically Error 0085 Node s says it s on board od but there s no such HERON cartier The boatd number used in a C6 node statement does not refer to a valid board Valid boards are defined by BD statements Board number 0 refers to the first BD statement board number 1 to the second BD statement and so on BD API hep9a 1 0 board number 0 C6 1 mynode normal 0 0x11 myfile out In the above board number 1 refers to a second BD statement but there s only one board defined The board number should be 0 referring to BD API hep9a 1 0 BD API hep9a 1 0 board number 0 C6 0 mynode normal 0 0x11 myfile out 113 HUNT ENGINEERING Server Loader USER MANUAL Error 0100 Parsing os Too many nodes max
222. mber after processing HEART lt nodename gt lt fifo gt in a HEART statement but the fifo number is not a valid fifo number It must be a number from 0 to 5 HEART nodea 7 Error 0406 Line d Expected node name in HEART statement d The parser reached the end of file after processing HEART lt nodename gt lt fifo gt in a HEART statement A node name was expected HEART nodea 0 nw Error 0407 Line d HEART statement od uses invalid heron id or node s The parser successfully parses the node name in a HEART statement but finds that this node is not defined earlier in the network file HEART nodea 0 xxxx Error 0408 Line d HEART statement od in network file uses non HERON node s The parser successfully parses the node name in a HEART statement and finds that this node is defined earlier in the network file but the node is not a HERON node HEART nodea 0 c4x Error 0409 Line d Expected fifo number in HEART statement d The parser reached the end of file after processing HEART lt nodename gt lt fifo gt lt nodename gt in a HEART statement A fifo number was expected HEART nodea 0 nodeb N Error 0410 Line Goal HEART statement d in network file uses invalid fifo number 136 HUNT ENGINEERING Server Loader USER MANUAL The parser expected to find a fifo number after processing HEART lt nodename gt lt fifo gt lt nodename gt in a HEART statement but found a
223. me in C6 statement The parser reached the end of file after processing C6 lt n gt lt nodename gt lt type gt 112 HUNT ENGINEERING Server Loader USER MANUAL lt ccid gt lt heronid gt in a node statement A filename was expected The filename would be a C6x out file C6 0 mynode normal 0 Ox1 Error 0083 Line d Expected out filename in C6 statement The parser found the start of a new statement after processing C6 lt n gt lt node name gt lt type gt lt ccid gt lt heronid gt in a node statement A filename was expected The filename would be a C6x out file C6 0 mynode normal 0 0x1 C6 Error 0084 Line d Node s has HERON id 0x x ie board 0x x slot 0x x but its HERON carrier has a switch set to 0x x The heron id used in a C6 node statement indicates that the node is situated on one board but the board number used in the same C6 node statement indicates that the node is situated on a different board The heron id is a number made up of the board switch bits 7 6 5 4 and slot bits 3 2 1 0 The board switch encoded in the heron id should match the board switch as used in the BD APT statement as indicated by the board number used in the C6 node statement However note that if the heron id as used in the network file uses a board switch of 0 but the board number uses a red switch value other then 0 then the heron id is updated to the correct value BD API hep9a 1 0 board nu
224. ment The parser expected a board number after processing BD API lt boardname gt but found a text string instead Use 0 for FifoA or ComportA 1 for FifoB or ComportB and so on The device chosen will be used to communicate between target and host but note that on HEART boards such as HEPC9 FifoA is always used for booting processors and the device specified is only used by the Server BD API hep9a 0 x Error 0018 Line od Both MasterMode and Interrupts have already been defined but found a third keyword on The parser has already found and parsed MasterMode and Interrupt settings in a BD API board statement but then finds a third keyword on Only a sequence of two of the keywords on and off were expected BD API hep3b 0 0 off on on Error 0019 Line od Both MasterMode and Interrupts have already been defined but found a third keyword oft The parser has already found and parsed MasterMode and Interrupt settings in a BD API board statement but then finds a third keyword off Only a sequence of two of the keywords on and off were expected BD API hep3b 0 0 off on off Error 0020 Line d IRQ is already defined but found a second keyword 10 The parser has already found and parsed IRQ settings in a BD API board statement but then finds another IRQ keyword 10 Only one IRQ keyword 10 11 12 or 15 was expected BD API hep2e 0 0 12 10
225. mple unsigned long myfputs const SRVFIEPARAMS p return fputs p gt buf p gt Fd fflush USER_SRV_FFLUSH This function only uses the Fd parameter for the filehandle Example unsigned long myfflush const SRVFIEPARAMS p d fseek USER_SRV_FSEEK return fflush p gt Fd This function uses the Fd blks for offset and elts for whence parameters Example unsigned long myfseek const SRVFIEPARAMS p return fseek p gt buf p gt blks p gt elts ftell USER_SRV_FTELL This function only uses the Fd parameter for the filehandle Example unsigned long myftell const SRVFIEPARAMS p return ftell p gt Fd feof USER _SRV_FEOF This function only uses the Fd parameter for the filehandle Example unsigned long myfeof const SRVFIEPARAMS p return feof p gt Fd ferror USER_SRV_FERROR This function only uses the Fd parameter for the filehandle Example unsigned long myferror const SRVFIEPARAMS p return ferror p gt Fd Include include hesl h 94 HUNT ENGINEERING Server Loader USER MANUAL Return value 1 if successfull 0 upon error The only possible error is if you set whichfie to an unknown value int hesl terminate void The server function will serve a system of Cox FPGA and other types of nodes as per the network file that it is asked to process The system must have been reset boote
226. n the broadcasting module and the listening module trying to find a path via inter board connector modules such as the EM1 or EM2 Error 1400 No inter board module defined for board d Boards used in a BDCONN BDLINK statements must have an inter board module defined A BDCONN or BDLINK statement has declared an inter board connector module link between two boards but one board doesn t have an inter board connector module defined such as an EM2 or EM1 Error 1401 Board d cannot be a slave as there are no BDCONN BDLINK connections to it A board can be a slave only if it is connected via inter board connector modules such as EM2 or EM1 but not the EM1 C to another board Access to a slave board s reset HSB and fifo s will be via a master board Error 1402 Board d cannot be a slave as an EM1 C doesn t carry control signals reset HSB A board can be a slave only if it is connected via inter board connector modules such as EM2 or EM1 but not the EM1 C to another board Access to a slave board s reset HSB and fifo s will be via a master board Error 1403 Out of memory while trying to find master slave path between boards Memory allocation failed when trying to allocate enough space to store a master slave path of boards Error 1404 Cannot find a master board to support slave board od there are no BDCONN BDLINK connections for HSB towards a master board A slave board must have a master board I
227. n will show module information downloaded from modules in the network In the case of the C6x you must have used eeprom62 out or eeprom6 7 out in your network file for example the network file should have an entry similar to C6 0 heronl root 1 eeprom62 cut heronl out C6 0 heron2 normal 2 eeprom67 cut heron2 out eeprom62 out and eeprom6 7 out collect information stored in on module eeprom and forward it to the Server Loader This information contains among other things the module s ID memory sizes memory start addresses and memory read write wait cycles However it is not necessary to use the eeprom62 out and eeprom67 out files But if you don t use them you cannot use the c option either The following entry in the network file will work just as well C6 0 heronl root ch heronl out C6 0 heron2 normal 2 heron2 out Thus the eeprom files are purely to collect information from the modules The c option must be specified to show this information By default the c option will show just one line of data showing a module s ID and the 4 memory sizes When specifying c 2 all stored information will be displayed Please be aware that the c option will only display correct information when the eeprom files are declared in your network file In case you use c with the entries in the network file as above without eeprom files the Server Loader has not been able to collect information so it cannot show you any proper data Also
228. n your network file the very first node definition will define a node with index 0 the second node definition will define a node with id 1 and so on Examples of node definitions are C6 FPGA EM2 GDIO and PCIF But note that this is not a full list and in future more node types may be added The board is identified with a board id bdid In your network file the very first BD declaration will define a board with id 0 the second BD declaration will define a board with id 1 and so on Don t confuse the board id with the red switch Upon error the function returns a value of 2 or higher Otherwise it will return 0 and bdid will be set to the board via which reset for node nodeid can be accessed Example BD API hep9a 3 0 BD API hep9a 4 0 remote c6 0 MODa ROOT 1 0x02 module2 out fpga 1 io2v2 normal 0x14 rbtfile rbt em2 0 em2a normal 0x06 em2 1 em2b normal 0x16 BDCONN EM2a 0 EM2b 0 With the above network file definitions GetNodeRstAccessId 0 amp i will return 0 and i will be set to 0 because reset for node MODa can be accessed via board 0 hep9a 3 GetNodeRstAccessId 1 amp i will return 0 and i will be set to 0 because HSB for node io2v2 can be accessed via board 0 hep9a 3 GetNodeRstAccessId 4 amp i will return an error because there s no node with id 4 i e there s no fifth node definition Include Hinclu
229. name gt in a BOOTLINK statement A FIFO or Comport number was expected BOOTLINK mynode Error 0284 Line d BOOTLINK statement uses invalid link number s The parser expected to find a link number after processing BOOTLINK lt nodename gt in a BOOTLINK statement but found a text string instead BOOTLINK mynode xxxx Error 0285 Line d BOOTLINK statement uses invalid link number od The parser successfully found and parsed a FIFO or Comport number after processing BOOTLINK lt nodename gt in a BOOTLINK statement but the link number is not a valid FIFO or Comport C6 0 mynode root 0 0x1 myfile out BOOTLINK mynode 8 For example C6x nodes have 6 FIFOs and valid values are 0 1 2 3 4 and 5 Error 0286 Line d Expected node name in BOOTLINK statement The parser reached the end of file after processing BOOTLINK lt nodename gt lt n gt in a BOOTLINK statement A node name was expected 125 HUNT ENGINEERING Server Loader USER MANUAL BOOTLINK mynode 0 Error 0287 Line d BOOTLINK statement uses undefined node s The parser successfully parses the node name in a BOOTLINK statement but finds that this node is not defined earlier in the network file BOOTLINK mynode 0 xxxx Error 0288 Line d BOOTLINK statement uses non processor node s The parser successfully parses the node name in a BOOTLINK statement and this node is defined earlier in the network file but the node is not a pro
230. nclude file included but you may want to check this just to make sure Second you can simply add stubx c to your Code Composer Studio project In this case you must edit the stubx c file to reflect which heron module you are using If the module for which you compile link an application is a HERON1 module then include heronl h in the stubx c file If the module for which you compile link the application is a HERON4 include heron4 h in the stubx c file And so on In all examples the first method is used 34 HUNT ENGINEERING Server Loader USER MANUAL The Server Loader Host Libraries Overview It is possible to add Server Loader functionality to your PC program The Server Loader is available as a library For win32 systems a DLL plus LIB file are in the hes1 1lib win32 directory for LINUX there is a liblinuxsl gso shared library in the src directory installed into usr local 1ib for VxWorks the library is part of the vxwsl o file and for RTOS 32 there s a library rtossl lib in hes1 1ib rtos32 The Server Loader is written in C With version 4 08 of the Server Loader a new interface is introduced hesl h This provides an easier to use and more stable and simple interface to the Server Loadet It is strongly recommended to use this interface The old legacy interface of the Server Loader library proceeds via three classes network common and ccif The network class has all functions to read
231. nction will serve a system of Cox FPGA and other types of nodes as per the network file that it is asked to process The system must have been reset booted and started with the loader or serverloader when not using the s option function earlier The server function will complete if all processor nodes which are served by server have executed the srv_exit function Include include hesl h Return value server will return 0 upon success and return 2 or higher upon error Use get lasterr of the hesl class for a description of the error int hesl serverloader int argc char argv E The serverloader function will reset boot configure HEART start and serve a system of C6x FPGA and other types of nodes as per the network file that it is asked to process Include include hesl h Parameters argv is an array of pointers to character strings and argc is the number of entries in the argv array Each character string should represent a Server Loader option for example r for reset for a full list of options please refer to Invoking the command line Server Loader on page 14 One character string would represent the path and name of the network file Return value serverloader will return 0 upon success and return 2 or higher upon error Use get lasterr of the hesl class for a description of the error int hesl serverloader char options char network
232. ndard Setver Loader But the Server Loader isn t used to serve instead another program takes over and communicates with the booted DSP system In the exe example the Server Loader brary is used to reset and boot the DSP system then the API is used to communicate with the booted DSP system On WIN32 the 32 bit Microsoft Visual C C is supported versions 4 5 and 6 as well as the 32 bit Borland C C For LINUX the GNU C C compiler is supported For VxWorks the GNU C C compiler is supported For RTOS32 the Microsoft Visual C C compiler is supported 54 HUNT ENGINEERING Server Loader USER MANUAL Mixing Server Loader and API applications Introduction Sometimes you want to use both the Server Loader as well as the API The Server Loader is used to boot load a network of nodes and the API to create application specific communications between a node and the host PC Sometimes you want the Server Loader to only boot load the nodes sometimes you want the Server Loader to also serve the processor nodes When the Server Loader serves a processor node it executes on the host PC stdio requests from the processor nodes For example a processor node may want to execute a printf or fwrite It forwards the request to the Server Loader running on the host PC over a fifo connection with the host PC where the function is actually executed In both cases you can run the Setver Loader with API code or application
233. ng for debug The Server Loader plugin or the Server Loader executing with the g option reports an error while trying to prepare debugging First the software will try to do a Run Free on all nodes and boot the system according to the network file The prepare for debugging phase consists of halting the free running nodes load the executable file symbols for each node and place a breakpoint at bootloader then to make each node run again Debug gt Run Error 8620 Problem doing RunFree Is the target connected The Server Loader plugin or the Server Loader executing with the g option reports an error while trying to execute RunFree Debug gt Run Free for a node in the system 191 HUNT ENGINEERING Server Loader USER MANUAL Error 8621 Problem s when preparing for debug The Server Loader plugin or the Server Loader executing with the g option reports an error while trying to prepare debugging First the software will try to do a Run Free on all nodes and boot the system according to the network file The prepare for debugging phase consists of halting the free running nodes load the executable file symbols for each node and place a breakpoint at bootloader then to make each node run again Debug gt Run Error 8622 Problem when hitting breakpoint The Server Loader plugin or the Server Loader executing with the g option reports an error while w
234. node in the network that is directly connected to the host New with version 4 0 of the Server Loader is that all DSP processors on a HEPC9 that are connected to the host can now use stdio functions You still need to declare one of the DSP processors as root The HEPC9 has 6 fifo s and if you create connections between a DSP and the host PC the Server Loader will automatically serve this node To deal with possible synchronisation issues related to having more than 1 node being served a few extra functions have been added to the Server Loader DSP library In providing host I O to the root processor a certain degree of code and necessary data structures have been kept on the host This results in a smaller more compact library that is actually required on the root node Any call to one of these host I O functions is translated and sent to the host A full description of these I O functions can be found in the section on the Run Time Library 6 HUNT ENGINEERING Server Loader USER MANUAL Using the Server Loader In running any DSP application using the Server Loader the program must be correctly compiled with the relevant libraries into the required format for loading It must then be loaded via the appropriate Server Loader utility with a network description that details the type of host platform the network topology and the name of the executable targeted for each node Compiling a TI C Application for use with th
235. node type Possible values are currently define MOD_UNKNOWN define MOD _C4X define MOD _C6X define MOD_GDIO define MOD_HOST define MOD_EMC define MOD_EM1 define MOD EM2 define MOD FPGA CH ANAUNFWNE If a node is on a remote board you may want to know what board can be used to access the remote board Function GetNodeAccessHsbId will give you the board id of the board through which the remote board s HSB can be accessed The alternative GetNodeAccessHsbSw works identically but instead of a board id gives you the board s name and board number Finally use the Get NodeId function to give you the node id of a node whose board name board switch and slot you know The return values for all functions are 0 upon success 1 upon failure and larger than 1 upon error 42 HUNT ENGINEERING Server Loader USER MANUAL Connection information Inter Board Connections To know how Inter Board Connectors are defined in the network file to be connected to other Inter Board Connectors use int FindIBCLink int fnode id int ffifo int tnode_id int tfifo Specify the node id parameter fnode_id of the Inter Board Connector node you want information on and specify the channel parameter ffifo on which you want to know what Inter Board Connector it is connected to The return values for all functions are 0 upon success 1 upon failure i e channel is not connected to anything and larger than 1 upon erro
236. node up to a broadcast but finds it cannot find back the broadcast This is an internal error Please contact support and send your network file Error 1300 HEART statement od uses module x on an undefined board with switch x Error 1301 HEART statement od uses module x on an undefined board with switch x The heron ID used in a HEART statement doesn t match any of the defined boards red switch setting Bits 7 4 of the heron ID indicate the red switch of the board that the module is inserted in Error 1302 BDCAST statement d uses module x on an undefined board with switch x The heron ID used in a BDCAST statement doesn t match any of the defined boards red switch setting Bits 7 4 of the heron ID indicate the red switch of the board that the module is inserted in Error 1304 LISTEN statement d uses module x on an undefined board with switch x The heron ID used in a HEART statement doesn t match any of the defined boards red switch setting Bits 7 4 of the heron ID indicate the red switch of the board that the module is inserted in Error 1305 HEART statement od uses module x on an undefined board with switch x Error 1306 HEART statement od uses module x on an undefined board with switch x The heron ID used in a HEART statement doesn t match any of the defined boards red switch setting Bits 7 4 of the heron ID indicate the red switch of the board that the module is inserted in Error 1307
237. normal x AN Error 0078 Line d Invalid Code Composer node id s for node s The parser expected to find a Code Composer Studio id after parsing C6 lt n gt lt nodename gt lt nodetype gt in a node statement but found a text string instead C6 0 mynode normal x Error 0079 Line d Expected heron id in C6 statement The parser reached the end of file after processing C6 lt n gt lt nodename gt lt type gt lt ccid gt in a node statement A heron id was expected C6 0 mynode normal 0 Error 0080 Line d Node s uses invalid heron id s The parser expected to find a heron id a decimal or hexidecimal number after parsing C6 lt n gt lt nodename gt lt nodetype gt lt ccid gt in a node statement but found a text string instead Precede a hexidecimal number with Ox C6 0 mynode normal 0 xxxxx Error 0081 Line d Node s uses incorrect heron id 0x x Bits 0 3 must be slot 1 2 3 or 4 The parser has found and parsed a heron id after parsing C6 lt n gt lt nodename gt lt nodetype gt lt ccid gt lt heronid gt in a node statement but the heron id is not a valid number Bits 7 6 5 4 identify the board switch of the board the module in on and bits 3 2 1 0 identify the slot As valid slots for C6 nodes are 1 2 3 or 4 a heron id with bits 3 2 1 0 set to anything else is invalid C6 0 mynode normal 0 7 Error 0082 Line d Expected out filena
238. nteger Argument should be a pointer to unsigned int x Matches a hexadecimal integer with a format such as that used by the strtoul function with a base of 16 The string may or may not begin with a 0x or OX The argument should be a pointer to int e f g Matches a floating point number with a format such as that used by the strtod function The argument should be a pointer to a floating point variable S Matches a character string with no white space included c Matches a sequence of characters of length specified by the precision field Note the c specifier does not skip white space This specifier includes all characters up to the character The characters between the brackets form a scan set The specifier matches a sequence of characters where all the characters are members of the scan set p Matches a pointer value of the format output by the p specifier in the printf function The argument should be a pointer to a pointer to void N The argument should be a pointer to an integer variable to which is written the number of characters read so far by this call to fscanf Matches a character No argument is used If the function encounters an end of file or if an error occurs before any conversion is done the function returns EOF Otherwise the function returns the number of input items successfully converted and stored fseek int fseek FILE stream long offset int origin
239. ntf SL reports error d n r printf errstr return r Loader functions The loader functions are very similar to the serverloader functions The only difference is that they will not execute the server part of the Server Loader even if you specify the server option s There are 4 shapes similar to the serverloader shapes int loader int argc char argv int loader char options char network int loader HE HANDLE uDevice int n int argc char argv int loader HE HANDLE uDevice int n char options char network Example int main int argc char argv we int ie char errstr hesl sl r sl loader rlv network if r errstr sl getlasterr if errstr errstr 0 0 printf SL reports error d n r printf errstr return r Server function The server function can be used in conjunction with the loader function or with the 37 HUNT ENGINEERING Server Loader USER MANUAL serverloader function if used without the server option s This may be useful if you need to do some programming in between the loader and server stage for example set up threads that are going to communicate with DSP or FPGA nodes The server part of the Server Loader will examine all HEART statements and see which C6x nodes are connected to a host including those that are connected to a host via Inter Board Conne
240. o open any device specifically for use by the Server Loader The uDevice list allows you to tell the Server Loader what devices you happen to have open the Server Loader will then use handles you provide instead of trying to open a device If a device is not listed the Server Loader will open the device itself Parameter n is the number of open devices handles that you have listed in the array that uDevice points at Return value loader will return 0 upon success and return 2 or higher upon error Use get lasterr of the hesl class for a description of the error int hes1 loader HE HANDLE uDevice int n char options char network ji The loader function will reset boot configure HEART and start but not serve a system of C6x FPGA and other types of nodes as per the network file that it is asked to process Include Hinclude hesl h Parameters options is a pointer to a character string that holds Server Loader options for example rlv for a full list of options please refer to Invoking the command line Server Loader on page 14 option s will be ignored by this function though Parameter network is a pointer to a character string that represents the path and name of the network file Parameter uDevice is a pointer to an array of open device handles You don t need to open any device specifically for use by the Server Loader The uDevice list allows you to tell the Server Loader what
241. ol HSB between boards it was found that the slave board is not of type BD API Only boards of type BD APY can be defined as master and slave boards Error 2156 Board s has no IBC Inter Board Module When trying to configure board control HSB between boards it was found that the slave board has no inter board connector module defined Error 2157 Can t find switch setting of board s Internal error When trying to configure board control HSB between boards it was not possible to retrieve the red switch setting of the slave board Please contact support and send your network file Error 2159 Don t know how to program IBC on slave board od An EMIC EM1 or an unknown inter board connector module was used to connect master and slave boards Only boards with an EM2 inter board connector module can be used to define master and slave boards Error 2175 Board s is not of type API When trying to configure board control HSB between boards it was found that the master board is not of type BD API Only boards of type BD APPT can be defined as master and slave boards Error 2176 Board s is not an HEPC9 When trying to configure board control HSB between boards it was found that the master board is an HEPC9 or HECPCI9 Only HEPC9 or HECPCI9 boards can be defined as master and slave boards Error 2177 Board s has no IBC Inter Board Module When trying to configure board control HSB between
242. on the EM1C inter board connector module The EM1C has only one fifo fifo 0 Error 1661 A HEART statement uses a non existing EM1 fifo od An EM1 node used in a HEART statement uses a fifo number that doesn t exist on the EM1 inter board connector module The EM1 has only one fifo fifo 0 Error 1662 A HEART statement uses a non existing EM2 fifo od An EM2 node used in a HEART statement uses a fifo number that doesn t exist on the EM2 inter board connector module The EM2 has 6 fifos fifo 0 to 5 Error 1663 A HEART statement uses a non existing IBC fifo d Keyword IBC is no longer used please use EM1C EM1 or EM2 Error 1670 Board definitions d and od are identical os d The same board is defined twice Please define each board just once For example BD API heb2a 0 0 BD API heb2a 0 0 One BD API heb2a 0 0 definition is enough Error 1700 Parameter bdid is NULL in GetBoardId The third parameter supplied to GetBoardId is a NULL pointer 160 HUNT ENGINEERING Server Loader USER MANUAL Error 1701 No board with switch od found in network file The boardswitch specified in the second parameter of GetBoardId doesn t match any of the defined boards in the network file Error 1705 Parameter bdname is NULL in GetBoardName The second parameter supplied to GetBoardName is a NULL pointer Error 1706 No board with id d found Error 1707 Cannot find ROOT node on board with id d Error
243. on units that have been compiled for a different memory model will result in the application failing Therefore ensure that when building each individual executable output the library that is used matches the compiler options that were used for the memory model The following table indicates which libraries correspond with which models C62xx Stand alone Library Memory Model stdr6 2s lib Reduced library compiled for the small memory model stdr6210 lib Reduced library compiled for the ml0 memory model stdr6211 lib Reduced library compiled for the ml1 memory model 20 HUNT ENGINEERING Server Loader USER MANUAL stdr6212 1lib Reduced library compiled for the ml2 memory model stdr6213 lib Reduced library compiled for the ml3 memory model C67xx Stand alone Library Memory Model stdr67s lib Reduced library compiled for the small memory model stdr6710 lib Reduced library compiled for the ml0 memory model stdr6711 lib Reduced library compiled for the ml1 memory model stdr6712 lib Reduced library compiled for the m12 memory model stdr6713 lib Reduced library compiled for the ml3 memory model C4x Stand alone Library Memory Model stdr_br lib Reduced library big memory model register arguments stdr_bs lib Reduced library big memory model stack arguments stdr_sr lib Reduced library small memory model register arguments stdr_ss lib Reduced library small memory model stack arguments Concurrency issues HEPC9 only With the HEPC9 no
244. onnection should carry the control signals For example BD API hep9a 0 0 BD API hep9a 1 0 slave BDLINK 00 1 0 BDLINK 0111 Here there are two inter board connections between hep9a 0 0 and hep9a 0 1 You must choose which of the two is to carry the control signals To select the first BDLINK connection for the control signals use BD API hep9a 0 0 BD API hep9a 1 0 slave BDLINK 0010 BDLINK 0111 NORESET NOHSB Error 1422 Board God cannot be a slave as there are no BDCONN BDLINK connections to it A board can be a slave only if it is connected via inter board connector modules such as EM2 or EM1 but not the EM1 C to another board Access to a slave board s reset HSB and fifo s will be via a master board Error 1423 Out of memory while trying to find master slave path between boards Memory allocation failed when trying to allocate enough space to store a master slave path of boards Error 1424 Cannot find a master board to support slave board od there are no BDCONN BDLINK connections for reset towards a master board A slave board must have a master board It is possible to have multiple slaves and one master but without a master board slave boards cannot be accessed HeartConf has not found a master board to go with the slave board indicated Error 1425 There are d reset paths from master board od to remote board d Please use NORESET to specify what links not to use for reset Error 1
245. ons from the nodes to their inter board connectors EM1C EM1 or EM2 Please contact support and send your network file Error 1206 HEART routing Cannot place HEART statements d and d HeartConf has tried to fit your connections but found there were not enough resoutces timeslots to place a HEART statement HEART oodea 0 nodeb 0 6 149 HUNT ENGINEERING Server Loader USER MANUAL HEART nodea 1 nodec 0 1 In the above the nodea to nodeb connections takes 6 timeslots There is no timeslot left for use with the HEART statement for nodea fifo 1 Error 1207 HEART routing Unbroken HEART statement line d simplex This is an internal error HEART connections from one board to another board are supposed to have been broken up to one board only connections from the nodes to their inter board connectors EM1C EM1 or EM2 Please contact support and send your network file Error 1208 HEART routing Cannot place HEART statement d HeartConf has tried to fit your connections but found there were not enough resoutces timeslots to place a HEART statement HEART nodea 0 nodeb 0 6 HEART nodea 1 nodec 0 1 In the above the nodea to nodeb connections takes 6 timeslots There is no timeslot left for use with the HEART statement for the nodea to nodec connection Error 1209 HEART routing Internal error LISTEN statement od listens to an unknown broadcast index od HeartConf has tried to connect your LISTENing
246. ons passed to the Server Loader it was found that an unsupported IRQ number was used supported values are 10 11 12 and 15 tlsvql4 Error 8007 Parsing Options Invalid IRQ number c c after q option When parsing options passed to the Server Loader it was found that an unsupported IRQ number was used supported values are 10 11 12 and 15 tlsvq4 Error 8008 Parsing Options oc Unknown Option When parsing options passed to the Server Loader it was found that an unknown option was used tlsvz AN Error 8009 Parsing Options s or s Confusion in name of network file When parsing options passed to the Server Loader it was found that the network file c39 was specified two times or more Note that all arguments without 7 in front are interpreted as network filenames Error 8010 Parsing Options No network file specified When parsing options passed to the Server Loader no network file was found Arguments that don t start with in front are interpreted as network files Error 8011 Parsing Options Invalid number oc c after y option When parsing options passed to the Server Loader it was found that the y parameter was used with an unsupported value supported are 0 1 and 2 tlsvy4 Error 8012 Parsing Options No network file specified When parsing options passed to the Server Loader it was found that the p parameter was used without any letter or with an unsupp
247. or 3944 Error reading ELF file s os error Yod There was an error reading the PowerPC executable file as specified The function used was the standard C fread and the os error shown is errno Error 3950 Error seeking ELF file s sh offset Yod os error d There was an error seeking the PowerPC executable file as specified The function used was the standard C fseek and the os error shown is errno Error 3951 Unable to allocate memory Dad bytes while reading ELF file There was an error trying to allocate temporary memory The function used was the standard C malloc Error 3952 Error reading ELF file s os error Yod There was an error reading the PowerPC executable file as specified The function used was the standard C fread and the os error shown is errno Error 3960 Error seeking ELF file s sh offset Yod os error od There was an error seeking the PowerPC executable file as specified The function used was the standard C fseek and the os error shown is errno Error 3961 Unable to allocate memory d bytes while reading ELF file There was an error trying to allocate temporary memory The function used was the standard C malloc Error 3962 Error reading ELF file s os error Yod There was an error reading the PowerPC executable file as specified The function used was the standard C fread and the os error shown is errno
248. or just for VxWorks Once you have a SDP install for Windows you can add a VxWorks installation using the CD setup program But when un installing both Windows and VxWorks installation files will be removed 11 HUNT ENGINEERING Server Loader USER MANUAL Installation under RTOS 32 The installation program on the CD can create an installation for Windows with RTOS 32 attached to it You can use the CD setup program to install SDP which includes the Server Loader for both Windows and RTOS 32 at the same time But you can also install just for Windows or just for RTOS 32 Once you have a SDP install for Windows you can add a RTOS 32 installation using the CD setup program But when un installing both Windows and RTOS 32 installation files will be removed The Server Loader is delivered in both executable and library format The library format ttossLlib is located in hesl lib rtos32 of your API amp Tools installation The executable format sl rtb or sl exe is located in hesl bin rtos32 Completed Installation After successful installation the following sub directories can be seen in your API amp Tools installation directory default c heapi hesl bin Contains the Server Loader executables hesl inc Contains headers files e g stdioc60 h hesl lib Contains the run time libraries hesl etc Contains examples eeprom and idrom sources hesl sre LINUX only Server Loader executables and run time library
249. ork file O is returned and pdname is set to the board name The function will return 2 or higher if no such board is found and upon error Finally note that this function will only work with BD APT definitions in the network file References to board definitions that are BD but not BD API will result in an error being returned 70 HUNT ENGINEERING Server Loader USER MANUAL Example BD API hep9a 0 0 BD API hep8a 1 0 With the above network file definitions GetBoardName 0 bname will return 0 and hep9a will be written to bname GetBoardName 1 bname will return 0 and hep8a will be written to bname And GetBoardName 2 bname will return an error because there s no third BD API statement Include include hesl h Return value GetBoardId will return a value of 0 if a board with board index bdno is defined in the network file odname is then set to that BD API definition s board name In all other cases a value of 2 or higher is returned int hesl GetBoardRstAccessId int bdid int id GetBoardRstAccessId is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file When using certain inter board modules such as the EM2 reset connections may be created between mult
250. orted letter supported is o only Use po only po PROM only no board accesses will be done tlsvp 189 HUNT ENGINEERING Server Loader USER MANUAL AN Error 8013 Sorry can t handle PROM filenames larger than 1024 bytes b0 1 2 3 option When parsing options passed to the Server Loader HeartConf it was found that the b parameter was used with a PROM filename longer than 1024 bytes Error 8070 Maximum number of scan directories is d With the i option you have specified more directories than the Server Loader HeartConf can handle The maximum number is 16 directories Error 8071 Failed to allocate memory for include directory storage When parsing A options passed to the Server Loader HeartConf an out of memoty error was encountered while trying to allocate memory to store a directory The function used was strdup nn Error 8081 Parsing Options Expected a number after v When parsing options passed to HeartConf it was found that no number was eo AH specified after v EN N Error 8082 Parsing Options No network file specified When parsing options passed to Heart ont it was found that the p parameter was used without any letter or with an unsupported letter supported is o only Use po only po PROM only no board accesses will be done fvp AN Error 8088 Parsing Options c Unknown Option n When parsing options passed
251. ot a valid node Internal error When searching through the list of nodes a node with an unknown node type was found Please contact support and send your network file Error 1795 Parameter del is NULL in GetNodeHsbAccessSw Error 1795 Parameter dev is NULL in GetNodeRstAccessSw The second parameter supplied to GetNodeHsbAccessSw or GetNodeRstAccessSw is a NULL pointer Error 1796 Parameter bdsw is NULL in GetNodeHsbAccessSw Error 1796 Parameter bdsw is NULL in GetNodeRstAccessSw The third parameter supplied to GetNodeHsbAccessSw or GetNodeRstAccessSw is a NULL pointer Error 1797 Internal Error node od was found to be NULL nodes d Internal error When searching through the list of nodes a node pointing to NULL was found Please contact support and send your network file Error 1798 Node d is not a valid node Internal error When searching through the list of nodes a node with an unknown node type was found Please contact support and send your network file Error 2000 Failed to reset s Error 2001 Failed to reset s Error 2002 Failed to reset s Error 2003 Failed to reset s Error 2004 Failed to reset s Error 2005 Failed to reset s There was an error when trying to reset the specified board The function used is the API function HeReset Error 2100 Board s is not an API type board When processing BDLINK BDCONN connections it was found that a board used was not of type BD A
252. ot jumpers set on GDIO and HERON IO modules loose any meaning Any necessary GDIO or HERON IO links must be created using HEART connection statements This option to accommodate Code Composer Studio 2 0 CCS 2 0 Executables created by CCS 2 0 may be deposited in a release or debug directory By default the Server Loader adds a debug directory to the list of paths that should be searched to find an executable By using the t option you tell the Server Loader to look in the release directory instead of the debug directory instead for a DSP processor executable out file 15 HUNT ENGINEERING Server Loader USER MANUAL The waitperiod in milli seconds that the Server Loader should wait after issuing a write transfer before assuming it has timed out The default value is 0 which means to wait forever Under normal usage you would use the default value g n Start up Code Composer Studio and prepare for debugging Then n value is the number of seconds of decoupling between the Server Loader and Code Composer Studio Decoupling is simply a wait period after issuing a Code Composer Studio action The wait allows the Server Loader to de schedule and Code Composer Studio to run There is some variation between different PC s in the actual value and this allows you to alter the wait if necessary Usually the default Ce will work and you don t need to specify an n value bn Where n 0 1 2 or
253. our API amp Tools installation Legacy Class Network Interface Basics The network class is now a legacy interface and will be obsoleted in future Please use the hes class as described in earlier sections in this Chapter for new projects The network class will remain supported for some time to support existing applications The network class exports the following functions for booting serving a network int parse _input_file char filename int open void int reset void int load void int run void void serfit void int close void int verify void The parse_input_file opens a network description file This network description file is exactly the same as for the normal Server Loader Upon successful parsing 0 is returned any other value indicates some error The parse_input_file function also initialises internal structures which are used in the subsequent functions open reset e verify The open function opens the boards defined in the BD statement in the network description file Upon success 0 is returned any other value denotes some error The reset function resets the boards defined in the BD statement in the network description file Upon success 0 is returned any other value denotes some error The load function loads code onto all the processors as described in the network description file by C6 statements Upon success 0 is returned any other value denotes some error
254. ove network file definitions GetNodeRstAccessSw 0 dev amp b will return 0 hep9a will be written to dev and b will be set to 3 because reset for node MODa can be accessed via the first board listed which is hep9a 3 GetNodeRstAccessSw 1 dev amp b will also return 0 hep9a will be written to dew and b will be set to 3 because reset for node io2v2 can be accessed via board hep9a 3 GetNodeRstAccessSw 4 dev amp b will return an error because there s no node with id 4 i e there s no fifth node definition Include include hesl h Return value GetNodeHsbAccessSw will return a value of 2 or higher upon error and 0 if no error was encountered Parameters dev and bdsw will be set to the board via which HSB for node nodeid can be accessed int hesl GetNodeType int nodeid int ntype GetNodeType is an information function After a function such as loader heartconf serverloader or parse_network_file has been executed you can use this function to extract certain information from the network file 84 HUNT ENGINEERING Server Loader USER MANUAL GetNodeType will tell you what is the node type root or normal of the node with node index nodeid The node type is an integer number a list of node types is defined in hesl h MOD ROOT and MOD NORMAL Note that mote node types may be add
255. r HEART connections To know how nodes ate inter connected as defined in the network file via HEART use int FindNodeConnCount int fromid int toid int count int FindNodeConn int fromid int toid int from fifo int to fifo int idx With FindNodeConnCount you can specify two node id s Eromid and toid whose connections you wish to know and hes will tell you how many connections there are between the two nodes You can then use FindNodeConn to find out how the two nodes are connected Supply node id parameters fromid and toid and hes will give you the first node s outgoing fifo i e parameter from_fifo that is connected to the other node s incoming fifo parameter to_fifo There may be multiple connections between them hence the idx parameter Note that a connection may go via Inter Board Connectors Windows and other non console programs When using the verbose C vi option progress information is printed to stdout Similarly the Server part of the Server Loader works as a console program i e printf requests are printed out to stdout gets requests are read from stdin For Windows applications and other non console programs you could write your own Server part and use only the loader to boot load your network But if you would really like to use the standard Server Loadetr there s also the option to redirect Server functions The Server Loader allows you to replace the functions it uses to p
256. r SetUseSlotSwitch int r Similar to I lt path gt option Set network file name Similar to r option Similar to 1l option Not available as option Similar to s option Similar to v option Similar to g option Similar to g lt r gt option Similar to k option Similar to k lt r gt option Similar to d option similar to p option Similar to f option Similar to x option Similar to w option Similar to a option Similar to j option 49 HUNT ENGINEERING Server Loader USER MANUAL Example The essence of using the network parameters is in the following code snippet We assume that the command line is similar to the Server Loader include lt stdio h gt include lt stdlib h gt include lt string h gt include heapi h include network h int main int argc char argv int 04 network net for i 1 i lt argc i if stremp argv i r 0 net SetResetSwitch TRUE if stremp argv i 1 0 net SetLoadSwitch TRUE 0 if stremp argv i s 0 net SetServeSwitch TRUE E legacy Class Common Interface basics The common class is now a legacy interface and will be obsoleted in future Please use the hes class as described in earlier sections in this Chapter for new projects The common class will remain supported for some time to support existing applications Class common is the base class for network and for most of the other classes used in
257. r has completed other threads tasks may start to communicate 27 HUNT ENGINEERING Server Loader USER MANUAL HETFLASH Using the HETFLASH The HETFLASH is a TIM 40 module with up to 8 Mbytes of flash memory It has no on module processor It serves to boot a stand alone C4x system With version 3 3 of the Server Loader you can now use the HETFLASH To program the HETEFLASH with a Server Loader program you must change your network file Also for the actual programming you need to put the HETFLASH in slot 1 of your C4x board After programming it you can remove it and put the HETFLASH at its designated slot Preparing a Server Loader program for HETFLASH The first step in preparing a Server Loader program for programming into a HETFLASH is to develop the program using the Server Loader and or Code Composer Once you have finished the actual development and have a program you re happy with it s time to think about the HETFLASH The HETFLASH has a BOOTEN jumper which when fitted will send the contents of its memory over comport 3 to the neighbouring C4x Therefore the data that we prepare to put into the HETFLASH must essentially be a boot stream for the whole system The C4x that the HETFLASH is connected to via a comport is thus the ROOT processor To prepare a Server Loader application you need to do the following Find out what the global bus register GBCR value and local bus control register LBCR values are for a
258. r PROM buffer board s Error 2503 Cannot allocate 1024 bytes for PROM file buffer board s Out of memory error The function used is malloc Error 2504 Unable to open s for writing errno 0x x Error 2505 Unable to open s for writing errno 0x x Error 2506 Unable to open s for writing errno 0x x Error 2507 Unable to open s for writing errno 0x x When trying to open a file for writing with the specified name an error occurred The errno displayed at the end is the errno of the standard C library the function used is the fopen function Error 2508 Unknown PROM selection d A bx option with an x value other than 0 1 2 or 3 was used Such errors should have been caught at an earlier stage and this error probably indicates an internal error Please contact support and send your network file 169 HUNT ENGINEERING Server Loader USER MANUAL Error 2520 Unable to open s for writing errno 0x x Error 2521 Unable to open s for writing errno 0x x When trying to open a file for writing with the specified name an error occurred The errno displayed at the end is the errno of the standard C library the function used is the fopen function Error 2522 Too many HEART messages Cannot store all of them into VHDL RAM With Virtex devices HEART configuration data is stored in BLOCK RAM with a size of 1024 bytes But the total amount of HEA
259. r the VxWorks server rtossl options network for the RTOS 32 server where network is the name of the network description file The four forms are the same apart from the name of the Server Loader program The network description file is an ASCII file that tells the Server Loader which program to load onto what node a node being e g a C6x or C4x processor The following line would invoke the Server Loader with the network description file network win32sl i rls network fot the Win32 bit server linuxsl i rls network for the LINUX server 14 HUNT ENGINEERING Server Loader USER MANUAL sp vxwsl i rls network for the VxWorks server With RTOS 32 the command line would be in a configuration file as follows CommandLine a rtossl exe i rls network Command Line Options SE Reset all boards and processors in the network 1 Load code onto all processors defined in the network file s Serve stdio requests from the root processor v n Run in verbose mode Parameter n specifies a more detailed verbose level Currently implemented is 2 v 2 which shows routing tables used during the loading phase Also implemented is 4 v 4 showing the packet header returned from the module by eeprom62 67 out c n Show selected HERON module information C6x or IDROM information C4x The n value specifies a larger selection Currently implemented is 2 c 2 which will displ
260. r was expected BDLINK 0 AN Error 0343 Line d BDLINK statement uses invalid fifo number s The parser expected to find a fifo number after processing BDLINK lt bdnumber gt in a BDLINK or BDPATH statement but found a text string instead BDLINK 0 xxxx AN Error 0344 Line d BDLINK statement uses invalid fifo number od The parser successfully found and parsed a fifo number after processing BDLINK 130 HUNT ENGINEERING Server Loader USER MANUAL lt bdnumber gt in a BDLINK or BDPATH statement but the fifo number is not a valid fifo number BDLINK 0 8 AN The BDLINK or BDPATH definition specifies how two boards are connected via an EM2 EM1 or EM1c module so really the fifo number identifies the channel number used on the EM module Error 0345 Line d Expected board number in BDLINK statement The parser reached the end of file after processing BDLINK lt bdnumber gt lt fifo gt in a BDLINK or BDPATH statement A board number was expected BDLINK 0 0 AN Error 0346 Line d BDLINK statement uses undefined board s The parser successfully found and parsed a board number after processing BDLINK lt bdnumber gt lt fifo gt in a BDLINK or BDPATH statement but the board number is not a valid number The board number relates to board definitions the first board definition defines board 0 the second board definition defines board 1 and so on BD API hep9a 5 0 this is bo
261. r will also not serve the module in slot 4 Although there is a bi directional fifo connection between the module and the host module fourth is not a processor module and will thus not be served by the Server Loader 56 HUNT ENGINEERING Server Loader USER MANUAL NOSERVE keyword Now consider the case that you want to run the Server Loader simultaneously with an API application that communicates with a processor node that is served by the Server Loader Let s assume that the API application communicates with the processor module both ways So your network file would be something like node declarations pcif 0 host normal 0x05 c6 0 first root 1 0x01 modl out fifo connections heart host 0 first 0 1 heart first 0 host 0 1 heart host 1 first 1 1 heart first 1 host 1 1 The problem is that we don t know which of the two bi directional fifo connections will be used by the Server Loader The Server Loader will effectively at random choose one of the two bi directional connections to serve processor node first The solution is offered by the NOSERVE keyword This reserved keyword tells the Server Loader to not use a fifo connection to serve a node For example node declarations pcif 0 host normal 0x05 c6 0 first root 1 0x01 modl out fifo connections he
262. rary compiled for the ml0 memory model stio6711 lib Standard library compiled for the ml1 memory model stio6712 lib Standard library compiled for the ml2 memory model stio6713 1ib Standard library compiled for the ml3 memory model The following table indicates which C4x libraries correspond with which models I O Library for C4x Memory Model and Argument Passing Method stdio_br lib Standard library compiled with the big memory model option and register argument passing stdio_bs lib Standard library compiled with the big memory model option and stack argument passing stdio_sr lib Standard library compiled with the small memory model option and with register argument passing stdio_ss lib Standard library compiled with the small memory model option and with stack argument passing The Stand alone Library for normal nodes The stand alone library is available in several versions These libraries are located in the lib directory With the TI compiler tools there are a number of memory models that can be used Other than the small memory model there is a m10 ml1 m1l2 and m13 memory model In the small memory model both code and data are expected to be within a 32 kbyte area If this is not the case you must use one of the m1 options The C4x TI compiler uses 4 different models with 2 parameters big and small memory model and register stack parameter passing It is important to note that linking an application with compilati
263. read semaphore for board od s The Server Loadet tried to initialise a RTOS32 semaphore but encountered an error The function used was RTKCreateSemaphore Error 7329 Cannot start thread for board d s The Server Loader encountered an error when trying a start a thread that was meant to serve one node The function used was RTKRTLCreateThread Hy Error 8001 Parsing Options Expected a number after v When parsing options passed to the Server Loader it was found that no number was ec AH specified after v tlsv N Error 8002 Parsing Options Expected a number after c When parsing options passed to the Server Loader it was found that no number was specified after c tlsve N Error 8003 Parsing Options Expected a number after k When parsing options passed to the Server Loader it was found that no number was specified after k tlsvk Error 8004 Parsing Options Expected a number after w When parsing options passed to the Server Loader it was found that no number was 188 HUNT ENGINEERING Server Loader USER MANUAL CC ES EH specified after w tlsvw AN Error 8005 Parsing Options Expected a number after g When parsing options passed to the Server Loader it was found that no number was DEE specified after g tlsvg N Error 8006 Parsing Options Invalid IRQ number oc c after q option When parsing opti
264. reakpoint routine The routine does nothing it simply waits until all processors have hit their respective breakpoints Finally the StartDebugging routine is called This simple does 2 single steps which steps us out of the bootloader routine to the very first C code line after boot loader Now close the connection to Code Composer Studio by issuing a call to CoUninitialize The system is now ready for debugging Legacy Class Ccif Interface parameters The ccif class is now a legacy interface and will be obsoleted in future Please use the hes class as described in earlier sections in this Chapter for new projects The ccif class will remain supported for some time to support existing applications There are no parameters for the ccif class Example supporting the g option The essence of supporting the g option within your own Microsoft Visual C C application is in the following code snippet if met GetDebugSwitch if user requested to use g Find out the path to the network file We will use spath to set Code Composer s search directory if description _filename 1 strcpy spath description filename Mutilate spath else GetCurrentDirectory 256 spath Start up Code composer if cc StartCodeComposer spath return 0 and do a RunFree if cc RunFree gt 0 return 0 We need to give CC some time here to release the processors
265. rint fread fwrite by other functions functions that you have written yourself To replace the verbose print option you can use void set_user_ vprint USER_VBSFUNC fie where the function prototype is defined as follows typedef void USER_VBSFUNC char str Example void myprint char str d int main int argc char arvg print_to_window somehWnd str 43 HUNT ENGINEERING Server Loader USER MANUAL hesl sl int r sl set_user_vprint myprint r sl loader rlv network The print_to_window function would be a function you defined yourself writing text to a window in your Windows application Similarly most functions used by the Server to execute Server functions can be replaced int set user fie USER_SRVFUNC fie int whichfie The whichfie parameter identifies the Server function you wish to replace define USER SRV FCLOSE oxa0 define USER SRV FREAD Oxal define USER_SRV_FWRITE Oxa2 define USER SRV FUNGETC 0xa3 define USER SRV FGETS 0xa4 define USER SRV FPUTS 0xa5 define USER SRV FFLUSH 0xa6 define USER SRV FSEEK 0xa7 define USER SRV FTELL Oxas define USER_SRV_FEOF Dan define USER_SRV_FERROR Daa The function prototype is defined as typedef unsigned long USER_SRVFUNC const SRVFIEPARAMS The Server will pass a pointer to a structure that holds relevant information regarding the serve request The structure is defined at time of writing as
266. rks well you need to incorporate the bootloader function in all programs of the processors in the network You must execute the boot loader function before executing the config off function Releasing the config line before the bootloader is run might confuse the bootloader since this routine is looking at all FIFOs to see what other processors in the network are sending boot packets Example code The main routine of each processor s program should look like void main Load other processors bootloader Now it s OK to release the config line config off Actual program DSP BIOS and bootloader In DSP BIOS applications the best place for the bootloader call is the main routine again The main routine under DSP BIOS is actually a kind of start up routine that allows you to run initialisation routines while DSP BIOS isn t running yet formally DSP BIOS has been initialised but hardware and software interrupts ate disabled This allows us to boot processors further on in the network without DSP BIOS threads competing and perhaps accidentally booting a neighbouring processor It would also be possible to use a call to bootloader in a thread task but then you have to ensure that bootloader is the only instance that can access other processors over the FIFO and you must ensure that no other thread task tries to access a neighbouring processor at the same time Only when bootloade
267. rn 0 hep9a will be written to dev and bdsw will be set to 0 GetNodeBoardSw 2 dev amp bdid will return 0 as well hep9a will be written to dev and parameter bdsw will be set to 8 And GetNodeBoardSw 3 dev amp bdid will return an error because there s no fourth node definition Include include hesl h Return value Get NodeBoardSw will return a value of 0 if the node identified by node index nodeid is defined in the network file the board name is then written to dev and bdsw is set to the board index of the board the node is on The function will return a value of 2 or higher if nodeid is an invalid node id and upon error int hesl GetNodeCount void 75 HUNT ENGINEERING Server Loader USER MANUAL GetNodeCount is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file GetNodeCount returns the number of nodes defined in a network file Examples of node definitions ate C6 FPGA EM2 GDIO and PCIF But note that this is not a full list and in future more node types may be added Example c6 0 MODa ROOT 1 0x01 modulel out pcif 0 hosta normal 0x05 em2 0 em2a normal 0x06 With the above network file definitions GetNodeCount will return 3 Includ
268. rnal error There is no master board for the specified board first parameter of GetBoardHsbAccessId or GetBoardRstAccessId This is an internal error as slave boards without a master board should be been caught when the network file gets parsed and processed Please contact support and send the network file Error 1735 Board od is not a BD API board 162 HUNT ENGINEERING Server Loader USER MANUAL GetBoardHsbAccessId or GetBoardRstAccessId can be used only with boards of type BD API Error 1736 Board od is not a valid board There is no board in the list of defined boards with index specified first parameter of GetBoardHsbAccessId or GetBoardRstAccesslId The index must be between 0 and the number of boards defined in the network file minus one Error 1750 Parameter del is NULL in GetNodeld The first parameter supplied to GetNodeld is a NULL pointer Error 1751 Parameter node_id is NULL in GetNodeld The fourth parameter supplied to GetNodeld is a NULL pointer Error 1752 Internal Error node d was found to be NULL nodes d Internal error When searching through the list of nodes a node pointing to NULL was found Please contact support and send your network file Error 1754 No node found for board s od slot d After searching the list of defined nodes in the network no node was found for the board specified in parameters one and two in the slot specified by parameter three Error 1755 Parame
269. rogram that shows how to run a 2 processor network 3heron Contains an example program that shows how to run a 3 processor network 2boards Contains examples programs that show how you could use multiple boards that are connected via Inter Board Connectors sl_api Contains 2 sample directories that demonstrate how API and Server Loader can be combined successfully easily and smoothly batch Use Server Loader to load network use API to custom serve network exe Use Server Loader Host Library to both load and custom serve network parallel Use the Setrver Loader to load network then serve 1 or more serve connections Start a different DOS box to run your own API host program on 1 or mote free node host connections threads Use the Server Loader to load network then serve 1 or more node host connections Start a separate thread to access free host node connections Mysl contains an example of using the Host libraries to make your own version of the Server Loader program Running the C6x Examples The examples are supplied without executable code This means that you must first create a new Code Composer Studio project and build an executable out file This is easily done with HUNT ENGINEERING s Create New HERON API Project plugin It is available from the Tools menu entry in a Code Composer Studio processor window With the stdtest 2heron and 3heron examples the example can be run using w32 bat w3
270. ronment The functions exit and system are normally available through the ANSI C general utilities stdlib header These are provided by the functions srv_exit and srv_system respectively These functions should be used in place of the more common exit and system functions srv_exit stop the program srv_system execute an operating system command Network Loading Functions boot loader ensures loading of nodes below this node in the network Remarks Concerning fread and fwrite C6x version 3 1 and earlier C4x all versions In order to stay compatible with the host file formats the following mechanism has been adopted for both routines fread and fwrite fread void ptr size_t size size t nitems FILE stream fwrite void ptr size_t size size t nitems FILE stream The size parameter above indicates the data size in bytes Be careful concerning the use of sizeof The example below demonstrates how fwrite would be used to write 32 C6x wotds each 32 bits in size to a stream include stdioC 6 x h FILE fpr int data 32 fwrite data sizeof int 32 fpr The above remarks apply to the old server protocol which is used in Server Loader 3 1 or earlier and is still used in Server Loader 3 2 and above for C4x support However in Server Loader 3 2 a new protocol has been introduced for C6x processors that is faster and simpler One of the reasons behind this is that the C4x has a dword 32 bit based ad
271. ropagate Reset BDCONN em2a 0 em2b 0 BDCONN em2a 1 em2b 1 noreset You also need to be careful with more than 2 boards as you can create loops even while not using multiple links between any two boards For example BDCONN em2a 0 em2b 0 BDCONN em2b 0 em2c 0 BDCONN em2c 1 em2a 1 Here you can see that Reset propagates from em2a to em2b to em2c But then Reset propagates back to em2a and this is not allowed Again use the noreset keyword to break the Reset propagation loop Error 0340 Line Yod Expected board number in BDLINK statement The parser reached the end of file after processing BDLINK or BDPATH in a BDLINK or BDPATH statement A board number was expected BDLINK AN Error 0341 Line d BDLINK statement uses undefined board s The parser successfully found and parsed a board number after processing BDLINK lt bdnumber gt in a BDLINK or BDPATH statement but the board number is not a valid number The board number relates to the board definition the first board definition defines board 0 the second board definition defines board 1 and so on BD API hep9a 5 0 this is board 0 BD API hep9a 2 0 this is board 1 BDLINK 5 In the above there is no board 5 Specify board 0 or board 1 only Error 0342 Line d Expected fifo number in BDLINK statement The parser reached the end of file after processing BDLINK lt bdnumber gt in a BDLINK or BDPATH statement A fifo numbe
272. ror 5006 Internal error No node information BDCAST statement d Internal error A node pointer used in a BDCAST statement points to NULL Please contact support and send your network file Error 5007 Internal error No node information LISTEN statement d Internal error A node pointer used in a LISTEN statement points to NULL Please contact support and send your network file Error 5008 Can t find switch setting of board od Internal error When trying to find the red switch setting of a board used by a node an error occurred Please contact support and send your network file Error 5050 Can t find switch setting of board od Error 5051 Can t find switch setting of board od Internal error When trying to find the red switch setting of a valid board an error occurred Please contact support and send your network file Error 5052 Don t know how to program non blocking fifo for node s Error 5053 Don t know how to program non blocking fifo for node s Internal error The Server Loader or HeartConf cannot find the programming data to program non blocking mode Please contact support and send your network file Error 5100 Internal error Board is a NULL pointer Board index od boards d Internal error The board pointer of a valid board points to NULL Please contact support and send your network file Error 5101 An HEPC9 must be specified as an API board Direct access is not supported Internal
273. rror 0165 Line d Node s uses invalid node type s The parser expected to find a node type ROOT or NORMAL after parsing EMx lt n gt lt nodename gt x 2 1 1c in a node statement but found a text string that is not a valid node type i e the type string is not ROOT and is not NORMAL EM2 0 mynode xxxx Error 0166 Line od Expected heron id in EM1C EM1 EM2 statement The parser reached the end of file after processing EMx lt n gt lt nodename gt lt type gt x 2 1 1c in a node statement A heron id was expected EM2 0 mynode normal nw Error 0167 Line d Node s uses invalid heron id s The parser expected to find a heron id a decimal or hexidecimal number after parsing EMx lt n gt lt nodename gt lt nodetype gt x 2 1 1c in a node statement but found a text string instead Precede a hexidecimal number with Ox EM2 0 mynode normal xxxxx Error 0168 Line d Node s uses invalid heron id s nIBC slot number is 6 so its heron id must be 0x06 0x16 0x26 etc The parser has found and parsed a heron id after parsing EMx lt n gt lt nodename gt lt nodetype gt lt heronid gt x 2 1 1c in a node statement but the heron id is not a valid number Bits 7 6 5 4 identify the board switch of the board the module in on and bits 3 2 1 0 identify the slot A valid slot for inter board modules is 6 only a heron id with bits 3 2 1 0 set to anythin
274. rver Loader in a separate DOS box and boot the processors bypassing Code Composer Now you would return to Code Composer and halt all processors The processors were made to spin in a small loop ruled by a volatile variable Change the value of the variable to 0 and you could jump out of the loop Do this for all processors and you re ready to debug With Code Composer Studio this all disappears you only need to use the plug in or use the g option with the standard command line Server Loader This will do all of the above for you automatically and will prepare everything for debugging a Server Loader program There is a separate document that describes the details of the Server Loader plug in Here we only focus on some issues that are not purely plug in related Plug In Parameters The plug in implements several of the Server Loader command line switches both in the front end and in the Property Page From the front end Stop L MV Reset M Load V Serve V Verbose V Halt at bootloader Use out files Release Debug Source J Skip FPGA Network file fe Soemhunt apil S hesl etc c6s examples stdtest network Browse Edit a Hunt Engineering Server Loader Plug In v4 06 09 2002 Input Server Loader Plug In command line S L Server Loader plug in r Reset radio box 1 Load radio box 25 HUNT ENGINEERING Server Loader USER MANUAL sS Serve radio box v Verbose radio box a Skip FPGA check box
275. s C62 and C67 multi processor DSP systems as well as C40 and C44 multi processor DSP systems The Server Loadet is supported under Windows 95 98 Windows NT 4 x Windows 2000 RedHat Linux 6 1 and up The Server Loader requires a network file which is an ASCII file with a description of the DSP network to be booted C6x and C4x node entries in the network file have different keywords and the Server Loader will check if files to be loaded to the C6x are really C6x COFF files and will check if files to be loaded to the C4x are really C4x COFF files Following the introduction of the HUNT ENGINEERING API the need for the Server Loader to support motherboards using direct I O has been removed and all new as well as many existing motherboards ate supported from the Server Loader by using the API interface This allows the introduction of new boards to be matched by a release of the Server Loader this same benefit applies to the other tools that may be used It also benefits any applications developed using the program interface to the Server Loadet After a system level reset of the DSP processors the application is downloaded via the host interface on the motherboard The Server Loader ensures that each particular node in the network is booted Once the network has been booted the Server Loader allows the root processor access to a certain number of host resources such as keyboard screen and file system The root node is the first
276. s done the function returns EOF Otherwise the function returns the number of input items successfully converted ungetc int ungetc int c FILE stream TI C4x Library stdio_xx 1lib TI C6x Library stioxxxx lib ungetc pushes the character c back on to the specified input stream That character will therefore be returned by the next call to getc for that stream If the function successfully pushes a character it returns the character c else it returns EOF Note A call to fseek will erase all memory of characters that have been pushed onto the stream with ungete viprintf int vfprintf FILE stream char format va_list arg TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib vfprintf corresponds to fprintf in that it performs formatted output to the specified stream As with the function fprintf the format argument is used to control the conversion of the arguments However the argument list of fprintf is replaced by the single argument arg which should be an argument pointer initialised by va_start The function returns the number of characters output or if an output error occurs returns a negative value vprintf int vprintf char format va_list arg TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib vprintf corresponds to printf in that it performs formatted output to the stdout stream As with the function printf the format argument controls the conversion of the following arguments However as wi
277. s each function s parameters relating to the SRVFIEPARAMS structure fclose USER SRV _FCLOSE This function only uses the Fd parameter for the filehandle Example unsigned long myfclose const SRVFIEPARAMS p return fclose p gt Fd fread USER SRV FREAD This function uses the first 4 parameters as its naming suggests Example unsigned long myfread const SRVFIEPARAMS p d fwrite USER SRV FWRITE return fread p gt buf p gt blks p gt elts p gt Fd This function uses the first 4 parameters as its naming suggests Example unsigned long myfwrite const SRVFIEPARAMS p return fwrite p gt buf p gt blks p gt elts p gt Fd ungetc USER _SRV_FUNGETC This function uses the Fd and blks denoting a character parameters Example unsigned long myungetc const SRVFIEPARAMS p d fgets USER_SRV_ FGETS return ungetc p gt blks p gt Fd ta This function uses the Fd blks for size and buf parameters The elts parameter is actually set to 1 so blks elts would also denote the correct size Example unsigned long myfgets const SRVFIEPARAMS p 93 HUNT ENGINEERING Server Loader USER MANUAL return fgets p gt buf p gt blks p gt Fd fputs USER_SRV_FPUTS This function uses the Fd and buf parameters The blks parameter is set to the size of the buf string and the elts parameter is set to 1 Exa
278. s not fitted The testing mode allows you to test that the flash network file is correct It also allows you to verify that the flash rom file as created is correct And you don t need to program the HETFLASH all the time to try the next idea However to use the flash testing mode you must have a comport connection between the bus interface and the ROOT C4x For example on a HEPC2 E or HEPC4 you would connect a cable between host port A and a comport connector of the C4x processor that would be next to the HETFLASH Replacing the flash entry by flashtest in the network file enables testing mode For example if your flash network file states Soe See at Sale Bee ee See Seale BROS ee EE See eee See Board description BD API Board_type Board_Id Device Id Gah E EEP E NE ey Ny ed E EE E flash API hep3b 0 0 32 HUNT ENGINEERING Server Loader USER MANUAL then using the flash testing mode needs this to be changed to a a am Ne RN kN EE EE E IO ee a ys aR VE tN re ea es are es ten Board description BD API Board_type Board_Id Device Id TEE E E EE E ENE E AELE PEN E EE D E E EE a E E E NEEE E E E E ebe EH flashtest API hep3b 0 0 The most important requirement for the testing option to work is a comport cable to the C4x that would be adjacent to the HETFLASH This is not always possible though e g with a twin or quad module 33 HUNT ENGINEERING Server Loader USER MANUAL Server Loader and HERON API How is t
279. s not listed HeartConf will open the device itself Parameter n is the number of open devices handles that you have listed in the array that uDevice points at 87 HUNT ENGINEERING Server Loader USER MANUAL Return value loader will return 0 upon success and return 2 or higher upon error Use get lasterr of the hesl class for a description of the error int hes1 loader int argc char argv y The loader function will reset boot configure HEART and start but not serve a system of C6x FPGA and other types of nodes as per the network file that it is asked to process Include include hesl h Parameters argv is an array of pointers to character strings and argc is the number of entries in the argv array Each character string should represent a Server Loader option for example r for reset for a full list of options please refer to Invoking the command line Server Loader on page 14 option s will be ignored by this function though One character string would represent the path and name of the network file Return value loader will return 0 upon success and return 2 or higher upon error Use get lasterr of the hes class for a description of the error int hes1 loader char options char network 1 The loader function will reset boot configure HEART and start but not serve a system of C6x FPGA and other types of nodes as per the network file that it is asked to
280. se Server Loader to load network use API to custom setve network exe Use Setver Loader Host Library to both load and custom setve netwk mysl contains an example of using the Host libraries to make your own version of the Server Loader program Running the C4x Examples In most example directories there s only one example In such cases the example can be run using the w32 bat batchfile w32 In the mysl amp sl api directories to run the local sample personalised Server Loader use my32 Compiling the C4x Examples All example directories have a batch files make bat This batch files will compile all example programs for the C4x Compiling on LINUX VxWorks or RTOS 32 At the time of writing this manual no TI C compiler was available for LINUX VxWorks ot RTOS 32 systems To compile DSP programs use a Windows PC or use a Windows emulator on LINUX In either case you should be able to use the provided batch files even if you may have to change some or all of the hard coded paths in these batch files 63 HUNT ENGINEERING Server Loader USER MANUAL Server Loader Library Functions int hesl FindIBCLink int fnode_id int ffifo int tnode_id int tfifo d FindIBCLink is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file FindIBCL
281. se the function returns non zero rewind void rewind FILE stream TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib rewind repositions the specified stream to the first character of the associated file Has no effect on streams associated to devices such as keyboard or VDU It is implemented as a macro scanf int scanf char format TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib scanf reads input from the stream stdin and interprets the input according to the format string format storing the resulting values in the variables pointed to by the arguments that follow The meaning of the format string is identical to that of the function fscanf If an end of file or input error occurs before any conversion is done the function returns EOF Otherwise it returns the number of items successfully converted and stored 101 HUNT ENGINEERING Server Loader USER MANUAL setbuf int setbuf FILE stream char buf TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib setbuf is identical to setvbuf file buf _IOFBF BUFSIZ It is used before any input or output operation is done on an opened stream It causes the buffer buf to be used for the specified stream instead of the automatically allocated buffer and causes the buffering mode to be fully buffered If buf is a null pointer then the buffer used is that which was originally automatically allocated The size of the buffer is obtained by BUFSIZ
282. sed via the same board hep9a 0 GetBoardHsbAccessId 1 amp i will return 0 and i will be set to 0 because HSB on hep9a 1 can be accessed via board hep9a 0 i e board 0 GetBoardHsbAccessId 2 amp i will return an error because there s no board with id 2 i e there s no third BD definition Include include hesl h Return value Get BoardHsbAccessId will return a value of 2 or higher upon error and 0 if no error was encountered Parameter id will be set to the board via which HSB on board bdid can be accessed 68 HUNT ENGINEERING Server Loader USER MANUAL int hesl GetBoardHsbAccessSw int bdid char dev int bdsw IS Get BoardHsbAccessSw is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file When using certain inter board modules such as the EM2 HSB connections may be created between multiple boards Using such inter board modules it is possible to access all of a board fifo s hsb reset via another board connected to it A board that is to be accessed via another board is specified with the remote keyword in a BD API definition This way boards that are not inserted in the PC can still be booted and accessed via another board which is inserted in a PC Get BoardHs
283. ss to a slave board s reset HSB and fifo s will be via a master board Error 1417 Out of memory while trying to find master slave path between boards Memory allocation failed when trying to allocate enough space to store a master slave path of boards Error 1418 Cannot find a master board to support slave board od there are no BDCONN BDLINK connections for reset towards a master board A slave board must have a master board It is possible to have multiple slaves and one master but without a master board slave boards cannot be accessed HeartConf has not found a master board to go with the slave board indicated Error 1419 There are od reset paths from master board od to remote board od Please use NORESET to specify what links not to use for reset Error 1420 There are reset paths from d master boards to remote board od Please use NORESET to specify what links not to use for reset Error 1421 There are od reset paths from master boards to remote board od Please use NORESET to specify what links not to use for reset Connections between inter board connector modules on different boards transport control signals reset HSB when the boards are configured as master and slave s But there may only be one control path between a master and a slave or between successive slave boards Use the NORESET and NOHSB keywords to select what 154 HUNT ENGINEERING Server Loader USER MANUAL inter board c
284. sseessesseesres 28 PROGRAMMING THE HETFLASH cccsssssecesssccesesssecsessnsecsssseeesnsssecsesessecssaeeceensssecsesessecsecaeessnensecees 30 VERIFYING THE HETFELASH erei ENEE r e a a ddee 31 TROUBLESHOOTING HETELASH e aaraa t rae aaae aE e aaeoa adea E Aoa eatae eaan eadarainn aia 32 FLASH TESTING P TION asteet E aaaea aeaa aa nh E aaae ea Taa ebena aa EE EO aa 32 SERVER LOADER AND HERONGAPI cssssssssscsssssssssssccccccssssssssssscccssssssssssscees J How IS THE HERON API USED IN THE SERVER LOADER cssssccssssesseecseceeseecsseceeeeecsseceeeeecsaeeeeeees 34 Whats Nil 10 JUNCHONS ENEE Ee dE ee sek Roane E 34 HOW EEN 34 THE SERVER LOADER HOST LIBRARIES ccccssssssssrcccccsssssssssscscsssseseess JD KE EE 35 SERVERLOADER FUNCTIONS eege EE aes Ge Ee EE 35 LOADER Le 37 SERVER FUNCTION eessen eelere ee os Ne dee dee 37 FEAGMESERVERUP eegen N deene derbei eege Eet eege ee gedeg 38 HEARTCONF FUNCTIONS cas Sesto seeds oie est See ee le ed A EA 38 TERMINATION edd EEN EEN ces eels 40 PARSING THE NETWORK FILE 34 5 e sh eiat hcl edt weed os Sa ec EE 40 RETRIEVING NETWORK FILE INFORMATION 41 E 41 N de informati n 5 sch ro8 eGR ode te EE Reason EE 42 Connection informati n aiseta narena inen raian ianea p Erea oainnt i atean esia ateriaa aarian niiet 43 WINDOWS AND OTHER NON CONSOLE PROGRAM 43 ERROR HANDLING se Ha ee Seiwa a See ee ee ewe 46 VERSION INFORMATION peras aiee casseeee E EREE GEA E EEES EE
285. ssor node Nodes defined in BOOTSLOT statements must be C6x or PPC nodes because a BOOTSLOT statement tells the software via what timeslot FIFO 0 the node is to be booted FPGA 0 fpganode normal 0x02 myfile out BOOTLINK fpeanode Error 0314 Line d Expected timeslot in BOOTSLOT statement The parser reached the end of file after processing BOOTSLOT lt nodename gt in a BOOTSLOT statement A timeslot number was expected BOOTSLOT mynode Error 0315 Line d BOOTSLOT statement uses invalid timeslot number s The parser expected to find a timeslot number after processing BOOTSLOT lt nodename gt in a BOOTSLOT statement but found a text string instead BOOTSLOT mynode xxxx Error 0316 Line d BOOTSLOT statement uses invalid timeslot number d The parser successfully found and parsed a timeslot number after processing BOOTSLOT lt nodename gt in a BOOTSLOT statement but the timeslot is not a valid number It has to be a number from 0 to 5 C6 0 mynode root 0 0x1 myfile out BOOTSLOT mynode 8 Error 0330 No inter board module defined for board d Boards used in a BDCONN BDLINK statements must have an inter board module defined n The parser has successfully parsed all BDCONN BDLINK and BDPATH definitions But it finds that one or boards used don t have an inter board module 128 HUNT ENGINEERING Server Loader USER MANUAL defined BD API hep9a 5 0 this is board 0 BD API hep9a 2 0
286. string Typically you use it to retrieve an error description when a Server Loader function has returned a value larger than 2 The string buffer itself is within the hes class object Therefore you should not manipulate or change the buffer contents Include include hesl h Return value get lasterr will return a pointer to a string that describes the last error encountered by HeartConf or the Server Loader int hesl GetNodeBoardId int nodeid int bdid i GetNodeBoardld is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file GetNodeBoardlId will tell you what the board id is of the board that the node is defined to be on in the network file Boards can be identified with a board id bdid In your network file the very first BD declaration will define a board with id 0 the second BD declaration will define a board with id 1 and so on Don t confuse the board id with the red switch Nodes can be identified with a node id nodeid In your network file the very first node definition will define a node with index 0 the second node definition will define a node with id 1 and so on Examples of node definitions are C6 FPGA EM2 GDIO and PCIF But note that this is not a full list and
287. t d The parser reached the end of file after processing UMIRESET in a UMIRESET statement A node name was expected UMIRESET N Error 0501 Line d UMIRESET statement od uses invalid heron id or node s The parser successfully parses the node name in a UMIRESET statement but finds that this node is not defined earlier in the network file UMIRESET xxxx Error 0502 Line d UMIRESET statement od uses non HERON node s The parser successfully parses the node name in a UMIRESET statement and finds that this node is defined earlier in the network file but the node is not a HERON node 141 HUNT ENGINEERING Server Loader USER MANUAL UMIRESET cs Error 0503 Line d Expected fifo number in UMIRESET statement d The parser reached the end of file after processing UMIRESET lt nodename gt in a UMIRESET statement A fifo number was expected UMIRESET nodea AN Error 0504 Line od UMIRESET statement d uses invalid fifo number The parser expected to find a fifo number after processing UMIRESET lt nodename gt in a UMIRESET statement but found a text string instead UMIRESET nodeca xxxx Error 0505 Line od UMIRESET statement d uses invalid fifo number d The parser successfully found and parsed a fifo number after processing UMIRESET lt nodename gt lt fifo gt in a UMIRESET statement but the fifo number is not a valid fifo number It must be a number from 0 to 5
288. t alter the types for the semaphore and the semaphore creation and thread functions The FlagMeServerUp function can also be used with the hes class s loader and server function but please be aware that the semaphore is flagged from within the server function The semaphore will be flagged after all threads that serve nodes have been created but before actual serving of those nodes starts Example On the HUNT ENGINEERING CD you will find an example of using the Server Loader library and an API code thread using the hes class s loader server and serverloader functions It s in software examples server_loader_examples c6x sl_api threads Completion Server Loader library The hes class s server and serverloader using s option functions will complete only after all processor nodes that are served have executed the srv_exit function If there are no processor nodes that are to be served the functions complete immediately Please be aware all of bi directional fifo connections between processor nodes and host If that processor node doesn t execute any stdio functions it s easy to forget to call srv_exit in that code Either that or use NOSERVE in the network file Stv_exit The srv_exit function is to be executed in the DSP code on a processor node served by the Server Loader The function sends over a fifo connection
289. t board od A node has been defined to exist on a board that is not defined BD API hep9a 2 0 this is board 0 FPGA 2 fpganode normal 0x02 myfile out In the above there is no board 2 There is only a board 0 with red switch 2 Error 1003 Parsing Ys Node s has HERON id 0x x ie board 0x x slot 0x x but its HERON carrier has a switch set to 0x x A node has been defined to exist on a board that is defined but its heron id doesn t match the red switch setting of the defined board BD API hep9a 2 0 this is board 0 FPGA 0 fpganode normal 0x32 myfile out In the above board 0 is an HEPC9 with the red switch set to 2 The FPGA definition states that the FPGA module is on board 0 but the heron id used identifies a red switch setting of 3 bits 7 4 of 0x32 Error 1004 Parsing s Node s says it s on board od but there s no such HERON carrier A node has been defined to exist on a board that is not defined Or the board is defined but the board doesn t support nodes of that type BD API hep9a 2 0 this is board 0 FPGA 2 fpganode normal 0x02 myfile out In the above there is no board 2 There is only a board 0 with red switch 2 Error 1005 Parsing s No path found on board d between ROOT node s and node s On systems that use a ROOT node the Server Loader will check that a boot path 144 HUNT ENGINEERING Server Loader USER MANUAL exists from the ROOT to every NORMAL node T
290. t character from the specified stream If a read error occurs or and end of file is encountered EOF is returned fgets char fgets char string int n FILE stream TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib fgets reads a maximum of n 1 characters from the specified stream into the string str If a newline or an end of file is encountered reading stops The string is terminated with a NUL character 96 HUNT ENGINEERING Server Loader USER MANUAL If an error occurs or if an end of file is encountered before any characters have been read the function returns NULL else the function returns str fopen FILE fopen char filename char mode TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib fopen opens the specified file associating a stream with it It returns a pointer to be used to identify the stream in subsequent operations NULL is returned if the operation fails fprintf int fprintf FILE stream char format TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib fprintf outputs the arguments following the format argument to the specified stream The format argument controls the output format of the arguments that follow The format string contains two types of object Plain characters that are directly copied to the output and conversion characters that apply to each next argument A conversion begins with the character The conversion characters are d I The int argument is
291. t example documentation For VxWorks VXWORKS must be defined and be 1 For LINUX _LINUX must be defined and be 1 For RTOS 32 _RTOS32 must be defined and be 1 Linking with Libraries With a 32 bit Microsoft Visual C C compiler you should link with the win32s1 1lib library To run your application make sure that the win32s1 d11 file is located in the system directory of your operating system Windows 95 98 c windows system and in Windows NT W2K c winnt system32 SDK install should have done this for you With a 32 bit Borland C C compiler you should link with the win32slbl 1lib library To run your application make sure that the win32slb1 dl11 file is located in the system directory of your operating system Windows 95 98 c windows system and in Windows NT W2K c winnt system32 SDK install should have done this for you With LINUX you should link with 1iblinuxs1 so which should have been deposited in ust local lib by the installation script With VxWorks there s no need to link with a library if the vxwsl o has already been loaded separately onto the system If this is not the case either link with vxwsl o or vxwsllib o The former vxwsl o contains the Server Loader executable HeartConf as well as the 47 HUNT ENGINEERING Server Loader USER MANUAL Server Loadet library With RTOS 32 you should link with rtossllib which should be located in the hesl lib rtos32 sub directory of y
292. t is to be accessed via another board is specified with the remote keyword in a BD APT definition This way boards that are not inserted in the PC can still be booted and accessed via another board which is inserted in a PC Get BoardHsbAccessId tells you via what other board HSB can be accessed for the board with board id bdid If the board s HSB can be accessed directly then id will be set to the same value as bdid If the board is remote then id will be set to the board id of the board via which HSB on board bdid can be accessed Note that GetBoardHsbAccessId is identical to Get BoardHsbAccessS amp w but that the access board is identified with id in Get BoardHsbAccessId and with dev and bdsw in Get BoardHsb AccessSw Parameters The board is identified with a board id bdid In your network file the very first BD declaration will define a board with id 0 the second BD declaration will define a board with id 1 and so on Don t confuse the board id with the red switch If no error is encountered id will be set to the board via which HSB on board bdid can be accessed Example BD API hep9a 0 0 BD API hep9a 1 0 remote em2 0 em2a normal 0x06 em2 1 em2b normal 0x16 BDCONN EM2a 0 EM2b 0 With the above network file definitions GetBoardHsbAccessId 0 amp i will return 0 and i will be set to 0 because HSB on hep9a 0 can be acces
293. t is empty or a non processor module is in the slot Error 3613 Cannot receive HSB message via board os from slot 0x x error x s There was an error when trying to receive a message over HSB The error description in brackets is from the HUNT ENGINEERING API HeHSBReceiveMessage function The error code in brackets is an API error code The typical reason for this error is when Code Composer Studio is running or has run and no Debug gt RunFree has been executed on the module in the slot specified Other reasons for this error can be that the slot is empty or a non processor module is in the slot Error 3614 Unexpected HSB message received board s slot ox message_type not x received x An HSB message was successfully sent to the slot specified and an HSB message was received back from the module in that slot However the message type in the reply was not the expected MODULE_TYPE_REPLY which is what is expected after a module type query The HSB data is corrupted or perhaps the module boots from PROM and the standard HUNT ENGINEERING code isn t running Error 3615 Board Query on non API board s Internal error Attempt to run a board query on a board that doesn t have that feature Please contact support and send your network file Error 3650 Invalid device c cannot write HEPC6OA direct access Error 3651 Invalid device oc cannot read HEPC6A direct access Error 3658 Invalid device Yoc cannot read
294. t is possible to have multiple slaves and one master but without a master board slave boards cannot be accessed HeartConf has not found a master board to go with the slave board indicated 152 HUNT ENGINEERING Server Loader USER MANUAL Error 1405 There are d HSB paths from master board od to remote board d Please use NOHSB to specify what links not to use for HSB Error 1406 There are HSB paths from d master boards to remote board od nPlease use NOHSB to specify what links not to use for HSB Error 1407 There are d HSB paths from master boards to remote board od nPlease use NOHSB to specify what links not to use for HSB Connections between inter board connector modules on different boards transport control signals reset HSB when the boards are configured as master and slave s But there may only be one control path between a master and a slave or between successive slave boards Use the NORESET and NOHSB keywords to select what inter board connection should carry the control signals For example BD API hep9a 0 0 BD API hep9a 1 0 slave BDLINK 0010 BDLINK 0111 Here there are two inter board connections between hep9a 0 0 and hep9a 0 1 You must choose which of the two is to carry the control signals To select the first BDLINK connection for the control signals use BD API hep9a 0 0 BD API hep9a 1 0 slave BDLINK 0010 BDLINK 0111 NORESET NOHSB Error 1408 Board d cannot be a slave as there ar
295. t only can the ROOT node issue standard I O requests NORMAL nodes can do so as well A node needs to have a duplex HEART connection with the host interface in order to be able to do so In fact more than 1 node may issue standard I O requests So what happens if 2 DSP s want to write a message on the screen at the same time The Server Loader ensures that access to stdout stdin and stderr are mutually exclusive So if both DSP1 and DSP2 want to do a Server Loader printf the Server Loader will ensure that one proceeds without being interrupted by the other Each DSP that can send I O requests will have a dedicated server thread running on the host PC Server threads can only access stdout stdin or stderr once they gain access to a global semaphore For all other accesses the onus is on the user to prevent concurrent access of a shared PC resoutce For example if you have 2 DSP processors that both try to access a file named myfile txt you have to make sure that both processors do this without stepping on each other s toes Also if you want to have sets of standard I O calls go undisturbed you must take care of this situation yourself With the current version of the Server Loader you can only use stdio functions within 1 task or thread Using printf statements within 2 or more concurrent tasks or threads may result in your application hanging If you are a
296. t options for example rv Possible Heart ont options are t reset v verbose z no zap and b0 1 2 3 For an explanation of these options please refer to Invoking the command line Server Loader on page 14 Parameter network is a pointer to a character string that represents the path and name of the network file Return value heart conf will return 0 upon success and return 2 or higher upon error Use getlasterr of the hesl class for a description of the error int hesl heartconf HE HANDLE uDevice 86 HUNT ENGINEERING Server Loader USER MANUAL int n int argc char argv The heartconf function will configure HEART and optionally reset a system as per the network file that it is asked to process Include include hesl h Parameters argv is an array of pointers to character strings and argc is the number of entries in the argv array Each character string should represent a HeartConf option r reset v verbose z no zap or b0 1 2 3 for an explanation of these options please refer to Invoking the command line Server Loadet on page 14 One character string would represent the path and name of the network file Parameter uDevice is a pointer to an array of open device handles You don t need to open any device specifically for use by HeartConf The uDevice list allows you to tell HeartConf what devices you happ
297. tact support and send your network file Error 6004 Unsupported function for module used Internal error The HSBZap function is not implemented for one of the node types used in the network file Please contact support and send your network file Error 6005 Unsupported function for module used Internal error The ResetZap function is not implemented for one of the node types used in the network file Please contact support and send your network file Error 6100 SetIdromName not implemented for host interface module type Internal error The SetIdromName function is not implemented for the host interface module type PCIF Please contact support and send your network file Error 6150 SetIdromName not implemented for inter board module type Internal error The SetIdromName function is not implemented for the inter board connector module type IBC Please contact support and send your network file Error 6200 SetIdromName not implemented for host interface module type Internal error The SetldromName function is not implemented for IO modules GDIO Please contact support and send your network file Error 6250 SetIdromName not implemented for host interface module type Internal error The SetIdromName function is not implemented for HERON IO and HERON FPGA modules FPGA Please contact support and send your network file Error 7000 Error reading tag of incoming message The Serv
298. ted on a board with the red switch setting set to 1 But the heron id 0x21 implies a red switch setting of 2 BD API hep9a 1 0 board number 0 GDIO 0 mynode normal 0x01 But when using heron id 0x01 the heron id is automatically updated to a heron id with the correct board switch as derived from the board number 0 So you will be fine if for the heron id you simply write the slot number In the above the software will update heron id 0x01 to the correct heron id 0x11 automatically Error 0140 Line d Node s says it s on board d but there s no such HERON carrier The board number used in a GDIO node statement does not refer to a valid board Valid boards are defined by BD statements Board number 0 refers to the first BD statement board number 1 to the second BD statement and so on BD API hep9a 1 0 board number 0 GDIO 1 mynode normal 0x11 In the above board number 1 refers to a second BD statement but there s only one board defined The board number should be 0 referring to BD API hep9a 1 0 BD API hep9a 1 0 board number 0 GDIO 0 mynode normal 0x11 Error 0160 Parsing os Too many nodes maximum is d For each node defined in the network file CND C6 CAT FPGA GDIO PCIF etc an internal object is created Because only so many objects can be stored in the array that the Server Loader and HeartConf software uses there
299. tements to ensure that the node specified can be reached from the host and from the ROOT node Error 3020 No module in slot d cannot boot s The HERON DSP module specified couldn t be booted because the slot is empty Error 3021 Module in slot d is not a processor module cannot boot s Error 3022 Module in slot d is an FPGA module cannot boot s The HERON DSP module specified couldn t be booted because the module in the slot is not a HERON DSP module Error 3040 No module in slot Yd cannot boot s 171 HUNT ENGINEERING Server Loader USER MANUAL The HERON DSP module specified couldn t be booted because the slot is empty Error 3041 Module in slot d is not a processor module cannot boot s Error 3042 Module in slot Yod is an FPGA module cannot boot s The HERON DSP module specified couldn t be booted because the module in the slot is not a HERON DSP module Error 3080 No module in slot Yod cannot send bitstream to s Couldn t send the bitstream to the HERON FPGA or HERON IO module specified because the slot is empty Error 3081 Module in slot d is a processor module cannot send bitstream to s Error 3082 Module in slot d is not an FPGA ot HERON IO module cannot send bitstream to Ys Couldn t send the bitstream to the HERON FPGA or HERON IO module specified because the module in the slot is not a HERON FPGA or HERON IO module Error 3200 Node s Cannot find HRN
300. ter modtype is NULL in GetNodeModType The second parameter supplied to GetNodeModType is a NULL pointer Error 1756 Internal Error node od was found to be NULL nodes d Internal error When searching through the list of nodes a node pointing to NULL was found Please contact support and send your network file Error 1757 Node od is not a valid node Internal error When searching through the list of nodes a node with an unknown node type was found Please contact support and send your network file Error 1760 Parameter bdid is NULL in GetNodeBoardld The second parameter supplied to GetNodeBoardld is a NULL pointer Error 1761 Internal Error node d was found to be NULL nodes d Internal error When searching through the list of nodes a node poiting to NULL was found Please contact support and send your network file Error 1762 Node d is not a valid node Internal error When searching through the list of nodes a node with an unknown node type was found Please contact support and send your network file Error 1765 Parameter bdsw is NULL in GetNodeBoardSw The second parameter supplied to GetNodeBoardSw is a NULL pointer Error 1766 Parameter del is NULL in GetNodeBoardSw The third parameter supplied to GetNodeBoardSw is a NULL pointer Error 1767 Internal Error node od was found to be NULL nodes d Internal error When searching through the list of nodes a node pointing to NULL 163 HUNT ENGI
301. ter processing FPGA lt n gt lt nodename gt in a node statement A node type ROOT or NORMAL was expected FPGA 0 mynode Error 0105 Line d Node s uses invalid node type s The parser expected to find a node type ROOT or NORMAL after parsing FPGA lt n gt lt nodename gt in a node statement but found a text string that is not a valid node type i e the type string is not ROOT and is not NORMAL FPGA 0 mynode xxxx Error 0106 Line od Expected heron id in FPGA statement The parser reached the end of file after processing FPGA lt n gt lt nodename gt lt type gt in a node statement A heron id was expected FPGA 0 mynode normal N 114 HUNT ENGINEERING Server Loader USER MANUAL Error 0107 Line d Node s uses invalid heron id s The parser expected to find a heron id a decimal or hexidecimal number after parsing FPGA lt n gt lt nodename gt lt nodetype gt in a node statement but found a text string instead Precede a hexidecimal number with Ox FPGA 0 mynode normal xxxxx Lei Error 0108 Line Yod Node s uses incorrect heron id 0x x Bits 0 3 must be slot 1 2 3 or 4 The parser has found and parsed a heron id after parsing FPGA lt n gt lt nodename gt lt nodetype gt lt heronid gt in a node statement but the heron id is not a valid number Bits 7 6 5 4 identify the board switch of the board the module
302. ternal error The connecting inter board connector module as stored in the Server Loader is NULL Please contact support and send your network file Error 1547 Node s is not an Inter Board Module Internal error The connecting inter boatd connector module as stored in the Server Loader is not an inter board connector module Please contact support and send your network file Error 1560 There s no node with index d maximum d FindNodeConn error A node has an index that isn t in the list of nodes the index is smaller than 0 or higher than the number of nodes defined in the network file Error 1561 Internal error Node d of d nodes is NULL Internal error A node with a valid index in the list of nodes points to nothing Please contact support and send your network file Error 1562 There s no node with index d maximum d FindNodeConn error A node has an index that isn t in the list of nodes the index is smaller than 0 or higher than the number of nodes defined in the network file Error 1563 Internal error Node d of d nodes is NULL Internal error A node with a valid index in the list of nodes points to nothing Please contact support and send your network file Error 1570 There s no node with index d maximum d FindNodeConnCount error A node has an index that isn t in the list of nodes the index is smaller than 0 or higher than the number of nodes defined in the network file 158 HU
303. th vfprintf the variable argument list is replaced by a single argument arg which should be an argument pointer initialised by va_start 103 HUNT ENGINEERING Server Loader USER MANUAL The function returns the number of characters output or if an output error occurs returns a negative value vsprintf int vsprintf char str char format va_list arg TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib vsprintf corresponds to sprintf in that it writes formatted output to the specified stream As with the function sprintf the format argument controls the conversion of the following arguments However as with vfprintf the variable argument list is replaced by a single argument arg which should be an argument pointer initialised by va_start The function returns the number of characters output or if an output error occurs returns a negative value 104 HUNT ENGINEERING Server Loader USER MANUAL Technical Support Technical support for HUNT ENGINEERING products should first be obtained from the comprehensive Support section www hunteng co uk support index 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 www hunteng co uk for the list of current re sellers HUNT ENGINEERING technical support can be contacted by emailing support hunteng co uk calling the direct support telephone number
304. the product 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 www hunteng co uk support index 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 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 Server Loader USER MANUAL TABLE OF CONTENTS EE 6 USING THE SERVER LQADER seen n A Eesen eu A A eeng H COMPILING A TI C APPLICATION FOR USE WITH THE SERVER LOADER s ssssieseeesesesreereeersstsrsrrereeeesseseeee
305. ting a serve thread for each node that it has to serve Thus each processor node that is served will have an associated server thread running within the Server Loader on the host PC Example node declarations peif 0 host normal 0x05 c6 0 first root 1 0x01 modl out c6 0 second normal 0 0x02 mod2 out fifo connections heart host 0 first 0 1 heart first 0 host 0 1 heart host 1 second 0 1 heart second 0 host 1 1 In the above example network file there is a bi directional fifo connection defined between the PC and the module in slot 1 Between the host PC and the second module there is also a bi directional fifo connection The Server Loader will serve both modules first and second using 2 threads one thread serving first and the other thread serving second Now consider another example network file node declarations peif 0 host normal 0x05 c6 0 third root 1 0x03 mod3 out fpga 0 fourth normal 0 0x04 bit rbt fifo connections heart third 0 host 4 1 heart host 5 fourth 0 1 heart fourth 0 host 5 1 The Server Loader will not serve the module in slot 3 Although it is a processor module the link between host PC and the module is not bi directional there s only a fifo connection from module third to the host and not vice versa The Server Loade
306. uffer size It tries to allocate memory to receive the buffer date but encounters an out of memory error The error is reported by the standard C malloc function Error 7105 Server cannot re allocate Yod bytes to write The Server Loadet tries to execute a fwrite request with a large buffer size It tries to allocate memory to receive the buffer date but encounters an out of memory error The error is reported by the standard C realloc function Error 7106 Server cannot allocate d bytes to read The Server Loader tries to execute a fgets request with a large buffer size It tries to allocate memory to store the buffer date but encounters an out of memory error The error is reported by the standard C malloc function Error 7107 Server cannot re allocate Yod bytes to read The Server Loadert tries to execute a fgets request with a large buffer size It tries to allocate memory to store the buffer date but encounters an out of memory error The error is reported by the standard C realloc function 184 HUNT ENGINEERING Server Loader USER MANUAL Error 7108 Server protocol error in remove The Server Loader tries to decode a remove request from a node but finds that the file name is longer than the buffer size The mode description is longer than 512 bytes or the information sent in a remove request was corrupted Error 7109 Server protocol error in rename The Serv
307. und that the master board has no inter board connector module defined Error 2128 Can t find switch setting of board s Internal error When trying to configure board control reset signal between boards it was not possible to retrieve the red switch setting of the master board Please contact 166 HUNT ENGINEERING Server Loader USER MANUAL support and send your network file Error 2129 Board s is not an API type board When trying to configure board control reset signal between boards it was found that the slave board is not of type BD APP Only boards of type BD APP can be defined as master and slave boards Error 2130 Board s is not an HEPC9 board When trying to configure board control reset signal between boards it was found that the slave board is not of type BD APP Only boards of type BD APP can be defined as master and slave boards Error 2131 Board us has no IBC Inter Board Module When trying to configure board control reset signal between boards it was found that the slave board has no inter board connector module defined Error 2132 Can t find switch setting of board s Internal error When trying to configure board control reset signal between boards it was not possible to retrieve the red switch setting of the slave board Please contact support and send your network file Error 2133 Don t know how to program IBC on slave board od An EMIC EM1 or an unknown inter bo
308. urred while trying to receive the optional additional amount of data The error occurred in a call to HUNT ENGINEERING API function HeRead Error 7100 Server protocol error in fopen The Setver Loader tries to decode an fopen request from a node but finds that the file name is longer than the buffer size The filename is longer than 512 bytes or the information sent in a fopen request was corrupted Error 7101 Server protocol error in fopen The Server Loader tries to decode a fopen request from a node but finds that the mode description e g r or rw is longer than the buffer size The mode description is longer than 512 bytes or the information sent in a fopen request was corrupted Error 7102 Server cannot allocate d bytes to read The Server Loadet tries to execute a fread request with a large buffer size It tries to allocate memory to store the buffer date but encounters an out of memory error The error is reported by the standard C malloc function Error 7103 Server cannot re allocate Yod bytes to read The Server Loadetr tries to execute a fread request with a large buffer size It tries to allocate memory to store the buffer date but encounters an out of memory error The error is reported by the standard C realloc function Error 7104 Server cannot allocate od bytes to write The Server Loadet tries to execute a fwrite request with a large b
309. ve been written to the output stream or returns a negative value if an error occurred The arguments have the same meaning as those for the function fprintf 100 HUNT ENGINEERING Server Loader USER MANUAL putc int putc int c FILE stream TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib putc writes the character c to the specified output stream It returns the character written If an error occurs the function returns EOF It is implemented as a macro putchar int putchar int c TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib putchar is identical to putec c stdout The character c is written to the stdout stream If an error occurs the function returns EOF It is implemented as a macro puts int puts char str TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib puts writes the string str to the stdout stream appending a newline character The terminating NUL character of str is not written remove int remove char filename TI C4x Library stdio_xx lib TI C6x Library stioxxxx lib remove causes the specified file to be removed If successful returns zero else it returns non zero rename int rename char old name char new name TI C4x Library stdio_ xx lib 7 TI C6x Library stioxxxx lib rename renames the file old_name to the file new_name where old_name and new_name must be pointers to NUL terminated strings If the operation is successful zero is returned el
310. ve or between successive slave boards Use the NORESET and NOHSB keywords to select what 153 HUNT ENGINEERING Server Loader USER MANUAL inter board connection should carry the control signals For example BD API hep9a 0 0 BD API hep9a 1 0 slave BDLINK 00 1 0 BDLINK 0111 Here there are two inter board connections between hep9a 0 0 and hep9a 0 1 You must choose which of the two is to carry the control signals To select the first BDLINK connection for the control signals use BD API hep9a 0 0 BD API hep9a 1 0 slave BDLINK 0010 BDLINK 0111 NORESET NOHSB Error 1414 Unknown HEPC9 extension module ox Cannot continue An inter board connector module other than the currently supported EM2 EM1 or EM1 C was defined Note that if you used the legacy keyword IBC this keyword is no longer defining an inter board connector module use EM2 EM or EM1C Error 1415 Board d cannot be a slave as there are no BDCONN BDLINK connections to it A board can be a slave only if it is connected via inter board connector modules such as EM2 or EM1 but not the EM1 C to another board Access to a slave board s reset HSB and fifo s will be via a master board Error 1416 Board d cannot be a slave as an EM1 C doesn t carry control signals reset HSB A board can be a slave only if it is connected via inter board connector modules such as EM2 or EM1 but not the EM1 C to another board Acce
311. verloader function So you would have something like int r hesl sl 1 start a separate thread executing API code r sl serverloader rlsv network 2 process any errors ie cases where r is not 0 3 wait for completion of the API thread However now we need some mechanism for the API thread to know when it s safe to start opening fifo s and accessing them This provided by the FlagMeServerUp function You create a semaphore in your code and then pass the semaphore to FlagMeServerUp Then the Server Loader will flag the semaphore when it s safe to open and access fifo s Your code would look something like Int r hesl sl HANDLE serverready NULL serverready CreateSemaphore NULL 0 1 slsem 1 process error if serverready is NULL sl1 FlagMeServerUp serverready 2 start a separate thread executing API code the API code must wait for serverready to be flagged r sl serverloader rlsv network 3 process any errors ie cases where r is not 0 4 wait for completion of the API thread 60 HUNT ENGINEERING Server Loader USER MANUAL In your API code at the very start you would have something like void _cdecl ThreadDoApi void ptr if serverready NULL WaitForSingleObject serverready INFINITE now add your API code The code for non Windows operating systems is very similar jus
312. vice is a pointer to an array of open device handles You don t need to open any device specifically for use by the Server Loader The uDevice list allows you to tell the Server Loader what devices you happen to have open the Server Loader will then use handles you provide instead of trying to open a device If a device is not listed the Server Loader will open the device itself Parameter n is the number of open devices handles that you have listed in the array that uDevice points at Return value serverloader will return 0 upon success and return 2 or higher upon error Use get lasterr of the hesl class for a description of the error int hesl serverloader HE HANDLE uDevice int n char options char network ji The serverloader function will reset boot configure HEART start and serve a system of C6x FPGA and other types of nodes as per the network file that it is asked to process 91 HUNT ENGINEERING Server Loader USER MANUAL Parameters options is a pointer to a character string that holds Server Loader options for example rlsv for a full list of options please refer to Invoking the command line Server Loader on page 14 Parameter network is a pointer to a character string that represents the path and name of the network file Parameter uDevice is a pointer to an array of open device handles You don t need to open any device specifically for use by the Server Loader The uDevice list a
313. will be set to 0 GetBoardId hep9a 2 amp bdid will return 0 and bdid will be set to 1 not 2 And GetBoardId hep9a 1 amp bdid will return an error because there s no board hep9a 1 Include include hesl h Return value GetBoardId will return a value of 0 if a board specified by dev and bdsw is defined in the network file odid is then set to the board index of that board Get BoardId will return a value of 1 if no board specified by dev and bdsw is defined in the network file Upon error the value 2 is returned int hesl GetBoardName int bdid char bdname i GetBoardName is an information function After a function such as loader heartconf serverloader or parse network file has been executed you can use this function to extract certain information from the network file GetBoardName will tell you what the board name is of a board with board index bdid Note that it will write a character string to bdname so parameter bdname must be an character array or point to a malloc ed memoty area Boards can be identified with a board id bdid In your network file the very first BD declaration will define a board with id 0 the second BD declaration will define a board with id 1 and so on Don t confuse the board id with the red switch If a board with board id bdid is defined in the netw
314. will use fifo 0 and HSB The API code should not open those devices until the Server Loader has completed the boot load process and configured HEART The API code may open a fifo before it s HEART connection is configured but must not use or access any fifo until the Server Loader has fully completed configuring HEART So how do we know when our API code can start accessing fifo s Using the hesl class s loader Synchronisation is easiest when using the loader function in the hes class Your code would look something like this int r hesl sl r sl loader rlv network 1 process any errors ie cases where r is not 0 2 start a separate thread executing API code r sl server 3 process any errors ie cases where r is not 0 4 wait for completion of the API thread After a successful call to the hes class s loader function the nodes defined in the network file will have been booted loaded and all HEART connections configured Now we can set up a new thread that will execute API code code that will execute its own communications with nodes in the network file using fifo connections defined in that network file All nodes ate booted loaded and all fifo connections are configured so it s safe to open and access any fifo that is any fifo not used by the Server Loader to serve a module We still have to start up the server part of the Server Loader after we
315. wo BDCONN statements but it finds that a sending fifo is used twice BDCONN em2b 0 em2c 0 oneway BDCONN em2a 0 em2b 0 In the above fifo 0 of em2b is used twice Error 0400 Line d Expected node name in HEART statement d The parser reached the end of file after processing HEART in a HEART statement A node name was expected HEART AN Error 0401 Line d HEART statement od uses invalid heron id or node s The parser successfully parses the node name in a HEART statement but finds that this node is not defined earlier in the network file HEART xxxx Error 0402 Line d HEART statement d uses non HERON node s The parser successfully parses the node name in a HEART statement and finds that 135 HUNT ENGINEERING Server Loader USER MANUAL this node is defined earlier in the network file but the node is not a HERON node HEART c4x Error 0403 Line d Expected fifo number in HEART statement d The parser reached the end of file after processing HEART lt nodename gt in a HEART statement A fifo number was expected HEART nodea AN Error 0404 Line od HEART statement od uses invalid fifo number The parser expected to find a fifo number after processing HEART lt nodename gt in a HEART statement but found a text string instead HEART nodea xxxx Error 0405 Line od HEART statement d uses invalid fifo number d The parser successfully found and parsed a fifo nu
316. x Error 0222 Line od Undefined node s in HOSTLINK TOHOST FROMHOST statement The parser successfully parses an optional node name but finds that this node is not defined earlier in the network file HOSTLINK xxxx Error 0223 Line d Expected link number in HOSTLINK TOHOST FROMHOST statement The parser reached the end of file after processing HOSTLINK TOHOST FROMHOST lt nodename gt in a host statement A FIFO or Comport number was expected via which the ROOT node is connected to the host PC HOSTLINK mynode Error 0224 Line d Cannot find ROOT node for board 0 in HOSTLINK TOHOST FROMHOST statement A HOSTLINK TOHOST FROMHOST statement defines what FIFO or Comport on the ROOT node is connected to host PC However no ROOT node was defined for board 0 Verify your network file and make sure that the node that is connected to the host PC is set to be the ROOT node The board on which this node resides must be defined first in the list of BD statements Error 0224 Line d Cannot find first node for board 0 in HOSTLINK TOHOST FROMHOST statement A HOSTLINK TOHOST FROMHOST statement defines what FIFO or Comport on the first node is connected to host PC However no nodes were defined for board 123 HUNT ENGINEERING Server Loader USER MANUAL 0 ie the first BD statement For HEART boards such as the HEPC9 you don t really need to use a HOSTLINK TOHOST or FROMHOST statement because
317. xt string instead BDCONN emnodea 0 emnodeb xxxx Error 0383 Line d BDCONN statement uses invalid link number d The parser successfully found and parsed a fifo number after processing BDCONN lt nodename gt lt fifo gt lt nodename gt lt fifo gt in a BDCONN statement but the fifo 134 HUNT ENGINEERING Server Loader USER MANUAL number is not a valid fifo number It must be a number from 0 to 5 BDCONN emnodea 0 emnodeb 7 AN Error 0384 Line d Fifo od on board d used at least twice in BDCONN statements The parser successfully parsed at least two BDCONN statements but it finds that a receiving fifo is used twice BDCONN em2a 0 em2b 0 BDCONN em2c 0 em2b 0 In the above fifo 0 of em2b is used twice Error 0385 Line od Fifo od on board od used at least twice in BDCONNWN statements The parser successfully parsed at least two BDCONN statements but it finds that a sending fifo is used twice BDCONN em2a 0 em2b 0 BDCONN em2a 0 em2c 0 In the above fifo 0 of em2a is used twice Error 0386 Line od Fifo od on board d used at least twice in BDCONNWN statements The parser successfully parsed at least two BDCONN statements but it finds that a receiving fifo is used twice BDCONN em2c 0 em2a 0 oneway BDCONN em2a 0 em2b 0 In the above fifo 0 of em2a is used twice Error 0387 Line od Fifo od on board d used at least twice in BDCONNWN statements The parser successfully parsed at least t
318. y Parameter uDevice is an array of handles HE_HANDLB and parameter n is to specify the number of valid handles open devices in the uDevice array It depends on the network file and the options used what devices the Server Loader will tty to open Please note that the Server Loader may use multiple handles for example both Fifo A and HSB Example int main int argc char argv hesl sl HE DWORD Status int r HE HANDLE FifoADev NULL HSBDev NULL Status HeOpen hep9a 0 HSB amp FifoADev if Status HE OK d Status HeOpen hep9a 0 FifoA S amp HSBDev if Status HE OK d Use devices printf Open error x n Status return 0 printf Open error x n Status return 0 But suppose now you wish to run serverloader And you don t want to close those devices Wi HE HANDLE hDevice 2 hDevice 0 FifoADev hDevice 1 HSBDev r sl serverloader hDevice 2 argc argv The return value for each of the 4 serverloader functions is 0 upon success Upon error a value other than 0 is returned With the getlasterr function you can retrieve a description of the error encountered by the Server Loadetr Example int main int argc char argv 36 HUNT ENGINEERING Server Loader USER MANUAL int E char errstr hesl sl r sl serverloader argc argv if r errstr sl getlasterr if errstr errstr 0 0 pri
319. you must not execute HeReset if you do you will reset the system and all booted programs and all HEART fifo connections will disappear It is not necessary to run HeartConf because the Server Loader will have configured all fifo connection you defined in the network file 55 HUNT ENGINEERING Server Loader USER MANUAL Example On the HUNT ENGINEERING CD you will find an example of using the Server Loader library then running API code after booting loading the nodes defined in a network file It s in software examples server_loader_examples c6x sl_api exe Boot network serve nodes amp run API code at the same time With version 4 08 it is also possible to run both the Server Loader and API code at the same time Well actually a similar thing was also possible with earlier versions but as explicit support was missing it was a bit tricky The Server Loader needs a bi directional fifo connection between a processor node and the host PC to serve that processor node and an API application that wishes to communicate with the same node will need its own fifo connection between that node and the host PC Server threads The Setrver Loader will serve all processor nodes that have a duplex bi directional fifo connection with the host In the case that there are multiple duplex connections between a processor node and the host the Server Loader will randomly choose one connection The Server Loader implements such functionality by crea

Server/Loader User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents