Issue 9221: OnBoard Memory (xtce-rtf)
Source:  (, )
Nature: Clarification
Severity: Significant
Summary: There are no specific descriptions of onboard memory possible, i.e. block size, addressing technique, etc as per tables 12, 13 of the ECSS. This I would expect at the space-system 
description level? 
        
Onboard memory is a very specific type of space system element, for which a lot of specific data is always needed, and it would be worth making specific entry types appropriate to  onboard memory system elements. This to include Memory ID, Accessibility (read,write), smallest addressable unit, addressing technique, block length, subblock symbolic name, subblock offset, subblock length, etc

Resolution: 
Revised Text: 
Actions taken:
December 1, 2005: received issue
Discussion: 
Resolution:
Onboard memory handling between different spacecraft and ground systems has been even more varied than commands and telemetry.  To the extent that onboard memory locations can be named and brought down as "software telemetry" they are supported by XTCE, however, an exchange format for memory definitions beyond telemetry parameter definition is out of the current scope.  It is possible that this could be addressed by a future specification, but there are also numerous specifications for memory data for ordinary ground-based computer systems (Motorola S-records, Intel Hex format, Unix STABs, etc.) that may be applicable.
deferred
End of Annotations:=====
A ID:        ESA023        Name:        Ian Harrison 
        Company:        ESA        Email:        ian.harrison@esa.int 
        Notification:        YES 
        Name:        XTCE        Document #:        formal/05-08-01 
        Section:        OnBoard Memory -         Version #:        1.0 
        Revision d.:        01/08/2005        Page: 
        Nature:        Clarification        Severity:        Significant 
        Full Description:        There are no specific descriptions of onboard memory possible, i.e. block size, addressing 
        technique, etc as per tables 12, 13 of the ECSS. This I would expect at the space-system 
        description level? 
        
        Onboard memory is a very specific type of space system element, for which a lot of specific 
         data is always needed, and it would be worth making specific entry types appropriate to 
        onboard memory system elements. This to include Memory ID, Accessibility (read,write), 
        smallest addressable unit, addressing technique, block length, subblock symbolic name, 
        subblock offset, subblock length, etc.