package/nxp: new package directory
PATCH v4 1/9 package/nxp: new package directory
The "nxp" directory is intended to contain all NXP QorIQ (including PowerPC and LayerScape serial) related packages, together with their download site and version info.
---
changes since v3:
no changes.
changes since v2:
1. change the sub-direcotry to "nxp".
2. add helper.mk macro to extract compressed file.
changes since v1:
no changes.
--- package/Config.in | 1 + package/nxp/Config.in | 4 ++++ package/nxp/helper.mk | 32 ++++++++++++++++++++++++++++++++ 3 files changed, 37 insertions(+) create mode 100644 package/nxp/Config.in create mode 100644 package/nxp/helper.mk
package/Config.in +1 -0
@@ -494,6 +494,7 @@ endmenu source "package/nvidia-driver/Config.in" source "package/nvidia-tegra23/Config.in" source "package/nvme/Config.in" + source "package/nxp/Config.in" source "package/ofono/Config.in" source "package/on2-8170-modules/Config.in" source "package/open2300/Config.in"
package/nxp/Config.in new file +4 -0
@@ -0,0 +1,4 @@ +menu "NXP QorIQ libraries" + depends on BR2_aarch64 || BR2_arm || BR2_powerpc64 || BR2_powerpc + +endmenu
package/nxp/helper.mk new file +32 -0
@@ -0,0 +1,32 @@ +################################################################################ +# +# helper +# +################################################################################ + +# Helper for self-extracting binaries distributed by NXP. +# +# The --force option makes sure it doesn't fail if the source +# directory already exists. The --auto-accept skips the license check, +# as it is not needed in Buildroot because we have legal-info. Since +# there's a EULA in the binary file, we extract it in this macro, and +# it should therefore be added to the LICENSE_FILES variable of +# packages using this macro. Also, remember to set REDISTRIBUTE to +# "NO". Indeed, this is a legal minefield: the EULA specifies that the +# Board Support Package includes software and hardware (sic!) for +# which a separate license is needed... +# +# $(1): full path to the archive file +# +define NXP_EXTRACT_HELPER + awk 'BEGIN { start = 0; } \ + /^EOEULA/ { start = 0; } \ + { if (start) print; } \ + /<<EOEULA/ { start = 1; }' \ + $(1) > $(@D)/EULA + cd $(@D) && sh $(1) --force --auto-accept + find $(@D)/$(basename $(notdir $(1))) -mindepth 1 -maxdepth 1 -exec mv {} $(@D) \; + rmdir $(@D)/$(basename $(notdir $(1))) +endef + +include $(sort $(wildcard package/nxp/*/*.mk))
Signature · 1 line
2.17.1
[Buildroot] v4 [PATCH 2/9] package/qoriq-rcw: move rcw into nxp and rename it
From: Jerry Huang <[email protected]>
Move package/rcw into package/nxp,
and rename it to qoriq-rcw.
---
changes since v3:
no changes.
changes since v2:
1. change the package name to qoriq-rcw to keep consistent with imx-xxx.
2. add the handing in Config.in.legacy
changes since v1:
1. new patch.
2. move rcw to sub-directory freescale-qoriq.
3. rename to fsl-qoriq-rcw.
---
Config.in.legacy | 8 +++
DEVELOPERS | 2 +-
package/Config.in.host | 2 +-
package/{rcw => nxp/qoriq-rcw}/Config.in.host | 6 +--
.../rcw.hash => nxp/qoriq-rcw/qoriq-rcw.hash} | 2 +-
package/nxp/qoriq-rcw/qoriq-rcw.mk | 50 +++++++++++++++++++
package/rcw/rcw.mk | 50 -------------------
7 files changed, 64 insertions(+), 56 deletions(-)
rename package/{rcw => nxp/qoriq-rcw}/Config.in.host (88%)
rename package/{rcw/rcw.hash => nxp/qoriq-rcw/qoriq-rcw.hash} (82%)
create mode 100644 package/nxp/qoriq-rcw/qoriq-rcw.mk
delete mode 100644 package/rcw/rcw.mkConfig.in.legacy +8 -0
@@ -146,6 +146,14 @@ endif comment "Legacy options removed in 2019.11" +config BR2_PACKAGE_HOST_RCW + bool "rcw package was removed" + select BR2_LEGACY + help + Because rcw package has been renamed to qoriq-rcw and moved + to "nxp", option BR2_PACKAGE_HOST_RCW is removed, the option + BR2_PACKAGE_HOST_QORIQ_RCW can be used for QorIQ platforms. + config BR2_PACKAGE_RPI_USERLAND_START_VCFILED bool "rpi-userland start vcfiled was removed" select BR2_LEGACY
DEVELOPERS +1 -1
@@ -1590,6 +1590,7 @@ F: package/mrouted/ F: package/mtd/ F: package/mtools/ F: package/nginx-upload/ +F: package/nxp/qoriq-rcw/ F: package/omniorb/ F: package/openresolv/ F: package/paxtest/
@@ -1610,7 +1611,6 @@ F: package/python-pyrex/ F: package/python-tinyrpc/ F: package/python-txdbus/ F: package/raptor/ -F: package/rcw/ F: package/rng-tools/ F: package/rsyslog/ F: package/setools/
package/Config.in.host +1 -1
@@ -45,6 +45,7 @@ menu "Host utilities" source "package/mtd/Config.in.host" source "package/mtools/Config.in.host" source "package/mxsldr/Config.in.host" + source "package/nxp/qoriq-rcw/Config.in.host" source "package/omap-u-boot-utils/Config.in.host" source "package/openocd/Config.in.host" source "package/opkg-utils/Config.in.host"
@@ -62,7 +63,6 @@ menu "Host utilities" source "package/qemu/Config.in.host" source "package/raspberrypi-usbboot/Config.in.host" source "package/rauc/Config.in.host" - source "package/rcw/Config.in.host" source "package/rustc/Config.in.host" source "package/s6-rc/Config.in.host" source "package/sam-ba/Config.in.host"
package/nxp/qoriq-rcw/Config.in.host renamed from package/rcw/Config.in.host +3 -3
@@ -1,4 +1,4 @@ -config BR2_PACKAGE_HOST_RCW +config BR2_PACKAGE_HOST_QORIQ_RCW bool "host rcw" help This package provides an reset configuration word(RCW)
@@ -11,9 +11,9 @@ config BR2_PACKAGE_HOST_RCW https://source.codeaurora.org/external/qoriq/qoriq-components/rcw/ -if BR2_PACKAGE_HOST_RCW +if BR2_PACKAGE_HOST_QORIQ_RCW -config BR2_PACKAGE_HOST_RCW_CUSTOM_PATH +config BR2_PACKAGE_HOST_QORIQ_RCW_CUSTOM_PATH string "RCW Source file paths" help Space-separated list of .rcw and .rcwi files, that will be
package/nxp/qoriq-rcw/qoriq-rcw.hash renamed from package/rcw/rcw.hash +1 -1
@@ -1,3 +1,3 @@ # Locally calculated -sha256 1421ada9fec10b12ff21cd9ad82f0a835b191cb2dde80f03547764574b1346c3 rcw-LSDK-18.12.tar.gz +sha256 1421ada9fec10b12ff21cd9ad82f0a835b191cb2dde80f03547764574b1346c3 qoriq-rcw-LSDK-18.12.tar.gz sha256 a531b3146425e592db17a51ff39c4801cb01fb4055ffdaada0572decc0655bcd LICENSE
package/nxp/qoriq-rcw/qoriq-rcw.mk new file +50 -0
50 lines not on this page · raw message
package/rcw/rcw.mk deleted +0 -50
50 lines not on this page · raw message
Signature · 1 line
2.17.1
PATCH v4 3/9 package/qoriq-rcw: bump to version LSDK-19.09
In reply to Changming HuangFrom: Jerry Huang <[email protected]>
Change the RCW version to LSDK-19.09.
---
changes since v3:
no changes.
changes since v2:
1. change the hash value.
changes since v1:
1. add-back license hash.
--- package/nxp/qoriq-rcw/qoriq-rcw.hash | 2 +- package/nxp/qoriq-rcw/qoriq-rcw.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
package/nxp/qoriq-rcw/qoriq-rcw.hash +1 -1
@@ -1,3 +1,3 @@ # Locally calculated -sha256 1421ada9fec10b12ff21cd9ad82f0a835b191cb2dde80f03547764574b1346c3 qoriq-rcw-LSDK-18.12.tar.gz +sha256 4a9ce5bb1733239bf1b740b705df20f90802b16114e24f3fd56c08a7ba4b56c2 qoriq-rcw-LSDK-19.09.tar.gz sha256 a531b3146425e592db17a51ff39c4801cb01fb4055ffdaada0572decc0655bcd LICENSE
package/nxp/qoriq-rcw/qoriq-rcw.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -QORIQ_RCW_VERSION = LSDK-18.12 +QORIQ_RCW_VERSION = LSDK-19.09 QORIQ_RCW_SITE = https://source.codeaurora.org/external/qoriq/qoriq-components/rcw QORIQ_RCW_SITE_METHOD = git QORIQ_RCW_LICENSE = BSD-3-Clause
Signature · 1 line
2.17.1
PATCH v4 4/9 package/qoriq-rcw: add target rcw binary support
In reply to Changming HuangFrom: Jerry Huang <[email protected]>
For NXP QorIQ (PowerPC and Layerscape) platform, we need to specify the RCW file and build it to binary.
Introduce BR2_PACKAGE_HOST_QORIQ_RCW_BIN to specify the RCW binary file.
---
changes since v3:
no changes.
changes since v2:
1. modify the patch descrition.
2. more detail for BR2_PACKAGE_HOST_QORIQ_RCW_BIN.
3. remove two options not used in this patch.
4. add the condition detection in makefile for QorIQ RCW.
changes since v1:
1. add option BR2_PACKAGE_HOST_RCW_ATF for ATF.
--- package/nxp/qoriq-rcw/Config.in.host | 12 ++++++++++++ package/nxp/qoriq-rcw/qoriq-rcw.mk | 15 +++++++++++++++ 2 files changed, 27 insertions(+)
package/nxp/qoriq-rcw/Config.in.host +12 -0
@@ -25,4 +25,16 @@ config BR2_PACKAGE_HOST_QORIQ_RCW_CUSTOM_PATH included for use in the SDK or with post scripts but no RCW binary will not be generated. +config BR2_PACKAGE_HOST_QORIQ_RCW_BIN + string "Custom RCW" + depends on !BR2_PACKAGE_HOST_QORIQ_RCW_CUSTOM_PATH + help + This option is used to specify the RCW binary file for board. + which is composed with platform/serdes_value/rcw_file, platform + is the platform name, serdes_value is the setting of the Serdes, + rcw_file is the file name of RCW, for example: + "ls1028ardb/R_SQPP_0x85bb/rcw_1300_sdboot.bin" + + If this option is empty, no rcw file is used. + endif
package/nxp/qoriq-rcw/qoriq-rcw.mk +15 -0
@@ -37,6 +37,21 @@ endef define HOST_QORIQ_RCW_INSTALL_DELIVERY_FILE $(INSTALL) -D -m 0644 $(@D)/PBL.bin $(BINARIES_DIR)/PBL.bin endef +else +QORIQ_RCW_PATH_FILE_BIN = $(call qstrip,$(BR2_PACKAGE_HOST_QORIQ_RCW_BIN)) + +ifneq ($(QORIQ_RCW_PATH_FILE_BIN),) +QORIQ_RCW_PLATFORM = $(firstword $(subst /, ,$(QORIQ_RCW_PATH_FILE_BIN))) +QORIQ_RCW_FILE_BIN = $(lastword $(subst /, ,$(QORIQ_RCW_PATH_FILE_BIN))) + +define HOST_QORIQ_RCW_BUILD_CMDS + $(MAKE) -C $(@D)/$(QORIQ_RCW_PLATFORM) +endef + +define HOST_QORIQ_RCW_INSTALL_DELIVERY_FILE + $(INSTALL) -D -m 0644 $(@D)/$(QORIQ_RCW_PATH_FILE_BIN) $(BINARIES_DIR)/$(QORIQ_RCW_FILE_BIN) +endef +endif endif # Copy source files and script into $(HOST_DIR)/share/rcw/ so a developer
Signature · 1 line
2.17.1
PATCH v4 5/9 boot/arm-trusted-firmware: introduce two new options
In reply to Changming Huangtwo new options for arm-trusted-firmware:
1. BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_TARGETS
- for additional targets, E.G. "pbl".
2. BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_DEPENDENCIES
- for additional dependencies, E.G. "host-qoriq-rcw"
---
changes since v3:
no changes.
changes since v2:
1. introduce option BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_TARGETS.
2. introduce option BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_DEPENDENCIES.
3. rewrite the makefile with these two options
changes since v1:
1. Use option BR2_PACKAGE_HOST_RCW_ATF as the condition for RCW used by ATF.
--- boot/arm-trusted-firmware/Config.in | 11 +++++++++++ boot/arm-trusted-firmware/arm-trusted-firmware.mk | 6 ++++++ 2 files changed, 17 insertions(+)
boot/arm-trusted-firmware/Config.in +11 -0
@@ -153,4 +153,15 @@ config BR2_TARGET_ARM_TRUSTED_FIRMWARE_IMAGES Names of generated image files that are installed in the output images/ directory. +config BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_TARGETS + string "Additional ATF targets options" + help + Additional target options for ATF build + E.G. 'pbl' + +config BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_DEPENDENCIES + string "Additional AFT dependencies" + help + Additional dependencies for ATF build, E.G. "host-qoriq-rcw" + endif
boot/arm-trusted-firmware/arm-trusted-firmware.mk +6 -0
@@ -92,6 +92,12 @@ endif ARM_TRUSTED_FIRMWARE_MAKE_TARGETS = all +ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += \ + $(call qstrip,$(BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_TARGETS)) + +ARM_TRUSTED_FIRMWARE_DEPENDENCIES += \ + $(call qstrip,$(BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_DEPENDENCIES)) + ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_FIP),y) ARM_TRUSTED_FIRMWARE_MAKE_TARGETS += fip ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-openssl
Signature · 1 line
2.17.1
PATCH v4 5/9 boot/arm-trusted-firmware: introduce two new options
Hello,
Quoted 3 lines · On Wed, 5 Feb 2020 18:52:23 +0800 Changming Huang <[email protected]> wrote:
two new options for arm-trusted-firmware:
1.BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_TARGETS
- for additional targets, E.G. "pbl".
This option was already added in commit 05b8c7da6de863561d66717735a4870f2766454c, which is part of Buildroot master.
Quoted 4 lines
2.
BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_DEPENDENCIES
- for additional dependencies, E.G. "host-qoriq-rcw"Signed-off-by Changming Huang <[email protected]>
No need to resend just for that, though, it can be fixed when applying.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
[Buildroot] [EXT] Re: [PATCH v4 5/9] boot/arm-trusted-firmware: introduce two new options
Best Regards
Jerry Huang
Quoted 24 lines
-----Original Message-----
From: Thomas Petazzoni <[email protected]>
Sent: Wednesday, February 5, 2020 8:29 PM
To: Jerry Huang <[email protected]>
Cc: buildroot at busybox.net; olteanv at gmail.com; michael at walle.cc; geomatsi at gmail.com; matthew.weber at collins.com
Subject: [EXT] Re: [Buildroot] [PATCH v4 5/9] boot/arm-trusted-firmware:
introduce two new optionsCaution: EXT Email
Hello,
Quoted 3 lines · On Wed, 5 Feb 2020 18:52:23 +0800 Changming Huang <[email protected]> wrote:
two new options for arm-trusted-firmware:
1.BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_TARGETS
- for additional targets, E.G. "pbl".This option was already added in commit
05b8c7da6de863561d66717735a4870f2766454c, which is part of Buildroot master.
Quoted 6 lines
Quoted 4 lines
2.
BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_DEPENDENCIES
- for additional dependencies, E.G. "host-qoriq-rcw"Signed-off-by Changming Huang <[email protected]>No need to resend just for that, though, it can be fixed when applying.
Sure, I will remove this options from next version.
Quoted 11 lines
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbootlin.c
om&data=02%7C01%7Cjerry.huang%40nxp.com%7Cc92f05de22194ab439 ff08d7aa3709bc%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C6371 65025674223306&sdata=wsI3e76EHN6NNtKknPiZpBnWAn1FyALHUgbjp4 LKAdw%3D&reserved=0
PATCH v4 6/9 package/qoriq-cadence-dp-firmware: new package
In reply to Changming HuangFrom: Jerry Huang <[email protected]>
This package provides the firmware for LS1028ARDB DP (display port).
---
changes since v3:
no changes.
changes since v2:
1. change the package name to qoriq-cadence-dp-firmware.
2. add the hash of COPYING.
3. modify makefile with new option.
4. update DEVELOPERS with alphabetic ordering
changes since v1:
1. rename the package to fsl-qoriq-cadence-dp-fw.
2. update DEVELOPERS.
3. add the hash of package.
4. modify the context fo config file to package name.
5. re-write the makefile according to rule of buildroot.
6. add the license message in makefile.
--- DEVELOPERS | 3 +++ package/nxp/Config.in | 2 ++ package/nxp/helper.mk | 2 ++ .../nxp/qoriq-cadence-dp-firmware/Config.in | 4 ++++ .../qoriq-cadence-dp-firmware.hash | 3 +++ .../qoriq-cadence-dp-firmware.mk | 23 +++++++++++++++++++ 6 files changed, 37 insertions(+) create mode 100644 package/nxp/qoriq-cadence-dp-firmware/Config.in create mode 100644 package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.hash create mode 100644 package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.mk
DEVELOPERS +3 -0
@@ -513,6 +513,9 @@ F: configs/nanopi_m1_plus_defconfig F: configs/olimex_a13_olinuxino_defconfig F: configs/orangepi_plus_defconfig +N: Changming Huang <[email protected]> +F: package/nxp/qoriq-cadence-dp-firmware/ + N: Chris Packham <[email protected]> F: package/gstreamer1/gst1-shark/ F: package/micropython/
package/nxp/Config.in +2 -0
@@ -1,4 +1,6 @@ menu "NXP QorIQ libraries" depends on BR2_aarch64 || BR2_arm || BR2_powerpc64 || BR2_powerpc +source "package/nxp/qoriq-cadence-dp-firmware/Config.in" + endmenu
package/nxp/helper.mk +2 -0
@@ -4,6 +4,8 @@ # ################################################################################ +NXP_QORIQ_SITE = http://www.nxp.com/lgfiles/sdk/lsdk1909 + # Helper for self-extracting binaries distributed by NXP. # # The --force option makes sure it doesn't fail if the source
package/nxp/qoriq-cadence-dp-firmware/Config.in new file +4 -0
@@ -0,0 +1,4 @@ +config BR2_PACKAGE_QORIQ_CADENCE_DP_FIRMWARE + bool "qoriq-cadence-dp-firmware" + help + NXP QorIQ cadence DP firmware, a resident EL3 firmware.
package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.hash new file +3 -0
@@ -0,0 +1,3 @@ +# Locally calculated +sha256 5871c5717be32f14a59624d5699d405e8ce9ae2e9c9ef86fd16e13d264a40e58 firmware-cadence-lsdk1909.bin +sha256 d55f024af2bfff714b90de596f6d0399124b999e8c18a86b13a3b507bae6f561 COPYING
package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.mk new file +23 -0
@@ -0,0 +1,23 @@ +################################################################################ +# +# qoriq-cadence-dp-firmware +# +################################################################################ + +QORIQ_CADENCE_DP_FIRMWARE_VERSION = lsdk1909 +QORIQ_CADENCE_DP_FIRMWARE_SITE = $(NXP_QORIQ_SITE) +QORIQ_CADENCE_DP_FIRMWARE_SOURCE = firmware-cadence-$(QORIQ_CADENCE_DP_FIRMWARE_VERSION).bin +QORIQ_CADENCE_DP_FIRMWARE_LICENSE = NXP-Binary-EULA +QORIQ_CADENCE_DP_FIRMWARE_LICENSE_FILES = COPYING +QORIQ_CADENCE_DP_FIRMWARE_INSTALL_IMAGES = YES +QORIQ_CADENCE_DP_FIRMWARE_INSTALL_TARGET = NO + +define QORIQ_CADENCE_DP_FIRMWARE_EXTRACT_CMDS + $(call NXP_EXTRACT_HELPER,$(QORIQ_CADENCE_DP_FIRMWARE_DL_DIR)/$(QORIQ_CADENCE_DP_FIRMWARE_SOURCE)) +endef + +define QORIQ_CADENCE_DP_FIRMWARE_INSTALL_IMAGES_CMDS + $(INSTALL) -D -m 0644 $(@D)/dp/ls1028a-dp-fw.bin $(BINARIES_DIR)/ls1028a-dp-fw.bin +endef + +$(eval $(generic-package))
Signature · 1 line
2.17.1
PATCH v4 6/9 package/qoriq-cadence-dp-firmware: new package
Am 2020-02-05 11:52, schrieb Changming Huang:
Quoted 66 lines
From: Jerry Huang <[email protected]>
This package provides the firmware for LS1028ARDB DP (display port).
Signed-off-by Jerry Huang <[email protected]>---
changes since v3:
no changes.changes since v2:
1. change the package name to qoriq-cadence-dp-firmware.
2. add the hash of COPYING.
3. modify makefile with new option.
4. update DEVELOPERS with alphabetic orderingchanges since v1:
1. rename the package to fsl-qoriq-cadence-dp-fw.
2. update DEVELOPERS.
3. add the hash of package.
4. modify the context fo config file to package name.
5. re-write the makefile according to rule of buildroot.
6. add the license message in makefile.--- DEVELOPERS | 3 +++ package/nxp/Config.in | 2 ++ package/nxp/helper.mk | 2 ++ .../nxp/qoriq-cadence-dp-firmware/Config.in | 4 ++++ .../qoriq-cadence-dp-firmware.hash | 3 +++ .../qoriq-cadence-dp-firmware.mk | 23 +++++++++++++++++++ 6 files changed, 37 insertions(+) create mode 100644 package/nxp/qoriq-cadence-dp-firmware/Config.in create mode 100644 package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.hash create mode 100644
package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.mkDEVELOPERS +3
-0@@ -513,6 +513,9 @@ F: configs/nanopi_m1_plus_defconfig F: configs/olimex_a13_olinuxino_defconfig F: configs/orangepi_plus_defconfig +N: Changming Huang <[email protected]> +F: package/nxp/qoriq-cadence-dp-firmware/ + N: Chris Packham <[email protected]> F: package/gstreamer1/gst1-shark/ F: package/micropython/package/nxp/Config.in +2
-0@@ -1,4 +1,6 @@ menu "NXP QorIQ libraries" depends on BR2_aarch64 || BR2_arm || BR2_powerpc64 || BR2_powerpc +source "package/nxp/qoriq-cadence-dp-firmware/Config.in" + endmenupackage/nxp/helper.mk +0
-0
package/nxp/helper.mk line 9
Quoted 6 lines
package/nxp/helper.mk +2
-0@@ -4,6 +4,8 @@ # ################################################################################ +NXP_QORIQ_SITE = http://www.nxp.com/lgfiles/sdk/lsdk1909 +
I'm not sure if that NXP_QORIQ_SITE should go in here. But the specifc version "lsdk1909" is for sure not correct.
Quoted 39 lines
package/nxp/helper.mk +0
-0# Helper for self-extracting binaries distributed by NXP. ## The --force option makes sure it doesn't fail if the source
package/nxp/qoriq-cadence-dp-firmware/Config.in new file +4
-0@@ -0,0 +1,4 @@ +config BR2_PACKAGE_QORIQ_CADENCE_DP_FIRMWARE + bool "qoriq-cadence-dp-firmware" + help + NXP QorIQ cadence DP firmware, a resident EL3 firmware.diff --git a/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.hash b/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.hash new file mode 100644
index 0000000000..89aaf1d71b
---/dev/null
+++
b/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.hashpackage/nxp/qoriq-cadence-dp-firmware/Config.in new file +2
-0@@ -0,0 +1,3 @@ +# Locally calculated +sha256
5871c5717be32f14a59624d5699d405e8ce9ae2e9c9ef86fd16e13d264a40e58firmware-cadence-lsdk1909.bin
+sha256d55f024af2bfff714b90de596f6d0399124b999e8c18a86b13a3b507bae6f561COPYING
diff --gita/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.mkb/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.mknew file mode 100644
index 0000000000..239f4b9d75
---/dev/null
+++b/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.mk
package/nxp/qoriq-cadence-dp-firmware/Config.in line 8
Quoted 8 lines
package/nxp/qoriq-cadence-dp-firmware/Config.in new file +8
-0@@ -0,0 +1,23 @@ +################################################################################ +# +# qoriq-cadence-dp-firmware +# +################################################################################ + +QORIQ_CADENCE_DP_FIRMWARE_VERSION = lsdk1909 +QORIQ_CADENCE_DP_FIRMWARE_SITE = $(NXP_QORIQ_SITE)
why don't you just useQORIQ_CADENCE_DP_FIRMWARE_SITE =
http://www.nxp.com/lgfiles/sdk/$(QORIQ_CADENCE_DP_FIRMWARE_VERSION)
Quoted 14 lines
package/nxp/qoriq-cadence-dp-firmware/Config.in new file +1
-0+QORIQ_CADENCE_DP_FIRMWARE_SOURCE =firmware-cadence-$(QORIQ_CADENCE_DP_FIRMWARE_VERSION).bin
package/nxp/qoriq-cadence-dp-firmware/Config.in new file +7
-0+QORIQ_CADENCE_DP_FIRMWARE_LICENSE = NXP-Binary-EULA +QORIQ_CADENCE_DP_FIRMWARE_LICENSE_FILES = COPYING +QORIQ_CADENCE_DP_FIRMWARE_INSTALL_IMAGES = YES +QORIQ_CADENCE_DP_FIRMWARE_INSTALL_TARGET = NO + +define QORIQ_CADENCE_DP_FIRMWARE_EXTRACT_CMDS + $(callNXP_EXTRACT_HELPER,$(QORIQ_CADENCE_DP_FIRMWARE_DL_DIR)/$(QORIQ_CADENCE_DP_FIRMWARE_SOURCE))
package/nxp/qoriq-cadence-dp-firmware/Config.in new file +4
-0+endef + +define QORIQ_CADENCE_DP_FIRMWARE_INSTALL_IMAGES_CMDS + $(INSTALL) -D -m 0644 $(@D)/dp/ls1028a-dp-fw.bin
Quoted 2 lines
$(BINARIES_DIR)/ls1028a-dp-fw.bin
+endef
Installing the firmware into the target filesystem is missing. As pointed out by me - and also
Vladimir - the DisplayPort driver should rather load the firmare by its on and should not
depend on the bootloader to load it.
Quoted 2 lines
+
+$(eval $(generic-package))
[Buildroot] [EXT] Re: [PATCH v4 6/9] package/qoriq-cadence-dp-firmware: new package
Best Regards
Jerry Huang
Quoted 96 lines
-----Original Message-----
From: Michael Walle <[email protected]>
Sent: Wednesday, February 5, 2020 9:48 PM
To: Jerry Huang <[email protected]>
Cc: buildroot at busybox.net; thomas.petazzoni at bootlin.com; matthew.weber at collins.com; geomatsi at gmail.com; olteanv at gmail.com
Subject: [EXT] Re: [PATCH v4 6/9] package/qoriq-cadence-dp-firmware: new packageCaution: EXT Email
Am 2020-02-05 11:52, schrieb Changming Huang:
Quoted 22 lines
From: Jerry Huang <[email protected]>
This package provides the firmware for LS1028ARDB DP (display port).
Signed-off-by Jerry Huang <[email protected]>---
changes since v3:
no changes.changes since v2:
1. change the package name to qoriq-cadence-dp-firmware.
2. add the hash of COPYING.
3. modify makefile with new option.
4. update DEVELOPERS with alphabetic orderingchanges since v1:
1. rename the package to fsl-qoriq-cadence-dp-fw.
2. update DEVELOPERS.
3. add the hash of package.
4. modify the context fo config file to package name.
5. re-write the makefile according to rule of buildroot.
6. add the license message in makefile.Quoted 7 lines
--- DEVELOPERS | 3 +++ package/nxp/Config.in | 2 ++ package/nxp/helper.mk | 2 ++ .../nxp/qoriq-cadence-dp-firmware/Config.in | 4 ++++ .../qoriq-cadence-dp-firmware.hash | 3 +++ .../qoriq-cadence-dp-firmware.mk | 23+++++++++++++++++++
Quoted 38 lines
6 files changed, 37 insertions(+) create mode 100644 package/nxp/qoriq-cadence-dp-firmware/Config.in create mode 100644 package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.hash create mode 100644
package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.mkDEVELOPERS +3
-0@@ -513,6 +513,9 @@ F: configs/nanopi_m1_plus_defconfig F: configs/olimex_a13_olinuxino_defconfig F: configs/orangepi_plus_defconfig +N: Changming Huang <[email protected]> +F: package/nxp/qoriq-cadence-dp-firmware/ + N: Chris Packham <[email protected]> F: package/gstreamer1/gst1-shark/ F: package/micropython/package/nxp/Config.in index renamed from package/nxp/Config.in +0
-0
575542c7ab..855d62700b100644package/nxp/Config.in +0
-0@@ -1,4 +1,6 @@ menu "NXP QorIQ libraries" depends on BR2_aarch64 || BR2_arm || BR2_powerpc64 ||
BR2_powerpcpackage/nxp/Config.in +2
-0+source "package/nxp/qoriq-cadence-dp-firmware/Config.in" + endmenupackage/nxp/helper.mk index renamed from package/nxp/helper.mk +0
-0
79e4236249..2eee2227af100644package/nxp/helper.mk line 6
Quoted 3 lines
package/nxp/helper.mk +0
-0@@ -4,6 +4,8 @@ #################################################################
######package/nxp/helper.mk line 11
Quoted 5 lines
package/nxp/helper.mk +2
-0########## +NXP_QORIQ_SITE = +https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.+nxp.com%2Flgfiles%2Fsdk%2Flsdk1909&data=02%7C01%7Cjerry.huang% 40n
Quoted 1 line
+xp.com%7Ce570360260aa4b23ad6708d7aa42085b%7C686ea1d3bc2b4c6fa92 cd99c5
Quoted 1 line
Quoted 7 lines
+c301635%7C0%7C0%7C637165072894599859&sdata=y0oeGsbp%2FvxW GdocRx4W
package/nxp/helper.mk
Quoted 2 lines
package/nxp/helper.mk +2
-0+Z1sPhepE3gFFfIdSTev%2F%2BU4%3D&reserved=0 +I'm not sure if that
NXP_QORIQ_SITEshould go in here. But the specifc version "lsdk1909" is for sure not correct.
Will remove NXP_QORIQ_SITE from next version.
Quoted 49 lines
package/nxp/qoriq-cadence-dp-firmware/Config.in
Quoted 40 lines
# Helper for self-extracting binaries distributed by NXP. #
# The --force option makes sure it doesn't fail if the source diff
--git a/package/nxp/qoriq-cadence-dp-firmware/Config.in b/package/nxp/qoriq-cadence-dp-firmware/Config.in
new file mode 100644
index 0000000000..3f494bd3a3package/nxp/qoriq-cadence-dp-firmware/Config.in new file +4
-0@@ -0,0 +1,4 @@ +config BR2_PACKAGE_QORIQ_CADENCE_DP_FIRMWARE + bool "qoriq-cadence-dp-firmware" + help + NXP QorIQ cadence DP firmware, a resident EL3 firmware.diff --git a/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.hash b/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.hash new file mode 100644
index 0000000000..89aaf1d71b
---/dev/null
+++
b/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.hashpackage/nxp/qoriq-cadence-dp-firmware/Config.in new file +2
-0@@ -0,0 +1,3 @@ +# Locally calculated +sha256
5871c5717be32f14a59624d5699d405e8ce9ae2e9c9ef86fd16e13d264a40e58firmware-cadence-lsdk1909.bin
+sha256d55f024af2bfff714b90de596f6d0399124b999e8c18a86b13a3b507bae6f561COPYING
diff --gita/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.mkb/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.mknew file mode 100644
index 0000000000..239f4b9d75
---/dev/null
+++b/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.mkpackage/nxp/qoriq-cadence-dp-firmware/Config.in new file +0
-0@@ -0,0 +1,23 @@+###############################################################
######package/nxp/qoriq-cadence-dp-firmware/Config.in line 4
Quoted 5 lines
package/nxp/qoriq-cadence-dp-firmware/Config.in new file +4
-0+########### +# +# qoriq-cadence-dp-firmware +#+###############################################################
######
Quoted 13 lines
package/nxp/qoriq-cadence-dp-firmware/Config.in line 8
Quoted 4 lines
package/nxp/qoriq-cadence-dp-firmware/Config.in new file +4
-0+########### + +QORIQ_CADENCE_DP_FIRMWARE_VERSION = lsdk1909 +QORIQ_CADENCE_DP_FIRMWARE_SITE = $(NXP_QORIQ_SITE)why don't you just use
QORIQ_CADENCE_DP_FIRMWARE_SITE=
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.nxp.
com%2Flgfiles%2Fsdk%2F%24(QORIQ_CADENCE_DP_FIRMWARE_VERSION&a mp;data=02%7C01%7Cjerry.huang%40nxp.com%7Ce570360260aa4b23ad6708 d7aa42085b%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C6371650 72894609853&sdata=4nh9qImzs1JjE1CPLEKU3Hx%2BP7lkLudTNfd41TZ7K %2Fc%3D&reserved=0)
will use the url directly next version.
Quoted 12 lines
package/nxp/qoriq-cadence-dp-firmware/Config.in
Quoted 10 lines
package/nxp/qoriq-cadence-dp-firmware/Config.in new file +1
-0+QORIQ_CADENCE_DP_FIRMWARE_SOURCE =firmware-cadence-$(QORIQ_CADENCE_DP_FIRMWARE_VERSION).bin
package/nxp/qoriq-cadence-dp-firmware/Config.in new file +7
-0+QORIQ_CADENCE_DP_FIRMWARE_LICENSE = NXP-Binary-EULA +QORIQ_CADENCE_DP_FIRMWARE_LICENSE_FILES = COPYING +QORIQ_CADENCE_DP_FIRMWARE_INSTALL_IMAGES = YES +QORIQ_CADENCE_DP_FIRMWARE_INSTALL_TARGET = NO + +define QORIQ_CADENCE_DP_FIRMWARE_EXTRACT_CMDS + $(callNXP_EXTRACT_HELPER,$(QORIQ_CADENCE_DP_FIRMWARE_DL_DIR)/$(QORI
Q_CADENCE
Quoted 11 lines
Quoted 7 lines
_DP_FIRMWARE_SOURCE))package/nxp/qoriq-cadence-dp-firmware/Config.in new file +4
-0+endef + +define QORIQ_CADENCE_DP_FIRMWARE_INSTALL_IMAGES_CMDS + $(INSTALL) -D -m 0644 $(@D)/dp/ls1028a-dp-fw.bin$(BINARIES_DIR)/ls1028a-dp-fw.bin
+endefInstalling the firmware into the target filesystem is missing. As pointed out by me - and also Vladimir - the DisplayPort driver should rather load the firmare by its on and should not depend on the bootloader to load it.
We don't install this firmware into target filesystem, because we need to load it to hardware before mounting target filesystem.
Quoted 2 lines
Quoted 2 lines
+
+$(eval $(generic-package))
[Buildroot] [EXT] Re: [PATCH v4 6/9] package/qoriq-cadence-dp-firmware: new package
Am 2020-02-07 02:26, schrieb Jerry Huang:
Quoted 199 lines
Best Regards
Jerry HuangQuoted 97 lines
-----Original Message-----
From: Michael Walle <[email protected]>
Sent: Wednesday, February 5, 2020 9:48 PM
To: Jerry Huang <[email protected]>
Cc: buildroot at busybox.net; thomas.petazzoni at bootlin.com; matthew.weber at collins.com; geomatsi at gmail.com; olteanv at gmail.com
Subject: [EXT] Re: [PATCH v4 6/9] package/qoriq-cadence-dp-firmware:
new
packageCaution: EXT Email
Am 2020-02-05 11:52, schrieb Changming Huang:
Quoted 22 lines
From: Jerry Huang <[email protected]>
This package provides the firmware for LS1028ARDB DP (display port).
Signed-off-by Jerry Huang <[email protected]>---
changes since v3:
no changes.changes since v2:
1. change the package name to qoriq-cadence-dp-firmware.
2. add the hash of COPYING.
3. modify makefile with new option.
4. update DEVELOPERS with alphabetic orderingchanges since v1:
1. rename the package to fsl-qoriq-cadence-dp-fw.
2. update DEVELOPERS.
3. add the hash of package.
4. modify the context fo config file to package name.
5. re-write the makefile according to rule of buildroot.
6. add the license message in makefile.Quoted 7 lines
--- DEVELOPERS | 3 +++ package/nxp/Config.in | 2 ++ package/nxp/helper.mk | 2 ++ .../nxp/qoriq-cadence-dp-firmware/Config.in | 4 ++++ .../qoriq-cadence-dp-firmware.hash | 3 +++ .../qoriq-cadence-dp-firmware.mk | 23+++++++++++++++++++
Quoted 38 lines
6 files changed, 37 insertions(+) create mode 100644 package/nxp/qoriq-cadence-dp-firmware/Config.in create mode 100644 package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.hash create mode 100644
package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.mkDEVELOPERS +3
-0@@ -513,6 +513,9 @@ F: configs/nanopi_m1_plus_defconfig F: configs/olimex_a13_olinuxino_defconfig F: configs/orangepi_plus_defconfig +N: Changming Huang <[email protected]> +F: package/nxp/qoriq-cadence-dp-firmware/ + N: Chris Packham <[email protected]> F: package/gstreamer1/gst1-shark/ F: package/micropython/package/nxp/Config.in index renamed from package/nxp/Config.in +0
-0
575542c7ab..855d62700b100644package/nxp/Config.in +0
-0@@ -1,4 +1,6 @@ menu "NXP QorIQ libraries" depends on BR2_aarch64 || BR2_arm || BR2_powerpc64 ||
BR2_powerpcpackage/nxp/Config.in +2
-0+source "package/nxp/qoriq-cadence-dp-firmware/Config.in" + endmenupackage/nxp/helper.mk index renamed from package/nxp/helper.mk +0
-0
79e4236249..2eee2227af100644package/nxp/helper.mk line 6
Quoted 3 lines
package/nxp/helper.mk +0
-0@@ -4,6 +4,8 @@ #################################################################
######package/nxp/helper.mk line 11
Quoted 5 lines
package/nxp/helper.mk +2
-0########## +NXP_QORIQ_SITE = +https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.+nxp.com%2Flgfiles%2Fsdk%2Flsdk1909&data=02%7C01%7Cjerry.huang% 40n
Quoted 1 line
+xp.com%7Ce570360260aa4b23ad6708d7aa42085b%7C686ea1d3bc2b4c6fa92 cd99c5
Quoted 1 line
Quoted 8 lines
+c301635%7C0%7C0%7C637165072894599859&sdata=y0oeGsbp%2FvxW GdocRx4W
package/nxp/helper.mk
Quoted 2 lines
package/nxp/helper.mk +2
-0+Z1sPhepE3gFFfIdSTev%2F%2BU4%3D&reserved=0 +I'm not sure if that
NXP_QORIQ_SITEshould go in here. But the specifc version
"lsdk1909" is for sure not correct.Will remove
NXP_QORIQ_SITEfrom next version.Quoted 49 lines
package/nxp/qoriq-cadence-dp-firmware/Config.in
Quoted 40 lines
# Helper for self-extracting binaries distributed by NXP. #
# The --force option makes sure it doesn't fail if the source diff
--git a/package/nxp/qoriq-cadence-dp-firmware/Config.in b/package/nxp/qoriq-cadence-dp-firmware/Config.in
new file mode 100644
index 0000000000..3f494bd3a3package/nxp/qoriq-cadence-dp-firmware/Config.in new file +4
-0@@ -0,0 +1,4 @@ +config BR2_PACKAGE_QORIQ_CADENCE_DP_FIRMWARE + bool "qoriq-cadence-dp-firmware" + help + NXP QorIQ cadence DP firmware, a resident EL3 firmware.diff --git a/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.hash b/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.hash new file mode 100644
index 0000000000..89aaf1d71b
---/dev/null
+++
b/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.hashpackage/nxp/qoriq-cadence-dp-firmware/Config.in new file +2
-0@@ -0,0 +1,3 @@ +# Locally calculated +sha256
5871c5717be32f14a59624d5699d405e8ce9ae2e9c9ef86fd16e13d264a40e58firmware-cadence-lsdk1909.bin
+sha256d55f024af2bfff714b90de596f6d0399124b999e8c18a86b13a3b507bae6f561COPYING
diff --gita/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.mkb/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.mknew file mode 100644
index 0000000000..239f4b9d75
---/dev/null
+++b/package/nxp/qoriq-cadence-dp-firmware/qoriq-cadence-dp-firmware.mkpackage/nxp/qoriq-cadence-dp-firmware/Config.in new file +0
-0@@ -0,0 +1,23 @@+###############################################################
######package/nxp/qoriq-cadence-dp-firmware/Config.in line 4
Quoted 5 lines
package/nxp/qoriq-cadence-dp-firmware/Config.in new file +4
-0+########### +# +# qoriq-cadence-dp-firmware +#+###############################################################
######Quoted 13 lines
package/nxp/qoriq-cadence-dp-firmware/Config.in line 8
Quoted 4 lines
package/nxp/qoriq-cadence-dp-firmware/Config.in new file +4
-0+########### + +QORIQ_CADENCE_DP_FIRMWARE_VERSION = lsdk1909 +QORIQ_CADENCE_DP_FIRMWARE_SITE = $(NXP_QORIQ_SITE)why don't you just use
QORIQ_CADENCE_DP_FIRMWARE_SITE=
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.nxp.
com%2Flgfiles%2Fsdk%2F%24(QORIQ_CADENCE_DP_FIRMWARE_VERSION&a mp;data=02%7C01%7Cjerry.huang%40nxp.com%7Ce570360260aa4b23ad6708 d7aa42085b%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C6371650 72894609853&sdata=4nh9qImzs1JjE1CPLEKU3Hx%2BP7lkLudTNfd41TZ7K %2Fc%3D&reserved=0)will use the url directly next version.
Quoted 12 lines
package/nxp/qoriq-cadence-dp-firmware/Config.in
Quoted 10 lines
package/nxp/qoriq-cadence-dp-firmware/Config.in new file +1
-0+QORIQ_CADENCE_DP_FIRMWARE_SOURCE =firmware-cadence-$(QORIQ_CADENCE_DP_FIRMWARE_VERSION).bin
package/nxp/qoriq-cadence-dp-firmware/Config.in new file +7
-0+QORIQ_CADENCE_DP_FIRMWARE_LICENSE = NXP-Binary-EULA +QORIQ_CADENCE_DP_FIRMWARE_LICENSE_FILES = COPYING +QORIQ_CADENCE_DP_FIRMWARE_INSTALL_IMAGES = YES +QORIQ_CADENCE_DP_FIRMWARE_INSTALL_TARGET = NO + +define QORIQ_CADENCE_DP_FIRMWARE_EXTRACT_CMDS + $(callNXP_EXTRACT_HELPER,$(QORIQ_CADENCE_DP_FIRMWARE_DL_DIR)/$(QORI
Q_CADENCEQuoted 13 lines
Quoted 7 lines
_DP_FIRMWARE_SOURCE))package/nxp/qoriq-cadence-dp-firmware/Config.in new file +4
-0+endef + +define QORIQ_CADENCE_DP_FIRMWARE_INSTALL_IMAGES_CMDS + $(INSTALL) -D -m 0644 $(@D)/dp/ls1028a-dp-fw.bin$(BINARIES_DIR)/ls1028a-dp-fw.bin
+endefInstalling the firmware into the target filesystem is missing. As pointed out by
me - and also Vladimir - the DisplayPort driver should rather load the firmare by
its on and should not depend on the bootloader to load it.
Quoted 2 lines
We don't install this firmware into target filesystem, because we need to load it to hardware before mounting target filesystem.
You didn't get my point. The correct way to load the firmware is by linux
requesting it from the filesystem, not by loading it in the bootloader. So
at least this package should go into the right direction, independent from
what you're doing in your own kernel. Also what is the upstream status of
the graphics patches for the LS1028A. I couldn't find any patches regarding
ls1028a and its mali core on the linux mailing list. If there are no patches
for now, please wait until it will be discussed on the kernel mailing list
how the firmware loading will be handled. TBH, I don't like to see some proprietary handling in buildroot.
-michael
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
+
+$(eval $(generic-package))
PATCH v4 7/9 package/qoriq-rcw:Enable IIC5_PMUX and CLK_OUT_PMUX for GPIO
In reply to Changming HuangFrom: Jerry Huang <[email protected]>
Because GPIO is used as interrupt for eNETC PHY and Micro-bus, IIC5_PMUX and CLK_OUT_PMUX are enabled for GPIO.
---
changes since v3:
no changes.
changes since v2:
no changes.
changes since v1:
1. change to unconditional for these two patches.
--- ...b-Enable-IIC5_PMUX-for-GPIO-function.patch | 42 +++++++++++++++++++ ...nable-CLK_OUT_PMUX-for-GPIO-function.patch | 40 ++++++++++++++++++ 2 files changed, 82 insertions(+) create mode 100644 package/nxp/qoriq-rcw/0001-ls1028ardb-Enable-IIC5_PMUX-for-GPIO-function.patch create mode 100644 package/nxp/qoriq-rcw/0002-ls1028ardb-Enable-CLK_OUT_PMUX-for-GPIO-function.patch
package/nxp/qoriq-rcw/0001-ls1028ardb-Enable-IIC5_PMUX-for-GPIO-function.patch new file +42 -0
@@ -0,0 +1,42 @@ +From 33b403cee1fa215927bc65dc14baf35a2fdbe7b3 Mon Sep 17 00:00:00 2001 +From: Jerry Huang <[email protected]> +Date: Thu, 19 Sep 2019 12:12:20 +0800 +Subject: [PATCH 1/2] ls1028ardb: Enable IIC5_PMUX for GPIO function + +Set IIC5_PMUX = 1 to enable GPIO function. + +Signed-off-by: Jianchao Wang <[email protected]> +Signed-off-by: Jerry Huang <[email protected]> +--- + ls1028ardb/R_SQPP_0x85bb/rcw_1300_emmcboot.rcw | 2 +- + ls1028ardb/R_SQPP_0x85bb/rcw_1300_sdboot.rcw | 2 +- + 2 files changed, 2 insertions(+), 2 deletions(-) + +diff --git a/ls1028ardb/R_SQPP_0x85bb/rcw_1300_emmcboot.rcw b/ls1028ardb/R_SQPP_0x85bb/rcw_1300_emmcboot.rcw +index b46ea2e..5466a63 100644 +--- a/ls1028ardb/R_SQPP_0x85bb/rcw_1300_emmcboot.rcw ++++ b/ls1028ardb/R_SQPP_0x85bb/rcw_1300_emmcboot.rcw +@@ -26,7 +26,7 @@ SYSCLK_FREQ=600 + IIC2_PMUX=6 + IIC3_PMUX=2 + IIC4_PMUX=2 +-IIC5_PMUX=2 ++IIC5_PMUX=1 + IIC6_PMUX=2 + CLK_OUT_PMUX=2 + EC1_SAI4_5_PMUX=5 +diff --git a/ls1028ardb/R_SQPP_0x85bb/rcw_1300_sdboot.rcw b/ls1028ardb/R_SQPP_0x85bb/rcw_1300_sdboot.rcw +index 04e2208..1908d8c 100644 +--- a/ls1028ardb/R_SQPP_0x85bb/rcw_1300_sdboot.rcw ++++ b/ls1028ardb/R_SQPP_0x85bb/rcw_1300_sdboot.rcw +@@ -26,7 +26,7 @@ SYSCLK_FREQ=600 + IIC2_PMUX=6 + IIC3_PMUX=2 + IIC4_PMUX=2 +-IIC5_PMUX=2 ++IIC5_PMUX=1 + IIC6_PMUX=3 + CLK_OUT_PMUX=2 + EC1_SAI4_5_PMUX=5 +-- +2.17.1
package/nxp/qoriq-rcw/0002-ls1028ardb-Enable-CLK_OUT_PMUX-for-GPIO-function.patch new file +40 -0
@@ -0,0 +1,40 @@ +From 4a3c9ea5d0c7bf8eec8cb6276d6f4d940f3946db Mon Sep 17 00:00:00 2001 +From: Jerry Huang <[email protected]> +Date: Thu, 19 Sep 2019 12:13:48 +0800 +Subject: [PATCH 2/2] ls1028ardb/rcw: Enable CLK_OUT_PMUX for GPIO function + +Signed-off-by: Jianchao Wang <[email protected]> +Signed-off-by: Jerry Huang <[email protected]> +--- + ls1028ardb/R_SQPP_0x85bb/rcw_1300_emmcboot.rcw | 2 +- + ls1028ardb/R_SQPP_0x85bb/rcw_1300_sdboot.rcw | 2 +- + 2 files changed, 2 insertions(+), 2 deletions(-) + +diff --git a/ls1028ardb/R_SQPP_0x85bb/rcw_1300_emmcboot.rcw b/ls1028ardb/R_SQPP_0x85bb/rcw_1300_emmcboot.rcw +index 5466a63..a5ed4d4 100644 +--- a/ls1028ardb/R_SQPP_0x85bb/rcw_1300_emmcboot.rcw ++++ b/ls1028ardb/R_SQPP_0x85bb/rcw_1300_emmcboot.rcw +@@ -28,7 +28,7 @@ IIC3_PMUX=2 + IIC4_PMUX=2 + IIC5_PMUX=1 + IIC6_PMUX=2 +-CLK_OUT_PMUX=2 ++CLK_OUT_PMUX=1 + EC1_SAI4_5_PMUX=5 + EC1_SAI3_6_PMUX=5 + USB3_CLK_FSEL=39 +diff --git a/ls1028ardb/R_SQPP_0x85bb/rcw_1300_sdboot.rcw b/ls1028ardb/R_SQPP_0x85bb/rcw_1300_sdboot.rcw +index 1908d8c..c930b83 100644 +--- a/ls1028ardb/R_SQPP_0x85bb/rcw_1300_sdboot.rcw ++++ b/ls1028ardb/R_SQPP_0x85bb/rcw_1300_sdboot.rcw +@@ -28,7 +28,7 @@ IIC3_PMUX=2 + IIC4_PMUX=2 + IIC5_PMUX=1 + IIC6_PMUX=3 +-CLK_OUT_PMUX=2 ++CLK_OUT_PMUX=1 + EC1_SAI4_5_PMUX=5 + EC1_SAI3_6_PMUX=5 + USB3_CLK_FSEL=39 +-- +2.17.1
Signature · 1 line
2.17.1
PATCH v4 8/9 package/nxp/qoriq-rcw: introduce BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE for boot mode
In reply to Changming HuangIntroduce BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE for the boot mode. Because the RCW binary can be stored in different media, for example:
sd - RCW locate in SD card, boot the board from SD card
emmc - RCW locate in eMMC chip, boot the board from eMMC chip
qspi - RCW locate in QSPI flash, boot the board from QSPI flash flexspi_nor - RCW locate in flexSPI, boot the board from flexSPI Nor/Nand flash
---
changes since v3:
1. split this option from board patch.
--- package/nxp/qoriq-rcw/Config.in.host | 6 ++++++ 1 file changed, 6 insertions(+)
package/nxp/qoriq-rcw/Config.in.host +6 -0
@@ -37,4 +37,10 @@ config BR2_PACKAGE_HOST_QORIQ_RCW_BIN If this option is empty, no rcw file is used. +config BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE + string "QorIQ RCW Boot mode" + depends on !BR2_PACKAGE_HOST_QORIQ_RCW_CUSTOM_PATH + help + Specify the boot mode, for example, sd, emmc, flexspi_nor. + endif
Signature · 1 line
2.17.1
PATCH v4 8/9 package/nxp/qoriq-rcw: introduce BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE for boot mode
Quoted 20 lines
Introduce
BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODEfor the boot mode. Because the RCW binary can be stored in different media, for example:
sd - RCW locate in SD card, boot the board from SD card
emmc - RCW locate in eMMC chip, boot the board from eMMC chip
qspi - RCW locate in QSPI flash, boot the board from QSPI flashflexspi_nor- RCW locate in flexSPI, boot the board from flexSPI Nor/Nand flashSigned-off-by Changming Huang <[email protected]>---
changes since v3:
1. split this option from board patch.--- package/nxp/qoriq-rcw/Config.in.host | 6 ++++++ 1 file changed, 6 insertions(+)package/nxp/qoriq-rcw/Config.in.host +0
-0
package/nxp/qoriq-rcw/Config.in.host config BR2_PACKAGE_HOST_QORIQ_RCW_BIN · line 46
Quoted 10 lines
package/nxp/qoriq-rcw/Config.in.host +6
-0@@ -37,4 +37,10 @@ config BR2_PACKAGE_HOST_QORIQ_RCW_BIN If this option is empty, no rcw file is used. +config BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE + string "QorIQ RCW Boot mode" + depends on !BR2_PACKAGE_HOST_QORIQ_RCW_CUSTOM_PATH + help + Specify the boot mode, for example, sd, emmc, flexspi_nor. + endif
Does it make sense to add any default value for this option ?
Regards,
Sergey
PATCH v4 9/9 board/nxp/ls1028ardb: new board
In reply to Changming HuangThis is to support NXP LS1028ARDB board in Buildroot. The board is setup to track the Linux at 4.19 via NXP LSDK-19.09.
The target will build uboot and RCW binary with arm-trusted-firmware support.
board/nxp/ls1028ardb/: scripts related with ls1028ardb nxp_ls1028ardb-64b_defconfig: defconfig boot from SD card
---
changes since v3:
1. merge previous version patch 8 and patch 9 to one.
2. split RCW options BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE to another patch.
3. remove scritps about emmc and xspi.
4. remove xspi and emmc configuration.
5. add new option BR2_ROOTFS_OVERLAY for 10-network.rules.
6. modify u-boot environment scripts, remove all setting not used.
7. remove the scripts which is not used by default configuration.
changes since v2:
1. Modify the qoriq-cadence-dp-firmware option in defconfig.
2. rename defconfig to nxp_ls1028*.
3. remove extra packages except busybox in defconfig.
4. modify the description of file genimage.xspi.cfg.template.
changes since v1:
1. add new option in configs/freescale_ls1028ardb-xxxx_defconfig.
--- board/nxp/common/ls/busybox.config | 9 ++ .../etc/udev/rules.d/10-network.rules | 16 ++++ board/nxp/ls1028ardb/genimage.sd.cfg.template | 52 ++++++++++++ board/nxp/ls1028ardb/post-image.sh | 57 +++++++++++++ board/nxp/ls1028ardb/readme.txt | 61 +++++++++++++ .../nxp/ls1028ardb/u-boot-environment-sd.txt | 13 +++ configs/nxp_ls1028ardb-64b_defconfig | 85 +++++++++++++++++++ 7 files changed, 293 insertions(+) create mode 100644 board/nxp/common/ls/busybox.config create mode 100644 board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-network.rules create mode 100644 board/nxp/ls1028ardb/genimage.sd.cfg.template create mode 100755 board/nxp/ls1028ardb/post-image.sh create mode 100644 board/nxp/ls1028ardb/readme.txt create mode 100644 board/nxp/ls1028ardb/u-boot-environment-sd.txt create mode 100644 configs/nxp_ls1028ardb-64b_defconfig
board/nxp/common/ls/busybox.config new file +9 -0
@@ -0,0 +1,9 @@ +# +# Additional Busybox Settings +# +CONFIG_TASKSET=y +CONFIG_FEATURE_TASKSET_FANCY=y +CONFIG_FEATURE_DF_FANCY=y +CONFIG_FEATURE_SEAMLESS_GZ=y +CONFIG_FEATURE_SEAMLESS_BZ2=y +CONFIG_FEATURE_SEAMLESS_XZ=y
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-network.rules new file +16 -0
@@ -0,0 +1,16 @@ +# ENETC rules +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.0", DRIVERS=="fsl_enetc", NAME:="eno0" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.1", DRIVERS=="fsl_enetc", NAME:="eno1" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.2", DRIVERS=="fsl_enetc", NAME:="eno2" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.6", DRIVERS=="fsl_enetc", NAME:="eno3" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.0", DRIVERS=="fsl_enetc_vf", NAME:="eno0vf0" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.1", DRIVERS=="fsl_enetc_vf", NAME:="eno0vf1" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.2", DRIVERS=="fsl_enetc_vf", NAME:="eno1vf0" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.3", DRIVERS=="fsl_enetc_vf", NAME:="eno1vf1" +# LS1028 switch rules +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p0", NAME="swp0" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p1", NAME="swp1" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p2", NAME="swp2" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p3", NAME="swp3" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p4", NAME="swp4" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p5", NAME="swp5"
board/nxp/ls1028ardb/genimage.sd.cfg.template new file +52 -0
52 lines not on this page · raw message
board/nxp/ls1028ardb/post-image.sh new file +57 -0
57 lines not on this page · raw message
board/nxp/ls1028ardb/readme.txt new file +61 -0
61 lines not on this page · raw message
board/nxp/ls1028ardb/u-boot-environment-sd.txt new file +13 -0
@@ -0,0 +1,13 @@ +baudrate=115200 +bootcmd=setenv bootargs root=/dev/mmcblk0p2 rootwait rw earlycon=uart8250,0x21c0500 console=ttyS0,115200 cma=256M video=1920x1080-32 at 60;mmcinfo;fatload mmc 0:1 ${dp_load} ${dp_file}; hdp load ${dp_load} ${dp_offset};fatload mmc 0:1 ${loadaddr} ${bootfile};fatload mmc 0:1 ${fdtaddr} ${fdtfile};booti ${loadaddr} - ${fdtaddr} +bootdelay=3 +bootfile=Image +fdtfile=fsl-ls1028a-rdb.dtb +loadaddr=0xa0000000 +fdtaddr=0xb0000000 +dp_file=ls1028a-dp-fw.bin +dp_load=0x90000000 +dp_offset=0x2000 +stderr=serial +stdin=serial +stdout=serial
configs/nxp_ls1028ardb-64b_defconfig new file +85 -0
85 lines not on this page · raw message
Signature · 1 line
2.17.1
PATCH v4 9/9 board/nxp/ls1028ardb: new board
Hi Jerry,
Quoted 323 lines · Changming Huang
This is to support NXP LS1028ARDB board in Buildroot. The board is setup to track the Linux at 4.19 via NXP LSDK-19.09.
The target will build uboot and RCW binary with arm-trusted-firmware support.
board/nxp/ls1028ardb/: scripts related with ls1028ardb nxp_ls1028ardb-64b_defconfig: defconfig boot from SD card
Signed-off-by Changming Huang <[email protected]>---
changes since v3:
1. merge previous version patch 8 and patch 9 to one.
2. split RCW optionsBR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODEto another patch.
3. remove scritps about emmc and xspi.
4. remove xspi and emmc configuration.
5. add new optionBR2_ROOTFS_OVERLAYfor 10-network.rules.
6. modify u-boot environment scripts, remove all setting not used.
7. remove the scripts which is not used by default configuration.changes since v2:
1. Modify the qoriq-cadence-dp-firmware option in defconfig.
2. rename defconfig to nxp_ls1028*.
3. remove extra packages except busybox in defconfig.
4. modify the description of file genimage.xspi.cfg.template.changes since v1:
1. add new option in configs/freescale_ls1028ardb-xxxx_defconfig.--- board/nxp/common/ls/busybox.config | 9 ++ .../etc/udev/rules.d/10-network.rules | 16 ++++ board/nxp/ls1028ardb/genimage.sd.cfg.template | 52 ++++++++++++ board/nxp/ls1028ardb/post-image.sh | 57 +++++++++++++ board/nxp/ls1028ardb/readme.txt | 61 +++++++++++++ .../nxp/ls1028ardb/u-boot-environment-sd.txt | 13 +++ configs/nxp_ls1028ardb-64b_defconfig | 85 +++++++++++++++++++ 7 files changed, 293 insertions(+) create mode 100644 board/nxp/common/ls/busybox.config create mode 100644 board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-network.rules create mode 100644 board/nxp/ls1028ardb/genimage.sd.cfg.template create mode 100755 board/nxp/ls1028ardb/post-image.sh create mode 100644 board/nxp/ls1028ardb/readme.txt create mode 100644 board/nxp/ls1028ardb/u-boot-environment-sd.txt create mode 100644 configs/nxp_ls1028ardb-64b_defconfigboard/nxp/common/ls/busybox.config new file +9
-0@@ -0,0 +1,9 @@ +# +# Additional Busybox Settings +# +CONFIG_TASKSET=y +CONFIG_FEATURE_TASKSET_FANCY=y +CONFIG_FEATURE_DF_FANCY=y +CONFIG_FEATURE_SEAMLESS_GZ=y +CONFIG_FEATURE_SEAMLESS_BZ2=y +CONFIG_FEATURE_SEAMLESS_XZ=yboard/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-network.rules new file +16
-0@@ -0,0 +1,16 @@ +# ENETC rules +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.0", DRIVERS=="fsl_enetc", NAME:="eno0" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.1", DRIVERS=="fsl_enetc", NAME:="eno1" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.2", DRIVERS=="fsl_enetc", NAME:="eno2" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.6", DRIVERS=="fsl_enetc", NAME:="eno3" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.0", DRIVERS=="fsl_enetc_vf", NAME:="eno0vf0" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.1", DRIVERS=="fsl_enetc_vf", NAME:="eno0vf1" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.2", DRIVERS=="fsl_enetc_vf", NAME:="eno1vf0" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.3", DRIVERS=="fsl_enetc_vf", NAME:="eno1vf1" +# LS1028 switch rules +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p0", NAME="swp0" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p1", NAME="swp1" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p2", NAME="swp2" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p3", NAME="swp3" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p4", NAME="swp4" +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5", DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p5", NAME="swp5"board/nxp/ls1028ardb/genimage.sd.cfg.template new file +52
-0@@ -0,0 +1,52 @@ +# Minimal SD card image for the NXP boards Template +# +# SD card image (sdcard.img) format: +# * the SD card must have 4 kB free space at the beginning, +# * U-Boot is dumped as is, +# * a FAT partition at offset 64 MB is containing Image and DTB files +# * a single root filesystem partition is required (ext2, ext3 or ext4) +# + +image boot.vfat { + vfat { + files = { + %FILES% + } + } + size = 256M +} + +image sdcard.img { + hdimage { + } + + partition rcw { + in-partition-table = "no" + image = "bl2_sd.pbl" + offset = 4096 + } + + partition u-boot { + in-partition-table = "no" + image = "fip.bin" + offset = 1M + } + + partition u-boot-environment { + in-partition-table = "no" + image = "uboot-env.bin" + offset = 5M + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + offset = 64M + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext2" + } +}board/nxp/ls1028ardb/post-image.sh new file +57
-0@@ -0,0 +1,57 @@ +#!/usr/bin/env bash +# args from BR2_ROOTFS_POST_SCRIPT_ARGS +# $2 linux building directory +# $3 buildroot top directory +# $4 u-boot building directory + +# +# dtb_list extracts the list of DTB files from BR2_LINUX_KERNEL_INTREE_DTS_NAME +# in ${BR_CONFIG}, then prints the corresponding list of file names for the +# genimage configuration file +# +dtb_file() +{ + local DTB_LIST="$(sed -n 's/^BR2_LINUX_KERNEL_INTREE_DTS_NAME="\([\/a-z0-9 \-]*\)"$/\1/p' ${BR2_CONFIG})" + + for dt in $DTB_LIST; do + echo -n "\"`basename $dt`.dtb\", " + done +} + +# +# genimage.sd.cfg.template: Boot from SD +# genimage.emmc.cfg.template: Boot from eMMC +# +genimage_type() +{ + if grep -Eq "^BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE=\"emmc\"$" ${BR2_CONFIG}; then + echo "genimage.emmc.cfg.template" + elif grep -Eq "^BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE=\"sd\"$" ${BR2_CONFIG}; then + echo "genimage.sd.cfg.template" + fi +} + +main() +{ + local FILES="$(dtb_file) "ls1028a-dp-fw.bin", "Image"" + local GENIMAGE_CFG="$(mktemp --suffix genimage.cfg)" + local GENIMAGE_TMP="${BUILD_DIR}/genimage.tmp" + + sed -e "s/%FILES%/${FILES}/" \ + board/nxp/ls1028ardb/$(genimage_type) > ${GENIMAGE_CFG} + + rm -rf "${GENIMAGE_TMP}" + + genimage \ + --rootpath "${TARGET_DIR}" \ + --tmppath "${GENIMAGE_TMP}" \ + --inputpath "${BINARIES_DIR}" \ + --outputpath "${BINARIES_DIR}" \ + --config "${GENIMAGE_CFG}" + + rm -f ${GENIMAGE_CFG} + + exit $? +} + +main $@board/nxp/ls1028ardb/readme.txt new file +61
-0@@ -0,0 +1,61 @@ +LS1028ARDB board is one platform based on LS1028A silicon for industry, +which is supported in LSDK-19.09. + +One simple image file is created by buildroot, which includes RCW, uboot, +Linux kernel, rootfs and other necessary binaries for this board. + +To program the image file created by buildroot into the flash. +There are two way to do it: + +1. Program the image file on PC machine for SD card boot + $ sudo dd if=./output/images/sdcard.img of=/dev/sdx + # or in some other host machine: + $ sudo dd if=./output/images/sdcard.img of=/dev/mmcblkx + + # find the right SD Card device name in your host machine and replace the + # ?sdx? or ?mmcblkx?. + +2. Program the image file on board for eMMC and XSPI boot +Make sure your board has ipaddr, netmask, and serverip defined to reach your +tftp server. + + 2.1 Program eMMC boot image file to eMMC chip + # Make sure output/images/sdcard.img is stored to tftp server + # Below command is one example + => tftpboot 0xa0000000 sdcard.img + => mmc dev 1 + => mmc erase 0 0x200000 + => mmc write 0xa0000000 0 0x200000 + + # The size "0x200000" will be changed when the image size is different. + + 2.2 Program XSPI boot image file to flash + # Make sure output/images/xspi.cpio.img is stored to tftp server + # Below command is one example + => tftpboot 0xa0000000 xspi.cpio.img + => sf probe + => sf erase 0 $filesize + => sf write 0xa0000000 0 $filesize + +3. Booting your new system +Before booting the new system, we should make sure the switch setting is right. +below switch setting is for each booting mode: + +-----------+---------------------+ + |Boot mode | Switch setting | + +---------------------------------+ + |SD boot | SW2[1~4] = 0b?1000 | + +---------------------------------+ + |eMMC boot | SW2[1~4] = 0b?1001 | + +---------------------------------+ + |XSPI boot | SW2[1~4] = 0b?1111 | + +-----------+---------------------+ + +or we use following command to reset the board in uboot prompt: + # boot from SD card + => qixis_reset sd + + # boot from eMMC chip + => qixis_reset emmc + + # boot from XSPI + => qixis_reset qspiboard/nxp/ls1028ardb/u-boot-environment-sd.txt new file +13
-0@@ -0,0 +1,13 @@ +baudrate=115200 +bootcmd=setenv bootargs root=/dev/mmcblk0p2 rootwait rw earlycon=uart8250,0x21c0500 console=ttyS0,115200 cma=256M video=1920x1080-32 at 60;mmcinfo;fatload mmc 0:1 ${dp_load} ${dp_file}; hdp load ${dp_load} ${dp_offset};fatload mmc 0:1 ${loadaddr} ${bootfile};fatload mmc 0:1 ${fdtaddr} ${fdtfile};booti ${loadaddr} - ${fdtaddr} +bootdelay=3 +bootfile=Image +fdtfile=fsl-ls1028a-rdb.dtb +loadaddr=0xa0000000 +fdtaddr=0xb0000000 +dp_file=ls1028a-dp-fw.bin +dp_load=0x90000000 +dp_offset=0x2000 +stderr=serial +stdin=serial +stdout=serialconfigs/nxp_ls1028ardb-64b_defconfig new file +28
-0@@ -0,0 +1,85 @@ +# Architecture +BR2_aarch64=y +BR2_cortex_a72=y + +# Filesystem +BR2_TARGET_ROOTFS_EXT2=y +BR2_TARGET_ROOTFS_EXT2_4=y + +# Hostname and issue +BR2_TARGET_GENERIC_HOSTNAME="LS1028ARDB" + +# toolchain +BR2_TOOLCHAIN_BUILDROOT_GLIBC=y +BR2_TOOLCHAIN_BUILDROOT_LIBC="glibc" + +# Linux headers same as kernel +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_19=y + +# bootloader +BR2_TARGET_UBOOT=y +BR2_TARGET_UBOOT_BOARDNAME="ls1028ardb_tfa" +BR2_TARGET_UBOOT_CUSTOM_GIT=y +BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://source.codeaurora.org/external/qoriq/qoriq-components/u-boot" +BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="LSDK-19.09" +BR2_TARGET_UBOOT_NEEDS_DTC=y +BR2_TARGET_UBOOT_FORMAT_BIN=n +BR2_TARGET_UBOOT_FORMAT_CUSTOM=y +BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME="u-boot-dtb.bin"
configs/nxp_ls1028ardb-64b_defconfig line 38
Quoted 10 lines
configs/nxp_ls1028ardb-64b_defconfig new file +10
-0+BR2_PACKAGE_UBOOT_TOOLS_MKIMAGE=y +BR2_TARGET_UBOOT_ENVIMAGE=y +BR2_TARGET_UBOOT_ENVIMAGE_SOURCE="board/nxp/ls1028ardb/u-boot-environment-sd.txt" +BR2_TARGET_UBOOT_ENVIMAGE_SIZE="0x2000" + +# Kernel +BR2_LINUX_KERNEL=y +BR2_LINUX_KERNEL_CUSTOM_GIT=y +BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://source.codeaurora.org/external/qoriq/qoriq-components/linux" +BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="LSDK-19.09-V4.19"
The LSDK has monthly bugfix releases and the most recent tag, currently, is LSDK-19.09-update-311219-V4.19. There have been some bugfixes since the tag you're proposing related to the Ethernet ports, among other things. Shouldn't you use the most recently available tag? Similar question for U-Boot and atf.
configs/nxp_ls1028ardb-64b_defconfig line 47
Quoted 9 lines
configs/nxp_ls1028ardb-64b_defconfig new file +9
-0+BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y +BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="$(LINUX_DIR)/arch/arm64/configs/lsdk.config" +BR2_LINUX_KERNEL_DTS_SUPPORT=y +BR2_LINUX_KERNEL_INTREE_DTS_NAME="freescale/fsl-ls1028a-rdb" +BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y +BR2_LINUX_KERNEL_IMAGE_TARGET_NAME="Image" + +# Serial port config +BR2_TARGET_GENERIC_GETTY=y
I think getty on downstream Buildroot for LS1028A-RDB doesn't work properly with this setting as y. What is different here?
Quoted 14 lines
configs/nxp_ls1028ardb-64b_defconfig new file +14
-0+BR2_TARGET_GENERIC_GETTY_PORT="ttyS0" + +# required tools to create the microSD image +BR2_PACKAGE_HOST_DOSFSTOOLS=y +BR2_PACKAGE_HOST_GENIMAGE=y +BR2_PACKAGE_HOST_MTOOLS=y +BR2_ROOTFS_POST_IMAGE_SCRIPT="board/nxp/ls1028ardb/post-image.sh" +BR2_ROOTFS_POST_SCRIPT_ARGS="$(LINUX_DIR) $(TOPDIR) $(UBOOT_DIR)" + +# busybox setting +BR2_PACKAGE_BUSYBOX_CONFIG_FRAGMENT_FILES="board/nxp/common/ls/busybox.config" +BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y + +# packages for rcw
configs/nxp_ls1028ardb-64b_defconfig line 71
Quoted 10 lines
configs/nxp_ls1028ardb-64b_defconfig new file +10
-0+BR2_PACKAGE_HOST_QORIQ_RCW=y +BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE="sd" +BR2_PACKAGE_HOST_QORIQ_RCW_BIN="ls1028ardb/R_SQPP_0x85bb/rcw_1300_sdboot.bin" + +#Display port firmware +BR2_PACKAGE_QORIQ_CADENCE_DP_FIRMWARE=y + +#eudev support +BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y +BR2_ROOTFS_OVERLAY="board/nxp/ls1028ardb/enetc_init_overlay"
Why is this called so specific "enetc_init_overlay" and not "rootfs_overlay"? If we want to add more files to the rootfs in the future, can't we just use the same rootfs overlay for that?
Quoted 15 lines
configs/nxp_ls1028ardb-64b_defconfig new file +14
-1+ +# Arm-Trusted-Firmware +BR2_TARGET_ARM_TRUSTED_FIRMWARE=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_FIP=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_UBOOT_AS_BL33=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_UBOOT_BL33_IMAGE="u-boot-dtb.bin" +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://source.codeaurora.org/external/qoriq/qoriq-components/atf" +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="LSDK-19.09" +BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="ls1028ardb" +BR2_TARGET_ARM_TRUSTED_FIRMWARE_IMAGES="fip.bin bl2_sd.pbl" +BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_TARGETS="pbl" +BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_DEPENDENCIES="host-qoriq-rcw" +BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_VARIABLES="BOOT_MODE=sd RCW=$(BINARIES_DIR)/rcw_1300_sdboot.bin" --
Quoted 2 lines
2.17.1
Thanks,
-Vladimir
[Buildroot] [EXT] Re: [PATCH v4 9/9] board/nxp/ls1028ardb: new board
Best Regards
Jerry Huang
Quoted 400 lines
-----Original Message-----
From: Vladimir Oltean <[email protected]>
Sent: Wednesday, February 5, 2020 8:39 PM
To: Jerry Huang <[email protected]>
Cc: buildroot at busybox.net; Thomas Petazzoni <[email protected]>; Michael Walle <[email protected]>; Matthew Weber <[email protected]>; geomatsi at gmail.com
Subject: [EXT] Re: [PATCH v4 9/9] board/nxp/ls1028ardb: new boardCaution: EXT Email
Hi Jerry,
Quoted 5 lines · Changming Huang
This is to support NXP LS1028ARDB board in Buildroot. The board is setup to track the Linux at 4.19 via NXP LSDK-19.09.
The target will build uboot and RCW binary with arm-trusted-firmware
support.
Quoted 9 lines
board/nxp/ls1028ardb/: scripts related with ls1028ardb nxp_ls1028ardb-64b_defconfig: defconfig boot from SD card
Signed-off-by Changming Huang <[email protected]>---
changes since v3:
1. merge previous version patch 8 and patch 9 to one.
2. split RCW optionsBR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODEtoanother patch.
Quoted 14 lines
3. remove scritps about emmc and xspi.
4. remove xspi and emmc configuration.
5. add new optionBR2_ROOTFS_OVERLAYfor 10-network.rules.
6. modify u-boot environment scripts, remove all setting not used.
7. remove the scripts which is not used by default configuration.changes since v2:
1. Modify the qoriq-cadence-dp-firmware option in defconfig.
2. rename defconfig to nxp_ls1028*.
3. remove extra packages except busybox in defconfig.
4. modify the description of file genimage.xspi.cfg.template.changes since v1:
1. add new option in configs/freescale_ls1028ardb-xxxx_defconfig.Quoted 8 lines
--- board/nxp/common/ls/busybox.config | 9 ++ .../etc/udev/rules.d/10-network.rules | 16 ++++ board/nxp/ls1028ardb/genimage.sd.cfg.template | 52 ++++++++++++ board/nxp/ls1028ardb/post-image.sh | 57 +++++++++++++ board/nxp/ls1028ardb/readme.txt | 61 +++++++++++++ .../nxp/ls1028ardb/u-boot-environment-sd.txt | 13 +++ configs/nxp_ls1028ardb-64b_defconfig | 85+++++++++++++++++++
Quoted 37 lines
7 files changed, 293 insertions(+) create mode 100644 board/nxp/common/ls/busybox.config create mode 100644 board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-network.ru les create mode 100644 board/nxp/ls1028ardb/genimage.sd.cfg.template create mode 100755 board/nxp/ls1028ardb/post-image.sh create mode 100644 board/nxp/ls1028ardb/readme.txt create mode 100644 board/nxp/ls1028ardb/u-boot-environment-sd.txt create mode 100644 configs/nxp_ls1028ardb-64b_defconfigboard/nxp/common/ls/busybox.config new file +9
-0@@ -0,0 +1,9 @@ +# +# Additional Busybox Settings +# +CONFIG_TASKSET=y +CONFIG_FEATURE_TASKSET_FANCY=y +CONFIG_FEATURE_DF_FANCY=y +CONFIG_FEATURE_SEAMLESS_GZ=y +CONFIG_FEATURE_SEAMLESS_BZ2=y +CONFIG_FEATURE_SEAMLESS_XZ=ydiff --git a/board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-network. rules b/board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-network. rules
new file mode 100644
index 0000000000..19f41634bdboard/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +1
-0+++ ork.rulesboard/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw line 2
Quoted 2 lines
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +2
-0@@ -0,0 +1,16 @@ +# ENETC rules +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.0",DRIVERS=="fsl_enetc", NAME:="eno0"
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw line 3
Quoted 1 line
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +1
-0+ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.1",DRIVERS=="fsl_enetc", NAME:="eno1"
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw line 4
Quoted 1 line
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +1
-0+ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.2",DRIVERS=="fsl_enetc", NAME:="eno2"
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw line 5
Quoted 1 line
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +1
-0+ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.6",DRIVERS=="fsl_enetc", NAME:="eno3"
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw line 6
Quoted 1 line
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +1
-0+ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.0",DRIVERS=="fsl_enetc_vf", NAME:="eno0vf0"
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw line 7
Quoted 1 line
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +1
-0+ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.1",DRIVERS=="fsl_enetc_vf", NAME:="eno0vf1"
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw line 8
Quoted 1 line
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +1
-0+ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.2",DRIVERS=="fsl_enetc_vf", NAME:="eno1vf0"
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw line 9
Quoted 1 line
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +1
-0+ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:01.3",DRIVERS=="fsl_enetc_vf", NAME:="eno1vf1"
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw line 11
Quoted 2 lines
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +2
-0+# LS1028 switch rules +ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5",DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p0", NAME="swp0"
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw line 12
Quoted 1 line
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +1
-0+ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5",DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p1", NAME="swp1"
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw line 13
Quoted 1 line
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +1
-0+ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5",DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p2", NAME="swp2"
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw line 14
Quoted 1 line
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +1
-0+ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5",DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p3", NAME="swp3"
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw line 15
Quoted 1 line
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +1
-0+ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5",DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p4", NAME="swp4"
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw line 16
Quoted 1 line
board/nxp/ls1028ardb/enetc_init_overlay/etc/udev/rules.d/10-netw new file +1
-0+ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:00:00.5",DRIVERS=="mscc_felix", ATTR{phys_port_name}=="p5", NAME="swp5"
Quoted 64 lines
board/nxp/ls1028ardb/genimage.sd.cfg.template new file +50
-0@@ -0,0 +1,52 @@ +# Minimal SD card image for the NXP boards Template # # SD card image +(sdcard.img) format: +# * the SD card must have 4 kB free space at the beginning, # * +U-Boot is dumped as is, # * a FAT partition at offset 64 MB is +containing Image and DTB files # * a single root filesystem partition +is required (ext2, ext3 or ext4) # + +image boot.vfat { + vfat { + files = { + %FILES% + } + } + size = 256M +} + +image sdcard.img { + hdimage { + } + + partition rcw { + in-partition-table = "no" + image = "bl2_sd.pbl" + offset = 4096 + } + + partition u-boot { + in-partition-table = "no" + image = "fip.bin" + offset = 1M + } + + partition u-boot-environment { + in-partition-table = "no" + image = "uboot-env.bin" + offset = 5M + } + + partition boot { + partition-type = 0xC + bootable = "true" + image = "boot.vfat" + offset = 64M + } + + partition rootfs { + partition-type = 0x83 + image = "rootfs.ext2" + } +}board/nxp/ls1028ardb/post-image.sh new file +0
-0board/nxp/ls1028ardb/post-image.sh line 6
Quoted 6 lines
board/nxp/ls1028ardb/post-image.sh new file +6
-0@@ -0,0 +1,57 @@ +#!/usr/bin/env bash +# args from BR2_ROOTFS_POST_SCRIPT_ARGS # $2 linux building directory +# $3 buildroot top directory # $4 u-boot building directory + +# +# dtb_list extracts the list of DTB files from
BR2_LINUX_KERNEL_INTREE_DTS_NAMEboard/nxp/ls1028ardb/post-image.sh
Quoted 6 lines
board/nxp/ls1028ardb/post-image.sh new file +6
-0+# in ${BR_CONFIG}, then prints the corresponding list of file names for the +# genimage configuration file +# +dtb_file() +{ + local DTB_LIST="$(sed -n's/^BR2_LINUX_KERNEL_INTREE_DTS_NAME="\([\/a-z0-9 \-]*\)"$/\1/p' ${BR2_CONFIG})"
board/nxp/ls1028ardb/post-image.sh
Quoted 13 lines
board/nxp/ls1028ardb/post-image.sh new file +13
-0+ + for dt in $DTB_LIST; do + echo -n "\"`basename $dt`.dtb\", " + done +} + +# +# genimage.sd.cfg.template: Boot from SD +# genimage.emmc.cfg.template: Boot from eMMC +# +genimage_type() +{ + if grep -Eq"^BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE=\"emmc\"$"
${BR2_CONFIG}; thenboard/nxp/ls1028ardb/post-image.sh line 27
Quoted 2 lines
board/nxp/ls1028ardb/post-image.sh new file +2
-0+ echo "genimage.emmc.cfg.template" + elif grep -Eq"^BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE=\"sd\"$" ${BR2_CONFIG}; then
board/nxp/ls1028ardb/post-image.sh
Quoted 12 lines
board/nxp/ls1028ardb/post-image.sh new file +12
-0+ echo "genimage.sd.cfg.template" + fi +} + +main() +{ + local FILES="$(dtb_file) "ls1028a-dp-fw.bin", "Image"" + local GENIMAGE_CFG="$(mktemp --suffix genimage.cfg)" + local GENIMAGE_TMP="${BUILD_DIR}/genimage.tmp" + + sed -e "s/%FILES%/${FILES}/" \ + board/nxp/ls1028ardb/$(genimage_type) >${GENIMAGE_CFG}
Review
Quoted 17 lines
board/nxp/ls1028ardb/post-image.sh new file +16
-0+ + rm -rf "${GENIMAGE_TMP}" + + genimage \ + --rootpath "${TARGET_DIR}" \ + --tmppath "${GENIMAGE_TMP}" \ + --inputpath "${BINARIES_DIR}" \ + --outputpath "${BINARIES_DIR}" \ + --config "${GENIMAGE_CFG}" + + rm -f ${GENIMAGE_CFG} + + exit $? +} + +main $@(quoted diff) +0
-0
b/board/nxp/ls1028ardb/readme.txtQuoted 14 lines
new file mode 100644
index 0000000000..713babd7c3board/nxp/ls1028ardb/readme.txt new file +9
-0@@ -0,0 +1,61 @@ +LS1028ARDB board is one platform based on LS1028A silicon for industry, +which is supported in LSDK-19.09. + +One simple image file is created by buildroot, which includes RCW, uboot, +Linux kernel, rootfs and other necessary binaries for this board. + +To program the image file created by buildroot into the flash. +There are two way to do it: +board/nxp/ls1028ardb/readme.txt line 19
Quoted 10 lines
board/nxp/ls1028ardb/readme.txt new file +10
-0+1. Program the image file on PC machine for SD card boot + $ sudo dd if=./output/images/sdcard.img of=/dev/sdx + # or in some other host machine: + $ sudo dd if=./output/images/sdcard.img of=/dev/mmcblkx + + # find the right SD Card device name in your host machine and replace the + # ?sdx? or ?mmcblkx?. + +2. Program the image file on board for eMMC and XSPI boot +Make sure your board has ipaddr, netmask, and serverip defined to reachyour
Quoted 12 lines
board/nxp/ls1028ardb/readme.txt new file +12
-0+tftp server. + + 2.1 Program eMMC boot image file to eMMC chip + # Make sure output/images/sdcard.img is stored to tftp server + # Below command is one example + => tftpboot 0xa0000000 sdcard.img + => mmc dev 1 + => mmc erase 0 0x200000 + => mmc write 0xa0000000 0 0x200000 + + # The size "0x200000" will be changed when the image size is different. +board/nxp/ls1028ardb/readme.txt
Quoted 10 lines
board/nxp/ls1028ardb/readme.txt new file +10
-0+ 2.2 Program XSPI boot image file to flash + # Make sure output/images/xspi.cpio.img is stored to tftp server + # Below command is one example + => tftpboot 0xa0000000 xspi.cpio.img + => sf probe + => sf erase 0 $filesize + => sf write 0xa0000000 0 $filesize + +3. Booting your new system +Before booting the new system, we should make sure the switch setting isright.
Review
Quoted 21 lines
board/nxp/ls1028ardb/readme.txt new file +20
-0+below switch setting is for each booting mode: + +-----------+---------------------+ + |Boot mode | Switch setting | + +---------------------------------+ + |SD boot | SW2[1~4] = 0b?1000 | + +---------------------------------+ + |eMMC boot | SW2[1~4] = 0b?1001 | + +---------------------------------+ + |XSPI boot | SW2[1~4] = 0b?1111 | + +-----------+---------------------+ + +or we use following command to reset the board in uboot prompt: + # boot from SD card + => qixis_reset sd + + # boot from eMMC chip + => qixis_reset emmc + + # boot from XSPI + => qixis_reset qspi(quoted diff) +0
-0
b/board/nxp/ls1028ardb/u-boot-environment-sd.txtboard/nxp/ls1028ardb/u-boot-environment-sd.txt line 2
Quoted 7 lines
new file mode 100644
index 0000000000..f91e6b585fboard/nxp/ls1028ardb/u-boot-environment-sd.txt new file +2
-0@@ -0,0 +1,13 @@ +baudrate=115200 +bootcmd=setenv bootargs root=/dev/mmcblk0p2 rootwait rwearlycon=uart8250,0x21c0500 console=ttyS0,115200 cma=256M video=1920x1080-32 at 60;mmcinfo;fatload mmc 0:1 ${dp_load} ${dp_file}; hdp load ${dp_load} ${dp_offset};fatload mmc 0:1 ${loadaddr} ${bootfile};fatload mmc 0:1 ${fdtaddr} ${fdtfile};booti ${loadaddr} - ${fdtaddr}
Review
Quoted 12 lines
board/nxp/ls1028ardb/u-boot-environment-sd.txt new file +11
-0+bootdelay=3 +bootfile=Image +fdtfile=fsl-ls1028a-rdb.dtb +loadaddr=0xa0000000 +fdtaddr=0xb0000000 +dp_file=ls1028a-dp-fw.bin +dp_load=0x90000000 +dp_offset=0x2000 +stderr=serial +stdin=serial +stdout=serial(quoted diff) +0
-0b/configs/nxp_ls1028ardb-64b_defconfig
Quoted 18 lines
new file mode 100644
index 0000000000..ede72ff0efconfigs/nxp_ls1028ardb-64b_defconfig new file +12
-0@@ -0,0 +1,85 @@ +# Architecture +BR2_aarch64=y +BR2_cortex_a72=y + +# Filesystem +BR2_TARGET_ROOTFS_EXT2=y +BR2_TARGET_ROOTFS_EXT2_4=y + +# Hostname and issue +BR2_TARGET_GENERIC_HOSTNAME="LS1028ARDB" + +# toolchainconfigs/nxp_ls1028ardb-64b_defconfig line 22
Quoted 10 lines
configs/nxp_ls1028ardb-64b_defconfig new file +10
-0+BR2_TOOLCHAIN_BUILDROOT_GLIBC=y +BR2_TOOLCHAIN_BUILDROOT_LIBC="glibc" + +# Linux headers same as kernel +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_19=y + +# bootloader +BR2_TARGET_UBOOT=y +BR2_TARGET_UBOOT_BOARDNAME="ls1028ardb_tfa" +BR2_TARGET_UBOOT_CUSTOM_GIT=y+BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://eur01.safelinks.protectio n.outlook.com/?url=https%3A%2F%2Fsource.codeaurora.org%2Fexternal%2Fqo riq%2Fqoriq-components%2Fu-boot&data=02%7C01%7Cjerry.huang%40nx p.com%7Ce7f374b4b8684185612a08d7aa3878c0%7C686ea1d3bc2b4c6fa92cd 99c5c301635%7C0%7C0%7C637165031827183010&sdata=Zhc99R0%2F7y tVSywcJTFySbuX99tLwthU2yAym2dGxEE%3D&reserved=0"
configs/nxp_ls1028ardb-64b_defconfig line 30
Quoted 8 lines
configs/nxp_ls1028ardb-64b_defconfig new file +7
-0+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="LSDK-19.09" +BR2_TARGET_UBOOT_NEEDS_DTC=y +BR2_TARGET_UBOOT_FORMAT_BIN=n +BR2_TARGET_UBOOT_FORMAT_CUSTOM=y +BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME="u-boot-dtb.bin" +BR2_PACKAGE_UBOOT_TOOLS_MKIMAGE=y +BR2_TARGET_UBOOT_ENVIMAGE=y+BR2_TARGET_UBOOT_ENVIMAGE_SOURCE="board/nxp/ls1028ardb/u-boot-e nvironment-sd.txt"
configs/nxp_ls1028ardb-64b_defconfig line 36
Quoted 6 lines
configs/nxp_ls1028ardb-64b_defconfig new file +5
-0+BR2_TARGET_UBOOT_ENVIMAGE_SIZE="0x2000" + +# Kernel +BR2_LINUX_KERNEL=y +BR2_LINUX_KERNEL_CUSTOM_GIT=y+BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://eur01.safelinks.protection .outlook.com/?url=https%3A%2F%2Fsource.codeaurora.org%2Fexternal%2Fqor iq%2Fqoriq-components%2Flinux&data=02%7C01%7Cjerry.huang%40nxp. com%7Ce7f374b4b8684185612a08d7aa3878c0%7C686ea1d3bc2b4c6fa92cd99 c5c301635%7C0%7C0%7C637165031827183010&sdata=qR633dpjWuIi3ck %2BWjyZOuJlhp4ZtiTLWy9YfiFzctc%3D&reserved=0"
Quoted 7 lines
configs/nxp_ls1028ardb-64b_defconfig line 38
Quoted 1 line
configs/nxp_ls1028ardb-64b_defconfig new file +1
-0+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="LSDK-19.09-V4.19"The LSDK has monthly bugfix releases and the most recent tag, currently, is LSDK-19.09-update-311219-V4.19. There have been some bugfixes since the tag you're proposing related to the Ethernet ports, among other things. Shouldn't you use the most recently available tag? Similar question for U-Boot and atf.
Ok, the uboot and Linux will use the latest LSDK version LSDK-19.09-update-311219 and LSDK-19.09-update-311219-V4.19.
Quoted 4 lines
configs/nxp_ls1028ardb-64b_defconfig line 39
Quoted 2 lines
configs/nxp_ls1028ardb-64b_defconfig new file +1
-0+BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y+BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="$(LINUX_DIR)/arch/arm64 /configs/lsdk.config"
Quoted 10 lines
configs/nxp_ls1028ardb-64b_defconfig line 47
Quoted 7 lines
configs/nxp_ls1028ardb-64b_defconfig new file +7
-0+BR2_LINUX_KERNEL_DTS_SUPPORT=y +BR2_LINUX_KERNEL_INTREE_DTS_NAME="freescale/fsl-ls1028a-rdb" +BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y +BR2_LINUX_KERNEL_IMAGE_TARGET_NAME="Image" + +# Serial port config +BR2_TARGET_GENERIC_GETTY=yI think getty on downstream Buildroot for LS1028A-RDB doesn't work properly with this setting as y. What is different here?
Ls1028ardb need the GETTY, otherwise we can't enter Linux prompt.
Quoted 22 lines
configs/nxp_ls1028ardb-64b_defconfig
Quoted 8 lines
configs/nxp_ls1028ardb-64b_defconfig new file +8
-0+BR2_TARGET_GENERIC_GETTY_PORT="ttyS0" + +# required tools to create the microSD image +BR2_PACKAGE_HOST_DOSFSTOOLS=y +BR2_PACKAGE_HOST_GENIMAGE=y +BR2_PACKAGE_HOST_MTOOLS=y +BR2_ROOTFS_POST_IMAGE_SCRIPT="board/nxp/ls1028ardb/post-image.sh" +BR2_ROOTFS_POST_SCRIPT_ARGS="$(LINUX_DIR) $(TOPDIR)$(UBOOT_DIR)"
configs/nxp_ls1028ardb-64b_defconfig line 53
Quoted 3 lines
configs/nxp_ls1028ardb-64b_defconfig new file +2
-0+ +# busybox setting+BR2_PACKAGE_BUSYBOX_CONFIG_FRAGMENT_FILES="board/nxp/common/ls /busybox.config"
configs/nxp_ls1028ardb-64b_defconfig line 63
Quoted 6 lines
configs/nxp_ls1028ardb-64b_defconfig new file +5
-0+BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y + +# packages for rcw +BR2_PACKAGE_HOST_QORIQ_RCW=y +BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE="sd"+BR2_PACKAGE_HOST_QORIQ_RCW_BIN="ls1028ardb/R_SQPP_0x85bb/rcw_1 300_sdboot.bin"
Quoted 11 lines
configs/nxp_ls1028ardb-64b_defconfig line 71
Quoted 7 lines
configs/nxp_ls1028ardb-64b_defconfig new file +7
-0+ +#Display port firmware +BR2_PACKAGE_QORIQ_CADENCE_DP_FIRMWARE=y + +#eudev support +BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y +BR2_ROOTFS_OVERLAY="board/nxp/ls1028ardb/enetc_init_overlay"Why is this called so specific "
enetc_init_overlay" and not "rootfs_overlay"? If we want to add more files to the rootfs in the future, can't we just use the same rootfs overlay for that?
Will change to rootfs_overlay to cover all options.
Quoted 35 lines
configs/nxp_ls1028ardb-64b_defconfig line 76
Quoted 6 lines
configs/nxp_ls1028ardb-64b_defconfig new file +5
-0+ +# Arm-Trusted-Firmware +BR2_TARGET_ARM_TRUSTED_FIRMWARE=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_FIP=y +BR2_TARGET_ARM_TRUSTED_FIRMWARE_UBOOT_AS_BL33=y+BR2_TARGET_ARM_TRUSTED_FIRMWARE_UBOOT_BL33_IMAGE="u-boot-dt b.bin"
configs/nxp_ls1028ardb-64b_defconfig line 78
Quoted 2 lines
configs/nxp_ls1028ardb-64b_defconfig new file +1
-0+BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y+BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://eur 01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsource.codeaurora. org%2Fexternal%2Fqoriq%2Fqoriq-components%2Fatf&data=02%7C01%7 Cjerry.huang%40nxp.com%7Ce7f374b4b8684185612a08d7aa3878c0%7C686ea 1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637165031827183010&sd ata=mnN%2FjI0pui6Tkc7oYBPPFqu0RvYPHTxW0xy%2FI2vONHo%3D&rese rved=0"
Quoted 1 line
+BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="LSDK- 19.09"
configs/nxp_ls1028ardb-64b_defconfig line 83
Quoted 4 lines
configs/nxp_ls1028ardb-64b_defconfig new file +3
-0+BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="ls1028ardb" +BR2_TARGET_ARM_TRUSTED_FIRMWARE_IMAGES="fip.bin bl2_sd.pbl" +BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_TARGETS="pbl"+BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_DEPENDENCIES="h ost-qoriq-rcw"
Quoted 1 line
+BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_VARIABLES="BOOT _MODE=sd RCW=$(BINARIES_DIR)/rcw_1300_sdboot.bin"
Quoted 3 lines
--
2.17.1Thanks,
-Vladimir
PATCH v4 1/9 package/nxp: new package directory
In reply to Changming HuangHi Changming,
Quoted 22 lines
package/nxp/helper.mk new file +22
-0+################################################################################ +# +# helper +# +################################################################################ + +# Helper for self-extracting binaries distributed by NXP. +# +# The --force option makes sure it doesn't fail if the source +# directory already exists. The --auto-accept skips the license check, +# as it is not needed in Buildroot because we have legal-info. Since +# there's a EULA in the binary file, we extract it in this macro, and +# it should therefore be added to the LICENSE_FILES variable of +# packages using this macro. Also, remember to set REDISTRIBUTE to +# "NO". Indeed, this is a legal minefield: the EULA specifies that the +# Board Support Package includes software and hardware (sic!) for +# which a separate license is needed... +# +# $(1): full path to the archive file +# +define NXP_EXTRACT_HELPER + awk 'BEGIN { start = 0; } \
package/nxp/helper.mk line 32
Quoted 10 lines
package/nxp/helper.mk new file +10
-0+ /^EOEULA/ { start = 0; } \ + { if (start) print; } \ + /<<EOEULA/ { start = 1; }' \ + $(1) > $(@D)/EULA + cd $(@D) && sh $(1) --force --auto-accept + find $(@D)/$(basename $(notdir $(1))) -mindepth 1 -maxdepth 1 -exec mv {} $(@D) \; + rmdir $(@D)/$(basename $(notdir $(1))) +endef + +include $(sort $(wildcard package/nxp/*/*.mk))
This seems to be a duplication of the FREESCALE_IMX_EXTRACT_HELPER, isn't it?
Do we then can remove the other one and use only the new "nxp" one?
By the way is there a plan to move all NXP specific packages (qoriq and imx) to the nxp subdir?
--
Heiko
Best Regards
Jerry Huang
Quoted 55 lines
-----Original Message-----
From: Heiko Thiery <[email protected]>
Sent: Wednesday, February 5, 2020 10:09 PM
To: Jerry Huang <[email protected]>
Cc: buildroot at busybox.net; olteanv at gmail.com; Michael Walle <[email protected]>; geomatsi at gmail.com; matthew.weber at collins.com; Thomas Petazzoni <[email protected]>
Subject: [EXT] Re: [Buildroot] [PATCH v4 1/9] package/nxp: new package directoryCaution: EXT Email
Hi Changming,
Quoted 1 line
+###############################################################
######package/nxp/helper.mk line 4
Quoted 5 lines
package/nxp/helper.mk new file +4
-0+########### +# +# helper +#+###############################################################
######Quoted 12 lines
package/nxp/helper.mk new file +12
-0+########### + +# Helper for self-extracting binaries distributed by NXP. +# +# The --force option makes sure it doesn't fail if the source # +directory already exists. The --auto-accept skips the license check, +# as it is not needed in Buildroot because we have legal-info. Since +# there's a EULA in the binary file, we extract it in this macro, and +# it should therefore be added to the LICENSE_FILES variable of # +packages using this macro. Also, remember to set REDISTRIBUTE to # +"NO". Indeed, this is a legal minefield: the EULA specifies that the +# Board Support Package includes software and hardware (sic!) for #package/nxp/helper.mk
Quoted 10 lines
package/nxp/helper.mk new file +10
-0+which a separate license is needed... +# +# $(1): full path to the archive file # define NXP_EXTRACT_HELPER + awk 'BEGIN { start = 0; } \ + /^EOEULA/ { start = 0; } \ + { if (start) print; } \ + /<<EOEULA/ { start = 1; }' \ + $(1) > $(@D)/EULA + cd $(@D) && sh $(1) --force --auto-accept + find $(@D)/$(basename $(notdir $(1))) -mindepth 1 -maxdepth 1-exec mv {} $(@D) \;
package/nxp/helper.mk line 32
Quoted 3 lines
package/nxp/helper.mk new file +3
-0+ rmdir $(@D)/$(basename $(notdir $(1))) endef + +include $(sort $(wildcard package/nxp/*/*.mk))This seems to be a duplication of the
FREESCALE_IMX_EXTRACT_HELPER, isn't it?
Do we then can remove the other one and use only the new "nxp" one?
Quoted 2 lines
By the way is there a plan to move all NXP specific packages (qoriq and imx) to the nxp subdir?
Yes, the helper is the duplication of FREESCALE_IMX_EXTRACT_HELPER.
Because Freescale is merged into NXP a few years ago, according to NXP's policy, we need to use nxp, instead of freescale. So, I think the packages related NXP should be move into nxp directory.
Quoted 2 lines
--
Heiko
Hi Jerry, Heiko,
Quoted 1 line · Jerry Huang
[snip]
Quoted 11 lines
Quoted 7 lines
This seems to be a duplication of the
FREESCALE_IMX_EXTRACT_HELPER, isn't it?
Do we then can remove the other one and use only the new "nxp" one?By the way is there a plan to move all NXP specific packages (qoriq and imx) to the nxp subdir?
Yes, the helper is the duplication of
FREESCALE_IMX_EXTRACT_HELPER.
Because Freescale is merged into NXP a few years ago, according to NXP's policy, we need to use nxp, instead of freescale. So, I think the packages related NXP should be move into nxp directory.
Is it really NXP policy though?
The thing is that LS1028A and several other boards are already supported by some downstream Buildroot patches, so it makes sense to keep using the folder names that we have there, i.e. "nxp" instead of changing to "freescale".
However I don't think there is any hard requirement either way, so in practice, whatever generates the least amount of friction should work.
Quoted 2 lines
Quoted 2 lines
--
Heiko
Thanks,
-Vladimir
Quoted 11 lines · On Thu, 6 Feb 2020 11:44:24 +0200 Vladimir Oltean <[email protected]> wrote:
Quoted 10 lines
Quoted 6 lines
This seems to be a duplication of the
FREESCALE_IMX_EXTRACT_HELPER, isn't it?
Do we then can remove the other one and use only the new "nxp" one?By the way is there a plan to move all NXP specific packages (qoriq and imx) to the nxp subdir?
Yes, the helper is the duplication of
FREESCALE_IMX_EXTRACT_HELPER.
Because Freescale is merged into NXP a few years ago, according to NXP's policy, we need to use nxp, instead of freescale. So, I think the packages related NXP should be move into nxp directory.
Quoted 5 lines
Is it really NXP policy though?
The thing is that LS1028A and several other boards are already supported by some downstream Buildroot patches, so it makes sense to keep using the folder names that we have there, i.e. "nxp" instead of changing to "freescale".
The proposal is not to change from nxp to freescale, but the opposite.
However, I think it's good to keep in mind that NXP's policy applies to whatever NXP does. The Buildroot project is independent and is not forced in any way to comply with NXP policies.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Hi Thomas,
Quoted 15 lines · Thomas Petazzoni
Quoted 11 lines · On Thu, 6 Feb 2020 11:44:24 +0200 Vladimir Oltean <[email protected]> wrote:
Quoted 10 lines
Quoted 6 lines
This seems to be a duplication of the
FREESCALE_IMX_EXTRACT_HELPER, isn't it?
Do we then can remove the other one and use only the new "nxp" one?By the way is there a plan to move all NXP specific packages (qoriq and imx) to the nxp subdir?
Yes, the helper is the duplication of
FREESCALE_IMX_EXTRACT_HELPER.
Because Freescale is merged into NXP a few years ago, according to NXP's policy, we need to use nxp, instead of freescale. So, I think the packages related NXP should be move into nxp directory.
Quoted 8 lines
Quoted 5 lines
Is it really NXP policy though?
The thing is that LS1028A and several other boards are already supported by some downstream Buildroot patches, so it makes sense to keep using the folder names that we have there, i.e. "nxp" instead of changing to "freescale".The proposal is not to change from nxp to freescale, but the opposite.
It depends on perspective, but I guess you already got the point.
Quoted 4 lines
However, I think it's good to keep in mind that NXP's policy applies to whatever NXP does. The Buildroot project is independent and is not forced in any way to comply with NXP policies.
Not trying to suggest otherwise, just to explain why the freescale -> nxp name change took place between Jerry's v2 and v3 of this patch series. The arguments have been brought on both sides, I don't think it's a big deal either way as long as the naming between device families is consistent and there isn't any unjustified duplication, so I'll just let Jerry make a decision one way or another.
Quoted 7 lines
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Regards,
-Vladimir