question on multiple drivers for inout port

[Okashii]

Hi, If I have an entity A with a inout port, say parameter_a, and it has 2
identical child components B and C with inout port parameter_b, is there any
way to connect the 2 parameter_b's to the parameter_a? This is because I
want the 2 child components to be able to read and write the values of
parameter_a, and A may also send the altered value back to some other parent
components. If using inout port is not feasible, is there any other design
solution to this?

 

[Mike Treseler]

Okashii wrote:
If using inout port is not feasible, is there any other design

solution to this?

I would get rid of the internal ports and
put the whole thing in one design entity.

-- Mike Treseler

 

[Ralf Hildebrandt]

Okashii wrote:

Hi, If I have an entity A with a inout port, say parameter_a, and it has 2
identical child components B and C with inout port parameter_b, is there any
way to connect the 2 parameter_b's to the parameter_a? This is because I
want the 2 child components to be able to read and write the values of
parameter_a, and A may also send the altered value back to some other parent
components. If using inout port is not feasible, is there any other design
solution to this?

Use tri-state busses and the resolved data type std_logic(_vector).

For internal signals I would recommend to split them into two busses -
each for one direction. Only the topmost entity should contain inouts.

Ralf