d351bfb2bd
When the rcw tools is built, it is probably to generate the RCW (Reset Configuration Word) of the target. So it makes sense to do this directly in the Buildroot infra and install it in the images directory, just like we do for e.g. device tree blobs. Add an option BR2_PACKAGE_HOST_RCW_CUSTOM_PATH that allows to specify the source for the RCW. And while we're at it, make it possible to specify multiple .rcw and .rcwi files, just like for device trees. Signed-off-by: Jared Bents <jared.bents@rockwellcollins.com> [Arnout: * Reword help text and commit message * Remove definition of RCW_DELIVERY_FILE * Define and use RCW_FILES * Enclose everything in ifneq($(RCW_FILES),) * Enclose error in ifeq($(BR_BUILDING),y) * Add actual error message * Don't limit to only %.rcwi files * Don't delete *.bin ] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
29 lines
935 B
Plaintext
29 lines
935 B
Plaintext
config BR2_PACKAGE_HOST_RCW
|
|
bool "host rcw"
|
|
help
|
|
This package provides an reset configuration word(RCW)
|
|
compiler to build NXP QoriQ/LS PBL/RCW binary(s).
|
|
|
|
The package installs example configurations and scripts
|
|
for each devkit supported in the current release see
|
|
$(HOST_DIR)/share/rcw. Either a SDK or post scripts can
|
|
then use this toolset and examples.
|
|
|
|
https://source.codeaurora.org/external/qoriq/qoriq-components/rcw/
|
|
|
|
if BR2_PACKAGE_HOST_RCW
|
|
|
|
config BR2_PACKAGE_HOST_RCW_CUSTOM_PATH
|
|
string "RCW Source file paths"
|
|
help
|
|
Space-separated list of .rcw and .rcwi files, that will be
|
|
used to generate a RCW binary. The entire list of .rcwi files
|
|
used by the .rcw file must be specified. There must be a
|
|
single .rcw file in the list.
|
|
|
|
This is optional. If left empty, the rcw package will be
|
|
included for use in the SDK or with post scripts but no
|
|
RCW binary will not be generated.
|
|
|
|
endif
|