Jump to: navigation, search

Difference between revisions of "DSDP/DD/Face-to-face Toronto 22-Feb-2006"

< DSDP‎ | DD
(Minutes)
Line 5: Line 5:
  
 
== Minutes ==
 
== Minutes ==
* Eclipse 3.2 Debug Platform
+
=== Eclipse 3.2 Debug Platform ===
** Demos / feedback session on prototyping – IBM, Wind River, QNX/CDT, others?
+
* Demos / feedback session on prototyping – IBM, Wind River, QNX/CDT, others?
*** Pawel Piech - Wind River
+
** Pawel Piech - Wind River
**** Implemented directly against platform
+
*** Implemented directly against platform
**** (presentation)
+
**** The current state of the flexible hierachy aligns well with WR's debugger implementation.
+
**** Main issues at this point: 
+
***** Need retargetable actions
+
***** Need public interface to get at standard images for label providers
+
***** Column support in views is incomplete at this point
+
*** Alan Boxall
+
**** Implemented directly against platform
+
**** Moving from 3.0 to 3.1 - the biggest challenge was to get the multi-threaded UI to talk to their synchronous debug engine.
+
***** They queue up all asynchronous requests.  They use a lot of caching.
+
**** They are using the compatibility mode right now.
+
**** Taking advantage of 3.2 EDM in the future:  eventually, IBM's debug engines will drive the hieararchy.
+
**** Number of jobs is somewhat alarming.  (See performance discussions below.)
+
**** Plan to do some prototyping against flexible hierarchy after 3.2 is released.
+
*** Mikhail Khodjaiants, QNX
+
**** (presentation)
+
**** CDT has requests to provide customized versions of variables and registers view.  Probably will happen after CDT 3.2.
+
**** Using compatibility mode right now for flexibile hierarchy (for 3.1).  Still need more investigation for how to expose customization.
+
**** TI:
+
***** We need flexible hierarchy exposed at CDI layer.
+
***** We use disassmebly view.  Need a disassembly memory renderer.
+
***** Summary, they need flexibility at top and bottom.
+
***** They would like to see CDT define a more embedded-centric user experience without major changes to CDI.
+
***** Some view customizations.
+
**** Freescale:
+
***** Multi-core flexibility is important.
+
**** Nokia:
+
***** Similar comments to TI.
+
*** ATI
+
**** Builds against Eclipse platform, but haven't had a chance to look at 3.2 yet.
+
*** AMI
+
**** Builds against Eclipse platform.
+
**** Migrated an old VB debugger.  Looked at CDT and did some prototyping, but decided it would be too much work.
+
**** They are lacking some features using the platform directly, but also believe they have less problems.  One big issue was using GDB with their architecture.
+
**** First product: Oct 05 and based on 3.1.
+
**** Biggest issue is trying to use the memory view with their architecture.
+
**** Haven't prototyped against 3.2 EDM yet, but they can benefit from simplified hiearchy.  Update policies are also critically important because of very slow target connections.  Will focus on 3.2 after April.
+
**** Continually re-evaluate CDT.  Could potentially use parts of CDT.
+
*** PalmSource
+
**** Have a released product on 3.0 with a customized CDT.
+
**** Working on a 3.1-based product with un-modified CDT.  Trying to use GDB.
+
**** Also like view customization.
+
* TI: Demo of view customizations in E 3.1
+
** Variables and registers view are in table tree format (using tree control)
+
* Performance discussion
+
*** IBM will come to EclipseCon that shows performance across multiple versions
+
*** Concerns about the large numbers of working threads spawned
+
*** Will have some suggestions for performance improvements
+
*** Action items:  each company should run its own performance numbers
+
* Update Policy
+
** Progress Update – Samantha (IBM)
+
 
*** (presentation)
 
*** (presentation)
**** Slide 4Element, Model Proxy Factory, Model Proxy, and Model provided by client"Update Policy" is actually "View Updater"
+
*** The current state of the flexible hierachy aligns well with WR's debugger implementation.
*** Implementation is in the model and is model-specific.
+
*** Main issues at this point:   
*** Still work to do before we have a generic implementation.
+
**** Need retargetable actions
*** Update policy will have to be part of viewer, and model proxy will have to be part of the model.
+
**** Need public interface to get at standard images for label providers
** Need to form a workgroup to address the issues in Samantha's presentationNeed to collect use cases from folks in this group.
+
**** Column support in views is incomplete at this point
** Need to share a common look-and-feel, even if the implementation is in the model.
+
** Alan Boxall
** What's in 3.2
+
*** Implemented directly against platform
*** You can create model Proxies that tell how and when debug events are handled
+
*** Moving from 3.0 to 3.1 - the biggest challenge was to get the multi-threaded UI to talk to their synchronous debug engine.
*** Not there: a generic update policy
+
**** They queue up all asynchronous requestsThey use a lot of caching.
* Memory View
+
*** They are using the compatibility mode right now.
** Demo by Ted Williams (WR) of new renderer for memory view.
+
*** Taking advantage of 3.2 EDM in the future:  eventually, IBM's debug engines will drive the hieararchy.
** DD group would like this contributed
+
*** Number of jobs is somewhat alarming. (See performance discussions below.)
** Other features
+
*** Plan to do some prototyping against flexible hierarchy after 3.2 is released.
*** Programmatic foreground and background coloring
+
** Mikhail Khodjaiants, QNX
*** Customizable context menu
+
*** (presentation)
*** Symbol interleave with address bar
+
*** CDT has requests to provide customized versions of variables and registers view.  Probably will happen after CDT 3.2.
*** Optional confirm before write
+
*** Using compatibility mode right now for flexibile hierarchy (for 3.1)Still need more investigation for how to expose customization.
*** Undo write
+
*** TI:
*** Column headings with sub-address - user can turn on and off
+
**** We need flexible hierarchy exposed at CDI layer.
** EDM 3.2 Progress Update – Darin W (IBM)
+
**** We use disassmebly view.  Need a disassembly memory renderer.
*** Stuff in M5 (public API freeze)
+
**** Summary, they need flexibility at top and bottom.
**** Virtual tree - turned out to be more complicated than they thought.
+
**** They would like to see CDT define a more embedded-centric user experience without major changes to CDI.
**** Virtual table
+
**** Some view customizations.
**** Incremental load
+
*** Freescale:
*** Stuff not in M5
+
**** Multi-core flexibility is important.
**** Scopes / drag and drop
+
*** Nokia:
**** Columns  
+
**** Similar comments to TI.
*** Moving forward, our API's are provisional, so we can still make changes.
+
** ATI
**** March 30 - M6 feature freeze - only 3 weeks of development left
+
*** Builds against Eclipse platform, but haven't had a chance to look at 3.2 yet.
**** Columns and removing the last remaining synchronous interfaces
+
** AMI
*** What's next after the 3.2 release?
+
*** Builds against Eclipse platform.
**** How much feedback they get will determine how quickly these provisional API's can be public
+
*** Migrated an old VB debugger.  Looked at CDT and did some prototyping, but decided it would be too much work.
**** Would need feedback in first 3 months:  July - Sept
+
*** They are lacking some features using the platform directly, but also believe they have less problems.  One big issue was using GDB with their architecture.
**** The customized view content may have to go through another cycle.
+
*** First product: Oct 05 and based on 3.1.
*** 125374 - multi-column support in variables view:  patch posted.  Darin says this is close to the actual design.  Ted would like more granuality in toggling specific columns on and off.  Ted will add this to bug entry.
+
*** Biggest issue is trying to use the memory view with their architecture.
*** Plugable cell editors probably won't make the release.  Ted to look at provided a patch to possibly help get this in.
+
*** Haven't prototyped against 3.2 EDM yet, but they can benefit from simplified hiearchy.  Update policies are also critically important because of very slow target connections.  Will focus on 3.2 after April.
*** API versioning - adding new interfaces on top of old ones vs. deprecating.  When are interfaces collapsed together
+
*** Continually re-evaluate CDT.  Could potentially use parts of CDT.
**** Intention is that the adapters would live for a while in order to enable the backward-compatible debug model.
+
** PalmSource
*** Using the editor with multiple debugging backends
+
*** Have a released product on 3.0 with a customized CDT.
**** Double-click gutter action - how is this resolved when the same editor is shared between two debug engines.
+
*** Working on a 3.1-based product with un-modified CDT.  Trying to use GDB.
**** Seems to be a bigger problem that spans multiple projects:  CDT, DD, PTP
+
*** Also like view customization.
* Contributions and Participation Discussion
+
** TI: Demo of view customizations in E 3.1
** See Felix's notes
+
** Variables and registers view are in table tree format (using tree control)
** How can we get better participation to help Darin out on the debugger interfaces and views?
+
* EDM 3.2 Progress Update – Darin W (IBM)
** Where do we want to go next?  Volunteers for implementation?
+
** Stuff in M5 (public API freeze)
*** New breakpoint features?
+
*** Virtual tree - turned out to be more complicated than they thought.
*** More memory rendering?
+
*** Virtual table
*** Multi-core
+
*** Incremental load
*** Sample debugger implementation from Wind River?
+
** Stuff not in M5
*** Debug console
+
*** Scopes / drag and drop
 +
*** Columns  
 +
** Moving forward, our API's are provisional, so we can still make changes.
 +
*** March 30 - M6 feature freeze - only 3 weeks of development left
 +
*** Columns and removing the last remaining synchronous interfaces
 +
** What's next after the 3.2 release?
 +
*** How much feedback they get will determine how quickly these provisional API's can be public
 +
*** Would need feedback in first 3 months:  July - Sept
 +
*** The customized view content may have to go through another cycle.
 +
** 125374 - multi-column support in variables view:  patch posted.  Darin says this is close to the actual design.  Ted would like more granuality in toggling specific columns on and off.  Ted will add this to bug entry.
 +
** Plugable cell editors probably won't make the release.  Ted to look at provided a patch to possibly help get this in.
 +
** API versioning - adding new interfaces on top of old ones vs. deprecating.  When are interfaces collapsed together
 +
*** Intention is that the adapters would live for a while in order to enable the backward-compatible debug model.
 +
** Using the editor with multiple debugging backends
 +
*** Double-click gutter action - how is this resolved when the same editor is shared between two debug engines.
 +
*** Seems to be a bigger problem that spans multiple projects:  CDT, DD, PTP
 +
 
 +
=== Performance discussion ===
 +
* IBM will come to EclipseCon that shows performance across multiple versions
 +
* Concerns about the large numbers of working threads spawned
 +
* Will have some suggestions for performance improvements
 +
* Action items:  each company should run its own performance numbers
 +
 
 +
=== Update Policy ===
 +
* Progress Update – Samantha (IBM)
 +
** (presentation)
 +
*** Slide 4:  Element, Model Proxy Factory, Model Proxy, and Model provided by client.  "Update Policy" is actually "View Updater"
 +
** Implementation is in the model and is model-specific.
 +
** Still work to do before we have a generic implementation.
 +
** Update policy will have to be part of viewer, and model proxy will have to be part of the model.
 +
* Need to form a workgroup to address the issues in Samantha's presentation.  Need to collect use cases from folks in this group.
 +
* Need to share a common look-and-feel, even if the implementation is in the model.
 +
* What's in 3.2
 +
** You can create model Proxies that tell how and when debug events are handled
 +
** Not there: a generic update policy
 +
 
 +
=== Memory View ===
 +
* Demo by Ted Williams (WR) of new renderer for memory view.
 +
* DD group would like this contributed
 +
* Other features
 +
** Programmatic foreground and background coloring
 +
** Customizable context menu
 +
** Symbol interleave with address bar
 +
** Optional confirm before write
 +
** Undo write
 +
** Column headings with sub-address - user can turn on and off
 +
 
 +
=== Contributions and Participation Discussion ===
 +
* See Felix's notes
 +
* How can we get better participation to help Darin out on the debugger interfaces and views?
 +
* Where do we want to go next?  Volunteers for implementation?
 +
** New breakpoint features?
 +
** More memory rendering?
 +
** Multi-core
 +
** Sample debugger implementation from Wind River?
 +
** Debug console
 
* Committer List
 
* Committer List
 
** This list is based on the sub-project leads who volunteer to build use-cases and coordinate prototyping for platform improvements.  The commiters will have edit access to the Wiki and DSDP/DD CVS repository.
 
** This list is based on the sub-project leads who volunteer to build use-cases and coordinate prototyping for platform improvements.  The commiters will have edit access to the Wiki and DSDP/DD CVS repository.
Line 125: Line 129:
 
** Ewa Matejska (PalmSource)
 
** Ewa Matejska (PalmSource)
 
** Ted Williams (WR)
 
** Ted Williams (WR)
* Miscellaneous
+
 
** Eclipse 3.2 launching framework feedback
+
=== Miscellaneous ===
*** (subset of presentation from EclipseCon "Integrating Custom Debuggers into the Eclipse Platform")
+
* Eclipse 3.2 launching framework feedback
* Thursday TM/DD joint session notes
+
** (subset of presentation from EclipseCon "Integrating Custom Debuggers into the Eclipse Platform")
** Doug: Update on DSDP, Plans for EclipseCon
+
 
*** See [http://www.eclipse.org/dsdp DSDP Website].  Discussed new sub-projects:  MTJ and NAB.  Project pages will be posted in 1 to 2 weeks.
+
=== Thursday TM/DD joint session notes ===
*** All companies will be represented at EclipseCon.  Aaron S, Mikhail K, Kirk B, Tom H won't be there, though.
+
* Doug: Update on DSDP, Plans for EclipseCon
*** AI:  Doug to setup lunch tables - due by Mar 1.  Will coordinate with Doug S to not duplicate CDT areas.
+
** See [http://www.eclipse.org/dsdp DSDP Website].  Discussed new sub-projects:  MTJ and NAB.  Project pages will be posted in 1 to 2 weeks.
*** BOF - schedule at the conference.
+
** All companies will be represented at EclipseCon.  Aaron S, Mikhail K, Kirk B, Tom H won't be there, though.
** Hobston: SPIRIT
+
** AI:  Doug to setup lunch tables - due by Mar 1.  Will coordinate with Doug S to not duplicate CDT areas.
*** (2 presentations)
+
** BOF - schedule at the conference.
*** First presentation - SPIRIT for EDA - this is more for information
+
* Hobston: SPIRIT
*** Second presentation - SPIRIT for Debuggers
+
** (2 presentations)
*** Debug working group is probably needed to drive the SPIRIT definition.
+
** First presentation - SPIRIT for EDA - this is more for information
**** Ideal if Eclipse could join the consortium.  ARM and Mentor can be interfaces, too.
+
** Second presentation - SPIRIT for Debuggers
**** Hobson could work on setting up the debug working group.  Hobson will also check on what they can make available for parsers.  Hobson will check on licensing of SPIRIT XML files.
+
** Debug working group is probably needed to drive the SPIRIT definition.
*** Next steps
+
*** Ideal if Eclipse could join the consortium.  ARM and Mentor can be interfaces, too.
**** Each member company to look into joining SPIRIT
+
*** Hobson could work on setting up the debug working group.  Hobson will also check on what they can make available for parsers.  Hobson will check on licensing of SPIRIT XML files.
**** DSDP-DD and DSDP-TM to nominate representative for a debug working group
+
** Next steps
**** DSDP-DD and/or DSDP-TM to build tools for generating/reading/validating SPIRIT files.  AI for Aaron to talk to company about potential contributions.  No Java Parser available yet for SPIRIT - we could contribute this in DD.
+
*** Each member company to look into joining SPIRIT
** Doug - WR's data files standards
+
*** DSDP-DD and DSDP-TM to nominate representative for a debug working group
*** Two feature requests from SPIRIT
+
*** DSDP-DD and/or DSDP-TM to build tools for generating/reading/validating SPIRIT files.  AI for Aaron to talk to company about potential contributions.  No Java Parser available yet for SPIRIT - we could contribute this in DD.
**** Board initialization specification
+
* Doug - WR's data files standards
**** Help file indexing so registers can point to Silicon Vendor's pdf/html manuals
+
** Two feature requests from SPIRIT
**** Flow:  SoC describes silicon -> Board vendor describes hardware and initialization -> user customizes initialization.   
+
*** Board initialization specification
** Aaron Spear - general discussion on SPIRIT requirements
+
*** Help file indexing so registers can point to Silicon Vendor's pdf/html manuals
*** (presentation)
+
** Flow:  SoC describes silicon -> Board vendor describes hardware and initialization -> user customizes initialization.   
*** Feedback on additional register spec requirements
+
* Aaron Spear - general discussion on SPIRIT requirements
**** Unique ID
+
** (presentation)
**** Initial grouping, but ability for a user to change groups
+
** Feedback on additional register spec requirements
**** Textual descriptions - problematic for I18N - how should SPIRIT handle?
+
*** Unique ID
**** Mapping between debug format and registers - does this belong in SPIRIT or elsewhere?
+
*** Initial grouping, but ability for a user to change groups
**** Disassembly information should be a part of this - eventually we'd like table-driven disassembly - separate discussion
+
*** Textual descriptions - problematic for I18N - how should SPIRIT handle?
**** Endianness, default display size:  byte, word, long, double, etc.
+
*** Mapping between debug format and registers - does this belong in SPIRIT or elsewhere?
**** Help index
+
*** Disassembly information should be a part of this - eventually we'd like table-driven disassembly - separate discussion
**** Long description for tool tip
+
*** Endianness, default display size:  byte, word, long, double, etc.
*** Feedback on additional memory spec requirements
+
*** Help index
**** Flash - should be a separate discussion - CFI standard (?)
+
*** Long description for tool tip
**** Cache
+
** Feedback on additional memory spec requirements
**** Virtual - should be a separate topic - ATI limited the XML to what's physically on the chip. - need to describe MMU structure
+
*** Flash - should be a separate discussion - CFI standard (?)
**** Need to think about run-time memory map changes that are tied to the OS.  Debugger will need to look at the MMU structure and also need to know about kernel data structures to handle the effective-to-physical address translation.
+
*** Cache
**** Shared memory between cores
+
*** Virtual - should be a separate topic - ATI limited the XML to what's physically on the chip. - need to describe MMU structure
 +
*** Need to think about run-time memory map changes that are tied to the OS.  Debugger will need to look at the MMU structure and also need to know about kernel data structures to handle the effective-to-physical address translation.
 +
*** Shared memory between cores

Revision as of 17:03, 23 February 2006

Agenda & Attendee List

Presentations

Minutes

Eclipse 3.2 Debug Platform

  • Demos / feedback session on prototyping – IBM, Wind River, QNX/CDT, others?
    • Pawel Piech - Wind River
      • Implemented directly against platform
      • (presentation)
      • The current state of the flexible hierachy aligns well with WR's debugger implementation.
      • Main issues at this point:
        • Need retargetable actions
        • Need public interface to get at standard images for label providers
        • Column support in views is incomplete at this point
    • Alan Boxall
      • Implemented directly against platform
      • Moving from 3.0 to 3.1 - the biggest challenge was to get the multi-threaded UI to talk to their synchronous debug engine.
        • They queue up all asynchronous requests. They use a lot of caching.
      • They are using the compatibility mode right now.
      • Taking advantage of 3.2 EDM in the future: eventually, IBM's debug engines will drive the hieararchy.
      • Number of jobs is somewhat alarming. (See performance discussions below.)
      • Plan to do some prototyping against flexible hierarchy after 3.2 is released.
    • Mikhail Khodjaiants, QNX
      • (presentation)
      • CDT has requests to provide customized versions of variables and registers view. Probably will happen after CDT 3.2.
      • Using compatibility mode right now for flexibile hierarchy (for 3.1). Still need more investigation for how to expose customization.
      • TI:
        • We need flexible hierarchy exposed at CDI layer.
        • We use disassmebly view. Need a disassembly memory renderer.
        • Summary, they need flexibility at top and bottom.
        • They would like to see CDT define a more embedded-centric user experience without major changes to CDI.
        • Some view customizations.
      • Freescale:
        • Multi-core flexibility is important.
      • Nokia:
        • Similar comments to TI.
    • ATI
      • Builds against Eclipse platform, but haven't had a chance to look at 3.2 yet.
    • AMI
      • Builds against Eclipse platform.
      • Migrated an old VB debugger. Looked at CDT and did some prototyping, but decided it would be too much work.
      • They are lacking some features using the platform directly, but also believe they have less problems. One big issue was using GDB with their architecture.
      • First product: Oct 05 and based on 3.1.
      • Biggest issue is trying to use the memory view with their architecture.
      • Haven't prototyped against 3.2 EDM yet, but they can benefit from simplified hiearchy. Update policies are also critically important because of very slow target connections. Will focus on 3.2 after April.
      • Continually re-evaluate CDT. Could potentially use parts of CDT.
    • PalmSource
      • Have a released product on 3.0 with a customized CDT.
      • Working on a 3.1-based product with un-modified CDT. Trying to use GDB.
      • Also like view customization.
    • TI: Demo of view customizations in E 3.1
    • Variables and registers view are in table tree format (using tree control)
  • EDM 3.2 Progress Update – Darin W (IBM)
    • Stuff in M5 (public API freeze)
      • Virtual tree - turned out to be more complicated than they thought.
      • Virtual table
      • Incremental load
    • Stuff not in M5
      • Scopes / drag and drop
      • Columns
    • Moving forward, our API's are provisional, so we can still make changes.
      • March 30 - M6 feature freeze - only 3 weeks of development left
      • Columns and removing the last remaining synchronous interfaces
    • What's next after the 3.2 release?
      • How much feedback they get will determine how quickly these provisional API's can be public
      • Would need feedback in first 3 months: July - Sept
      • The customized view content may have to go through another cycle.
    • 125374 - multi-column support in variables view: patch posted. Darin says this is close to the actual design. Ted would like more granuality in toggling specific columns on and off. Ted will add this to bug entry.
    • Plugable cell editors probably won't make the release. Ted to look at provided a patch to possibly help get this in.
    • API versioning - adding new interfaces on top of old ones vs. deprecating. When are interfaces collapsed together
      • Intention is that the adapters would live for a while in order to enable the backward-compatible debug model.
    • Using the editor with multiple debugging backends
      • Double-click gutter action - how is this resolved when the same editor is shared between two debug engines.
      • Seems to be a bigger problem that spans multiple projects: CDT, DD, PTP

Performance discussion

  • IBM will come to EclipseCon that shows performance across multiple versions
  • Concerns about the large numbers of working threads spawned
  • Will have some suggestions for performance improvements
  • Action items: each company should run its own performance numbers

Update Policy

  • Progress Update – Samantha (IBM)
    • (presentation)
      • Slide 4: Element, Model Proxy Factory, Model Proxy, and Model provided by client. "Update Policy" is actually "View Updater"
    • Implementation is in the model and is model-specific.
    • Still work to do before we have a generic implementation.
    • Update policy will have to be part of viewer, and model proxy will have to be part of the model.
  • Need to form a workgroup to address the issues in Samantha's presentation. Need to collect use cases from folks in this group.
  • Need to share a common look-and-feel, even if the implementation is in the model.
  • What's in 3.2
    • You can create model Proxies that tell how and when debug events are handled
    • Not there: a generic update policy

Memory View

  • Demo by Ted Williams (WR) of new renderer for memory view.
  • DD group would like this contributed
  • Other features
    • Programmatic foreground and background coloring
    • Customizable context menu
    • Symbol interleave with address bar
    • Optional confirm before write
    • Undo write
    • Column headings with sub-address - user can turn on and off

Contributions and Participation Discussion

  • See Felix's notes
  • How can we get better participation to help Darin out on the debugger interfaces and views?
  • Where do we want to go next? Volunteers for implementation?
    • New breakpoint features?
    • More memory rendering?
    • Multi-core
    • Sample debugger implementation from Wind River?
    • Debug console
  • Committer List
    • This list is based on the sub-project leads who volunteer to build use-cases and coordinate prototyping for platform improvements. The commiters will have edit access to the Wiki and DSDP/DD CVS repository.
    • Paul Gingrich (TI)
    • Samantha Chan (IBM)
    • Ken Ryall (Nokia)
    • Kirk Beitz (Freescale)
    • Ewa Matejska (PalmSource)
    • Aaron Spear (Mentor)
    • Chris Recoskie (TI)
    • Darin Wright (IBM)
    • Pawel Piech (Wind River)
    • Pete Nichols (IBM)
    • Ewa Matejska (PalmSource)
    • Ted Williams (WR)

Miscellaneous

  • Eclipse 3.2 launching framework feedback
    • (subset of presentation from EclipseCon "Integrating Custom Debuggers into the Eclipse Platform")

Thursday TM/DD joint session notes

  • Doug: Update on DSDP, Plans for EclipseCon
    • See DSDP Website. Discussed new sub-projects: MTJ and NAB. Project pages will be posted in 1 to 2 weeks.
    • All companies will be represented at EclipseCon. Aaron S, Mikhail K, Kirk B, Tom H won't be there, though.
    • AI: Doug to setup lunch tables - due by Mar 1. Will coordinate with Doug S to not duplicate CDT areas.
    • BOF - schedule at the conference.
  • Hobston: SPIRIT
    • (2 presentations)
    • First presentation - SPIRIT for EDA - this is more for information
    • Second presentation - SPIRIT for Debuggers
    • Debug working group is probably needed to drive the SPIRIT definition.
      • Ideal if Eclipse could join the consortium. ARM and Mentor can be interfaces, too.
      • Hobson could work on setting up the debug working group. Hobson will also check on what they can make available for parsers. Hobson will check on licensing of SPIRIT XML files.
    • Next steps
      • Each member company to look into joining SPIRIT
      • DSDP-DD and DSDP-TM to nominate representative for a debug working group
      • DSDP-DD and/or DSDP-TM to build tools for generating/reading/validating SPIRIT files. AI for Aaron to talk to company about potential contributions. No Java Parser available yet for SPIRIT - we could contribute this in DD.
  • Doug - WR's data files standards
    • Two feature requests from SPIRIT
      • Board initialization specification
      • Help file indexing so registers can point to Silicon Vendor's pdf/html manuals
    • Flow: SoC describes silicon -> Board vendor describes hardware and initialization -> user customizes initialization.
  • Aaron Spear - general discussion on SPIRIT requirements
    • (presentation)
    • Feedback on additional register spec requirements
      • Unique ID
      • Initial grouping, but ability for a user to change groups
      • Textual descriptions - problematic for I18N - how should SPIRIT handle?
      • Mapping between debug format and registers - does this belong in SPIRIT or elsewhere?
      • Disassembly information should be a part of this - eventually we'd like table-driven disassembly - separate discussion
      • Endianness, default display size: byte, word, long, double, etc.
      • Help index
      • Long description for tool tip
    • Feedback on additional memory spec requirements
      • Flash - should be a separate discussion - CFI standard (?)
      • Cache
      • Virtual - should be a separate topic - ATI limited the XML to what's physically on the chip. - need to describe MMU structure
      • Need to think about run-time memory map changes that are tied to the OS. Debugger will need to look at the MMU structure and also need to know about kernel data structures to handle the effective-to-physical address translation.
      • Shared memory between cores