Jump to content

Justin Huang

  • Content Count

  • Joined

  • Last visited

About Justin Huang

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Erwin, Why are the '-c' and '-o' options discarded in the buildCommand section for .o target? If the command to build a target, e.g., tgt.out from input.txt, is ' exe -i input.txt -o a -opta x -optb y -optc z ', where the '-o' option does not mean output, how to map this command to 'ipxact:command, ipxact:flags, and ipxact:targetName, ipxact:dependency'? Does ipxact has assumption that each build command should have -o option which means output, and -c option for dependency? How can I know which option should be remved from ipxact:flags? Thanks, Justin
  2. Hi Erwin, What if we used customized inhouse tool to compile hello.c into hello.s (assembly code) and then generate hello.o from hello.s as shown below. how to describe it in IP-XACT XML? hello.s: hello.c cmd1 flags1 cmd2 flags2 hello.o: hello.s cmd3 flags3 2nd question: if hello.c includes a few headers, e.g., a.h, b.h, ..., should these header files be listed as dependency in IP-XACT XML?
  3. Hi, I'd like to encode the .o/.so buildCommand in IPXACT XML fileSet, such that user can rebuild the .o/.so file from XML. For example, the .o/.so generation command look like this: % g++ -c hello.cpp -o hello.o % g++ hello.o -shared -fPIC -o libhello.so Should I encode XML fileSet like below? <ipxact:fileSet> <ipxact:file> <ipxact:name>hello.cpp</ipxact:name> <ipxact:fileType>cppSource</ipxact:fileType> </ipxact:file> <ipxact:file> <ipxact:name>hello.so</ipxact:name> <ipxact:fileType>s
  4. I'd like to describe IP documents, e.g., user guide, in IP-XACT XML file. I did not find any example showing how to describe docs in IP-XACT XML, I added a Documentation view, documentation componentInstantiation and fileSets as shown below, is it recommended way? <ipxact:component ...> ... <ipxact:model> <ipxact:views> <ipxact:view> <ipxact:name>Documentation</ipxact:name> <ipxact:envIdentifier>::</ipxact:envIdentifier> <ipxact:component
  5. I did not get much results on TGI implementation from Google search. So I'll try my luck here to see if there is any TGI library example available and seek suggestions on TGI library implementation.
  6. Hi Erwin, I'd like to know the VLNV of sub IPs, i.e., SUB_IP_X/Y/Z used in IP_A. As some sub-modules in IP_A have no IP-XACT component XML description, if I write a design xml for IP_A, then we cannot reconstruct RTL of IP_A using the ipxact:componentInstance and the ipxact:interconnection/adHocConnection info in the ipxact:design description. It seems IP-XACT spec does not define if it is valid to use a design xml in which the design has sub-modules with no IP-XACT component xml description. Or you can describe sub-IPs in XML containing file sets only. SUB_IP_X/Y/Z alread
  7. Hi, Suppose we have an IP, e.g., IP_A, which instantiates a few sub-IPs, e.g., SUB_IP_X/Y/Z (which have ipxact component xml), and a few sub-modules which are not packaged in IP-XACT component XML. I'd like to track all the sub-IPs used by IP_A, but am not sure if ipxact:design is the right choice to describe the design hierarchy as the sub-level of IP_A includes both sub-IPs described using IP-XACT and sub-units that are not packaged using IP-XACT. Thanks, Justin
  • Create New...