Jump to content

Mats Johnson

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by Mats Johnson

  1. Having found 1.5.4.5.1 it seems clear that all the registers must come first, then the registerFiles. Intuitively it would seem reasonable to want to order them in ascending addressOffset order.
  2. We came upon a tool that requires (2009 standard) that in an addressBlock, all registers come first, then all registerFiles. I had interpreted the standard (6.10.1.1) such that there is a list of elements, where each is either a register or a registerFile. Am I wrong, or the tool?
  3. That surprises me a bit, I assumed that there would be no such "hard" requirements on virtual registers, and that that would be the motivation to have the feature to begin with. Looking at my problem from the other direction then, if I have several addressblocks inside a memorymap, the databus and the registers being 32 bit. Then there is a special addressblock that contains some wider (e.g. 128 bit, or even more) datastructures. Those are also updated over the 32 bit bus, the updates are made safe somehow, e.g. through buffered writes, or some more global synchronisation (like disable the block, update the addressblock, then enable again). I would have thought that would be a task for the virtual registers, but if not, how would I model such data structures in IP-XACT?
  4. If I create "virtual registers", that is, registers defined inside an addressBlock with usage "memory", does the size of the register still need to be <= the addressBlock width, as mandated by "SCR 7.5 RegisterSizeWithinBlock"?
×
×
  • Create New...