ACM Home Page
Please provide us with feedback. Feedback
Hardware/software IP integration using the ROSES design environment
Full text PdfPdf (755 KB)
Source
ACM Transactions on Embedded Computing Systems (TECS) archive
Volume 6 ,  Issue 3  (July 2007) table of contents
Article No. 17  
Year of Publication: 2007
ISSN:1539-9087
Authors
Flávio R. Wagner  UFRGS---Instituto de Informática, Porto Alegre, Brazil
Wander Cesário  MND (Methodologies & Designs), Montigny-Le-Bretonneux, France
Ahmed A. Jerraya  TIMA Laboratory, Grenoble, France
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 11,   Downloads (12 Months): 89,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1275986.1275989
What is a DOI?

ABSTRACT

Considering current time-to-market pressures, IP reuse is mandatory for the design of complex embedded systems-on-chip (SoC). The integration of IP components into a given design is the most complex task in the whole reuse process. This paper describes the IP integration approach implemented in the ROSES design environment, which presents a unique combination of features that enhance IP reuse: automatic assembly of interfaces between heterogeneous software and hardware IP components; easy adaptation to different on-chip communication structures and bus and core standards; generation of customized and minimal OSs for programmable components; and an architecture-independent high-level API embedded into SystemC that makes application software independent from system implementation. Application code is written by using communication functions available in this API. ROSES automatically assembles wrappers that implement these functions, such that the application code does not need to be modified in order to run in the final synthesized system.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
ARM AMBA. 2005. http://www.arm.com/armwww.nsf/html/AMBA/
2
3
4
 
5
 
6
Böke, C. 2000. Combining two customization approaches: Extending the customization tool TEReCS for software synthesis of real-time execution platforms. In Proceedings of the Workshop on Architectures of Embedded Systems.
7
8
9
 
10
CoWare, Inc. 2005. http://www.coware.com
 
11
 
12
Diaz-Nava, M. and Okvist, G. 2002. The Zipper prototype: A complete and flexible VDSL multicarrier solution. IEEE Communications Magazine 40, 92--105.
 
13
Gauthier, L., Yoo, S., and Jerraya, A. A. 2001. Automatic generation and targeting of application specific operating systems and embedded systems software. IEEE Transactions on CAD of Integrated Circuits 20, 1293--1301.
 
14
IBM CoreConnect Bus Architecture. 2005. http://www3.ibm.com/chips/products/coreconnect/index.html
 
15
Keutzer, K., Malik, S., Richard Newton, A., Rabaey, J., and Sangiovanni-Vincentelli, A. 2000. System-level design: Orthogonalization of concerns and platform-based design. IEEE Transactions on CAD of Integrated Circuits 19, 1523--1543.
16
 
17
Mentor Graphics. 2005. http://www.mentor.com
 
18
Open Core Protocol. 2005. http://www.ocpip.org
19
 
20
Rammig, F. 2000. Web-based system design with components off the shelf. In Proceedings of the Forum on Design Languages.
21
22
 
23
Shandle, J. and Martin, G. 2002. Making embedded software reusable for SoCs. EEDesign.
24
 
25
Sonics SiliconBackplane MicroNetwork. 2005. http://www.sonicsinc.com
 
26
SPIRIT consortium. 2005. http://www.spiritconsortium.com
 
27
SystemC. 2005. http://www.systemc.org
 
28
Virtual Socket Interface Alliance. 2005. http://www.vsi.org
 
29
XML Specification, W3C Recommendation. 2005. available at: http://www.w3c.org/XML.

Collaborative Colleagues:
Flávio R. Wagner: colleagues
Wander Cesário: colleagues
Ahmed A. Jerraya: colleagues