Ultra96 v2 BSP hardware project

Hello,

I'm bharath and trying to understand the hardware implementation of a BSP project and hence I created project using 2020.1 BSP and Petalinux and opened the block diagram in Vivado. I don't understand the reason behind using so many system resets and different clocks used. Can anyone help me understand the logic behind this. Thank you in advance.

Attachments:

ULTRA96V2.pdf

Top Replies

drozwood90 over 4 years ago +2

Hi there, This is on purpose. The Ultra96v2 is a highly flexible device that we use across many trainings, courses, reference designs, as well as for examples to customers. The additional things you see…
bhfletcher over 4 years ago +1

Hi Bharath, I have reviewed what you have shown, and I agree that it doesn't make much sense. I expect this may be an artifact of something unexpected happening in the scripting. Let me get with the team…

bhfletcher over 4 years ago

Hi Bharath,

I have reviewed what you have shown, and I agree that it doesn't make much sense. I expect this may be an artifact of something unexpected happening in the scripting. Let me get with the team and see if we can figure out why it is doing that.

Thanks for bringing this to our attention!
Bryan
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel
drozwood90 over 4 years ago

Hi there,

This is on purpose. The Ultra96v2 is a highly flexible device that we use across many trainings, courses, reference designs, as well as for examples to customers. The additional things you see there was a collaboration across our various teams to enable all of that in a coordinated way without everyone causing conflicts with each other's designs.

With the configuration you see there, that BASE design can be leveraged for general purpose PL work, Video (Dual Camera Mezzanine), Vitis AI, as well as Vitis HLS acceleration. The available clocks and associated resets are required by the higher level platform needs. For example, in Vitis HLS and Vitis AI, the tools use the processor reset and XLCONCAT blocks to communicate accelerated HLS to the PL and back from the PL to the PS. While the logic does not have to be in place for these tools, the clocks and resets have to be part of the platform.

If you would like to remove these, you can. Anything we added as part of this should be under the "Vitis Additions" function in the build scripts for the 2020.1 branch.
https://github.com/Avnet/hdl/blob/2020.1/Boards/ULTRA96V2/ultra96v2_oob.tcl#L521

Keep in mind, for PL resources, anything that is not tied to an external pin and not used in some other way will be optimized out of the design anyway.

--Dan
Cancel
Vote Up +2 Vote Down

Sign in to reply

Cancel
bhs09 over 4 years ago in reply to bhfletcher

Hi Bryan,

Thanks for responding, apologies for late response. Anything more about this from the team? Thanks again
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
bhs09 over 4 years ago in reply to drozwood90

HI Daniel,

Thanks for responding and apologies for late response.
Okay it makes sense, can those be named appropriately? For ex if one of the clock is for the camera, if the name reflects that I think will make it easier for anybody wanting to addon peripherals to the PL.

Thanks again
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
drozwood90 over 4 years ago in reply to bhs09

Hi there,

I already posted below.

--Dan
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
drozwood90 over 4 years ago in reply to bhs09

Hi there,

You can name things however you want.

--Dan
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel