New Setup for Cores in Chipyard 1.4.0

[James Hardy]

Hi all,

I am noticing in Chipyard 1.4.0, there are new broadcast modules generated in any multicore builds which seem to link up all of the Tiles in the build. Can anyone give me an explanation on how the Tiles communicate, split up work and report when work is done in the new build structure. Any and all details possible would be much appreciated.

Best,
James Hardy

[Jerry Zhao]

What "broadcast modules" are you referring to? And what multicore configs are you building?

-Jerry

--
You received this message because you are subscribed to the Google Groups "Chipyard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chipyard+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chipyard/6593806a-414f-4a4a-bc2b-b5154a0314d0n%40googlegroups.com.

[James Hardy]

The Configs being used are WithNLargeBooms(4) and WithNBigCores(8). Inside the RocketTile and BoomTile module there is a BundleBridgeNexus module which is automatically created under the name broadcast. When looking at the full design, it seems that these bridges are connected up outside of the Tiles.

[Jerry Zhao]

Those modules send trace information to an external traceport for debug. They do not facilitate core-to-core communication.

-Jerry

To view this discussion on the web visit https://groups.google.com/d/msgid/chipyard/2e4fc0cc-62c1-4f83-bfd8-346d689e8297n%40googlegroups.com.

[James Hardy]

How would I go about accessing/decoding the information sent on that traceport? Is there a specific node that it is sent to? Also, would it still be possible to get an idea of how this heterogeneous core setup would communicate and split up jobs in the Chipyard architecture if given baremetal C code?