Sending a bus to a sheet

Is it possible to send an entire bus to a sheet through one hierarchical sheet pin or do I really have to break out each of the 44 signals individually?

Yes, it is possible.

Thanks. I guess I should have gone on to ask, “how do I do it?” I’ve done what I think are the obvious things and the signals are not connected through.

Yup, that’s what I mean by doing the obvious things. Doesn’t work. And by ‘doesn’t work’ I mean that the signals in the two sheets are not connected in the netlist. When I go to the PCB and import the netlist, there’s no rat’s nest line where it’s supposed to be.

I thought it should work too so I still wonder if I’m just missing something really simple. I can get single wires to make the transition to sub-sheets with no problem.

My signals are a processor bus, in fact they’re the QBUS if you’re familiar with it. However, that consists of a lot more than just data[21…0], there are all the assorted control lines, so for the purposes of your question they’re probably more like disparate signals that I wish to group together.

If I recall correctly Eeschema supports homogeneous buses only (e.g. DATA[31:0]), it doesn’t currently support heterogeneous buses (e.g. {DQS0, DM0, DQ[7:0]})

Well that’s disappointing but, reading the manual, it does say that. That will make the schematic more difficult to draw, more error-prone, and much more cluttered looking. Too bad. Thanks to both of your for your help.

1 Like

Fell free to add your voice to this bug that asks for such feature:

1 Like

Please pardon the massive necro, but I’m having a similar sort of problem. I’m building a 65C02-based computer, and I’m running the address and data buses out through hierarchical pins.
The ERC is telling me that most of the pins on those buses are unconnected. I’ve stuck a label on each wire saying which signal is coming out of the bus, and connected the bus up to everywhere it needs to go.
What am I doing wrong, and how can I fix it?

The buses themselves aren’t labeled(they shouldn’t need to be), but I’ve been calling the hierarchical pins ADDR_BUS and DATA_BUS.

As far as I know, KiCAD still doesn’t support doing what I wanted to do. I’ve since broken all those signals out into individual hierarchical pins and that works. However, grouping numbered address and data signals together did work for me so offhand I’m not sure what you’re doing wrong.

That feature with mixed bus signals would be very handy. @David_Bridgham have you raised an issue for that feature?

Cioma’s reply has a link to the bug report that was posted almost 4 years ago. I see that its status is listed as “in progress” and the latest message there, only last month, suggests that this fix may finally come along with v6.0. I hope that’s so.

1 Like

Wohoo! Thanks for that great news!

See this video that was released soon after the initial release of 5.0. Yeah, most of it is asking for donations (the donation link in the youtube description isn’t active anymore, use the donate to cern button on the main kicad website if you want to donate), but there are some quick shots of what is in development for 6.0.

For the enhancements of busses see 0:44 in the video.

Unfortunately soon after 5.0 was released there was a major issue with the version of one of the dependencies being disabled in many Linux environments so 6.0 development was back-burnered until the dependency was upgraded. We all hope that once 5.1 is released development on 6.0 will resume.

1 Like

To my own experience , It’s possible, you just have to name both your hierarchical pin and the bus in the same BUS[0…15] style. like this:

Well, it appears as “Fix committed” in Gitlab, are you running nighties @jj8431 ?

This is what we get with a 2x2 years old thread…

1 Like

Closed as this thread is to old and will only confuse users of newer versions of kicad.