Deos Celestial D4j

From DDCIDeos
Jump to navigationJump to search


This release provides Celestial_Program with updated dpaa-prl-4.0.1 + dpaa-4.0.1.

This page was constructed following the Create Release Wiki instructions.

Description

The previous distribution is at:

\\nx3000\ship\dds\windows\approved\DDS-celestial-deos-jupiter-20231113
 \\nx3000\ship\dds\ubuntu\approved\DDS-docker-celestial-deos-jupiter-20231113

The candidate distribution is at:

 \\ddsbuild.ddci.com\DDCI_integration\DDS-celestial-deos-jupiter-20240201
   ftp://redhat5.ddci.com//Workstation/cygwin-20180401-ddci-dist-jupiter/x86_64/archive/1706800105
 \\ddsbuild.ddci.com\DDCI_integration\DDS-docker-celestial-deos-jupiter-20240201
   ftp://redhat5.ddci.com//Workstation/cygwin-20180401-ddci-dist-jupiter/x86_64/archive/1706800105

Note: The candidate distribution was created by patching the previous distribution via the DDS Patch Process.

Components to Work

Below are the Deos components that have been identified to work for this release. See also the list of Recent FTP server unreleased symbolic links.

Component Constraints: Refresh constraints

  • Must be installed together:
    • ansi-4.12.0
    • desk-headers-1.0.0
      • desk-headers provides stdio.h which includes stdio-ansi.h which is provided by ansi-4.12.0.
  • Must be installed together:
    • vfile-8.0.0
    • vfileconfig-1.13.0
    • kernel-11.8.0
    • ftpserver-11.7.0
    • desk-headers-1.0.0
    • ansi-4.12.0
      • vfileconfig-1.13.0 updates to schema 10 which is required by vfile-8.0.0.
      • kernel-11.8.0 updates libkfs.so vfile driver to vfile-8.x.
      • ftpserver-11.7.0 updates to vfile-8.x.
      • desk-headers-1.0.0 provides stdio.h in lieu of ansi providing it.
  • Must be installed together:
    • bsp-common-3.4.0
      • bsp-common-3.4.0 requires OpenArbor-12.6.0
  • Must be installed together:
    • deos-rtems-introspection 1.5.0
    • status-monitor 11.6.0
    • gdbserver-ddci 11.2.2
    • Also recommended: RTEMS 6.0.1 (deos-rtems-docs deos-rtems-adapter-aarch64 deos-rtems-adapter-arm deos-rtems-adapter-common deos-rtems-adapter-ppc deos-rtems-adapter-x86 deos-rtems-adapter-x86-64 deos-rtems-tools-aarch64 deos-rtems-tools-arm deos-rtems-tools-common deos-rtems-tools-ppc deos-rtems-tools-x86 deos-rtems-tools-x86-64 deos-rtems-autotools)

See also BDU_Script_Maintenance.

Components Version Phase CCB Who Test Report Release Notes

Legend

CCB: A Release CCB has been held
Phases:

  • Dev - In Development
  • Test - Component unreleased and ready to test
  • Delta - A Delta baseline must be established
  • Audit - One (or more) SQA Audits must be performed (e.g., a Verification and/or Software Conformity Audit)
  • Stable - You are done! All steps (including test report) in the Deos Software Release HowTo or OpenArbor Development HowTo have been followed.

Who: The person responsible for doing the work associated with the component.

Remarks: Free form text. It must contain the test report when done.

Docker Image Content

Celestial-docker-tbd

Differences from Prior Release

Added/Modified Packages

New Packages

Updated Packages

  • dpaa-4.0.1-1
  • dpaa-prl-4.0.1-2

Removed Components

Unreleased Components

DDS Test Summary

No OA testing required. Manually testing to be done by MV.

Note: Resource settings to use deos-time:

<memoryMappedResource
name = "TIME"
startAddress = "0x42E80000"
lengthInBytes = "0x1000"
accessRights = "r"
allowMultipleOwners = "yes"
cacheMode = "off"
resourceOverlapList = "TIME_CONTROL"
proxyAccessPermitted = "yes"
>
</memoryMappedResource>
<memoryMappedResource
name = "TIME_CONTROL"
startAddress = "0x42E80000"
lengthInBytes = "0x1000"
accessRights = "rw"
allowMultipleOwners = "yes"
cacheMode = "off"
resourceOverlapList = "TIME"
proxyAccessPermitted = "yes"
>
</memoryMappedResource>


Trac ARM Version 280 Test Report Trac 80x86 Version 278 Test Report Trac PPC Version 278 Test Report

Additional Testing

Diff Results

Known Problems

One thing to mention is they would be better off creating a new hypstart with the latest dpaa/dpaa-prl. This has to do with the new start up sequence. If they have an older dpaa running on the target and ftp the new dpaa on they will lose one of the interfaces at first. There is a work around, but easier if they just create a new hypstart instead.

QA Report

QA Report

Full Component Content

DDS-celestial-deos-jupiter-20240201