Load Checking

The information needed to perform the checks mentioned in the previous section is added to the application file by the configurer. The checks are designed to ensure that the network of DSPs being used matches the network described in the configuration file closely enough to allow the application to be loaded. Note that only the following things are checked:

•	the types of the processors mentioned in the configuration file; processors that differ only in the provision of external memory are considered equivalent providing the actual processor has no less memory than the processor declared in the configuration file.

•	the links that are used during the loading process; links that are not used during loading are not checked.

Load checking is supported only by versions of the Sundance bootloaders dated 27 February 2004 or later. If you attempt to load an application containing checking information to a TIM with an old bootloader, the system hang. Contact Sundance for information about updating your flash ROM with the latest bootloaders. Load checking can be inhibited by using an OPTION statement in the configuration file.

The server attempt to send some words to the root processor describing the declared type of the root. If these words are not read within a few milliseconds, the server report that the root processor cannot be accessed. You should check that you have selected the correct DSP board and that the link connection between the board and the host has been enabled.

The server now waits a few milliseconds for a reply from the root. If there is no reply, the server report that the root processor is not responding. You should check that there is a TIM in the carrier board slot that is connected to the host link, and that a current version of the bootloader has been programmed into the flash ROM.

The response from the root indicate whether or not its type is acceptable. If it is not, the server report that the root is of the wrong type. You should check that the type of the root processor specified in the configuration file matches the actual type of the processor connected to the host link.

Finally the server sends the application down to the root which distribute it to the rest of the network. Once everything has been sent, the server reads back a response from the root. A successful response means that the application has loaded correctly and it start to execute. There are two possible failure responses:

One of the processors in the network is not responding. This could be the consequence of an incorrect link connection or the use of a TIM with an old bootloader. You should check that you have specified the correct WIRE connection between the named processors and that the non-responding processor has a current bootloader.

One of the processors in the network is not of the type expected. You should check that you have specified the correct WIRE connection between the named processors and that the actual processors connected in this way are of the correct types.