-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Noc output data path with chip_bridge #115
Comments
I'm not quite sure what you're asking for. The chip bridge is turning three 64 bit networks into a single 32 bit link. In the NO_CHIP_BRIDGE case, those three links are directly wired off the chip. We have I/O modules for when chip_bridge is in use, not for NO_CHIP_BRIDGE. Could you be a little more specific about what you're looking for? |
Referring to the image attached. I want to add a new core that takes the 64 bit noc signals and is connected through the chipset. But I want to bypass all the xbar, bootrom and other stuff that's part of the chipset. What configuration should I be using here? And is it possible to bypass the BOOTROM and other UART components? |
When you say "core", what exactly do you mean? It doesn't make sense to "bypass" the crossbar etc if you want that core to talk to other devices/cores. You can probably just connect whatever the device is to the chipset crossbars. Perhaps you could send me an email with more detail if you don't want to give it in a public forum? |
Sure, I sent you an email with more detail. |
In the chipset.v file, there's a set of noc_data/noc_valid I/O's for no chip_bridge.
Is there a way to use use those with chip_bridge? I want to use those noc_data/valid as inputs to my own module. I can see that it goes through credit_to_valrdy, chipset_imp1, and fpga_bridge which is kind of confusing. can someone help with the noc_data path?
The text was updated successfully, but these errors were encountered: