Skip to content

Runner fixes in xsdb #92464

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 3 commits into
base: main
Choose a base branch
from

Conversation

kedareswararao
Copy link

This pull does the below

  • Update the xsdb runner to support passing of bl31, pdi, and system.dtb
    files.
  • Update the PDI PATH variables in the RPU port to use runner argument
    instead of environment variables.

Appana Durga Kedareswara rao added 3 commits July 1, 2025 19:32
This update enhances the runner script to optionally accept bl31, pdi,
and system.dtb as arguments. These inputs are not mandatory and will
only be used if explicitly provided. This allows for more flexible boot
configurations, especially useful when testing different firmware and
system setups without modifying the script.

Signed-off-by: Appana Durga Kedareswara rao <appana.durga.kedareswara.rao@amd.com>
…ions

In 2025.1 xsdb release for Versal Gen 2 platform target definitions got
changed, Updated config file to align with latest target definitions.

Signed-off-by: Appana Durga Kedareswara rao <appana.durga.kedareswara.rao@amd.com>
Modified the XSDB configuration to take the PDI path directly from the
runner script's arguments rather than relying on an environment variable.
This change improves usability and makes the runner more self-contained.

Signed-off-by: Appana Durga Kedareswara rao <appana.durga.kedareswara.rao@amd.com>
Copy link

sonarqubecloud bot commented Jul 1, 2025

Copy link
Contributor

@michalsimek michalsimek left a comment

Choose a reason for hiding this comment

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

Already reviewed this internally.

@henrikbrixandersen
Copy link
Member

Already reviewed this internally.

@michalsimek Perhaps we should get you started on getting the collaborator role on the AMD/Xilinx area in Zephyr?
https://docs.zephyrproject.org/latest/project/project_roles.html#collaborator

@michalsimek
Copy link
Contributor

Already reviewed this internally.

@michalsimek Perhaps we should get you started on getting the collaborator role on the AMD/Xilinx area in Zephyr? https://docs.zephyrproject.org/latest/project/project_roles.html#collaborator

I am already listed there:

Xilinx Platforms:
status: odd fixes
collaborators:
- henrikbrixandersen
- ibirnbaum
- michalsimek

Or is there something else needed?

@henrikbrixandersen
Copy link
Member

Or is there something else needed?

Did you receive an invitation for joining the project on GitHub?

@danieldegrasse danieldegrasse added this to the v4.3.0 milestone Jul 11, 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.

5 participants