+ Post New Thread
Page 2 of 2 FirstFirst 1 2
Results 21 to 26 of 26
  1. #21
    Junior Member level 1
    Points: 841, Level: 6

    Join Date
    Oct 2014
    Posts
    19
    Helped
    0 / 0
    Points
    841
    Level
    6

    Re: Best Way to Implement Shared RAM

    Sorry, no, I miswrote.

    There will never be two modules that need to write the same bit at the same time (hence the merged A/B write), however one module may write it and another module may read it. This is in addition to read access via the "external" interface to my core.



    •   AltAdvertisment

        
       

  2. #22
    Super Moderator
    Points: 67,706, Level: 63
    Achievements:
    7 years registered
    Awards:
    Most Frequent Poster 3rd Helpful Member

    Join Date
    Apr 2014
    Posts
    13,844
    Helped
    3158 / 3158
    Points
    67,706
    Level
    63

    Re: Best Way to Implement Shared RAM

    Hi,

    There will never be two modules that need to write the same bit at the same time (hence the merged A/B write), however one module may write it and another module may read it. This is in addition to read access via the "external" interface to my core.
    I didn´t ask for "at the same time".

    --> To avoid further confusion: Show your sketch.

    Klaus
    Please don´t contact me via PM, because there is no time to respond to them. No friend requests. Thank you.



    •   AltAdvertisment

        
       

  3. #23
    Junior Member level 1
    Points: 841, Level: 6

    Join Date
    Oct 2014
    Posts
    19
    Helped
    0 / 0
    Points
    841
    Level
    6

    Re: Best Way to Implement Shared RAM

    They won't need to write to the same bit at any time. For example TXBUSY would only be written by the Tx module.



    •   AltAdvertisment

        
       

  4. #24
    Super Moderator
    Points: 29,664, Level: 42
    ads-ee's Avatar
    Join Date
    Sep 2013
    Location
    USA
    Posts
    6,843
    Helped
    1628 / 1628
    Points
    29,664
    Level
    42

    Re: Best Way to Implement Shared RAM

    Quote Originally Posted by groover View Post
    to it to keep everything in one place.

    I see that for the size of memories, the width of buses, etc. putting values in parameters allows instantiation of different copies of module with different settings, so maybe the number of registers is a special case and can be a parameter, but considering my aim of describing bits in one place how would you recommend I do this without defines?

    Thanks!

    `include my_parameters_of_the_register_definitions.vhd
    and include it in any file that needs to access those address definitions.

    or pass the parameters through the instantiations of all the modules from the top level (my preferred method).

    Using parameters makes code far more portable and reusable.


    1 members found this post helpful.

  5. #25
    Super Moderator
    Points: 67,706, Level: 63
    Achievements:
    7 years registered
    Awards:
    Most Frequent Poster 3rd Helpful Member

    Join Date
    Apr 2014
    Posts
    13,844
    Helped
    3158 / 3158
    Points
    67,706
    Level
    63

    Re: Best Way to Implement Shared RAM

    Hi,

    They won't need to write to the same bit at any time. For example TXBUSY would only be written by the Tx module.
    This is what I thought.

    It's your job to provide informations...I don't want to ask again...


    Klaus
    Please don´t contact me via PM, because there is no time to respond to them. No friend requests. Thank you.



    •   AltAdvertisment

        
       

  6. #26
    Junior Member level 1
    Points: 841, Level: 6

    Join Date
    Oct 2014
    Posts
    19
    Helped
    0 / 0
    Points
    841
    Level
    6

    Re: Best Way to Implement Shared RAM

    Quote Originally Posted by ads-ee View Post

    `include my_parameters_of_the_register_definitions.vhd
    and include it in any file that needs to access those address definitions.

    or pass the parameters through the instantiations of all the modules from the top level (my preferred method).

    Using parameters makes code far more portable and reusable.
    Many thanks for all your help ads-ee! I have decided to go with the trickle-down parameters like you suggested. I already have a basic version implemented.



--[[ ]]--