| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
meta-xilinx-mali400
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
| |
Remove vcu machine feature from zynqmp-common machine as there is
no CG or DR device with a VCU.
Signed-off-by: Christian Kohn <chris.kohn@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
wic uses the sfdisk(-native) utility from the util-linux project. Adding
support for 4k sectors requires a version of sfdisk that can handle
variable-sized sectors specified on the command-line. The version of sfdisk in
scarthgap (2.39.3) does not have this feature, but the version in master
(2.40.4) does.
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
The microblaze util-linux patch needs to be updated for 2.40 as well.
Move existing integration to specifically target the Poky version,
while a new 2.40 version is created. This should allow either version
if the user decided to use PREFERRED_VERSION.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
| |
Recent versions of the 'sfdisk' utility support non-512 byte sized sector
sizes by allowing the user to specify the size the wish to use on the command
line. Update wic to provide this option in the case where a user wishes to
generate an image with a sector size other than 512 bytes.
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A partition's label is stored as part of a partition's meta-data. Whether or
not labeling is supported depends on the filesystem type and whether or not
that type supports labels. GPT partition names, on the other hand, are stored
in the GPT table's metadata and only depends on whether or not GPT
partitioning is used; support for GPT partition names is not required
per-filesystem.
In a wks configuration file, the user specifies they want a filesystem label
applied to a filesystem by using the '--label <name>' directive. A user
specifies they want a GPT partition name applied to a partition using the
'--part-name <name>' directive.
The wic code conflates these two and sets a partition's GPT name in either
case when a user specifies '--part-name <name>' (correct) and '--label <name>'
(not correct).
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
do_configure adds the EXTRA_DT_INCLUDES files to the DTS using the
`/include/` syntax, while Yocto's devicetree.bbclass runs the GCC
preprocessor over the resulting DTS file, leaving these include
statements untouched (since the GCC preprocessor only follows syntax
it recognizes).
This patch converts the include syntax to `#include`, ensuring that
the preprocessor processes it correctly, following and parsing all
included files. This allows a user DTSI to use nested `#include`
statements in overlays. e.g.:
system-user.dtsi
&axi_ad9083_rx_xcvr {
sys-clk-select =3D <XCVR_QPLL>;
out-clk-select =3D <XCVR_REFCLK_DIV2>;
};
Signed-off-by: Semyon Barenboym <semyon.barenboym@abra.co.il>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
multiple archs
Add signal handling for microblze emulation processes. Needed if the
APU shuts down unexpectedly. Note, when APU shuts down correctly, the
microblaze will return a non-zero code. Ignore this as it leads to a
potentially confusing error.
Add -bootbin arch:file support, as we need a different 'arch' configuration
for future processors.
Much of the above was implemented by:
Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
| |
Mingw32 can fail with libquadmath files not being packaged.
This workaround was originally written for PetaLinux, move to
meta-xilinx-core.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
| |
When two different wic session access the files at the same time, pseudo
aborts have been observed. Serializing the wic and wic.ufs works around
this issue.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
| |
The wic tool now has the ability to take a command-line argument specifying
the sector size to use. Switch to this version to build so we no longer need
separate wic programs for 512 and 4k.
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
| |
Updating DP driver name
Signed-off-by: Ashish Kumar Vishwakarma <ashishkumar.vishwakarma@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
| |
This recipe has not been updated in a number of years and is not
currently buildable.
Remove the recipe to prevent confusion.
Signed-off-by: John Toomey <john.toomey@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add the ability to create *.wic.ufs (etc.) images that use a 4096-byte
sector/block size.
This solution uses the local layer version of wic and passing in
--sector-size 4096 when calling the fork of wic in this layer.
(currently only supports ext and vfat)
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
Revised commit message and some integration details
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a command-line argument, --sector-size <N>, to wic's "create" subcommand
and allow it to propagate throughout the wic code so it can be used when
generating a wic image.
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
Added scripts/lib/scriptpath.py change.
Updated the wic version to make it clear it's from this layer.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
| |
Import a copy of wic and lib/oe as of poky commit:
8f74fa4073d4b2ba8e0d9559aa654f3cafcf373a
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
| |
Before the user may have been forced to specify certain parameters, even if
they wanted to just use --help. Move the sanity checks after the help check
to avoid unnecessary warnings and errors.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
| |
Use -dump boot_files option to extract all the required boot files
for QEMU boot.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
| |
Update DEFAULTTUNE for all aarch64 based common machines to
cortexa72-cortexa53 to align with Marketing requirements.
Signed-off-by: Christian Kohn <chris.kohn@amd.com>
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
| |
Adjusted to use an intermediate default BOOTGEN_ARCH, so that no
override is required.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
| |
The stand-alone, non-create version of wic is available from
git.yoctoproject.org, use this stripped-down version.
Based on work from: Trevor Woerner <trevor.woerner@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
| |
Signed-off-by: John Toomey <john.toomey@amd.com>
Also expanded the DESCRIPTION of 'ISP'
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Use boot_files to dump images all the images and remove bh, plm and
pcm_cdo dump options.
Also add print messages for plm and pmc_cdo load address which helps
for debugging.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix runqemu QEMU MB instance below warnings.
qemu-system-microblazeel: -device loader,file=/scratch/sandeep/yocto/2025.1/yp-bc/build/tmp/deploy/images/versal-vek280-sdt-seg/BOOT-versal-vek280-sdt-seg_bh.bin,addr=0xF201E000,force-raw: warning: short-form boolean option 'force-raw' deprecated
Please use force-raw=on instead
qemu-system-microblazeel: -device loader,file=/scratch/sandeep/yocto/2025.1/yp-bc/build/tmp/deploy/images/versal-vek280-sdt-seg/CDO/pmc_cdo.bin,addr=0xf2000000,force-raw: warning: short-form boolean option 'force-raw' deprecated
Please use force-raw=on instead
So use "force-raw=on" in QEMU_HW_FW_FILES arguments.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
| |
Add nativesdk to BBCLASSEXTEND to match meta-openembedded
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
| |
deploy should only be performed in the native case, otherwise a conflict
and error can occur.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Used to combine multiple qemuboot.conf files, non-blank values replace prior values.
./qemuboot-tool: <command> <argument> ...
load <file> - load a new file
merge <file> - load and fill any new/empty variables
remove <var> - Remove a variable
Commands can be chained, such as:
load file1 remove val1 merge file2
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
| |
Instead of using the hard coded path, ${DEPLOY_DIR_IMAGE} we should be using
@DEPLOY_DIR_IMAGE@ where applicable. The exception is QB_DTB where the
qemuboot.conf export function will sanitize the path for us.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
| |
On AMD FPGA SoC machines, we almost always include the serial port options
with the core QB_OPT_APPEND value. If a machine requires QB_SERIAL_OPT
it can override them.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
| |
In the same way that an image recipe would generate a qemuboot.conf, also
generate one for the boot.bin. This will allow us to use runqemu with
just the boot.bin, as well as merge boot.bin specific items with common
(non-machine specific) filesystem qemuboot.conf.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
| |
This will allow the caller of runqemu to override the APU's qemu dtb using
the standard DEVICE_TREE environment option to runqemu.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
To ensure it is easier to override the APU device-tree, support -dtb as an
analog for -hw-dtb to the APU. Additionally, runqemu needs to define a kernel
to pass -dtb, so ignore the -kernel parameter as it doesn't do anything in
the system emulated APU.
Also check and error if an APU DTB is not passed in, either via -dtb or -hw-dtb.
This can cause qemu to lock up, try to prevent this error.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
| |
Adjust the qemu-system-aarch64-multiarch script to remove reference to these.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
| |
The common machine are missing the necessary boot firmware, so clear the QB
(qemu) settings. This will make it easier to 'merge' in the board specific
configurations, where applicable.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Copy all dependent files into ${B}
Construct the bif with relative paths in the ${B} (build) directory
Deploy the resulting build to:
boot.bin-extracted
This is similar behavior to the SDT workflow's 'extracted' directory and
will enable people to re-run bootgen, as necessary, outside of the build
environmet.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
| |
In order to coordinate the deployed filename and machine qemu setting, use
the common variable PMU_ROM.
Note, the variable needs to be defined in a global location as native
recipes are not run with machine.conf loaded.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
| |
Currently the qemu flash drive bin files has static qspi suffix for
both qspi and ospi boot mode, Instead of generating the qspi always
based on OSPI boot mode value generate the qemu ospii flash bin file.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
| |
Refactor QEMU_HW_BOOT_MODE to accept only boot mode value and move
"-boot mode" to qb_extra_args. This makes checking for boot mode value
easier in getVar operations.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
| |
When we've disabled a recipe due to preferred provider status, we do NOT
want to cache the result. If the result is cached, and the user adjusts
the value it may not be recognized requiring the user to delete the
cache directory as a workaround.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
| |
gen-machine-conf is moving to using TFA_CONSOLE to match the newer TFA
recipe implementations. Adjust the older arm-trusted-firmware to match
while retaining compatibility with prior ATF_CONSOLE if required.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QB_MACHINE is now set in each base machine. This ensures that the default
configuration is correct, and can still be overriden if necessary.
This solves a problem where bitbake -e could fail to expand properly
in some cases.
QB_DEFAULT_KERNEL was removed, and restored back to the default settings.
The defaults now work properly with all tested configurations.
Note: simpleImage.mb is obsolete and no longer used in this context.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|
|
|
|
|
|
|
|
|
|
| |
QB_ variables are automatically included in the generated qemuboot.conf
files, even if they are not used by runqemu. Rename various AMD specific
values to avoid them being added to the file.
QB_BOOT_MODE -> QEMU_HW_BOOT_MODE
QB_SD_DRIVE_INDEX -> QEMU_HW_SD_DRIVE_INDEX
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|