⟦d1320bb84⟧

TextFile

*******************************************************

         R E L E A S E   D E S C R I P T I O N

*******************************************************




Module id number: CSS/7389
--------------------------

Module name:      S-Net Utility Program (SNUP)
----------------------------------------------

Actual release:   03.02            Release date: 851031
-----------------------            --------------------

Previous release: 03.01            Release date: 851005
-----------------------            --------------------




New facilities:
---------------

  >> 0104 <<

    This release can communicate with (boot etc) a CMR placed in
    a CU.

  >> 0105 <<

    The module has been restructured to facilitate the building
    of a programmed interface to the SNUP facilities.

  >> 0201 <<

    A more complete restructuring has been done to separate
    the interactive parts and the function parts of SNUP.
    If the function parts of SNUP are used as a linkmodule set,
    the TPE link modules may be omitted from the link files.

    An improved strategy for bootloading remote PUs have been
    implemented. This requires that the local PUCD and the
    remote STI both have the support for this function.

    Setparity and erasememory has been implemented as
    separate commands, available both as interactive
    and programmed parts.

  >> 0301 <<

    May now run in MX type 2.

    SNIs can be handled in MX type 2 without PUCD.

    MX type of remote PU (or CU-CMR) is automatically
    determined at masterclear of the same.

    Size of remote MIC RAM (used for communication with
    remote boot loader) automatically determined.

    Remote IO write and read commands may be executed
    (will only work if remote MX is type 2).

    If bit 15 in the Root parameter in the boot file header
    is set, SNUP will install memory IO pointers in the
    bootmodule prior to starting it and it may thus be
    ensured that all output from the bootmodule is
    received by SNUP.
    ALL offline test bootmodules should be generated
    with R:#8000 in the MXBOOT command line   !!!!!

Changes:
--------

  >> 0102 <<

    This release uses the new frame format (the format including
    pu-active bits and masterclear bits in the protocol 3 frames).

  >> 0103 <<

    The interface between the very SNUP module and the SNIF module
    is changed, so that errors detected by SNIF are returned to the
    caller of SNIF procedures (instead of being reported directly
    on the current output file in text form).

    In this version SNUP attempts to use a PUCD for S-net communication.
    If the PUCD does not reply properly, direct STI communication is
    attempted.

    Note: it has not been practically possible to test the PUCD communi-
    cation before releasing. The direct STI communication and the modified
    SNIF procedure interface is tested, however. If no PUCD is running
    or if the PUCD is not assigned, SNUP will work properly with the
    direct STI interface.

    The SNIF interface is described in the file SNIF.I.

  >> 0201 <<

    SNUP will now only use the STI/SBA directly if no PUCD
    exists in the system.

    Completion codes are as far as possible given back to
    the user of SNUP.

    SNUP now uses unique port names when communicating with
    PUCD. This allows for more than one SNUP to exist
    in a complete S-net (and also in each PU).

    The masterclear of a CMR has been optimized to wait
    only the necessary time for the CMR to finish its
    selftest.

    SET TARGET CMR ADDR no longer masterclears the CMR.
    This also gives the change, that a CMR must be
    mastercleared before it is loaded by a boot module
    (this is done automatically when using the BOOT command).

Errors corrected:
-----------------

  >> 0105 <<

    The strategy for determining whether a patch (with check)
    has been completed or failed has been changed to
    facilitate a faster timeout in case of a non-responding
    remote PU.

    SNUP can now be restarted.

  >> 0201 <<

    Filenames may now have the usual syntax, i.e.
    '.' is now treated as a letter in filenames
    and any letter or digit or '_' may now follow
    after '.' in filenames. They may also start
    with '.' .
    This has, however, the side-effect that decimal
    constants may not follow directly after '.',
    e.g. the construction '0.0' is no longer allowed
    but must be typed '0. 0'. Hexadecimal constants
    are not affected by this and are recommended.

  >> 0301 <<

    Breaks may now be sent to and understood by remote test
    programs loaded by SNUP. This requires TPE version 3.1
    or later to be linked into the test program.

  >> 0302 <<

    Version 0301 could not communicate via PUCD. This is
    corrected in current version.

Reported errors, not corrected:
-------------------------------

    SNUP can not always communicate with remote test
    programs e.g. RAM test.

PRs implemented in current release:
-----------------------------------

Comments:
---------

  For further information refer to CSS/7389/PSP/0105, Issue 2 «a5»
DataMuseum.dk

CR80 Hard and Floppy Disks

⟦d1320bb84⟧ TextFile

Derivation

TextFile
