aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
6 daysarm-bsp/n1sdp: Use git clone to fetch FW for the N1SDPyocto-4.0.44.0.4kirkstoneAdam Johnston
git.linaro.org/landing-teams/working no longer seems to serve snapshots in tar.gz format, breaking the N1SDP build for kirkstone. Using same tag as the existing snapshot, fetch the binaries with a conventional git clone, as per master. Signed-off-by: Adam Johnston <adam.johnston@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2024-03-20arm/opencsd: upgrade to 1.2.1 to fix kernel buildRoss Burton
Linux 5.15.149 contains the following change[1]: perf cs-etm: Bump minimum OpenCSD version to ensure a bugfix is present Since commit d927ef5004ef ("perf cs-etm: Add exception level consistency check"), the exception that was added to Perf will be triggered unless the following bugfix from OpenCSD is present: [...] The opencsd requirement is now 1.2.1 onwards, but the kirkstone branch has 1.2.0. The 1.2.1 release was just three bugfixes on top of 1.2.0 so this should be a safe upgrade: 3fecfb0 opencsd: etm4x: Update etm4x / ete decoder to flush context to client immediately. db97bbc opencsd: decode: Update decoder base to implement memory accessor invalidation. a7b77aa opencsd: memaccess: Allow memory accessors to have cache invalidated by decoder. [1] a7af1be5cf5507dd6c157b7a25453942f805db76 Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2023-08-24arm-bsp/secure-partitions: fix build with GCC 11.4yocto-4.0.34.0.3Ross Burton
GCC 11.4 has improved code generation and needs the __aarch64_cas4_sync intrinsic from libgcc, but one of the modules here doesn't link to libgcc. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2023-07-10arm/edk2: add support for qemuarm and qemuarm64Jon Mason
Add basic support for running edk2 on qemuarm and qemuarm64. This necessitated the need to add ACPI and EFI to the default kernel configs for these machines. Signed-off-by: Jon Mason <jon.mason@arm.com>
2023-04-13arm-bsp/linux-yocto: Fix N1SDP PCI quirk patchyocto-4.0.24.0.2Vikas Katariya
The poky commit 74f086529911bdaf07a8414d50de411e20739541 updates the kernel to v5.15.103 which breaks the PCI quirk patch for the N1SDP. Signed-off-by: Vikas Katariya <vikas.katariya@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2023-02-09CI: pin to kas 3.2 as 3.2.1 failsRoss Burton
For some reason the kas 3.2.1 container fails: No such file or directory: '/builds/engineering/yocto/meta-arm/ci/ci/base.yml' Note the repeated /ci/, which is wrong. Pin the kas container to 3.2 for now until this is resolved. Signed-off-by: Ross Burton <ross.burton@arm.com>
2023-02-04arm-bsp/firmware-image-juno: Fix deployment of compressed ImageDaniel Díaz
A recent commit compressed the kernel image (to Image.gz) and by default enabled an initramfs image. In the case for when such that (initramfs) is not desirable, the deploy step of the Juno firmware will still try to install the Image file, (not Image.gz), so this fails: ERROR: firmware-image-juno-1.0-r0 do_deploy: ExecutionError('/oe/build/tmp-glibc/work/juno-oe-linux/firmware-image-juno/1.0-r0/temp/run.do_deploy.360477', 1, None, None) ERROR: Logfile of failure stored in: /oe/build/tmp-glibc/work/juno-oe-linux/firmware-image-juno/1.0-r0/temp/log.do_deploy.360477 Log data follows: | DEBUG: Executing python function sstate_task_prefunc | DEBUG: Python function sstate_task_prefunc finished | DEBUG: Executing shell function do_deploy | cp: cannot stat '/oe/build/tmp-glibc/deploy/images/juno/Image': No such file or directory | WARNING: /oe/build/tmp-glibc/work/juno-oe-linux/firmware-image-juno/1.0-r0/temp/run.do_deploy.360477:152 exit 1 from 'cp -L -f /oe/build/tmp-glibc/deploy/images/juno/Image /oe/build/tmp-glibc/work/juno-oe-linux/firmware-image-juno/1.0-r0/image/juno-firmware-19.06/SOFTWARE/' | WARNING: Backtrace (BB generated script): | #1: do_deploy, /oe/build/tmp-glibc/work/juno-oe-linux/firmware-image-juno/1.0-r0/temp/run.do_deploy.360477, line 152 | #2: main, /oe/build/tmp-glibc/work/juno-oe-linux/firmware-image-juno/1.0-r0/temp/run.do_deploy.360477, line 163 NOTE: recipe firmware-image-juno-1.0-r0: task do_deploy: Failed ERROR: Task (../meta-arm/meta-arm-bsp/recipes-bsp/images/firmware-image-juno.bb:do_deploy) failed with exit code '1' This updates the else case for when an initramfs image is not in use so that the right kernel image is deployed, by using the KERNEL_IMAGETYPE variable, to use either version of the kernel image. Signed-off-by: Daniel Díaz <daniel.diaz@linaro.org> Signed-off-by: Jon Mason <jon.mason@arm.com>
2023-01-30Revert "CI: add patches to fix perf with clang"Ross Burton
These fixes have been merged into oe-core so are no longer needed. This reverts commit e3cb27c06a94c2a806602bf3544efc550ed3ab07. Signed-off-by: Ross Burton <ross.burton@arm.com>
2023-01-18arm-bsp/linux-yocto: Update juno patchJon Mason
Update the juno kernel patch to work with the latest kirkstone kernel, and remove the workaround. Signed-off-by: Jon Mason <jon.mason@arm.com>
2023-01-18arm-bsp/juno: move to compressed initramfs imageJon Mason
Change u-boot and machine config to default to booting a compressed initramfs. This allows for easier testing. A compressed image is needed as the image is too big for the storage, and the error notifying of such is vague. Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-12-19arm-bsp/linux-yocto: temporarily downgrade juno to 5.15.72Ross Burton
The mailbox patches don't apply to 5.15.78 so until they can be rebased and retested, pin the kernel to 5.15.72. Signed-off-by: Ross Burton <ross.burton@arm.com>
2022-12-19CI: add patches to fix perf with clangRoss Burton
Apply two in-flight patches to fix the build of perf with clang. Signed-off-by: Ross Burton <ross.burton@arm.com>
2022-12-16ci/get-binary-toolchains: rewrite, slightlyRoss Burton
Add set -e so errors are fatal. Allow HOST_ARCH and VER to be overridden by the environment, for testing. Pull the tarball basename into a variable to reduce duplication. Turn the wget call into a function to reduce duplication. Drop the big-endian binaries as we never use those. Signed-off-by: Ross Burton <ross.burton@arm.com>
2022-12-15CI: remove armcompiler referencesRoss Burton
Arm Compiler has been removed, so remove it from the CI. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-12-15arm-toolchain/armcompiler: remove recipeRoss Burton
As far as we know nobody is actually using the Arm Compiler recipe: 6.17 does a network operation on every call to check the license and this fails with the network isolation that do_compile has in kirkstone, and 6.18 is behind a loginwall so we cannot download it in a recipe. Unless we have actual users asking for a recipe, remove it from the layer to avoid confusion. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-12-15arm/trusted-firmware-m: remove compiler optionsRoss Burton
The recipe supports the use of both Arm's binary GCC (aka GNU Arm Embedded Compiler, or gnu-rm) and binary Clang (aka Arm Compiler). However, armcompiler was never tested and doesn't work: 6.17 does a network operation on every call to check the license which fails with the network isolation in do_compile tasks, and 6.18 is behind a loginwall so we can't automatically fetch it in a recipe. Simplify the recipe to hardcode the use of gnu-rm, and remove the clang support. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-12-15CI: define DEFAULT_TAG and CPU_REQUESTJon Mason
DEFAULT_TAG and CPU_REQUEST are being used to help with internal Gitlab pipeline setups know which type of machines to run on, but has no value outside of Arm Corp. Gitlab CI allows for variables to be overridden by default. So, we can give it a default value of NULL/empty and have everything work internally and externally by default. Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-12-14CI: no need to install telnetRoss Burton
The kas 3.1 container has telnet in. We can also remove python3-subunit once kas 3.2 is released. Signed-off-by: Ross Burton <ross.burton@arm.com>
2022-12-14CI: use the .setup fragment in machine-coverageRoss Burton
Signed-off-by: Ross Burton <ross.burton@arm.com>
2022-12-14CI: add tags to all jobsRoss Burton
Tag all jobs with the DEFAULT_TAG variable so each instance can control what tags the jobs have, whilst still explicitly tagging the jobs which need specific tags (such as x86_64 for jobs which need to run x86-only binaries) Signed-off-by: Ross Burton <ross.burton@arm.com>
2022-12-14CI: add variables needed for k8s runnersRoss Burton
The Kas container needs to use the entrypoint as that is where the user changes from root to a normal user. Also set the KUBERNETES_CPU_REQUEST to the variable CPU_REQUEST as this needs to be tuned per-deployment. Signed-off-by: Ross Burton <ross.burton@arm.com>
2022-11-14arm-bsp/linux-yocto: refresh juno-dts-mhu-doorbell.patch for 5.15.72Ross Burton
The linux-yocto recipe in oe-core upgraded to 5.15.72, so rebase the doorbell patches to apply correctly. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-10-19arm-bsp/machine: corstone1000: disable pulling the kernel into the initramfsyocto-4.0.14.0.1Abdellatif El Khlifi
exclude kernel-image-* packages from the rootfs Signed-off-by: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-10-19arm-bsp/corstone1000: use compressed kernel imageAbdellatif El Khlifi
To fit the kernel image into the allotted space, a compressed kernel image is now needed. Use the Image.gz from the kernel build process and change the relevant places to use the new image name. This also necessitates adding an unzip command to u-boot to uncompress it to memory (and the loadm is still needed to setup the efi mem boot device). Also, the unzipped image is larger than before. So, increase the size that loadm is copying. This change shrinks the initramfs bundle size from 12MB to 4.8MB Signed-off-by: Jon Mason <jon.mason@arm.com> Signed-off-by: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-09-29arm-bsp/n1sdp: update linux-yocto patchesJon Mason
Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-09-27arm/fvp-base-r-aem: upgrade to version 11.19.14Jiacheng Tang
Update version in documentation. Issue-Id: SCM-5168 Signed-off-by: Jiacheng Tang <jiacheng.tang@arm.com> Change-Id: Ic6302540e5ec3eb4d2ef436018cba7328f6dfc68 Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-09-14arm/lib: Specify the FVP environment variables explicitlyPeter Hoyes
It is sometimes useful to be able to configure the behavior of FVPs using environment variables, e.g. for licensing or plugins. Add a new FVP option: FVP_ENV_PASSTHROUGH, which allows the Bitbake variables to be passed to the environment to be specified explicitly (in a similar way to BB_ENV_PASSTHROUGH). This ensures that: * FVPs launched via runfvp have a reproducable environment * FVPs launched via testimage (which run from an isolated Bitbake task) can receive environment variables Change the self-tests to use cwd instead of PATH to find the mock FVPs, as the PATH environment variable is no longer passed through. Issue-Id: SCM-4964 Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com> Change-Id: Idf6ac6d41fda4cd5f950bc383c2fc1fa1acdf4e3 Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-09-14arm/trusted-firmware-m: fix branch issueJon Mason
The 1.5.x branch no longer exists on the tf-m git repo, but the SHA is still present. Update the branch name to allow for this. Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-09-12arm-bsp:ffa-debugfs: update git SHA for v2.1.0Vishnu Banavath
git sha on https://git.gitlab.arm.com/linux-arm/linux-trusted-services/-/tree/v2.1.0 has been changed recently for v2.1.0 tag. This change is to update ffa-debugfs-mod_2.1.0.bb to fetch correct git SHA. Signed-off-by: Vishnu Banavath <vishnu.banavath@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-09-10arm-toolchain/gcc,external-arm-toolchain: resolve conflict with gcc headersDenys Dmytriyenko
Historically external-arm-toolchain recipe packaged all gcc headers from ${libdir}/gcc/${TARGET_SYS}/${BINV}/include - some would be picked up by packages like gcc-sanitizers, libssp-dev. libquadmath-dev or libgomp-dev. The rest would fall into catch-all libgcc-dev package. Unfortunately, that could result in a conflict with a target gcc, which also packages some of those files, like unwind.h or stddef.h, among others. The conflict could be seen with this config: EXTRA_IMAGE_FEATURES += "dev-pkgs tools-sdk" TCMODE = "external-arm" EXTERNAL_TOOLCHAIN = "/OE/toolchains/gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu" And the error message is: Error: Transaction test error: file /usr/lib/gcc/aarch64-poky-linux/11.2.1/include/stddef.h conflicts between attempted installs of libgcc-s-dev-11.2.1-r0.1.cortexa57 and gcc-arm+11.2-r2022.02.1.cortexa57 file /usr/lib/gcc/aarch64-poky-linux/11.2.1/include/unwind.h conflicts between attempted installs of libgcc-s-dev-11.2.1-r0.1.cortexa57 and gcc-arm+11.2-r2022.02.1.cortexa57 Modify external-arm-toolchain recipe according to how libgcc in OE-Core handles those header files by removing and not packaging them: https://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/gcc/libgcc-common.inc#n40 Also need to adjust gcc recipe to pick up unwind.h from EXTERNAL_TOOLCHAIN location now, since libgcc-dev no longer carries it, and install it into STAGING_LIBDIR_NATIVE, where OE-Core gcc-target.inc expects it from gcc-cross: https://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/gcc/gcc-target.inc#n164 Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-09-01arm/oeqa: Make linuxboot test case timeout configurablePeter Hoyes
In complex stacks, e.g. with many cores or many init scripts, the time to Linux shell may be more than 10 minutes. Make the boot timeout configurable using TEST_FVP_LINUX_BOOT_TIMEOUT, leaving the default value at 10 minutes. Issue-Id: SCM-4958 Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com> Change-Id: Ie074acd4b4509d0230d1f77a2a527d497bb295ce Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-08-23optee-ftpm: Update to "main" branchLeo Yan
Since the github repository doesn't contain a "master" branch but has the "main" branch now, this patch updates to the "main" branch so can download the repository successfully. CC: Ilias Apalodimas <ilias.apalodimas@linaro.org> CC: Jerome Forissier <jerome.forissier@linaro.org> CC: Peter Griffin <peter.griffin@linaro.org> Signed-off-by: Leo Yan <leo.yan@linaro.org> Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-08-09optee: use CFLAGS{32,64} to pass --sysrootJerome Forissier
Since upstream OP-TEE 3.16.0, CFLAGS32 and CFLAGS64 can be used to set the sysroot option that previously required the LIBGCC_LOCATE_CFLAGS patches. Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org> Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-08-09docs: Introduce meta-arm OEQA documentationPeter Hoyes
Add documentation for how to use the OEQA framework to test targets in meta-arm. Include instructions on using OEFVPTarget as well as the OEFVPSerialTarget introduced by the recent refactor of runfvp. Issue-Id: SCM-4954 Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com> Change-Id: I146ec1c82214471fe9d18a999fd92efb38f652f9 Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-08-09docs: Update FVP_CONSOLES in runfvp documentationPeter Hoyes
The runfvp refactor to enable OEFVPSerialTarget created FVP_CONSOLES which maps the names used for serial ports in test cases to the names used for serial ports in the FVP stdout. Refactor the FVP_CONSOLE section -> FVP_CONSOLES, noting the the 'default' console is still used for the --console runfvp flag. Issue-Id: SCM-4954 Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com> Change-Id: Ieb13d74cfd425900f44b4b2e6d125393e7b456ad Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-08-08gem5: add meta-arm-bsp dependencyJon Mason
meta-gem5 needs the 5.4 kernel, which is only present in the meta-arm-bsp layer. Add this as a dependency to resolve issues. Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-08-04arm-toolchain/layer.conf: remove BB_DANGLINGAPPENDS_WARNONLYRoss Burton
This appears to be historical from when the toolchain was in meta-linaro. It isn't needed anymore, there's one bbappend in meta-arm-toolchain for grub which is part of oe-core, so will never be dangling. This variable has a global effect, so leaving it in here has a negative impact on users. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-08-03optee.inc: update setting for OPTEE_ARCHChangqing Li
lib32-optee-os do_compile failed since OPTEE_ARCH is not set correctly. In file included from lib/libutee/include/link.h:9, from lib/libutee/arch/arm/tcb.c:37: lib/libutee/include/elf.h:67:2: error: #error Unknown architecture 67 | #error Unknown architecture | ^~~~~ In file included from lib/libutee/arch/arm/tcb.c:37: lib/libutee/include/link.h:13:9: error: unknown type name 'Elf_Addr' 13 | Elf_Addr dlpi_addr; /* module relocation base */ Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-08-03runfvp: Stop the FVP when telnet shuts down cleanlyPeter Hoyes
At the moment, when using the --console flag, if telnet is shut down cleanly (i.e. by typing "quit" at the prompt instead of Ctrl+C), runfvp still waits on the FVP to exit of its own accord, so hangs. Move the fvp.run() call so that when telnet quits, it immediately proceeds to shut down the FVP. Issue-Id: SCM-4954 Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com> Change-Id: I2169c99586a1eebc2c6ab4b2e15fb0c769fc81a8 Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-08-02optee-os.inc: support multilibChangqing Li
Run command: bitbake optee-os && bitbake lib32-optee-os bitbake lib32-optee-os will fail with following error since bitbake optee-os already deploy same file under the path. RROR: lib32-optee-os-3.12.0+gitAUTOINC+3d47a131bc-r0 do_deploy: The recipe lib32-optee-os is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /build/tmp-glibc/deploy/images/qemuarm64/optee/tee.elf (matched in manifest-qemuarm64-optee-os.deploy) Fix by deploy them to differernt dir Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-07-30arm/edk2-firmware: cherry pick gcc 12.x compatibility patchesMaciej Borzecki
Cherry pick gcc 12.x compatibility patches from the upstream. Signed-off-by: Maciej Borzecki <maciek@thing.com>
2022-07-27arm-bsp/sdcard-image-n1sdp: Fix N1SDP dependenciesAdam Johnston
When enabling trusted boot, the UEFI binary was replaced with a FIP image (which contains the UEFI binary), therefore the SD card image should depend on trusted-firmware-a rather than edk2-firmware. Signed-off-by: Adam Johnston <adam.johnston@arm.com>
2022-07-27arm-bsp/edk2-firmware: Add NT_FW_CONFIG to N1SDP to fix aborts when ↵Adam Johnston
accessing virtual memory NT_FW_CONFIG DTB contains platform information passed by TF-A boot stage. This information is used for Virtual memory map generation during PEI phase and passed on to DXE phase as a HOB, where it is used in ConfigurationManagerDxe. Signed-off-by: Adam Johnston <adam.johnston@arm.com>
2022-07-27arm-bsp/sdcard-image-n1sdp: N1SDP trusted bootAdam Johnston
This commit configures N1SDP firmware for TBBR bootflow as follows: * uefi.bin replaced with with fip.bin * load address adjusted for FIP image Signed-off-by: Adam Johnston <adam.johnston@arm.com>
2022-07-27arm-bsp/scp-firmware: N1SDP trusted bootAdam Johnston
This commit configures scp-firmware for TBBR bootflow as follows: * SCP FW upgraded to 2.10 for the N1SDP only * Updates SCP FW src to master * BL31 replaced in the SCP firmware image with BL1 Signed-off-by: Adam Johnston <adam.johnston@arm.com>
2022-07-27arm-bsp/trusted-firmware-a: N1SDP trusted bootAdam Johnston
This commit configures trusted-firmware-a for TBBR bootflow on N1SDP as follows: * Trusted Firmware is upgraded to 2.7.0 for the N1SDP only * Trusted boot is enabled. * Generation of root-of-trust is enabled * All TB images (BLx, DTBs) are built * uefi.bin is specified as the BL33 image * BL2, BL31, BL33 are signed and stored in the FIP * N1SDP platform sources are patched to increase max size BL2 and reduce max size of BL1 Signed-off-by: Adam Johnston <adam.johnston@arm.com>
2022-07-27arm/oeqa: Fix regex warning in linuxboot test casePeter Hoyes
The linuxboot test case prints the following in log.do_testimage, only when executing testimage without a pycache: linuxboot.py:18: DeprecationWarning: invalid escape sequence \: self.target.expect(self.console, "login\:", timeout=10*60) Fix the warning by escaping the ':' character correctly in the pexpect regex. Issue-Id: SCM-4957 Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com> Change-Id: I8ad54c7df6b7d1d1ddeab31cf66daff1ab84e227 Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-07-18arm/lib: Improve FVPRunner shutdown logicPeter Hoyes
We have encountered intermittent hanging during FVP shutdown, so improve the termination logic by first issuing a terminate(), waiting a bit then, if necessary, issuing a kill(). Move returncode logic to after the telnet/pexpect cleanup so it actually runs. Move pexpect.EOF logic into FVPRunner.stop so that it executes before closing the pexpect handle. Issue-Id: SCM-4957 Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com> Change-Id: Iebb3c3c89367256b1e116e66ffdb6b742358bce4 Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-07-13arm/oeqa: Use linuxboot and OEFVPSerialTarget instead of noopPeter Hoyes
Create a new "linuxboot" test that uses the pexpect methods on OEFVPSerialTarget to wait for a Linux login shell. Switch to this test method for fvp-baser-aemv8r64, corstone500 and corstone1000. Issue-Id: SCM-4957 Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com> Change-Id: Idd749652ee72e244b7a3831dd2295e0bfaed3bfa Signed-off-by: Jon Mason <jon.mason@arm.com>
2022-07-13arm/oeqa: Create new OEFVPSerialTarget with pexpect interfacePeter Hoyes
Refactor OEFVPTarget into new base class, OEFVPSSHTarget. OEFVPTarget extends OEFVPSSHTarget and additionally waits for a Linux login prompt for compatibility with tests in OE-core. OEFVPSerialTarget also extends OEFVPSSHTarget. It also exposes the entire API of pexpect, with the first argument being the FVP_TEST_CONSOLE varflag key. It logs each console output to separate files inside the core-image-minimal work directory. Issue-Id: SCM-4957 Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com> Change-Id: I1b93f94471c6311da9ee71a48239640ee37de0af Signed-off-by: Jon Mason <jon.mason@arm.com>