openclaw/tqma6-yocto-mirror
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Complete Yocto mirror with license table for TQMa6UL (2038-compliance)

Browse Source 
- 264 license table entries with exact download URLs (224/264 resolved)
- Complete sources/ directory with all BitBake recipes
- Build configuration: tqma6ul-multi-mba6ulx, spaetzle (musl)
- Full traceability for Softwarefreigabeantrag
- GCC 13.4.0, Linux 6.6.102, U-Boot 2023.04, musl 1.2.4
- License distribution: GPL-2.0 (24), MIT (23), GPL-2.0+ (18), BSD-3 (16)
This commit is contained in:
Siggi (OpenClaw Agent)
2026-03-01 20:58:18 +00:00
commit 16accb6b24
15086 changed files with 1292356 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

64
sources/poky/meta/lib/oeqa/manual/abat.patch Normal file
View File

@@ -0,0 +1,64 @@
########
diff --git a/glxgears_check.sh b/glxgears_check.sh
index 17622b8..c4d3b97 100755
--- a/glxgears_check.sh
+++ b/glxgears_check.sh
@@ -31,7 +31,7 @@ else
sleep 6
- XPID=$( ps ax | awk '{print $1, $5}' | grep glxgears | awk '{print $1}')
+ XPID=$( ps | awk '{print $1, $5}' | grep glxgears | awk '{print $1}')
if [ ! -z "$XPID" ]; then
kill -9 $XPID >/dev/null 2>&1
echo "glxgears can run, PASS!"
diff --git a/x_close.sh b/x_close.sh
index e287be1..3429f1a 100755
--- a/x_close.sh
+++ b/x_close.sh
@@ -22,7 +22,7 @@
#
function close_proc(){
echo "kill process Xorg"
-XPID=$( ps ax | awk '{print $1, $5}' | egrep "X$|Xorg$" | awk '{print $1}')
+XPID=$( ps | awk '{print $1, $6}' | egrep "X$|Xorg$" | awk '{print $1}')
if [ ! -z "$XPID" ]; then
kill $XPID
sleep 4
diff --git a/x_start.sh b/x_start.sh
index 9cf6eab..2305796 100755
--- a/x_start.sh
+++ b/x_start.sh
@@ -24,7 +24,7 @@
X_ERROR=0
#test whether X has started
-PXID=$(ps ax |awk '{print $1,$5}' |egrep "Xorg$|X$" |grep -v grep | awk '{print $1}')
+PXID=$(ps |awk '{print $1,$6}' |egrep "Xorg$|X$" |grep -v grep | awk '{print $1}')
if [ ! -z "$PXID" ]; then
echo "[WARNING] Xorg has started!"
XORG_STATUS="started"
@@ -35,9 +35,11 @@ else
#start up the x server
echo "Start up the X server for test in display $DISPLAY................"
- $XORG_DIR/bin/X >/dev/null 2>&1 &
+ #$XORG_DIR/bin/X >/dev/null 2>&1 &
+ #sleep 8
+ #xterm &
+ /etc/init.d/xserver-nodm start &
sleep 8
- xterm &
fi
XLOG_FILE=/var/log/Xorg.0.log
[ -f $XORG_DIR/var/log/Xorg.0.log ] && XLOG_FILE=$XORG_DIR/var/log/Xorg.0.log
@@ -54,7 +56,7 @@ fi
X_ERROR=1
fi
- XPID=$( ps ax | awk '{print $1, $5}' | egrep "X$|Xorg$" |grep -v grep| awk '{print $1}')
+ XPID=$( ps | awk '{print $1, $6}' | egrep "X$|Xorg$" |grep -v grep| awk '{print $1}')
if [ -z "$XPID" ]; then
echo "Start up X server FAIL!"
echo
########

626
sources/poky/meta/lib/oeqa/manual/bsp-hw.json Normal file
View File

@@ -0,0 +1,626 @@
[
{
"test": {
"@alias": "bsps-hw.bsps-hw.boot_and_install_from_USB",
"author": [
{
"email": "alexandru.c.georgescu@intel.com",
"name": "alexandru.c.georgescu@intel.com"
}
],
"execution": {
"1": {
"action": "plugin usb which contains live image burned",
"expected_results": "User can choose install system from usb stick onto harddisk from boot menu or command line option \n"
},
"2": {
"action": "configure device BIOS to firstly boot from USB if necessary",
"expected_results": "Installed system can boot up"
},
"3": {
"action": "boot the device and select option \"Install\" from boot menu",
"expected_results": ""
},
"4": {
"action": "proceed through default install process",
"expected_results": ""
},
"5": {
"action": "Remove USB, and reboot into new installed system. \nNote: If installation was successfully completed and received this message \"\"(sdx): Volume was not properly unmounted...Please run fsck.\"\" ignore it because this was allowed according to bug 9652.",
"expected_results": ""
}
},
"summary": "boot_and_install_from_USB"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.live_boot_from_USB",
"author": [
{
"email": "juan.fernandox.ramos.frayle@intel.com",
"name": "juan.fernandox.ramos.frayle@intel.com"
}
],
"execution": {
"1": {
"action": "Plugin usb which contains live image burned.",
"expected_results": "User can choose boot from live image on usb stick from boot menu or command line option"
},
"2": {
"action": "Configure device BIOS to firstly boot from USB if necessary.",
"expected_results": ""
},
"3": {
"action": "Reboot the device and boot from USB stick.",
"expected_results": "Live image can boot up with usb stick"
}
},
"summary": "live_boot_from_USB"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.switch_among_multi_applications_and_desktop",
"author": [
{
"email": "alexandru.c.georgescu@intel.com",
"name": "alexandru.c.georgescu@intel.com"
}
],
"execution": {
"1": {
"action": "launch several applications(like contacts, file manager, notes, etc)",
"expected_results": "user could switch among multi applications and desktop"
},
"2": {
"action": "launch terminal",
"expected_results": ""
},
"3": {
"action": "switch among multi applications and desktop",
"expected_results": ""
},
"4": {
"action": "close applications \nNote: The case is for sato image only. ",
"expected_results": ""
}
},
"summary": "switch_among_multi_applications_and_desktop"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.connman_offline_mode_in_connman-gnome",
"author": [
{
"email": "alexandru.c.georgescu@intel.com",
"name": "alexandru.c.georgescu@intel.com"
}
],
"execution": {
"1": {
"action": "Launch connman-properties after system booting \n\n",
"expected_results": ""
},
"2": {
"action": "choose \"offline mode\" and check the connection of all network interfaces ",
"expected_results": "All connection should be off after clicking \"offline mode\" . "
}
},
"summary": "connman_offline_mode_in_connman-gnome"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.check_CPU_utilization_after_standby",
"author": [
{
"email": "alexandru.c.georgescu@intel.com",
"name": "alexandru.c.georgescu@intel.com"
}
],
"execution": {
"1": {
"action": "Start up system",
"expected_results": ""
},
"2": {
"action": "run \"top\" command and check if there is any process eating CPU time",
"expected_results": ""
},
"3": {
"action": "make system into standby and resume it",
"expected_results": ""
},
"4": {
"action": "run \"top\" command and check if there is any difference with the data before standby",
"expected_results": "There should be no big difference before/after standby with \"top\" . "
}
},
"summary": "check_CPU_utilization_after_standby"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.Add_multiple_files_in_media_player",
"author": [
{
"email": "alexandru.c.georgescu@intel.com",
"name": "alexandru.c.georgescu@intel.com"
}
],
"execution": {
"1": {
"action": "Launch media player",
"expected_results": ""
},
"2": {
"action": "Add multiple files(5 files) in media player at same time (ogg or wav)",
"expected_results": ""
},
"3": {
"action": "Verify the sound.",
"expected_results": "Media player should be OK with this action, it reproduce files correctly."
}
},
"summary": "Add_multiple_files_in_media_player"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.video_-_libva_check_(ogg_video_play)",
"author": [
{
"email": "alexandru.c.georgescu@intel.com",
"name": "alexandru.c.georgescu@intel.com"
}
],
"execution": {
"1": {
"action": "check if libva is installed on system (or libogg)",
"expected_results": ""
},
"2": {
"action": "copy sample ogg file to system",
"expected_results": ""
},
"3": {
"action": "launch media player can play the ogg file",
"expected_results": "ogg file can be played without problem when libva is used (or libogg) "
}
},
"summary": "video_-_libva_check_(ogg_video_play)"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.media_player_-_play_video_(ogv)",
"author": [
{
"email": "alexandru.c.georgescu@intel.com",
"name": "alexandru.c.georgescu@intel.com"
}
],
"execution": {
"1": {
"action": "copy sample ogv file to system",
"expected_results": ""
},
"2": {
"action": "launch media player and make sure it can play the ogv file",
"expected_results": "ogv file can be played without problem"
}
},
"summary": "media_player_-_play_video_(ogv)"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.media_player_-_stop/play_button_(ogv)",
"author": [
{
"email": "alexandru.c.georgescu@intel.com",
"name": "alexandru.c.georgescu@intel.com"
}
],
"execution": {
"1": {
"action": "copy sample ogv file to system",
"expected_results": ""
},
"2": {
"action": "launch media player can play the ogv file",
"expected_results": ""
},
"3": {
"action": "click \"stop\" button to stop playing",
"expected_results": ""
},
"4": {
"action": "click \"start\" button to resume playing",
"expected_results": "ogv file can be start/stop without problem"
}
},
"summary": "media_player_-_stop/play_button_(ogv)"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.audio_-_play_(ogg)_with_HDMI",
"author": [
{
"email": "alexandru.c.georgescu@intel.com",
"name": "alexandru.c.georgescu@intel.com"
}
],
"execution": {
"1": {
"action": "copy sample ogg file to system",
"expected_results": ""
},
"2": {
"action": "connect system with a monitor with HDMI",
"expected_results": ""
},
"3": {
"action": "launch media player and play the ogg file",
"expected_results": "ogg file can be played without problem with HDMI"
}
},
"summary": "audio_-_play_(ogg)_with_HDMI"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.audio_-_play_(wav)_with_HDMI",
"author": [
{
"email": "alexandru.c.georgescu@intel.com",
"name": "alexandru.c.georgescu@intel.com"
}
],
"execution": {
"1": {
"action": "copy sample wav file to system",
"expected_results": ""
},
"2": {
"action": "connect system with a monitor with HDMI",
"expected_results": ""
},
"3": {
"action": "launch media player and play the wav file",
"expected_results": "wav file can be played without problem, with HDMI"
}
},
"summary": "audio_-_play_(wav)_with_HDMI"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.Graphics_-_ABAT",
"author": [
{
"email": "alexandru.c.georgescu@intel.com",
"name": "alexandru.c.georgescu@intel.com"
}
],
"execution": {
"1": {
"action": "Download ABAT test suite from internal git repository, git clone git://tinderbox.sh.intel.com/git/abat",
"expected_results": ""
},
"2": {
"action": "Apply following patch to make it work on yocto environment",
"expected_results": ""
},
"3": {
"action": "Run \"./abat.sh\" to run ABAT test refer to abat.patch",
"expected_results": "All ABAT test should pass. \nNote : If below 3 fails appears ignore them. \n- start up X server fail.. due is already up \n- module [intel_agp] \n- module [i915]"
}
},
"summary": "Graphics_-_ABAT"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.Graphics_-_x11perf_-_2D",
"author": [
{
"email": "alexandru.c.georgescu@intel.com",
"name": "alexandru.c.georgescu@intel.com"
}
],
"execution": {
"1": {
"action": "Run \"x11perf -aa10text\" and \"x11perf -rgb10text\"",
"expected_results": ""
},
"2": {
"action": "Get the FPS result and compare it with upstream graphics data on Sandybridge",
"expected_results": "There should not be big regression between Yocto and upstream linux . "
}
},
"summary": "Graphics_-_x11perf_-_2D"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.Check_if_SATA_disk_can_work_correctly",
"author": [
{
"email": "yi.zhao@windriver.com",
"name": "yi.zhao@windriver.com"
}
],
"execution": {
"1": {
"action": "Run fdisk command to create partition on SATA disk. ",
"expected_results": "The SATA device can mount, umount, read and write. "
},
"2": {
"action": "Mount/Umount \n mke2fs /dev/sda1 \n mount -t ext2 /dev/sda1 /mnt/disk \n umount /mnt/disk",
"expected_results": ""
},
"3": {
"action": "Read/Write (filesystem) \n touch /mnt/disk/test.txt \n echo abcd > /mnt/disk/test.txt \n cat /mnt/disk/test.txt",
"expected_results": ""
},
"4": {
"action": "Read/Write (raw) \n dd if=/dev/sda1 of=/tmp/test bs=1k count=1k \n This command will read 1MB from /dev/sda1 to /tmp/test",
"expected_results": ""
}
},
"summary": "Check_if_SATA_disk_can_work_correctly"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.Install_and_boot_from_USB-drive_to_HDD-drive",
"author": [
{
"email": "david.israelx.rodriguez.castellanos@intel.com",
"name": "david.israelx.rodriguez.castellanos@intel.com"
}
],
"execution": {
"1": {
"action": "Get a HDD drive.",
"expected_results": "User can choose install system from USB stick on HDD drive from boot menu or command line option \n"
},
"2": {
"action": "Plugin USB which contains live image burned (USB1).",
"expected_results": "Installed system can boot up."
},
"3": {
"action": "Configure device BIOS to firstly boot from USB if necessary",
"expected_results": ""
},
"4": {
"action": "Boot the device and select option \"Install\" from boot menu.",
"expected_results": ""
},
"5": {
"action": "Make sure that the divice in which image is going to be installed is the HDD drive.",
"expected_results": ""
},
"6": {
"action": "Proceed through default install process.",
"expected_results": ""
},
"7": {
"action": "Remove USB1, and reboot into new installed system.",
"expected_results": ""
}
},
"summary": "Install_and_boot_from_USB-drive_to_HDD-drive"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.Install_and_boot_from_USB-drive_to_SD-drive",
"author": [
{
"email": "david.israelx.rodriguez.castellanos@intel.com",
"name": "david.israelx.rodriguez.castellanos@intel.com"
}
],
"execution": {
"1": {
"action": "Get a SD-drive with enough free space to install an image.",
"expected_results": "User can choose install system from USB stick on SD-drive from boot menu or command line option. \n"
},
"2": {
"action": "Plugin USB which contains live image burned (USB1).",
"expected_results": "Installed system can boot up."
},
"3": {
"action": "Configure device BIOS to firstly boot from USB if necessary",
"expected_results": ""
},
"4": {
"action": "Boot the device and select option \"Install\" from boot menu.",
"expected_results": ""
},
"5": {
"action": "Make sure that the device in which image is going to be installed is the SD-drive.",
"expected_results": ""
},
"6": {
"action": "Proceed through default install process.",
"expected_results": ""
},
"7": {
"action": "Remove USB1, and reboot into new installed system.",
"expected_results": ""
}
},
"summary": "Install_and_boot_from_USB-drive_to_SD-drive"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.Test_boot_on_serial_communication_SD",
"author": [
{
"email": "juan.fernandox.ramos.frayle@intel.com",
"name": "juan.fernandox.ramos.frayle@intel.com"
}
],
"execution": {
"1": {
"action": "1.- Create a yocto project image in a SD card \nexample \n2 - Configure a connection like shown in the link avobe: \nhttps://wiki.yoctoproject.org/wiki/MinnowMax_board_Serial_video_connection_guide \n3 - Verify the Minow Max board is connected to the host \n4 - Boot the system to desktop \n5 - Open a Terminal and check the IP \nIn Terminal type $ifconfig\"",
"expected_results": "Verify you can create a live image \n"
}
},
"summary": "Test_boot_on_serial_communication_SD"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.Test_boot_on_serial_communication_HDD",
"author": [
{
"email": "juan.fernandox.ramos.frayle@intel.com",
"name": "juan.fernandox.ramos.frayle@intel.com"
}
],
"execution": {
"1": {
"action": "1 - Create a yocto project image in a HDD \nexample \n2 - Configure a connection like shown in the link avobe: \nhttps://wiki.yoctoproject.org/wiki/MinnowMax_board_Serial_video_connection_guide \n3 - Verify the Minow Max board is connected to the host \n4 - Boot the system to desktop \n5 - Open a Terminal and check the IP \nIn Terminal type $ifconfig\"> ",
"expected_results": "Verify you can create a live image \n"
}
},
"summary": "Test_boot_on_serial_communication_HDD"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.Test_boot_on_serial_communication_USB",
"author": [
{
"email": "juan.fernandox.ramos.frayle@intel.com",
"name": "juan.fernandox.ramos.frayle@intel.com"
}
],
"execution": {
"1": {
"action": "1.- Create a yocto project image in a USB \nexample <dd if= core-image-sato-sdk.hddimg of =/dev/sdb>",
"expected_results": "Verify you can create a live image \n"
},
"2": {
"action": "Configure a connection like shown in the link avobe: \nhttps://wiki.yoctoproject.org/wiki/MinnowMax_board_Serial_video_connection_guide\n\n",
"expected_results": "Video signal is present and not delayed \n"
},
"3": {
"action": " Verify the Minow Max board is connected to the host",
"expected_results": "Verify the system boot ok and no errors are present \n"
},
"4": {
"action": " Boot the system to desktop",
"expected_results": " Check that a valid IP is retrieved"
},
"5": {
"action": " Open a Terminal and check the IP \nIn Terminal type $ifconfig\" ",
"expected_results": ""
}
},
"summary": "Test_boot_on_serial_communication_USB"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.Test_Seek_bar_and_volume_control",
"author": [
{
"email": "juan.fernandox.ramos.frayle@intel.com",
"name": "juan.fernandox.ramos.frayle@intel.com"
}
],
"execution": {
"1": {
"action": "Run media player and load a media file ",
"expected_results": "Media player correctly open audio/video file \n"
},
"2": {
"action": "Verify that seek and volume control are present ",
"expected_results": "Seek bar and volume control are present \n"
},
"3": {
"action": "Verify that selecting the speaker icon opens the volume control",
"expected_results": "Volume control bar must appear \n"
},
"4": {
"action": "Verify you can increase and decrease volume level with the volume control",
"expected_results": "Volume level must be increased and decreased \n"
},
"5": {
"action": "Observe that slider on the seek bar moves along with the video/audio play",
"expected_results": "Video/audio file can be played and slider moves along with the video/audio play \n"
},
"6": {
"action": "Verify you can navigate the video with the slider back and forward",
"expected_results": "The slider can move back and forward in the seek bar \n"
},
"7": {
"action": "Verify that seek and volume control are functional in full screen mode",
"expected_results": "Press the full screen mode icon, seek bar and volume control must work fine \n"
},
"8": {
"action": "Verify that pressing << or >> while playing a file makes the slide goes slow/backwards or faster",
"expected_results": "Verify << and >> works correctly"
}
},
"summary": "Test_Seek_bar_and_volume_control"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.Check_if_watchdog_can_reset_the_target_system",
"author": [
{
"email": "yi.zhao@windriver.com",
"name": "yi.zhao@windriver.com"
}
],
"execution": {
"1": {
"action": "1.Check if watchdog device exist in /dev/ directory. Run command echo 1 > /dev/watchdog and wait for 60s. Then, the target will reboot.",
"expected_results": "The watchdog device exist in /dev/ directory and can reboot the target.\n"
}
},
"summary": "Check_if_watchdog_can_reset_the_target_system"
}
},
{
"test": {
"@alias": "bsps-hw.bsps-hw.System_can_boot_up_via_NFS",
"author": [
{
"email": "yi.zhao@windriver.com",
"name": "yi.zhao@windriver.com"
}
],
"execution": {
"1": {
"action": "Connect the board's first serial port to your workstation and then start up your favourite serial terminal so that you will be able to interact with the serial console. If you don't have a favourite, picocom is suggested: $ picocom /dev/ttyS0 -b 115200 ",
"expected_results": "The system can boot up without problem\n"
},
"2": {
"action": "Power up or reset the board and press a key on the terminal when prompted to get to the U-Boot command line ",
"expected_results": ""
},
"3": {
"action": "Set up the environment in U-Boot: => setenv ipaddr => setenv serverip ",
"expected_results": ""
},
"4": {
"action": "Download the kernel and boot: => tftp tftp $loadaddr vmlinux => bootoctlinux $loadaddr coremask=0x3 root=/dev/nfs rw nfsroot=: ip=::::edgerouter:eth0:off mtdparts=phys_mapped_flash:512k(boot0),512k(boot1),64k@3072k(eeprom)\n",
"expected_results": ""
}
},
"summary": "System_can_boot_up_via_NFS"
}
}
]

96
sources/poky/meta/lib/oeqa/manual/build-appliance.json Normal file
View File

@@ -0,0 +1,96 @@
[
{
"test": {
"@alias": "build-appliance.build-appliance.Build_core-image-minimal_with_build-appliance-image",
"author": [
{
"email": "corneliux.stoicescu@intel.com",
"name": "corneliux.stoicescu@intel.com"
}
],
"execution": {
"1": {
"action": "Build with AUTOREV or download from Autobuilder an image for Yocto Build Appliance. ",
"expected_results": ""
},
"2": {
"action": "Boot the image under VMWare Player. ",
"expected_results": ""
},
"3": {
"action": "Build qemux86 core-image-minimal using bitbake command line in the build-appliance-image ",
"expected_results": ""
},
"4": {
"action": "Launch the image just built using runqemu. ",
"expected_results": "core-image-minimal should build and boot. "
}
},
"summary": "Build_core-image-minimal_with_build-appliance-image"
}
},
{
"test": {
"@alias": "build-appliance.build-appliance.Build_a_image_without_error_(added_recipe)",
"author": [
{
"email": "sstncr@gmail.com",
"name": "sstncr@gmail.com"
}
],
"execution": {
"1": {
"action": "Launch Build Appliance",
"expected_results": "User could build a image without error and the added package is in the image"
},
"2": {
"action": "Set \"Machine\" in conf/local.conf, for example, qemuarm",
"expected_results": ""
},
"3": {
"action": "Install a new package to the image, for example, acpid. Set the following line in conf/local.conf: IMAGE_INSTALL:append = \" acpid\"",
"expected_results": ""
},
"4": {
"action": "Build a image using bitbake command line, for example, bitbake core-image-minimal",
"expected_results": ""
},
"5": {
"action": "After build finished, launch the image and check if the added package built into image",
"expected_results": ""
}
},
"summary": "Build_a_image_without_error_(added_recipe)."
}
},
{
"test": {
"@alias": "build-appliance.build-appliance.Create_core-image-sato-sdk_using_build_appliance",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Build with AUTOREV or download from Autobuilder an image for Yocto Build Appliance. ",
"expected_results": ""
},
"2": {
"action": "Boot the image under VMWare Player. ",
"expected_results": ""
},
"3": {
"action": "Build qemux86 core-image-sato-sdk using bitbake command line in the build-appliance-image ",
"expected_results": ""
},
"4": {
"action": "Launch the image just built using runqemu. ",
"expected_results": ""
}
},
"summary": "Create_core-image-sato-sdk_using_build_appliance"
}
}
]

294
sources/poky/meta/lib/oeqa/manual/crops.json Normal file
View File

@@ -0,0 +1,294 @@
[
{
"test": {
"@alias": "crops-default.crops-default.sdkext_eSDK_devtool_build_make",
"author": [
{
"email": "francisco.j.pedraza.gonzalez@intel.com",
"name": "francisco.j.pedraza.gonzalez@intel.com"
}
],
"execution": {
"1": {
"action": "IMPORTANT NOTE: The firsts 5 steps refer to configuration of the environment to run the rest of the steps. These only apply for CROPS-eSDK. \n\n\n\n",
"expected_results": ""
},
"2": {
"action": " Initiate your Crops-esdk environment as it says in wiki https://github.com/crops/docker-win-mac-docs/wiki \n\n",
"expected_results": ""
},
"3": {
"action": "Create the following tree of files <crops-esdk-workdir-workspace>/sdkext/files/myapp <crops-esdk-workdir-workspace>/sdkext/files/myapp_cmake \n\n\n",
"expected_results": ""
},
"4": {
"action": " Create the following files withing the myapp directory myapp.c and the Makefile. Write the following inside of each file: \n---------------------------------------- \nMakefile should contain \n\nall: myapp \n\nmyapp: myapp.o \n\t$(CC) $(LDFLAGS) $< -o $@ \n\nmyapp.o: myapp.c \n\t$(CC) $(CFLAGS) -c $< -o $@ \n\nclean: \n\trm -rf myapp.o myapp \n\n----------------------------- \nmyapp.c shold contain \n\n\n#include <stdio.h> \n\nint \nmain(int argc, char *argv[]) \n{ \n\tprintf(\"Hello world\\n\"); \n \n\treturn 0; \n} \n------------------------------------ \n\n",
"expected_results": "be sure that the indentations on the makefile are tabs not spaces. \n\n"
},
"5": {
"action": " Create the following files within the myapp_cmake directory CMakeLists.txt and myapp.c. Write the following inside each file: \n\n------------------------------------ \nCMakeLists.txt should contain: \n\ncmake_minimum_required (VERSION 2.6) \nproject (myapp) \n# The version number. \nset (myapp_VERSION_MAJOR 1) \nset (myapp_VERSION_MINOR 0) \n\n# add the executable \nadd_executable (myapp myapp.c) \n\ninstall(TARGETS myapp \nRUNTIME DESTINATION bin) \n\n------------------------------------------ \nmyapp.c should contain: \n\n#include <stdio.h> \n\nint \nmain(int argc, char *argv[]) \n{ \n\tprintf(\"Hello world\\n\"); \n\n\treturn 0; \n} \n------------------------------------------------- \n\n",
"expected_results": "Be sure that the indentations on CMakeLists.txt is tabs not spaces."
},
"6": {
"action": " source environment-setup-i586-poky-linux \n\n",
"expected_results": "This should output a message that says SDK environment now set up; additionally you may now run devtool to perform development tasks etc etc ... \n\n"
},
"7": {
"action": " run command which devtool \n\n",
"expected_results": "this should output the directory of the devtool script and it should be within the sdk workdir you are working in. \n\n "
},
"8": {
"action": "devtool add myapp <directory>(this is myapp dir) \n\n\n",
"expected_results": "The directory you should input is the myapp directory. This should automatically create the recipe myapp.bb under <crops-esdk-workdir-workspace>/recipes/myapp/myapp.bb"
},
"9": {
"action": " devtool build myapp \n\n",
"expected_results": "This should compile an image"
},
"10": {
"action": " devtool reset myapp ",
"expected_results": "This cleans sysroot of the myapp recipe, but it leaves the source tree intact. meaning it does not erase."
}
},
"summary": "sdkext_eSDK_devtool_build_make"
}
},
{
"test": {
"@alias": "crops-default.crops-default.sdkext_devtool_build_esdk_package",
"author": [
{
"email": "francisco.j.pedraza.gonzalez@intel.com",
"name": "francisco.j.pedraza.gonzalez@intel.com"
}
],
"execution": {
"1": {
"action": "IMPORTANT NOTE: The firsts 5 steps refer to configuration of the environment to run the rest of the steps. These only apply for CROPS-eSDK. \n\n\n\n",
"expected_results": ""
},
"2": {
"action": " Initiate your Crops-esdk environment as it says in wiki https://github.com/crops/docker-win-mac-docs/wiki \n\n",
"expected_results": ""
},
"3": {
"action": " Create the following tree of files <crops-esdk-workdir-workspace>/sdkext/files/myapp/ \n <crops-esdk-workdir-workspace>/sdkext/files/myapp_cmake \n\n",
"expected_results": ""
},
"4": {
"action": " Create the following files withing the myapp directory myapp.c and the Makefile. Write the following inside of each file: \n---------------------------------------- \nMakefile should contain \n\nall: myapp \n\nmyapp: myapp.o \n\t$(CC) $(LDFLAGS) $< -o $@ \n\nmyapp.o: myapp.c \n\t$(CC) $(CFLAGS) -c $< -o $@ \n\nclean: \n\trm -rf myapp.o myapp \n\n----------------------------- \nmyapp.c shold contain \n\n#include <stdio.h> \n\nint \nmain(int argc, char *argv[]) \n{ \n\tprintf(\"Hello world\\n\"); \n \n\treturn 0; \n} \n------------------------------------ \n\n",
"expected_results": "be sure that the indentations on the makefile are tabs not spaces. \n\n"
},
"5": {
"action": " Create the following files within the myapp_cmake directory CMakeLists.txt and myapp.c. Write the following inside each file: \n\n------------------------------------ \nCMakeLists.txt should contain: \n\ncmake_minimum_required (VERSION 2.6) \nproject (myapp) \n# The version number. \nset (myapp_VERSION_MAJOR 1) \nset (myapp_VERSION_MINOR 0) \n\n# add the executable \nadd_executable (myapp myapp.c) \n\ninstall(TARGETS myapp \nRUNTIME DESTINATION bin) \n\n------------------------------------------ \nmyapp.c should contain: \n\n#include<stdio.h> \n\nint \nmain(int argc, char *argv[]) \n{ \n\tprintf(\"Hello world\\n\"); \n\n\treturn 0; \n} \n------------------------------------------------- \n\n",
"expected_results": "Be sure that the indentations on CMakeLists.txt is tabs not spaces. \n\n"
},
"6": {
"action": " source environment-setup-i586-poky-linux \n\n",
"expected_results": "This should output a message that says SDK environment now set up; additionally you may now run devtool to perform development tasks etc etc ... \n\n"
},
"7": {
"action": " run command which devtool \n\n",
"expected_results": " this should output the directory of the devtool script and it should be within the sdk workdir you are working in. \n\n"
},
"8": {
"action": " devtool add myapp <directory> (this is myapp dir) \n\n",
"expected_results": " The directory you should input is the myapp directory. This should automatically create the recipe myapp.bb under <crops-esdk-workdir-workspace>/recipes/myapp/myapp.bb \n\n"
},
"9": {
"action": " devtool package myapp \n\n",
"expected_results": " you should expect a package creation of myapp and it should be under the /tmp/deploy/ \n\n"
},
"10": {
"action": " devtool reset myapp ",
"expected_results": "This cleans sysroot of the myapp recipe, but it leaves the source tree intact. meaning it does not erase.\n</package_format>"
}
},
"summary": "sdkext_devtool_build_esdk_package"
}
},
{
"test": {
"@alias": "crops-default.crops-default.sdkext_devtool_build_cmake",
"author": [
{
"email": "francisco.j.pedraza.gonzalez@intel.com",
"name": "francisco.j.pedraza.gonzalez@intel.com"
}
],
"execution": {
"1": {
"action": "IMPORTANT NOTE: The firsts 5 steps refer to configuration of the environment to run the rest of the steps. These only apply for CROPS-eSDK. \n\n\n\n",
"expected_results": ""
},
"2": {
"action": " Initiate your Crops-esdk environment as it says in wiki https://github.com/crops/docker-win-mac-docs/wiki \n\n",
"expected_results": ""
},
"3": {
"action": " Create the following tree of files <crops-esdk-workdir-workspace>/sdkext/files/myapp \n <crops-esdk-workdir-workspace>/sdkext/files/myapp_cmake \n\n",
"expected_results": ""
},
"4": {
"action": " Create the following files withing the myapp directory myapp.c and the Makefile. Write the following inside of each file: \n---------------------------------------- \nMakefile should contain \n\nall: myapp \n\nmyapp: myapp.o \n\t$(CC) $(LDFLAGS) $< -o $@ \n\nmyapp.o: myapp.c \n\t$(CC) $(CFLAGS) -c $< -o $@ \n\nclean: \n\trm -rf myapp.o myapp \n\n----------------------------- \nmyapp.c shold contain \n\n#include <stdio.h> \n\nint \nmain(int argc, char *argv[]) \n{ \n\tprintf(\"Hello world\\n\"); \n \n\treturn 0; \n} \n------------------------------------ \n\n",
"expected_results": "be sure that the indentations on the makefile are tabs not spaces. \n\n"
},
"5": {
"action": " Create the following files within the myapp_cmake directory CMakeLists.txt and myapp.c. Write the following inside each file: \n\n------------------------------------ \nCMakeLists.txt should contain: \n\ncmake_minimum_required (VERSION 2.6) \nproject (myapp) \n# The version number. \nset (myapp_VERSION_MAJOR 1) \nset (myapp_VERSION_MINOR 0) \n\n# add the executable \nadd_executable (myapp myapp.c) \n\ninstall(TARGETS myapp \nRUNTIME DESTINATION bin) \n\n------------------------------------------ \nmyapp.c should contain: \n\n#include \n\nint \nmain(int argc, char *argv[]) \n{ \n\tprintf(\"Hello world\\n\"); \n\n\treturn 0; \n} \n------------------------------------------------- \n\n",
"expected_results": "Be sure that the indentations on CMakeLists.txt is tabs not spaces. \n\n"
},
"6": {
"action": " source environment-setup-i586-poky-linux \n\n",
"expected_results": "This should output a message that says SDK environment now set up; additionally you may now run devtool to perform development tasks etc etc ... \n\n"
},
"7": {
"action": " run command which devtool \n\n",
"expected_results": "this should output the directory of the devtool script and it should be within the sdk workdir you are working in. \n\n"
},
"8": {
"action": " devtool add myapp <directory> (this is myapp_cmake dir) \n\n",
"expected_results": "The directory you should input is the myapp_cmake directory. This should automatically create the recipe myapp.bb under <crops-esdk-workdir-workspace>/recipes/myapp/myapp.bb \n\n"
},
"9": {
"action": " devtool build myapp \n\n",
"expected_results": "This should compile an image \n\n"
},
"10": {
"action": " devtool reset myapp ",
"expected_results": "This cleans sysroot of the myapp recipe, but it leaves the source tree intact. meaning it does not erase. "
}
},
"summary": "sdkext_devtool_build_cmake"
}
},
{
"test": {
"@alias": "crops-default.crops-default.sdkext_extend_autotools_recipe_creation",
"author": [
{
"email": "francisco.j.pedraza.gonzalez@intel.com",
"name": "francisco.j.pedraza.gonzalez@intel.com"
}
],
"execution": {
"1": {
"action": "IMPORTANT NOTE: The firsts 2 steps refer to configuration of the environment to run the rest of the steps. These only apply for CROPS-eSDK. \n\n\n\n",
"expected_results": ""
},
"2": {
"action": "Initiate your Crops-esdk environment as it says in wiki https://github.com/crops/docker-win-mac-docs/wiki \n\n",
"expected_results": ""
},
"3": {
"action": " source environment-setup-i586-poky-linux \n\n",
"expected_results": " This should output a message that says SDK environment now set up; additionally you may now run devtool to perform development tasks etc etc ... \n\n"
},
"4": {
"action": "run command which devtool \n\n",
"expected_results": "this should output the directory of the devtool script and it should be within the sdk workdir you are working in. \n\n"
},
"5": {
"action": "devtool sdk-install -s libxml2 \n\n",
"expected_results": "this should install libxml2 \n\n"
},
"6": {
"action": "devtool add librdfa https://github.com/rdfa/librdfa \n\n",
"expected_results": "This should automatically create the recipe librdfa.bb under /recipes/librdfa/librdfa.bb \n\n"
},
"7": {
"action": "devtool build librdfa \n\n",
"expected_results": "This should compile \n\n"
},
"8": {
"action": "devtool reset librdfa ",
"expected_results": "This cleans sysroot of the librdfa recipe, but it leaves the source tree intact. meaning it does not erase."
}
},
"summary": "sdkext_extend_autotools_recipe_creation"
}
},
{
"test": {
"@alias": "crops-default.crops-default.sdkext_devtool_kernelmodule",
"author": [
{
"email": "francisco.j.pedraza.gonzalez@intel.com",
"name": "francisco.j.pedraza.gonzalez@intel.com"
}
],
"execution": {
"1": {
"action": "IMPORTANT NOTE: The firsts 2 steps refer to configuration of the environment to run the rest of the steps. These only apply for CROPS-eSDK. \n\n\n",
"expected_results": ""
},
"2": {
"action": " Initiate your Crops-esdk environment as it says in wiki https://github.com/crops/docker-win-mac-docs/wiki \n\n",
"expected_results": ""
},
"3": {
"action": "source environment-setup-i586-poky-linux \n\n",
"expected_results": "This should output a message that says SDK environment now set up; additionally you may now run devtool to perform development tasks etc etc ... \n \n"
},
"4": {
"action": "run command which devtool \n\n",
"expected_results": "this should output the directory of the devtool script and it should be within the sdk workdir you are working in. \n\n"
},
"5": {
"action": "devtool add kernel-module-hello-world https://git.yoctoproject.org/git/kernel-module-hello-world \n\n",
"expected_results": "This should automatically create the recipe kernel-module-hello-world.bb under <crops-esdk-workdir-workspace>/recipes/kernel-module-hello-world/kernel-module-hello-world.bb "
},
"6": {
"action": "devtool build kernel-module-hello-world \n\n",
"expected_results": "This should compile an image \n\n"
},
"7": {
"action": "devtool reset kernel-module-hello-world ",
"expected_results": "This cleans sysroot of the kernel-module-hello-world recipe, but it leaves the source tree intact. meaning it does not erase."
}
},
"summary": "sdkext_devtool_kernelmodule"
}
},
{
"test": {
"@alias": "crops-default.crops-default.sdkext_recipes_for_nodejs",
"author": [
{
"email": "francisco.j.pedraza.gonzalez@intel.com",
"name": "francisco.j.pedraza.gonzalez@intel.com"
}
],
"execution": {
"1": {
"action": "IMPORTANT NOTE: The firsts 2 steps refer to configuration of the environment to run the rest of the steps. These only apply for CROPS-eSDK. \n\n\nlets say variable npm = npm://registry.npmjs.org;name=winston;version=2.2.0 \n\n",
"expected_results": ""
},
"2": {
"action": "Initiate your Crops-esdk environment as it says in wiki https://github.com/crops/docker-win-mac-docs/wiki \n\n",
"expected_results": ""
},
"3": {
"action": "source environment-setup-i586-poky-linux \n\n",
"expected_results": "This should output a message that says SDK environment now set up; additionally you may now run devtool to perform development tasks etc etc ... \n\n"
},
"4": {
"action": "run command which devtool \n\n",
"expected_results": "this should output the directory of the devtool script and it should be within the sdk workdir you are working in. \n\n"
},
"5": {
"action": " 4a) git clone git://git.openembedded.org/meta-openembedded in layers/build directory \n \n4b) Add meta-openembedded/meta-oe in bblayer.conf as mentioned below: ${SDKBASEMETAPATH}/layers/build/meta-openembedded/meta-oe \\ \n\n4c) devtool add \"npm://registry.npmjs.org;name=npm;version=2.2.0\" \n\n",
"expected_results": " This should automatically create the recipe npm.bb under /recipes/npm/npm.bb \n\n"
},
"6": {
"action": "devtool build npm \n\n",
"expected_results": "This should compile an image \n\n"
},
"7": {
"action": " devtool reset npm",
"expected_results": "This cleans sysroot of the npm recipe, but it leaves the source tree intact. meaning it does not erase."
}
},
"summary": "sdkext_recipes_for_nodejs"
}
}
]

322
sources/poky/meta/lib/oeqa/manual/eclipse-plugin.json Normal file
View File

@@ -0,0 +1,322 @@
[
{
"test": {
"@alias": "eclipse-plugin.eclipse-plugin.support_SSH_connection_to_Target",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "In Eclipse, swich to Remote System Explorer to create a connention baseed on SSH, input the remote target IP address as the Host name, make sure disable the proxy in Window->Preferences->General->Network Connection, set Direct as Active Provider field. ",
"expected_results": "the connection based on SSH could be set up."
},
"2": {
"action": "Configure connection from Eclipse: Run->Run Configurations->C/C++ Remote Application\\ ->New Connection->General->SSH Only ",
"expected_results": ""
},
"3": {
"action": "Then right click to connect, input the user ID and password. ",
"expected_results": ""
},
"4": {
"action": "expand the connection, it will show the Sftp Files etc. \nNOTE. Might need to change dropbear to openssh and add the packagegroup-core-eclipse-debug recipe",
"expected_results": ""
}
},
"summary": "support_SSH_connection_to_Target"
}
},
{
"test": {
"@alias": "eclipse-plugin.eclipse-plugin.Launch_QEMU_from_Eclipse",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Set the Yocto ADT's toolchain root location, sysroot location and kernel, in the menu Window -> Preferences -> Yocto ADT. \n \n",
"expected_results": ""
},
"2": {
"action": "wget https://downloads.yoctoproject.org/releases/yocto/yocto-$VERSION/machines/qemu/qemux86/ (ex:core-image-sato-sdk-qemux86-date-rootfs-tar-bz2) \nsource /opt/poky/version/environment-setup-i585-poky-linux \n\nExtract qemu with runqemu-extract-sdk /home/user/file(ex.core-image-sato-sdk-qemux86.bz2) \n/home/user/qemux86-sato-sdk \n\n",
"expected_results": " Qemu can be lauched normally."
},
"3": {
"action": "(a)Point to the Toolchain: \n \nIf you are using a stand-alone pre-built toolchain, you should be pointing to the /opt/poky/{test-version} directory as Toolchain Root Location. This is the default location for toolchains installed by the ADT Installer or by hand. If ADT is installed in other location, use that location as Toolchain location.\nIf you are using a system-derived toolchain, the path you provide for the Toolchain Root Location field is the Yocto Project's build directory. \n \n E.g:/home/user/yocto/poky/build \n",
"expected_results": ""
},
"4": {
"action": "(b)Specify the Sysroot Location: \nSysroot Location is the location where the root filesystem for the target hardware is created on the development system by the ADT Installer (SYSROOT in step 2 of the case ADT installer Installation). \n \n Local : e.g: /home/user/qemux86-sato-sdk \nUsing ADT : e.g :/home/user/test-yocto/qemux86 \n\n",
"expected_results": ""
},
"5": {
"action": "(c)Select the Target Architecture: \n \nThe target architecture is the type of hardware you are going to use or emulate. Use the pull-down Target Architecture menu to make your selection. \n \n\n",
"expected_results": ""
},
"6": {
"action": "(d) QEMU: \nSelect this option if you will be using the QEMU emulator. Specify the Kernel matching the QEMU architecture you are using. \n wget https://downloads.yoctoproject.org/releases/yocto/yocto-$VERSION/machines/qemu/qemux86/bzImage-qemux86.bin \n e.g: /home/$USER/yocto/adt-installer/download_image/bzImage-qemux86.bin \n\n",
"expected_results": ""
},
"7": {
"action": "(e) select OK to save the settings. \n\n\n1: In the Eclipse toolbar, expose the Run -> External Tools menu. Your image should appear as a selectable menu item. \n2: Select your image in the navigation pane to launch the emulator in a new window. \n3: If needed, enter your host root password in the shell window at the prompt. This sets up a Tap 0 connection needed for running in user-space NFS mode. \n",
"expected_results": ""
}
},
"summary": "Launch_QEMU_from_Eclipse"
}
},
{
"test": {
"@alias": "eclipse-plugin.eclipse-plugin.Relocatable_SDK_-_C_-_Build_Hello_World_ANSI_C_Autotools_Project",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Launch a QEMU of target environment.(Reference to case \"ADT - Launch qemu by eclipse\") ",
"expected_results": ""
},
"2": {
"action": "Select File -> New -> Project.",
"expected_results": ""
},
"3": {
"action": "Double click C/C++.",
"expected_results": ""
},
"4": {
"action": "Click C or C++ Project to create the project.",
"expected_results": ""
},
"5": {
"action": "Expand Yocto ADT Project.",
"expected_results": ""
},
"6": {
"action": "Select Hello World ANSI C Autotools Project.",
"expected_results": ""
},
"7": {
"action": "Put a name in the Project name. Do not use hyphens as part of the name. \n \n",
"expected_results": ""
},
"8": {
"action": "Click Next.",
"expected_results": ""
},
"9": {
"action": "Add information in the Author and Copyright notice fields. \n1",
"expected_results": ""
},
"10": {
"action": "Click Finish. \n1",
"expected_results": ""
},
"11": {
"action": "If the \"open perspective\" prompt appears, click \"Yes\" so that you open the C/C++ perspective. \n1",
"expected_results": ""
},
"12": {
"action": "In the Project Explorer window, right click the project -> Reconfigure project. \n1",
"expected_results": ""
},
"13": {
"action": "In the Project Explorer window, right click the project -> Build project. \n1",
"expected_results": "Under the Project files, a new folder appears called Binaries. This indicates that the compilation have been successful and the project binary have been created. \n"
},
"14": {
"action": "Right click it again and Run as -> Run Configurations. \n\t\t\tUnder Run Configurations expand \"C/C++ Remote Application\". A configuration for the current project should appear. Clicking it will display the configuration settings. \n\t\t\tin \"C/C++ Application\" field input Remote Absolute File path for C/C++ Application. e.g.: /home/root/myapplication \n\t\t\tIn \"Connection\" drop-down list make sure a TCF connection is set up for your target. If not, create a new one by clicking the New button. \n1",
"expected_results": "step 14 to step 16 -> Build succeed and the console outputs Hello world, you can also check the output on target."
},
"15": {
"action": "After all settings are done, select the Run button on the bottom right corner \n\n1",
"expected_results": ""
},
"16": {
"action": "Repeat the steps 14-15, but instead of using Run Configurations use Debug Configurations: \nRight click it again and Debug as -> Debug Configurations \nUnder Debug Configurations expand \"C/C++ Remote Application\". A configuration for the current project should appear. Clicking it will display the configuration settings. \nin \"C/C++ Application\" field input Remote Absolute File path for C/C++ Application.\ne.g.: /home/root/myapplication \nIn \"Connection\" drop-down list make sure a TCF connection is set up for your target. If not, create a new one by clicking the New button \n1",
"expected_results": ""
},
"17": {
"action": "After all settings are done, select the Debug button on the bottom right corner",
"expected_results": ""
}
},
"summary": "Relocatable_SDK_-_C_-_Build_Hello_World_ANSI_C_Autotools_Project"
}
},
{
"test": {
"@alias": "eclipse-plugin.eclipse-plugin.Relocatable_SDK_-_C++_-_Build_Hello_World_C++_Autotools_project",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Launch a QEMU of target environment.(Reference to case \"ADT - Launch qemu by eclipse\") ",
"expected_results": ""
},
"2": {
"action": "Select File -> New -> Project. ",
"expected_results": ""
},
"3": {
"action": "Double click C/C++. ",
"expected_results": ""
},
"4": {
"action": "Click C or C++ Project to create the project. ",
"expected_results": ""
},
"5": {
"action": "Expand Yocto ADT Project. ",
"expected_results": ""
},
"6": {
"action": "Select Hello World ANSI C++ Autotools Project. ",
"expected_results": ""
},
"7": {
"action": "Put a name in the Project name. Do not use hyphens as part of the name. \n \n",
"expected_results": ""
},
"8": {
"action": "Click Next.",
"expected_results": ""
},
"9": {
"action": "Add information in the Author and Copyright notice fields.",
"expected_results": ""
},
"10": {
"action": "Click Finish. \n1",
"expected_results": ""
},
"11": {
"action": "If the \"open perspective\" prompt appears, click \"Yes\" so that you open the C/C++ perspective. \n1",
"expected_results": ""
},
"12": {
"action": "In the Project Explorer window, right click the project -> Reconfigure project. \n1",
"expected_results": ""
},
"13": {
"action": "In the Project Explorer window, right click the project -> Build project. \n\n1",
"expected_results": "under the Project files, a new folder appears called Binaries. This indicates that the compilation have been successful and the project binary have been created. \n"
},
"14": {
"action": "Right click it again and Run as -> Run Configurations. \n\t\t\tUnder Run Configurations expand \"C/C++ Remote Application\". A configuration for the current project should appear. Clicking it will display the configuration settings. \n\t\t\tin \"C/C++ Application\" field input Remote Absolute File path for C/C++ Application. e.g.: /home/root/myapplication \n\t\t\tIn \"Connection\" drop-down list make sure a TCF connection is set up for your target. If not, create a new one by clicking the New button. \n1",
"expected_results": "step 14 to step 16 -> Build succeed and the console outputs Hello world, you can also check the output on target."
},
"15": {
"action": "After all settings are done, select the Run button on the bottom right corner \n\n1",
"expected_results": ""
},
"16": {
"action": "Repeat the steps 14-15, but instead of using Run Configurations use Debug Configurations: \n\t\tRight click it again and Debug as -> Debug Configurations \n\t\tUnder Debug Configurations expand \"C/C++ Remote Application\". A configuration for the current project should appear. Clicking it will display the configuration settings. \n\t\tin \"C/C++ Application\" field input Remote Absolute File path for C/C++ Application. \n\t\te.g.: /home/root/myapplication \n\t\tIn \"Connection\" drop-down list make sure a TCF connection is set up for your target. If not, create a new one by clicking the New button \n1",
"expected_results": ""
},
"17": {
"action": "After all settings are done, select the Debug button on the bottom right corner",
"expected_results": ""
}
},
"summary": "Relocatable_SDK_-_C++_-_Build_Hello_World_C++_Autotools_project"
}
},
{
"test": {
"@alias": "eclipse-plugin.eclipse-plugin.Build_Eclipse_Plugin_from_source",
"author": [
{
"email": "laurentiu.serban@intel.com",
"name": "laurentiu.serban@intel.com"
}
],
"execution": {
"1": {
"action": "Clone eclipse-poky source. \n \n - git clone git://git.yoctoproject.org/eclipse-poky \n\n",
"expected_results": "Eclipse plugin is successfully installed \n\nDocumentation is there. For example if you have release yocto-2.0.1 you will found on https://downloads.yoctoproject.org/releases/yocto/yocto-2.0.1/eclipse-plugin/mars/ archive with documentation like org.yocto.doc-development-$date.zip \n \n"
},
"2": {
"action": "Checkout correct tag. \n\n - git checkout <eclipse-version>/<yocto-version> \n\n",
"expected_results": "After plugin is build you must have 4 archive in foder scripts from eclipse-poky: \n - org.yocto.bc - mars-master-$date.zip \n - org.yocto.doc - mars-master-$date.zip --> documentation \n - org.yocto.sdk - mars-master-$date.zip \n - org.yocto.sdk - mars-master-$date.-archive.zip --> plugin "
},
"3": {
"action": "Move to scripts/ folder. \n\n",
"expected_results": ""
},
"4": {
"action": "Run ./setup.sh \n\n",
"expected_results": ""
},
"5": {
"action": "When the script finishes, it prompts a command to issue to build the plugin. It should look similar to the following: \n\n$ ECLIPSE_HOME=/eclipse-poky/scripts/eclipse ./build.sh /&1 | tee -a build.log \n\nHere, the three arguments to the build script are tag name, branch for documentation and release name. \n\n",
"expected_results": ""
},
"6": {
"action": "On an eclipse without the Yocto Plugin, select \"Install New Software\" from Help pull-down menu \n\n",
"expected_results": ""
},
"7": {
"action": "Select Add and from the dialog choose Archive... Look for the *archive.zip file that was built previously with the build.sh script. Click OK. \n\n",
"expected_results": ""
},
"8": {
"action": "Select all components and proceed with Installation of plugin. Restarting eclipse might be required.\n",
"expected_results": ""
}
},
"summary": "Build_Eclipse_Plugin_from_source"
}
},
{
"test": {
"@alias": "eclipse-plugin.eclipse-plugin.Eclipse_Poky_installation_and_setup",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Install SDK \n\ta)Download https://autobuilder.yocto.io/pub/releases//toolchain/x86_64/poky-glibc-x86_64-core-\timage-sato-i586-toolchain-.sh \n\tb)Run the SDK installer and accept the default installation directory ",
"expected_results": ""
},
"2": {
"action": "Install \"Eclipse IDE for C/C++ Developers\" Oxygen release (4.7.0) \n\ta) Go to https://www.eclipse.org/downloads/packages/all, click \"Oxygen R\" \n\tb) Click to download the build for your OS \n\tc) Click \"Download\" button to download from a mirror \n\td) Run \"tar xf\" to extract the downloaded archive ",
"expected_result": ""
},
"3": {
"action": "Install \"Eclipse IDE for C/C++ Developers\" Oxygen release (4.7.0) (Continue) \n\te) Run \"eclipse/eclipse\" to start Eclipse \n\tf) Optional step for host machine within Intel network: In Eclipse workbench window, go to \"Window\" menu -> \"Preferences...\". \n\tg) In \"Preferences\" dialog, go to \"General\" -> \"Network Connections\", set \"Active Provider\" to \"Manual\". In \"Proxy \tentries\" table, select HTTP and click \"Edit\" and enter host \"proxy-chain.intel.com\" port 911, click OK. Repeat for HTTPS with port 912 \nClick OK to close \"Preferences\" dialog. \n\th) Go to \"File\" menu -> \"Restart\" to restart Eclipse for proxy settings to take effect. ",
"expected_result": ""
},
"4": {
"action": "Install Eclipse Poky plugins \n\ta) Download https://autobuilder.yocto.io/pub/releases/<yocto-version>/eclipse-plugin/<eclipse-version>/org.yocto.sdk-development-<date>-archive.zip \n\tb) In Eclipse workbench window, go to \"Help\" menu -> \"Install New Software...\" \n\tc) In \"Install\" dialog, click \"Add...\" button \n\td) In \"Add Repository\" dialog, enter \"Eclipse Poky\" for (repository) Name, click \"Archive...\" ",
"expected_results": ""
},
"5": {
"action": "Install Eclipse Poky plugins (continue) \n\te) In \"Repository archive\" browse dialog, select the downloaded Eclipse Poky repository archive \n\tf) Back in \"Add Repository\" dialog, click \"OK\" \n\tg) Back in \"Install\" dialog, make sure \"Work with:\" is set to \"Eclipse Poky\" repository, tick \"Yocto Project \tDocumentation Plug-in\" and \"Yocto Project SDK Plug-in\", click \"Next >\" and verify plugins/features name/version, \tclick \"Next >\" and accept license agreement, click \"Finish\" \n\th) If \"Security Warning\" dialog appears, click \"OK\" to install unsigned content. \n\ti) In \"Software Updates\" dialog, click \"Yes\" to restart Eclipse to complete Eclipse Poky plugins installation. ",
"expected_results": ""
},
"6": {
"action": "Setup Eclipse Poky to use SDK \n\ta) In Eclipse workbench window, go to \"Window\" menu -> \"Preferences\". \n\tb) In \"Preferences\" window, go to \"Yocto Project SDK\", in \"Cross Compiler Options\" frame, select \"Standalone pre-\tbuilt toolchain\". ",
"expected_results": "Eclipse Poky plugins installed and running successfully, e.g. observe that \"Yocto Project Tools\" menu is available on Eclipse workbench window."
}
},
"summary": "Eclipse_Poky_installation_and_setup"
}
}
]

200
sources/poky/meta/lib/oeqa/manual/kernel-dev.json Normal file
View File

@@ -0,0 +1,200 @@
[
{
"test": {
"@alias": "kernel-dev.kernel-dev.Kernel_dev_defconfig",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_7 ",
"expected_results": ""
},
"2": {
"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps_7",
"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_7"
}
},
"summary": "Kernel_dev_defconfig"
}
},
{
"test": {
"@alias": "kernel-dev.kernel-dev.Kernel_dev_defconfig+fragments",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_8 ",
"expected_results": ""
},
"2": {
"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps_8",
"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_8"
}
},
"summary": "Kernel_dev_defconfig+fragments"
}
},
{
"test": {
"@alias": "kernel-dev.kernel-dev.Kernel_dev_Applying_patches",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites ",
"expected_results": ""
},
"2": {
"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps",
"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results"
}
},
"summary": "Kernel_dev_Applying_patches"
}
},
{
"test": {
"@alias": "kernel-dev.kernel-dev.Kernel_dev_linux-yocto-local-source",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_2 ",
"expected_results": ""
},
"2": {
"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps_2",
"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_2"
}
},
"summary": "Kernel_dev_linux-yocto-local-source"
}
},
{
"test": {
"@alias": "kernel-dev.kernel-dev.Kernel_dev_linux-yocto-custom-local-source",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_3 ",
"expected_results": ""
},
"2": {
"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps_3",
"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_3"
}
},
"summary": "Kernel_dev_linux-yocto-custom-local-source"
}
},
{
"test": {
"@alias": "kernel-dev.kernel-dev.Kernel_dev_recipe-space_meta",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_5 ",
"expected_results": ""
},
"2": {
"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps_5",
"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_5"
}
},
"summary": "Kernel_dev_recipe-space_meta"
}
},
{
"test": {
"@alias": "kernel-dev.kernel-dev.Kernel_dev_External_source",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_6 ",
"expected_results": ""
},
"2": {
"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps_6",
"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_6"
}
},
"summary": "Kernel_dev_External_source"
}
},
{
"test": {
"@alias": "kernel-dev.kernel-dev.Kernel_dev_building_external_modules(hello-mod)",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_10 ",
"expected_results": ""
},
"2": {
"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup_10",
"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_10"
}
},
"summary": "Kernel_dev_building_external_modules(hello-mod)"
}
},
{
"test": {
"@alias": "kernel-dev.kernel-dev.Kernel_dev_local_parallel_meta",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wikioproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_4 ",
"expected_results": ""
},
"2": {
"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps_4",
"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_4"
}
},
"summary": "Kernel_dev_local_parallel_meta"
}
}
]

158
sources/poky/meta/lib/oeqa/manual/oe-core.json Normal file
View File

@@ -0,0 +1,158 @@
[
{
"test": {
"@alias": "oe-core.bitbake.Test_bitbake_menuconfig",
"author": [
{
"email": "jose.perez.carranza@intel.com",
"name": "jose.perez.carranza@intel.com"
}
],
"execution": {
"1": {
"action": "clone poky \n \n",
"expected_results": ""
},
"2": {
"action": "cd poky \n\n",
"expected_results": ""
},
"3": {
"action": "source oe-init-build-env && cd build \n\n",
"expected_results": ""
},
"4": {
"action": "set below in local.conf \n\n \tMACHINE = \"qemux86\" \n\n",
"expected_results": ""
},
"5": {
"action": "bitbake linux-yocto -c kernel_configme -f \n\n",
"expected_results": ""
},
"6": {
"action": "bitbake linux-yocto -c menuconfig \n\n",
"expected_results": ""
},
"7": {
"action": "Once menuconfig launches, use the interface to navigate through the selections and \n enable option \"64-bit kernel\" \n\n",
"expected_results": ""
},
"8": {
"action": "Save changes and set name of the file as \"test.config\" ",
"expected_results": "Open file: \n \npoky/build//tmp/work/qemux86-poky-linux/linux-yocto/4.X.X+*/linux-qemux86-standard-build/test.config \n \n \n\nand verify that changes are present in the file as follows: \n \nCONFIG_64BIT=y \n \nCONFIG_X86_64=y"
}
},
"summary": "Test_bitbake_menuconfig"
}
},
{
"test": {
"@alias": "oe-core.bitbake.test_bitbake_devshell",
"author": [
{
"email": "jose.perez.carranza@intel.com",
"name": "jose.perez.carranza@intel.com"
}
],
"execution": {
"1": {
"action": "clone poky ",
"expected_results": ""
},
"2": {
"action": "cd poky ",
"expected_results": ""
},
"3": {
"action": "source oe-init-build-env && cd build ",
"expected_results": ""
},
"4": {
"action": "bitbake matchbox-desktop ",
"expected_results": "Package was build correctly "
},
"5": {
"action": "bitbake matchbox-desktop -c devshell ",
"expected_results": "A terminal with a shell prompt within the OpenEmbedded build environment is opened "
},
"6": {
"action": "Verify that \"matchbox-desktop\" binary file is not created under\"src\" directory ",
"expected_results": ""
},
"7": {
"action": "Run command:./configure ${CONFIGUREOPTS} && make ",
"expected_results": "Verify that \"matchbox-desktop\" binary file was created successfully under \"src/\" directory "
},
"8": {
"action": "Exit fromthe devshell terminal,exit ",
"expected_results": "Terminal back to the build directory"
}
},
"summary": "test_bitbake_devshell"
}
},
{
"test": {
"@alias": "oe-core.bitbake.test_dependency_explorer_is_launched",
"author": [
{
"email": "jose.perez.carranza@intel.com",
"name": "jose.perez.carranza@intel.com"
}
],
"execution": {
"1": {
"action": "clone poky ",
"expected_results": ""
},
"2": {
"action": "cd poky ",
"expected_results": ""
},
"3": {
"action": "source oe-init-build-env ",
"expected_results": ""
},
"4": {
"action": "bitbake -u taskexp -g core-image-full-cmdline \n\nNOTE: To execute the last command of this test, it's necessary that the machine is executing an X11 server, or if that's not the case (for example, if running the test on a headless server), it is required to enable ssh X11 forwarding on both, the server and the client, and have the X11 server running on the client. \n\nThe instructions to enable X11 forwarding vary between distributions. But for example, these are the steps to enable it between a server running openSUSE Leap 42.1 and a client with Fedora 24: \nA. On the server, make sure /home//.ssh/config contains the line: \n ForwardX11 yes \nB. On the server, make sure xauth is installed by running: \n which xauth \nC. On the client, connect to the server, enabling X11 forwarding, for example by using: \n ssh -X user@server \nNOTE 2: depexp was renamed to taskexp on 2.3 M4",
"expected_results": "Verify that a \"dependency explorer\" is opened and file \n dependencies are listed "
}
},
"summary": "test_dependency_explorer_is_launched"
}
},
{
"test": {
"@alias": "oe-core.bitbake.test_bitbake_sane_error_for_invalid_layer",
"author": [
{
"email": "jose.perez.carranza@intel.com",
"name": "jose.perez.carranza@intel.com"
}
],
"execution": {
"1": {
"action": "clone poky \n",
"expected_results": ""
},
"2": {
"action": "cd poky \n \n",
"expected_results": ""
},
"3": {
"action": "source oe-init-build-env && cd build \n \n",
"expected_results": ""
},
"4": {
"action": "Add a invalid layer to conf/bblayers.conf \"<poky dir>/my-invalid-layer\" \n\t\n",
"expected_results": ""
},
"5": {
"action": "bitbake core-image-minimal",
"expected_results": "Below error should be displayed:\n\"ERROR: Layer directory does not exist! Please check BBLAYERS in <poky dir>/<build dir>/conf/bblayers.conf\""
}
},
"summary": "test_bitbake_sane_error_for_invalid_layer"
}
}
]

32
sources/poky/meta/lib/oeqa/manual/sdk.json Normal file
View File

@@ -0,0 +1,32 @@
[
{
"test": {
"@alias": "sdk.sdk_runqemu.test_install_cross_toolchain_can_run_multiple_qemu_for_x86",
"author": [
{
"email": "ee.peng.yeoh@intel.com",
"name": "ee.peng.yeoh@intel.com"
}
],
"execution": {
"1": {
"action": "Prepare kernel, rootfs tar.bz2 image, and qemu configuration \n \ta. Download kernel, rootfs tar.bz2 image and qemu configuration from public autobuilder webpage \n \tb. Goto https://autobuilder.yocto.io/pub/releases/<target_release>/machines/qemu/qemux86/ \n \tc. Download \n \t \ti. rootfs tar.bz2: core-image-sato-sdk-qemux86.tar.bz2 \n \t\tii. kernel: bzImage-qemux86.bin \n \t\tiii. qemu configuration: core-image-sato-sdk-qemux86.qemuboot.conf ",
"expected_results": "Download completes successfully."
},
"2": {
"action": "Download & install toolchain tarball matching your host from public autobuilder \n \ta. Goto https://autobuilder.yocto.io/pub/releases/<target_release>/toolchain/x86_64/ \n \tb. Download poky-glibc-x86_64-core-image-sato-<type-arch>-toolchain-<release-version>.sh \n \tc. Run command: poky-glibc-x86_64-core-image-sato-<type-arch>-toolchain-<release-version>.sh \n \td. After installation toolchain Run source command : source /toolchain-installed-path/environment-setup-<architecture name>-poky-linux",
"expected_results": "Toolchain gets installed successfully."
},
"3": {
"action": "Extract rootfs twice into two images \n \ta. Run 2 commands below: \n runqemu-extract-sdk core-image-sato-sdk-qemux86.tar.bz2 qemux86_rootfs_image1 \n runqemu-extract-sdk core-image-sato-sdk-qemux86.tar.bz2 qemux86_rootfs_image2",
"expected_results": "Both images build successfully."
},
"4": {
"action": " From the 2 terminals, start qemu to boot up both two images \n \ta. Run 2 commands below: \n runqemu <kernel-name> core-image-sato-sdk-qemux86.qemuboot.conf qemux86_rootfs_image1 \n runqemu <kernel-name> core-image-sato-sdk-qemux86.qemuboot.conf qemux86_rootfs_image2 ",
"expected_results": "Expect both qemu to boot up successfully."
}
},
"summary": "test_install_cross_toolchain_can_run_multiple_qemu_for:x86"
}
}
]

2572
sources/poky/meta/lib/oeqa/manual/toaster-managed-mode.json Normal file
View File

File diff suppressed because it is too large Load Diff

1170
sources/poky/meta/lib/oeqa/manual/toaster-unmanaged-mode.json Normal file
View File

File diff suppressed because it is too large Load Diff