Changelog & Release Notes

v1.0

New Features

Implementation of the Use-Cases.

Components versions used in the Reference Stack:

Component

Version

Source

Neoverse N2 Automotive Reference Design FVP (FVP_RD_N2_Automotive)

11.20.20

FVP download

Trusted Firmware-M (RSS)

a1e8602d5ec2acad923b24eb436dc0f663eea649 (based on master branch post 1.6.0)

Trusted Firmware-M repository

SCP-firmware

RD-INFRA-2022.08.18 (based on 2.10)

SCP-Firmware repository

Trusted Firmware-A

RD-INFRA-2022.08.18 (based on 2.7)

Trusted Firmware-A repository

U-Boot

2022.07

U-Boot repository

Xen

4.16

Xen repository

Linux Kernel

5.19.17

Linux repository

Zephyr

3.2.0

Zephyr repository

Third-party Yocto layers used to build the Reference Stack:

URL: https://git.yoctoproject.org/git/meta-arm
layers: meta-arm, meta-arm-toolchain
branch: langdale
revision: 025124814e8676e46d42ec5b07220283f1bdbcd0

URL: https://git.yoctoproject.org/git/poky
layers: meta, meta-poky
branch: langdale
revision: 3ec705d3203766a9a437ef7c7837f820c0800ead

URL: https://git.openembedded.org/meta-openembedded
layers: meta-filesystems, meta-networking, meta-oe, meta-python
branch: langdale
revision: c354f92778c1d4bcd3680af7e0fb0d1414de2344

URL: https://git.yoctoproject.org/git/meta-zephyr
layers: meta-zephyr-core
branch: langdale
revision: 030c1e2d8960dd09b7de239d62092e812eaceb42

URL: https://git.yoctoproject.org/git/meta-virtualization
layers: meta-virtualization
branch: langdale
revision: 8857b36ebfec3d548755755b009adc491ef320ab

Changed

Initial version.

Limitations

  • Currently, MPAM support in Xen is available for the system level cache (SLC) partitioning only.

  • In the Virtualization Reference Stack Architecture, DomU MPAM settings can only be manipulated by xl after the DomU has been created and started.

  • The FVP only provides the programmer’s view of MPAM. There is no functional behaviour change implemented.

  • SCP RAM Firmware is not covered by the RSS-oriented secure boot process. The binary of SCP RAM Firmware is preloaded in SRAM when the FVP is launched.

  • In the Virtualization Architecture, the Virtual Network connection recovery after restarting the DomU guest is not supported.

  • Build and runtime validation is only supported on x86_64 host machines.

  • In the HIPC, the iperf parameter “-l/–length” should be less than 1473 (IP and UDP overhead) in the case of Zephyr running as a UDP server since it does not support IP fragmentation.

Resolved and Known Issues

Known Issues

In the HIPC, some logs about packet buffer exhaustion or traffic sending failure can be observed because of FVP performance bottleneck. Some logs and possible causes are listed here:

  • In the zperf sample, when the packet buff pool is consumed, veth_rpmsg: Failed to allocate packet. will be printed.

  • FVP unfair scheduling results in asynchronism between the TCP sender and the TCP receiver. When the sender has sent many packets, and the receiver does not reply with any ack since it was not scheduled, it will cause the size of the TCP window to be too small to send any packet. Finally, Failed to send the packet (-11) will be logged.

  • In the zperf TCP testing case, if the application layer does not process the packet buffer in time after the connection is closed, net_tcp: context->tcp == NULL will be logged.