1997
DOI: 10.1109/54.587736
|View full text |Cite
|
Sign up to set email alerts
|

System-on-a-chip cosimulation and compilation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
27
0

Year Published

1997
1997
2007
2007

Publication Types

Select...
4
2
2

Relationship

0
8

Authors

Journals

citations
Cited by 37 publications
(27 citation statements)
references
References 8 publications
0
27
0
Order By: Relevance
“…Only a handful of years ago, it was easy enough to hook a probe to the memory and I/O buses, but, with the advent of systems on a chip and application-specific integrated circuits, it is no longer possible to obtain those signals for they never leave the silicon [27], [35]. The only way to debug these systems is to either probe the silicon itself (a bit unrealistic) or to add logic to the chip to bring the desired signal off the chip; the latter option is limited by the number of physical pins that can be put on a chip and spared for simple debug and evaluation purposes.…”
Section: Motivationmentioning
confidence: 99%
“…Only a handful of years ago, it was easy enough to hook a probe to the memory and I/O buses, but, with the advent of systems on a chip and application-specific integrated circuits, it is no longer possible to obtain those signals for they never leave the silicon [27], [35]. The only way to debug these systems is to either probe the silicon itself (a bit unrealistic) or to add logic to the chip to bring the desired signal off the chip; the latter option is limited by the number of physical pins that can be put on a chip and spared for simple debug and evaluation purposes.…”
Section: Motivationmentioning
confidence: 99%
“…C-VHDL (or Verilog) environments can be developed [18]. Most commercial HDL simulators support the execution of external C functions for this purpose.…”
Section: Related Workmentioning
confidence: 99%
“…Nevertheless they are adequate just in the very first stage of the development, before the HW/SW partitioning, because the HW and SW design flows need different techniques and different tools when the abstraction level decreases toward a real implementation. [3][4][5][6] use distinct simulation engines and different language descriptions for the hardware and the software side. This allows to use levels of abstraction lower than the behavioral one, and to evaluate the software in its compiled (binary code) form.…”
Section: Co-simulation Environmentsmentioning
confidence: 99%