boards: amd: kv260_r5: add support for fsbl and bitstream #86064
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some tests requires to also run fsbl and load bitstream before loading Zephyr. Currently only --elf-file and --fsbl are suported. But there could be also bitstream loaded via --bistream parameter but xsdb script is missing it. Tricky part on it is when only fsbl or bitstream are loaded they are sharing the same argument location that's why detect if second parameter is bitstream by matching "*.bit" in it to support all combinations. And also switch board to jtag boot mode all the time. The reason is that starter kits with SOM have preloaded SW already and starting in QSPI boot mode that's why with using XSDB make sure that board is running in jtag boot mode all the time no matter if any SW runs on it. Signed-off-by: Michal Simek <michal.simek@amd.com>
kedareswararao
approved these changes
Feb 20, 2025
Contributor
|
@ibirnbaum @henrikbrixandersen any chance you can help review? |
henrikbrixandersen
approved these changes
Mar 24, 2025
kedareswararao
pushed a commit
to Xilinx/zephyr-amd
that referenced
this pull request
May 23, 2025
Some tests requires to also run fsbl and load bitstream before loading Zephyr. Currently only --elf-file and --fsbl are suported. But there could be also bitstream loaded via --bistream parameter but xsdb script is missing it. Tricky part on it is when only fsbl or bitstream are loaded they are sharing the same argument location that's why detect if second parameter is bitstream by matching "*.bit" in it to support all combinations. And also switch board to jtag boot mode all the time. The reason is that starter kits with SOM have preloaded SW already and starting in QSPI boot mode that's why with using XSDB make sure that board is running in jtag boot mode all the time no matter if any SW runs on it. Signed-off-by: Michal Simek <michal.simek@amd.com> Link: zephyrproject-rtos/zephyr#86064 State: waiting
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some tests requires to also run fsbl and load bitstream before loading Zephyr.
Currently only --elf-file and --fsbl are suported. But there could be also bitstream loaded via --bistream parameter but xsdb script is missing it.
Tricky part on it is when only fsbl or bitstream are loaded they are sharing the same argument location that's why detect if second parameter is bitstream by matching "*.bit" in it to support all combinations.
And also switch board to jtag boot mode all the time. The reason is that starter kits with SOM have preloaded SW already and starting in QSPI boot mode that's why with using XSDB make sure that board is running in jtag boot mode all the time no matter if any SW runs on it.