Systemc: From the ground up

SystemC: From the Ground Up

Volumn , Issue , 2005, Pages 1-279

  Black, David C ^a   Bunton, Bill ^b   Donovan, Jack ^c   Keist, Anna ^a  

^a XtremeEDA   (United States)

^b LSI Corporation   (United States)

^c HighIP Design Company   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84892230515     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/978-0-387-69958-5     Document Type: Book

References (31)

1. We will see later that SystemC is actually a C++ class library that "sits on top" of C++.
2. This scenario describes a recent experience by one of the authors.
3. Gajski and L. Cai, "Transaction Level Modeling," First IEEE/ACM/IFIP International Conference on Hardware/Software Codesign and System Synthesis (CODES+ISSS 2003), Newport Beach, CA, October 1, 2003
4. SPW is available from CoWare, Inc. (www.coware.com).
5. CoCentric System Studio is available from Synopsys, Incorporated (www.synopsys.com).
6. For example, the book, Microelectrofluidic Systems: Modeling and Simulation by Tianhao Zhang et al., CRC Press, ISBN: 0849312760, describes applying SystemC to a non-electronic system.
7. For some installations, dynamic libraries may also be referenced if using the SystemC Verification library.
8. See AMBA AHB Cycle-Level Interface Specification at www.arm.com.
9. SC-CTHREAD is a special case of SC-THREAD. This process type is a thread process that has the requirement of being sensitive to a clock. SC-CTHREAD is under consideration for deprecation; however, several synthesis tools depend on it at the time of writing.
10. Discussed later.
11. This implementation takes advantage of the linearly scaled 53-bit integer mantissa inside a 64-bit IEEE-754 compatible floating-point unit. On processors without an FPU, this behavior must be emulated in software, and there will be no speed advantage.
12. This naming convention is not without some controversy in some programming circles; however, most groups have accepted it and deal with the name mismatch.
13. cpp is the C/C++ pre-processor that handles # directives such as # define.
14. However, see the last section of this chapter for a preview of upcoming features.
15. SC-CTHREAD is discussed in a later chapter on Additional Topics.
16. This queue is limited only by the resources of the simulation machine itself.
17. Kahn, G. (1974). The semantics of a simple language for parallel programming. In J.L. Rosenfeld (Ed.), Proceedings of IFIP Congress 74 (pp.471-475). Amsterdam: North-Holland.
18. It is unclear whether the concepts discussed here have any application outside of electrical signals.
19. This usage may surprise non-HDL experienced folks. HDL-experienced users should understand the VHDL or Verilog analogy.
20. Future versions of C++ compiler/linker tool sets may fix this restriction.
21. However, without an interface, a SystemC channel cannot be used with a SystemC port.
22. If you are having a hard time with this syntax, refer to the C++ scope resolution operator in Appendix A.
23. See next section for a discussion of specialized ports.
24. The prefix ef is a convention. Some groups might prefer a suffix, ef. In any case, a convention should be adopted.
25. Some of this syntax was provided for backwards compatibility with earlier versions of SystemC (specifically 1.x).
26. SC-FATAL is discussed in Chapter 14, Additional Topics.
27. See the manual page for getenv in a Linux environment.
28. Available from http://www.cs.man.ac.uk/apt/tools/gtkwave
29. The inquisitive reader may choose to research Lamda calculus to understand the reasons for this. Basically, the SCV needs to store equations to allow it to do constraint solving.
30. We ask this question from an electronic system design perspective, not from a philosophical perspective.
31. Actis Design www.actisdesign.com.