diff --git a/configs/AM335X/AM335X_linux_config.txt b/configs/AM335X/AM335X_linux_config.txt index 323004ed7..13ae94a57 100644 --- a/configs/AM335X/AM335X_linux_config.txt +++ b/configs/AM335X/AM335X_linux_config.txt @@ -26,7 +26,6 @@ Replacement Variables '__LINUX_UBUNTU_VERSION_SHORT__' : '22.04' '__RTOS_UBUNTU_VERSION_LONG__' : '14.04 (64-bit), 16.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : 'featuring Matrix' '__SYSFW_CORE_NAME__' : \ '__IMAGE_TYPE__' : 'default' diff --git a/configs/AM335X/AM335X_linux_toc.txt b/configs/AM335X/AM335X_linux_toc.txt index 50aa51765..e5217f6d4 100644 --- a/configs/AM335X/AM335X_linux_toc.txt +++ b/configs/AM335X/AM335X_linux_toc.txt @@ -118,10 +118,8 @@ linux/Foundational_Components/Graphics/SGX/Build_Guide linux/Examples_and_Demos linux/Examples_and_Demos_Application_Demos linux/Examples_and_Demos/Application_Demos/QT_Thermostat_HMI_Demo -linux/Examples_and_Demos/Application_Demos/PdM_Anomaly_Detection linux/Examples_and_Demos/Application_Demos/PRU_ADC linux/Examples_and_Demos/Application_Demos/Additional_Application_Demo_Links -linux/Examples_and_Demos_Matrix_User_Guide linux/Examples_and_Demos_Sub-system_Demos linux/How_to_Guides linux/How_to_Guides_Host @@ -130,10 +128,8 @@ linux/How_to_Guides/Host/Customizing_the_SDK_Splash_Screen linux/How_to_Guides/Host/AM335x_ICEv2_flash_erase linux/How_to_Guides/Host/Program_the_eMMC_on_Beaglebone_Black linux/How_to_Guides_Target -linux/How_to_Guides/Target/How_to_Recalibrate_the_Touchscreen linux/How_to_Guides/Target/Processor_SDK_Linux_File_System_Optimization_Customization linux/How_to_Guides/Target/How_to_add_a_JVM -linux/How_to_Guides/Target/How_to_use_a_Mouse_instead_of_the_Touchscreen_with_Matrix linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux linux/How_to_Guides/Target/How_to_fix_y2k38 linux/How_to_Guides/Target/How_to_Change_dtb_File diff --git a/configs/AM437X/AM437X_linux_config.txt b/configs/AM437X/AM437X_linux_config.txt index 07a54fa24..78f96a422 100644 --- a/configs/AM437X/AM437X_linux_config.txt +++ b/configs/AM437X/AM437X_linux_config.txt @@ -26,7 +26,6 @@ Replacement Variables '__LINUX_UBUNTU_VERSION_SHORT__' : '22.04' '__RTOS_UBUNTU_VERSION_LONG__' : '14.04 (64-bit), 16.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : 'featuring Matrix' '__SYSFW_CORE_NAME__' : \ '__IMAGE_TYPE__' : 'default' diff --git a/configs/AM437X/AM437X_linux_toc.txt b/configs/AM437X/AM437X_linux_toc.txt index 2c28029a2..40a0810b1 100644 --- a/configs/AM437X/AM437X_linux_toc.txt +++ b/configs/AM437X/AM437X_linux_toc.txt @@ -117,9 +117,7 @@ linux/Foundational_Components/Graphics/SGX/Build_Guide linux/Examples_and_Demos linux/Examples_and_Demos_Application_Demos linux/Examples_and_Demos/Application_Demos/QT_Thermostat_HMI_Demo -linux/Examples_and_Demos/Application_Demos/PdM_Anomaly_Detection linux/Examples_and_Demos/Application_Demos/Additional_Application_Demo_Links -linux/Examples_and_Demos_Matrix_User_Guide linux/Examples_and_Demos_Sub-system_Demos linux/How_to_Guides linux/How_to_Guides_Host @@ -127,10 +125,8 @@ linux/How_to_Guides/Host/Moving_Files_to_the_Target_System linux/How_to_Guides/Host/Customizing_the_SDK_Splash_Screen linux/How_to_Guides/Host/AM335x_AM437x_Hardware_Migration_Guide linux/How_to_Guides_Target -linux/How_to_Guides/Target/How_to_Recalibrate_the_Touchscreen linux/How_to_Guides/Target/Processor_SDK_Linux_File_System_Optimization_Customization linux/How_to_Guides/Target/How_to_add_a_JVM -linux/How_to_Guides/Target/How_to_use_a_Mouse_instead_of_the_Touchscreen_with_Matrix linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux linux/How_to_Guides/Target/How_to_Change_dtb_File linux/How_to_Guides/Target/How_to_fix_y2k38 diff --git a/configs/AM57X/AM57X_linux_config.txt b/configs/AM57X/AM57X_linux_config.txt index 4e7f956f9..ef60a246f 100644 --- a/configs/AM57X/AM57X_linux_config.txt +++ b/configs/AM57X/AM57X_linux_config.txt @@ -26,7 +26,6 @@ Replacement Variables '__LINUX_UBUNTU_VERSION_SHORT__' : '22.04' '__OPTEE_PLATFORM_FLAVOR__' : 'am57xx' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : \ '__IMAGE_TYPE__' : 'default' diff --git a/configs/AM57X/AM57X_linux_toc.txt b/configs/AM57X/AM57X_linux_toc.txt index c5a933b76..23a72345c 100644 --- a/configs/AM57X/AM57X_linux_toc.txt +++ b/configs/AM57X/AM57X_linux_toc.txt @@ -140,10 +140,8 @@ linux/How_to_Guides/Host/How_to_Flash_Linux_System_from_U-boot linux/How_to_Guides/Host/Customizing_the_SDK_Splash_Screen linux/How_to_Guides/Host/Additional_How_to_Guide_Links linux/How_to_Guides_Target -linux/How_to_Guides/Target/How_to_Recalibrate_the_Touchscreen linux/How_to_Guides/Target/Processor_SDK_Linux_File_System_Optimization_Customization linux/How_to_Guides/Target/How_to_add_a_JVM -linux/How_to_Guides/Target/How_to_use_a_Mouse_instead_of_the_Touchscreen_with_Matrix linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux linux/How_to_Guides/Target/How_to_Change_dtb_File linux/How_to_Guides/Target/How_to_fix_y2k38 diff --git a/configs/AM62AX/AM62AX_edgeai_config.txt b/configs/AM62AX/AM62AX_edgeai_config.txt index 8dd6ad9f1..31fd4a687 100644 --- a/configs/AM62AX/AM62AX_edgeai_config.txt +++ b/configs/AM62AX/AM62AX_edgeai_config.txt @@ -27,7 +27,6 @@ Replacement Variables '__OPTEE_PLATFORM_FLAVOR__' : 'k3-am62axx' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '10 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' Configuration Values diff --git a/configs/AM62AX/AM62AX_linux_config.txt b/configs/AM62AX/AM62AX_linux_config.txt index 9596baca6..7007232d1 100644 --- a/configs/AM62AX/AM62AX_linux_config.txt +++ b/configs/AM62AX/AM62AX_linux_config.txt @@ -28,7 +28,6 @@ Replacement Variables '__FAMILY_NAME__' : 'am62ax' '__RTOS_UBUNTU_VERSION_LONG__' : '18.04 (64-bit), 16.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '10 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__IMAGE_TYPE__' : 'edgeai' diff --git a/configs/AM62DX/AM62DX_linux_config.txt b/configs/AM62DX/AM62DX_linux_config.txt index cc30aff05..94652be4b 100644 --- a/configs/AM62DX/AM62DX_linux_config.txt +++ b/configs/AM62DX/AM62DX_linux_config.txt @@ -28,7 +28,6 @@ Replacement Variables '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit), 16.04 (64-bit)' '__FAMILY_NAME__' : 'am62dxx' '__WINDOWS_SUPPORTED_LONG__' : '11 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__IMAGE_TYPE__' : 'default' diff --git a/configs/AM62LX/AM62LX_linux_config.txt b/configs/AM62LX/AM62LX_linux_config.txt index 07a5ac470..3bf9ad70e 100644 --- a/configs/AM62LX/AM62LX_linux_config.txt +++ b/configs/AM62LX/AM62LX_linux_config.txt @@ -28,7 +28,6 @@ Replacement Variables '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit), 16.04 (64-bit)' '__FAMILY_NAME__' : 'am62lxx' '__WINDOWS_SUPPORTED_LONG__' : '10 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__IMAGE_TYPE__' : 'default' diff --git a/configs/AM62PX/AM62PX_android_config.txt b/configs/AM62PX/AM62PX_android_config.txt index 9ebcd6ee3..c355b94bb 100644 --- a/configs/AM62PX/AM62PX_android_config.txt +++ b/configs/AM62PX/AM62PX_android_config.txt @@ -26,7 +26,6 @@ Replacement Variables '__LINUX_UBUNTU_VERSION_SHORT__' : '22.04' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit), 16.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '10 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' Configuration Values diff --git a/configs/AM62PX/AM62PX_linux_config.txt b/configs/AM62PX/AM62PX_linux_config.txt index dcbb13a19..f95320981 100644 --- a/configs/AM62PX/AM62PX_linux_config.txt +++ b/configs/AM62PX/AM62PX_linux_config.txt @@ -28,7 +28,6 @@ Replacement Variables '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit), 16.04 (64-bit)' '__FAMILY_NAME__' : 'am62px' '__WINDOWS_SUPPORTED_LONG__' : '10 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__IMAGE_TYPE__' : 'default' '__SPL_VCI_STRING_LEN__' : '20' diff --git a/configs/AM62X/AM62X_android_config.txt b/configs/AM62X/AM62X_android_config.txt index dd6a05e25..f988583d5 100644 --- a/configs/AM62X/AM62X_android_config.txt +++ b/configs/AM62X/AM62X_android_config.txt @@ -26,7 +26,6 @@ Replacement Variables '__LINUX_UBUNTU_VERSION_SHORT__' : '22.04' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit), 16.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '10 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' Configuration Values diff --git a/configs/AM62X/AM62X_linux_config.txt b/configs/AM62X/AM62X_linux_config.txt index 003e8a5bf..a58761499 100644 --- a/configs/AM62X/AM62X_linux_config.txt +++ b/configs/AM62X/AM62X_linux_config.txt @@ -28,7 +28,6 @@ Replacement Variables '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit), 16.04 (64-bit)' '__FAMILY_NAME__' : 'am62x' '__WINDOWS_SUPPORTED_LONG__' : '10 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__IMAGE_TYPE__' : 'default' '__SPL_VCI_STRING_LEN__' : '19' diff --git a/configs/AM64X/AM64X_linux_config.txt b/configs/AM64X/AM64X_linux_config.txt index 6c9c05215..54be98b93 100644 --- a/configs/AM64X/AM64X_linux_config.txt +++ b/configs/AM64X/AM64X_linux_config.txt @@ -28,7 +28,6 @@ Replacement Variables '__FAMILY_NAME__' : 'am64x' '__RTOS_UBUNTU_VERSION_LONG__' : '14.04 (64-bit), 16.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '10 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'DMSC' '__PCIE_BASE_ADDRESS__' : 'f102000' '__PCIE_DEVICE_ID__' : '0xb010' diff --git a/configs/AM65X/AM65X_linux_config.txt b/configs/AM65X/AM65X_linux_config.txt index e1523618d..4072c778a 100644 --- a/configs/AM65X/AM65X_linux_config.txt +++ b/configs/AM65X/AM65X_linux_config.txt @@ -27,7 +27,6 @@ Replacement Variables '__OPTEE_PLATFORM_FLAVOR__' : 'k3-am65x' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'DMSC' '__IMAGE_TYPE__' : 'default' diff --git a/configs/AM65X/AM65X_linux_toc.txt b/configs/AM65X/AM65X_linux_toc.txt index 159584123..d81faccf6 100644 --- a/configs/AM65X/AM65X_linux_toc.txt +++ b/configs/AM65X/AM65X_linux_toc.txt @@ -121,7 +121,6 @@ linux/How_to_Guides/Host/Moving_Files_to_the_Target_System linux/How_to_Guides/Host/K3_Resource_Partitioning_Tool linux/How_to_Guides/Target/Processor_SDK_Linux_File_System_Optimization_Customization linux/How_to_Guides/Target/How_to_add_a_JVM -linux/How_to_Guides/Target/How_to_use_a_Mouse_instead_of_the_Touchscreen_with_Matrix linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux linux/How_to_Guides/Target/How_to_Use_K3Conf_Tool linux/How_to_Guides/Target/How_to_Tune_Real_Time_Linux diff --git a/configs/AM67/AM67_linux_config.txt b/configs/AM67/AM67_linux_config.txt index 47001d9d4..9ed398e89 100644 --- a/configs/AM67/AM67_linux_config.txt +++ b/configs/AM67/AM67_linux_config.txt @@ -27,7 +27,6 @@ Replacement Variables '__OPTEE_PLATFORM_FLAVOR__' : 'k3-am62px' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__IMAGE_TYPE__' : 'default' diff --git a/configs/AM67A/AM67A_android_config.txt b/configs/AM67A/AM67A_android_config.txt index fb1c18b3a..9a5c96c3a 100644 --- a/configs/AM67A/AM67A_android_config.txt +++ b/configs/AM67A/AM67A_android_config.txt @@ -23,7 +23,6 @@ Replacement Variables '__LINUX_UBUNTU_VERSION_SHORT__' : '22.04' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit), 16.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '10 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' Configuration Values diff --git a/configs/AM67A/AM67A_linux_config.txt b/configs/AM67A/AM67A_linux_config.txt index 6ac304d03..473317fc8 100644 --- a/configs/AM67A/AM67A_linux_config.txt +++ b/configs/AM67A/AM67A_linux_config.txt @@ -28,7 +28,6 @@ Replacement Variables '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit), 16.04 (64-bit)' '__FAMILY_NAME__' : 'j722s' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__IMAGE_TYPE__' : 'edgeai' diff --git a/configs/AM68/AM68_linux_config.txt b/configs/AM68/AM68_linux_config.txt index 07203eced..952403d0a 100644 --- a/configs/AM68/AM68_linux_config.txt +++ b/configs/AM68/AM68_linux_config.txt @@ -27,7 +27,6 @@ Replacement Variables '__OPTEE_PLATFORM_FLAVOR__' : 'k3-j784s4' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__PCIE_BASE_ADDRESS__' : '2910000' '__PCIE_DEVICE_ID__' : '0xb00d' diff --git a/configs/AM68A/AM68A_linux_config.txt b/configs/AM68A/AM68A_linux_config.txt index 4cfe9520d..f68c845b8 100755 --- a/configs/AM68A/AM68A_linux_config.txt +++ b/configs/AM68A/AM68A_linux_config.txt @@ -27,7 +27,6 @@ Replacement Variables '__OPTEE_PLATFORM_FLAVOR__' : 'k3-j784s4' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__IMAGE_TYPE__' : 'edgeai' diff --git a/configs/AM69/AM69_linux_config.txt b/configs/AM69/AM69_linux_config.txt index 7e50585cc..cd4d54ffd 100644 --- a/configs/AM69/AM69_linux_config.txt +++ b/configs/AM69/AM69_linux_config.txt @@ -27,7 +27,6 @@ Replacement Variables '__OPTEE_PLATFORM_FLAVOR__' : 'k3-j784s4' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__PCIE_BASE_ADDRESS__' : '2900000' '__PCIE_DEVICE_ID__' : '0xb00d' diff --git a/configs/AM69A/AM69A_linux_config.txt b/configs/AM69A/AM69A_linux_config.txt index 07c86f098..27f21572c 100755 --- a/configs/AM69A/AM69A_linux_config.txt +++ b/configs/AM69A/AM69A_linux_config.txt @@ -27,7 +27,6 @@ Replacement Variables '__OPTEE_PLATFORM_FLAVOR__' : 'k3-j784s4' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__IMAGE_TYPE__' : 'edgeai' diff --git a/configs/CORESDK/CORESDK_linux_config.txt b/configs/CORESDK/CORESDK_linux_config.txt index 56c225a80..c95f170e6 100644 --- a/configs/CORESDK/CORESDK_linux_config.txt +++ b/configs/CORESDK/CORESDK_linux_config.txt @@ -25,7 +25,6 @@ Replacement Variables '__LINUX_UBUNTU_VERSION_SHORT__' : '18.04' '__RTOS_UBUNTU_VERSION_LONG__' : '14.04 (64-bit), 16.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : 'featuring Matrix' '__SYSFW_CORE_NAME__' : \ '__IMAGE_TYPE__' : 'default' diff --git a/configs/DRA821A/DRA821A_linux_config.txt b/configs/DRA821A/DRA821A_linux_config.txt index 5c60ebc3b..c82a05ff3 100644 --- a/configs/DRA821A/DRA821A_linux_config.txt +++ b/configs/DRA821A/DRA821A_linux_config.txt @@ -26,7 +26,6 @@ Replacement Variables '__LINUX_UBUNTU_VERSION_SHORT__' : '18.04' '__RTOS_UBUNTU_VERSION_LONG__' : '18.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : \ '__IMAGE_TYPE__' : 'default' diff --git a/configs/GEN/GEN_android_config.txt b/configs/GEN/GEN_android_config.txt index f8a81998d..c763aa153 100644 --- a/configs/GEN/GEN_android_config.txt +++ b/configs/GEN/GEN_android_config.txt @@ -25,7 +25,6 @@ Replacement Variables '__LINUX_UBUNTU_VERSION_SHORT__' : '18.04' '__RTOS_UBUNTU_VERSION_LONG__' : '18.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : \ Configuration Values diff --git a/configs/GEN/GEN_linux_config.txt b/configs/GEN/GEN_linux_config.txt index cc43cbc0b..ec86a3626 100644 --- a/configs/GEN/GEN_linux_config.txt +++ b/configs/GEN/GEN_linux_config.txt @@ -26,7 +26,6 @@ Replacement Variables '__LINUX_UBUNTU_VERSION_SHORT__' : '16.04 or 18.04' '__RTOS_UBUNTU_VERSION_LONG__' : '14.04 (64-bit), 16.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : 'featuring Matrix' '__IMAGE_TYPE__' : 'default' Configuration Values diff --git a/configs/GEN/GEN_linux_toc.txt b/configs/GEN/GEN_linux_toc.txt index bf39c6413..9f38816da 100644 --- a/configs/GEN/GEN_linux_toc.txt +++ b/configs/GEN/GEN_linux_toc.txt @@ -140,17 +140,14 @@ linux/Industrial_Protocols_OPCUA linux/Examples_and_Demos linux/Examples_and_Demos_Application_Demos linux/Examples_and_Demos/Application_Demos/Dual_Camera_Demo -linux/Examples_and_Demos/Application_Demos/Video_Analytics linux/Examples_and_Demos/Application_Demos/Barcode linux/Examples_and_Demos/Application_Demos/QT_Thermostat_HMI_Demo linux/Examples_and_Demos/Application_Demos/Optical_Flow_with_OpenVX linux/Examples_and_Demos/Application_Demos/ROS_Radar -linux/Examples_and_Demos/Application_Demos/PdM_Anomaly_Detection linux/Examples_and_Demos/Application_Demos/PRU_ADC linux/Examples_and_Demos/Application_Demos/Video_Graphics_Test linux/Examples_and_Demos/Application_Demos/Watchdog_demo linux/Examples_and_Demos/Application_Demos/Additional_Application_Demo_Links -linux/Examples_and_Demos_Matrix_User_Guide linux/Examples_and_Demos_Sub-system_Demos linux/How_to_Guides linux/How_to_Guides_Host @@ -165,10 +162,8 @@ linux/How_to_Guides/Host/AM335x_ICEv2_flash_erase linux/How_to_Guides/Host/How_to_Setup_Ubuntu_1404_Network_Boot linux/How_to_Guides/Host/Additional_How_to_Guide_Links linux/How_to_Guides_Target -linux/How_to_Guides/Target/How_to_Recalibrate_the_Touchscreen linux/How_to_Guides/Target/Processor_SDK_Linux_File_System_Optimization_Customization linux/How_to_Guides/Target/How_to_add_a_JVM -linux/How_to_Guides/Target/How_to_use_a_Mouse_instead_of_the_Touchscreen_with_Matrix linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux linux/How_to_Guides/Target/How_to_Change_dtb_File linux/How_to_Guides/Target/How_to_Set_Display_for_AM572x_GP_EVM diff --git a/configs/J7200/J7200_linux_config.txt b/configs/J7200/J7200_linux_config.txt index 047bcf422..fe0e9ba55 100644 --- a/configs/J7200/J7200_linux_config.txt +++ b/configs/J7200/J7200_linux_config.txt @@ -27,7 +27,6 @@ Replacement Variables '__OPTEE_PLATFORM_FLAVOR__' : 'k3-j721e' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'DMSC' '__PCIE_BASE_ADDRESS__' : '2910000' '__PCIE_DEVICE_ID__' : '0xb00f' diff --git a/configs/J721E/J721E_android_config.txt b/configs/J721E/J721E_android_config.txt index e7a40ac2e..8e5e89ffd 100644 --- a/configs/J721E/J721E_android_config.txt +++ b/configs/J721E/J721E_android_config.txt @@ -25,7 +25,6 @@ Replacement Variables '__LINUX_UBUNTU_VERSION_SHORT__' : '18.04' '__RTOS_UBUNTU_VERSION_LONG__' : '18.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'DMSC' Configuration Values diff --git a/configs/J721E/J721E_linux_config.txt b/configs/J721E/J721E_linux_config.txt index 3c0909ca0..3eef58a94 100644 --- a/configs/J721E/J721E_linux_config.txt +++ b/configs/J721E/J721E_linux_config.txt @@ -27,7 +27,6 @@ Replacement Variables '__OPTEE_PLATFORM_FLAVOR__' : 'k3-j721e' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'DMSC' '__PCIE_BASE_ADDRESS__' : '2900000' '__PCIE_DEVICE_ID__' : '0xb00d' diff --git a/configs/J721S2/J721S2_linux_config.txt b/configs/J721S2/J721S2_linux_config.txt index 0fb44b188..9c9cd98fe 100644 --- a/configs/J721S2/J721S2_linux_config.txt +++ b/configs/J721S2/J721S2_linux_config.txt @@ -27,7 +27,6 @@ Replacement Variables '__OPTEE_PLATFORM_FLAVOR__' : 'k3-j784s4' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__PCIE_BASE_ADDRESS__' : '2910000' '__PCIE_DEVICE_ID__' : '0xb00d' diff --git a/configs/J722S/J722S_linux_config.txt b/configs/J722S/J722S_linux_config.txt index 1b51c3ca2..fff0a5229 100644 --- a/configs/J722S/J722S_linux_config.txt +++ b/configs/J722S/J722S_linux_config.txt @@ -29,7 +29,6 @@ Replacement Variables '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' '__FAMILY_NAME__' : 'j722s' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__IMAGE_TYPE__' : 'adas' '__SPL_VCI_STRING_LEN__' : '19' diff --git a/configs/J742S2/J742S2_linux_config.txt b/configs/J742S2/J742S2_linux_config.txt index a9526822b..95defe789 100644 --- a/configs/J742S2/J742S2_linux_config.txt +++ b/configs/J742S2/J742S2_linux_config.txt @@ -27,7 +27,6 @@ Replacement Variables '__OPTEE_PLATFORM_FLAVOR__' : 'k3-j784s4' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__PCIE_BASE_ADDRESS__' : '2900000' '__PCIE_DEVICE_ID__' : '0xb00d' diff --git a/configs/J784S4/J784S4_linux_config.txt b/configs/J784S4/J784S4_linux_config.txt index 09b2794f4..dc6fba82b 100644 --- a/configs/J784S4/J784S4_linux_config.txt +++ b/configs/J784S4/J784S4_linux_config.txt @@ -27,7 +27,6 @@ Replacement Variables '__OPTEE_PLATFORM_FLAVOR__' : 'k3-j784s4' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'TIFS' '__PCIE_BASE_ADDRESS__' : '2900000' '__PCIE_DEVICE_ID__' : '0xb00d' diff --git a/configs/TDA4VM/TDA4VM_linux_config.txt b/configs/TDA4VM/TDA4VM_linux_config.txt index 61e491fc0..e3aee8e7f 100755 --- a/configs/TDA4VM/TDA4VM_linux_config.txt +++ b/configs/TDA4VM/TDA4VM_linux_config.txt @@ -27,7 +27,6 @@ Replacement Variables '__OPTEE_PLATFORM_FLAVOR__' : 'k3-j721e' '__RTOS_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__FEATURINGMATRIX__' : \ '__SYSFW_CORE_NAME__' : 'DMSC' '__PCIE_BASE_ADDRESS__' : '2900000' '__PCIE_DEVICE_ID__' : '0xb00d' diff --git a/source/devices/AM335X/linux/Release_Specific_Release_Notes.rst b/source/devices/AM335X/linux/Release_Specific_Release_Notes.rst index 7ef90b40e..866da3082 100644 --- a/source/devices/AM335X/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM335X/linux/Release_Specific_Release_Notes.rst @@ -15,7 +15,6 @@ execution of Linux based applications and includes the following: - SDK Installer - Setup Scripts - Makefiles -- Matrix Application Launcher - Example Applications - WLAN support (Wilink 8) - Code Composer Studio diff --git a/source/devices/AM437X/linux/Release_Specific_Release_Notes.rst b/source/devices/AM437X/linux/Release_Specific_Release_Notes.rst index d4855e401..9b2404297 100644 --- a/source/devices/AM437X/linux/Release_Specific_Release_Notes.rst +++ b/source/devices/AM437X/linux/Release_Specific_Release_Notes.rst @@ -16,7 +16,6 @@ execution of Linux based applications and includes the following: - SDK Installer - Setup Scripts - Makefiles -- Matrix Application Launcher - Example Applications - WLAN support (Wilink 8) - Code Composer Studio diff --git a/source/images/AM335x_Power_screen.png b/source/images/AM335x_Power_screen.png deleted file mode 100644 index c4f8f462b..000000000 Binary files a/source/images/AM335x_Power_screen.png and /dev/null differ diff --git a/source/images/AM335x_matrix_set_frequency.png b/source/images/AM335x_matrix_set_frequency.png deleted file mode 100644 index ddcb6785e..000000000 Binary files a/source/images/AM335x_matrix_set_frequency.png and /dev/null differ diff --git a/source/images/AM37xx_LI-3M02_Single_Camera_Approach.png b/source/images/AM37xx_LI-3M02_Single_Camera_Approach.png deleted file mode 100644 index cd9ee5972..000000000 Binary files a/source/images/AM37xx_LI-3M02_Single_Camera_Approach.png and /dev/null differ diff --git a/source/images/CompileErrorFix.PNG b/source/images/CompileErrorFix.PNG deleted file mode 100644 index eff430d49..000000000 Binary files a/source/images/CompileErrorFix.PNG and /dev/null differ diff --git a/source/images/IPC_Demo_Result.jpg b/source/images/IPC_Demo_Result.jpg deleted file mode 100644 index b00c35fde..000000000 Binary files a/source/images/IPC_Demo_Result.jpg and /dev/null differ diff --git a/source/images/MatrixAppLauncher.jpg b/source/images/MatrixAppLauncher.jpg deleted file mode 100644 index 1c2509092..000000000 Binary files a/source/images/MatrixAppLauncher.jpg and /dev/null differ diff --git a/source/images/Matrix_2_Main_Menu.png b/source/images/Matrix_2_Main_Menu.png deleted file mode 100644 index db3941e34..000000000 Binary files a/source/images/Matrix_2_Main_Menu.png and /dev/null differ diff --git a/source/images/Matrix_app_launcher.png b/source/images/Matrix_app_launcher.png deleted file mode 100644 index d92d3db6a..000000000 Binary files a/source/images/Matrix_app_launcher.png and /dev/null differ diff --git a/source/images/RemoveMenubar.png b/source/images/RemoveMenubar.png deleted file mode 100644 index 1c180a1cf..000000000 Binary files a/source/images/RemoveMenubar.png and /dev/null differ diff --git a/source/images/Screenshot-2.png b/source/images/Screenshot-2.png deleted file mode 100644 index 733bd4980..000000000 Binary files a/source/images/Screenshot-2.png and /dev/null differ diff --git a/source/images/Sitara-Debugger.png b/source/images/Sitara-Debugger.png deleted file mode 100644 index 1dddd2c20..000000000 Binary files a/source/images/Sitara-Debugger.png and /dev/null differ diff --git a/source/images/Sitara-Linux_QT_Resize_screen.png b/source/images/Sitara-Linux_QT_Resize_screen.png deleted file mode 100644 index 4b2c4f8fb..000000000 Binary files a/source/images/Sitara-Linux_QT_Resize_screen.png and /dev/null differ diff --git a/source/images/Sitara-compilerAndDebugger.jpeg b/source/images/Sitara-compilerAndDebugger.jpeg deleted file mode 100644 index 8792adb47..000000000 Binary files a/source/images/Sitara-compilerAndDebugger.jpeg and /dev/null differ diff --git a/source/images/Sitara-linux-Terminal-hello.jpeg b/source/images/Sitara-linux-Terminal-hello.jpeg deleted file mode 100644 index 678e24cbc..000000000 Binary files a/source/images/Sitara-linux-Terminal-hello.jpeg and /dev/null differ diff --git a/source/images/Sitara-linux-kits.png b/source/images/Sitara-linux-kits.png deleted file mode 100644 index b021c6f16..000000000 Binary files a/source/images/Sitara-linux-kits.png and /dev/null differ diff --git a/source/images/Sitara-linux-training-cross-tools-1.png b/source/images/Sitara-linux-training-cross-tools-1.png deleted file mode 100644 index 93e3d2814..000000000 Binary files a/source/images/Sitara-linux-training-cross-tools-1.png and /dev/null differ diff --git a/source/images/Sitara-terminal-pro.jpeg b/source/images/Sitara-terminal-pro.jpeg deleted file mode 100644 index 603eadebe..000000000 Binary files a/source/images/Sitara-terminal-pro.jpeg and /dev/null differ diff --git a/source/images/Sitara_Build_settings_1.png b/source/images/Sitara_Build_settings_1.png deleted file mode 100644 index a02e43177..000000000 Binary files a/source/images/Sitara_Build_settings_1.png and /dev/null differ diff --git a/source/images/Sitara_Linux_QT_Deploy_Public_Key.png b/source/images/Sitara_Linux_QT_Deploy_Public_Key.png deleted file mode 100644 index 7ce6dbb8f..000000000 Binary files a/source/images/Sitara_Linux_QT_Deploy_Public_Key.png and /dev/null differ diff --git a/source/images/Sitara_Linux_QT_Device_Configuration_Wizard_Selection.jpeg b/source/images/Sitara_Linux_QT_Device_Configuration_Wizard_Selection.jpeg deleted file mode 100644 index ea9bc19b3..000000000 Binary files a/source/images/Sitara_Linux_QT_Device_Configuration_Wizard_Selection.jpeg and /dev/null differ diff --git a/source/images/Sitara_Linux_QT_Password_for_Private_Key.jpeg b/source/images/Sitara_Linux_QT_Password_for_Private_Key.jpeg deleted file mode 100644 index d4f69acf5..000000000 Binary files a/source/images/Sitara_Linux_QT_Password_for_Private_Key.jpeg and /dev/null differ diff --git a/source/images/Sitara_Linux_QT_create_new_ssh_key.png b/source/images/Sitara_Linux_QT_create_new_ssh_key.png deleted file mode 100644 index 29453079e..000000000 Binary files a/source/images/Sitara_Linux_QT_create_new_ssh_key.png and /dev/null differ diff --git a/source/images/Sitara_Linux_QT_environment_setup_script.jpeg b/source/images/Sitara_Linux_QT_environment_setup_script.jpeg deleted file mode 100644 index 7d01b7cd8..000000000 Binary files a/source/images/Sitara_Linux_QT_environment_setup_script.jpeg and /dev/null differ diff --git a/source/images/Sitara_Linux_QT_library_listings_1.png b/source/images/Sitara_Linux_QT_library_listings_1.png deleted file mode 100644 index 714833c11..000000000 Binary files a/source/images/Sitara_Linux_QT_library_listings_1.png and /dev/null differ diff --git a/source/images/Sitara_Linux_QT_make_using_cross_compile.jpeg b/source/images/Sitara_Linux_QT_make_using_cross_compile.jpeg deleted file mode 100644 index 72fab1b2e..000000000 Binary files a/source/images/Sitara_Linux_QT_make_using_cross_compile.jpeg and /dev/null differ diff --git a/source/images/Sitara_Linux_QT_new_project.png b/source/images/Sitara_Linux_QT_new_project.png deleted file mode 100644 index 9e50c33cc..000000000 Binary files a/source/images/Sitara_Linux_QT_new_project.png and /dev/null differ diff --git a/source/images/Sitara_Linux_QT_new_terminal_props.png b/source/images/Sitara_Linux_QT_new_terminal_props.png deleted file mode 100644 index b7d4a1740..000000000 Binary files a/source/images/Sitara_Linux_QT_new_terminal_props.png and /dev/null differ diff --git a/source/images/Sitara_Linux_QT_ok_to_close_devices.png b/source/images/Sitara_Linux_QT_ok_to_close_devices.png deleted file mode 100644 index c6f978ea6..000000000 Binary files a/source/images/Sitara_Linux_QT_ok_to_close_devices.png and /dev/null differ diff --git a/source/images/Sitara_Linux_QT_options.jpeg b/source/images/Sitara_Linux_QT_options.jpeg deleted file mode 100644 index f7e4df7dd..000000000 Binary files a/source/images/Sitara_Linux_QT_options.jpeg and /dev/null differ diff --git a/source/images/Sitara_Linux_QT_options_SSH_Key_Configuration.jpeg b/source/images/Sitara_Linux_QT_options_SSH_Key_Configuration.jpeg deleted file mode 100644 index 9af2eafac..000000000 Binary files a/source/images/Sitara_Linux_QT_options_SSH_Key_Configuration.jpeg and /dev/null differ diff --git a/source/images/Sitara_Linux_QT_options_add_device.png b/source/images/Sitara_Linux_QT_options_add_device.png deleted file mode 100644 index b6aac59ff..000000000 Binary files a/source/images/Sitara_Linux_QT_options_add_device.png and /dev/null differ diff --git a/source/images/Sitara_Linux_QT_qtcreator.png b/source/images/Sitara_Linux_QT_qtcreator.png deleted file mode 100644 index 831b25286..000000000 Binary files a/source/images/Sitara_Linux_QT_qtcreator.png and /dev/null differ diff --git a/source/images/Sitara_Linux_Qt_project_kits_select.png b/source/images/Sitara_Linux_Qt_project_kits_select.png deleted file mode 100644 index 8a3d4c73d..000000000 Binary files a/source/images/Sitara_Linux_Qt_project_kits_select.png and /dev/null differ diff --git a/source/images/Sitara_Linux_Qt_project_vc_select.png b/source/images/Sitara_Linux_Qt_project_vc_select.png deleted file mode 100644 index cbfba32ad..000000000 Binary files a/source/images/Sitara_Linux_Qt_project_vc_select.png and /dev/null differ diff --git a/source/images/Sitara_Linux_options_Generic_Linux_Device_Configuration_Setup.jpeg b/source/images/Sitara_Linux_options_Generic_Linux_Device_Configuration_Setup.jpeg deleted file mode 100644 index d06f9743a..000000000 Binary files a/source/images/Sitara_Linux_options_Generic_Linux_Device_Configuration_Setup.jpeg and /dev/null differ diff --git a/source/images/Sitara_SendCMD_code.png b/source/images/Sitara_SendCMD_code.png deleted file mode 100644 index 6e38136c5..000000000 Binary files a/source/images/Sitara_SendCMD_code.png and /dev/null differ diff --git a/source/images/Sitara_add_command.png b/source/images/Sitara_add_command.png deleted file mode 100644 index c593d228d..000000000 Binary files a/source/images/Sitara_add_command.png and /dev/null differ diff --git a/source/images/Sitara_add_target_loc.jpeg b/source/images/Sitara_add_target_loc.jpeg deleted file mode 100644 index 1f9c5c86b..000000000 Binary files a/source/images/Sitara_add_target_loc.jpeg and /dev/null differ diff --git a/source/images/Sitara_addexisting.png b/source/images/Sitara_addexisting.png deleted file mode 100644 index 0af0d4197..000000000 Binary files a/source/images/Sitara_addexisting.png and /dev/null differ diff --git a/source/images/Sitara_addkeyboard.png b/source/images/Sitara_addkeyboard.png deleted file mode 100644 index 3c66f4054..000000000 Binary files a/source/images/Sitara_addkeyboard.png and /dev/null differ diff --git a/source/images/Sitara_adjust_widths.png b/source/images/Sitara_adjust_widths.png deleted file mode 100644 index f697f8a66..000000000 Binary files a/source/images/Sitara_adjust_widths.png and /dev/null differ diff --git a/source/images/Sitara_default_url.png b/source/images/Sitara_default_url.png deleted file mode 100644 index d9be82890..000000000 Binary files a/source/images/Sitara_default_url.png and /dev/null differ diff --git a/source/images/Sitara_deploy_remote.jpeg b/source/images/Sitara_deploy_remote.jpeg deleted file mode 100644 index 54fc41ec0..000000000 Binary files a/source/images/Sitara_deploy_remote.jpeg and /dev/null differ diff --git a/source/images/Sitara_fullscreen.png b/source/images/Sitara_fullscreen.png deleted file mode 100644 index bd002e453..000000000 Binary files a/source/images/Sitara_fullscreen.png and /dev/null differ diff --git a/source/images/Sitara_goto_slot.jpeg b/source/images/Sitara_goto_slot.jpeg deleted file mode 100644 index f8b472769..000000000 Binary files a/source/images/Sitara_goto_slot.jpeg and /dev/null differ diff --git a/source/images/Sitara_hello_world_UI.png b/source/images/Sitara_hello_world_UI.png deleted file mode 100644 index db4afccd4..000000000 Binary files a/source/images/Sitara_hello_world_UI.png and /dev/null differ diff --git a/source/images/Sitara_layout_vertically.png b/source/images/Sitara_layout_vertically.png deleted file mode 100644 index 55922b7df..000000000 Binary files a/source/images/Sitara_layout_vertically.png and /dev/null differ diff --git a/source/images/Sitara_matrix.PNG b/source/images/Sitara_matrix.PNG deleted file mode 100644 index fde3c063a..000000000 Binary files a/source/images/Sitara_matrix.PNG and /dev/null differ diff --git a/source/images/Sitara_pushbutton.png b/source/images/Sitara_pushbutton.png deleted file mode 100644 index 929dff353..000000000 Binary files a/source/images/Sitara_pushbutton.png and /dev/null differ diff --git a/source/images/Sitara_remote_host.jpeg b/source/images/Sitara_remote_host.jpeg deleted file mode 100644 index f372cbdb9..000000000 Binary files a/source/images/Sitara_remote_host.jpeg and /dev/null differ diff --git a/source/images/Sitara_rename_objects.jpeg b/source/images/Sitara_rename_objects.jpeg deleted file mode 100644 index d28aa137e..000000000 Binary files a/source/images/Sitara_rename_objects.jpeg and /dev/null differ diff --git a/source/images/Sitara_stylesheet.jpeg b/source/images/Sitara_stylesheet.jpeg deleted file mode 100644 index 2cecc8cf5..000000000 Binary files a/source/images/Sitara_stylesheet.jpeg and /dev/null differ diff --git a/source/images/Sitara_successful_deploy.png b/source/images/Sitara_successful_deploy.png deleted file mode 100644 index 1e34cfa43..000000000 Binary files a/source/images/Sitara_successful_deploy.png and /dev/null differ diff --git a/source/images/Sitara_tabStyle.jpeg b/source/images/Sitara_tabStyle.jpeg deleted file mode 100644 index 2c5f026e0..000000000 Binary files a/source/images/Sitara_tabStyle.jpeg and /dev/null differ diff --git a/source/images/Sitara_tab_widget.png b/source/images/Sitara_tab_widget.png deleted file mode 100644 index 44de5e55b..000000000 Binary files a/source/images/Sitara_tab_widget.png and /dev/null differ diff --git a/source/images/Sitara_target_test.png b/source/images/Sitara_target_test.png deleted file mode 100644 index da7915a0e..000000000 Binary files a/source/images/Sitara_target_test.png and /dev/null differ diff --git a/source/images/Sitara_terminal_cpp.jpeg b/source/images/Sitara_terminal_cpp.jpeg deleted file mode 100644 index 4356a1e8b..000000000 Binary files a/source/images/Sitara_terminal_cpp.jpeg and /dev/null differ diff --git a/source/images/Sitara_terminal_h.png b/source/images/Sitara_terminal_h.png deleted file mode 100644 index 45f263fa6..000000000 Binary files a/source/images/Sitara_terminal_h.png and /dev/null differ diff --git a/source/images/Sitara_ui_layout.jpeg b/source/images/Sitara_ui_layout.jpeg deleted file mode 100644 index 2cfa5622e..000000000 Binary files a/source/images/Sitara_ui_layout.jpeg and /dev/null differ diff --git a/source/images/Sitara_webkitwidgets.png b/source/images/Sitara_webkitwidgets.png deleted file mode 100644 index b138f1b7b..000000000 Binary files a/source/images/Sitara_webkitwidgets.png and /dev/null differ diff --git a/source/images/Sitara_webview.jpeg b/source/images/Sitara_webview.jpeg deleted file mode 100644 index 0d4795bd3..000000000 Binary files a/source/images/Sitara_webview.jpeg and /dev/null differ diff --git a/source/images/Sitarea_Linux_Qt_project_terminal.png b/source/images/Sitarea_Linux_Qt_project_terminal.png deleted file mode 100644 index 203fd39ce..000000000 Binary files a/source/images/Sitarea_Linux_Qt_project_terminal.png and /dev/null differ diff --git a/source/images/Va_demo_diagram.png b/source/images/Va_demo_diagram.png deleted file mode 100644 index a91e5454a..000000000 Binary files a/source/images/Va_demo_diagram.png and /dev/null differ diff --git a/source/images/anomaly-detection.png b/source/images/anomaly-detection.png deleted file mode 100644 index 2f08646af..000000000 Binary files a/source/images/anomaly-detection.png and /dev/null differ diff --git a/source/images/data-acquisition-motor-drive.png b/source/images/data-acquisition-motor-drive.png deleted file mode 100644 index 43c88dd20..000000000 Binary files a/source/images/data-acquisition-motor-drive.png and /dev/null differ diff --git a/source/images/develop-pdm-workflow.png b/source/images/develop-pdm-workflow.png deleted file mode 100644 index 77bd63c39..000000000 Binary files a/source/images/develop-pdm-workflow.png and /dev/null differ diff --git a/source/images/pdm-in-matrix-gui.png b/source/images/pdm-in-matrix-gui.png deleted file mode 100644 index cc92aae6e..000000000 Binary files a/source/images/pdm-in-matrix-gui.png and /dev/null differ diff --git a/source/images/pdm-qt-gui-anomaly-detection.png b/source/images/pdm-qt-gui-anomaly-detection.png deleted file mode 100644 index 318ab593b..000000000 Binary files a/source/images/pdm-qt-gui-anomaly-detection.png and /dev/null differ diff --git a/source/images/rnn-inference-lib.png b/source/images/rnn-inference-lib.png deleted file mode 100644 index 6e4bad8ed..000000000 Binary files a/source/images/rnn-inference-lib.png and /dev/null differ diff --git a/source/images/system-model.png b/source/images/system-model.png deleted file mode 100644 index 983827f08..000000000 Binary files a/source/images/system-model.png and /dev/null differ diff --git a/source/images/training-RNN.png b/source/images/training-RNN.png deleted file mode 100644 index 069b1a68d..000000000 Binary files a/source/images/training-RNN.png and /dev/null differ diff --git a/source/linux/Examples_and_Demos.rst b/source/linux/Examples_and_Demos.rst index 6eab682ff..95d85b55d 100644 --- a/source/linux/Examples_and_Demos.rst +++ b/source/linux/Examples_and_Demos.rst @@ -4,13 +4,8 @@ Examples and Demos #################################### -.. ifconfig:: CONFIG_sdk in ('SITARA') - - .. include:: Examples_and_Demos/_Matrix_Demos.rst - .. toctree:: :maxdepth: 5 - Examples_and_Demos_Matrix_User_Guide Examples_and_Demos_Sub-system_Demos Examples_and_Demos_Application_Demos diff --git a/source/linux/Examples_and_Demos/Application_Demos/Additional_Application_Demo_Links.rst b/source/linux/Examples_and_Demos/Application_Demos/Additional_Application_Demo_Links.rst index aa6eb87b8..f726763bc 100644 --- a/source/linux/Examples_and_Demos/Application_Demos/Additional_Application_Demo_Links.rst +++ b/source/linux/Examples_and_Demos/Application_Demos/Additional_Application_Demo_Links.rst @@ -17,7 +17,7 @@ This demo showcases Human Machine Interface (HMI) for Electric Vehicle Supply Eq Protection Relay Demo ===================== -Matrix UI provides out of box demo to showcase Human Machine Interface (HMI) for Protection Relays. More details can be found at http://www.ti.com/tool/TIDEP-0102 +An out of box demo to showcase Human Machine Interface (HMI) for Protection Relays. More details can be found at http://www.ti.com/tool/TIDEP-0102 mmWave Gesture Controlled HMI ============================= diff --git a/source/linux/Examples_and_Demos/Application_Demos/PdM_Anomaly_Detection.rst b/source/linux/Examples_and_Demos/Application_Demos/PdM_Anomaly_Detection.rst deleted file mode 100644 index 2d3aac764..000000000 --- a/source/linux/Examples_and_Demos/Application_Demos/PdM_Anomaly_Detection.rst +++ /dev/null @@ -1,339 +0,0 @@ -.. _PdM_Anomaly_Detection: - -Predictive Maintenance Demo -=========================== - -Introduction --------------- - -Predictive Maintenance (PdM) promises to achieve levels of efficiency and safety on the factory floor never seen before -in the current established best practices for systems and processes. Machine downtime is one of the biggest challenges -on the production line. The current method of MRO (maintain, repair, operate) is far from what the optimum level of -production can be. With predictive maintenance, once data is coming from equipment in real-time (or near real-time depending on application needs), -advanced analytics are used to identify asset reliability risks that could impact business operations. By applying machine -learning and analytics to operational data generated by critical assets to gain a better understanding of asset performance, -companies can act on these insights as part of a continuous improvement process. - -Predictive maintenance employs advanced analytics on the machine data collected from end sensor nodes to draw meaningful insights -that more accurately predict machine failures. It is comprised of three steps: sense, compute and act. Data is collected from sensors -that are already available in machines, by adding NEW sensors, or by using control inputs. Depending upon the machine types -and the required failure analysis, different sensor signals -- such as temperature, sound, magnetic field, current, voltage, ultrasonic, -vibration -- are analyzed to predict the failure. The predicted information from sensor data analysis is used to generate an event, -work order and notification. The sensor data is also used to visualize the machine's overall operating condition. -An action is taken when the event reports an anomaly, a machine that is nearing the end of its useful life, or when wear and tear -is detected in machine parts. - -The following are the advantages of predictive maintenance using analytics: - -* Detects incipient failures and breakdowns in early stages and facilitates early repair -* Establishes shelf life of asset and assesses product warranty -* Maintains inventory and tabs on spare parts -* Explores hypothetical scenarios -* Early notification and alerts to field operators and improves safety standards -* Prevents unnecessary downtime in production processes -* Maximizes lifecycle of equipment -* Enables product innovation . new features, services and pricing models - -Some of the examples of predictive maintenance from real-life scenario includes: - -* Find defective bearings long before defects are visually seen -* Find misalignment between two rotating pieces of equipment -* Recognize when fans become unbalanced -* Identify when bearings need lubrication -* Tell when an electrical connection needs to be tightened -* Alert when oil is contaminated or in need of replacement - -An overview video for predictive maintenance can be found from -`predictive maintenance overview training `__. - -Processor SDK Linux now provides a predictive maintenance demo which leverages Recurrent Neural Network (RNN) -for anomaly detection over motor drive control. The sections below describes the demo in details, including -the system model for anomaly detection with RNN, the workflow of developing the PdM demo with step by step -instructions, the benchmarking results, and the PdM demo deliverables from Processor SDK Linux. - - -Anomaly detection system model with RNN ------------------------------------------ -In addition to Convolutional Neural Network (CNN), recently RNN emerged as high-quality -universal approximation method for time series. It is becoming more effective with -many desktop tools supported by GPU acceleration. - -For anomaly detection, a system model is established to predict the output from the input -for the normal scenario. If prediction of the output values is good, the system model -acts as a high-accuracy approximation of the physical system. With this system model, -if there are significant and continuous prediction errors, it indicates anomalies are happening. - -.. figure:: ../../../images/system-model.png - :width: 420px - :align: center - :height: 200px - - System model for anomaly detection with RNN - -Workflow for developing the PdM demo -------------------------------------------------- - -The figure below illustrates the workflow for developing the PdM demo. -It begins with acquiring data that describes the physical system in a range of healthy and faulty conditions. -The data can be from sensors, or generated from a physical model. Then, the acquired data will go through -some pre-processing, such as down-sampling to reduce the data dimension. After that, it comes to the stage -of developing the model. For PdM, the model can be either a detection model for condition monitoring (e.g., -anomaly detection) or a prediction model for prognostics (e.g., estimating the remaining useful life). -The model development requires identifying appropriate condition indicators and then training a model to -interpret these condition indicators. This is likely an iterative process, as you try different models -and indicators and tune the model parameters such as the number of RNN layers and nodes. The last step is -to deploy the model and integrate the solution into a system for machine monitoring and maintenance -at the edge devices. - -.. figure:: ../../../images/develop-pdm-workflow.png - :width: 800px - :align: center - :height: 200px - - Workflow for developing the PdM demo - - -In the following subsections, details are provided for the individual steps of this workflow using -the anomaly detection for motor drive as the example. - - -Sensor data acquisition -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -In our PdM anomaly detection demo, the sensor data are originating from `motor drive TI design `__. -In this TI design, AM437x IDK (running Processor SDK RTOS, PRU-ICSS EtherCAT Slave, and PRU-ICSS Industrial Drives) -is conducting motor control. It also receives the feedback about the phase current measurement and the position -measurement. On the other hand, AM437x IDK acts as Ethercat slave and communicates with TwinCAT master -on a host machine for setting the target velocity, target position, and etc. - -To acquire the sensor data in real-time, high-speed (921600 baud rate) UART is implemented to send out the -two phase currents (2 bytes each), and the motor position (4 bytes) with sampling rate of 10KHz. -To get continuous sensor data, PyAutoGUI is employed to achieve automated control of TwinCAT, so that -the motor can repeatedly move from position 1 to position 2, and then from position 2 back to position 1. - - -.. figure:: ../../../images/data-acquisition-motor-drive.png - :width: 760px - :align: center - :height: 320px - - Sensor data acquisition from motor drive - - -Sensor data pre-processing -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -For the sensor data with a frequency of 10KHz, simple pre-processing of -low-pass filtering and down-sampling to 50Hz is done to reduce the high frequency noise. -After that, normalization is done for the down-sampled sensor data. - -Depending on the application, some Other preprocessing techniques can be applied, such as -FFT, high order statistics, and wavelets. - - -Offline training to establish the model -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -To establish the RNN model, offline desktop training in MATLAB is done with the two -down-sampled phase currents. The RNN topology contains a single Long Short-Term Memory (LSTM) layer, and a -Fully Connected (FC) layer. There are 31 hidden nodes for the LSTM layer, and -31 inputs and 2 outputs for the FC layer. This is a simple RNN model, which is -specified to avoid overfitting and control the computation load. The trained -model is in Open Neural Network Exchange (ONNX) format. The last layer, regression layer, is the -output layer used for prediction. - - -.. figure:: ../../../images/training-RNN.png - :width: 185px - :align: center - :height: 220px - - Offline training RNN model with LSTM and FC layers - - -The RNN model is trained with the normal scenario data: motor moves with velocity of 100 degree -per second from 45 degree to 270 degree and back to 45, and so on so forth. -With a single training sequence about 50s long, the training with Matlab on a desktop -PC is completed in less than three minutes. - -Some other open source tools, such as Keras/Tensor Flow, Pytorch, can also be used -for the training. - - -Deploy and integration -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -After getting the model, the last step is to deploy the model and integrate it for anomaly -detection at the edge. - - -**Build RNN inference library** - -To establish the RNN inference library implementing the LSTM and FC layers, our initial -solution is using python scripts to convert the ONNX model into CPP header file, which -contains the initialized data structures with all the weights information. -The python scripts supports N stacked LSTM layers, plus one FC layer. The generated -CPP header is then compiled with the LSTM library to create the ARMv7 object file with -the initialization and processing APIs. - -.. figure:: ../../../images/rnn-inference-lib.png - :width: 370px - :align: center - :height: 270px - - Build RNN inference library - - - -**Real time anomaly detection at the edge** - -With the RNN inference library, we build the Linux user space application running on Arm -to perform anomaly detection. The figure below shows the call flow of the anomaly detection. -The two phase currents are received in real-time from the motor control application running on AM4 IDK. -Then, low pass filtering and down-sampling are applied to the phase currents, followed by normalization. -After that, RNN prediction is done upon the pre-processed phase currents, using the RNN inference library -built above. The predicted phase currents are then de-normalized, and compared with the actual phase -currents to calculate the prediction error. The prediction errors at the beginning for the normal -scenario are used for calibration: the maximal prediction error in this stage is scaled with a ratio -larger than 1 to be the anomaly detection threshold. After that, the prediction error will be used -to report anomalies: if the prediction is larger than the threshold found in the calibration stage, -then anomaly is reported. - - -.. figure:: ../../../images/anomaly-detection.png - :width: 480px - :align: center - :height: 360px - - Real time anomaly detection - - -Deliverables from Processor SDK Linux --------------------------------------- - -Processor SDK Linux provides an out of box PdM demo from Matrix GUI. It also supports -re-building the demo from the top-level Makefile. Python-based conversion tool -is also provided to convert an ONNX model into CPP header file. - - -Out of box demo with with pre-recorded sensor data -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The PdM demo for anomaly detection is provided from Matrix GUI under -Analytics submenu - PdM Anomaly Detection with RNN. - -.. figure:: ../../../images/pdm-in-matrix-gui.png - :width: 400px - :align: center - :height: 130px - - PdM anomaly detection demo in Matrix GUI - - -For this out of box demo, pre-recorded sensor data (/usr/share/ti/examples/pdm/normal100-anomaly150-normal100.log) -is used as the testing sequence, as shown in the demo scripts (/usr/bin/runPdmAnomalyDetection.sh). -This testing sequence starts with the normal scenario data, i.e., motor moves with velocity of 100 degree -per second from 45 degree to 270 degree and back to 45, and so on so forth. To create anomalies, the motor -moves with a higher velocity of 150 degree per second after some time. The figure below shows the Qt GUI display -of the demo. The left-side panel shows the real-time sensor input: the two phase currents in blue and green, -and the motor position in orange. The right-side panel shows the detection results: the blue line is the anomaly -detection threshold found from the calibration, the orange line draws the prediction error, while the red line -draws the time period of the detected anomaly. - -.. figure:: ../../../images/pdm-qt-gui-anomaly-detection.png - :width: 960px - :align: center - :height: 540px - - Anomaly detection demo display - - -Filesystem of Processor SDK Linux also packages two more pre-recorded testing sequences -(under /usr/share/ti/examples/pdm/), for some other anomalies. - -* normal270-anomaly170-normal270.log: motor moving from 45 degree to a different (170 instead of 270) degree. -* normal45-270-v100-with-friction2-iter10-15.log: hand-pressing the coupler between the motor and the encoder to add more friction. - - -Support rebuilding the demo from top-level Makefile -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The source of the PdM demo for real-time inference is available at -`pdm-anomaly-detection git rep `__. -The source is also bundled with Processor SDK Linux installer, under the example-applications -directory: - -:: - - [plsdk_install_dir]/example-applications/pdm-anomaly-detection-1.0 - - -Rebuilding of the demo can be done via the top-level Makefile of Processor SDK Linux: - -:: - - cd [plsdk_install_dir] - make pdm-anomaly-detection - - -After the compilation is completed, the demo binary can be found at -[plsdk_install_dir]/example-applications/pdm-anomaly-detection-1.0/RnnPdmAnomalyDetection. - - -ONNX model conversion tool -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Python scripts are provided in the PdM demo source under the model folder -to convert ONNX model to CPP header file with initialized data structures. -It supports N stacked LSTM layers plus on fully connected layer as the last layer. - -Before running the scripts, install the python packages below if this has -not been done earlier. - -:: - - sudo apt install python-pip - pip install numpy pandas scipy onnx - -Then, run the command below to do the conversion: - -:: - - cd pdm-anomaly-detection/model or pdm-anomaly-detection-1.0/model - python ./make_header.py -m ./[onnx-model-file] - -The output CPP header file is called LSTM_model.h which is placed under the same model folder. - - -Benchmarking for anomaly detection with RNN ---------------------------------------------- - -To conduct benchmarking for the RNN based anomaly detection, two threads are used with Qt/QML display -not in the picture. - -* thread 1: main processing thread with RNN prediction and anomaly detection -* thread 2: parsing thread to read senor data - -Linux clock_gettime() function is used for reading the time: - -:: - - clock_gettime(CLOCK_REALTIME, &ts0); - - /* Run LSTM network for prediction */ - runLstm(lstm_in1, lstm_in2, &lstm_out1, &lstm_out2); - - clock_gettime(CLOCK_REALTIME, &ts1); - ns_lstm = (ts1.tv_sec-ts0.tv_sec) * 1000000000 + ts1.tv_nsec-ts0.tv_nsec; - -Two benchmarking points are used: - -* Pre-processing: low-pass filtering and down-sampling to reduce 200 samples to 1 sample -* RNN prediction (LSTM + FC) on 1 sample - -Average compute time per sample: - -* RNN prediction: 0.083ms -* Pre-processing: 0.014ms -* Total (RNN prediction and pre-processing): 0.097ms - -With a sampling rate 50Hz, RNN based anomaly detection consumes around 0.5% of CPU running at 1GHz, -showing a low computation load. diff --git a/source/linux/Examples_and_Demos/Application_Demos/Video_Analytics.rst b/source/linux/Examples_and_Demos/Application_Demos/Video_Analytics.rst deleted file mode 100644 index 95614b901..000000000 --- a/source/linux/Examples_and_Demos/Application_Demos/Video_Analytics.rst +++ /dev/null @@ -1,331 +0,0 @@ -.. http://processors.wiki.ti.com/index.php/Processor_SDK_Demos_Video_Analytics - -Video Analytics -=============== - -.. rubric:: Overview - :name: overview-video-analytics - -The Video Analytics demo shipped with the Processor SDK Linux for AM57xx -showcases how a Linux Application running on Cortex A-15 cluster can -take advantage of C66x DSP, 3D SGX hardware acceleration blocks to -process a real-time camera input feed and render the processed output on -display - all using open programming paradigms such as OpenCV, OpenCL, -OpenGL, and Qt and standard Linux drivers for capture/display. - -A hand gesture is detected using morphological operators from OpenCV -library. The gesture is used to control a parameter (wind speed) used in -physical simulation of water waves. Result of simulation is visualized -in real-time via 3D rendering of water surface. The hardware IP blocks, -such as IVAHD, M4 cores, are not utilized for this demo. - -.. rubric:: Setup - :name: setup - -In order to re-create the demo, user would need a standard `AM572x GP -EVM `__ and `Processor SDK Linux -package `__. The demo is -integrated into the Matrix GUI and can be launched by touching the -"Video Analytics" icon on the LCD. The sources to the demo are packaged -in the Processor SDK Linux Installer, under "example-applications" -folder and can be compiled using the SDK's top-level Makefile - -.. rubric:: Building Blocks - :name: building-blocks - -- **Camera Capture**: The camera module on AM572x GP EVM acquires color - frames of 640x480 resolution. The images are received by the OpenCV - framework using camera capture class, that depends on the standard - V4L2 Linux driver (/dev/video1). -- **Gesture Recognition**: The first 30 frames captured are used to - estimate the background, and later subtracted to extract the hand - contour, using erode and dilute operations available in the OpenCV - Library. Analysis of largest contour is performed to find convex - hulls. Hand gesture classification is based on ratio of outer and - inner contour. Several discrete values are sent to wave simulation - algorithm. -- **Wave Simulation**: Wave simulation is done in two stages: - calculation of initial (t=0)) Phillips spectrum followed by spectrum - updates per each time instant. Height map is generated in both steps - using 2D IFFT (of spectrum). The Gesture inputs are used to vary the - wind direction for wave simulation -- **Graphics Rendering**: Finally, 2D vertex grid is generated with the - above height map. Fragment rendering uses user-defined texture and - height dependent coloring. -- **Display**: The displayed content includes - Camera feed, overlayed - with the contour detection, and the generated water surface - -.. rubric:: Block diagram - :name: block-diagram - -| - -.. raw:: html - -
- -.. raw:: html - -
- -.. Image:: /images/Va_demo_diagram.png - -.. raw:: html - -
- -.. raw:: html - -
- -| - -.. rubric:: Demo Internals - :name: demo-internals - -.. rubric:: Programming Paradigm - :name: programming-paradigm - -- Code running on A15 Linux platform is written in C++ and links with - QT5, OpenCV and OpenCL host side libraries. -- Code running on DSP C66x is written in OpenCL C -- Code running on GPU is written in GLSL. -- Standard V4L2 Linux driver is used for camera capture -- The demo uses OpenCV 3.1, OpenCL 1.2, OpenGL ES 2.0/GLSL and QT 5.5 - -.. rubric:: OpenCV (running on ARM A15s) - :name: opencv-running-on-arm-a15s - -| *FLOW: camera color frames from V4L2 driver -> OpenCV based algorithms - -> single float converted to 4 discrete values* - -Video analytics functionality includes simple algorithm to extract -contours of hand, and detect how widely opened the hand is. A parameter -which indicates ratio between convex hull and contours is used to -control physical simulation of waves.This is an output argument -converted to wind speed, in 2.5-10 ms range (4 discrete values). -Initially image background is estimated (for 30 frames) using MOG2 -(Mixture Of Gaussians), standard OpenCV algorithm. Later, the background -is subtracted from camera frames, before morphological operations: erode -and dilute are performed.Next two steps include contour detection (which -is also presented in camera view window) and convex hull estimation. -Ratio between outer and inner contour indicates (in 1.1-1.8 range) can -be correlated with number of fingers and how widely are they spread. If -they are more widely spread, parameter is converted to higher wind speed -and waves become higher. - -.. rubric:: OpenCL (running on ARM A15s + C66x) - :name: opencl-running-on-arm-a15s-c66x - -| *FLOW: 4 discrete values of wind speed (2.5, 4, 7, 10m/s) -> OpenCL - based algorithms -> 256x256 float height map matrix (-1, ..., +1 range - of vertex heights)* - -Wave surface simulation is based on generation of Phillips (2D) spectrum -followed by 2D IFFT (256x256). Both operations are executed by OpenCL -offload to single DSP core. Many details on this algorithm can be found -in -`graphics.ucsd.edu/courses/rendering/2005/jdewall/tessendorf.pdf `__. -This stage is controlled by wave speed (output of gesture detection -algorithm) using fixed wind direction *(an idea for improvement: wind -direction can be controlled using hand gesture).* - -Height map in form of 256x256 float matrix is generated on output and -used by OpenGL based vertex renderer (performed in next step). Wave -surface simulation consists of two steps: - -- initial setup defining starting conditions (wind speed and wind - direction are used as input in this stage only) -- update of wave surface height map (Phillips spectrum modification - generated at t=0, along time axe and 2D IFFT for each time step). - -.. rubric:: OpenGL ES (running on ARM A15s + GPU/SGX) - :name: opengl-es-running-on-arm-a15s-gpusgx - -*FLOW: 256x256 float height map matrix + fixed texture -> OpenGL ES -based algorithm -> rendered frame buffers* - -OpenGL ES is a subset of Open GL for desktop devices. Important -difference (for this project) is requirement to use vertex buffers and -only triangle strips. Also Qt provides wrapper functions (QOpenGL -functions) created with intention to hide differences between different -OpenGL versions and also to slightly simplify programming. On the -downside, it involves Qt specific syntax (not far from original OpenGL -ES functions). Height Map data (256x256, but sub-sampled by 4x4, hence -64x64 vertices) received from previous stage, are rendered specific -coloring and user supplied JPEG image. Fragment shader does mixing of -texture and color derived from interpolated height giving more natural -visualization. Currently lighting effects are not used (Implementing -this can significantly improve the quality of rendering). - -.. rubric:: QT 5 (running on ARM A15) - :name: qt-5-running-on-arm-a15 - -*FLOW: user input (mouse and keyboard) -> QT application -> windowing -system and control of above threads* - -| qt-opencv-multithreaded - (`github.com/devernay/qt-opencv-multithreaded `__ - ) is skeleton GUI application providing camera input and some basic - image processing algorithms. Additional algorithm (w.r.t baseline) is - hand gesture which starts OpenCV thread and OpenCL simulation thread. - Wave surface window (detached, 600x400) appears only if hand is put - (at 2-3ft) in front of EVM camera. Intensity of waves is defined by - how much fingers are spread. -| Please wait for 2-3 seconds (after start of Gesture detection) before - putting hand in front of camera, to allow good background estimation. - Wave display window can be closed by pressing [x] in top right corner, - and some other algorithm selected or gesture detection restarted (e.g. - to estimate new background). - -.. rubric:: Directory Structure - :name: directory-structure - -The functionality is organized as shows in the files/description below. - -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| | file name | description | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 1 | CameraConnectDialog.cpp/CameraConnectDialog.h | | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2 | CameraGrab.cpp/CameraGrab.h | Auxilliary camera frame acquisition functions to achieve full FPS | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 3 | CameraView.cpp/CameraView.h | Major class instantiated after connecting to camera. This class creates processing thread, wavesimulation thread and also instantiates wave display (3D graphics) widget. | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 4 | CaptureThread.cpp/CaptureThread.h | Input (camera) frame buffering. | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 5 | FrameLabel.cpp/FrameLabel.h | | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 6 | GeometryEngine.cpp/GeometryEngine.h | Height map mash creation, vertex updates | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 7 | Gesture.cpp/Gesture.h | Hand gesture (OpenCV) detection algorith, | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 8 | ImageProcessingSettingsDialog.cpp/ImageProcessingSettingsDialog.h | Settings of parameters used by image processing algorithms. | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 9 | main.cpp | main function | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 10 | MainWindow.cpp/MainWindow.h | | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 11 | MatToQImage.cpp/MatToQImage.h | Conversion from OpenCV Mat object to QT QImage object | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 12 | ProcessingThread.cpp/ProcessingThread.h | Main processing thread, frame rate dynamics, invokes variois image processing algorithms | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 13 | SharedImageBuffer.cpp/SharedImageBuffer.h | | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 14 | WaveDisplayWidget.cpp/WaveDisplayWidget.h | Wave surface 3D rendering (invokes methods from GeometryEngine.cpp) | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 15 | WaveSimulationThread.cpp/WaveSimulationThread.h | Wave surface physical simulation thread - host side of OpenCL dispatch. | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 16 | Buffers.h | | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 17 | Structures.h | | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 18 | Config.h | | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 19 | phillips.cl | DSP OpenCL phillips spectrum generation kernels and 2D IFFT kernel (invoking dsplib.ae66 optimized 1D FFT). After compilation (by clocl) phillips.dsp\_h is generated, and included in WaveSimulationThread.cpp (ocl kernels are compiled and downloaded in this thread, before run-time operation is started). | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 20 | vshader.glsl | Vertex shader (gets projection matrix, position and texture position as input arguments; generates texture coordinate and height for fragment shader | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 21 | fshader.glsl | Fragment shader doing linear interpolation of textures and mixing texture with height dependent color, and adds ambient light | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 22 | shaders.qrc | Specify shader filenames | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 23 | textures.qrc | Specify texture file (2D block which is linearly interpolated in fragment shader, using position arguments provided by vertex shader) | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 24 | qt-opencv-multithreaded.pro | Top level QT make file: phi | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 25 | ImageProcessingSettingsDialog.ui | User interface definition file for modification of algorithm parameters. | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 26 | CameraView.ui | Camera view user interface definition file - right click mouse action brings up image processing algorithm selection | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 27 | CameraConnectDialog.ui | | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 28 | MainWindow.ui | | -+------+---------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -| - -.. rubric:: Performance - :name: performance - -The hand gesture detection/wave surface simulation/wave surface -rendering demo pipeline runs at 18-20 fps. For other algorithms (e.g. -smoothing, canny) the pipeline runs at 33-35 fps. - -.. rubric:: Licensing - :name: licensing - -The demo code is provided under BSD/MIT License - -.. rubric:: FAQ/Known Issues - :name: faqknown-issues - -- Brighter lighting conditions are necessary for noise-free camera - input, to allow good contour detection. In poor lighting conditions, - there would be false or no detection. -- OpenCV 3.1 version shows low FPS rate for Camera Capture. Hence, a - custom solution based on direct V4L2 ioctl() calls is adopted - (cameraGrab.cpp file) to boost the FPS - diff --git a/source/linux/Examples_and_Demos/_AM335x_Power_Management_User_Guide.rst b/source/linux/Examples_and_Demos/_AM335x_Power_Management_User_Guide.rst deleted file mode 100644 index ace60e788..000000000 --- a/source/linux/Examples_and_Demos/_AM335x_Power_Management_User_Guide.rst +++ /dev/null @@ -1,306 +0,0 @@ -.. http://processors.wiki.ti.com/index.php/AM335x_Power_Management_User_Guide - -AM335x Power Management User Guide ------------------------------------- - -.. rubric:: Overview - :name: overview-am335x-pm - -This article provides a description of the example applications under -the Power page of the Matrix application that comes with the Sitara -SDK. This page is labled "Power" in the top-level Matrix GUI. The -location of the Power icon on the main Matrix app list may be different -than shown here, depending on screen size. (Screen shots from SDK 06.00) - -| - -.. Image:: /images/Matrix_app_launcher.png - -| - -| PLEASE NOTE: cpufreq may cause I2C lockups on AM335x EVM boards. - Beaglebone is not affected. This is a known issue related to the CPLD - firmware. If the CPLD firmware on your EVM is detected to be the wrong - version, the Matrix application output will inform you of the version - mismatch and continue. -| Once updated CPLD firmware is available, this documentation will be - updated to teach users how to upgrade their CPLD if necessary/desired. - This procedure will require an Altera programming pod. - -.. rubric:: Power Examples - :name: power-examples - -Several power examples exist to provide users the ability to dynamically -switch the CPU clock frequency. The frequencies shown are those -available for your system. Upon making a selection, you will be -presented a confirmation page. The readout number "BogoMIPS" will -confirm the new clock frequency. Please note that the frequency will -read out with a slight margin compare to the intended frequency. For -example, if you select 1GHz, you may see a number like 998.84 (in MHz). -This is normal. After reviewing the confirmation page, press the Close -button to return to normal Matrix operation. - -Other power examples are provided which may be useful for power -management developers and power users. These have been included in -Matrix in part to make users aware that these valuable debugging tools -exist, in addition to the convenience of executing each application from -the GUI. In depth descriptions for each application follow. Similar -descriptions are also given via description pages in Matrix, which will -be displayed when clicking the button. Where appropriate, the -documentation will point out the corresponding command line operation. - -The Suspend/Resume button demonstrates the ability to put the machine -into a suspended state. See below for complete documentation of this -feature. - -Please note that the order of applications which appear on your screen -may differ from the picture below, due to devices with different screen -sizes, and differences between different versions of Matrix. Screen shot -is from SDK 06.00. - -| - -.. Image:: /images/AM335x_Power_screen.png - -| - -.. rubric:: Set Frequency - :name: set-frequency - -This command opens up another screen from which you choose the frequency -based on the available frequencies on the board. Here is a picture of -the screen you will see: - -| - -.. Image:: /images/AM335x_matrix_set_frequency.png - -| - -The following are the Linux command line equivalents for selecting the -operating frequency. Please note that changing the frequency also -changes the MPU voltage accordingly. The commands are part of the -"cpufreq" kernel interface for selecting the OPP (operating performance -point). Cpufreq provides an opportunity to save power by -adjusting/scaling voltage and frequency based on the current cpu load. - -:: - - (command line equivalent) - cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies - (view options, select one for next step) - echo > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed - cat /proc/cpuinfo - -.. rubric:: Suspend/Resume - :name: suspendresume - -:: - - (command line equivalent) - mkdir /debug - mount -t debugfs debugfs /debug - echo mem > /sys/power/state - -| This command sequence will put the platform into suspend mode. The - final command initiates the suspend. - -| IMPORTANT NOTE: When running this from Matrix, the system will only - properly resume if the user sends a keypress to the UART. If the user - presses the touchscreen or a button on the EVM, resume will not - complete normally. This issue will be fixed in a future release. If - you run these commands from the terminal - all of the normal wakeup - events (UART keypress, touchscreen press, EVM keypad press) will - operate correctly. - -.. rubric:: SmartReflex - :name: smartreflex - -SmartReflex is an active power management technique which optimizes -voltage based on silicon process ("hot" vs. "cold" silicon), -temperature, and silicon degradation effects. In most cases, SmartReflex -provides significant power savings by lowering operating voltage. - -On AM335x, SmartReflex is enabled by default in Sitara SDK releases -since 05.05.00.00. Please note that the kernel configuration menu -presents two options: "AM33XX SmartReflex support" and "SmartReflex -support". For AM33XX SmartReflex, you must select "AM33XX SmartReflex -support", and ensure that the "SmartReflex support" option is disabled. -The latter option is intended for AM37x and OMAP3 class devices. - -The SmartReflex driver requires the use of either the TPS65217 or -TPS65910 PMIC. Furthermore, SmartReflex is currently supported only on -the ZCZ package. Please note that SmartReflex may not operate on AM335x -sample devices which were not programmed with voltage targets. To -disable SmartReflex, type the following commands at the target terminal: - -:: - - mkdir /debug - mount -t debugfs debugfs /debug - cd /debug/smartreflex ==> NOTE: You may not see 'smartreflex' node if you have early silicon. In this case SmartReflex operation is not possible. - echo 0 > autocomp - (Performing "echo 1 > autocomp" will re-enable SmartReflex) - -On AM335x, to compile SmartReflex support out of the kernel, follow this -procedure to modify the kernel configuration: - -:: - - cd - make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig - - Select "System Type" - Select "TI OMAP Common Features" - Deselect "AM33xx SmartReflex Support" - Select "Exit" until you are prompted to save the configuration changes, and save them. - Rebuild the kernel. - -.. rubric:: Dynamic Frequency Scaling - :name: dynamic-frequency-scaling - -This feature, which can be enabled via patch to the SDK, enables scaling -frequency INDEPENDENT of voltage. It is also referred to as DFS (as in -DVFS without the 'V'). - -`Media:0001-Introduce-dynamic-frequency-scaling.patch `__ - -.. rubric:: Discussion - :name: discussion - -Certain systems are unable to scale voltage, either because they employ -a fixed voltage regulator, or use the ZCE package of AM335x. Without -being able to scale voltage, the power savings enabled via DVFS are -lost. This is because the current version of the omap-cpufreq driver -requires a valid MPU voltage regulator in order to operate. The purpose -of this DFS feature is to enable additional power savings for systems -with these sort of limitations. - -When using the ZCE package of AM335x, the CORE and MPU voltage domains -are tied together. Due to Advisory 1.0.22, you are not allowed to -dynamically modify the CORE frequency/voltage because the EMIF cannot -support it. However, to achieve maximum power savings, it may still be -desirable to use a PMIC which supports dynamic voltage scaling, in order -to use Adaptive Voltage Scaling (aka SmartReflex or AVS). This -implementation of DFS does not affect the ability of AVS to optimize the -voltage and save additional power. - -.. rubric:: Using the patch - :name: using-the-patch - -The patch presented here has been developed for and tested on the SDK -05.07. It modifies the omap-cpufreq driver to operate without requiring -a valid MPU voltage regulator. From a user perspective, changing -frequency via cpufreq is accomplished with exactly the same commands as -typical DVFS. For example, switching to 300 MHz is accomplished with the -following command: - -:: - - echo 300000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed - -After applying the patch, the user must modify the kernel defconfig in -order to enable the DFS feature. You should also configure the "Maximum -supported DFS voltage" (shown below) to whatever the fixed voltage level -is for your system, in microvolts. For example, use the value 1100000 to -signify 1.1V. The software will use the voltage level that you specify -to automatically disable any Operating Performance Points (OPPs) which -have voltages above that level. - -On AM335x, first apply the patch, then follow this procedure to modify -the kernel configuration: - -:: - - cd - make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig - - Select "System Type" - Select "TI OMAP Common Features" - Select "Dynamic Frequency Scaling" - Configure "Maximum supported DFS voltage (in microvolts)" (default is 1100000, or 1.1V) - Select "Exit" until you are prompted to save the configuration changes, and save them. - Rebuild the kernel. - -.. rubric:: Power Savings - :name: power-savings - -- Tested on a rev 1.2 EVM, running Linux at idle. -- The delta between power consumption at 300MHz and 600MHz, with - voltage unchanged, is approximately 75mW. - -.. rubric:: Static CORE OPP 50 - :name: static-core-opp-50 - -Configuring the AM335x system to CORE OPP50 frequency and voltage is an -advanced power savings method that can be used, provided that you -understand the tradeoffs involved. - -This patch, which was developed against the u-boot source tree from the -SDK 05.07, configures the bootloader to statically program the system to -CORE OPP50 voltage (0.95V) and frequencies. It also configures the MPU -to OPP50 voltage (0.95V) and frequency (300MHz). DDR2 is configured with -optimized timings to run at 125MHz. - -Apply the following patch to your u-boot source tree and rebuild both -MLO and u-boot.img. (Refer to -`AM335x\_U-Boot\_User's\_Guide#Building\_U-Boot `__) - -`Media:0001-Static-CORE-OPP50-w-DDR2-125MHz-MPU-300MHz.patch `__ - -.. rubric:: Caveats - :name: caveats - -- According to section 5.5.1 of the AM335x datasheet, operation of the - Ethernet MAC and switch (CPSW) is NOT supported for CORE OPP50. - -- Note that MPU OPP50 operation is not supported for the 1.0 silicon - revision (silicon errata Advisory 1.0.15). - -- Also be aware of Advisory 1.0.24, which states that boot may not be - reliable because OPP100 frequencies are used by ROM at OPP50 - voltages. - -- DDR2 memory must be used (as on the AM335x EVM up to rev 1.2). DDR2 - memory timings must be modified to operate at 125MHz. - -.. rubric:: Power Savings - :name: power-savings-1 - -- On an EVM (rev 1.2), active power consumption when Linux is idle for - CORE and MPU rails was measured at 150mW. Using the out-of-the-box - SDK at OPP100 (MPU and CORE), the comparable figure is 334mW. -- Further savings are possible by disabling Ethernet drivers in the - Linux defconfig. Refer to - `AM335x\_CPSW\_(Ethernet)\_Driver's\_Guide#Driver\_Configuration `__ - and disable "Ethernet driver support" to acheive additional power - savings. - -.. rubric:: Power Management Reference - :name: power-management-reference - -- `AM335x Linux Power Management User - Guide `__ - -Refer to this page for Linux specific information on AM335x devices. - -- `AM335x Power Estimation - Tool `__ - -The Power Estimation Tool (PET) provides users the ability to gain -insight in to the power consumption of select Sitara processors. - -- `AM335x Power Consumption - Summary `__ - -This document discusses the power consumption for common system -application usage scenarios for the AM335x ARM® Cortex™-A8 -Microprocessors (MPUs). - -- `AM335x Power Management Standby User's - Guide `__ - -Standby for AM335x is a inactive (system suspended) power saving mode in -which the power savings achieved would be lesser than that achieved -through DeepSleep0 mode but with lesser resume latency and additional -wake-up sources. diff --git a/source/linux/Examples_and_Demos/_Camera_Users_Guide.rst b/source/linux/Examples_and_Demos/_Camera_Users_Guide.rst deleted file mode 100644 index 0022439a7..000000000 --- a/source/linux/Examples_and_Demos/_Camera_Users_Guide.rst +++ /dev/null @@ -1,314 +0,0 @@ -.. http://processors.wiki.ti.com/index.php/Camera_Users_Guide - -Camera Users Guide -==================== - -.. rubric:: Introduction - :name: introduction - -This users guide provides an overview of camera loopback example -integrated in matrix application on AM37x platform. This application can -be executed by selecting the "Camera" icon at the top-level matrix. - -| - -.. Image:: /images/Main_screen.png - -| - -.. rubric:: Supported Platforms - :name: supported-platforms-camera-ug - -- AM37x - -| - -.. rubric:: Camera Loopback Example - :name: camera-loopback-example - -Camera example application demonstrates streaming of YUV 4:2:2 parallel -data from Leopard Imaging LI-3M02 daughter card with MT9T111 sensor on -AM37x EVM. Here, driver allocated buffers are used to capture data from -the sensor and display to any active display device (LCD/DVI/TV) in VGA -resolution (640x480). - -Since the LCD is at inverted VGA resolution video buffer is rotated by -90 degree. Rotation is enabled using the hardware rotation engine called -Virtual Rotated Frame Buffer (VRFB), VRFB provides four virtual frame -buffers: 0, 90, 180 and 270. For statically compiled drivers, VRFB -buffer can be declared in the bootloader. In this example, data is -displayed through video1 pipeline and -"omap\_vout.vid1\_static\_vrfb\_alloc=y" bootargument is included in the -bootargs. - -.. rubric:: Sensor Daughter card - :name: sensor-daughter-card - -Smart sensor modules have control algorithms such as AE, AWB and AF are -implemented in the module. Third parties like Leopard Imaging and E-Con -Systems provide smart sensor solutions for OMAP35x/AM37x Rev G EVM and -Beagle Board. SDK 5.02 integrates support for LI-3M02 daughter card -which has MT9T111 sensor, the sensor is configured in 8-bit YUV4:2:2 -mode. `Leopard -Imaging `__ -daughter card LI-3M02 can be ordered from their website. - -For additional support on daughter cards or sensor details please -contact the respective third parties - -- `Leopard Imaging `__ - -Contact: support@leopardimaging.com - -- `E-Con Systems `__ - -Contact: `Harishankkar `__ - -.. rubric:: Connectivity - :name: connectivity - -+----------------------+-----------------------------------------+------------+-----------+ -| OMAP35xx/AM/DM37xx | Signal Description | Comment | IO Type | -+----------------------+-----------------------------------------+------------+-----------+ -| cam\_hs | Camera Horizontal Sync | | IO | -+----------------------+-----------------------------------------+------------+-----------+ -| cam\_vs | Camera Vertical Sync | | IO | -+----------------------+-----------------------------------------+------------+-----------+ -| cam\_xclka | Camera Clock Output a | Optional | O | -+----------------------+-----------------------------------------+------------+-----------+ -| cam\_xclkb | Camera Clock Output b | Optional | O | -+----------------------+-----------------------------------------+------------+-----------+ -| cam\_[d0:12] | Camera/Video Digital Image Data | | I | -+----------------------+-----------------------------------------+------------+-----------+ -| cam\_fld | Camera Field ID | Optional | IO | -+----------------------+-----------------------------------------+------------+-----------+ -| cam\_pclk | Camera Pixel Clock | | I | -+----------------------+-----------------------------------------+------------+-----------+ -| cam\_wen | Camera Write Enable | Optional | I | -+----------------------+-----------------------------------------+------------+-----------+ -| cam\_strobe | Flash Strobe Contrl Signal | Optional | O | -+----------------------+-----------------------------------------+------------+-----------+ -| cam\_global\_reset | Global Reset - Strobe Synchronization | Optional | IO | -+----------------------+-----------------------------------------+------------+-----------+ -| cam\_shutter | Mechanical Shutter Control Signa | Optional | O | -+----------------------+-----------------------------------------+------------+-----------+ - -LI-3M02 daughter card is connected to the 26-pin J31 connector on the -EVM. 24MHz oscillator on the LI daughter card is used to drive the -sensor device, alternatively camera clock output generated by processor -ISP block can be used to drive the sensor pixel clock. Horizontal sync -(HS) and vertical sync (VS) lines are used to detect end of line and -field respectively. Sensor data line CMOS D4:D11 are connected to the -processor D4:D11. - -.. Image:: /images/AM37xx_LI-3M02_Single_Camera_Approach.png - -**Connectivity of LI-3M02 daughter card to AM/DM37x** - -- Note: H/V signal connectivity not required for ITU-R BT.656 input - since synchronization signals are extracted from BT.656 bit stream - -.. rubric:: Media Controller Framework - :name: media-controller-framework - -SDK 5.02 includes support for media controller framework, for additional -details of media controller framework and its usage please refer the -`PSP capture driver users -guide `__ - -In order to enable streaming each links between each entity is -established. Currently only MT9T111/TV5146 => CCDC => Memory has been -validated. - -:: - - Media: Opened Media Device - Enumerating media entities - [1]:OMAP3 ISP CCP2 - [2]:OMAP3 ISP CCP2 input - [3]:OMAP3 ISP CSI2a - [4]:OMAP3 ISP CSI2a output - [5]:OMAP3 ISP CCDC - [6]:OMAP3 ISP CCDC output - [7]:OMAP3 ISP preview - [8]:OMAP3 ISP preview input - [9]:OMAP3 ISP preview output - [10]:OMAP3 ISP resizer - [11]:OMAP3 ISP resizer input - [12]:OMAP3 ISP resizer output - [13]:OMAP3 ISP AEWB - [14]:OMAP3 ISP AF - [15]:OMAP3 ISP histogram - [16]:mt9t111 2-003c - [17]:tvp514x 3-005c - Total number of entities: 17 - Enumerating links/pads for entities - pads for entity 1=(0 INPUT) (1 OUTPUT) - [1:1]===>[5:0] INACTIVE - - pads for entity 2=(0 OUTPUT) - [2:0]===>[1:0] INACTIVE - - pads for entity 3=(0 INPUT) (1 OUTPUT) - [3:1]===>[4:0] INACTIVE - [3:1]===>[5:0] INACTIVE - - pads for entity 4=(0 INPUT) - - pads for entity 5=(0 INPUT) (1 OUTPUT) (2 OUTPUT) - [5:1]===>[6:0] ACTIVE - [5:2]===>[7:0] INACTIVE - [5:1]===>[10:0] INACTIVE - [5:2]===>[13:0] ACTIVE - [5:2]===>[14:0] ACTIVE - [5:2]===>[15:0] ACTIVE - - pads for entity 6=(0 INPUT) - - pads for entity 7=(0 INPUT) (1 OUTPUT) - [7:1]===>[9:0] INACTIVE - [7:1]===>[10:0] INACTIVE - - pads for entity 8=(0 OUTPUT) - [8:0]===>[7:0] INACTIVE - - pads for entity 9=(0 INPUT) - - pads for entity 10=(0 INPUT) (1 OUTPUT) - [10:1]===>[12:0] INACTIVE - - pads for entity 11=(0 OUTPUT) - [11:0]===>[10:0] INACTIVE - - pads for entity 12=(0 INPUT) - - pads for entity 13=(0 INPUT) - - pads for entity 14=(0 INPUT) - - pads for entity 15=(0 INPUT) - - pads for entity 16=(0 OUTPUT) - [16:0]===>[5:0] ACTIVE - - pads for entity 17=(0 OUTPUT) - [17:0]===>[5:0] INACTIVE - - Enabling link [MT9T111]===>[ccdc] - [MT9T111]===>[ccdc] enabled - Enabling link [ccdc]===>[video_node] - [ccdc]===>[video_node] enabled - - Capture: Opened Channel - successfully format is set on all pad [WxH] - [640x480] - Capture: Capable of streaming - Capture: Number of requested buffers = 3 - Capture: Init done successfully - - - Display: Opened Channel - Display: Capable of streaming - Display: Number of requested buffers = 3 - Display: Init done successfully - - Display: Stream on... - Capture: Stream on... - -.. rubric:: AM/DM37x ISP Configuration - :name: amdm37x-isp-configuration - -ISP CCDC block should be configured to enable 8-bit YUV4:2:2 parallel -data input, the registers below provide details of ISP and CCDC -registers in this mode. - -**ISP Registers:** - -:: - - ISP_CTRL: 0x480BC040 - 29C14C - ISP_SYSCONFIG: 0x480BC004 - 2000 - ISP_SYSSTATUS: 0x480BC008 - 1 - ISP_IRQ0ENABLE: 0x480BC00C - 811B33F9 - ISP_IRQ0STATUS: 0x480BC010 - 0 - ISP_IRQ1ENABLE: 0x480BC014 - 0 - ISP_IRQ1STATUS: 0x480BC018 - 80000300 - -**CCDC Registers:** - -:: - - CCDC_PID: 0x480BC600 - 1FE01 - CCDC_PCR - 0 - CCDC_SYN_MODE: 0x480BC604 - 31000 - CCDC_HD_VD_WID: 0x480BC60C - 0 - CCDC_PIX_LINES: 0x480BC610 - 0 - CCDC_HORZ_INFO: 0x480BC614 - 27F - CCDC_VERT_START: 0x480BC618 - 0 - CCDC_VERT_LINES: 0x480BC61C - 1DF - CCDC_CULLING: 0x480BC620 - FFFF00FF - CCDC_HSIZE_OFF: 0x480BC624 - 500 - CCDC_SDOFST: 0x480BC628 - 0 - CCDC_SDR_ADDR: 0x480BC62C - 1C5000 - CCDC_CLAMP: 0x480BC630 - 10 - CCDC_DCSUB: 0x480BC634 - 40 - CCDC_COLPTN: 0x480BC63 - 0 - CCDC_BLKCMP: 0x480BC63C - 0 - CCDC_FPC: 0x480BC640 - 0 - CCDC_FPC_ADDR: 0x480BC644 - 0 - CCDC_VDINT: 0x480BC648 - 1DE0140 - CCDC_ALAW: 0x480BC64C - 0 - CCDC_REC: 0x480BC650 - 0 - CCDC_CFG: 0x480BC65 - 8800 - CCDC_FMTCFG: 0x480BC658 - 0 - CCDC_FMT_HORZ: 0x480BC65C - 280 - CCDC_FMT_VERT: 0x480BC660 - 1E0 - CCDC_PRGEVEN0: 0x480BC684 - 0 - CCDC_PRGEVEN1: 0x480BC688 - 0 - CCDC_PRGODD0: 0x480BC68C - 0 - CCDC_PRGODD1: 0x480BC690 - 0 - CCDC_VP_OUT: 0x480BC694 - 3BE2800 - CCDC_LSC_CONFIG: 0x480BC698 - 6600 - CCDC_LSC_INITIAL: 0x480BC69C - 0 - CCDC_LSC_TABLE_BA: 0x480BC6A0 - 0 - CCDC_LSC_TABLE_OF: 0x480BC6A4 - 0 diff --git a/source/linux/Examples_and_Demos/_Hands_on_with_QT.rst b/source/linux/Examples_and_Demos/_Hands_on_with_QT.rst deleted file mode 100644 index c85878f74..000000000 --- a/source/linux/Examples_and_Demos/_Hands_on_with_QT.rst +++ /dev/null @@ -1,1479 +0,0 @@ -.. http://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_Hands_on_with_QT -.. _hands-on-with-qt: -.. rubric:: Introduction - :name: introduction-hands-on-qt - -This lab is going to give you a hands on tutorial on QT, the GUI -devolpment tool, which is a component of the Sitara SDK. Each of the -following sections below will walk you through a particular Lab -exercise, the key points to take away, and the step-by-step -instructions to complete the lab. The labs in this section will -utilize both a command line build approach and a IDE approach using QT -Creator. - -**Training:** - You can find the necessary code segments embedded -in the this article. You can cut and paste them from the wiki as -needed. - -**Hands On Session:** - In the vmware image, there are cheater files: -/home/sitara/QT\_Lab You can cut and paste section of code from this -file rather than have to type them in. You can find a copy here, just -right click and select "Save Target As": `File:QT -Lab.tar.gz `__ - -**NOTE:** In this guide commands to be executed for each step will be -marked in **BOLD** - -.. rubric:: Lab Configuration - :name: lab-configuration - -The following are the hardware and software configurations for this lab. -The steps in this lab are written against this configuration. The -concepts of the lab will apply to other configurations but will need to -be adapted accordingly. - -.. rubric:: - Hardware - :name: hardware - -- AM335x EVM-SK (TMDSSK3358) - `Order - Now `__ - - .. raw:: html - -
- - **NOTE** - All Sitara boards with an LCD display or HDMI/DVI out can be used - for these labs, but the steps below related to serial and ethernet - connections may differ. - - .. raw:: html - -
- -- Router connecting AM335x EVM-SK and Linux Host -- USB cable connection between AM335x EVM-SK and Linux Host using the - micro-USB connector (J3/USB0) - - .. raw:: html - -
- - **NOTE** - The AM335x EVM uses a standard DB9 connector and serial cable. New - Win7 based Host PCs may require a USB-to-Serial cable since newer - laptops do not have serial ports. Additionally, since the serial - connection is not required for these labs, you can telnet or ssh - into the target over ethernet instead of using a serial terminal for - target interaction. - - .. raw:: html - -
- -- 5V power supply (typically provided with the AM335x EVM-SK) - -.. rubric:: Software - :name: software - -- A Linux host PC configured as per the `Linux Host - Configuration `__ - page - - - **\*\*PLEASE NOTE\*\*** currently the Linux Host Configuration - page is under revision. Please download Ubuntu 14.04 rather than - Ubuntu 12.04 at this link http://releases.ubuntu.com/14.04/ - -- Sitara Linux SDK installed. This lab assumes the latest Sitara Linux - SDK is installed in /home/sitara. If you use a different location - please modify the below steps accordingly. -- SD card with Sitara Linux SDK installed. - - - For help creating a 2 partition SD card with the SDK content see - the :ref:`create\_sdcard.sh script ` page - -- QT Creator 5.7.0 installed on your Linux host. - - - You can download Qt Creator from open source distribution version - of Qt at https://download.qt.io/official_releases/qt/ - - QT will download as a .run file. Make the file executable by - running the **chmod + ** command and **./**. These - steps should launch the QT installer. - - Extract the package. Qt creator will be under Tools/Qt5.7.0 - folder. In some cases it may also be under the opt folder. Type - **cd /opt/Qt5.7.0** into the command line to locate the file. - - The labs in this wiki page is validated with Ubuntu 14.04 on 64 - bit machine. - -.. rubric:: Supported Platforms and revisions - :name: supported-platforms-and-revisions - -The following platforms are system tested to verify proper operation. - -- am335x -- am37x -- am35x -- am180x -- BeagleBoard XM - -**This current version has been validated on ti-processor-sdk version -02.00.01.07 using QT Creator 3.6.0** - -.. rubric:: LAB 1: Hello World Command Line - :name: lab-1-hello-world-command-line - -.. rubric:: Description - :name: description - -This LAB is optional, it introduces where to find QT components and -build tools in the Sitara SDK. Approximate time to complete this LAB: 15 -minutes. This section will cover the following topics - -- Introduction to build tools -- enviroment setup script -- The QT component of the Sitara SDK - - - where to find things in the Sitara SDK - -.. rubric:: Key Points - :name: key-points - -- Where in the SDK to find the build tools -- Where in the SDK to find the QT components -- How to setup your build environment -- How to utilize the above points to create a Hello World application. - -.. rubric:: Lab Steps - :name: lab-steps - -#. Connect the cables to the EVM. For details on where to connect these - cables see the **Quick Start Guide** that came with your EVM. - - #. Connect the Serial cable to provide access to the console. - #. Connect the network cable - #. Insert the SD card into the SD connector - #. Insert the power cable into the 5V power jack - -#. Power on the EVM and allow the boot process to finish. You will know - when the boot process has finished when you see the Matrix - application launcher on the LCD screen - - .. raw:: html - -
- - **NOTE** - You may be required to calibrate the touchscreen. If so follow the on - screen instructions to calibrate the touchscreen. - - .. raw:: html - -
- -#. Open a terminal window on your Linux host by double clicking the - Terminal icon on the desktop -#. The cross-compiler is located in the linux-devkit/bin directory of - the SDK installation directory. In the terminal window enter the - following commands, replacing the and fields - with the target machine you are using and the SDK version installed. - - .. raw:: html - -
- - **NOTE** - You can use TAB completion to help with this - - .. raw:: html - -
- - - **cd /home/sitara/AM335x/ti-processor-sdk-linux--/linux-devkit/sysroots/x86\_64-arago-linux/usr/bin** - - **ls** - -#. You should see a listing of the cross-compile tools available like - the one below. - - .. Image:: /images/Sitara-linux-training-cross-tools-1.png - -#. To locate the pre-built ARM libraries perform the following commands: - - - **cd /home/sitara/AM335x/ti-processor-sdk-linux--/linux-devkit/sysroots/cortexa8hf-vfp-neon-linux-gnueabi/usr/lib** - - **ls** - -#. You should now see a listing of all the libraries (some are contained - within their individual sub-directories) available as pre-built - packages within the SDK. -#. Now list only the QT libraries from the same directory by listing all - libs starting with libQt. - - - **ls libQt\*** - -#. You should see a listing of QT related libraries that can be used to - build and run QT projects. - - .. Image:: /images/Sitara_Linux_QT_library_listings_1.png - -#. You can also find out where the QT header files are located. At the - directory below are sub directories full of QT header files. - - - **cd /home/sitara/AM335x/ti-processor-sdk-linux--/linux-devkit/sysroots/cortexa8hf-vfp-neon-linux-gnueabi/usr/include/qt5** - - **ls** - -#. In order to make it easier to perform cross-compilations and ensure - linking with the proper cross-compiled libraries instead of the host - system libraries the **environment-setup** script has been created in - the linux-devkit directory. This script will configure many standard - variables such as CC to use the cross-compile toolchain, as well as - adding the toolchain to your PATH and configuring paths for library - locations. To utilize the setting provided by the environment-setup - script you will need to **source** the script. Perform the following - commands to source the environment-setup script and observe the - change in the QMAKESPEC variable: - - - **echo $QMAKESPEC** - - **source /home/sitara/AM335x/ti-processor-sdk-linux--/linux-devkit/environment-setup** - - **echo $QMAKESPEC** - -#. You should see the changes that were applied by executing the setup - script. - - .. Image:: /images/Sitara_Linux_QT_environment_setup_script.jpeg - -#. You should have observed that the QMAKESPEC variable now contains the - path to the QMAKESPEC files. Additionally your compile tools were - added. There was also another change that occurred which was that - your standard prompt changed from **sitara@ubuntu** to - **[linux-devkit]**. The purpose of this change is to make it easy to - identify when the environment-setup script has been sourced. This is - important because there are times when you DO NOT want to source the - environment-setup script. A perfect example is when building the - Linux kernel. During the kernel build there are some applications - that get compiled which are meant to be run on the host to assist in - the kernel build process. If the environment-setup script has been - sourced then the standard CC variable will cause these applications - to be built for the ARM, which in turn will cause them to fail to - execute on the x86 host system. - -#. As mentioned above sometimes it is not appropriate to source the - environment-setup script, or you only want to source it during a - particular build but not affect your default environment. The way - this is done in the SDK is to source the environment-setup script - inside of the project Makefile so that it is used only during the - build process. - -#. Take a look at the enviroment setup file to see what all is going on - there. Look through file to see where the compile tools variables - such as CC and CPP and PATH are defined. - - - **gedit /home/sitara/AM335x/ti-processor-sdk-linux--/linux-devkit/environment-setup** - -#. It is now time to build a Hello World project using QT. You need to - create two files: helloworld.cpp and helloworld.pro - - - **mkdir /home/sitara/AM335x/ti-processor-sdk-linux--/example\_applications/helloworld** - - **cd /home/sitara/AM335x/ti-processor-sdk-linux--/example\_applications/helloworld** - - **gedit helloworld.cpp** and add the following code - - .. raw:: html - -
- - **IMPORTANT** - You can find pre-written files in the in the - **/home/sitara/sitara-training-helper-files/QT\_Lab/lab1** - directory. You can just copy those files to your directory instead - of typing the contents if you want to - - .. raw:: html - -
- - `` #include `` - #include - int main(int argc, char \*\*argv) - { - QApplication app(argc,argv); - QLabel label("Hello World"); - label.show(); - return app.exec(); - } - - **gedit helloworld.pro** and add code - - .. raw:: html - -
- - **IMPORTANT** - You can find pre-written files in the in the - **/home/sitara/sitara-training-helper-files/QT\_Lab/lab1** - directory. You can just copy those files to your directory instead - of typing the contents if you want to - - .. raw:: html - -
- - ``QT += core gui widgets`` - SOURCES += helloworld.cpp - -#. Now lets use qmake to create a Makefile - - - **qmake helloworld.pro** - -#. Notice how qmake automatically generated a Makefile for us, now lets - build. - - - **make** - -#. Notice the build is using our cross-compiler-arm-linux-gnueabihf-g++ - - .. Image:: /images/Sitara_Linux_QT_make_using_cross_compile.jpeg - -#. Also notice we now have an executable, lets see what type of file we - created - - - **file helloworld** - -#. You should see something similar to the following: helloworld: ELF - 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked - (uses shared libs), for GNU/Linux 2.6.31, - BuildID[sha1]=0x8569a0956d8efffcfde68fca5c883be5fa4f1c31, not - stripped - -#. Finally lets copy the helloworld over to our target file system and - run it. - - - If you have not already done so connect with **minicom** and type - **ifconfig** to find your target's ip address - - .. raw:: html - -
- - **NOTE** - You can also get your ip address from Matrix if it is running. - **Select Settings->Network Settings** - - .. raw:: html - -
- - - On your Linux host console issue the command **scp -r helloworld - root@xx.xx.xx.xx:/home/root** replacing the xx.xx.xx.xx below with - you target's ip address. - - When asked for password, just **hit return** - - **Type yes** when asked if you would like to continue - - Move back over to your minicom window and execute it. You should - find the helloworld in your default /home/root directory on the - target. - - - **./helloworld** - -#. You should see helloworld print on the LCD panel of your target - board. - - -.. rubric:: LAB 2: QT Creator Hello World - :name: lab-2-qt-creator-hello-world - -.. rubric:: Description - :name: description-1 - -This section will cover setting up QT Creator the integrated development -environment. We start to investigate how QT Creator aids in rapid GUI -development. - -.. rubric:: Key Points - :name: key-points-1 - -- Setting up QT Creator to find your tools -- Setting up QT Creator to communicate with the target platform -- Creating hello world and run using QT Creator. - -.. rubric:: Lab Steps - :name: lab-steps-1 - -#. Source the enviroment setup file to ensure all the paths are setup - correctly. This was done in the previous section. If you already see - [linux-devkit]: as your prompt then you can skip this step. - - - **source /home/sitara/AM335x/ti-processor-sdk-linux--/linux-devkit/environment-setup** - -#. Bring up Qt Creator - - - **./home/sitara/Qt5.7.0/Tools/QtCreator/bin/qtcreator** - - .. raw:: html - -
- - **IMPORTANT** - By bringing QT Creator up manually, you will pass in the - environment setup. If you double click on the Qt Creator Icon from - the Desktop, you will not have the enviroment setup correctly and - your lab will not work later on. - - .. raw:: html - -
- -#. QT creator should be up and running now - - .. Image:: /images/Sitara_Linux_QT_qtcreator.png - -#. Now lets setup QT creator to configure qmake. From the QT creator - main menu shown above select the following: - - - **Tools -> Options...** - - On the left side vertical menubar click **Build & Run** - - Click the **Qt Versions** tab under Build & Run - - **Remove** any versions that may already exist to make sure you - start with a clean configuration - - Click **Add...** on the right - - Navigate to - **/home/sitara/AM335x/ti-processor-sdk-linux--/linux-devkit/sysroots/x86\_64-arago-linux/usr/bin/qt5** - - **Select qmake** then **click on Open** - - Double click on **Version Name** and give the Qt Version a - descriptive name such as **QT 5.5 Sitara** See image below. - - .. Image:: /images/Sitara_Linux_QT_options.jpeg - - .. raw:: html - -
- - **IMPORTANT** - Notice there is a red ! icon. Don't worry, lets add in the toolchain - next and it should change to yellow. - - .. raw:: html - -
- - - Click **Apply** to save your changes - -#. Now we will setup the toolchain - - - Click the **Compiler** tab under Build & Run - - Click **Add** in the top right and add a **GCC** - - Change the name to **arm-linux-gnueabihf-gcc**. This can be done - by editing the "Name" field. - - For Compiler Path **select Browse** - - - Navigate to - **/home/sitara/AM335x/ti-processor-sdk-linux--/linux-devkit/sysroots/x86\_64-arago-linux/usr/bin** - - Select **arm-linux-gnueabihf-gcc** and **click on open** - - Make sure to click on **Apply** to save your changes. - - .. Image:: /images/Sitara-compilerAndDebugger.jpeg - -#. Next, let’s setup the Debuggers. - - - Click the Debuggers tab under Build and Run - - Click **Add** in the top right - - Change the name to **GDB Engine**. This can be done by editing the - "Name" field. - - For Debugger Path **select Browse** - - - Navigate to - **/home/sitara/AM335x/ti-processor-sdk-linux--/linux-devkit/sysroots/x86\_64-arago-linux/usr/bin** - - Select **arm-linux-gnueabihf-gdb** and **click on open** - - Make sure to click on **Apply** to save your changes. - - .. Image:: /images/Sitara-Debugger.png - -#. Click the **Kits** tab under **Build & Run** - - - Change the name to give the device a unique name: **AM335x EVM** - - Select Device type **Generic Linux Device** instead of Desktop. - - Select Compiler **arm-linux-gnueabihf-gcc** instead of the host - gcc. - - For Debugger select **GDB Engine**. - - For QT Version select **Qt 5.5 Sitara** - - Click **Apply** to register the options. - - .. Image:: /images/Sitara-linux-kits.png - -#. Now let's setup our Target. While still in the **Tools -> Options** - menu - - - On the left side of the window, select the **Devices tab** - - In Devices: click the **Devices tab** - - Click **Add...** in the top right - - .. Image:: /images/Sitara_Linux_QT_options_add_device.png - - - Select **Generic Linux device** and click on **Start Wizard** - - .. Image:: /images/Sitara_Linux_QT_Device_Configuration_Wizard_Selection.jpeg - - - The Device Configuration Wizard Selection Dialog box comes up - - - Type in the name of the Device: **AM335x EVM** - - Type in the IP address of the Embedded Linux Device. Type the - IP address for your board, not the one shown in the screen - capture. - - .. raw:: html - -
- - **NOTE** - This is the same IP address you obtained in the previous lab - - .. raw:: html - -
- - - For Username type in **root** (Most Texas Instruments Boards - have this username) - - Make sure Authentication type is Password, but **leave the - password field blank**. - - Click **Next** - - .. Image:: /images/Sitara_Linux_options_Generic_Linux_Device_Configuration_Setup.jpeg - - - Click **Finish**. You should see that the target test passed, so - you can close that window. - - .. Image:: /images/Sitara_target_test.png - -#. Now we need to setup an SSH key so that the host can communicate with - the target - - - Still under the Devices tab click **Create New** for Private key - file - - .. Image:: /images/Sitara_Linux_QT_create_new_ssh_key.png - - - - - **Key algorithm RSA** - - Select **Key size: 1024** - - Then click **Generate and Save Key Pair...** - - .. Image:: /images/Sitara_Linux_QT_options_SSH_Key_Configuration.jpeg - - - - - Click **Do not Encrypt key file** - - .. Image:: /images/Sitara_Linux_QT_Password_for_Private_Key.jpeg - - - - - Just use the default name qtc\_id.pub and **Click Save** and - **Click Close** to close the Generate SSH Key window. - - - Under the Devices tab now click **Deploy Public Key...** - - .. Image:: /images/Sitara_Linux_QT_Deploy_Public_Key.png - - - - - Select the file just generated (should be under - /home/sitara/.ssh) - - .. raw:: html - -
- - **IMPORTANT** - You may need to right click and select **show hidden files** - - .. raw:: html - -
- - - Select the file **qtc\_id.pub** and click on **Open**, shortly - a window should show up saying "Deployment finished - sucessfully" - - .. Image:: /images/Sitara_successful_deploy.png - - - Close the window and **Click OK** to exit the Linux Devices - Window. - - .. Image:: /images/Sitara_Linux_QT_ok_to_close_devices.png - -#. Now that lets create a project build it and run it on the host - - - Select **File -> New File or Project** - - Then select **Applications** under projects then select **QT - Widgets Applicaton** on the top center - - Click on **Choose** - - .. Image:: /images/Sitara_Linux_QT_new_project.png - - - Type in the name of the project as **terminal**. We will be - building on this project in the next section. - - Change the **Create in** value to **/home/sitara** - - Click on **Next** - - .. Image:: /images/Sitarea_Linux_Qt_project_terminal.png - - - Select the desired Kit for the target system - - Click on **Next** - - .. Image:: /images/Sitara_Linux_Qt_project_kits_select.png - - - Type in **terminal** for the **Class name** - - Click **Next** - - .. Image:: /images/Sitara_Linux_QT_new_terminal_props.png - - - Select **None** under version control - - Click **Finish** - - .. Image:: /images/Sitara_Linux_Qt_project_vc_select.png - -#. Now we've setup a new project let's explore and add some code. - - - Click on **Edit** on the **left hand menubar** and look at the - project files including terminal.pro, main.cpp, terminal.cpp and - terminal.ui - - .. Image:: /images/Sitara-terminal-pro.jpeg - - - Under **Forms**, double click on **terminal.ui** This will bring - up the widget editor. - - Remove the menuBar where it says Type Here on the top of the ui - - Right click on the menuBar and select **Remove MenuBar** - - Use the same procedure to remove the statusBar at the bottom of - the ui. It is not that easy to see, but it is there and blank. - - Once again remove the ToolBar (mainToolBar). It is found at the - top of the ui and is also hard to see. - - .. Image:: /images/RemoveMenubar.png - - - Find the **label widget** in the category of *display widgets*, - **left click and drag it on to the User Interface (UI).** - - Type **Hello World!!!** into the label widget and strech out the - borders so you can see all the letters. - - .. Image:: /images/Sitara_hello_world_UI.png - -#. Now we need to check and update the build and run settings: - - - On the left side vertical menubar select **Projects** - - Select the **Build and Run** tab and select **Build** under - AM335x. - - Uncheck **Shadow build** as shown in the screenshot below: - - .. Image:: /images/Sitara_Build_settings_1.png - - - Now under the AM335x select the **Run** tab - - Under Method click **Add** and select **Add** and then **Deploy to - Remote Linux Host** - - However you see the error under the Run - secton. - - .. Image:: /images/Sitara_deploy_remote.jpeg - - - To fix the error do the following: - - - Click on **Edit** on the left side vertical bar and click on - **terminal.pro** - - Add the two lines below to the bottom of terminal.pro as shown - in the screen shot below - - .. raw:: html - -
- - **IMPORTANT** - You can find pre-written files in the in the - /home/sitara/sitara-training-helper-files/QT\_Lab/lab2 - directory. You can just copy those files to your directory - instead of typing the contents if you want to - - .. raw:: html - -
- - ``target.path += /home/root`` - INSTALLS += target - - .. Image:: /images/Sitara_add_target_loc.jpeg - - - Select **File -> Save** - - - Click on **Projects** on the left side vertical bar and you should - now see the error is gone and replaced with /home/root/terminal - - Now in the Run portion: **Select Add -> terminal (on Remote - Generic Linux Host)** - - .. Image:: /images/Sitara_remote_host.jpeg - -#. Finally we are ready to run - - - Click the **Green Arrow** on the bottom left to run the project - - .. raw:: html - -
- - **NOTE** - ti-processor-sdk-linux-<> version 02.00.00.00 and 02.00.01.07 has - dropbear package that doesn't let the QT Creator to deploy the - built image on the target board. dropbear version 2015.71 fixes - this problem and the prebuilt binary can be download from - `here `__. - Replace the /usr/sbin/dropbearmulti on target board filesystem - with the downloaded 2015.71 dropbearmulti binary. Change the - copied file mode to executable. Restart the target board. QT - Creator should be able to successfully deploy the binary now - - .. raw:: html - -
- - - If you receive the error 'g++: Command not found', navigate to - tools>options>build and run>kits. Add “linux-oe-g++” to the “Qt - mkspec” text box - - .. Image:: /images/CompileErrorFix.PNG - - - Save all files if asked - - .. Image:: /images/Sitara-linux-Terminal-hello.jpeg - -#. Extra Investigation: - - - From minicom: run **top** on the target while helloworld is - running. Check out CPU utilization and memory utilization for this - simple app. - - See how much memory is used by helloworld by itself, you may need - to kill matrix **/etc/init.d/matrix-gui-2.0 stop** - - -.. rubric:: LAB 3: Terminal project - :name: lab-3-terminal-project - -.. rubric:: Description - :name: description-2 - -This section shows how you can use QT Creator to create a GUI from -scratch. - -.. rubric:: Key Points - :name: key-points-2 - -- Adding widgets to a an User Interface (ui). -- Adding code to make the widgets do something meaningful. - -.. rubric:: Lab Steps - :name: lab-steps-2 - -#. We will continue on from the previous lab using the terminal project - you created. First we will remove the Hello world widget and resize - the ui. - - - Click **terminal.ui** to bring up design mode. - - Click the **Hello World widget**, and **delete it** making the ui - empty and clean - -#. This next action is mainly for those with small displays, but will - not adversely affect larger displays. - - - **Select the entire ui** as shown below. - - **Edit the Geometry values to Width = 440 and Height = 230** as - shown. - - .. Image:: /images/Sitara-Linux_QT_Resize_screen.png - -#. Next we will add the Tab Widget. Just like the label widget, drag it - over to the ui. - - .. Image:: /images/Sitara_tab_widget.png - - - Select the tab widget layout. Currently, the tab widget is part of - our ui, but it is just sitting at fixed location where we dragged - it. - - - On the upper right side right click on the **terminal QWidget - and select Lay Out -> Lay Out Vertical** as shown below - - .. Image:: /images/Sitara_layout_vertically.png - - - Now the tab widget should completely fill the ui. - -#. Now let's ad - - - Two **Push Button Widgets** - - One **Text Browser widget** - - One **Line Edit widget.** - - - **Drag all of them up to the ui** - - - Now lets set the TabWidget layout like we did with the terminal - widget - - - Right click on the upper right **QtabWidget -> Lay Out -> Lay - Out in a Grid** - - Move them around so they look somewhat like the screen shot - below - - .. Image:: /images/Sitara_ui_layout.jpeg - -#. Lets Rename the Push Button widgets. - - - Double click on the **PushButton text** in the ui - - Edit the upper push button to say **Send CMD** - - Edit the lower push botton to say **Exit** - - Depending on how the grid layout worked for you, lets stretch out - the Text Browser widget and the bottom Push Button widget to take - up the whole screen horizontally if needed. - - - Just click on the widget and **drag the border to fill the - screen** See screen shot below: - - .. Image:: /images/Sitara_adjust_widths.png - -#. Now lets give our widget objects a unique name. - - - Select the **Text Browser widget** - - Go over to properties on the bottom right and edit **ObjectName** - - - Add the text **\_linuxshell** to the end of the textBrowser - name as shown below: - - .. Image:: /images/Sitara_rename_objects.jpeg - -#. Now create unique names for the other 3 widgets. - - - For lineEdit: **lineEdit\_commandline** - - For the Send CMD push button: **pushButton\_sendcmd** - - For exit push button: **pushButton\_exit** - -#. We are not done yet, but for fun lets run this application and see - what it looks like on the target. - - - **Push the Green Arrow** at the bottom left to launch on the - target. Save all files if asked. - - .. raw:: html - -
- - **IMPORTANT** - You can not start a new application on the target if your previous - one is still running. To exit, push the "X" on the menubar at the - top right of your target. - - .. raw:: html - -
- - .. raw:: html - -
- - **NOTE** - It should appear just as we designed it, but pushing the buttons - has no effect because we haven't added any code yet. - - .. raw:: html - -
- -#. Now we are going to add code to make the buttons do what we wish them - to do. - - - Right click on the **Exit widget -> Go to slot** - - .. Image:: /images/Sitara_goto_slot.jpeg - - - In the **Go to Slot selector**, select the first selection - **clicked()** and hit OK - -#. Notice this pops you over to your terminal.cpp file where some code - has been automatically added for you. - - .. raw:: html - -
- - **IMPORTANT** - The code additions below can also be found in the - **/home/sitara/sitara-training-helper-files/QT\_Lab/lab3** directory - and can be copied into your project - - .. raw:: html - -
- - - Add the following line of code to - **on\_pushButton\_exit\_clicked()** - ``qApp->quit();`` - - .. Image:: /images/Sitara_pushbutton.png - -#. Now repeat the same process you did for the exit button on the send - CMD button. We will add code to control that button press. - - .. raw:: html - -
- - **NOTE** - You will need to go back to the ui file to do this - - .. raw:: html - -
- - - Right click on the **Send CMD widget -> Go to slot** - - In the **Go to Slot selector**, select the first selection - **clicked()** and hit OK - - Add the following line at the top of terminal.cpp to support - QProcess. - ``#include `` - - Add the following code to **on\_pushButton\_sendCmd\_clicked()** - ``QString LinuxTexttoSend = ui->lineEdit_commandline->text();`` - // QProcess used to binaries in /usr/bin - QProcess process; - // Merge Channels so the output of binaries can be seen - process.setProcessChannelMode(QProcess::MergedChannels); - // Start whatever command is in LinuxTexttoSend - process.start(LinuxTexttoSend, QIODevice::ReadWrite); - // Run the command and loop the output into a QByteArray - QByteArray data; - while(process.waitForReadyRead()) - data.append(process.readAll()); - ui->textBrowser\_linuxshell->setText(data.data()); - - .. Image:: /images/Sitara_SendCMD_code.png - -#. Finally since we don't have a keyboard to type a command lets add a - predefined command to our **line Edit Widget** like shown below: - - - Double click on the **line edit** and add the text: **date - --help** - - .. Image:: /images/Sitara_add_command.png - -#. Now run, you should see interaction with the Linux shell when you - push sendCMD. - - -.. rubric:: LAB 4: Enhancing the project with a web viewer, soft - keyboard, and Style Sheets - :name: lab-4-enhancing-the-project-with-a-web-viewer-soft-keyboard-and-style-sheets - -.. rubric:: Description - :name: description-3 - -In this section we Enhance our GUI with a web browser, soft keyboard and -style sheets. - -.. rubric:: Key Points - :name: key-points-3 - -- Adding a Web view. -- Adding a softkeyboard. -- How to adjust the look and feel - -.. rubric:: Lab Steps - :name: lab-steps-3 - -#. One of the first things we did in the Terminal Lab was to add a Tab - widget which is a container widget. So far we added a Linux shell - terminal to Tab 1, now lets add a Web View widget to Tab 2 - - - From the terminal.ui, **click on Tab 2** and notice it is empty. - - - Drag over a **QWebView widget** to Tab 2 - - Set the Layout of Tab 2 to a **vertical layout** - - .. raw:: html - -
- - **NOTE** - Do you recall how we did this on the Terminal Lab? On the top - right, right click tabWidget -> Lay Out -> Lay Out Vertically - - .. raw:: html - -
- - - When complete with the above steps, it should look like the - following: - - .. Image:: /images/Sitara_webview.jpeg - -#. Now we can add a default URL. Since we are not connected to the - internet, lets bring up matrix since it is running on a local server. - - - Select the **WebView widget** and on the bottom right find the - **url** property of **QWebView** near the bottom of the list. - - Type in: **http://localhost** - - .. Image:: /images/Sitara_default_url.png - - .. raw:: html - -
- - **NOTE** - Notice how the Webview in your ui tries to display the webpage but - can't since it is not local to your host. Some people see this - error and some do not. - - .. raw:: html - -
- -#. Now we need to add the webkit libraries to our project. - - - Go to **Edit** mode and bring up the **terminal.pro** file - - Add **webkitwidgets** as shown below - - .. Image:: /images/Sitara_webkitwidgets.png - -#. Give it a try and run it, you should see the Matrix displayed. - - .. raw:: html - -
- - **IMPORTANT** - You will need to use the **Exit** button on **Tab1** to close this - program - - .. raw:: html - -
- -#. Now lets address a couple of cosmetic issues. Notice how our new GUI - does not fill the entire screen. - - - Change over to *Edit'* mode and bring up **main.cpp**. - - Find the line **w.show()** - - - **Remove that line** - - **type w.** and notice how QT Creator will fill in all the - possible options. Also notice that when you start to type it - will jump the available options with the matching text. - - Select **w.showFullScreen();** see screen shot. - - .. Image:: /images/Sitara_fullscreen.png - -#. Now re-run and notice how it takes up the full screen. - - .. Image:: /images/Sitara_matrix.PNG - -
- - **IMPORTANT** - You will need to use the **Exit** button on **Tab1** to close this - program - - -#. Now lets fix another issue back on Tab 1. We hard coded in a default - command: **date --help** - - - Since we did not provide a keyboard, lets add a soft keyboard. - - - Download a keyboard class from this location: `Qt Keyboard - Template - wiki `__. - These instruction assume you downloaded the tarball to the - **/home/sitara** directory. - - .. raw:: html - -
- - **IMPORTANT** - If you are using a TI laptop or followed the host configuration - steps you can find these files in the - **/home/sitara/sitara-training-helper-files/QT\_Lab/keyboard** - directory and can skip these steps - - .. raw:: html - -
- - - **cd /home/sitara** - - **tar -xzvf Keyboard.tar.gz** - - - Copy the keyboard files to your terminal project directory - - - **cd /home/sitara/terminal/** - - **cp -rf /keyboard .** - - - Now lets add keyboard into our project. - - - Go to **Edit** mode and right click on **terminal -> Add - Existing Files** as shown below. - - .. Image:: /images/Sitara_addexisting.png - - - Navigate to the keyboard directory - **/home/sitara/terminal/keyboard** and add all 4 files in that - directory. - - .. Image:: /images/Sitara_addkeyboard.png - - .. raw:: html - -
- - **NOTE** - Notice how all four keyboard files are now part of the Terminal - project. Click on the **keyboard.ui** and take a look. It is - made up mainly of QPushButtons and one QLineEdit and layout - controls - - .. raw:: html - -
- - - Now we need to hook in the keyboard to the terminal GUI. - - .. raw:: html - -
- - **IMPORTANT** - As always you can find copy that you can copy into your project in - the /home/sitara/sitara-training-helper-files/QT\_Lab/lab4 - directory - - .. raw:: html - -
- - - Add some code to terminal.h - - - At the top of the file add - ``#include "keyboard/keyboard.h"`` - - In **private slots:** add - ``void open_keyboard_lineEdit();`` - - In the section **private:** add - ``Keyboard *lineEditkeyboard;`` - - .. Image:: /images/Sitara_terminal_h.png - - - Now add some code to **terminal.cpp** - - - In the function **terminal::terminal** - ``lineEditkeyboard = new Keyboard();`` - connect( ui->lineEdit\_commandline - ,SIGNAL(selectionChanged()),this - ,SLOT(open\_keyboard\_lineEdit())); - - Also add the function below to the bottom of terminal.cpp - ``void terminal::open_keyboard_lineEdit()`` - { - QLineEdit \*line = (QLineEdit \*)sender(); - lineEditkeyboard->setLineEdit(line); - lineEditkeyboard->show(); - } - - .. Image:: /images/Sitara_terminal_cpp.jpeg - -#. You are now ready to run your code. - - - Run and verify when you touch the line edit widget, that the - keyboard pops up. - - .. raw:: html - -
- - **IMPORTANT** - Depending on your screen resolution you may need to double-tap the - bar at the top of the keyboard to size it to full screen - - .. raw:: html - -
- -#. Type in a linux command such as **ps** to list the running processes - and verify that you get back the expected results. - -#. Next lets add specific colors to the GUI components using style - sheets. - - - Go back to your ui in the upper right corner: right click on the - **terminal widget -> Change styleSheet** - - .. Image:: /images/Sitara_stylesheet.jpeg - - - Cut and paste from terminal sytle sheet settings at the end of - this lab section to the Terminal stylesheet settings and Apply - them - - .. raw:: html - -
- - **IMPORTANT** - You can find this file in the - **/home/sitara/sitara-training-helper-files/QT\_Lab/lab4/style\_sheet\_terminal.txt** - file - - .. raw:: html - -
- - - Do the same thing for the Tab Widget by cutting and pasting from - the tab style sheet settings at the end of this Lab section - - .. raw:: html - -
- - **IMPORTANT** - You can find this file in the - **/home/sitara/sitara-training-helper-files/QT\_Lab/lab4/style\_sheet\_tab.txt** - file - - .. raw:: html - -
- -#. voila ... TI colors - your setup should now match the look and feel - of the one below: - - .. Image:: /images/Sitara_tabStyle.jpeg - -#. Run it! - -#. Extra investigation: Run a debug session and set break points in - keyboard.cpp. Notice how the each QPushbutton signals the - keyboardHandler slot. - - - - - .. raw:: html - -
- - **NOTE** - If breakpoints are not working for you, verify you have created a - Debug version of terminal and not a Release version. Look under - Projects and "Build Settings" and check Details under Build Steps. - - .. raw:: html - -
- -**terminal style sheet settings** - -.. code-block:: cpp - - QWidget { - background-color: rgb(0, 0, 0); - } - - QTabWidget::pane { - position: absolute; - border: 2px solid red; - } - - QTabWidget::tab-bar { - alignment: center; - } - - - QTabBar::tab { - color: red; - background-color: black; - border: 2px solid red; - border-radius: 0px; - padding: 4px; - margin-left: 0.25em; - margin-right: 0.25em; - } - - QTabBar::tab:selected, QTabBar::tab:hover { - color: white; - background: red; - } - - QPushButton { - /**font: bold 16pt; - color: white ; - - border-image: url(:/pushblueup.png); - background-color: transparent; - border-top: 3px transparent; - border-bottom: 3px transparent; - border-right: 10px transparent; - border-left: 10px transparent;**/ - } - - -**tab style sheet settings** - -.. code-block:: cpp - - QWidget{ - background-color: red; - } - - QTextBrowser{ - background-color: black; - color: yellow; - } - - QLineEdit{ - background-color: white; - color: black; - } - - QPushButton{ - } - - QWebView{ - background-color: white; - } - - -.. rubric:: LAB 5: Exploring Existing Demos and Examples - :name: lab-5-exploring-existing-demos-and-examples - -.. rubric:: Key Points - :name: key-points-4 - -- Exploring existing projects in the QT SDK. -- Using a SGX accelerated QT Demo - -.. rubric:: Lab Steps - :name: lab-steps-4 - -#. In a console window on your host: - - - **gedit /home/sitara/AM335x/ti-processor-sdk-linux--/example-applications/matrix-gui-browser-2.0/main.cpp** - - .. raw:: html - -
- - **NOTE** - This is the QT application which displays matrix for all Sitara - platforms. As you can see it uses a QWebView just like we did in - the Terminal Enhancements Lab. The main differences are that you - pass in the url as an argument, and all window framing was - removed. - - .. raw:: html - -
- -#. Now try this one using the minicom connection to your target, it may - surpise some of you: - - - **cd usr/share/qt5/examples** - - We are now in the target Filesystem provided with Sitara SDK. Lets - search for how many QT project files we can find. - - - **find . -name \*.pro** - - - There are many QT project files here - - - **find . -name \*.pro** \| wc - - - Over 300 different projects already available in the SDK. - -#. Lets take a look at one specific example **hellogl2**. This is an SGX - accelerate QT demo. In your minicom window do - - - **cd /usr/share/qt5/examples/opengl/hellogl2** - - run this **./hellogl2** - -#. You should see an SGX accelerated demo - -#. As mentioned there are many demos available. Some may not work due to - how QT was configured when it was built. - -#. Some additional demo of interest: - - #. **/usr/share/qt5/examples/webkitwidgets/browser** -- This is the - broswer demo featured in matrix. - -#. Extra Excercise: Pull in one the the demos or examples into QT - Creator by opening it as a project. Build it and run it on the - target. - - .. raw:: html - -
- - **NOTE** - You may need to do some project setup to make sure you will run - on the target - - .. raw:: html - -
- -.. rubric:: Debugging QT Libraries - :name: debugging-qt-libraries - -For debugging QT application with source code to QT libraries, -corresponding QT library will need to be installed to the -/linux-devkit/sysroots/armv7ahf-neon-linux-gnueabi -location. The \*.ipk package can be found from the -:ref:`yocto build of PSDK ` -under :file:`build/arago-tmp-external-arm-toolchain/work/armv7ahf-neon-linux-gnueabi`. -Linux "find" command can be used to refine the search for \*.ipk file. -For example, following steps to debug qtbase application - -1. Copy and install the associated ipk packages into the sysroot -directory - -# dpkg -x qtbase-dbg\_xxx\_armv7ahf-neon.ipk sysroots/armv7ahf-neon-linux-gnueabi/ - -2. Set sysroot in the QT Creator: Under Tools -> Options -> Debugger tab -of the QT Creator, go to the GDB tab and add these additional startup -commands, for example set sysroot -/home/sitara/ti-processor-sdk-linux-xxx/linux-devkit/sysroots/armv7ahf-neon-linux-gnueabi -set debug-file-directory -/home/sitara/ti-processor-sdk-linux-xxx/linux-devkit/sysroots/armv7ahf-neon-linux-gnueabi/usr/lib/.debug - -| - diff --git a/source/linux/Examples_and_Demos/_Matrix_Demos.rst b/source/linux/Examples_and_Demos/_Matrix_Demos.rst deleted file mode 100644 index 6500f4727..000000000 --- a/source/linux/Examples_and_Demos/_Matrix_Demos.rst +++ /dev/null @@ -1,39 +0,0 @@ -.. http://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Example_Applications_User%27s_Guides -.. rubric:: Applications available by development platform - :name: applications-available-by-development-platform - -There are a number of Example Applications provided within the Processor SDK for Linux. Below are the applications available on each platform and the User's Guides associated with each component. - -.. note:: - The example applications below assume that you are using the default pinmux/profile configuration that the board ships with, unless otherwise noted in the individual application's User's Guide - -| - -.. csv-table:: - :header: "Applications", "`AM335x EVM `__", "`AM335x ICE `__", "`AM335x SK `__","`BeagleBone Black `__","`AM437x EVM `__","`AM437x Starter Kit `__","`AM437x IDK `__","`AM572x EVM `__","`AM572x IDK `__","`AM571x IDK `__","`AM574x IDK `__","`AM65x EVM `__","`AM65x IDK `__","`66AK2Hx EVM `__ & `K2K EVM `__","`K2Ex EVM `__","`66AK2L06 EVM `__","`K2G EVM `__","`OMAP-L138 LCDK `__","Users Guide","Description" - - Matrix GUI,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,`Matrix User's Guide `__ ,Provides an overview and details of the graphical user interface (GUI) implementation of the application launcher provided in the Sitara Linux SDK - Power & Clocks,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,`Sitara Power Management User Guide `__ ,Provides details of power management features for all supported platforms. - Multimedia,X,,X,X,X,X,X,X,X,X,X,X,X,,,,,,`Multimedia User's Guide `__ ,Provides details on implementing ARM/Neon based multimedia using GStreamer pipelines and FFMPEG open source codecs. - Accelerated Multimedia,,,,,,,,X,X,X,X,,,X,X,X,X,,`Multimedia Training `__,Provides details on hardware accelerated (IVAHD/VPE/DSP) multimedia processing using GStreamer pipelines. - Graphics,X,,X,X,X,X,X,X,X,X,X,X,X,,,,,,`Graphics Getting Started Guide `__ ,Provides details on hardware accelerated 3D graphics demos. - OpenCL,,,,,,,,,,,,,,X,X,X,X,,`OpenCL Examples `__ ,Provides OpenCL example descriptions. Matrix GUI provides two out of box OpenCL demos: Vector Addition and Floating Point Computation. - Camera,,,,,X,X,X,X,X,X,X,,,,,,,,`Camera User's Guide `__ ,Provides details on how to support smart sensor camera sensor using the Media Controller Framework - Video Analytics,,,,,,,,,,,,,,,,,,,`Video Analytics Demo `__ ,Demonstrates the capability of AM57x for video analytics. It builds on Qt and utilizes various IP blocks on AM57x. - DLP 3D Scanner,,,,,,,,,,,,,,,,,,,`3D Machine Vision Reference Design `__ ,Demonstrates the capability of AM57x for DLP 3D scanning. - Simple People Tracking,X,,X,X,X,X,X,,,,,,,,,,,,`3D TOF Reference Design `__ ,Demonstrates the capability of people tracking and detection with TI?s ToF (Time-of-Flight) sensor - Barcode Reader,X,X,X,X,X,X,X,,,,,X,X,X,X,X,X,,`Barcode Reader `__ ,Demonstrates the capability of detecting and decoding barcodes - USB Profiler,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,NA , - ARM Benchmarks,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,NA , - Display,X,,X,,X,X,,X,X,X,X,X,X,,,,,,NA , - WLAN and Bluetooth,X,,X,,X,X,,X,,,,,,,,,,,`WL127x WLAN and Bluetooth Demos `__ ,Provides details on how to enable the WL1271 daughtercard which is connected to the EVM - QT Demos,X,,X,X,X,X,X,X,X,X,X,X,X,,,,,,`Hands on with QT `__,"Provides out of box Qt5.4 demos from Matrix GUI, including Calculator, Web Browser, Deform (shows vector deformation in the shape of a lens), and Animated Tiles." - Web Browser,X,,X,X,X,X,X,X,X,X,X,X,X,,,,,,NA , - System Settings,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,NA , - EVSE Demo,X,,X,X,X,X,X,,,,,X,X,,,,,,`HMI for EV charging infrastructure `__ ,Provides out of box demo to showcase Human Machine Interface (HMI) for Electric Vehicle Supply Equipment(EVSE) Charging Stations. - Protection Relay Demo,X,,X,X,,,,,,,,,,,,,,,`HMI for Protection Relay Demo `__,Matrix UI provides out of box demo to showcase Human Machine Interface (HMI) for Protection Relays. - mmWave Gesture Controlled HMI,X,,X,X,X,X,X,,,,,X,X,,,,,,`Gesture controlled HMI based on mmWave gesture recognition and presence detection `__ ,Provides out of box demo to showcase gesture controlled Human Machine Interface (HMI). - Predictive Maintenance (PdM) demo,X,,X,X,X,X,X,,,,,X,X,,,,,,`PdM using RNN for Anomaly Detection `__ ,Provides out of box demo for Predictive Maintenance using Recurrent Neural Network (RNN) for anomaly detection. - Qt5 Thermostat HMI Demo,X,,X,X,X,X,X,,,,,X,X,,,,,,`Qt5 Thermostat HMI Demo `__,Provides out of box Qt5-based HMI for Thermostat - TI Deep Learning,,,,,,,,,,,,,,X,X,X,X,,`TI Deep Learning Examples `__,Provides TI Deep Learning examples - Arm NN,X,X,X,X,X,X,X,X,,,,,X,,,,,,`Arm NN Examples `__,Demonstrates Arm NN classification with MobileNet model diff --git a/source/linux/Examples_and_Demos/_Matrix_User_Guide.rst b/source/linux/Examples_and_Demos/_Matrix_User_Guide.rst deleted file mode 100644 index bd8d0cb1c..000000000 --- a/source/linux/Examples_and_Demos/_Matrix_User_Guide.rst +++ /dev/null @@ -1,576 +0,0 @@ -.. http://processors.wiki.ti.com/index.php/Matrix_Users_Guide -.. rubric:: Important Note - :name: important-note - -This guide is for the latest version of Matrix that is included in -Processor SDK Linux. If you are looking for information about the old -Matrix then this can be found at the following link `**Previous Version -of -Matrix** `__\ *** -*** - -.. rubric:: Supported Platforms - :name: supported-platforms-matrix-ug - -This version of Matrix supports **all** Sitara devices, as well as -K2H/K2K, K2E, and K2L platforms. - -.. rubric:: Initial Boot Up - :name: initial-boot-up - -When you first boot up a target system which has display device attached -(e.g., AM335x, AM437x, and AM57x platforms), Matrix should be -automatically started. Matrix can be either operated by touchscreen or -mouse. Default startup for most SDK platforms is touchscreen. Should you -encounter any problems below are some tips to get everything running -smoothly. See `**Matrix Startup Debug** <#matrix-startup-debug>`__ - -When you boot up a target system without display (e.g., K2H/K2K, K2E, -and K2L platforms), Matrix will not be automatically started during -booting, and only -`Remote\_Matrix `__ -is available for use after the booting. - -.. note:: - Matrix demo does not start until XFRM netlink socket initialization is complete on the platfroms with display support. - If the Matrix demo is enabled to run during boot, an error message 'Connection Refused. Failed to load URL http://localhost' will be displayed. - Wait until 'Initializing XFRM netlink socket' message is displayed in the serial console and click on URL http://localhost to start the Matrix demo. - -| - -.. rubric:: Overview - :name: overview-matrix - -Matrix is an HTML 5 based application launcher created to highlight -available applications and demos provided in new Software Development -Kits. There are two forms of Matrix, local and remote Matrix. All of the -example applications and demos are available using either the local or -remote version. The local version launches by default when the target -system is booted and uses the target system's touchscreen interface for -user input. Matrix comes as a 4x3 matrix of icons or as a 4x2 matrix -depending on the display resolution. - -.. Image:: /images/Matrix_2_Main_Menu.png - -.. rubric:: Local and Remote Matrix - :name: local-and-remote-matrix - -.. rubric:: Local Matrix - :name: local-matrix - -Local Matrix refers to Matrix being displayed on a display device -attached to the target system. The launcher for Matrix is just a -simple QT application that displays a Webkit base browser that points -to the URL http://localhost:80 - -.. raw:: html - -
- -**NOTE** -Local matrix is not available for platforms without display support, nor -the Keystone-2 platforms, such as K2H/K2K, K2E, K2L, and K2G platforms. - -.. raw:: html - -
- -.. rubric:: Remote Matrix - :name: remote-matrix - -Remote Matrix refers to Matrix being ran in any modern day web browser -not located on the target system. - -The URL for Remote Matrix is http:// - -You can find the target's ip address by using local Matrix and clicking -on the Settings icon and then on the Network Settings icon. Or using a -terminal logged in to the target system enter the below command: - -:: - - ifconfig - -From the output displayed, look in the section that starts with eth0. -You sould see an IP address right after "inet addr". This is the IP -address you should use for remote Matrix. - -With Remote Matrix you can interact with Matrix on your PC, cellphone, -tablet, or any device with a modern web browser. You can now launch text -based applications or scripts and have the output streamed back to your -web browser! Launching a gui application from Matrix requires you to -still look at the display device connected to the target system. - -.. rubric:: Matrix Project Webpage - :name: matrix-project-webpage - -The offical website for Matrix is located at -`**gforge.ti.com/gf/project/matrix-gui-v2/** `__ Any -comments or bug reports for Matrix should be posted there. - -.. rubric:: How to Use the Matrix - :name: how-to-use-the-matrix - -Matrix is based on HTML 5 and is designed to be easily customizable. All -applications and submenus for Matrix can be found in the target system's -usr/share/matrix-gui-2.0/apps/ directory. Matrix utilizes the .desktop -standard along with some additional parameters to easily allow -modifying, adding and removing an application or directory. - -.. rubric:: Matrix Components - :name: matrix-components - -Below is a summary of all the Matrix web pages: - -.. rubric:: Menu Pages - :name: menu-pages - -- Contains all the directories or application that belongs to each - directory level. - -.. rubric:: Application Description - :name: application-description - -- Optional and associated with a particular application. -- Provide additional information which can be useful for various - reasons -- Displayed when the associated application icon is pressed. - -.. rubric:: Example Application Description Page - :name: example-application-description-page - -Below is an example application description page. Description pages can -be used to add additional information that may not be obvious. - -.. raw:: html - -
- -.. raw:: html - -
- -.. Image:: /images/Screenshot-2.png - -.. raw:: html - -
- -.. raw:: html - -
- -.. rubric:: Coming Soon Page - :name: coming-soon-page - -- Displayed for Matrix directories that doesn't contain any - applications within it. - -.. rubric:: Application/Script Execution Page - :name: applicationscript-execution-page - -- For console based application, displays the output text of the - application - -.. rubric:: Icons - :name: icons - -- 96x96 png image files which are associated to a submenu or an - application. -- Can be re-used by many applications - -.. rubric:: Applications - :name: applications - -- Any application can be launched by Matrix -- Local Matrix uses the graphics display layer. If a launched - application also uses the graphics display layer there will be a - conflict. - -.. rubric:: Updating Matrix - :name: updating-matrix - -Matrix 2 utilizes a caching system that caches the information read from -the .desktop files and also the html that is generated from the various -php pages. While this provides a substantial performance boost, -developers must be aware that any changes to the Matrix apps folder -which includes adding, deleting and modifying files can result in many -problems within Matrix. To properly update Matrix with the latest -information, Matrix's caches need to be cleared. - -.. rubric:: Automatically Clearing Matrix Cache - :name: automaticallyclearing-matrix-cache - -The simpliest way to clear Matrix's cache is to use the Refresh Matrix -application found within Matrix's Settings submenu. Simply running the -application will cause Matrix to clear all the cached files and -regenerate the .desktops cache file. Once the application is done -running, Matrix will be updated with the latest information found from -within the apps folder. - -.. rubric:: Manually Clearing Matrix Cache - :name: manually-clearing-matrix-cache - -Matrix caching system consists of 1 file and 1 directory. Within -Matrix's root directory there contains a file called json.txt. Json.txt -is a JSON file that contains information gathered from all the .desktops -located within the apps directory. This file is generated by executing -the generate.php file. - -Also located in Matrix's root directory is a folder called cache. This -folder contains all of the html files cached from the various dynamic -php webpages. - -To clear Matrix's caches you need to perform only two steps: - -1. Execute the generate.php file. - -In the terminal of the target system, enter the folllowing line of code. - -:: - - php generate.php - -or - -In a browser enter the following url. Note replace with the -IP address of the target system. - -:: - - http://:80/generate.php - -Viewing generate.php in the browser should display a blank page. There -is no visual output to this webpage. - -2. You need to clear the files located within Matrix's cache folder. -Enter the following commands. - -:: - - cd /usr/share/matrix-gui-2.0/cache - rm -r * - -Once the above steps are completed, Matrix will be updated. - -.. rubric:: Launching Matrix - :name: launching-matrix - -Use the following shell script in the target's terminal window to run -Matrix as a background task: - -:: - - /etc/init.d/matrix-gui-2.0 start - -This script ensures that the touchscreen has been calibrated and that -the Qt Window server is running. - -Alternatively, Matrix can be launched manually with this full syntax: - -:: - - matrix_browser -qws http://localhost:80 - -The “-qws” parameter is required to start the Qt window server if this -is the only/first Qt application running on the system. - -The third parameter is the URL that you want the application's web -browser to go to. http://localhost:80 points to the web server on the -target system that is hosting Matrix. - -.. rubric:: Matrix Startup Debug - :name: matrix-startup-debug - -The following topics cover debugging Matrix issue at startup or -disabling Matrix at start up. - -.. rubric:: Touchscreen not working - :name: touchscreen-not-working - -Please see this wiki page to recalibrate the touch screen: `**How to -Recalibrate the -Touchscreen** `__ - -.. rubric:: Matrix is running but I don't want it running - :name: matrix-is-running-but-i-dont-want-it-running - -#. Exit Matrix by going to the Settings submenu and running the Exit - Matrix application. Note that exiting Matrix only shuts down local - Matrix. Remote Matrix can still be used. -#. Or if the touchscreen is not working, from the console, type: - -:: - - /etc/init.d/matrix-gui-2.0 stop - - -.. rubric:: I don't want Matrix to run on boot up - :name: i-dont-want-matrix-to-run-on-boot-up - -From the console type the following commands: - -:: - - cd /etc/rc5.d - mv S97matrix-gui-2.0 K97matrix-gui-2.0 - -| This will cause local Matrix to not automatically start on boot up. - -.. rubric:: How to Enable Mouse Instead of Touchscreen for the Matrix - :name: how-to-enable-mouse-instead-of-touchscreen-for-the-matrix - -You can enable mouse by referring to the following: `**How to Enable -Mouse for the Matrix -GUI** `__\ *** -*** - -.. rubric:: How to Switch Display from LCD to DVI out for the Matrix - :name: how-to-switch-display-from-lcd-to-dvi-out-for-the-matrix - - -You can switch the display output by referring to the following: -`**How to Switch Display Output for the Matrix -GUI** `__\ *** -*** - -.. rubric:: Adding a New Application/Directory to Matrix - :name: adding-a-new-applicationdirectory-to-matrix - -Below are step by step instructions. - -#. Create a new folder on your target file system at - /usr/share/matrix-gui-2.0/apps/. The name should be a somewhat - descriptive representation of the application or directory. The - folder name must be different than any existing folders at that - location. -#. Create a .desktop file based on the parameters discussed below. It is - recommended the name of the desktop file match the name of the newly - created folder. No white spaces can be used for the .desktop - filename. The .desktop file parameters should be set depending on if - you want to add a new application or a new directory to Matrix. The - Type field must be set according to your decision. The .desktop file - must have the .desktop suffix. -#. Update the Icon field in the .desktop to reference any existing Icon - in the /usr/share/matrix-gui-2.0 directory or subdirectories. You can - also add a new 96x96 png image and place it into your newly created - folder. -#. Optionally for applications you can add a HTML file that contains the - application description into your newly created directory. If you add - a description page then update the X-Matrix-Description field in the - .desktop file. -#. Refresh Matrix using the application "Refresh Matrix" located in the - Settings submenu. - - -Run your new application from Matrix! -See reference examples below: `**Examples** <#examples>`__ - -Blank template icons for Matrix can be found here: -`**gforge.ti.com/gf/download/frsrelease/712/5167/blank\_icons\_1.1.tar.gz** `__ - -.. rubric:: Creating the .Desktop File - :name: creating-the-.desktop-file - -The .desktop file is based on standard specified at the -`**standards.freedesktop.org/desktop-entry-spec/latest/** `__ -Additional fields were added that are unique for Matrix. - -Format for each parameter: - -= - -The fields and values are case sensitive. - -.. rubric:: Examples - :name: examples - -.. rubric:: Creating a New Matrix Directory - :name: creating-a-new-matrix-directory - -You can get all the files including the image discussed below from the -following file: -`**Ex\_directory.tar.gz** `__ - -Create a directory called ex\_directory - -Create a new file named hello\_world\_dir.desktop - -Fill the contents of the file with the text shown below: - -:: - - #!/usr/bin/env xdg-open - [Desktop Entry] - Name=Ex Demo - Icon=/usr/share/matrix-gui-2.0/apps/ex_directory/example-icon.png - Type=Directory - X-MATRIX-CategoryTarget=ex_dir - X-MATRIX-DisplayPriority=5 - -This .desktop above tells Matrix that this .desktop is meant to create a -new directory since Type=Directory. The directory should be named "Ex -Demo" and will use the icon located within the ex\_directory directory. -This new directory should be the 5th icon displayed as long as there -aren't any other .desktop files that specify X-MATRIX-DisplayPriority=5 -and will be displayed in the Matrix Main Menu. Now any applications that -wants to be displayed in this directory should have their .desktop -Category parameter set to ex\_dir. - -- Note that sometimes Linux will rename the .desktop file to the name - specified in the Name field. If this occurs don't worry about trying - to force it to use the file name specified. -- If you are writing these files in Windows, be sure to use Unix-style - EOL characters - -Now move the .desktop file and image into the ex\_directory directory -that was created. - -.. rubric:: Moving the Newly created Directory to the Target's - File System - :name: moving-the-newly-createddirectory-to-the-targets-filesystem - -Open the Linux terminal and go to the directory that contains the -ex\_directory. - -Enter the below command to copy ex\_directory to -the /usr/share/matrix-gui-2.0/apps/ directory located in the target's -file system. Depending on the targetNFS directory premissions you might -have to include sudo before the cp command. - -:: - - host $ cp ex_directory ~/ti-processor-sdk-linux-[platformName]-evm-xx.xx.xx.xx/targetNFS/usr/share/matrix-gui-2.0/apps/ - -If NFS isn't being used then you need to copy the ex\_directory to -the the /usr/share/matrix-gui-2.0/apps/ directory in the target's -filesystem. - -.. rubric:: Updating Matrix - :name: updating-matrix-1 - -Now in either local or remote Matrix go to the Settings directory and -click on and then run the Refresh Matrix application. This will delete -all the cache files that Matrix generates and regenerates all the needed -files which will include any updates that you have made. - -Now if you go back to Matrix's Main Menu the 5th icon should be the icon -for your Ex Demo. - -.. rubric:: Creating a New Application - :name: creating-a-new-application - -This example is assuming that you completed the \ `**Creating a New -Matrix Directory** <#creating-a-new-matrix-directory>`__ example. - -You can get all the files including the image discussed below from the -following file: -`**Ex\_application.tar.gz** `__\ *** -*** - -Create a new directory called ex\_application - -Create a file named test.desktop - -Fill the contents of the file with the below text: - -:: - - #!/usr/bin/env xdg-open - [Desktop Entry] - Name=Test App - Icon=/usr/share/matrix-gui-2.0/apps/ex_application/example-icon.png - Exec=/usr/share/matrix-gui-2.0/apps/ex_application/test_script.sh - Type=Application - ProgramType=console - Categories=ex_dir - X-Matrix-Description=/usr/share/matrix-gui-2.0/apps/ex_application/app_desc.html - X-Matrix-Lock=test_app_lock - -Type=Application lets Matrix know that this .desktop is for an -application. The name of the application is "Test App". The -icon example-icon.png can be found within the ex\_application -directory. The command to execute is a shell script that will be located -within ex\_application. The script that is being ran is a simply shell -script that output text to the terminal. Therefore, the ProgramType -should be set to console. This application should be added to the Ex -Demo directory from the previous example. Therefore, Categories will be -set to ex\_dir which is the same value that X-MATRIX-CategoryTarget is -set to. You could optionally remove the Categories field to have this -application displayed in Matrix's Main Menu. This application will also -have a description page. The html file to be used is located within the -ex\_application directory. A lock is also being used. Therefore, any -other application including itself that has the same lock can't run -simultaneously. - -Create a file named test\_script.sh - -:: - - echo "You are now running you first newly created application in Matrix" - echo "I am about to go to sleep for 30 seconds so you can test out the lock feature if you want" - sleep 30 - echo "I am finally awake!" - -| The newly created script needs to have its permission set to be - executable. Enter the below command to give read, write and execute - permission to all users and groups for the script: - -:: - - host $ chmod 777 test_script.sh - -Create a new file called app\_desc.html - -:: - -

Test Application Overview

-

Purpose:

-

The purpose of this application is to demonstrate the ease in adding a new application to Matrix.

- -Now move the .desktop file, script file, the png image located in the -Ex\_application.tar.gz file and the html file into the ex\_application -folder. - -.. rubric:: Moving the newly created Directory to the Target System - :name: moving-the-newly-createddirectory-to-the-target-system - -Open the Linux terminal and go to the directory that contains the -ex\_application directory. - -Enter the below command to copy the ex\_application directory -to /usr/share/matrix-gui-2.0/apps/ located in the target's file system. -Depending on the targetNFS directory permissions you might have to -include sudo before the cp command. - -:: - - host $ cp ex_application ~/ti-processor-sdk-linux-[platformName]-evm-xx.xx.xx.xx/targetNFS/usr/share/matrix-gui-2.0/apps/ - -If your not using NFS but instead are using a SD card then copy -ex\_application into the /usr/share/matrix-gui-2.0/apps/ directory in -the target's filesystem. - -.. rubric:: Updating Matrix - :name: updating-matrix-2 - -Now in either local or remote Matrix go to the Settings directory and -click and then run the Refresh Matrix application. This will delete all -the cache files that Matrix generates and regenerate all the needed -files which will include any updates that you have made. - -Now if you go back to the Matrix's Main Menu and click on the Ex -Demo directory you should see your newly created application. Click on -the application's icon and you will see the application's description -page. Click the Run button and your application will execute. If you try -to run two instances of this application simultaneously via local and -remote Matrtix you will get a message saying that the program can't run -because a lock exists. Because of X-Matrix-Lock being set to -test\_app\_lock, Matrix knows not to run two instances of a -program simultaneously that share the same lock. You can run the -application again when the previous application is done running. - -You have just successfully added a new application to Matrix using all -the possibly parameters! - diff --git a/source/linux/Examples_and_Demos/_WLAN_and_Bluetooth.rst b/source/linux/Examples_and_Demos/_WLAN_and_Bluetooth.rst index ebedd2b78..3bbc5fdfc 100644 --- a/source/linux/Examples_and_Demos/_WLAN_and_Bluetooth.rst +++ b/source/linux/Examples_and_Demos/_WLAN_and_Bluetooth.rst @@ -98,14 +98,6 @@ page for more instruction. - `WLAN Throughput Test `__ -- **Web-Browsing on Matrix UI and Remote (PC Based) Web Browser (QT - GUI)** - -- `QT Web Browser - Connect to AP using Command - line `__ -- `QT Web Browser - Connect to AP using QT - GUI `__ - - **WLAN Low Power Use Case Demo (Magic Packet visibly wakes up system)** diff --git a/source/linux/Examples_and_Demos_Application_Demos.rst b/source/linux/Examples_and_Demos_Application_Demos.rst index 9bf63ddf6..6ef459c8c 100644 --- a/source/linux/Examples_and_Demos_Application_Demos.rst +++ b/source/linux/Examples_and_Demos_Application_Demos.rst @@ -6,12 +6,10 @@ Application Demos :maxdepth: 5 Examples_and_Demos/Application_Demos/Dual_Camera_Demo - Examples_and_Demos/Application_Demos/Video_Analytics Examples_and_Demos/Application_Demos/Barcode Examples_and_Demos/Application_Demos/QT_Thermostat_HMI_Demo Examples_and_Demos/Application_Demos/Optical_Flow_with_OpenVX Examples_and_Demos/Application_Demos/ROS_Radar - Examples_and_Demos/Application_Demos/PdM_Anomaly_Detection Examples_and_Demos/Application_Demos/PRU_ADC Examples_and_Demos/Application_Demos/Video_Graphics_Test Examples_and_Demos/Application_Demos/Watchdog_demo diff --git a/source/linux/Examples_and_Demos_Matrix_User_Guide.rst b/source/linux/Examples_and_Demos_Matrix_User_Guide.rst deleted file mode 100644 index f73b40b66..000000000 --- a/source/linux/Examples_and_Demos_Matrix_User_Guide.rst +++ /dev/null @@ -1,4 +0,0 @@ -********************************** -Matrix User Guide -********************************** -.. include:: Examples_and_Demos/_Matrix_User_Guide.rst diff --git a/source/linux/Examples_and_Demos_Sub-system_Demos.rst b/source/linux/Examples_and_Demos_Sub-system_Demos.rst index e5f88bab3..0323ea979 100644 --- a/source/linux/Examples_and_Demos_Sub-system_Demos.rst +++ b/source/linux/Examples_and_Demos_Sub-system_Demos.rst @@ -6,8 +6,6 @@ Power Management ================ .. include:: Examples_and_Demos/_Power_Management.rst -.. include:: Examples_and_Demos/_AM335x_Power_Management_User_Guide.rst - .. include:: Examples_and_Demos/_ARM_Multimedia_Users_Guide.rst Accelerated Multimedia @@ -18,16 +16,6 @@ Graphics and Display ==================== Refer to various SGX 3D demos and other Graphics applications at :doc:`Foundational_Components/Graphics/index` chapter. -DSP offload with OpenCL -======================= -See http://downloads.ti.com/mctools/esd/docs/opencl/examples/index.html - -.. include:: Examples_and_Demos/_Camera_Users_Guide.rst - WLAN and Bluetooth ================== .. include:: Examples_and_Demos/_WLAN_and_Bluetooth.rst - -Hands on with QT -================ -.. include:: Examples_and_Demos/_Hands_on_with_QT.rst diff --git a/source/linux/Foundational_Components/IPC/_Quick_Start_Guide.rst b/source/linux/Foundational_Components/IPC/_Quick_Start_Guide.rst deleted file mode 100644 index 77b69002e..000000000 --- a/source/linux/Foundational_Components/IPC/_Quick_Start_Guide.rst +++ /dev/null @@ -1,358 +0,0 @@ -.. http://processors.wiki.ti.com/index.php/Processor_SDK_IPC_Quick_Start_Guide -.. rubric:: Overview - :name: overview-ipc - -This page is meant to be a Quick Start Guide for applications using -IPC (Inter Processor Communication) in Processor SDK. - -It begins with details about the out-of-box demo provided in the -Processor SDK Linux filesystem, followed by rebuilding the demo code and -running the built images. ( This covers the use case with the Host -running linux OS and the slave cores running RTOS). - -Also details about building and running the IPC examples are covered. - -The goal is to provides information for users to get familiar with IPC -and its build environment, in turn, to help users in developing their -projects quickly. - -| - -.. rubric:: Linux out of box demos - :name: linux-out-of-box-demos - -The out of box demo is only available on Keystone-2 EVMs. - -.. note:: - - This assumes the release images are loaded in the - flash/SD Card. If needed to update to latest release follow the - `Linux Getting Started Guide `__ - to update the release images on flash memory/SD card on the EVM using - Program-evm or using the procedures for SD Card. - -1. Connect the EVM Ethernet port 0 to a corporate or local network - with DHCP server running, when the Linux kernel boots up, the rootfs - start up scripts will get an IP address from the DHCP server and print - the IP address to the EVM on-board LCD. -2. Open an Internet browser (e.g. Mozilla Firefox) on a remote - computer that connects with the same network as the EVM. -3. Type the IP address displayed on EVM LCD to the browser and click - cancel button to launch the Matrix launcher in the remote access mode - instead of on the on-board display device. -4. Click the Multi-core Demonstrations, then Multi-core IPC Demo to - start the IPC demonstration. - - .. Image:: /images/MatrixAppLauncher.jpg - :scale: 60 - - - The result from running IPC Demo - - .. Image:: /images/IPC_Demo_Result.jpg - :scale: 60 - - -.. note:: - - To view the out-of-box demo source code, please - install Linux and RTOS Processor SDKs from `SDK download - page `__ - -The source code are located in: - -:: - - Linux side application: /ipc_x_xx_xx_xx/linux/src/tests/MessageQBench.c - DSP side application: /ipc_x_xx_xx_xx/packages/ti/ipc/tests/messageq_single.c - -**Rebuilding the demo:** - -| -| **ARM Linux:** - -**1.** Install Linux Proc SDK at the default location - -**2.** Include cross-compiler directory in the $PATH - -:: - - export PATH=/linux-devkit/sysroots/x86_64-arago-linux/usr/bin:$PATH - -**3.** Setup TI RTOS PATH using - -:: - - export TI_RTOS_PATH= - export IPC_INSTALL_PATH= - -**4.** In Linux Proc SDK, start the top level build: - -:: - - $ make ti-ipc-linux - -**5.** The ARM binary will be located under the directory where the - source code is /ipc\_x\_xx\_xx\_xx/linux/src/tests/ - -.. note:: - - Please follow the build instruction in `Linux Kernel User Guide - `__ - to set up the build environment. - -| -| **DSP RTOS :** - -**1.** Install RTOS Proc SDK at the default location - -**2.** If RTOS Proc SDK and tools are not installed at its default - location, then the environment variables, SDK\_INSTALL\_PATH and - TOOLS\_INSTALL\_PATH need to be exported with their installed locations. - -:: - - export SDK_INSTALL_PATH= - export TOOLS_INSTALL_PATH= - -.. note:: - - For ProcSDK 3.2 or older releases, tools are not included in RTOS SDK, - so point to CCS: - -:: - - export TOOLS_INSTALL_PATH= - -**3.** Configure the build environment in - /processor\_sdk\_rtos\_\_x\_xx\_xx\_xx - directory - -:: - - $ cd /processor_sdk_rtos__x_xx_xx_xx - $ source ./setupenv.sh - -**4.** Start the top level build: - -:: - - $ make ipc_bios - -**5.** The DSP binary will be located under the directory where the - source code is - -:: - - /ipc_x_xx_xx_xx/packages/ti/ipc/tests - -| - -.. rubric:: Build IPC Linux examples - :name: build-ipc-linux-examples - -IPC package and its examples are delivered in RTOS Processor SDK, but -can be built from Linux Proc SDK. To build IPC examples, both Linux and -RTOS processor SDKs need to be installed. They can be downloaded from -`SDK download -page `__ - -To install Linux Proc SDK, please follow the instruction in `Download -and Install the SDK -`__ - -To Install RTOS Proc SDK, please see `Processor SDK for RTOS -`__ - -Once the Linux and RTOS Processor SDKs are installed at their default -locations, the IPC Linux library, not included in the Linux Proc SDK, -can be built on Linux host machine with the following commands: - -:: - - $ cd - $ make ti-ipc-linux - -The IPC examples in RTOS Proc SDK including out-of-box demo can be built -with the following commands: - -:: - - $ cd - $ make ti-ipc-linux-examples - -.. note:: - - Please follow the build instruction in `Linux Kernel User Guide - `__ - to set up the build environment. - -.. note:: - - If RTOS Proc SDK is not installed at its default - location, then the environment variables, TI\_RTOS\_PATH - needs to be exported with their installed locations. - -:: - - export TI_RTOS_PATH= - -Also if using Processor SDK 3.2 or older release, need to also set TI_CCS_PATH to CCSV6 location - -:: - - export TI_CCS_PATH=/ccsv6 - -.. rubric:: Run IPC Linux examples - :name: run-ipc-linux-examples - -1. The executables are in RTOS Proc SDK under the - ipc\_xx\_xx\_xx\_xx/examples directory. - -:: - - __elf/ex/host/bin/debug/app_host - __elf/ex/bin/debug/__elf/ex/bin/debug/`__ - for details of moving files to filesystem) - -3. Load and start the executable on the target DSP/IPU. - -For AM57x platforms, Modify the symbolic links in /lib/firmware of the -default image names to the built binaries. The images pointed by the -symbolic links will be downloaded to and started execution on the -corresponding processors by remoteproc during Linux Kernel boots. - -:: - - DSP image files: dra7-dsp1-fw.xe66 dra7-dsp2-fw.xe66 - IPU image files: dra7-ipu1-fw.xem4 dra7-ipu2-fw.xem4 - -For OMAP-L138 platform, Modify the symblic link in /lib/firmware of the -default image names to the build binary - -:: - - DSP image files: rproc-dsp-fw - -For Keystone-2 platforms, use the Multi-Processor Manager (MPM) Command -Line utilities to download and start the DSP executibles. Please refer -to /usr/bin/mc\_demo\_ipc.sh for examples - -:: - - The available commands are: - mpmcl reset - mpmcl status - mpmcl load - mpmcl run - -4. Run the example - From the Linux kernel prompt, run the host executable, app\_host. - An example from running ex02\_messageq: - -:: - - root@am57xx-evm:~# ./app_host DSP1 - -The console output: - -:: - - --> main: - --> Main_main: - --> App_create: - App_create: Host is ready - <-- App_create: - --> App_exec: - App_exec: sending message 1 - App_exec: sending message 2 - App_exec: sending message 3 - App_exec: message received, sending message 4 - App_exec: message received, sending message 5 - App_exec: message received, sending message 6 - App_exec: message received, sending message 7 - App_exec: message received, sending message 8 - App_exec: message received, sending message 9 - App_exec: message received, sending message 10 - App_exec: message received, sending message 11 - App_exec: message received, sending message 12 - App_exec: message received, sending message 13 - App_exec: message received, sending message 14 - App_exec: message received, sending message 15 - App_exec : message received - App_exec: message received - App_exec: message received - <-- App_exec: 0 - --> App_delete: - <-- App_delete: - <-- Main_main: - <-- main: - root@am57xx-evm:~# - -| - -.. rubric:: Build IPC RTOS examples - :name: build-ipc-rtos-examples - -The IPC package also includes examples for the use case with Host and -the slave cores running RTOS/BIOS. They can be built from the Processor -SDK RTOS package. - -.. note:: - - To Install RTOS Proc SDK, please follow the - instructions in `RTOS SDK Getting Started Guide - `__ - In the RTOS Processor SDK, the ipc examples are located under - /processor\_sdk\_rtos\_\_x\_xx\_xx\_xx/ipc\_/examples/\_bios\_elf. - -NOTE: The platform in the directory name may be slightly different from -the top level platform name. For example, platform name DRA7XX refer to -common examples for DRA7XX & AM57x family of processors. - -Once the RTOS Processor SDKs is installed at the default location, the -IPC examples can be built with the following commands: - -:: - - 1. Configure the build environment in - /processor_sdk_rtos__x_xx_xx_xx directory - $ cd /processor_sdk_rtos__x_xx_xx_xx - $ source ./setupenv.sh - 2. Start the top level build: - $ make ipc_examples - -.. note:: - - If RTOS Proc SDK and tools are not installed at its - default location, then the environment variables, SDK\_INSTALL\_PATH and - TOOLS\_INSTALL\_PATH need to be exported with their installed locations. - -| - -.. rubric:: Run IPC RTOS examples - :name: run-ipc-rtos-examples - -The binary images for the examples are located in the corresponding -directories for host and the individual cores. The examples can be run -by loading and running the binaries using CCS through JTAG. - -.. rubric:: Build your own project - :name: build-your-own-project - -After exercising the IPC build and running examples, users can take -further look at the source code of the examples as references for their -own project. - -The sources for examples are under -ipc\_xx\_xx\_xx\_xx/examples/\_\_elf directories. Once -modified the same build process described above can be used to rebuild -the examples. - diff --git a/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_CCS_Compiling.rst b/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_CCS_Compiling.rst index 68e102139..635c9d2ce 100644 --- a/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_CCS_Compiling.rst +++ b/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_CCS_Compiling.rst @@ -32,10 +32,7 @@ See this link to meet the above requirements: Although the Processor Linux SDK includes several Qt example applications using Code Composer Studio to build or debug these applications isn't recommended. QT Creator is the official IDE designed -to be used when developing or debugging Qt applications.Please reference -to the following link for further information on all the basic to -download, install, run, and debug QT applications: `Hands on with -Qt `__ +to be used when developing or debugging Qt applications. | diff --git a/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_CCS_Installation.rst b/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_CCS_Installation.rst index c417f4387..f841d1a38 100644 --- a/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_CCS_Installation.rst +++ b/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_CCS_Installation.rst @@ -292,9 +292,7 @@ After opening CCS with a new workspace: #. The *Projects:* list will now be populated with the projects found. #. Uncheck the following projects. They are Qt projects and are imported - using a different method. For more information, see the :ref:`Hands on - with QT ` - training. + using a different method. - matrix\_browser - refresh\_screen diff --git a/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_Remote_Explorer_Setup_with_CCS.rst b/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_Remote_Explorer_Setup_with_CCS.rst index 2994d651c..834dbb26f 100644 --- a/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_Remote_Explorer_Setup_with_CCS.rst +++ b/source/linux/Foundational_Components/Tools/Code_Composer_Studio/_Remote_Explorer_Setup_with_CCS.rst @@ -23,8 +23,7 @@ prerequisites are met: should be on the same subnet. #. Know the IP of your evm. - - You can obtain the IP address of the EVM using matrix and - selecting **Settings -> Network Settings** or by connecting over + - You can obtain the IP address of the EVM by connecting over the serial console and using the **ifconfig** command. .. rubric:: Opening the Remote System Explorer Perspective diff --git a/source/linux/Foundational_Components/_IPC.rst b/source/linux/Foundational_Components/_IPC.rst index b2b77186e..81ea339bc 100644 --- a/source/linux/Foundational_Components/_IPC.rst +++ b/source/linux/Foundational_Components/_IPC.rst @@ -8,12 +8,6 @@ Overview .. include:: Foundational_Components/IPC/_IPC_Overview.rst -********************* -IPC Quick Start Guide -********************* - -.. include:: Foundational_Components/IPC/_Quick_Start_Guide.rst - ************** IPC for AM57xx ************** diff --git a/source/linux/Foundational_Components_Multimedia_IVAHD.rst b/source/linux/Foundational_Components_Multimedia_IVAHD.rst index 62ff25071..75f309046 100644 --- a/source/linux/Foundational_Components_Multimedia_IVAHD.rst +++ b/source/linux/Foundational_Components_Multimedia_IVAHD.rst @@ -74,31 +74,6 @@ capabilities. | -.. rubric:: Multimedia Demos Available via Matrix - :name: multimedia-demos-available-via-matrix - -The following Multimedia demos are available via Matrix on AM57xx EVM -(X15 board with LCD). The table below provides a list of these demos, -with a brief description. - -+-----------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| **Demo Name** | **Details** | -+-----------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| IVAHD H264 Decode | This demo runs a gstreamer playbin pipeline to decode H264 using IVAHD. The demo plays back audio as well and you can listen if speakers are connected. | -+-----------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| IVAHD H264 Encode | This demo runs a gstreamer pipeline to do H264 encoding on IVAHD. The input clip is in NV12 format. The output is saved to /home/root directory | -+-----------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| AAC Decode | This demo runs a gstreamer playbin pipeline for ARM audio decoding and playout. | -+-----------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| H.265 (HEVC) Decode | This demonstrates HEVC decoding on ARM. The gstreamer pipeline decodes and display an H265 stream. | -+-----------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| VIP VPE IVAHD MPEG4 Encode and Decode | This demonstrates video capture via Video Input Port (VIP), color space conversion and scaling with Video Processing Engine (VPE), IVAHD MPEG4 encoding, IVAHD MPEG4 decoding and display | -+-----------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| DSP C66 Image Processing | This demonstrates the use of DSP C66x plugin (dsp66videokernel) for offloading image processing tasks to DSP. | -+-----------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - -| - .. rubric:: Software Stack of Accelerated Codec Encoding/Decoding :name: software-stack-of-accelerated-codec-encodingdecoding diff --git a/source/linux/How_to_Guides/Host/AM335x_AM437x_Hardware_Migration_Guide.rst b/source/linux/How_to_Guides/Host/AM335x_AM437x_Hardware_Migration_Guide.rst index 921d6588f..d8c38be08 100644 --- a/source/linux/How_to_Guides/Host/AM335x_AM437x_Hardware_Migration_Guide.rst +++ b/source/linux/How_to_Guides/Host/AM335x_AM437x_Hardware_Migration_Guide.rst @@ -1025,4 +1025,4 @@ Software Migration Guide .. Image:: /images/am335_437_sw_stack.png :scale: 120 % -As seen by the above image, the user application sits on top of the software stack. In order for a user to develop an application, one does not need to know about the Linux Kernel implementation. Once the Linux system is up and running, user application could start executing its desired tasks. Therefore, an application written on AM335x should work on AM437x without any modifications. For example, users could take the “Hello World” Qt `example <../../Examples_and_Demos_Sub-system_Demos.html#hands-on-with-qt>`__, build it for AM335x and execute it on AM437x. Please keep in mind that this will only work if common IP exists between AM437x and AM335x. The dual camera `example `__ will not function properly on AM335x because the VPFE IP is not present on AM335x. +As seen by the above image, the user application sits on top of the software stack. In order for a user to develop an application, one does not need to know about the Linux Kernel implementation. Once the Linux system is up and running, user application could start executing its desired tasks. Therefore, an application written on AM335x should work on AM437x without any modifications. Please keep in mind that this will only work if common IP exists between AM437x and AM335x. The dual camera `example `__ will not function properly on AM335x because the VPFE IP is not present on AM335x. diff --git a/source/linux/How_to_Guides/Target/How_to_Recalibrate_the_Touchscreen.rst b/source/linux/How_to_Guides/Target/How_to_Recalibrate_the_Touchscreen.rst deleted file mode 100644 index e57d4b0d6..000000000 --- a/source/linux/How_to_Guides/Target/How_to_Recalibrate_the_Touchscreen.rst +++ /dev/null @@ -1,119 +0,0 @@ -.. http://processors.wiki.ti.com/index.php/How_to_Recalibrate_the_Touchscreen - -How to Recalibrate the Touchscreen -=================================== - -.. rubric:: Non-Weston based Graphic System - :name: non-weston-based-graphic-system - -.. rubric:: Where is the pointercal file? - :name: where-is-the-pointercal-file - -The Processor SDK Linux moves the calibration file for the touchscreen -from the default location of /etc/pointercal to instead be placed at -/run/media/mmcblk0p1/pointercal if the SD device is present. This was -done to allow user's to easily delete this file and force a -recalibration without requiring a Linux PC to mount the file system or a -serial console to access the device. In this case the pointercal file is -now written to a FAT partition of the SD card, which can be mounted on -both Windows or Linux. - -If the pointercal file is created at /run/media/mmcblk0p1/pointercal, -and there is not already a file in /etc/pointercal then the file is also -copied to the old default location. This is to prevent requiring the -export of the TSLIB\_CALIBFILE variable as described in later sections -of this document. - -In the case that there is no SD card available then the pointercal file -will be written to the default /etc/pointercal location. - -.. rubric:: Recalibrating by Deleting pointercal - :name: recalibrating-by-deleting-pointercal - -Because the pointercal file is now written to the FAT partition of the -SD card recalibrating the touchscreen can be done by simply inserting -the SD card into a PC and deleting the pointercal file found on the -first partition (assuming the first partition is a FAT partition). When -the system is then rebooted you will be asked to calibrate the -touchscreen. - -.. rubric:: Recalibrating over Serial Console - :name: recalibrating-over-serial-console - -If you do have access to the serial console you can always recalibrate -the touchscreen using the **ts\_calibrate** command as normal. However, -in this case if you already have a pointercal file on the SD card you -will need to export the **TSLIB\_CALIBFILE** variable to point to that -location before you run **ts\_calibrate**. i.e. - -.. code-block:: console - - root@:~# export TSLIB_CALIBFILE=/run/media/mmcblk0p1/pointercal - root@:~# ts_calibrate - -**NOTE:** If you have Matrix or any other GUI application already -running you should stop that application (`How to Stop -Matrix <../../Examples_and_Demos_Matrix_User_Guide.html>`__) -before running **ts\_calibrate** so that you can see the calibration -screen. - -.. rubric:: Exporting TSLIB\_CALIBFILE - :name: exporting-tslib_calibfile - -The environment variable TSLIB\_CALIBFILE is used by the *tslib* package -to indicate the location of the pointercal file. The default value for -TSLIB\_CALIBFILE is /etc/pointercal. If you are writing a program that -uses *tslib* you should make sure that you export TSLIB\_CALIBFILE to -point to the location of your pointercal file (as indicated in the -previous section), or that you place a copy of the pointercal file at -the default /etc/pointercal location. - -.. rubric:: Weston based Graphic System - :name: weston-based-graphic-system - -.. rubric:: Where is the ws-calibrate.rules file? - :name: where-is-the-ws-calibrate.rules-file - -The Processor SDK Linux moves the Weston calibration file for the -touchscreen from the default location of -/etc/udev/rules.d/ws-calibrate.rules to instead be placed at -/run/media/mmcblk0p1/ws-calibrate.rules if the SD device is present. -This was done to allow user's to easily delete this file and force a -recalibration without requiring a Linux PC to mount the file system or a -serial console to access the device. In this case the ws-calibrate.rules -file is now written to a FAT partition of the SD card, which can be -mounted on both Windows or Linux. - -If the ws-calibrate.rules file is created at -/run/media/mmcblk0p1/ws-calibrate.rules, and there is not already a file -in /etc/udev/rules.d/ws-calibrate.rules then the file is also copied to -the old default location. - -In the case that there is no SD card available then the -ws-calibrate.rules file will be written to the default -/etc/udev/rules.d/ws-calibrate.rules. - -.. rubric:: Recalibrating by Deleting ws-calibrate.rules - :name: recalibrating-by-deleting-ws-calibrate.rules - -To trigger touchscreen re-calibration, both ws-calbration.rules files -need to be deleted. The ws-calbration.rules file which is now written to -the FAT partition of the SD card can be deleted by simply inserting the -SD card into a PC and deleting the ws-calbration.rules file found on the -first partition (assuming the first partition is a FAT partition) and we -also need to delete /etc/udev/rules.d/ws-calibrate.rules from the -filesystem. After both ws-calibration.rules files are removed, you will -be asked to calibrate the touchscreen when the Weston is launched at the -first time or relaunched by issuing "/etc/init.d/weston start" command -at the console. - -Alternatively, you may delete the above listed files directly from the -EVM's console by issuing the following commands at EVM's Linux prompt, -and reboot the EVM to allow recalibration of the LCD. - -.. code-block:: console - - root@:~# rm /etc/udev/rules.d/ws-calibrate.rules - root@:~# rm /run/media/mmcblk0p1/ws-calibrate.rules - root@:~# reboot - diff --git a/source/linux/How_to_Guides/Target/How_to_use_a_Mouse_instead_of_the_Touchscreen_with_Matrix.rst b/source/linux/How_to_Guides/Target/How_to_use_a_Mouse_instead_of_the_Touchscreen_with_Matrix.rst deleted file mode 100644 index 050b93c06..000000000 --- a/source/linux/How_to_Guides/Target/How_to_use_a_Mouse_instead_of_the_Touchscreen_with_Matrix.rst +++ /dev/null @@ -1,84 +0,0 @@ -.. http://processors.wiki.ti.com/index.php/How_to_use_a_Mouse_instead_of_the_Touchscreen_with_Matrix - -How to use a Mouse instead of the Touchscreen with Matrix -================================================================== -.. rubric:: Introduction - :name: introduction-use-mouse-instead-of-touch - -A mouse can be used instead of touchscreen input with the Matrix GUI by -following these steps. It is also possible to use touchscreen and mouse -input simultaneously. - -**Restrictions:** For AM37x and AM35x: The mouse must be connected -through a USB 2.0 hub to the EVM. It must not be connected directly to -the EVM. - -.. rubric:: Enable Mouse - :name: enable-mouse - -On your Target File system, edit the file: /etc/init.d/matrix-gui-2.0 -This script file will set Mouse support by default, but if it detects a -touchscreen, then it will setup touchscreen support. If you comment out -the touchscreen support then the default will remain mouse support. Use -the '#' to comment out the line below: - -For Mouse support, Replace: - -:: - - if [ -e /dev/input/touchscreen0 ] - then - export QWS_MOUSE_PROTO=Tslib:/dev/input/touchscreen0 - fi - -with - -:: - - # if [ -e /dev/input/touchscreen0 ] - # then - # export QWS_MOUSE_PROTO=Tslib:/dev/input/touchscreen0 - # fi - -To Enable both Mouse and touchscreen simultaneously: Replace - -:: - - export QWS_MOUSE_PROTO=Tslib:/dev/input/touchscreen0 - -with - -:: - - export QWS_MOUSE_PROTO="Tslib:/dev/input/touchscreen0 Auto" - -**Warning**: If you enable both, the touchscreen now requires a double -touch instead of a single touch. - -.. rubric:: Kernel - :name: kernel - -The Kernel has been configured to enable mouse support in your SDK, so -this step is not necessary if you are using the SDK. - -If you have built your own kernel: The kernel must be configured to -include the PS/2 mouse support. To verify this, run the menuconfig -utility. - -| Instructions on executing menuconfig can be found here: `Customizing - the Kernel - Configuration <../../Foundational_Components_Kernel_Users_Guide.html#customizing-the-configuration>`__ - -| -| Look under: - -Device Drivers ---> Input device support ---> <\*> Mouse interface - -Device Drivers ---> Input device support ---> <\*> Mice ---> - -If mouse support is not already included in the kernel, enable the above -two configuration by typing 'y' and rebuild the kernel. You can find -instructions for rebuilding kernel here: - -`Linux Kernel User's Guide <../../Foundational_Components_Kernel_Users_Guide.html>`__ - diff --git a/source/linux/How_to_Guides_Developer_Notes.rst b/source/linux/How_to_Guides_Developer_Notes.rst index db875cdc7..c916262d3 100644 --- a/source/linux/How_to_Guides_Developer_Notes.rst +++ b/source/linux/How_to_Guides_Developer_Notes.rst @@ -14,10 +14,8 @@ Developer Notes How_to_Guides/Host/AM335x_ICEv2_flash_erase How_to_Guides/Host/How_to_Setup_Ubuntu_1404_Network_Boot How_to_Guides/Host/Additional_How_to_Guide_Links - How_to_Guides/Target/How_to_Recalibrate_the_Touchscreen How_to_Guides/Target/Processor_SDK_Linux_File_System_Optimization_Customization How_to_Guides/Target/How_to_add_a_JVM - How_to_Guides/Target/How_to_use_a_Mouse_instead_of_the_Touchscreen_with_Matrix How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux How_to_Guides/Target/How_to_Change_dtb_File How_to_Guides/Target/How_to_Set_Display_for_AM572x_GP_EVM diff --git a/source/linux/How_to_Guides_Target.rst b/source/linux/How_to_Guides_Target.rst index e6819ad42..f99789727 100644 --- a/source/linux/How_to_Guides_Target.rst +++ b/source/linux/How_to_Guides_Target.rst @@ -5,10 +5,8 @@ Target .. toctree:: :maxdepth: 5 - How_to_Guides/Target/How_to_Recalibrate_the_Touchscreen How_to_Guides/Target/Processor_SDK_Linux_File_System_Optimization_Customization How_to_Guides/Target/How_to_add_a_JVM - How_to_Guides/Target/How_to_use_a_Mouse_instead_of_the_Touchscreen_with_Matrix How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux How_to_Guides/Target/How_to_Change_dtb_File How_to_Guides/Target/How_to_Set_Display_for_AM572x_GP_EVM diff --git a/source/linux/Overview/Processor_SDK_Linux_Creating_a_SD_Card_with_Windows.rst b/source/linux/Overview/Processor_SDK_Linux_Creating_a_SD_Card_with_Windows.rst index 017131de0..39ab7ad86 100644 --- a/source/linux/Overview/Processor_SDK_Linux_Creating_a_SD_Card_with_Windows.rst +++ b/source/linux/Overview/Processor_SDK_Linux_Creating_a_SD_Card_with_Windows.rst @@ -104,13 +104,9 @@ Here is the process to follow to create the SD card. #. Plug it into a supported hardware platform and boot the platform from the SD card. #. If the platform has a display (Starterkit, for example), you should - see the Matrix application from the SDK. If the hardware does not - have a display, you should be able to access Matrix remotely through - a web browser if the PC and the board are on a common network. You - can also connect to the board using a terminal emulator (ex. Tera - Term) in order to view the serial console and interact with the - embedded Linux system (ex. run ifconfig to get the IP address of the - target board in order to connect to it to view remote matrix). + see the landing application from the SDK. You can also connect to the board + using a terminal emulator (ex. Tera Term) in order to view the serial console + and interact with the embedded Linux system. | diff --git a/source/linux/Overview/Processor_SDK_Linux_Getting_Started_Guide.rst b/source/linux/Overview/Processor_SDK_Linux_Getting_Started_Guide.rst index fba9eb739..5fbcd9855 100644 --- a/source/linux/Overview/Processor_SDK_Linux_Getting_Started_Guide.rst +++ b/source/linux/Overview/Processor_SDK_Linux_Getting_Started_Guide.rst @@ -20,15 +20,6 @@ pieces work together. We package all of this together with a working Linux Embedded System that has been built with all of the things mentioned above. -.. ifconfig:: CONFIG_sdk in ('SITARA') - - It contains a featured application called - “Matrix” (derived from the fact that it is basically a simple - Graphical User’s Interface (GUI) of icon’s arranged in a “matrix”). - Matrix is a fairly simple embedded Linux system that highlights some - of the key features of the TI Processor offering (LCD display, - graphics, networking, etc.). - What it really serves as is a “known good” starting point. One of the big challenges with starting development on a new platform (not to mention, a new Operating System (OS) for many), is getting an @@ -86,8 +77,7 @@ pieces to simplify things a bit: .. ifconfig:: CONFIG_sdk in ('SITARA') - RTOS application sources and configuration files - - A Yocto/OE compliant filesystem and sources for example - applications in Matrix + - A Yocto/OE compliant filesystem .. ifconfig:: CONFIG_sdk in ('JACINTO','j7_foundational') @@ -121,29 +111,23 @@ So, if you’re not quite there yet, let’s discuss some other options. Maybe you’d like to evaluate the SDK a bit to see if it is how you’d like to get started. -If this is not good enough and you really want to get your hands on -something, check out the next section which shares how to play with the -embedded Linux system |__FEATURINGMATRIX__|, the first piece of the SDK -mentioned earlier. All you’ll need is access to a Linux -computer, a SD card, a SD card reader, some free, open-source software, -and a supported :ref:`Hardware Platform `. - -.. ifconfig:: CONFIG_sdk in ('SITARA') - - .. rubric:: Evaluating the SDK Embedded Linux System and Matrix - :name: evaluating-the-sdk-embedded-linux-system-and-matrix - -.. ifconfig:: CONFIG_sdk in ('JACINTO','j7_foundational') +If this is not good enough and you really want to get your hands on something, +check out the next section which shares how to play with the embedded Linux +system, the first piece of the SDK mentioned earlier. All you’ll need is access +to a Linux computer, a SD card, a SD card reader, some free, open-source +software, and a supported :ref:`Hardware Platform +`. - .. rubric:: Evaluating the SDK Embedded Linux System - :name: evaluating-the-sdk-embedded-linux-system + .. rubric:: Evaluating the SDK Embedded Linux System + :name: evaluating-the-sdk-embedded-linux-system If you’re a hands on person, reading documentation and looking at presentations gets old fast. So, if you want to see an example of what you can build with the SDK and actually hold it in your hands and play with it (or show it to someone else that needs help understanding what you want to do with it), with minimal effort, you can simply run the -SDK Embedded Linux System |__FEATURINGMATRIX__| on a supported :ref:`Hardware platform `. +SDK Embedded Linux System on a supported :ref:`Hardware platform +`. This will allow you to poke and prod and interact. It’s a powerful way to get the imagination active and engaged. @@ -161,7 +145,7 @@ to get the imagination active and engaged. card is simply a few revisions old and you want the latest and greatest. If that is the case, check out the :ref:`Create SD Card ` page. Just remember, you won’t be able to build or change anything, - simply evaluate the SDK Embedded Linux System with Matrix as delivered. + simply evaluate the SDK Embedded Linux System as delivered. But, even this is enough to get the imagination going and all some folks want to do. diff --git a/source/linux/Overview/Top_Level_Makefile.rst b/source/linux/Overview/Top_Level_Makefile.rst index b70f75a85..781f60a52 100644 --- a/source/linux/Overview/Top_Level_Makefile.rst +++ b/source/linux/Overview/Top_Level_Makefile.rst @@ -182,9 +182,6 @@ package: - ``arm-benchmarks`` - Builds the ARM Benchmarks for the ARCH defined in Rules.make. - - ``am-sysinfo`` - Build the helper applications used by the system - settings demos in Matrix. - .. rubric:: Additional Targets :name: additional-targets diff --git a/source/linux/Release_Specific_PLSDK_Release_Notes.rst b/source/linux/Release_Specific_PLSDK_Release_Notes.rst index d5dbf3291..d579f5716 100644 --- a/source/linux/Release_Specific_PLSDK_Release_Notes.rst +++ b/source/linux/Release_Specific_PLSDK_Release_Notes.rst @@ -16,7 +16,6 @@ execution of Linux based applications and includes the following: - SDK Installer - Setup Scripts - Makefiles -- Matrix Application Launcher - Example Applications - WLAN support (Wilink 8) - Code Composer Studio