User:Bcronk@ddci.com

From DDCIDeos
Jump to navigationJump to search

Week 4

Out-Of-Office Time

  • 27-JAN - 1-Feb In Phoenix for Geek Week
  • Check Calendar for meetings/appointments

The Queue

Priority Goal Type Due Date Cur. Date Discussion Forum Remarks
0 Collins HotDish Boot Loader Quote Manage N/A 2019-01-21 Staff Done
05 HotDish Boot Issue Manage N/A 2019-01-21 Staff
10 Hiring Manage N/A 2019-01-21 Staff
20 Surcouf Release Manage N/A 2019-01-25 PL/PLM
20 Rosti Release Manage N/A 2019-01-25 PL/PLM
30 HI IOI Quote Manage N/A 2019-01-21 Staff
50 Complete customer list (CAF sig.) Manage N/A 2019-01-21 PL/PLM
60 Review BSP_Developer_Training_Internal Manage N/A 2019-01-21 Deos Team Meeting
70 Support Logs Manage N/A 2019-01-21 Deos Team Meeting

Meetings

Collins Boot Loader Meeting

Issue 1: Flash Component (FSI) =

Not related to DDC-I.

Issue 2: PPC Startup =

  • Previous variant of this issue was refered to ass "cold start".
  • Solderability issue fixes most units, some still have a low failure rate that go away by making the TLB change.

Topic HW Watchdog Design =

  • Is the reset state after WD trip the same as processor reset? Collins to answer.

PL/PLM

  • TBD

Staff

  • TBD

Harrys

  • TBD

Deos Team Meeting

  • TBD

DesertEagle

  • System tick interrupt managed by handler (RR)
  • Second interrupt manage by thread timer
  • clarification on board, bus and MAL media
  • u-boot only in binary form (that I know of)
  • Network driver for LS1048A (DAL-E only)

Surcouf

  • Workspace conversion issues

Network

  • Driver and callback
    • setup DMA then call
    • error callback
    • initialization function for mac address
    • always callback only DMA when mac is setup
    • Consider buffer space (x number of bytes after packet) for error communication etc.
  • Promiscuoius mode (grab everything on ETH0)
  • Memory
    • Application manages buffer and tells driver how to setup descriptors (free and dirty lists)
  • Errors
    • Need specifica on which errors and data strucutre
  • Phy init via config only acceptable
    • pooling mode on ETH0
    • pool or interrupt on other interfaces
  • AI: DDCI TAP driver interface

File System

Boot

  • Watch Dog jumper on disables RAM test
  • Need MCE handler requirements
  • TBC - no need for "Power On Reset with Watchdog" in Figure 4-1
  • AI: DDCI: Measure time from rest to POST
  • AI: DDCI: Propose codes and Datat structure for error codes
  • Confirm a register for boot to cause a reset

RTOS

  • 4.1.2.3 Interrupt latency and scheduling
    • AI: DDCI: measure crit. time values and assist with requirement updates as a result
  • AI: DDCI: RTOS-178 - propose as simple of an API as possible (pointer to hyp. dest identified as golden or writable; return success - including CRC check - or a specific error).
  • AI: MDA - Exclude Deos reuable software components from SDRIL list in SoW

BSP

  • AI: DDCI: BSP-099 - need to see if this is possile and how
  • BSP-100 - User mode interupt is what is intended
  • BSP-105 - configured at design time BUT MDA will confirm wether or not this should be done by their apps

Validation Methods and Levels

  • RTOS-176 - OK to include the two types (analysis and test) and the one level (CSCI)

Program Management

  • Add percentage complete column to program management spreadsheet

Savianos

  • TBD

PAG

  • A664 and it's future (i.e., RCIv6 ASIC vs. PCI)
  • What is Deos Porting Package?
  • Why are we calling the CFFS the Deos File System?
  • Why are we calling the Status Monitor the System Monitor?

Misc

Support Text

1) <install-root>\desk\help\openarbor-user-guide.htm (e.g., C:\DDC-I\desk\help\openarbor-user-guide.htm) 2) From within OpenArbor: Help -> Help Contents -> DDC-I Deos Documents -> Guides -> OpenArbor User Guide

Sorry to hear of your difficulties. The best/quickest way for us to assist you is for you to provide us with your OpenArbor workspace that is exhibiting the problem. The best/easiest way to get us your workspace is the following: from OpenArbor -> File -> Export -> General -> Archive File -> Next -> Select All -> Browse (to provide a location/file name) -> Finish. Then send us the resulting archive file via our secure transfer site (see below).

There is no need to encrypt your file (e.g., myWorkspace.zip), as the transmission mechanism is secure: https://deos.ddci.com/upload Username: TBD Password: <to follow in a subsequent e-mail>

Upconvert Text

In OpenArbor, right-click on zcu102 and open the dialog Properties | DDC-I Options | Deos | Integration Tool. In that tab, there is a checkbox titled "Validate XML in place". When that is unchecked, the XML is updated in the ./output/platreg-itfiles folder. You can then proceed to diff that against your XML in ./xml and merge in the changes you wish.

Upgrade Text

After installing the above, here are the high-level steps for each time you upgrade to a new version of DDS:

1 - Be sure you have a backup copy of your workspace.

2 - Open your workspace using the latest OpenArbor, and accept the dialog indicating it wants to upgrade the workspace. This is a one way function. The only way to undo this operation is to revert to your backup copy.

3 - Ensure that the conversion completed successfully by examining the warnings and errors. If there are new warnings (i.e., warnings you did not get before) please let us know via support@ddci.com. If there are errors, these must be resolved. Please contact support@ddci.com for assistance.

4 - For every DDS/desk/* file that has been "copied for editing" within the workspace, a "diff" must be performed to see if any changes we've made in the new DDS need to be ported into your workspace copies (i.e., merge our new updates into your existing files). This can be done with utilities such as: 1) beyond compare; 2) diff (bash command line); or 3) OpenArbor; we recommend OpenArbor.

The last step (syep 4) is the most important and time consuming step. Consequently, I will highlight the process (using OpenArbor) of doing the compares and merging the results.

A) In your newly converted workspace, select new -> DDC-I Deos Platform Project. In the New Platform Project dialog, select the platform(s) you are using and change the name (e.g., new-platform). Click Finish.

B) It is easiest to compare validated XML to validated XML in order to reduce differences due to new tool versions. So, For every DDS/desk/* file that has been "copied for editing" within the workspace, use the <platform-name>\output\platreg and/or <platform-name>\output\platregd folder to compare the files.

Once all changes have been merged, use Update Target Load to try your newly upgraded integration. If there are error, please contact support@ddci.com for assistance.

Training Installation Text

Please download the DDC-I Developer Suite Deos v20180426, for Windows 7 and Windows 10, from: https://deos.ddci.com/upload Username: support Password: zwap8ping2

The contents of this release include the following: 

-- OpenArbor 8.3.0.r85978 - Eclipse-based GUI
-- Deos [multicore-1524757814]- Time/Space Partitioning RTOS
   ARM PPC X86 kernel-multicore-examples network-standard-apps mpc5777c t10xx-mc s32v234-sbc zcu102 cffs deos653p1 deos653p2 deos-rtems-arm deos-rtems-ppc deos-rtems-x86 ist ist-arinc653-examples 
   Deos BSPs[qemu-arm qemu-ppc qemu-x86 ]
-- GCC 5.3.0 - C/C++ Compilers
-- TRAC 2.9.2 Build 276 - Debuggers/Simulators

To install the software, perform the following steps:

1. Extract the downloaded archive file to a location of your choice on your 

  system.

2. If possible, disable any virus-checking software for the duration of the 

  install.

3. Copy the FlexNet license file (deos-training-20180617.lic), found at the 

  root of the extracted archive, to a location of your choice on your system.

4. If you are the license administrator: Execute the file setupDDCI-LIC.exe, 

  found at the root of the extracted archive.  This will  install the  
  licensing  daemons  which allow  and support  the execution of DDC-I tools.

5. On each user system, create environment variable, DDCIFLEX_LICENSE_FILE, 

  and set it to either the path of the license file (see step 3).

6. If you are the license administrator: Execute the file setupDDCI.exe, 

  found at the root of the extracted archive.  This will  install the  
  DDC-I Developer Suite Deos v20180426.

7. If possible, exclude cirus scanning from both the DDC-I Developer Suite 

  installed root/tree as well as your Workspace root/tree.

After the DDC-I Developer Suite is installed, the user manuals are available from within OpenArbor. Launch and go to Help | Help Contents | DDC-I Deos Documents. This will bring up the documentation table of contents. We suggest you start reading the "OpenArbor User Guide" to become familiar with the product. All of the user manuals are also available in the archive and are found under the root of the archive in the directory "docs". In particular, consult the "DDS Installation Guide for Windows" if you encounter any problems during the installation.

If you have any questions/comments regarding installation, please technical support, mailto:support@ddci.com.


=

The Deos Sales Multicore 18A release (DDS-sales-deos-multicore-20180426.zip) is available for download, for the next seven days, from our temporary transfer site: https://deos.ddci.com/upload Username: embraer Password: <to follow in a subsequent e-mail>

The contents of this release include the following: 

-- OpenArbor 8.3.0.r85978 - Eclipse-based GUI
-- Deos [multicore-1524757814]- Time/Space Partitioning RTOS
   ARM PPC X86 kernel-multicore-examples network-standard-apps mpc5777c t10xx-mc s32v234-sbc zcu102 cffs deos653p1 deos653p2 deos-rtems-arm deos-rtems-ppc deos-rtems-x86 ist ist-arinc653-examples 
   Deos BSPs[qemu-arm qemu-ppc qemu-x86 ]
-- GCC 5.3.0 - C/C++ Compilers
-- TRAC 2.9.2 Build 276 - Debuggers/Simulators

To install the software, perform the following steps:

1. Extract the archive to a temporary location; refered to as $/ in the 

  directions below.

2. Disable any virus-checking software for the duration of the install.

3. Copy the FlexNet license file provided separately by DDC-I via email to a 

  location of your choice on the system.

4. If you are the license administrator: Execute the file $/setupDDCI-LIC.exe. 

  This will  install the  licensing  daemons  which allow  and support  the
  execution of DDC-I tools.

5. On each user system, create environment variable, DDCIFLEX_LICENSE_FILE, 

  and set to either port@server-name or the path to the license file (see 
  step 3).

6. If you are the license administrator: execute the file $/setupDDCI.exe. 

  You will need to specify a destination folder on your system with no
  spaces in the path name (e.g., c:\DDC-I).

After the DDC-I Developer Suite is installed, the user manuals are available from within OpenArbor. Launch and go to Help|Help Contents|DDC-I Documents. This will bring up the documentation table of contents. I suggest you start reading the "OpenArbor User Guide" to become familiar with the product. All of the user manuals are also available in the extracted tree. They are found in the directory $/docs. In particular, consult the "DDS Installation Guide for Windows" (i.e., $/dds_install_windows.html) if you encounter any problems during the installation.

If you have any questions/comments regarding this shipment, please contact mailto:support@ddci.com.

Thank you for using DDC-I products and services.

Sincerely, Bill Cronk Engineering Director DDC-I, Inc. 28057 Lupine Dr., Evergreen, CO 80439 USA Work: 602-386-4381 Mobile: 303-674-2825 mailto:bcronk@ddci.com

Retrieved from "https://ddci.zapto.org/ddciWiki/index.php?title=User:Bcronk@ddci.com&oldid=30299"