Adrián Herrera Arcila
cb55a84894
Previously, meta-atp extended the original gem5 recipe to add the ATP Engine models; the .bbappend was complex, because it pulled from two sources, and it was not possible to make machine-based overrides, as it is a native recipe. To solve this, we use the recent EXTRAS feature to add the gem5 models from a different recipe. Signed-off-by: Adrián Herrera Arcila <adrian.herrera@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
1.1 KiB
ATP Engine integration in gem5, and the gem5-atp-arm64 machine
Users should select the gem5-atp-arm64 machine in their conf/local.conf file.
Users can build the target image of preference, for example:
bitbake core-image-minimal
The resulting gem5 native executable contains the AMBA ATP Engine. The resulting target image contains the kernel modules, UAPI and test suite.
Users should run the environment as follows:
oe-run-native atp-gem5-native start-gem5-atp.sh
This script launches a fast simulation to fast-forward Linux boot. Once Linux boot is completed, the fast simulation switches into a detailed simulation for the final usable environment. Users can connect and interact with the environment as follows:
oe-run-native gem5-m5term-native m5term <PORT>
The connection PORT is announced by the deploy script as:
system.terminal: Listening for connections on port <PORT>
This is usually port 3456.
Users can verify access to the ATP device by running the integration test suite from within the simulated environment as follows:
test_atp.out