Jump to content

tjroamer

Members
  • Content Count

    10
  • Joined

  • Last visited

  1. Hi, the subelement clockInterfaceRef and resetInterfaceRef can be useful for bus interface specification. They have been mentioned once in the specification in the section 5.12: If the clock and reset ports are associated with the protocol of a bus interface, the special purpose clock or reset busInterface (see 6.5.1) can be referenced from any bus interface using the clockInterfaceRef and resetInterfaceRef subelements. However, the clockInterfaceRef and resetInterfaceRef are missing in the xsd schema, also, there is no other hints how to specify them. BR /Kenny
  2. Is this a design flaw in the IP-XACT standard? I think address spaces should have belonged to "Design" top level element instead of "Component". What is the rational behind this design decision?
  3. This is correct. The p_INT is not TLM style, but since I have to generate a systemc model, which contains both signal and transactional level ports in one component. These ports need to be assigned to a view for the design configuration. In this case, I assigned all of the systemc-relevant ports and sockets to TLM view. Not very accurate, but I don't see any better solutions so far.
  4. In our design, there are one processor, one bus and several peripherals. Is it possible to create a memory map from the master port to all of the slave ports of the peripherals? For different designs, the memory map should be different. Finally I want to generate information from IP-XACT files like the following: DesignCfg1: ARM.IAHB: Peri1.AHB: 0x2000_0000 - 0x2000_FFFF .... Perix.AHB: 0x3000_0000 - 0x3000_0FFF ARM.DAHB: Peri1.AHB: 0x4000_0000 - 0x4000_FFFF .... Perix.AHB: 0x4001_0000 - 0x4001_0FFF DesignCfg2: ARM.IAHB: Peri1.AHB: 0x1000_0000 - 0x1000_FFFF .... Perix.AHB: 0x2000_0000 - 0x2000_0FFF ARM.DAHB: Peri1.AHB: 0x3000_0000 - 0x3000_FFFF .... Perix.AHB: 0x3001_0000 - 0x3001_0FFF I cannot do that in the processor local address space, because the processor has to be instantiated many times with different address mappings to the master ports. In fact, this information belongs to design.
  5. Hi Erwin, thanks for your answer. I overlooked that topic. Now it is clear to me, in my case, I have to define two ports in the model->ports element, and then assign TLM view to p_INT and RTL view to p_int with language specific data type using wireTypeDefs Best regards, /Kenny
  6. Hi, I am just curious whether it is possible to represent both TLM and RTL variant in one single IP-XACT file. For a component, we have only one model node, which contains serveral ports. The component can also have bus interfaces sitting at a higher level. For a specific model port, I have two variants, let's say: VHDL: p_int: std_logic SystemC: p_INT: sc_in<bool> Note that they have different names. I need to specify a specific name in the port node. The current solution is that I generate two IP-XACT files, one for RTL and the other for TLM, both have their specific different name in the file. I checked out the Leon2 example, where I found two different component IP-XACT file sets Leon2RTL and Leon2TLM, where for instance the component dma has been defined twice. My question is: is this an intended use case for the IP-XACT to apply one single IP-XACT file to represent two variants with different languages? Thanks.
  7. tjroamer

    IEEE 1685-2014 and TGI.WSDL specification

    I am also missing the wsdl file for the 1685-2014. Have you been able to discuss with the members about this? Thanks, /kenny
  8. for your case, I would choose to design a primitive channel to realize your requirement. This channel should be very similar to the sc_fifo, except that the element can be read/written with a given index or a specific order. I don't think using the build-in language elements to do this is a elegant way, since you may be changing the semantics of these elements. To implement it, just take a look at the sc_fifo implement. /Kenny
  9. Hi, I am trying the Leon2 example contained in the ip-xact standard pacakge. My intention is to run the tcl tgi generator using the WSDL. However, I cannot manage them to work due to the missing SOAP::WSDL tcl package. See the tcl generator file: \Leon2_1685-2014\Leon2\spiritconsortium.org\Leon2RTL\ahbbus\1.2\componentGenerator\defaultMaster.tcl: package require SOAP::WSDL By searching this pacakge in google I did not get any useful information. It seems that this package is pretty old and has been discontinued already in 2005. I am suprised that the Leon2 example is using a TCL package which the user cannot find in the internet. Could anybody tell me where I can download the SOAP::WSDL tcl pacakge? What I found is only the Wub from google, but I cannot get it to work with the Leon2 example. If anybody has already made the generator example work, I am very much appreciated to get an instruction how to do that. Thanks in advance. /Kenny
  10. tjroamer

    Error <E533>

    You could have other constructors in your Derived class. When you create the instance D, the constructor Derived(sc_module_name name):sc_module(name){} is not called, instead, a constructor like Derived(const char* par) {} is called. You may need to check the body of the Derived class.
×