It is a pre-built binary, hence no control over passing correct LDFLAGS.
This used to be a warning and recently became an error. Fixes:
ERROR: vis-01.50.07.15-r1 do_package_qa: QA Issue: File /usr/bin/RadioApp in package vis doesn't have GNU_HASH (didn't pass LDFLAGS?) [ldflags]
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Workaround for these:
.../ti/drv/cppi/test/k2h/armv7/linux/fw_main.c:50: multiple definition of `coreNum';
./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/src/cppi_test.c:102: first defined here
.../ti/drv/cppi/test/k2h/armv7/linux/fw_main.c:50: multiple definition of `errorCount';
./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/src/cppi_test.c:102: first defined here
.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:85: multiple definition of `fw_passCfgVaddr';
./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:85: first defined here
.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:84: multiple definition of `fw_srioCfgVaddr';
./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:84: first defined here
.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:83: multiple definition of `fw_qmssDataVaddr';
./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:83: first defined here
.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:82: multiple definition of `fw_qmssCfgVaddr';
./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:82: first defined here
Needs to be fixed properly later:
https://gcc.gnu.org/gcc-10/porting_to.html
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Workaround for these:
qmss/mpm_transport_qmss_interface.so:(.bss+0x0): multiple definition of `fw_qmssCfgVaddr'; mpm_transport.so:(.bss+0x0): first defined here
qmss/mpm_transport_qmss_interface.so:(.bss+0x4): multiple definition of `fw_qmssDataVaddr'; mpm_transport.so:(.bss+0x4): first defined here
qmss/mpm_transport_qmss_interface.so:(.bss+0x8): multiple definition of `fw_srioCfgVaddr'; mpm_transport.so:(.bss+0x8): first defined here
qmss/mpm_transport_qmss_interface.so:(.bss+0xc): multiple definition of `fw_srioSerdesCfgVaddr'; mpm_transport.so:(.bss+0xc): first defined here
qmss/mpm_transport_qmss.so:(.bss+0x0): multiple definition of `fw_qmssCfgVaddr'; mpm_transport.so:(.bss+0x0): first defined here
qmss/mpm_transport_qmss.so:(.bss+0x4): multiple definition of `fw_qmssDataVaddr'; mpm_transport.so:(.bss+0x4): first defined here
qmss/mpm_transport_qmss.so:(.bss+0x8): multiple definition of `fw_srioCfgVaddr'; mpm_transport.so:(.bss+0x8): first defined here
qmss/mpm_transport_qmss.so:(.bss+0xc): multiple definition of `fw_srioSerdesCfgVaddr'; mpm_transport.so:(.bss+0xc): first defined here
qmss/mpm_transport_qmss_osal.so:(.bss+0x0): multiple definition of `fw_qmssCfgVaddr'; mpm_transport.so:(.bss+0x0): first defined here
qmss/mpm_transport_qmss_osal.so:(.bss+0x4): multiple definition of `fw_qmssDataVaddr'; mpm_transport.so:(.bss+0x4): first defined here
qmss/mpm_transport_qmss_osal.so:(.bss+0x8): multiple definition of `fw_srioCfgVaddr'; mpm_transport.so:(.bss+0x8): first defined here
qmss/mpm_transport_qmss_osal.so:(.bss+0xc): multiple definition of `fw_srioSerdesCfgVaddr'; mpm_transport.so:(.bss+0xc): first defined here
Needs to be fixed properly later:
https://gcc.gnu.org/gcc-10/porting_to.html
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Workaround for the following gcc10 errors:
.../gdbc6x/gdb/varobj.h:221: multiple definition of `ada_varobj_ops'; mi-cmd-var.o:.../gdbc6x/gdb/./varobj.h:221: first defined here
.../gdbc6x/gdb/varobj.h:220: multiple definition of `java_varobj_ops'; mi-cmd-var.o:.../gdbc6x/gdb/./varobj.h:220: first defined here
.../gdbc6x/gdb/varobj.h:219: multiple definition of `cplus_varobj_ops'; mi-cmd-var.o:.../gdbc6x/gdb/./varobj.h:219: first defined here
.../gdbc6x/gdb/varobj.h:218: multiple definition of `c_varobj_ops'; mi-cmd-var.o:.../gdbc6x/gdb/./varobj.h:218: first defined here
Needs to be resolved properly in the code later:
https://gcc.gnu.org/gcc-10/porting_to.html
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Workaround for this gcc10 error:
.../linux/src/api/gates/GateHWSpinlock.c:96: multiple definition of `_GateHWSpinlock_cfgParams';
.libs/Ipc.o:.../linux/src/api/Ipc.c:97: first defined here
Needs to be resolved properly in the code:
https://gcc.gnu.org/gcc-10/porting_to.html
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Cc: Suman Anna <s-anna@ti.com>
It was giving this warning for years, finally gone:
| warning: `sys_errlist' is deprecated; use `strerror' or `strerror_r' instead
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Cc: Suman Anna <s-anna@ti.com>
update am64x rtos firmware to keep pinmux and control MMRs
remain unlocked now since linux needs this to be unlock.
this fix the USB and performance degradation issues.
am64xx: 07.03.00.19
Signed-off-by: Shiju Sivasankaran <shiju@ti.com>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Switch to using all of multi-certificate boot images. This allows us
to create bootable images - in this case, we are missing tiboot3.bin
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
IMAGE type and dependencies can easily be centralized to SoC include
file. This is necessary to make sure that we don't do the duplication
and having multiple places to fix up.
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Switch to using all of multi-certificate boot images. This allows us
to create bootable images - in this case, we are missing tiboot3.bin
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
wic and tar dependency on trusted firmware is wrong. It is u-boot build
that depends on trusted firmware deployment and is correctly handled by
u-boot recipe. No point in duplicating that dependency, so just clean it
all up.
Reported-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
We use the default IMAGE_BOOT_FILES configuration which matches up with
legacy boot configuration. Document the same to allow folks to
understand by just looking at the SoC include file.
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
We use the default IMAGE_BOOT_FILES configuration which matches up with
legacy boot configuration. Document the same to allow folks to
understand by just looking at the SoC include file.
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Lets keep things consistent by providing two possibilities for platforms
to pick from - legacy boot and multi-certificate boot.
In legacy boot, the base bootloader and system firmware are
maintained as separate binaries (tiboot3.bin and sysfw.itb).
In multi-certificate boot that newer K3 devices support, ROM is smarter
and can handle multiple x509 certificate based images: so we can strip
out the sysfw.itb and integrate it as part of tiboot3.bin itself. This
improves authentication and overall system boot times since we are now
able to boot both the system controller and the boot processor in
parallel.
We do have a scheme currently to identify the images necessary for boot
etc, but things are handled on a platform conf file basis. We can
improve that by introducing the pattern at the top level include and use
the relevant pattern in platforms as needed.
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Remove duplicate machine-specific redefines of UBOOT_BINARY, UBOOT_IMAGE and
UBOOT_SYMLINK variables, as they are already defined with same values in the
common k3r5.inc file.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Reviewed-by: Nishanth Menon <nm@ti.com>
Fixes:
.../scripts/secure-binary-image.sh: line 69: openssl: command not found
.../scripts/secure-binary-image.sh: line 78: openssl: command not found
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
OPTEEMACHINE name as defined in the optee_os project [1] for
j721e is k3-j721e.
This patch fixes the name to correct target.
[1]: 87613cf952
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Acked-by: Denys Dmytriyenko <denys@konsulko.com>
ti-upstream-tools[1] repository carries the overlays and defconfig
fragments that we don't wish to overload upstream kernel community with.
The reason for that being these are constantly on churn as our test
coverage increases etc. Currently we reuse the "BRANCH" variable to also
matchup with kernel and ti-upstream-tools repositories as well.
This can tend to be a little painful if we decide to start testing
various kernel configurations - RT etc.. So, lets just split out the
TOOLS_BRANCH separated from the branch we use for kernel. Even though
the branch remains the exact same at this point.
[1] https://git.ti.com/cgit/ti-linux-kernel/ti-upstream-tools/
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Add GNU Multiple Precision Arithmetic Library as a dependency for
mainline linux builds. These are necesary for kernel to handle gcc
plugins for builtins.h
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
The J7200/AM64 ti-sci-fw needs to be installed in the deploy
directory so that it can be packaged in Processor SDK bundle
This is required because the ti-sci-fw is needed in the
installer prebuilt-images in order to build the combined boot
image for J7200/AM64
Signed-off-by: Lucas Weaver <l-weaver@ti.com>
update ti-rtos-metadata and ti-rtos-firmware recipes of meta-ti to
pick AM64x rtos firmware from mcu-plus-sdk instead of PDK.
Other devices such as AM65x, J7 continue to use fw from PDK.
Built and tested both IPC echo test applications - "rpmsg_client_sample”
& “rpmsg_char_simple”. Both tests passed for all remote R5F cores
on AM64x EVM
Signed-off-by: Shiju Sivasankaran <shiju@ti.com>
[praneeth@ti.com: rebase to dunfell/next]
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Boards like the beaglebone currently hardcode "u-boot" as a dependency
for the image and the wic format, and this prevents one from choosing
a different bootloader via:
PREFERRED_PROVIDER_virtual/bootloader = "non-u-boot-bootloader"
Depending on "virtual/bootloader" instead of "u-boot" fixes this.
Signed-off-by: Vivien Didelot <vdidelot@pbsc.com>
Suggested-by: Denys Dmytriyenko <denis@denix.org>
Reviewed-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Between j7200 firmware tags 07.03.00.10 to 07.03.00.16
the downloadable weburl link changed
from *processor-sdk-rtos-jacinto7 to *processor-sdk-rtos-j7200.
This patch is to fix the recipe to pick the firmware from the
expected location on the new tag.
Fixes j7200 build error reported due to
77cdfa9f65 ("ti-rtos: Update metadata and versions for RTOS firmware")
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Reviewed-by: Denys Dmytriyenko <denis@denix.org>
And lets work with the latest kernel
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Bump up our recipe version for ti-upstream-tools for updates in config
files needed for latest kernel
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Update the image gen and linux-firmware commit SHAs so that
am65x, j7200 and j721e also picks v2021.01 sysfw and the applicable
DM update with following version
* 07.03.00.12 for J721E
* 07.03.00.10 for J7200
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
