1 / 16

Presenter : Shao- Cheih Hou

A Debug Probe for Concurrently Debugging Multiple Embedded Cores and Inter-Core Transactions in NoC -Based Systems Shan Tang and Qiang Xu Department of Computer Science & Engineering The Chinese University of Hong Kong, Shatin , N.T., Hong Kong. Presenter : Shao- Cheih Hou.

thimba
Download Presentation

Presenter : Shao- Cheih Hou

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Debug Probe for Concurrently Debugging Multiple Embedded Cores and Inter-Core Transactions in NoC-Based SystemsShan Tang and QiangXuDepartment of Computer Science & EngineeringThe Chinese University of Hong Kong, Shatin, N.T., Hong Kong Presenter : Shao-CheihHou Sight count : 11 ASPDAC ‘08

  2. Abstract • Existing SoC debug techniques mainly target bus-based systems. They are not readily applicable to the emerging system that use Networkon-Chip (NoC) as on-chip communication scheme. In this paper, we present the detailed design of a novel debug probe (DP) inserted between the core under debug (CUD) and the NoC. With embedded configurable triggers, delay control and timestamping mechanism, the proposed DP is very effective for inter-core transaction analysis as well as controlling embedded cores’ debug processes. Experimental results show the functionalities of the proposed DP and its area overhead1.

  3. What’s the problem? • More and more IP connect on bus in SoC • Single bus is not efficiency • Full connect is too complex and high cost • Network is a good way for chip(NoC) • In NoC, too many IPs need to verification • Design for debug => debug platform • Debug need more flexible • Programmabletrigger • Trace (timestamping) • Delay control • Run stop • Debug prob

  4. Related works Internal nodes[21] Monitor for NoC[7,8] Tracing[1,3,12,13,22] JTAG[21] Coresight[4] DfD for embedded cores[4] Open Core peotocol[15] interface Silicon debug platform Debug method This paper

  5. Debug platform architecture • Debug software • Software control • Each core structure config • Driver match • Off-chip debug controller • OCP and JTAG interface • Command I/O • Data output • On-chip debug architecture • DA(debug agent) • DP(debug probe)

  6. DA (Debug Agent) 6 • Receive/send debug command/data from/to Off-chip Debug Controller by using system JTAG port • Change debug command to package form, and passing to specific CUD or DP • Receive package form network and change to debug data

  7. Debug Probe-Overview

  8. Debug Access Module • Connect to Network interface(NI) • OCP protocol (slave interface) • Memory-map for each DP • Control the delay of the debug probe • For data synchronize

  9. Core Debug Module • JTAG Interface • Another way to configure the delay control • ARM ICE JTAG protocol use in this paper

  10. Core Trace Module • Dump trace data from core by bus • Solve “many-to-one” • Time slot for each core under debug • Trace bandwidth : TD(i)~Bchip(TS(()

  11. Transaction Trace Module • Trigger Unit • Control for config • Detector as comparator • MUX for output record • Trace Unit • Trace after trigger • Shadow buffer for start cycle • Record package • Record format

  12. DP Programming Module • The method for DP setup and run

  13. Experimental Result • Environment setup • ARM EICE JTAG • OCP protocol • Function Test – delay R/W

  14. Experimental Result(cont.) • Function Test – Transaction operation • Area of DP

  15. Conclusion • The paper propose a debug platform • For complex NoC base • Bus config and JTAG parallel • Trace for both core information and protocol information • Reconfigurable HW

  16. My Comment • Similar as problem in my target • NoC(not bus system) debug • Memory interface signal trace • JTAG and interconnect debug parallel • Problem for this paper • Only the simulation, no real case • Area analyze only for DP, not all the platform • No detail for SW and off-chip debug controller

More Related