1-26,27-2015: Oxford

Introduction, Roadmap, and Concepts

• Purpose: please give feedback
  
• What is the RPT? Context, design model
• Roadmap of workshop
• Summarize lessons, reverse order
• Concepts: RCE, interconnect, etc
• RCE intro: block diagrams, DPM connect
• CI intro: explain clustering (Gregg focus on COB later)
• Roles and responsibilities matrix
  
• ATCA intro: naming COB elements: front-board, rtm concept, shelf, dpm/dtm
• S/W intro: RCE embedded, host side; SDK concepts
• Work in progress intro: this is an intro workshop; protocol plugin model, but not going to
  cover firmware development in workshop; no PGP; documentation
  
• Mark create glossary and post
  

Overview of ATCA and the COB

• ATCA tutorial, concepts and ideas, fair detail
• Bsi, shelf configuration ??
  
• Drill down to COB
  

Tools and Installation

• Supported platforms
• Introduce what SDK is and what it's for: development and maintenance (host-side),
  point forward to Sergio's talk; hit some keywords of this process to set up Sergio; it's
  not a build system!
• Build conventions: major-minor-patch
• Show communication path that admin tools talk across
• Installing the SDK
• git: space requirements, time
• Who doing JTAG and DTM consoles?
• cross-compiler installation
• Host tools in SDK: atca_fu (e.g., atca_dump), identify, rebooter, con_reset
• Terminal shell, getting on the RCE

Shelf Installation, Networking, and Administration

• (Start from abstraction - a box on a network)
• Networking use cases - describe various and pick them most interesting;
  other cases offline Tuesday
• ( ATCA vs. IP philosophy/dichotomy )
• Then pick one of the use cases and walk through it practical detail
• By the end of talk, shelf with green lights and proper configuration

RPT Software Development and the SDK

• Core
  • RCE can query the bsi and shelf configuration info
  • Embedded development, RTEMS, including utilities like mdump, ldump wdump, etc
  • What added features - RTEMs for the RCE
• SDK
  • Emphasize SDK is not a build system
• Protocol plugins

User Support and Documentation

Notes

• We are committed to providing support: (a) small team supporting lots of folks, (b) work in progress,
  emphasize that talk to us through issue tracking/forums, (c) can't give implementation consulting support
• Emphasize that we;re here at workshop to collect feedback and gather support needs
• All API reference information will end up in Doxygen
• Questions to guide feedback:
  • Level of detail good or bad?
  • Topics missed?
  • Examples useful?