Skip to content

boards: avnet: add avnet zuboard 1cg #90920

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

singular0770
Copy link

@singular0770 singular0770 commented May 31, 2025

Adds initial support for the Avnet ZUBoard 1CG based on the AMD Zynq Ultrascale+ MPSoC. As with other boards in this family, support is currently limited to the first Cortex-R5 and does not support the Cortex A53 cores, second cortex R5, or dual core lockstep on the R5s. This board port is based on the AMD Kria KV260 starter kit, with the deviation that a new sram1 region is defined which matches the rproc_0_reserved memory region in the zynqmp_openamp.dtsi file in Linux so more memory is available to Zephyr than just the ATCM and the app can be run via remoteproc from Linux.

Copy link

Hello @singular0770, and thank you very much for your first pull request to the Zephyr project!
Our Continuous Integration pipeline will execute a series of checks on your Pull Request commit messages and code, and you are expected to address any failures by updating the PR. Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. If you haven't already, please make sure to review the project's Contributor Expectations and update (by amending and force-pushing the commits) your pull request if necessary.
If you are stuck or need help please join us on Discord and ask your question there. Additionally, you can escalate the review when applicable. 😊

@kartben kartben requested review from kartben and nordicjm June 2, 2025 08:06
Comment on lines 15 to 13
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=100000000
CONFIG_SYS_CLOCK_TICKS_PER_SEC=1000
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be set in soc Kconfig using dts functions

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You think this should be set in the ZynqMP SOC defconfig (soc/xlnx/zynqmp/Kconfig.soc)? I'd like to keep scope of this PR to just this board as there's a lot of work going on from AMD right now to better support their platform. Last time the ZynqMP value changed was 35ca8c9 where it was significantly slowed down for the QEMU R5.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there should be a dts device that specifies the cycles per second, and that should be read/set by the soc Kconfig.defconfig file, the ticks per second can be set there too. Neither should be set in a board defconfig file

Copy link
Author

@singular0770 singular0770 Jun 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you take a look now? I updated the ZynqMP Kconfig.defconfig to use dt_node_int_prop_int to retrieve the clock-frequency parameter of the selected triple-timer counter as CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC.

@singular0770 singular0770 force-pushed the add-avnet-zuboard-1cg branch 4 times, most recently from 30a0b50 to 86e603b Compare June 2, 2025 14:03
Add board definition for the Avnet ZUBoarcd 1CG development board. This
board is based on the Zynq Ultrascale+ MPSoC. As with other boards based
on this platform, currently only the first R5 core is supported.

Signed-off-by: Michael Estes <[email protected]>
Copy link

sonarqubecloud bot commented Jun 2, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants