Jump to content

Khushi

Members
  • Content Count

    69
  • Joined

  • Last visited

About Khushi

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Thank you Erwin. Does it mean, instead of following <ipxact:field><ipxact:pathSegments> <ipxact:pathSegment> <ipxact:pathSegmentName>system.comp.reg.fld</ipxact:pathSegmentName> </ipxact:pathSegment> </ipxact:pathSegments> </ipxact:field> I should put it like the following(to avoid '.' in pathSegment) <ipxact:field><ipxact:pathSegments> <ipxact:pathSegment> <ipxact:pathSegmentName>syst
  2. Hello All In IPXact, how we can specify the field access path ? For example, if their is a field 'fld' in a register 'reg" which access path 'system.comp.reg.fld' then, can we store the full path at field itself or do we need to store a part at addressBlock, another part at register and remianing at field level and in the later case need to concatnate the paths to get full hdl path of the field. Which one is recommended Can we store the full path at field itself as below <ipxact:field> <ipxact:name>fld</ipxact:name> <ipxact:accessHandle
  3. Hello All I have a scenario where a field reset value is determined by a port means that port will drive the reset value. Is it possible to represent this in IPXact ? Thanks Khushi
  4. Hello All I am looking at section C.18.1 in IP-Xact 1685-2014 document and noticed ipxact:vectors/ipxact:arrays element inside that, as shown below I am bit confused over the significance of vectors/arrays elements inside parameter xsd. I am not able to find any example where vectors/arrays elements can be used with the parameters. Can these be used to represent an array of parameters e.g. "parameter integer PARAMS[3:0] = {1,2,3,4}' or 'parameter [3:0] PARAM [7:0] ? If yes which part needs to be captured using vectors element and which part needs to be captured using
  5. Thanks Erwin Why in the standard we have two different elements (register and registerFile) ? Why not all capabilities (from simple to complex) are supported using simple register element. Is there some specific reason to have two elements (register for simple register sand registerFile for complex registers e.g. arrays, interleaved etc) > Can we write the IPXact registers descriptions entirely using register files? Are EDA tools supporting registerFile elements to generate UVM or C files? Regarding when we should use register and when registerFile => Can we use registerFi
  6. Hi I have a scenario where I have total 8 identical 32 bit registers back to back but placed 64 bit apart , for example reg1 @0x0, reg2@0x8, reg3@0x10, reg4@0x18 and so on in IPxact, can I represent this as a single register with ipxactL:dim set to 8 ? If yes, I do not find an element which specify that they are 64 bit apart. Is there a way to represent such registers in IPXact in compact way rather then specifying 8 different identical registers ? Thanks Khushi
  7. Hi In IPXACT standard document, I see inside an address block we can have either register or registerFile. In the same context I have following questions - What is the difference between register and registerfile in ipxact ? - When we should use register element or registerfile element to describe registers? Thanks Khushi
  8. Hi Erwin Thanks for your comments. Is it something which is mentioned in section 3.1.6 in https://www.accellera.org/images/downloads/standards/ip-xact/IP-XACT_User_Guide_2018-02-16.pdf Thank Khushi
  9. Hi Which element is IP-Xact is translated to uvm_reg_map in UVM ? In IP-xact, I have a slave interface(e.g. APB) to configure the registers(read/write). This slave interface has a memory map reference. In that memory map there are two address block and each address block has a set of registers. From here: IPxact registers => uvm reg IPxact register block => uvm reg block IPxact memory map => ?? ?? => uvm_reg_map. Thanks in advance Khushi
  10. In IP-Xact there is a section localMemoryMap inside address space which looks similar to the memoryMap. I am not sure to understand the difference between the two and what should be used and when. Can you help me on this ? Also in IP-xact, is it possible to define a register somewhere and instantiate it or use it at other places ? Thanks Khushi
  11. Hi I have a set of registers which can be accessed from two different addr maps (uvm_reg_map) and both sees these addresses at different address. We are trying to generate such uvm registers through IP-Xact. In IP-Xact I can specify registers/register blocks but I am not sure how to specify the fact that one register/register block can be seen at different address via different map/interface. How I can specify the uvm_reg_map in IP-Xact ? Any clue/example help on this please ? Thanks Khushi
  12. Hi I am trying to understand whileBoxElement in IP-XACT and its usage. Can someone explain this and provide some examples. Thanks
  13. Hi Erwin If I am correct, even in 1685-2009 we can describe RTL and TLM within the same component using two different views. Am I correct ? I have a scenario where I have an RTL IP with an optional port which is only present in one view(e.g. simulation view). can I use two view in such case and use viewnameref with that optional port ? Why I need to explicitly specify the typeName with wireTypeDef. In this specific case I want to use native types even when I have optional ports. Is it intentional to have typename mandatory ? How to manage two different businterfaces then ? I hav
  14. Hi Edwin, I understand your point but if both A.a and B.b map the clock signal and if we just connect A.a to B.b,should the tool connect the clock or not ? with error or without error ?. In general during interface connections, what happens to pins which has same direction on both sides ? Should tool connect them ? or left them unconnected ? with or without error/warning? Thanks Khushi
×
×
  • Create New...