diff --git a/README.md b/README.md index c858c01bc..21a3b7375 100644 --- a/README.md +++ b/README.md @@ -46,8 +46,6 @@ of directories listed under `configs/`. For example: * "J721S2" (representing Jacinto 7 AEP) * "J784S4" (representing Jacinto 7 AHP) * "J722S" (representing Jacinto 7 AEN) - * "GEN" (representing General family not listed above) - * "CORESDK" (representing CORESDK) OS represents the operating system. Possible values correspond to the second parameter of files listed under the `configs//` directory. For diff --git a/configs/CORESDK/CORESDK_linux_config.txt b/configs/CORESDK/CORESDK_linux_config.txt deleted file mode 100644 index c95f170e6..000000000 --- a/configs/CORESDK/CORESDK_linux_config.txt +++ /dev/null @@ -1,40 +0,0 @@ -# CORESDK family replacement variables and configuration values for Linux build - -# This file is processed by Python scripts to define both replacement -# variable and configuration values for a device family build. -# For replacement variables, all variables should be listed on a single -# line, and all the variables should be listed on consecutive lines -# (i.e. no additional blank lines between the replacement variables). -# Similarly, all the configuration values should be listed on individual, -# consecutive lines (with no blank linues between the configuration values). -# -# Note that neither replacement variables nor configuration values may contain -# a colon (i.e. ":") in their name. However, values may contain colons. - -Replacement Variables ---------------------- -'__PART_FAMILY_NAME__' : 'AM335x' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM335x devices' -'__PRODUCT_LINE_NAME__' : 'Sitara' -'__SDK_FULL_NAME__' : 'CORESDK Linux' -'__SDK_SHORT_NAME__' : 'CORESDK' -'__SDK_INSTALL_FILE__' : 'ti-processor-sdk-linux-[platform]--Linux-x86-Install.bin' -'__SDK_INSTALL_DIR__' : 'ti-processor-sdk-linux-[platformName]-evm-' -'__SDK_DOWNLOAD_URL__' : '`AM335X-Linux-SDK-Download-page `__' -'__LINUX_UBUNTU_VERSION_LONG__' : '18.04 (64-bit)' -'__LINUX_UBUNTU_VERSION_SHORT__' : '18.04' -'__RTOS_UBUNTU_VERSION_LONG__' : '14.04 (64-bit), 16.04 (64-bit)' -'__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__SYSFW_CORE_NAME__' : \ -'__IMAGE_TYPE__' : 'default' - -Configuration Values --------------------- -'CONFIG_part_family' : 'AM335X_family' -'CONFIG_part_variant' : 'AM335X' -'CONFIG_sdk' : 'SITARA' -'CONFIG_image_type' : 'default' -'CONFIG_icss_support' : 'no' -'CONFIG_rt_linux_support' : 'yes' -'CONFIG_gpu_ip' : 'SGX' -'CONFIG_crypto' : '' diff --git a/configs/CORESDK/CORESDK_linux_tags.py b/configs/CORESDK/CORESDK_linux_tags.py deleted file mode 100644 index 9058d5aa9..000000000 --- a/configs/CORESDK/CORESDK_linux_tags.py +++ /dev/null @@ -1,42 +0,0 @@ -# Device Family is CORESDK = CORESDK family -fam_name = 'CORESDK' - -# Processor SDK Linux documentation build configuration file - -# The master toctree document. -master_doc = 'linux/index' -# Output file base name for HTML help builder. -htmlhelp_basename = 'ProcessorSDKLinuxdoc' - -# Grouping the document tree into LaTeX files. List of tuples -# (source start file, target name, title, -# author, documentclass [howto, manual, or own class]). -latex_documents = [ - (master_doc, 'ProcessorSDKLinux.tex', u'Processor SDK Linux Documentation', - u'Texas Instruments Incorporated', u'manual'), -] - -# -- Options for manual page output --------------------------------------- - -# One entry per manual page. List of tuples -# (source start file, name, description, authors, manual section). -man_pages = [ - (master_doc, 'ProcessorSDKLinux', u'Processor SDK Linux Documentation', - ['Texas Instruments Incorporated'], 1) -] - -# If true, show URL addresses after external links. -#man_show_urls = False - - -# -- Options for Texinfo output ------------------------------------------- - -# Grouping the document tree into Texinfo files. List of tuples -# (source start file, target name, title, author, -# dir menu entry, description, category) -texinfo_documents = [ - (master_doc, 'ProcessorSDKLinux', u'Processor SDK Linux Documentation', - 'Texas Instruments Incorporated', 'ProcessorSDKLinux', 'One line description of project.', - 'Miscellaneous'), -] - diff --git a/configs/CORESDK/CORESDK_linux_toc.txt b/configs/CORESDK/CORESDK_linux_toc.txt deleted file mode 100644 index d5aa499a0..000000000 --- a/configs/CORESDK/CORESDK_linux_toc.txt +++ /dev/null @@ -1,5 +0,0 @@ -linux/index -linux/Release_Specific -linux/Release_Specific_CoreSDK_Release_Notes -linux/Release_Specific_CoreSDK_Yocto_layer_Configuration -linux/Release_Specific_CoreSDK_Migration_Guide diff --git a/configs/GEN/GEN_android_config.txt b/configs/GEN/GEN_android_config.txt deleted file mode 100644 index c763aa153..000000000 --- a/configs/GEN/GEN_android_config.txt +++ /dev/null @@ -1,38 +0,0 @@ -# General family replacement variables and configuration values for Android build - -# This file is processed by Python scripts to define both replacement -# variable and configuration values for a device family build. -# For replacement variables, all variables should be listed on a single -# line, and all the variables should be listed on consecutive lines -# (i.e. no additional blank lines between the replacement variables). -# Similarly, all the configuration values should be listed on individual, -# consecutive lines (with no blank linues between the configuration values). -# -# Note that neither replacement variables nor configuration values may contain -# a colon (i.e. ":") in their name. However, values may contain colons. - -Replacement Variables ---------------------- -'__PART_FAMILY_NAME__' : 'Sitara' -'__PART_FAMILY_DEVICE_NAMES__' : 'Sitara devices' -'__PRODUCT_LINE_NAME__' : 'Sitara' -'__SDK_FULL_NAME__' : 'Processor SDK Android' -'__SDK_SHORT_NAME__' : 'PASDK' -'__SDK_INSTALL_FILE__' : 'ti-processor-sdk-linux-[platform]--Linux-x86-Install.bin' -'__SDK_INSTALL_DIR__' : 'ti-processor-sdk-linux-[platformName]-evm-' -'__SDK_DOWNLOAD_URL__' : '`AM57xx-Android-SDK-Download-page `__' -'__LINUX_UBUNTU_VERSION_LONG__' : '18.04 (64-bit)' -'__LINUX_UBUNTU_VERSION_SHORT__' : '18.04' -'__RTOS_UBUNTU_VERSION_LONG__' : '18.04 (64-bit)' -'__WINDOWS_SUPPORTED_LONG__' : '7 (64-bit)' -'__SYSFW_CORE_NAME__' : \ - -Configuration Values --------------------- -'CONFIG_part_family' : 'General_family' -'CONFIG_part_variant' : 'Gen' -'CONFIG_sdk' : 'PSDKAnd' -'CONFIG_icss_support' : 'no' -'CONFIG_rt_linux_support' : 'no' -'CONFIG_gpu_ip' : 'SGX' - diff --git a/configs/GEN/GEN_android_tags.py b/configs/GEN/GEN_android_tags.py deleted file mode 100644 index ff5e7ee0d..000000000 --- a/configs/GEN/GEN_android_tags.py +++ /dev/null @@ -1,42 +0,0 @@ -# Device Family is GEN = General family -fam_name = 'GEN' - -# Processor SDK Android documentation build configuration file - -# The master toctree document. -master_doc = 'android/index' - -# Output file base name for HTML help builder. -htmlhelp_basename = 'ProcessorSDKAndroiddoc' - -# Grouping the document tree into LaTeX files. List of tuples -# (source start file, target name, title, -# author, documentclass [howto, manual, or own class]). -latex_documents = [ - (master_doc, 'ProcessorSDKAndroid.tex', u'Processor SDK Android Documentation', - u'Texas Instruments Incorporated', u'manual'), -] - -# -- Options for manual page output --------------------------------------- - -# One entry per manual page. List of tuples -# (source start file, name, description, authors, manual section). -man_pages = [ - (master_doc, 'ProcessorSDKAndroid', u'Processor SDK Android Documentation', - ['Texas Instruments Incorporated'], 1) -] - -# If true, show URL addresses after external links. -#man_show_urls = False - - -# -- Options for Texinfo output ------------------------------------------- - -# Grouping the document tree into Texinfo files. List of tuples -# (source start file, target name, title, author, -# dir menu entry, description, category) -texinfo_documents = [ - (master_doc, 'ProcessorSDKAndroid', u'Processor SDK Android Documentation', - 'Texas Instruments Incorporated', 'ProcessorSDKAndroid', 'One line description of project.', - 'Miscellaneous'), -] diff --git a/configs/GEN/GEN_android_toc.txt b/configs/GEN/GEN_android_toc.txt deleted file mode 100644 index e739886e6..000000000 --- a/configs/GEN/GEN_android_toc.txt +++ /dev/null @@ -1,5 +0,0 @@ -android/index -android/Overview -android/Overview_Getting_Started_Guide -android/Overview_Building_the_SDK -android/Overview_Technical_Support diff --git a/configs/GEN/GEN_linux_config.txt b/configs/GEN/GEN_linux_config.txt deleted file mode 100644 index ec86a3626..000000000 --- a/configs/GEN/GEN_linux_config.txt +++ /dev/null @@ -1,41 +0,0 @@ -# General family replacement variables and configuration values for Linux build - -# This file is processed by Python scripts to define both replacement -# variable and configuration values for a device family build. -# For replacement variables, all variables should be listed on a single -# line, and all the variables should be listed on consecutive lines -# (i.e. no additional blank lines between the replacement variables). -# Similarly, all the configuration values should be listed on individual, -# consecutive lines (with no blank linues between the configuration values). -# -# Note that neither replacement variables nor configuration values may contain -# a colon (i.e. ":") in their name. However, values may contain colons. - -Replacement Variables ---------------------- -'__PART_FAMILY_NAME__' : 'Sitara' -'__PART_FAMILY_DEVICE_NAMES__' : 'Sitara devices' -'__PRODUCT_LINE_NAME__' : 'Sitara' -'__SDK_BUILD_MACHINE__' : 'am57xx-evm' -'__SDK_FULL_NAME__' : 'Processor SDK Linux' -'__SDK_SHORT_NAME__' : 'SITARA' -'__SDK_INSTALL_FILE__' : 'ti-processor-sdk-linux-[platform]--Linux-x86-Install.bin' -'__SDK_INSTALL_DIR__' : 'ti-processor-sdk-linux-[platformName]-evm-' -'__SDK_DOWNLOAD_URL__' : '`AM57xx-Linux-SDK-Download-page `__' -'__LINUX_UBUNTU_VERSION_LONG__' : '16.04 (64-bit), 18.04 (64-bit)' -'__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)' -'__IMAGE_TYPE__' : 'default' - -Configuration Values --------------------- -'CONFIG_part_family' : 'General_family' -'CONFIG_part_variant' : 'Gen' -'CONFIG_sdk' : 'SITARA' -'CONFIG_image_type' : 'default' -'CONFIG_icss_support' : 'yes' -'CONFIG_rt_linux_support' : 'yes' -'CONFIG_gpu_ip' : 'SGX' -'CONFIG_crypto' : 'omap' - diff --git a/configs/GEN/GEN_linux_tags.py b/configs/GEN/GEN_linux_tags.py deleted file mode 100644 index b688bb6cf..000000000 --- a/configs/GEN/GEN_linux_tags.py +++ /dev/null @@ -1,42 +0,0 @@ -# Device Family is GEN = General family -fam_name = 'GEN' - -# Processor SDK Linux documentation build configuration file - -# The master toctree document. -master_doc = 'linux/index' - -# Output file base name for HTML help builder. -htmlhelp_basename = 'ProcessorSDKLinuxdoc' - -# Grouping the document tree into LaTeX files. List of tuples -# (source start file, target name, title, -# author, documentclass [howto, manual, or own class]). -latex_documents = [ - (master_doc, 'ProcessorSDKLinux.tex', u'Processor SDK Linux Documentation', - u'Texas Instruments Incorporated', u'manual'), -] - -# -- Options for manual page output --------------------------------------- - -# One entry per manual page. List of tuples -# (source start file, name, description, authors, manual section). -man_pages = [ - (master_doc, 'ProcessorSDKLinux', u'Processor SDK Linux Documentation', - ['Texas Instruments Incorporated'], 1) -] - -# If true, show URL addresses after external links. -#man_show_urls = False - - -# -- Options for Texinfo output ------------------------------------------- - -# Grouping the document tree into Texinfo files. List of tuples -# (source start file, target name, title, author, -# dir menu entry, description, category) -texinfo_documents = [ - (master_doc, 'ProcessorSDKLinux', u'Processor SDK Linux Documentation', - 'Texas Instruments Incorporated', 'ProcessorSDKLinux', 'One line description of project.', - 'Miscellaneous'), -] diff --git a/configs/GEN/GEN_linux_toc.txt b/configs/GEN/GEN_linux_toc.txt deleted file mode 100644 index 9f38816da..000000000 --- a/configs/GEN/GEN_linux_toc.txt +++ /dev/null @@ -1,202 +0,0 @@ -linux/index -linux/Overview -linux/Overview_Getting_Started_Guide -linux/Overview_Building_the_SDK -linux/Overview_Directory_Structure_Overview -linux/Overview_Software_Stack -linux/Overview_Technical_Support -linux/Overview_Training -linux/Overview_GPLv3_Disclaimer -linux/Overview/Processor_SDK_Linux_Getting_Started_Guide -linux/Overview/Processor_SDK_Linux_create_SD_card_script -linux/Overview/Processor_SDK_Linux_Creating_a_SD_Card_with_Windows -linux/Overview/Download_and_Install_the_SDK -linux/Overview/Program_EVM -linux/Overview/Run_Setup_Scripts -linux/Overview/Top_Level_Makefile -linux/Overview/GCC_ToolChain -linux/Release_Specific -linux/Release_Specific_PLSDK_Release_Notes -linux/Release_Specific_Performance_Guide -linux/Release_Specific_Yocto_layer_Configuration -linux/Release_Specific_Supported_Platforms_and_Versions -linux/Foundational_Components -linux/Foundational_Components_U-Boot -linux/Foundational_Components/U-Boot/Users-Guide -linux/Foundational_Components/U-Boot/UG-General-Info -linux/Foundational_Components/U-Boot/UG-DFU -linux/Foundational_Components/U-Boot/UG-Network -linux/Foundational_Components/U-Boot/UG-NAND -linux/Foundational_Components/U-Boot/UG-Memory-OMAP -linux/Foundational_Components/U-Boot/UG-SPI -linux/Foundational_Components/U-Boot/UG-QSPI -linux/Foundational_Components/U-Boot/UG-NOR -linux/Foundational_Components/U-Boot/UG-UART -linux/Foundational_Components/U-Boot/UG-SATA -linux/Foundational_Components/U-Boot/UG-UFS -linux/Foundational_Components/U-Boot/UG-DDR3 -linux/Foundational_Components/U-Boot/UG-HyperBus -linux/Foundational_Components/U-Boot/UG-RemoteProc -linux/Foundational_Components/U-Boot/Applications -linux/Foundational_Components/U-Boot/Apps-SPL-Debug-OpenOCD -linux/Foundational_Components/U-Boot/Apps-Load-in-CCS -linux/Foundational_Components/U-Boot/Apps-TroubleShooting -linux/Foundational_Components_Boot_Monitor -linux/Foundational_Components_Kernel -linux/Foundational_Components_Kernel_Drivers -linux/Foundational_Components/Kernel/Kernel_Drivers/ADC -linux/Foundational_Components/Kernel/Kernel_Drivers/Audio -linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/VPFE -linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/VIP -linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CAL -linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto/SA2UL_OMAP -linux/Foundational_Components/Kernel/Kernel_Drivers/MCAN -linux/Foundational_Components/Kernel/Kernel_Drivers/DCAN -linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS -linux/Foundational_Components/Kernel/Kernel_Drivers/Display/LCDC -linux/Foundational_Components/Kernel/Kernel_Drivers/GPIO -linux/Foundational_Components/Kernel/Kernel_Drivers/I2C -linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW -linux/Foundational_Components/Kernel/Kernel_Drivers/Network/NetCP -linux/Foundational_Components/Kernel/Kernel_Drivers/Network/PRUSS -linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW2g -linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_End_Point -linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Root_Complex -linux/Foundational_Components_Power_Management -linux/Foundational_Components/Power_Management/pm_overview -linux/Foundational_Components/Power_Management/pm_dvfs -linux/Foundational_Components/Power_Management/pm_smartreflex -linux/Foundational_Components/Power_Management/pm_suspend_resume -linux/Foundational_Components/Kernel/Kernel_Drivers/PWM -linux/Foundational_Components/Kernel/Kernel_Drivers/QSPI -linux/Foundational_Components/Kernel/Kernel_Drivers/SPI -linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/SATA -linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/NAND -linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD -linux/Foundational_Components/Kernel/Kernel_Drivers/UART -linux/Foundational_Components/Kernel/Kernel_Drivers/UBIFS -linux/Foundational_Components/Kernel/Kernel_Drivers/UFS -linux/Foundational_Components/Kernel/Kernel_Drivers/USB/MUSB -linux/Foundational_Components/Kernel/Kernel_Drivers/USB/DWC3 -linux/Foundational_Components/Kernel/Kernel_Drivers/VPE -linux/Foundational_Components_Kernel_Users_Guide -linux/Foundational_Components_Kernel_Release_Notes -linux/Foundational_Components_Kernel_RT_Release_Notes -linux/Foundational_Components_Kernel_LTP-DDT_Validation -linux/Foundational_Components_Kernel_FAQs -linux/Foundational_Components_Filesystem -linux/Foundational_Components_Tools -linux/Foundational_Components/Tools/Development_Tools -linux/Foundational_Components/Tools/Flash_Tools -linux/Foundational_Components/Tools/Pin_Mux_Tools -linux/Foundational_Components/Tools/Code_Composer_Studio -linux/Foundational_Components_PRU_Subsystem -linux/Foundational_Components/PRU-ICSS-Linux-Drivers -linux/Foundational_Components/PRU-ICSS/Linux_Drivers/RemoteProc -linux/Foundational_Components/PRU-ICSS/Linux_Drivers/RPMsg -linux/Foundational_Components/PRU-ICSS/RPMsg_Quick_Start_Guide -linux/Foundational_Components/PRU-ICSS/Linux_Drivers/PRU-ICSS_Ethernet -linux/Foundational_Components/PRU-ICSS/Linux_Drivers/PRU_ICSSG_Ethernet -linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pru-sw-uart -linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pru-icssg-pwm -linux/Foundational_Components/PRU-ICSS-Hardware -linux/Foundational_Components/PRU-ICSS/PRU-EVMs -linux/Foundational_Components/PRU-ICSS-Training -linux/Foundational_Components/PRU-ICSS-Firmware-Development -linux/Foundational_Components_IPC -linux/Foundational_Components_CMEM -linux/Foundational_Components_Multimedia_IVAHD -linux/Foundational_Components_OpenCL -linux/Foundational_Components_OpenCV -linux/Foundational_Components_OpenVX -linux/Foundational_Components_Virtualization -linux/Foundational_Components/Virtualization/Docker -linux/Foundational_Components_Machine_Learning -linux/Foundational_Components/Machine_Learning/armnn -linux/Foundational_Components/Machine_Learning/tflite -linux/Foundational_Components_OPTEE -linux/Foundational_Components_ATF - -linux/Foundational_Components/Graphics/index -linux/Foundational_Components/Graphics/Common/Display -linux/Foundational_Components/Graphics/Common/GTK+_Graphics_Framework -linux/Foundational_Components/Graphics/Common/OpenGL_ES -linux/Foundational_Components/Graphics/Common/PVR_Tools -linux/Foundational_Components/Graphics/Common/QT_Graphics_Framework -linux/Foundational_Components/Graphics/Common/Weston -linux/Foundational_Components/Graphics/SGX/AM3_Beagle_Bone_Black_Configuration -linux/Foundational_Components/Graphics/SGX/Overview -linux/Foundational_Components/Graphics/SGX/SGX_Debug_Info -linux/Foundational_Components/Graphics/SGX/Build_Guide - -linux/Industrial_Protocols -linux/Industrial_Protocols_ICSS_Dual_EMAC -linux/Industrial_Protocols_HSR_PRP -linux/Industrial_Protocols_PTP -linux/Industrial_Protocols_RSTP -linux/Industrial_Protocols_CCLINK -linux/Industrial_Protocols_SORTE -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/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/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_Sub-system_Demos -linux/How_to_Guides -linux/How_to_Guides_Host -linux/How_to_Guides/Host/How_to_Build_a_Ubuntu_Linux_host_under_VMware -linux/How_to_Guides/Host/Connect_to_an_EVM_via_Telnet -linux/How_to_Guides/Host/How_to_Setup_a_Samba_Server -linux/How_to_Guides/Host/Boot_Sequence -linux/How_to_Guides/Host/Moving_Files_to_the_Target_System -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/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/Processor_SDK_Linux_File_System_Optimization_Customization -linux/How_to_Guides/Target/How_to_add_a_JVM -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 -linux/How_to_Guides/Target/How_to_Boot_Beagle_Bone_Black_with_Processor_SDK_Linux -linux/How_to_Guides_Hardware_Setup_with_CCS -linux/How_to_Guides/Hardware_Setup_with_CCS/TMDX654_EVM_Hardware_Setup -linux/How_to_Guides/Hardware_Setup_with_CCS/AM572x_GP_EVM_Hardware_Setup -linux/How_to_Guides/Hardware_Setup_with_CCS/TMDXIDK5728_Hardware_Setup -linux/How_to_Guides/Hardware_Setup_with_CCS/66AK2G02_GP_EVM_Hardware_Setup -linux/How_to_Guides/Hardware_Setup_with_CCS/66AK2G02_ICE_EVM_Hardware_setup -linux/How_to_Guides/Hardware_Setup_with_CCS/EVMK2E_Hardware_Setup -linux/How_to_Guides/Hardware_Setup_with_CCS/EVMK2H_Hardware_Setup -linux/How_to_Guides/Hardware_Setup_with_CCS/ICE_AM335x_Hardware_Setup -linux/How_to_Guides/Hardware_Setup_with_CCS/ICE_AMIC110_EVM_Hardware_Setup -linux/How_to_Guides/Hardware_Setup_with_CCS/OMAPL138-C6748_LCDK_Hardware_Setup -linux/How_to_Guides_Linux_Porting_Guide_AM571x_AM570x_Speed_Grades -linux/Documentation_Tarball -common/PRU-ICSS/Getting_Started_with_PSSP -common/PRU-ICSS/Header_Files -common/PRU-ICSS/INTC_Configuration -common/PRU-ICSS/Overview -common/PRU-ICSS/PRU-Cape-Building-Demos -common/PRU-ICSS/PRU-Cape-Getting-Started-Guide -common/PRU-ICSS/PRU-Cape-Hardware-User-Guide -common/PRU-ICSS/PRU-Getting-Started-Labs -common/PRU-ICSS/PRU-Getting-Started-Labs_Lab1 -common/PRU-ICSS/PRU-Getting-Started-Labs_Lab2 -common/PRU-ICSS/PRU-Getting-Started-Labs_Lab2_cCode -common/PRU-ICSS/PRU-Getting-Started-Labs_Lab2_assemblyCode -common/PRU-ICSS/PRU-Getting-Started-Labs_Lab2_mixedCandAssembly -common/PRU-ICSS/PRU-Getting-Started-Labs_Lab3 -common/PRU-ICSS/PRU-Getting-Started-Labs_Lab4 -common/PRU-ICSS/PRU-Getting-Started-Labs_Lab4_TIRTOS -common/PRU-ICSS/PRU-Getting-Started-Labs_Lab5 -common/PRU-ICSS/PRU-Hands-on-Labs -common/PRU-ICSS/Resource_Tables diff --git a/configs/GEN/GEN_tags.py b/configs/GEN/GEN_tags.py deleted file mode 100644 index 265472393..000000000 --- a/configs/GEN/GEN_tags.py +++ /dev/null @@ -1,2 +0,0 @@ -# Device Family is GEN = General family -fam_name = 'GEN' diff --git a/source/common/PRU-ICSS/Overview.rst b/source/common/PRU-ICSS/Overview.rst index 0a644dc73..b2227cc94 100644 --- a/source/common/PRU-ICSS/Overview.rst +++ b/source/common/PRU-ICSS/Overview.rst @@ -162,7 +162,7 @@ Software Information RemoteProc driver information at :ref:`pru_remoteproc` - .. ifconfig:: CONFIG_part_family in ('AM335X_family','AM437X_family','General_family') + .. ifconfig:: CONFIG_part_family in ('AM335X_family','AM437X_family') Information about general purpose Ethernet over PRU is at :ref:`pru_icss_ethernet`. diff --git a/source/common/Release_Specific/_Processor_SDK_Supported_Platforms_and_Versions.rst b/source/common/Release_Specific/_Processor_SDK_Supported_Platforms_and_Versions.rst index 1200d0515..eb394a1c6 100644 --- a/source/common/Release_Specific/_Processor_SDK_Supported_Platforms_and_Versions.rst +++ b/source/common/Release_Specific/_Processor_SDK_Supported_Platforms_and_Versions.rst @@ -10,7 +10,7 @@ Supported Platforms and Versions The following operating systems have been validated to work with our SDK. -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family') - **Linux SDK** @@ -31,17 +31,6 @@ SDK. | | | 16.04 (64-bit) | +---------------------------+-------------------------+ -.. ifconfig:: CONFIG_part_family in ('General_family') - - - **Android SDK** - - +---------------------------+-------------------------+ - | **Operating System** | | **Version** | - +---------------------------+-------------------------+ - | Ubuntu | | 16.04 (64-bit) | - | | | 18.04 (64-bit) | - +---------------------------+-------------------------+ - .. ifconfig:: CONFIG_sdk in ('JACINTO','j7_foundational') - **Linux SDK** @@ -67,113 +56,6 @@ SDK. The following platforms and EVMs are supported with Processor SDK. -.. ifconfig:: CONFIG_part_family in ('General_family') - - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - |**Platform** |**EVM** |**Tested |**Document** |**Processor SDK |**Processor SDK |**Processor SDK |**Processor SDK | - | | |Version** | |Linux** |RT Linux** |RTOS** |Android** | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - |`AM65x/DRA80xM `__ |`__ | |l.ti.com/processor-sdk-rtos/esd/docs/ | | | | | - | | | |latest/rtos/How_to_Guides.html#am65x-evm>`__| | | | | - | +--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - | |`AM65x/DRA80xM IDK | Beta |Hardware User's Guide | X | X | X | X | - | |`__ | |l.ti.com/processor-sdk-rtos/esd/docs/ | | | | | - | | | |latest/rtos/How_to_Guides.html#am65x-evm>`__| | | | | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - |`AM57x `__ | | | | | - |am57x/overview.page>`__ |TMDSEVM572X>`__ | | | | | | | - | +--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - | |`AM572x IDK | 1.3A |`Hardware User's Guide `__ | | | | | - | |TMDXIDK5728>`__ | |`Hardware Setup with CCS `__ | | | | | - | +--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - | |`AM571x IDK | 1.3A |`Hardware User's Guide `__ | | | | | - | |tmdxidk5718>`__ | |`Hardware Setup with CCS `__ | | | | | - | +--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - | |`AM574x IDK | 1.0A |`Hardware User's Guide `__ | | | | | - | |TMDSIDK574>`__ | |`Hardware Setup with CCS `__ | | | | | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - |`AM437x `__ |TMDXEVM437X>`__ | |General_Purpose_EVM_HW_User_Guide>`__ | | | | | - | +--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - | |`AM437x SK | 1.1A |`Hardware User's Guide `__ | | | | | - | |TMDXSK437X>`__ | | | | | | | - | +--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - | |`AM437x IDK | 1.4A |`Hardware User's Guide `__ | | | | | - | |tmdsidk437x>`__ | | | | | | | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - |`K2H/K2K `__ |/evmk2h>`__ | |EVMK2H_Hardware_Setup>`__ | | | | | - | +--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - | |`TCI6638K2K EVM | 4.0 |`Hardware User's Guide `__ | |EVMK2H_Hardware_Setup>`__ | | | | | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - |`K2E `__ |/xevmk2ex>`__ | |EVMK2E_Hardware_Setup>`__ | | | | | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - |`K2L `__ |/xevmk2lx>`__ | |TCIEVMK2L_Hardware_Setup>`__ | | | | | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - |`K2G `__ | | | | | - |overview.html>`__ |EVMK2G>`__ | | | | | | | - | +--------------------------------------+----------+ +----------------+----------------+----------------+----------------+ - | |`K2G 1G EVM | 1.5D |`Hardware Setup with CCS `__ | |Hardware_Setup>`__ | | | | | - | +--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - | |`K2G Audio Daughtercard | D |`Software Support `__ | |Processor_SDK_RTOS_AUDK2G_AddOn>`__ | | | | | - | +--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - | |`K2G ICE EVM |1.0C Beta |`Hardware User's Guide `__ | | | | | - | |k2gice>`__ | |`Hardware Setup with CCS `__ | | | | | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - |`C665x `__ |/tmdsevm6657>`__ | |TMDSEVM6657L_EVM_Hardware_Setup>`__ | | | | | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - |`C667x `__ |/tmdsevm6678>`__ | |TMDXEVM6678L_EVM_Hardware_Setup>`__ | | | | | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - |`OMAPL137/C6747 `__ |/tmdsoskl137>`__ | |evmomapl137/revd/>`__ | | | | | - | | | |`Hardware Setup with CCS `__ | | | | | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - |`OMAPL138/C6748 `__ |/tmdslcdk138>`__ | |`Hardware Setup with CCS `__ | | | | | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+----------------+ - .. ifconfig:: CONFIG_part_family in ('AM335X_family') +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+ diff --git a/source/images/Back-to-back.jpeg b/source/images/Back-to-back.jpeg deleted file mode 100644 index 7f68d4a59..000000000 Binary files a/source/images/Back-to-back.jpeg and /dev/null differ diff --git a/source/images/Dra7-HOST.jpg b/source/images/Dra7-HOST.jpg deleted file mode 100644 index fb52cd3f1..000000000 Binary files a/source/images/Dra7-HOST.jpg and /dev/null differ diff --git a/source/images/MPCIe-to-PCIe_Adapter.jpg b/source/images/MPCIe-to-PCIe_Adapter.jpg deleted file mode 100644 index 661332699..000000000 Binary files a/source/images/MPCIe-to-PCIe_Adapter.jpg and /dev/null differ diff --git a/source/images/OMAP5-HOST.jpg b/source/images/OMAP5-HOST.jpg deleted file mode 100644 index c7c358ede..000000000 Binary files a/source/images/OMAP5-HOST.jpg and /dev/null differ diff --git a/source/images/Omap5-dwc3.png b/source/images/Omap5-dwc3.png deleted file mode 100644 index 0ffd3fc2f..000000000 Binary files a/source/images/Omap5-dwc3.png and /dev/null differ diff --git a/source/images/am65x-dwc3-usbhs.png b/source/images/am65x-dwc3-usbhs.png deleted file mode 100644 index 6be62fa99..000000000 Binary files a/source/images/am65x-dwc3-usbhs.png and /dev/null differ diff --git a/source/images/am65x-dwc3-usbss.png b/source/images/am65x-dwc3-usbss.png deleted file mode 100644 index eaf721596..000000000 Binary files a/source/images/am65x-dwc3-usbss.png and /dev/null differ 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 f726763bc..bc600520e 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 @@ -40,7 +40,3 @@ TIDL Demo .. note:: This demo is not applicable to AM57X devices. -.. ifconfig:: CONFIG_part_family in ('General_family') - - Refer to various TI DeepLearning demos documented at - :ref:`TIDL Examples and Demos `. diff --git a/source/linux/Foundational_Components/Graphics/Common/Display.rst b/source/linux/Foundational_Components/Graphics/Common/Display.rst index b3c193a0e..4680607c9 100644 --- a/source/linux/Foundational_Components/Graphics/Common/Display.rst +++ b/source/linux/Foundational_Components/Graphics/Common/Display.rst @@ -44,7 +44,7 @@ Finding the connector ID Run the following ``modetest`` command: -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family') .. code-block:: console @@ -82,7 +82,7 @@ Finding the plane ID To find the Plane ID, run the ``modetest`` command: -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family') .. code-block:: console diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Audio.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Audio.rst index 4792c5ba8..4b1738767 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Audio.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Audio.rst @@ -62,7 +62,7 @@ In most cases ``-Dplughw:0,0`` is the device we want to use for audio but in case we have several audio devices (onboard + USB for example) one need to specify which device to use for audio: -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family') ``-Dplughw:omap5uevm,0`` will use the onboard audio on OMAP5-uEVM board. @@ -131,145 +131,6 @@ After booting up the board it can be restored with a single command: Board-specific instructions ^^^^^^^^^^^^^^^^^^^^^^^^^^^ -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: OMAP5 uEVM - :name: omap5-uevm-kernel-audio - - | The board uses **twl6040 codec** connected through **McPDM** for - onboard audio and features one **Headset** connector, one **Stereo - Line In** and one **Stereo Line Out** 3.5mm jack connectors. - - .. rubric:: Kernel config - :name: kernel-config - - .. code-block:: text - - Device Drivers ---> - Sound card support ---> - Advanced Linux Sound Architecture ---> - ALSA for SoC audio support ---> - Audio support for Texas Instruments SoCs ---> - <*> SoC Audio support for OMAP boards using ABE and twl6040 codec - <*> OMAP4/5 HDMI audio support - - - .. rubric:: User space - :name: user-space - - To set up the audio routing on the board (Headset playback/capture): - - .. code-block:: text - - amixer -c omap5uevm sset 'Headset Left Playback' 'HS DAC' # HS Left channel from DAC - amixer -c omap5uevm sset 'Headset Right Playback' 'HS DAC' # HS Right channel from DAC - amixer -c omap5uevm sset Headset 4 # HS volume to -22dB - amixer -c omap5uevm sset 'Analog Left' 'Headset Mic' # Analog Left capture source from HS mic - amixer -c omap5uevm sset 'Analog Right' 'Headset Mic' # Analog Right capture source from HS mic - amixer -c omap5uevm sset Capture 1 # Analog Capture gain to 12dB - - To play audio to the HS: - - .. code-block:: text - - aplay -Dplughw:omap5uevm,0 - - On kernels where the AESS (ABE) support is not available the **Line - Out** can be used only when playing 4 channel audio. In this case the - first two channel will be routed to HS and the second two will be the - Line Out. - - .. code-block:: text - - amixer -c omap5uevm sset 'Handsfree Left Playback' 'HF DAC' # HF Left channel from DAC - amixer -c omap5uevm sset 'Handsfree Right Playback' 'HF DAC' # HF Right channel from DAC - amixer -c omap5uevm sset AUXL on # Enable route to AUXL from the HF path - amixer -c omap5uevm sset AUXR on # Enable route to AUXR from the HF path - amixer -c omap5uevm sset Handsfree 11 # HS volume to -30dB - - To play audio to the Line Out one should have 4 channel sample crafted - and channel 3,4 should have the audio destined to Line Out: - - .. code-block:: text - - aplay -Dplughw:omap5uevm,0 - -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: DRA7 and DRA72 EVM - :name: dra7-and-dra72-evm - - | The board uses **tlv320aic3106 codec** connected through **McASP3 - [AXR0 for playback, AXR1 for Capture]** for audio. The board features - four 3.5mm jack for **Headphone**, **Line In**, **Line Out** and one - for **Microphone**. - - .. rubric:: Kernel config - :name: kernel-config-1 - - .. code-block:: text - - Device Drivers ---> - Sound card support ---> - Advanced Linux Sound Architecture ---> - ALSA for SoC audio support ---> - Audio support for Texas Instruments SoCs ---> - <*> Multichannel Audio Serial Port (McASP) support - <*> OMAP4/5 HDMI audio support - CODEC drivers ---> - <*> Texas Instruments TLV320AIC3x CODECs - <*> ASoC Simple sound card support - - .. rubric:: User space - :name: user-space-1 - - The hardware defaults are correct for audio playback, the routing is OK - and the volume is 'adequate' but in case the volume is not correct: - - .. code-block:: text - - amixer -c DRA7xxEVM sset PCM 90 # Master Playback volume - - Playback to Headphone only: - - .. code-block:: text - - amixer -c DRA7xxEVM sset 'Left HP Mixer DACL1' on # HP Left route enable - amixer -c DRA7xxEVM sset 'Right HP Mixer DACR1' on # HP Right route enable - amixer -c DRA7xxEVM sset 'Left Line Mixer DACL1' off # Line out Left disable - amixer -c DRA7xxEVM sset 'Right Line Mixer DACR1' off # Line out Right disable - amixer -c DRA7xxEVM sset 'HP DAC' 90 # Adjust HP volume - - Playback to Line Out only: - - .. code-block:: text - - amixer -c DRA7xxEVM sset 'Left HP Mixer DACL1' off # HP Left route disable - amixer -c DRA7xxEVM sset 'Right HP Mixer DACR1' off # HP Right route disable - amixer -c DRA7xxEVM sset 'Left Line Mixer DACL1' on # Line out Left enable - amixer -c DRA7xxEVM sset 'Right Line Mixer DACR1' on # Line out Right enable - amixer -c DRA7xxEVM sset 'Line DAC' 90 # Adjust Line out volume - - Record from Line In: - - .. code-block:: text - - amixer -c DRA7xxEVM sset 'Left PGA Mixer Line1L' on # Line in Left enable - amixer -c DRA7xxEVM sset 'Right PGA Mixer Line1R' on # Line in Right enable - amixer -c DRA7xxEVM sset 'Left PGA Mixer Mic3L' off # Analog mic Left disable - amixer -c DRA7xxEVM sset 'Right PGA Mixer Mic3R' off # Analog mic Right disable - amixer -c DRA7xxEVM sset 'PGA' 40 # Adjust Capture volume - - Record from Analog Mic IN: - - .. code-block:: text - - amixer -c DRA7xxEVM sset 'Left PGA Mixer Line1L' off # Line in Left disable - amixer -c DRA7xxEVM sset 'Right PGA Mixer Line1R' off # Line in Right disable - amixer -c DRA7xxEVM sset 'Left PGA Mixer Mic3L' on # Analog mic Left enable - amixer -c DRA7xxEVM sset 'Right PGA Mixer Mic3R' on # Analog mic Right enable - amixer -c DRA7xxEVM sset 'PGA' 40 # Adjust Capture volume - .. ifconfig:: CONFIG_part_family in ('AM335X_family') .. rubric:: AM335x EVM @@ -484,105 +345,6 @@ Board-specific instructions amixer -c AM437xGPEVM sset 'Right PGA Mixer Mic3R' off # Analog mic Right disable amixer -c AM437xGPEVM sset 'PGA' 40 # Adjust Capture volume -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: BeagleBoard-X15 and AM572x-GP-EVM - :name: beagleboard-x15-and-am572x-gp-evm - - | The board uses **tlv320aic3104 codec** connected through **McASP3 - [AXR0 for playback, AXR1 for Capture]** for audio. The board features - two 3.5mm jack for **Line Out** and **Line In**. - - .. rubric:: Kernel config - :name: kernel-config-6 - - .. code-block:: text - - Device Drivers ---> - Sound card support ---> - Advanced Linux Sound Architecture ---> - ALSA for SoC audio support ---> - Audio support for Texas Instruments SoCs ---> - <*> Multichannel Audio Serial Port (McASP) support - <*> OMAP4/5 HDMI audio support - CODEC drivers ---> - <*> Texas Instruments TLV320AIC3x CODECs - <*> ASoC Simple sound card support - - .. rubric:: User space - :name: user-space-6 - - The hardware defaults are correct for audio playback, the routing is OK - and the volume is 'adequate' but in case the volume is not correct: - - .. code-block:: text - - amixer -c BeagleBoardX15 sset PCM 90 # Master Playback volume - - Playback (line out): - - .. code-block:: text - - amixer -c BeagleBoardX15 sset 'Left Line Mixer DACL1' on # Line out Left enable - amixer -c BeagleBoardX15 sset 'Right Line Mixer DACR1' on # Line out Right enable - amixer -c BeagleBoardX15 sset 'Line DAC' 90 # Adjust Line out volume - - Record (line in): - - .. code-block:: text - - amixer -c BeagleBoardX15 sset 'Left PGA Mixer Mic2L' on # Line in Left enable (MIC2/LINE2) - amixer -c BeagleBoardX15 sset 'Right PGA Mixer Mic2R' on # Line in Right enable (MIC2/LINE2) - amixer -c BeagleBoardX15 sset 'PGA' 40 # Adjust Capture volume - - | - -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: K2G EVM - :name: k2g-evm - - | The board uses **tlv320aic3106 codec** connected through **McASP2 - [AXR2 for playback, AXR3 for Capture]** for audio. The board features - two 3.5mm jack for **Headphone** and **Line In** - | ``NOTE 1: The Headphone jack is labeld as LINE OUT on the board`` - | ``NOTE 2: Both analog and HDMI audio is served by McASP2, this means that they must not be used at the same time!`` - | ``NOTE 3: Sampling rate is restricted to 44.1KHz family due to the reference clock for McASP2 (22.5792MHz)`` - - .. rubric:: Kernel config - :name: kernel-config-7 - - .. code-block:: text - - Device Drivers ---> - Sound card support ---> - Advanced Linux Sound Architecture ---> - ALSA for SoC audio support ---> - Audio support for Texas Instruments SoCs ---> - <*> Multichannel Audio Serial Port (McASP) support - CODEC drivers ---> - <*> Texas Instruments TLV320AIC3x CODECs - <*> ASoC Simple sound card support - - .. rubric:: User space - :name: user-space-7 - - The hardware defaults are correct for audio playback, the routing is OK - and the volume is 'adequate' but in case the volume is not correct: - - .. code-block:: text - - amixer -c K2GEVM sset PCM 110 # Master Playback volume - - For audio capture from Line-in: - - .. code-block:: text - - amixer -c K2GEVM sset 'Right PGA Mixer Line1R' on - amixer -c K2GEVM sset 'Left PGA Mixer Line1L' on - - | - .. ifconfig:: CONFIG_part_variant in ('J721E') .. rubric:: J721e Common Processor Board @@ -879,7 +641,7 @@ Additional Information .. rubric:: Software Help :name: additional-information-software-help -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family') #. `Tools and Techniques for Audio Debugging `__ @@ -894,7 +656,7 @@ Additional Information .. rubric:: Audio hardware codecs :name: additional-information-audio-hardware-codecs -.. ifconfig:: CONFIG_part_variant in ('Gen', 'AM335X', 'AM437X', 'AM62X', 'AM62AX', 'AM62PX', 'J722S', 'AM62LX') +.. ifconfig:: CONFIG_part_variant in ('AM335X', 'AM437X', 'AM62X', 'AM62AX', 'AM62PX', 'J722S', 'AM62LX') #. `TLV320AIC31 - Low-Power Stereo CODEC with HP Amplifier `__ diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/GPIO.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/GPIO.rst index f9d8b7f07..76e934ff0 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/GPIO.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/GPIO.rst @@ -15,7 +15,7 @@ For example, a MMC/SD driver may need to read a GPIO as in input to determine if a card is present. The H/W GPIO controllers available will vary by SoC and system configuration. -.. ifconfig:: CONFIG_part_family in ('J7_family', 'General_family', 'AM335X_family', 'AM437X_family') +.. ifconfig:: CONFIG_part_family in ('J7_family', 'AM335X_family', 'AM437X_family') .. ifconfig:: CONFIG_part_family in ('J7_family') @@ -23,12 +23,6 @@ configuration. J721E SoCs host DAVINCI GPIO IP. - .. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: AM65 specifics - - AM65 SoCs host DAVINCI GPIO IP. - Current software supports banked GPIO interrupt only. 16 GPIOs form a bank. Each bank can produce an interrupt; this is done to save the number of interrupt lines reaching the CPU. @@ -244,7 +238,7 @@ The GPIO Driver can also be easily leveraged by other drivers to "consume" a GPI | -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family') .. rubric:: Power Management diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_End_Point.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_End_Point.rst index 44cf85667..ae461a165 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_End_Point.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_End_Point.rst @@ -5,15 +5,6 @@ PCIe End Point .. rubric:: **Introduction** -.. ifconfig:: CONFIG_part_family in ('General_family') - - PCI controller IPs integrated in DRA7x/AM57x and 66AK2G SoCs are capable - of operating either in Root Complex mode (host) or End Point mode - (device). When operating in End Point(EP) mode, the controller can be - configured to be used as any function depending on the use case ('Test - endpoint' and 'NTB' are the only PCIe EP functions supported in Linux kernel - right now). - .. ifconfig:: CONFIG_part_family in ('AM64X_family','J7_family') PCIe controller IPs integrated in |__PART_FAMILY_NAME__| are capable @@ -114,36 +105,8 @@ PCIe End Point | PCIE0 | 1 lane | Standard female connector | +------------------------+-------------------+------------------------------------+ -.. ifconfig:: CONFIG_part_family in ('General_family') - - This wiki page provides usage information of PCIe EP Linux driver. - .. rubric:: **Hardware Setup Details** -.. ifconfig:: CONFIG_part_family in ('General_family') - - The following boards have a standard female connector. - - +-----------------+ - | dra74x-evm | - +-----------------+ - | dra72x-evm | - +-----------------+ - | am571x-idk | - +-----------------+ - | am572x-idk | - +-----------------+ - | k2g-gp-evm | - +-----------------+ - | am654-evm | - +-----------------+ - | am654-idk | - +-----------------+ - - These boards are, by default, intended to be operated in Root Complex - mode. So in order to connect two boards, a specialized cable like below - is required. - .. ifconfig:: CONFIG_part_family in ('AM64X_family','J7_family') |__PART_FAMILY_DEVICE_NAMES__| is, by default, intended to be operated in @@ -155,11 +118,6 @@ PCIe End Point An equivalent cable can be obtained from DigiKey (https://www.digikey.com/en/products/detail/3m/8kj2-0743-0250/5128345). -.. ifconfig:: CONFIG_part_family in ('General_family') - - Use either X1 cable or X4 cable depending on the slot provided in the board. - The part number is PE-FLEX1-MM-CX-3" (for 3" cable length x1). - Modify the cable to remove resistors in CK+ and CK- in order to avoid ground loops (power) and smoking clock drivers (clk+/-). @@ -181,28 +139,6 @@ The ends of the modified cable should look like below: .. Image:: /images/PCIE_B_both_sides.jpg -.. ifconfig:: CONFIG_part_family in ('General_family') - - Image of a dra72-evm and dra7-evm connected back to back. There is no - restriction on which end of the cable should be connected to host and - device. - - - .. Image:: /images/Back-to-back.jpeg - - | - - .. note:: - - For AM572x GP EVM, there is a Mini PCIe connector on - the LCD board. To connect 2 boards involving a AM572x GP EVM, a - mPCIe-to-PCIe adapter is needed. - - For AM65x boards, remove any jumpers present in the SERDES card when - operating in endpoint mode. - - .. Image:: /images/MPCIe-to-PCIe_Adapter.jpg - .. ifconfig:: CONFIG_part_family in ('J7_family') Following is an image of two J721E EVMs connected back to back. There is no @@ -245,104 +181,6 @@ The default dts is configured to be used in root complex mode. In order to use it in endpoint mode, the following changes have to be made in dts file. -.. ifconfig:: CONFIG_part_family in ('General_family') - - To configure dra7-evm in EP mode: - - :: - - diff --git a/arch/arm/boot/dts/dra7-evm.dts b/arch/arm/boot/dts/dra7-evm.dts - index eedd930..93d9f17 100644 - --- a/arch/arm/boot/dts/dra7-evm.dts - +++ b/arch/arm/boot/dts/dra7-evm.dts - @@ -1084,7 +1084,7 @@ - vdd-supply = <&smps7_reg>; - }; - - -&pcie1_rc { - +&pcie1_ep { - status = "okay"; - }; - - To configure dra72-evm in EP mode: - - :: - - diff --git a/arch/arm/boot/dts/dra72-evm-common.dtsi b/arch/arm/boot/dts/dra72-evm-common.dtsi - index f914e6a..9697ea3 100644 - --- a/arch/arm/boot/dts/dra72-evm-common.dtsi - +++ b/arch/arm/boot/dts/dra72-evm-common.dtsi - @@ -708,6 +708,6 @@ - watchdog-timers = <&timer10>; - }; - - -&pcie1_rc { - +&pcie1_ep { - status = "okay"; - }; - - To configure am572x-idk in EP mode: - - :: - - diff --git a/arch/arm/boot/dts/am572x-idk.dts b/arch/arm/boot/dts/am572x-idk.dts - index b2edeab..1ef70b3 100644 - --- a/arch/arm/boot/dts/am572x-idk.dts - +++ b/arch/arm/boot/dts/am572x-idk.dts - @@ -428,11 +428,11 @@ - }; - - &pcie1_rc { - - status = "okay"; - gpios = <&gpio3 23 GPIO_ACTIVE_HIGH>; - }; - - &pcie1_ep { - + status = "okay"; - gpios = <&gpio3 23 GPIO_ACTIVE_HIGH>; - }; - - To configure am65x-evm in EP mode: - - :: - - diff --git a/arch/arm64/boot/dts/ti/k3-am654-pcie-usb3.dtso b/arch/arm64/boot/dts/ti/k3-am654-pcie-usb3.dtso - index 3fc3c52aba80..789545d47e36 100644 - --- a/arch/arm64/boot/dts/ti/k3-am654-pcie-usb3.dtso - +++ b/arch/arm64/boot/dts/ti/k3-am654-pcie-usb3.dtso - @@ -14,9 +14,8 @@ - status = "okay"; - }; - - -&pcie1_rc { - +&pcie1_ep { - phys = <&serdes1 PHY_TYPE_PCIE 0>; - phy-names = "pcie-phy0"; - - reset-gpios = <&pca9555 5 GPIO_ACTIVE_HIGH>; - status = "okay"; - }; - - To configure am65x-idk in EP mode: - - :: - - diff --git a/arch/arm64/boot/dts/ti/k3-am654-pcie-usb2.dtso b/arch/arm64/boot/dts/ti/k3-am654-pcie-usb2.dtso - index f5c15bbdf029..b259a86e9d20 100644 - --- a/arch/arm64/boot/dts/ti/k3-am654-pcie-usb2.dtso - +++ b/arch/arm64/boot/dts/ti/k3-am654-pcie-usb2.dtso - @@ -46,10 +46,9 @@ - status = "okay"; - }; - - -&pcie0_rc { - +&pcie0_ep { - num-lanes = <2>; - phys = <&serdes0 PHY_TYPE_PCIE 1>, <&serdes1 PHY_TYPE_PCIE 1>; - phy-names = "pcie-phy0", "pcie-phy1"; - - reset-gpios = <&pca9555 5 GPIO_ACTIVE_HIGH>; - status = "okay"; - }; - .. ifconfig:: CONFIG_part_family in ('J7_family') .. rubric:: **10.x SDK (6.6 Kernel)** @@ -384,15 +222,6 @@ file. The following config options have to be enabled in order to configure the PCI controller to be used as a "Endpoint Test" function driver. -.. ifconfig:: CONFIG_part_family in ('General_family') - - :: - - CONFIG_PCI_ENDPOINT=y - CONFIG_PCI_EPF_TEST=y - CONFIG_PCI_DRA7XX_EP=y - - .. ifconfig:: CONFIG_part_family in ('AM64X_family','J7_family') :: @@ -407,13 +236,6 @@ PCI controller to be used as a "Endpoint Test" function driver. To find the list of endpoint controller devices in the system: -.. ifconfig:: CONFIG_part_family in ('General_family') - - :: - - # ls /sys/class/pci_epc/ - 51000000.pcie_ep - .. ifconfig:: CONFIG_part_family in ('AM64X_family','J7_family') .. parsed-literal:: @@ -423,13 +245,6 @@ To find the list of endpoint controller devices in the system: To find the list of endpoint function drivers in the system: -.. ifconfig:: CONFIG_part_family in ('General_family') - - :: - - # ls /sys/bus/pci-epf/drivers - pci_epf_test - .. ifconfig:: CONFIG_part_family in ('AM64X_family','J7_family') :: @@ -463,352 +278,6 @@ supported are: .. Image:: /images/pci-epf-test.png -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: 4.4 Kernel - - .. rubric:: Creating pci-epf-test device - - PCI endpoint function device can be created using the configfs. To - create pci-epf-test device, the following commands can be used: - - :: - - # mount -t configfs none /sys/kernel/config - # cd /sys/kernel/config/pci_ep/ - # mkdir pci_epf_test.0 - - The "mkdir pci\_epf\_test.0" above creates the pci-epf-test function - device. The name given to the directory preceding '.' should match with - the name of the driver listed in '/sys/bus/pci-epf/drivers' in order for - the device to be bound to the driver. - - The PCI endpoint framework populates the directory with configurable - fields. - - :: - - # cd pci_epf_test.0 - # ls - baseclass_code function revid vendorid - cache_line_size interrupt_pin subclass_code - deviceid peripheral subsys_id - epc progif_code subsys_vendor_id - - The driver populates these entries with default values when the device - is bound to the driver. The pci-epf-test driver populates vendorid with - 0xffff and interrupt\_pin with 0x0001. - - :: - - # cat vendorid - 0xffff - # cat interrupt_pin - 0x0001 - - | - - .. rubric:: Configuring pci-epf-test device - - The user can configure the pci-epf-test device using the configfs. In - order to change the vendorid and the number of MSI interrupts used by - the function device, the following commands can be used: - - :: - - # echo 0x104c > vendorid - # echo 16 > msi_interrupts - - .. rubric:: Binding pci-epf-test device to a EP controller - - In order for the endpoint function device to be useful, it has to be - bound to a PCI endpoint controller driver. Use the configfs to bind the - function device to one of the controller drivers present in the system. - - :: - - # echo "51000000.pcie_ep" > epc - - Once the above step is completed, the PCI endpoint is ready to establish - a link with the host. - - .. rubric:: 4.9 Kernel - - .. rubric:: Creating pci-epf-test device - - PCI endpoint function device can be created using the configfs. To - create pci-epf-test device, the following commands can be used: - - :: - - # mount -t configfs none /sys/kernel/config - # cd /sys/kernel/config/pci_ep/ - # mkdir dev - # mkdir dev/epf/pci_epf_test.0 - - The "mkdir dev/epf/pci\_epf\_test.0" above creates the pci-epf-test - function device. The name given to the directory preceding '.' should - match with the name of the driver listed in '/sys/bus/pci-epf/drivers' - in order for the device to be bound to the driver. - - The PCI endpoint framework populates the directory with configurable - fields. - - :: - - # ls dev/epf/pci_epf_test.0/ - baseclass_code function revid vendorid - cache_line_size interrupt_pin subclass_code - deviceid peripheral subsys_id - epc progif_code subsys_vendor_id - - The driver populates these entries with default values when the device - is bound to the driver. The pci-epf-test driver populates vendorid with - 0xffff and interrupt\_pin with 0x0001. - - :: - - # cat dev/epf/pci_epf_test.0/vendorid - 0xffff - # cat dev/epf/pci_epf_test.0/interrupt_pin - 0x0001 - - | - - .. rubric:: Configuring pci-epf-test device - - The user can configure the pci-epf-test device using the configfs. In - order to change the vendorid and the number of MSI interrupts used by - the function device, the following commands can be used: - - :: - - # echo 0x104c > dev/epf/pci_epf_test.0/vendorid - - The above command configures Texas Instruments as the vendor. - - If the endpoint is a DRA74x or AM572x device: - - :: - - # echo 0xb500 > dev/epf/pci_epf_test.0/deviceid - - If the endpoint is a DRA72x or AM572x device: - - :: - - # echo 0xb501 > dev/epf/pci_epf_test.0/deviceid - - The above command configures the deviceid. - - :: - - # echo 16 > dev/epf/pci_epf_test.0/msi_interrupts - - The above command configures the number of interrupts. 16 is the number of - interrupts being configured. The number of interrupts configured should be - between 1 to 32 for MSI. - - | - - .. rubric:: Binding pci-epf-test device to a EP controller - - In order for the endpoint function device to be useful, it has to be - bound to a PCI endpoint controller driver. Use the configfs to bind the - function device to one of the controller drivers present in the system. - - :: - - # echo "51000000.pcie_ep" > dev/epc - - Once the above step is completed, the PCI endpoint is ready to establish - a link with the host. - - .. rubric:: 4.14 Kernel - :name: pcie-end-point-4-14-kernel - - The following steps should be followed for the upstreamed solution (from - 4.12 kernel). The custom solution used in 4.9/4.4 should not be used for - upstreamed solution. - - .. rubric:: Creating pci-epf-test device - - PCI endpoint function device can be created using the configfs. To - create pci-epf-test device, the following commands can be used: - - :: - - # mount -t configfs none /sys/kernel/config - # cd /sys/kernel/config/pci_ep/ - - In the case of dra7x/am57x, use the below command to create - pci-epf-test function device. - - :: - - # mkdir functions/pci_epf_test/func1 - - In the case of k2g, use the below command to create - pci-epf-test function device. - - :: - - # mkdir functions/pci_epf_test_k2g/func1 - - In the case of am65x, use the below command to create - pci-epf-test function device. - - :: - - # mkdir functions/pci_epf_test_am6/func1 - - The PCI endpoint framework populates the directory with configurable - fields. - - All the commands below use pci_epf_test. However depending on the platform - pci_epf_test or pci_epf_test_k2g or pci_epf_test_am6 should be used. - - :: - - # ls functions/pci_epf_test/func1 - baseclass_code function revid vendorid - cache_line_size interrupt_pin subclass_code - deviceid peripheral subsys_id - epc progif_code subsys_vendor_id - - The driver populates these entries with default values when the device - is bound to the driver. The pci-epf-test driver populates vendorid with - 0xffff and interrupt\_pin with 0x0001. - - :: - - # cat functions/pci_epf_test/func1/vendorid - 0xffff - # cat functions/pci_epf_test/func1/interrupt_pin - 0x0001 - - | - - .. rubric:: Configuring pci-epf-test device - - The user can configure the pci-epf-test device using the configfs. In - order to change the vendorid and the number of MSI interrupts used by - the function device, the following commands can be used: - - :: - - # echo 0x104c > functions/pci_epf_test/func1/vendorid - - The above command configures Texas Instruments as the vendor. - - If the endpoint is a DRA74x or AM572x device: - - :: - - # echo 0xb500 > functions/pci_epf_test/func1/deviceid - - If the endpoint is a DRA72x or AM572x device: - - :: - - # echo 0xb501 > functions/pci_epf_test/func1/deviceid - - If the endpoint is K2G device: - - :: - - # echo 0xb00b > functions/pci_epf_test_k2g/func1/deviceid - - If the endpoint is AM6 device: - - :: - - # echo 0xb00c > functions/pci_epf_test_am6/func1/deviceid - - The above command configures the deviceid. - - :: - - # echo 16 > functions/pci_epf_test/func1/msi_interrupts - - The above command configures the number of interrupts. 16 is the number of - interrupts being configured. The number of interrupts configured should be - between 1 to 32 for MSI. - - .. rubric:: Binding pci-epf-test device to a EP controller - - In order for the endpoint function device to be useful, it has to be - bound to a PCI endpoint controller driver. Use the configfs to bind the - function device to one of the controller drivers present in the system. - - If the endpoint is a DRA72x or AM572x device: - :: - - # ln -s functions/pci_epf_test/func1 controllers/51000000.pcie_ep/ - - If the endpoint is a K2G device: - :: - - # ln -s functions/pci_epf_test_k2g/func1 controllers/21800000.pcie-ep/ - - If the endpoint is a AM654-EVM device: - :: - - # ln -s functions/pci_epf_test_am6/func1 controllers/5600000.pcie-ep - - If the endpoint is a AM654-IDK device: - :: - - # ln -s functions/pci_epf_test_am6/func1 controllers/5500000.pcie-ep - - .. rubric:: Starting the EP device - - In order for the EP device to be ready to establish the link, the - following command should be given. - - If the endpoint is a DRA72x or AM572x device: - :: - - # echo 1 > controllers/51000000.pcie_ep/start - - If the endpoint is a K2G device: - :: - - # echo 1 > controllers/21800000.pcie-ep/start - - If the endpoint is a AM654-EVM device: - :: - - # echo 1 > controllers/5600000.pcie-ep/start - - If the endpoint is a AM654-IDK device: - :: - - # echo 1 > controllers/5500000.pcie-ep/start - - Once the above step is completed, the PCI endpoint is ready to establish - a link with the host. - - - .. rubric:: *K2G Limitation* - - K2G outbound transfers has a limitation that the target address should - be aligned to a minimum of 1MB address. This restriction is because of - PCIE\_OB\_OFFSET\_INDEXn where BITS 1 to 19 is reserved. (Please note - 1MB is minimum alignment and it can be changed to 1MB/2MB/4MB/8MB by - specifying it in PCIE\_OB\_SIZE register). - - Outbound transfers are used by PCI endpoint to access RC's memory and - for raising MSI interrupts. So with 1MB restriction both RC memory and - MSI interrupts will be impacted since standard linux API's like - dma\_alloc\_coherent, get\_free\_pages etc.. doesn't give 1MB aligned - memory. While custom driver can be created to get 1MB aligned memory for - accessing RC's memory, MSI memory is allocated by RC controller driver - and there is no way to tell it to give 1MB aligned address. - - These restrictions are not specified in PCI standard and is bound to - cause issues for 66AK2G users. - .. ifconfig:: CONFIG_part_family in ('AM64X_family','J7_family') .. rubric:: Creating pci-epf-test device @@ -1007,14 +476,6 @@ support. The following config options have to be enabled in order to use the "Endpoint Test" PCI device. -.. ifconfig:: CONFIG_part_family in ('General_family') - - :: - - CONFIG_PCI=y - CONFIG_PCI_ENDPOINT_TEST=y - CONFIG_PCI_DRA7XX_HOST=y - .. ifconfig:: CONFIG_part_family in ('AM64X_family','J7_family') :: @@ -1025,13 +486,6 @@ The following config options have to be enabled in order to use the .. rubric:: *lspci output* -.. ifconfig:: CONFIG_part_family in ('General_family') - - :: - - 00:00.0 PCI bridge: Texas Instruments Device 8888 (rev 01) - 01:00.0 Unassigned class [ff00]: Texas Instruments Device b500 - .. ifconfig:: CONFIG_part_family in ('J7_family') :: @@ -1055,110 +509,6 @@ The following config options have to be enabled in order to use the .. rubric:: *Using the Endpoint Test function device* -.. ifconfig:: CONFIG_part_family in ('General_family') - - pci\_endpoint\_test driver creates the Endpoint Test function device - (/dev/pci-endpoint-test.0) which will be used by the following pcitest - utility. pci\_endpoint\_test can either be built-in to the kernel or - built as a module. For testing legacy interrupt, MSI interrupt has to be - disabled in the host. - - In order to not enable MSI (for testing legacy interrupt in DRA7) - - :: - - insmod pci_endpoint_test.ko no_msi=1 - - Please note MSI interrupt by default is not enabled for K2G. - - pcitest.sh added in tools/pci/ can be used to run all the default PCI - endpoint tests. Before pcitest.sh can be used, pcitest.c should be - compiled using - - :: - - cd - make headers_install ARCH=arm - arm-linux-gnueabihf-gcc -Iusr/include tools/pci/pcitest.c -o pcitest - cp pcitest /usr/sbin/ - cp tools/pci/pcitest.sh - - .. rubric:: pcitest.sh output - - :: - - root@dra7xx-evm:~# ./pcitest.sh - BAR tests - - :: - - BAR0: OKAY - BAR1: OKAY - BAR2: OKAY - BAR3: OKAY - BAR4: NOT OKAY - BAR5: NOT OKAY - - Interrupt tests - - LEGACY IRQ: NOT OKAY - MSI1: OKAY - MSI2: OKAY - MSI3: OKAY - MSI4: OKAY - MSI5: OKAY - MSI6: OKAY - MSI7: OKAY - MSI8: OKAY - MSI9: OKAY - MSI10: OKAY - MSI11: OKAY - MSI12: OKAY - MSI13: OKAY - MSI14: OKAY - MSI15: OKAY - MSI16: OKAY - MSI17: NOT OKAY - MSI18: NOT OKAY - MSI19: NOT OKAY - MSI20: NOT OKAY - MSI21: NOT OKAY - MSI22: NOT OKAY - MSI23: NOT OKAY - MSI24: NOT OKAY - MSI25: NOT OKAY - MSI26: NOT OKAY - MSI27: NOT OKAY - MSI28: NOT OKAY - MSI29: NOT OKAY - MSI30: NOT OKAY - MSI31: NOT OKAY - MSI32: NOT OKAY - - Read Tests - - READ ( 1 bytes): OKAY - READ ( 1024 bytes): OKAY - READ ( 1025 bytes): OKAY - READ (1024000 bytes): OKAY - READ (1024001 bytes): OKAY - - Write Tests - - WRITE ( 1 bytes): OKAY - WRITE ( 1024 bytes): OKAY - WRITE ( 1025 bytes): OKAY - WRITE (1024000 bytes): OKAY - WRITE (1024001 bytes): OKAY - - Copy Tests - - COPY ( 1 bytes): OKAY - COPY ( 1024 bytes): OKAY - COPY ( 1025 bytes): OKAY - COPY (1024000 bytes): OKAY - COPY (1024001 bytes): OKAY - .. ifconfig:: CONFIG_part_family in ('AM64X_family','J7_family') pci\_endpoint\_test driver creates the Endpoint Test function device which @@ -1222,48 +572,6 @@ The following config options have to be enabled in order to use the .. rubric:: **Files** -.. ifconfig:: CONFIG_part_family in ('General_family') - - +-----------+---------------------------------------------------+-----------------------------------+ - | Serial No | Location | Description | - +===========+===================================================+===================================+ - | 1 | drivers/pci/endpoint/pci-epc-core.c | PCI Endpoint Framework | - + +---------------------------------------------------+ + - | | drivers/pci/endpoint/pci-ep-cfs.c | | - + +---------------------------------------------------+ + - | | drivers/pci/endpoint/pci-epc-mem.c | | - + +---------------------------------------------------+ + - | | drivers/pci/endpoint/pci-epf-core.c | | - +-----------+---------------------------------------------------+-----------------------------------+ - | 2 | drivers/pci/endpoint/functions/pci-epf-test.c | PCI Endpoint Function Driver | - +-----------+---------------------------------------------------+-----------------------------------+ - | 3 | drivers/misc/pci_endpoint_test.c | PCI Driver | - +-----------+---------------------------------------------------+-----------------------------------+ - | 4 | tools/pci/pcitest.c | PCI Userspace Tools | - + +---------------------------------------------------+ + - | | tools/pci/pcitest.sh | | - +-----------+---------------------------------------------------+-----------------------------------+ - | 5 | **4.4 Kernel** | PCI Controller Driver | - + +---------------------------------------------------+ + - | | drivers/pci/controller/pci-dra7xx.c | | - + +---------------------------------------------------+ + - | | drivers/pci/controller/pcie-designware.c | | - + +---------------------------------------------------+ + - | | drivers/pci/controller/pcie-designware-ep.c | | - + +---------------------------------------------------+ + - | | drivers/pci/controller/pcie-designware-host.c | | - + +---------------------------------------------------+ + - | | **4.4 Kernel** | | - + +---------------------------------------------------+ + - | | drivers/pci/dwc/pci-dra7xx.c | | - + +---------------------------------------------------+ + - | | drivers/pci/dwc/pcie-designware.c | | - + +---------------------------------------------------+ + - | | drivers/pci/dwc/pcie-designware-ep.c | | - + +---------------------------------------------------+ + - | | drivers/pci/dwc/pcie-designware-host.c | | - +-----------+---------------------------------------------------+-----------------------------------+ - .. ifconfig:: CONFIG_part_family in ('AM64X_family','J7_family') +-----------+---------------------------------------------------+-----------------------------------+ diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Root_Complex.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Root_Complex.rst index 453d425fd..8999274d8 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Root_Complex.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Root_Complex.rst @@ -13,488 +13,6 @@ technology succeeding ISA and PCI bus that is designed to be used as a general-purpose serial I/O interconnect in multiple market segments, including desktop, mobile, server, storage and embedded communications. -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: Keystone PCIe - :name: keystone-pcie - - Keystone PCIe module is used on K2H/K2K, K2E, K2L and K2G SoCs. For more - details on the module specification, please refers to sprugs6d.pdf - documentation provided at ti.com. The K2G PCIe module spec is part of - spruhy8d.pdf. - - .. rubric:: Supported platforms - :name: supported-platforms - - SoCs: K2E, K2G - - Keystone PCIe driver may be used on K2L/K2HK and boards/EVMs using these - SoCs, but is not validated since nothing is hooked to PCIe port on these - EVMs. - - K2E EVM has a Marvel SATA controller (88se9182) hooked to PCIe port 1. - The Driver is validated by connecting a SATA hard disk to the SATA port - available on the EVM. K2G EVM has a single x1 PCIe slot which accepts - standard PCIe cards. Following PCIe cards are validated for basic - functionality on K2G EVM:- - - :: - - * Ethernet: Broadcom Corporation NetXtreme BCM5721 Gigabit (tg3 driver) - * Intel Corporation 82572EI Gigabit Ethernet (e1000e driver) - * USB: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host - * SATA: Marvell Technology Group Ltd. 88SE9120 SATA 6Gb/s - - K2G EVM: Make sure following jumper settings on the EVM:- - - :: - - * J44: put stub to short pin 1 & 2. This ensure proper reset to PCIe slot - * J15: put stub to short pin 2 & 3. This ensures 100MHz clock to PCIe slot - - | - - .. rubric:: Introduction to PCIe on TI Keystone platforms - :name: introduction-linux-pcie - - The TI Keystone platforms contain a PCI Express module which supports a - multi-lane I/O interconnect providing low pin count, high reliability, - and high-speed data transfer at rates of up to 5.0 Gbps per lane per - direction, The module supports Root Complex and End Point operation - modes. - - The PCIe driver implemented supports only the Root Complex (RC) - operation mode on K2 platforms (K2HK, K2E). The PCIe driver is designed - based on PCIE Designware Core driver. The Designware Core driver is - enhanced to support Keystone PCIe driver in the mainline kernel. The - diagram below shows the various drivers that Keystone PCI depends on to - implement the RC driver. PCI Designware Core driver provides a set of - function calls defined in drivers/pci/host/pcie-designware.h for - platform drivers to implement the RC driver. Keystone PCI module - required some enhancements to designware core because of the application - register space which otherwise is part of the designware core. These - keystone specific handling of the driver is re-factored into PCI - Keystone DW Core Driver and used from PCI Keystone platform driver. This - includes MSI/Legacy IRQ handling, Read/Write functions to write over the - PCI bus etc which are unique for Keystone PCI driver. - - :: - - Callbacks - |------------------| |--------------------| |---------------------| |---------------| - | PCI Keystone |<------| PCI Keystone DW |<------| PCI Designware Core | | | - | Platform Driver |------>| Core Driver |------>| Driver |-------| PCI Core | - | (pci-keystone.c) | | pci-keystone-dw.c | | pcie-designware.c | | | - |------------------| |--------------------| |---------------------| |---------------| - function calls function calls - - | - | PCIe has been verified on K2E EVM. K2E supports two PCI ports. Port 0 - is on Domain 0 and Port 1 is on Domain 1. On K2E EVM, a Marvel SATA - controller, 0x9182 is connected to port 1 that supports interfacing - with Hard disk drives (HDD). Following h/w setup is used to test SATA - HDD interface with K2E. Western Digital 1.0 TB SATA / 64MB Cache hard - disk drive, WD10EZEX is used for the test over PCI port 1. - - | - - :: - - ----------- SATA 6Gbps data cable ------------ - | WD10EZEX | --------------------------> | K2E EVM | - ----------- ------------ - ^ - | - (External power supply) - - Connect HDD to an external power supply. Connect the HDD SATA port to - K2E EVM SATA port using a 6Gbps data cable and power on the HDD. Power - On K2E EVM. The K2E rev 1.0.2.0 requires a hardware modification to get - the SATA detection on the PCI bus. Please check with EVM hardware vendor - for the details. - - For K2G EVM, there is a PCIe slot available to work with standard PCIe - cards. For example to test PCIe SATA as in K2E, connect the hard disk - SATA cables to the PCIe SATA controller card and insert the card into - the PCIe slot and Power on the EVM. Other PCIe cards can be tested in a - similar way. - - .. rubric:: Driver Configuration - :name: driver-configuration-pcierc - - Assume, you have default configuration set for kernel build. To enable - PCI Keystone driver, traverse the following config tree from menuconfig - - :: - - Bus support ---> - [*] PCI support - [*] Message Signaled Interrupts (MSI and MSI-X) - [ ] PCI Debugging - [ ] Enable PCI resource re-allocation detection - ...... - PCI host controller drivers ---> - [ ] Generic PCI host controller - [*] TI Keystone PCIe controller - - The RC driver can be built into the kernel as a static module. - - | - - .. rubric:: Device Tree bindings - :name: device-tree-bindings - - DT documentation is at - Documentation/devicetree/bindings/pci/pci-keystone.txt in the kernel - source tree. The PCIE SerDes Phy related DT documentation is available - at Documentation/devicetree/bindings/phy/ti-phy.txt - - | - - .. rubric:: Driver Source location - :name: driver-source-location - - The driver code is located at drivers/pci/host - - :: - - Files: pci-keystone.c - pci-keystone-dw.c - pci-keystone.h - - | - | The PCIe PHY (SerDes) contains the analog portion of the PHY, which is - the transmission line channel that is used to transmit and receive - data. It contains a phase locked loop, analog transceiver, phase - interpolator-based clock/data recovery, parallel-to-serial converter, - serial-to-parallel converter, scrambler, configuration, and test - logic. - - PCI driver calls into Phy SerDes driver to initialize PCI Phy (SerDes). - From PCI probe function, phy\_init() is called which results in SerDes - initialization. The SerDes code is a common driver used across all sub - systems such as SGMII, PCIe and 10G. The driver code for this located at - drivers/phy/phy-keystone-serdes.c - - .. rubric:: Limitations - :name: limitations - - - PCIe is verified only on K2E and K2G EVMs - - AER error interrupt is not handled by PCIE AER driver for Keystone as - this uses non standard platform interrupt - - ASPM interrupt is non standard on Keystone and the same is not - handled by the PCIe ASPM driver. - - | - - .. rubric:: U-Boot environment/scripts - :name: u-boot-environmentscripts - - The Keystone PCIe SerDes Phy hardware requires a firmware to configure - the Phy to work as a PCIe phy. As Keystone PCIe is statically built into - the kernel, this firmware is needed when Phy SerDes driver is probed. - When initramfs is used as the final rootfs, this firmware can reside at - /lib/firmware folder of the fs. For other boot modes (mmc, ubi, nfs), - k2-fw-initrd.cpio.gz has this firmware and can be loaded to memory and - the address is passed to kernel through second argument of bootm - command. Following env scripts are used to customize the u-boot - environment for various boot modes so that firmware is available to - initialize the phy SerDes when Phy SerDes driver is probed. - - firmware file ks2\_pcie\_serdes.bin is available in - ti-linux-firmware.git at ti-keystone folder or at /lib/firmware folder - of the file system images shipped with the release or under /lib/firmare - folder of the k2-fw-initrd.cpio.gz shipped with the release). If you are - using your own file system, make sure ks2\_pcie\_serdes.bin resides at - /lib/firmware folder. - - Setup u-boot env as follows. These are expected to be available in the - default env variable, but check and update it if not present. - - | - | Update init\_\* variables - - :: - - setenv init_fw_rd_mmc 'load mmc ${bootpart} ${rdaddr} ${bootdir}/${name_fw_rd}; run set_rd_spec' - setenv init_fw_rd_net 'dhcp ${rdaddr} ${tftp_root}/${name_fw_rd}; run set_rd_spec' - setenv init_fw_rd_ramfs 'setenv rd_spec - ' - setenv init_fw_rd_ubi 'ubifsload ${rdaddr} ${bootdir}/${name_fw_rd}; run set_rd_spec' - setenv set_rd_spec 'setenv rd_spec ${rdaddr}:${filesize}' - setenv name_fw_rd 'k2-fw-initrd.cpio.gz' - - Add init\_fw\_rd\_${boot} to bootcmd. - - :: - - setenv bootcmd 'run envboot; run set_name_pmmc init_${boot} init_fw_rd_${boot} get_pmmc_${boot} run_pmmc get_fdt_${boot} get_mon_${boot} get_kern_${boot} run_mon run_kern' - - | - - .. rubric:: Procedure to boot Linux with FS on hard disk - :name: procedure-to-boot-linux-with-fs-on-hard-disk - - .. rubric:: Enable AHCI, ATA drivers - :name: enable-ahci-ata-drivers - - Assume, you have default configuration set for kernel build. Both AHCI - and ATA drivers are to be enabled to build statically into the kernel - image if rootfs is mounted from the hard disk. Otherwise, if hard disk - is used as a storage device, the below drivers can be built as dynamic - modules and loaded from user space. - - From Kernel menuconfig, traverse the configuration tree as follows:- - - :: - - Device Drivers ---> - --------- - < > ATA/ATAPI/MFM/RLL support (DEPRECATED) ---- - SCSI device support ---> - <*> Serial ATA and Parallel ATA drivers (libata) ---> - *** Controllers with non-SFF native interface *** - <*> AHCI SATA support - <*> Platform AHCI SATA support - < > CEVA AHCI SATA support - ----------------- - *** Generic fallback / legacy drivers *** - <*> Generic ATA support - < > Legacy ISA PATA support (Experimental) - [ ] Multiple devices driver support (RAID and LVM) ---- - - - Boot Linux kernel on K2E EVM using NFS file system or Ramfs and using - rootfs provided in the SDK. Make sure SATA HDD is connected to EVM as - explained above and SATA EP is detected during boot up. This example - uses a 1TB HDD and create two partition. First partition is for - filesystem and is 510GB and second is for swap and is 256MB. - - | - - .. rubric:: Create partition with fdisk - :name: create-partition-with-fdisk - - First step is to create 2 partitions using fdisk command. At Linux - console type the following commands - - :: - - root@keystone-evm:~# fdisk /dev/sda - Welcome to fdisk (util-linux 2.21.2). - - Changes will remain in memory only, until you decide to write them. - Be careful before using the write command. - - :: - - Device does not contain a recognized partition table - Building a new DOS disklabel with disk identifier 0x9b51b66e. - - The device presents a logical sector size that is smaller than - the physical sector size. Aligning to a physical sector (or optimal - I/O) size boundary is recommended, or performance may be impacted. - - Command (m for help): m - Command action - a toggle a bootable flag - b edit bsd disklabel - c toggle the dos compatibility flag - d delete a partition - l list known partition types - m print this menu - n add a new partition - o create a new empty DOS partition table - p print the partition table - q quit without saving changes - s create a new empty Sun disklabel - t change a partition's system id - u change display/entry units - v verify the partition table - w write table to disk and exit - x extra functionality (experts only) - - Command (m for help): n - Partition type: - p primary (0 primary, 0 extended, 4 free) - e extended - Select (default p): p - Partition number (1-4, default 1): 1 - First sector (2048-1953525167, default 2048): 2048 - Last sector, +sectors or +size{K,M,G} (2048-1953525167, default 1953525167): +510G - Partition 1 of type Linux and of size 510 GiB is set - - :: - - Command (m for help): n - Partition type: - p primary (1 primary, 0 extended, 3 free) - e extended - Select (default p): p - Partition number (1-4, default 2): 2 - First sector (1069549568-1953525167, default 1069549568): - Using default value 1069549568 - Last sector, +sectors or +size{K,M,G} (1069549568-1953525167, default 1953525167): +256M - Partition 2 of type Linux and of size 256 MiB is set - - :: - - Command (m for help): p - - :: - - Disk /dev/sda: 1000.2 GB, 1000204886016 bytes - 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors - Units = sectors of 1 * 512 = 512 bytes - Sector size (logical/physical): 512 bytes / 4096 bytes - I/O size (minimum/optimal): 4096 bytes / 4096 bytes - Disk identifier: 0x9b51b66e - Device Boot Start End Blocks Id System - /dev/sda1 2048 1069549567 534773760 83 Linux - /dev/sda2 1069549568 1070073855 262144 83 Linux - - :: - - Command (m for help): p - - :: - - Disk /dev/sda: 1000.2 GB, 1000204886016 bytes - 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors - Units = sectors of 1 * 512 = 512 bytes - Sector size (logical/physical): 512 bytes / 4096 bytes - I/O size (minimum/optimal): 4096 bytes / 4096 bytes - Disk identifier: 0x9b51b66e - - Device Boot Start End Blocks Id System - /dev/sda1 2048 1069549567 534773760 83 Linux - /dev/sda2 1069549568 1070073855 262144 83 Linux - - Command (m for help): t - Partition number (1-4): 2 - Hex code (type L to list codes): L - - 0 Empty 24 NEC DOS 81 Minix / old Lin bf Solaris - 1 FAT12 27 Hidden NTFS Win 82 Linux swap / So c1 DRDOS/sec (FAT- - 2 XENIX root 39 Plan 9 83 Linux c4 DRDOS/sec (FAT- - 3 XENIX usr 3c PartitionMagic 84 OS/2 hidden C: c6 DRDOS/sec (FAT- - 4 FAT16 <32M 40 Venix 80286 85 Linux extended c7 Syrinx - 5 Extended 41 PPC PReP Boot 86 NTFS volume set da Non-FS data - 6 FAT16 42 SFS 87 NTFS volume set db CP/M / CTOS / . - 7 HPFS/NTFS/exFAT 4d QNX4.x 88 Linux plaintext de Dell Utility - 8 AIX 4e QNX4.x 2nd part 8e Linux LVM df BootIt - 9 AIX bootable 4f QNX4.x 3rd part 93 Amoeba e1 DOS access - a OS/2 Boot Manag 50 OnTrack DM 94 Amoeba BBT e3 DOS R/O - b W95 FAT32 51 OnTrack DM6 Aux 9f BSD/OS e4 SpeedStor - c W95 FAT32 (LBA) 52 CP/M a0 IBM Thinkpad hi eb BeOS fs - e W95 FAT16 (LBA) 53 OnTrack DM6 Aux a5 FreeBSD ee GPT - f W95 Ext'd (LBA) 54 OnTrackDM6 a6 OpenBSD ef EFI (FAT-12/16/ - 10 OPUS 55 EZ-Drive a7 NeXTSTEP f0 Linux/PA-RISC b - 11 Hidden FAT12 56 Golden Bow a8 Darwin UFS f1 SpeedStor - 12 Compaq diagnost 5c Priam Edisk a9 NetBSD f4 SpeedStor - 14 Hidden FAT16 <3 61 SpeedStor ab Darwin boot f2 DOS secondary - 16 Hidden FAT16 63 GNU HURD or Sys af HFS / HFS+ fb VMware VMFS - 17 Hidden HPFS/NTF 64 Novell Netware b7 BSDI fs fc VMware VMKCORE - 18 AST SmartSleep 65 Novell Netware b8 BSDI swap fd Linux raid auto - 1b Hidden W95 FAT3 70 DiskSecure Mult bb Boot Wizard hid fe LANstep - 1c Hidden W95 FAT3 75 PC/IX be Solaris boot ff BBT - 1e Hidden W95 FAT1 80 Old Minix - Hex code (type L to list codes): 82 - Changed system type of partition 2 to 82 (Linux swap / Solaris) - - Command (m for help): p - - Disk /dev/sda: 1000.2 GB, 1000204886016 bytes - 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors - Units = sectors of 1 * 512 = 512 bytes - Sector size (logical/physical): 512 bytes / 4096 bytes - I/O size (minimum/optimal): 4096 bytes / 4096 bytes - Disk identifier: 0x9b51b66e - - Device Boot Start End Blocks Id System - /dev/sda1 2048 1069549567 534773760 83 Linux - /dev/sda2 1069549568 1070073855 262144 82 Linux swap / Solaris - - | - - .. rubric:: Format partitions - :name: format-partitions - - :: - - root@k2e-evm~# mkfs.ext4 /dev/sda1 - mke2fs 1.42.1 (17-Feb-2012) - Filesystem label= - OS type: Linux - Block size=4096 (log=2) - Fragment size=4096 (log=2) - Stride=0 blocks, Stripe width=0 blocks - 33423360 inodes, 133693440 blocks - 6684672 blocks (5.00%) reserved for the super user - First data block=0 - Maximum filesystem blocks=0 - 4080 block groups - 32768 blocks per group, 32768 fragments per group - 8192 inodes per group - Superblock backups stored on blocks: - 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, - 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, - 102400000 - - :: - - Allocating group tables: done - Writing inode tables: done - Creating journal (32768 blocks): done - Writing superblocks and filesystem accounting information: done - - root@k2e-evm:~# ls -ltr /dev/sda* - brw-rw---- 1 root disk 8, 2 Sep 21 14:37 /dev/sda2 - brw-rw---- 1 root disk 8, 0 Sep 21 14:37 /dev/sda - brw-rw---- 1 root disk 8, 1 Sep 21 14:40 /dev/sda1 - - .. rubric:: Copy filesystem to rootfs - :name: copy-filesystem-to-rootfs - - This procedure assumes the cpio file for SDK filesystem is available on - the NFS or ramfs. - - :: - - >mkdir /mnt/test - >mount -t ext4 /dev/sda1 /mnt/test - >cd /mnt/test - >cpio -i -v .cpio - >cd / - >umount /mnt/test - - Where rootfs.cpio is the cpio file for the SDK fileystem. - - | - - .. rubric:: Booting with FS on harddisk - :name: booting-with-fs-on-harddisk - - Once the harddisk is formatted and has a rootfs installed, following - procedure can be used to boot Linux kernel using this rootfs. - - Boot EVM to u-boot prompt. Add following env variables to u-boot - environment :- - - :: - - K2E EVM # setenv boot hdd - K2E EVM # setenv get_fdt_hdd 'dhcp ${fdtaddr} ${tftp_root}/${name_fdt}' - K2E EVM # setenv init_fw_rd_hdd 'dhcp ${rdaddr} ${tftp_root}/${name_fw_rd}; run set_rd_spec' - K2E EVM # setenv get_kern_hdd 'dhcp ${loadaddr} ${tftp_root}/${name_kern}' - K2E EVM # setenv get_mon_hdd 'dhcp ${addr_mon} ${tftp_root}/${name_mon}' - K2E EVM # setenv init_hdd 'run args_all args_hdd' - K2E EVM # setenv args_hdd 'setenv bootargs ${bootargs} rw root=/dev/sda1' - K2E EVM # saveenv - - Now type boot command and boot to Linux. The above steps can be skipped - once u-boot implements these env variables by default which is expected - to be supported in the future. - .. ifconfig:: CONFIG_part_variant in ('AM64X') .. rubric:: **Features of AM64** diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/SPI.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/SPI.rst index b05b1d9ad..ede3a47f6 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/SPI.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/SPI.rst @@ -54,7 +54,7 @@ Note this isn't meant to be an exhaustive list and only takes into account features the SPI peripheral in the SoC is capable of but is currently not supported in the Linux driver. -.. ifconfig:: CONFIG_part_family in ('J7_family', 'General_family', 'AM335X_family', 'AM437X_family') +.. ifconfig:: CONFIG_part_family in ('J7_family', 'AM335X_family', 'AM437X_family') - SPI slave mode is supported only with DMA enabled. diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD.rst index 215989916..6d654c676 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD.rst @@ -18,7 +18,7 @@ such as a microprocessor unit (MPU) or digital signal processor (DSP) and either secure digital (SD), or secure digital input/output (SDIO) devices. The MMCSD host controller handles MMCSD and SDIO protocol with minimal LH intervention. -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') Main features of the MMCSD host controllers: @@ -50,7 +50,7 @@ References Features ******** -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') The SD driver supports the following features: @@ -82,7 +82,7 @@ Features Supported ultra high speed (UHS) modes ************************************** -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM57X_family', 'AM65X_family') +.. ifconfig:: CONFIG_part_family in ('AM57X_family', 'AM65X_family') +--------------------+--------+-------+-------+-------+-------+ | Platform | SDR104 | DDR50 | SDR50 | SDR25 | SDR12 | @@ -230,7 +230,7 @@ Supported ultra high speed (UHS) modes Driver configuration ******************** -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') The default kernel configuration enables support for MMCSD(built-in to kernel). @@ -305,7 +305,7 @@ Driver configuration MMC/SD/SDIO card support --> <*> Support for the SDHCI Controller in TI's AM654 SOCs -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. rubric:: **Enabling eMMC Card Background operations support** :name: enabling-emmc-card-background-operations-support @@ -414,7 +414,7 @@ MMC support in Linux Steps for working around SD card issues in Linux ************************************************ -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM57X_family', 'AM335X_family', 'AM437X_family') +.. ifconfig:: CONFIG_part_family not in ('AM57X_family', 'AM335X_family', 'AM437X_family') In some cases, failures can be seen while using some SD cards: @@ -527,7 +527,7 @@ Steps for working around SD card issues in Linux sdhci2: mmc@fa20000 { -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM57X_family', 'AM335X_family', 'AM437X_family') +.. ifconfig:: CONFIG_part_family in ('AM57X_family', 'AM335X_family', 'AM437X_family') Steps for working around SD card issues in Linux documentation is pending for |__PART_FAMILY_DEVICE_NAMES__| please reach out to: `Help e2e `__ for additional information. diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/DWC3.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/DWC3.rst index 62fbfdce4..b66146124 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/DWC3.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/DWC3.rst @@ -23,96 +23,6 @@ The SuperSpeed USB controller features: DWC3 is integrated in AM65x, OMAP5, DRA7x and AM437x SoCs from TI. -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: OMAP5 (omap5-uevm) - :name: omap5-omap5-uevm - - The following diagram depicts dwc3 integration in OMAP5. The ID and VBUS - events are sensed by a companion device (palmas). The palmas-usb driver - (drivers/extcon/extcon-palmas.c) notifies the events to OMAP glue driver - (driver/usb/dwc3/dwc3-omap.c) via the extcon framework. The glue driver - writes the events to the software mailbox present in DWC3 glue (SS USB - OTG controller module in the diagram) which interrupts the core using - UTMI+ signals. - - .. image:: /images/Omap5-dwc3.png - - .. rubric:: DRA7x/AM57x - :name: dra7xam57x - - The above diagram also depicts dwc3 integration in DRA7x/AM57x. Some - boards provide VBUS and ID events over GPIO whereas some provide ID over - GPIO and VBUS through Power Management IC (palmas). - - - DRA7-evm (J6-evm) and DRA72-evm (J6-eco) boards have ID detection but - no VBUS detection support. ID detection is provided through GPIO - expander (PCF8574). - - DRA71-evm (J6entry-evm) board has VBUS and ID detection support. Both - ID and VBUS detection are provided through GPIO expander (PCF8574). - - On these boards, the GPIO driver (drivers/extcon/extcon-usb-gpio.c) - notifies the ID and VBUS events to the OMAP dwc3 glue - (drivers/usb/dwc3/dwc3-omap.c) via the extcon framework. - - All DRA7x boards use USB1 port as Super-Speed dual-role port and USB2 - port High-Speed Host port (Type mini-A). You will need a mini-A to - Type-A adapter to use the Host port. - - .. rubric:: AM57x (BeagleBoard-x15/AM57xx-evm/AM57xx-IDK) - :name: am57x-beagleboard-x15am57xx-evmam57xx-idk - - - BeagleBoard-x15/AM57xx-evm use USB1 as Super-Speed host port and have - a on-board Super-Speed hub which provides 3 Super-Speed Host (Type-A) - ports. USB2 is used as High-Speed peripheral port. VBUS detection for - USB2 port is provided through Power Management IC (palmas). The - palmas USB driver (drivers/extcon/extcon-palmas.c) notifies the VBUS - event to the OMAP dwc3 glue (drivers/usb/dwc3/dwc3-omap.c) via the - extcon framework. - - - AM57xx-IDK boards use USB1 as a High-Speed Host port (Type-A) and - USB2 as a High-Speed dual-role port. ID detection for USB2 is - provided via GPIO whereas VBUS detection is provided through the PMIC - (palmas). The palmas USB driver (drivers/extcon/extcon-palmas.c) - notifies both VBUS and ID events to the OMAP dwc3 glue - (drivers/usb/dwc3/dwc3-omap.c) via the extcon framework. - - .. rubric:: AM65x - :name: am65x - - AM65x has 2 DWC3 controller instances. USB1 instance can be a super-speed - port and USB2 instance is a high-speed port. - The following diagram depicts dwc3 integration in AM65x's high-speed port. - VBUS and ID detection is done internally so companion device is not needed. - DWC3 controller uses HW UTMI mode to get the VBUS and ID events and the glue - driver (dwc3-am65.c) does not need to write to the software mailbox to - notify the events to the dwc3 core. - - - On AM65x-evm/IDK, USB2 port is used as high-speed dual-role port (micro-AB) - as shown in figure below. - - .. note:: The board might come with force host jumper J4 pre-installed at the - factory. Please remove this jumper for proper dual-role/device-mode operation - of USB2 port. - - - On AM65x-IDK, USB1 port is available as a high-speed dual-role port (micro-AB) - through a 2Lane PCIe USB2 SERDES card. See below figure. - - .. note:: AM65x-IDK might come with the force host jumper J5 pre-installed - on the SERDES card. Please remove this jumper for proper dual-role/device mode - operation of USB1 port. - - .. Image:: /images/am65x-dwc3-usbhs.png - - - On AM65x-evm, USB1 port is available as a Super-Speed device or host port - (3.0 micro-AB) through a 1Lane PCIe USB3 SERDES card. See below figure. - - .. note:: AM65x-evm might come with the force host jumper J5 pre-installed - on the SERDES card. Please remove this jumper for proper dual-role/device mode - operation of USB1 port. - - .. Image:: /images/am65x-dwc3-usbss.png - .. ifconfig:: CONFIG_part_family in ('AM437X_family') The following diagram depicts dwc3 integration in AM437x. Super-Speed is @@ -289,72 +199,19 @@ Kernel Configuration tool. .. rubric:: **Configuring DWC3 in gadget only** :name: configuring-dwc3-in-gadget-only -.. ifconfig:: CONFIG_part_family in ('General_family') - - set 'dr\_mode' as 'peripheral' in respective board dts files present in - arch/arm/boot/dts/ - - - omap5-uevm.dts for OMAP5 - - dra7-evm.dts for DRA7x - .. ifconfig:: CONFIG_part_family in ('AM437X_family') set 'dr\_mode' as 'peripheral' in respective board dts files present in arch/arm/boot/dts/. For AM437x GP EVM, it is am437x-gp-evm.dts. -.. ifconfig:: CONFIG_part_family in ('General_family') - - :: - - Example: To configure both the ports of DRA7 as gadget (default usb2 is configured as 'host') - arch/arm/boot/dts/dra7-evm.dts - - &usb1 { - dr_mode = "peripheral"; - pinctrl-names = "default"; - pinctrl-0 = <&usb1_pins>; - }; - &usb2 { - dr_mode = "peripheral"; - pinctrl-names = "default"; - pinctrl-0 = <&usb2_pins>; - }; - .. rubric:: Configuring DWC3 in host only :name: configuring-dwc3-in-host-only -.. ifconfig:: CONFIG_part_family in ('General_family') - - set 'dr\_mode' as 'host' in respective board dts files present in - arch/arm/boot/dts/ - - - omap5-uevm.dts for OMAP5 - - dra7-evm.dts for DRA7x - .. ifconfig:: CONFIG_part_family in ('AM437X_family') set 'dr\_mode' as 'host' in respective board dts files present in arch/arm/boot/dts/. For AM437x GP EVM, it is am437x-gp-evm.dts. -.. ifconfig:: CONFIG_part_family in ('General_family') - - :: - - Example: To configure both the ports of DRA7 as host (default usb1 is configured as 'otg') - arch/arm/boot/dts/dra7-evm.dts - &usb1 { - dr_mode = "host"; - pinctrl-names = "default"; - pinctrl-0 = <&usb1_pins>; - }; - &usb2 { - dr_mode = "host"; - pinctrl-names = "default"; - pinctrl-0 = <&usb2_pins>; - }; - -| - .. rubric:: Testing :name: testing-kerel-dwc3 @@ -364,36 +221,6 @@ Kernel Configuration tool. .. rubric:: Selecting cables :name: selecting-cables -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: OMAP5-uevm - :name: omap5-uevm-kernel-dwc3 - - OMAP5-evm has a single Super-Speed micro AB port provided by the DWC3 - controller. To use it in host mode a OTG adapter (Micro USB 3.0 9-Pin - Male to USB 3.0 Female OTG Cable) like below should be used. The ID pin - within the adapter must be grounded. Some of the adapters available in - the market don't have ID pin grounded. If the ID pin is not grounded the - dual-role port will not switch from peripheral mode to host mode. - - .. Image:: /images/OMAP5-HOST.jpg - - .. rubric:: DRA7x-evm - :name: dra7x-evm - - DRA7x-evm has 2 USB ports provided by the DWC3 controllers. USB1 is a - Super-Speed port and USB2 is a High-Speed port. USB1 is by default - configured in dual-role mode and USB2 is configured in host mode. - - For connecting a device to the USB2 port use a mini-A to Type-A OTG - adapter cable like this. The ID pin within the adapter cable must be - grounded. - - .. Image:: /images/Dra7-HOST.jpg - - For using the USB1 port in host mode use a Super-Speed OTG adapter cable - similar to the one used in OMAP5. - .. ifconfig:: CONFIG_part_family in ('AM437X_family') AM437x GP EVM has two USB ports. USB0 is a dual-role port and USB1 is a host diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/MUSB.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/MUSB.rst index c400f8704..5e69ad6c9 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/MUSB.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/MUSB.rst @@ -166,19 +166,6 @@ Table: - musb\_am335x.ko can't be removed (and we don't allow that to happen) to workaround a known hwmod issue. -.. ifconfig:: CONFIG_part_family in ('General_family') - - - multi-gadget cannot be used on OMAP-L138 because of lack of - sufficient number of endpoints to support multiple functions - - high bandwidth ISO cannot be supported on OMAP-L138. On trying a high - bandwidth ISO transfer, you should see message of the form: - - :: - - musb-hdrc musb-hdrc.1.auto: high bandwidth iso (3x896) not supported - - This behaviour is expected. - .. rubric:: **References** :name: references diff --git a/source/linux/Foundational_Components/Kernel/_FAQs.rst b/source/linux/Foundational_Components/Kernel/_FAQs.rst index 738bcccf8..230fc77a8 100644 --- a/source/linux/Foundational_Components/Kernel/_FAQs.rst +++ b/source/linux/Foundational_Components/Kernel/_FAQs.rst @@ -35,94 +35,3 @@ to enable it again, [ 7792.869822] omap_rtc 48838000.rtc: rtc core: registered 48838000.rtc as rtc1 root@dra7xx-evm:/sys/bus/platform/drivers/omap_rtc# -| - -.. ifconfig:: CONFIG_part_family in ('General_family') - - **Q: Without SD card in K2H/E, what options are availabe for Keystone-2 platforms to boot kernel?** - - **A:** Keystone-2 platforms support the following ways of booting the kernel: - - * Network Boot - - Netowrk Boot is to boot the kernel from network which downloads the kernel, boot monitor, - and dtb images from TFTP server and uses NFS mounted filesystem. - - This requires the TFTP and NFS servers set up first. The u-boot scripts assume TFTP and NFS servers are - on the same system and the IP address is set in "server_ip". - - The prebuilt kernel, boot monitor, and dtb files are located in /board-support/prebuilt_images folder. - The filesystem tarballs are the .tar.xz files and in /filesystem folder. - The filesystem needs to be extracted from the tarball to the NFS mount point, e.g. /nfs/k2e_fs. - The corresponding NFS mount point needs to be exported on server through /etc/exports. - - To boot from network, the following u-boot environment variables need to be set: - - :: - - => setenv boot net - => setenv server_ip - => setenv tftp_root - => setenv nfs_root - => saveenv - => boot - - * UBI Boot - - UBI boot is the default setting which boots kernel using the UBIFS filesystem on the NAND. - K2H/E platforms have NAND programmed for out-of-box demo. If the NAND image is corrupted, - it can be re-programmed using prebuilt UBI image (.ubi files) in /filesystem folder. - - Execute the following u-boot scripts to re-program the NAND with UBI image: - - :: - - /* Download the UBI image from TFTP server */ - /* Beware of the UBI image size not to exceed the NAND capacity */ - => setenv server_ip - => setenv name_ubi - => setenv tftp_root - => run get_ubi_net - /* Program NAND with the downloaded image */ - => run burn_ubi - - To boot kernel using UBIFS filesystem on the NAND, the u-boot environment variable "boot" needs to be set to ubi: - - :: - - => setenv boot ubi - => saveenv - => boot - - * RAMFS boot - - RAMFS boot is similar to Network boot which downloads kernel, boot monitor, and dtb images from TFTP server. - The difference from Network boot is that it uses a compressed cpio archive file, not the NFS mounted filesystem through netowrk. - The cpio archive is downloaded to the Kernel RAM space instead. - - The compressed cpio archive is not included in the Processor SDK, but can be created from the released filesystem. - The size of the released filesystem has increased beyond 80MB. As a result, special attention needs to be on the - filesystem size used to create the cpio archive. The filesystem needs to be under 80MB for use with RAMFS. - - On the host machine where the Processor SDK is installed, issue the following commands to create the cpio archive file: - - :: - - host$ mkdir target_fs - host$ cd target_fs - host$ tar xf /filesystem/arago-base-tisdk-image-k2e-evm.tar.xz - host$ find . | cpio -H newc -o > ../target_fs.cpio - host$ cd .. - host$ gzip target_fs.cpio - - The target_fs.cpio.gz file needs to be copied to the TFTP directory and be used for RAMFS boot. - The u-boot environment variables need to be set as: - - :: - - => setenv boot ramfs - => setenv server_ip - => setenv tftp_root - => setenv name_fs target_fs.cpio.gz - => saveenv - => boot diff --git a/source/linux/Foundational_Components/Kernel/_Users_Guide.rst b/source/linux/Foundational_Components/Kernel/_Users_Guide.rst index d37df90d4..fd2978865 100644 --- a/source/linux/Foundational_Components/Kernel/_Users_Guide.rst +++ b/source/linux/Foundational_Components/Kernel/_Users_Guide.rst @@ -5,7 +5,7 @@ Overview This document will cover the basic steps for building the Linux kernel. -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family') .. rubric:: Install host dependencies @@ -56,7 +56,7 @@ Compiler .. [comment] instructions for 32 bit processors -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') Before compiling the kernel or kernel modules the SDK's toolchain needs to be added to the PATH environment variable @@ -67,7 +67,7 @@ Compiler .. [comment] instructions for 64 bit processors -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. include:: Overview/GCC_ToolChain.rst :start-after: .. start_include_yocto_toolchain_host_setup @@ -94,7 +94,7 @@ The command to clean the kernel is: .. [comment] instructions for 32 bit processors -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. code-block:: console @@ -102,7 +102,7 @@ The command to clean the kernel is: .. [comment] instructions for 64 bit processors -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. code-block:: console @@ -127,7 +127,7 @@ a command of the form: .. [comment] instructions for 32 bit processors -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. code-block:: console @@ -135,7 +135,7 @@ a command of the form: .. [comment] instructions for 64 bit processors -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. code-block:: console @@ -150,7 +150,7 @@ as a starting point). .. [comment] instructions for 32 bit processors -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') platformName is am335x-evm for AM335x, am437x-evm for AM437x, am57xx-evm for AM57xx, k2hk-evm for K2H/K2K, k2e-evm for K2E, k2l-evm for K2L, k2g-evm for @@ -173,7 +173,7 @@ as a starting point). .. [comment] instructions for 64 bit processors -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') For example, to apply the recommended kernel configuration for K3 devices, use: @@ -209,7 +209,7 @@ To invoke the kernel configuration you simply use a command like: .. [comment] instructions for 32 bit processors -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. code-block:: console @@ -223,7 +223,7 @@ To invoke the kernel configuration you simply use a command like: .. [comment] instructions for 64 bit processors -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. code-block:: console @@ -250,7 +250,7 @@ Compiling the Kernel .. [comment] instructions for 32 bit processors -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') Once the kernel has been configured it must be compiled to generate the bootable kernel image as well as any dynamic kernel modules that were @@ -269,7 +269,7 @@ Compiling the Kernel .. [comment] instructions for 64 bit processors -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') By default U-boot expects to boot kernel `Image`, DTB, and DTOs found in root/boot of the SD card if using SD/MMC boot. The exception is for HS-SE (High Security - Security Enforced) @@ -297,7 +297,7 @@ Compiling the Device Tree Binaries .. [comment] instructions for 32 bit processors -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') Starting with the 3.8 kernel each TI evm has an unique device tree binary file required by the kernel. Therefore, you will need to build @@ -370,7 +370,7 @@ Compiling the Device Tree Binaries .. [comment] instructions for 64 bit processors -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') Each TI evm has an unique device tree binary file required by the kernel. Therefore, you will need to build @@ -447,7 +447,7 @@ Compiling the Kernel Modules .. [comment] instructions for 32 bit processors -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') By default the majority of the Linux drivers used in the sdk are not integrated into the kernel image file (zImage). These drivers are built as @@ -459,7 +459,7 @@ Compiling the Kernel Modules .. [comment] instructions for 64 bit processors -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') By default the majority of the Linux drivers used in the sdk are not integrated into the kernel image file (Image). These drivers are built as @@ -491,14 +491,14 @@ But developers may want to deploy and test new Kernel and DTB without going through the standard build system. For the specific purpose, board specific fitImage.its will be present in the prebuilt-images directory. -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') Pre-requisites ( Already part of SDK installations ): - Uboot build directory for ARMV7 - Linux Image and DTB -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') Pre-requisites ( Already part of SDK installations ): @@ -517,7 +517,7 @@ Describing FIT source FIT Image is a packed structure containing binary blobs and configurations. The Kernel FIT Image that we have has Kernel Image, DTB and the DTBOs -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. code-block:: dts @@ -596,7 +596,7 @@ local machine. For e.g change "linux.bin" to "/board-support/prebuilt-images/Image". -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') The new addition to the FIT from 8.6 to 9.0 is the FIT Signature. @@ -633,7 +633,7 @@ For e.g change "linux.bin" to Generating the fitImage ^^^^^^^^^^^^^^^^^^^^^^^ -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. note:: @@ -676,13 +676,13 @@ Generating the fitImage This step will embed the public key in the u-boot.dtb file that was already built during the initial u-boot build. -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. code-block:: console mkimage -r -f fitImage.its -k $UBOOT_PATH/board/ti/keys -K $UBOOT_PATH/build/$ARMV7/dts/dt.dtb fitImage -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. code-block:: console @@ -697,12 +697,12 @@ built during the initial u-boot build. Build uboot again ^^^^^^^^^^^^^^^^^ -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') The updated u-boot.dtb needs to be packed in u-boot.img for authentication so rebuild uboot ARMV7 without changing any parameters. -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') The updated u-boot.dtb needs to be packed in u-boot.img for authentication so rebuild uboot ARMV8 without changing any parameters. @@ -723,7 +723,7 @@ Installing the Kernel Image and Device Tree Binaries .. [comment] instructions for 32 bit processors -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. code-block:: console @@ -743,7 +743,7 @@ Installing the Kernel Image and Device Tree Binaries .. [comment] instructions for 64 bit processors -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. code-block:: console @@ -779,7 +779,7 @@ file system. The general format of the command is: .. [comment] instructions for 32 bit processors -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. code-block:: console @@ -794,7 +794,7 @@ file system. The general format of the command is: .. [comment] instructions for 64 bit processors -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. code-block:: console diff --git a/source/linux/Foundational_Components/Power_Management/pm_dvfs.rst b/source/linux/Foundational_Components/Power_Management/pm_dvfs.rst index 162121785..e00e0e170 100644 --- a/source/linux/Foundational_Components/Power_Management/pm_dvfs.rst +++ b/source/linux/Foundational_Components/Power_Management/pm_dvfs.rst @@ -236,26 +236,3 @@ based on what is detected to be supported by the specific SoC in use. To implement Dynamic Frequency Scaling (DFS), the voltages in the table can be changed to the same fixed value to avoid any voltage scaling from taking place if the system has been designed to use a single voltage. - -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: On-Demand OPP - - On-Demand is a load based DVFS governor, enabled by deafult. The - governor will scale voltage and frequency based on load between - available OPPs. - - - VDD\_MPU supports only 2 OPPs for now (OPP\_NOM, OPP\_OD). OPP\_HIGH - is not yet enabled. Future versions of Kernel may support OPP\_HIGH. - - VDD\_CORE has only one OPP which removes the possibility of DVFS on - VDD\_CORE. - - GPU DVFS is TBD. - - Supported OPPs: - - .. code-block:: text - - /* kHz uV */ - 1000000 1090000 /* OPP_NOM */ - 1176000 1210000 /* OPP_OD */ - diff --git a/source/linux/Foundational_Components/Power_Management/pm_overview.rst b/source/linux/Foundational_Components/Power_Management/pm_overview.rst index 3639de9ce..d89077a07 100644 --- a/source/linux/Foundational_Components/Power_Management/pm_overview.rst +++ b/source/linux/Foundational_Components/Power_Management/pm_overview.rst @@ -20,11 +20,6 @@ when an individual device or CPU is idle for relatively short duration. The dynamic power management features enabled on |__PART_FAMILY_DEVICE_NAMES__| are as follows: -.. ifconfig:: CONFIG_part_family in ('General_family') - - - MPU DVFS - - SmartReflex - .. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family') #. DVFS diff --git a/source/linux/Foundational_Components/Tools/Pin_Mux_Tools.rst b/source/linux/Foundational_Components/Tools/Pin_Mux_Tools.rst index 01083fb03..ddedb0e6b 100644 --- a/source/linux/Foundational_Components/Tools/Pin_Mux_Tools.rst +++ b/source/linux/Foundational_Components/Tools/Pin_Mux_Tools.rst @@ -77,25 +77,6 @@ first before any schematic or board design is started.** Some peripherals may expose Use Cases to allow you to quickly eliminate the signals you won't need. -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: AM57xx and MCASP - :name: am57xx-and-mcasp - - On the AM57xx series of devices there is a concept of IODELAY. It is a - module in the IO of the SoC that makes it possible to ensure valid IO - timings on data interfaces with a clock signal. On some peripherals the - use case selected can change the IODELAY setting for an IO. MCASP is an - advanced audio interface that allows each AXR pin to be an audio source - or audio sink, it also allows the SoC to be the clock master or slave, - and these configuration can be independently mixed and matched. This - makes it important to select the correct use case and pin configurations - since the IODELAY configuration changes depending on the options chosen. - See the "Virtual Mode Case Details" tables in the datasheet for more - information. - - | - .. rubric:: Power Domain Checking :name: power-domain-checking @@ -106,13 +87,6 @@ rails. With this information the PinMux Tool can raise a voltage conflict warning if a peripheral's IO requires a different voltage than is applied to the dual-voltage IO rail. -.. ifconfig:: CONFIG_part_family in ('General_family') - - Example: On the AM57xx pin B14 is supplied by VDDSHV3. If gpio5\_0 is - used on this pin, the IO will be either 1.8V or 3.3V depending on the - supply level applied to VDDSHV3. Damage may occur to the SoC pin if a - 3.3V signal was driven into gpio5\_0 while it is operating at 1.8V. - .. rubric:: Changing Pad Configuration Parameters :name: changing-pad-configuration-parameters @@ -122,17 +96,6 @@ for internal resistor pull and a check box for enabling receive functionality. These configuration parameters are SoC specific and may vary. -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: K2Gxx - :name: k2gxx - - The pins on this device have a "buffer class" feature that lets you fine - tune the output driver characteristics. For most I/Os, the options are - "Class B - Up to 100MHz" or "Class D - Up to 200MHz". The PinMux Tool - gives you the option to select the buffer class for pins that support - this feature (differential or SerDes I/Os, for example, don't support it). - .. rubric:: RX Enable / Input Enable :name: rx-enable-input-enable @@ -186,16 +149,6 @@ U-boot. File names will need to be prefixed by "${SOC}\_". Pinmux header file is common for each SOC here, and may need to be updated manually. -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: Everything Else (AM5, K2G) - :name: everything-else-am5-k2g - - Replace files in this directory - - ${PDK\_INSTALL\_DIR}\\packages\\ti\\board\\src\\${BOARD}\\ - - .. rubric:: Processor SDK Linux :name: processor-sdk-linux @@ -214,32 +167,11 @@ Edit the appropriate file in this directory: ${SDK\_INSTALL\_DIR}\\board\_support\\linux-\*\\arch\\arm64\\boot\\dts\\${BOARD}.dts -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family') ${SDK\_INSTALL\_DIR}\\board\_support\\linux-\*\\arch\\arm\\boot\\dts\\${BOARD}.dts -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: AM57xx u-boot - :name: am57xx-u-boot - - The PinMux tool will provide two files: genericFileFormatIOdelay.txt and - genericFileFormatPadConf.txt. A perl script is provided to convert the - generic formats and provide a format that can be used in u-boot. The - script and the instructions to run the script are on - `git.ti.com `__. - The output from the script is used to edit the file in this directory. - - ${SDK\_INSTALL\_DIR}\\board\_support\\u-boot-\*\\board\\ti\\am57xx\\mux\_data.h - - .. rubric:: K2G u-boot - :name: k2g-u-boot - - Replace the file in this directory. - - ${SDK\_INSTALL\_DIR}\\board\_support\\u-boot-\*\\board\\ti\\ks2\_evm\\mux-k2g.h - .. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family') .. rubric:: AM3 and AM4 u-boot diff --git a/source/linux/Foundational_Components/U-Boot/BG-Bootflow-K3.rst b/source/linux/Foundational_Components/U-Boot/BG-Bootflow-K3.rst index c1a570600..f9e1963c1 100644 --- a/source/linux/Foundational_Components/U-Boot/BG-Bootflow-K3.rst +++ b/source/linux/Foundational_Components/U-Boot/BG-Bootflow-K3.rst @@ -10,7 +10,7 @@ Bootflow Boot Flow ********* -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family') Booting the Linux kernel on an embedded platform is not as simple as simply pointing a program counter to the kernel location and letting the processor @@ -85,7 +85,7 @@ Boot Flow specific device tree blob (DTB) as an argument to U-Boot's **bootz** command that will extract and start the actual kernel. -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM62LX_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM62LX_family') On K3 architecture based devices, ROM supports boot only via MCU(R5). This means that bootloader has to run on R5 core. In order to meet this constraint, keeping diff --git a/source/linux/Foundational_Components/U-Boot/UG-DFU.rst b/source/linux/Foundational_Components/U-Boot/UG-DFU.rst index d97277a76..361643acb 100644 --- a/source/linux/Foundational_Components/U-Boot/UG-DFU.rst +++ b/source/linux/Foundational_Components/U-Boot/UG-DFU.rst @@ -21,48 +21,7 @@ The USB Peripheral boot mode is used to boot using USB interface using SPL-DFU feature. Steps outlined here can be used on platform that support USB Peripheral boot mode. -.. ifconfig:: CONFIG_part_family in ('General_family') - - #. Enable the SPL-DFU feature in u-boot and build MLO/u-boot binaries. - #. Load the MLO and u-boot.img using the dfu-util from host PC. - #. Once the u-boot is up, use DFU command from u-boot to flash the - binary images from Host PC (using dfu-utils tool) to the eMMC, or - QSPI to fresh/factory boards. - - - Example provided here is for dra7xx platform. - - - Use default "dra7xx\_evm\_defconfig" to build spl/u-boot-spl.bin, - u-boot.img. - - :: - - host$ make dra7xx_evm_defconfig - host$ make menuconfig - - select SPL/DFU support - menuconfig->SPL/TPL---> - .. - [*] Support booting from RAM - [*] Support USB Gadget drivers - [ ] Support USB Ethernet drivers - [*] Support DFU (Device Firmware Upgrade) - DFU device selection (RAM device) --> - - :: - - Unselect CONFIG_HUSH_PARSER - menuconfig--->Command Line interface - [*] Support U-boot commands - [ ] Use hush shell - - - - Build spl/u-boot-spl.bin and u-boot.img - - :: - - host$ make - -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM57X_family') - Set SYSBOOT SW2 switch to USB Peripheral boot mode diff --git a/source/linux/Foundational_Components/U-Boot/UG-General-Info.rst b/source/linux/Foundational_Components/U-Boot/UG-General-Info.rst index 5bcbf9b69..66be90d66 100644 --- a/source/linux/Foundational_Components/U-Boot/UG-General-Info.rst +++ b/source/linux/Foundational_Components/U-Boot/UG-General-Info.rst @@ -1,7 +1,7 @@ General Information ------------------- -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family') .. rubric:: Install host dependencies @@ -92,7 +92,7 @@ Build U-Boot the top-level directory and can be identified by looking for the "MAINTAINERS" file. -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') We strongly recommend the use of separate object directories when building. This is done with O= parameter to make. We also recommend that @@ -189,7 +189,7 @@ Build U-Boot statements. -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. ifconfig:: CONFIG_part_variant not in ('AM65X', 'AM64X', 'AM62LX') @@ -1292,7 +1292,7 @@ Image Formats Boot Flow ^^^^^^^^^ -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') Booting the Linux kernel on an embedded platform is not as simple as simply pointing a program counter to the kernel location and letting the processor @@ -1367,7 +1367,7 @@ Boot Flow specific device tree blob (DTB) as an argument to U-Boot's **bootz** command that will extract and start the actual kernel. -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM335X_family', 'AM437X_family', 'AM62LX_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM335X_family', 'AM437X_family', 'AM62LX_family', 'AM57X_family') On K3 architecture based devices, ROM supports boot only via MCU(R5). This means that bootloader has to run on R5 core. In order to meet this constraint, keeping diff --git a/source/linux/Foundational_Components/U-Boot/UG-Memory-OMAP.rst b/source/linux/Foundational_Components/U-Boot/UG-Memory-OMAP.rst index d01d3b9b7..24fbb68b9 100644 --- a/source/linux/Foundational_Components/U-Boot/UG-Memory-OMAP.rst +++ b/source/linux/Foundational_Components/U-Boot/UG-Memory-OMAP.rst @@ -254,16 +254,6 @@ to copy the boot images: to the SD card *boot* partition. At this point, the device can boot to u-boot prompt. -.. ifconfig:: CONFIG_part_family in ('General_family') - - However, if you are using OMAP-L138 based board (like the LCDK), then - you need to write the generated :file:`u-boot.ais` image to the SD card - using command: :command:`dd`. - - .. code-block:: console - - $ sudo dd if=u-boot.ais of=/dev/sd seek=117 bs=512 conv=fsync - USB *** @@ -304,12 +294,12 @@ Flash and boot SPL from USB storage Boot Linux from USB storage ============================== -.. ifconfig:: CONFIG_part_family not in ('General_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family not in ('AM57X_family') Booting Linux from USB storage documentation is pending for |__PART_FAMILY_DEVICE_NAMES__|, please reach out to: `Help e2e `__ for additional information. -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM57X_family') To load the Linux Kernel and rootfs from USB rather than a MMC card on AMx/DRA7x EVMs, if we assume that the USB device is partitioned the same @@ -326,7 +316,7 @@ Boot Linux from USB storage The USB drivers in Linux kernel need to be built-in (default modules). The configuration changes are: - .. ifconfig:: CONFIG_part_family in ('General_family', 'AM437X_family', 'AM57X_family') + .. ifconfig:: CONFIG_part_family in ('AM437X_family', 'AM57X_family') .. code-block:: Kconfig @@ -392,7 +382,7 @@ Boot Linux from USB storage => saveenv => boot -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM57X_family') Booting from SD/eMMC from SPL (Single stage or Falcon mode) =========================================================== diff --git a/source/linux/Foundational_Components/U-Boot/UG-QSPI.rst b/source/linux/Foundational_Components/U-Boot/UG-QSPI.rst index 6448c6793..4aeb961a2 100644 --- a/source/linux/Foundational_Components/U-Boot/UG-QSPI.rst +++ b/source/linux/Foundational_Components/U-Boot/UG-QSPI.rst @@ -1602,194 +1602,6 @@ Flash properties: # sudo dfu-util -c 1 -i 0 -a 1 -D tispl.bin # sudo dfu-util -c 1 -i 0 -a 2 -D u-boot.img -.. ifconfig:: CONFIG_part_variant in ('Gen') - - Memory Layout of QSPI Flash - - .. code-block:: text - - +----------------+ 0x00000 - | MLO | - | | - +----------------+ 0x040000 - | u-boot.img | - | | - +----------------+ 0x140000 - | DTB blob | - +----------------+ 0x1c0000 - | u-boot env | - +----------------+ 0x1d0000 - | u-boot env | - | (backup) | - +----------------+ 0x1e0000 - | | - | uImage | - | | - | | - +----------------+ 0x9e0000 - | | - | other data | - | | - +----------------+ - - .. rubric:: Writing to QSPI from U-Boot - :name: writing-to-qspi-from-u-boot - - Note: - - - From the U-Boot build, the **MLO** and **u-boot.img** files are the - ones to be written. - - We load all files from an SD card in this example but they can just - as easily be loaded via network (documented above) or other interface - that exists. - - Writing MLO and u-boot.img binaries. - - For QSPI\_1 build U-Boot with ``dra7xx_evm_config`` - - .. code-block:: console - - U-Boot # mmc rescan - U-Boot # fatload mmc 0 ${loadaddr} MLO - U-Boot # sf probe 0 - U-Boot # sf erase 0x00000 0x200000 - U-Boot # sf write ${loadaddr} 0x00000 ${filesize} - U-Boot # fatload mmc 0 ${loadaddr} u-boot.img - U-Boot # sf write ${loadaddr} 0x40000 ${filesize} - - change SW2[5:0] = 110110 for qspi boot. - - For QSPI\_4 build U-Boot with ``dra7xx_evm_qspiboot_config`` - - .. code-block:: console - - U-Boot # mmc rescan - U-Boot # fatload mmc 0 ${loadaddr} MLO - U-Boot # sf probe 0 - U-Boot # sf erase 0x00000 0x200000 - U-Boot # sf write ${loadaddr} 0x00000 0x10000 - U-Boot # fatload mmc 0 ${loadaddr} u-boot.img - U-Boot # sf write ${loadaddr} 0x40000 0x60000 - - change SW2[5:0] = 110111 for qspi boot. - - | - - .. rubric:: Writing to QSPI using DFU - :name: writing-to-qspi-using-dfu - - Setup: Connect the usb0 port of EVM to ubuntu host PC. Make sure - dfu-util tool is installed. - - .. code-block:: console - - #sudo apt-get install dfu-util - - From u-boot: - - .. code-block:: console - - U-Boot # env default -a - U-Boot # setenv dfu_alt_info ${dfu_alt_info_qspi}; dfu 0 sf "0:0:64000000:0" - - From ubuntu PC: Using dfu-util utilities to flash the binares to QSPI - flash. - - .. code-block:: console - - # sudo dfu-util -l - (C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc. - (C) 2010-2011 Tormod Volden (DfuSe support) - This program is Free Software and has ABSOLUTELY NO WARRANTY - dfu-util does currently only support DFU version 1.0 - Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=0, name="MLO" - Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=1, name="u-boot.img" - Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=2, name="u-boot-spl-os" - Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=3, name="u-boot-env" - Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=4, name="u-boot-env.backup" - Found DFU: [0451:d022] devnum=0, cfg=1, intf=0, alt=5, name="kernel" - - Flash the binaries to the respective regions using alternate interface - number (alt=). - - .. code-block:: console - - # sudo dfu-util -c 1 -i 0 -a 0 -D MLO - # sudo dfu-util -c 1 -i 0 -a 1 -D u-boot.img - # sudo dfu-util -c 1 -i 0 -a 2 -D - # sudo dfu-util -c 1 -i 0 -a 5 -D uImage - - .. rubric:: Booting from QSPI from u-boot - :name: booting-from-qspi-from-u-boot - - The default environment does not contain a QSPI boot command. The - following example uses the partition table found in the kernel. - - .. code-block:: console - - U-Boot # sf probe 0 - U-Boot # sf read ${loadaddr} 0x1e0000 0x800000 - U-Boot # sf read ${fdtaddr} 0x140000 0x80000 - U-Boot # setenv bootargs console=${console} root=/dev/mtdblock19 rootfstype=jffs2 - U-Boot # bootz ${loadaddr} - ${fdtaddr} - - .. rubric:: Booting from QSPI from SPL (Single stage or Falcon mode) - :name: booting-from-qspi-from-spl-single-stage-or-falcon-mode - - In this boot mode SPL (first stage bootloader) directly boots the Linux - kernel. Optionally, in order to enter into U-Boot, reset the board while - keeping 'c' key on the serial terminal pressed. When falcon mode is - enabled in U-Boot build (usually enabled by default), MLO checks if - there is a valid uImage present at a defined offset. If uImage is - present, it is booted directly. If valid uImage is not found, MLO falls - back to booting u-boot.img. - - For QSPI single stage or Falcon mode, the CONFIG\_QSPI\_BOOT shall - enabled. - - .. code-block:: text - - Menuconfig->Bood media - [ ] Support for booting from NAND flash - .. - [*] Support for booting from QSPI flash - [ ] Support for booting from SATA - ... - - MLO, u-boot.img (optional), DTB, uImage are stored in QSPI flash memory. - Refer the "Memory Layout" section for offset details. To flash binaries - to QSPI, you can use - `DFU `__, - for example. - - The QSPI boot uses uImage. Build the kernel uImage. You will need to - keep the U-Boot tool ``mkimage`` in your ``$PATH`` - - .. code-block:: console - - # make uImage modules dtbs LOADADDR=80008000 - - If kernel is not build with ``CONFIG_CMDLINE`` to set correct bootargs, - then add the needed bootargs in chosen node in DTB file, using fdtput - host utility. For example, for DRA74x EVM: - - .. code-block:: console - - # fdtput -v -t s arch/arm/boot/dts/dra7-evm.dtb "/chosen" bootargs "console=ttyO0,115200n8 root=" - - Set the environment variable "boot\_os" to 1. - - From u-boot prompt - - .. code-block:: console - - => setenv boot_os 1 - => saveenv - - Set the `board boot from - QSPI `__ - and reset the EVM. The SPL directly boots the kernel image from QSPI. - .. ifconfig:: CONFIG_part_variant in ('AM335X') SPI boot is supported on the following platforms: diff --git a/source/linux/Foundational_Components/Virtualization/Docker.rst b/source/linux/Foundational_Components/Virtualization/Docker.rst index 497c8236c..7ff3689dd 100644 --- a/source/linux/Foundational_Components/Virtualization/Docker.rst +++ b/source/linux/Foundational_Components/Virtualization/Docker.rst @@ -23,7 +23,7 @@ runtime may not be located on an NFS mount. While it is possible to use Docker on a NFS root, extra configuration is required to modify the default docker runtime directory. -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM62X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM62X_family') Please follow the instructions for the :ref:`Create SD Card Script ` and when prompted to select the root filesystem tarball, select the ``tisdk-default-image`` diff --git a/source/linux/Foundational_Components/_Processor_SDK_Linux_Filesystem.rst b/source/linux/Foundational_Components/_Processor_SDK_Linux_Filesystem.rst index 0f34efb42..d36ec7c83 100644 --- a/source/linux/Foundational_Components/_Processor_SDK_Linux_Filesystem.rst +++ b/source/linux/Foundational_Components/_Processor_SDK_Linux_Filesystem.rst @@ -34,19 +34,6 @@ This is the complete filesystem image, that contains standard Linux commands and features. This also contains the TI component libraries, binaries and :ref:`TI Apps Launcher OOB Demo ` -.. ifconfig:: CONFIG_sdk in ('SITARA') - - .. ifconfig:: CONFIG_part_family in ('General_family') - - For keystone devices (e.g., K2H/K2K, - K2E, K2L, and K2G), two filesystem tarballs are provided due to size - limit of the rootfs ubi image: - - - tisdk-server-rootfs-image-k2g-evm.tar.gz: base filesystem image used - to create the ubi image. - - tisdk-server-extra-rootfs-image-k2g-evm.tar.gz: complete filesystem - image that can be used with NFS and/or SD card (K2G only). - .. only:: _comment [comment] current SDK 7.x build for 'PSDK' doesn't have docker/tiny image, so comment out the following section @@ -85,6 +72,6 @@ Following is a list of all filesystem images provided by TI which can be built v .. note:: - - Watchout for console logs while running `oe-layersetup `__ - to get an exhaustive list of target filesystem images that can be built using Yocto. + + Watchout for console logs while running `oe-layersetup `__ + to get an exhaustive list of target filesystem images that can be built using Yocto. diff --git a/source/linux/Foundational_Components_U-Boot.rst b/source/linux/Foundational_Components_U-Boot.rst index fa0681e41..b224a7067 100644 --- a/source/linux/Foundational_Components_U-Boot.rst +++ b/source/linux/Foundational_Components_U-Boot.rst @@ -22,7 +22,7 @@ following platform(s): | `AM437x EVM-SK `__ | `AM437x IDK `__ -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM57x_family') +.. ifconfig:: CONFIG_part_family in ('AM57x_family') | `DRA76x EVM `__ | `DRA74x EVM `__ diff --git a/source/linux/How_to_Guides/Host/Boot_Sequence.rst b/source/linux/How_to_Guides/Host/Boot_Sequence.rst index e546eacad..ec0f4338d 100644 --- a/source/linux/How_to_Guides/Host/Boot_Sequence.rst +++ b/source/linux/How_to_Guides/Host/Boot_Sequence.rst @@ -9,7 +9,7 @@ Boot Sequence Please refer back to the particular U-boot component branch and version information for this release: :ref:`u-boot-release-notes` -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM57X_family') .. rubric:: Introduction :name: introduction-boot-sequence diff --git a/source/linux/How_to_Guides/Host/How_to_Flash_Linux_System_from_U-boot.rst b/source/linux/How_to_Guides/Host/How_to_Flash_Linux_System_from_U-boot.rst index d752fcdc8..d43447d16 100644 --- a/source/linux/How_to_Guides/Host/How_to_Flash_Linux_System_from_U-boot.rst +++ b/source/linux/How_to_Guides/Host/How_to_Flash_Linux_System_from_U-boot.rst @@ -12,234 +12,3 @@ How to Flash from U-boot Shell https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/doc/board/ti/j721e_evm.rst - -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: Application - :name: application - - This article applies to Sitara SDK 4.0.1 which uses the Platform Support - Package (PSP) software version 03.01.00.06 - - for AM35x and AM37x devices. This information is obsolete as newer - software has different NAND ECC requirements. - - .. rubric:: Introduction - :name: introduction-flash-linux-system-from-uboot - - This guide will show how use u-boot to flash the NAND of an OMAP3 EVM - (for AM37x, DM37x or OMAP35xx devices) or an AM3517EVM (for AM35x - devices) with Linux system binaries. - - - Assumptions: - - #. SD card with system binaries (x-loader, u-boot, Linux kernel) on - **boot** partition - #. Linux root filesystem in **rootfs** partition of SD card or root - filesystem available via NFS - - .. rubric:: Caution - :name: caution - - The procedures here will erase the NAND flash of the EVM. This includes - all u-boot environment variables. Use the "**printenv**" command (or - just "**pri**") in u-boot to print a complete list of environment - variables. Copy and paste these to a text file for safe keeping. - - .. rubric:: Boot EVM into SD/MMC card boot mode - :name: bootevm-into-sdmmc-card-boot-mode - - The SD card must at least have the files MLO, u-boot.bin, and uImage. - All of these files can also be found in the "./psp/prebuilt-images" - directory in the Sitara SDK installation (with names that include the - platform name and software revision info). The MLO file is simply a - re-named copy of the file x-load.bin.ift that is produced by rebuilding - x-loader and signing the file. When the board is booted in SD/MMC card - boot mode, the ROM code looks specifically for the file with the name - MLO as the primary bootloader. - - To boot from this SD card, the boot switches should be set to SD/MMC - boot: - - **For Mistral OMAP EVM (AM37x, DM37x or OMAP35xx devices)** - - | Set SW4 switches #1, #2, #3 and #6 to the ON position and all others - OFF (MMC1, UART3 boot order) - | **For LogicPD AM3517EVM (AM35x device)** - - | Set SW7 switches #1 and #4 to the ON position and all others OFF. - (USB, UART, MMC1, XIP boot order) - - Start the board and interrupt the boot process when prompted by hitting - any key in the UART terminal application: - - :: - - Texas Instruments X-Loader 1.45 (Mar 19 2010 - 19:44:19) - Starting X-loader on MMC - Reading boot sector - - 212504 Bytes Read from MMC - Starting OS Bootloader from MMC... - Starting OS Bootloader... - U-Boot 2009.11 (May 06 2010 - 16:57:54) - - OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz - OMAP3 EVM board + LPDDR/NAND - I2C: ready - DRAM: 128 MB - NAND: 256 MiB - *** Warning - bad CRC or NAND, using default environment - - In: serial - Out: serial - Err: serial - Read back SMSC id 0x92200000 - Die ID #731c0000000000000156087c0a023021 - Net: smc911x-0 - Hit any key to stop autoboot: 0 - OMAP3_EVM # - OMAP3_EVM # - - All of the commands in this guide are performed at the u-boot prompt. - - .. rubric:: Run the u-boot commands to flash the NAND - :name: run-the-u-boot-commands-to-flash-the-nand - - All of the following commands are performed at the u-boot prompt. - - These commands are actually a series of u-boot commands that are - connected together with semicolons. The individual commands can be - entered separately or simple pasted from here. - - | - - - Complete xloader write from MMC to NAND (only erases one block=128k). - - :: - - mw.b 0x81600000 0xff 0x20000;nand erase 0 20000;mmc init;fatload mmc 0 0x81600000 x-load.bin.ift;nandecc hw; nand write.i 0x81600000 0 20000 - - - Complete uboot write from MMC to NAND (only erases two blocks=256k) - - :: - - mw.b 0x81600000 0xff 0x40000;nand erase 80000 40000;mmc init;fatload mmc 0 0x81600000 u-boot.bin;nandecc sw; nand write.i 0x81600000 80000 40000 - - - Complete kernel write from MMC to NAND (erases 3M) - - :: - - mw.b 0x81600000 0xff 0x1400000;nand erase 280000 300000;mmc init;fatload mmc 0 0x81600000 uImage;nandecc sw; nand write.i 0x81600000 280000 300000 - - .. rubric:: Put the EVM in NAND boot mode - :name: put-the-evm-in-nandboot-mode - - With the EVM in NAND boot mode and the images flashed in NAND as - detailed above, the SD card does not need to be in the EVM at boot up. - X-loader and u-boot will run from NAND. In order to also pull the Linux - kernel (uImage) from NAND it will be necessary to halt the boot process - and edit some u-boot environment variables. - - | - - **For Mistral OMAP EVM (AM37x, DM37x or OMAP35xx devices)** - - Set SW4 switches #2, #4 and #6 to the ON position and all others OFF - (NAND, UART3 boot order) - - **For LogicPD AM3517EVM (AM35x device)** - - Set SW7 with switches #1 thru #8 all to the OFF position. (NAND, EMAC, - USB, MMC1 boot order) - - - Save off the original boot command - - :: - - setenv bootcmd_original ${bootcmd} - saveenv - - | - - - Create command for reading the kernel from NAND and then another - command for doing the boot where the kernel is pulled from NAND and - the root filesystem is from the SD/MMC card. - - :: - - setenv nand_kernel 'nand read.i ${loadaddr} 280000 300000' - setenv nand_mmc_boot 'run nand_kernel;setenv bootargs ${mmcargs}; bootm' - - Run this last command to actually perform the boot. And always save the - environment after making changes. - - :: - - saveenv - run nand_mmc_boot - - .. rubric:: Flashing the Root File System to NAND - :name: flashing-the-root-file-system-to-nand - - A jffs2 file system can be copied into NAND flash. Copy the file - rootfs.tar.gz to the /home/root directory on the SD Card. Boot the EVM - to Linux and enter the following commands: - - :: - - [prompt]$ flash_eraseall –j /dev/mtd4 - [prompt]$ mount /dev/mtdblock4 /media/nand –t jffs2 - [prompt]$ cd /media/nand - [prompt]$ tar xzf /home/root/rootfs.tar.gz - [prompt]$ reboot –f - - The bootargs under u-boot must be altered to use this new NAND file - system. - - NOTE:After the reboot the board is now running in u-boot, remember to - stop the autoboot sequence by typing any key. The following are u-boot - commands: - - :: - - setenv bootargs 'mem=128M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2 ip=dhcp' - bootm - - .. rubric:: Mounting File System from NFS - :name: mounting-file-system-from-nfs - - The file system can also be mounted as a Network File System (NFS). The - NFS is simply a sub-directory of the Linux host development system. - - Another command can be made to pull the root filesystem via NFS. This - command can be combine with the one to pull the bootloaders and kernel - from NAND. (The IP address and path to the NFS is an example and should - be changed by the user). - - :: - - setenv serverip - setenv nfsargs 'setenv bootargs mem=128M console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=${serverip}:/home/user/ti-sdk-AM3715-evm-4.0.0.0/rfs,nolock,rsize=1024,wsize=1024' - setenv nand_nfs_boot 'run nand_kernel;run nfsargs; bootm ${loadaddr}' - saveenv - run nand_nfs_boot - - .. rubric:: Default NAND partitioning (from x-loader) - :name: default-nand-partitioning-from-x-loader - - | /\* NAND is partitioned: - | \* 0x00000000 - 0x0007FFFF Booting Image (512k) - | \* 0x00080000 - 0x0023FFFF U-Boot Image (1.6M) - | \* 0x00240000 - 0x0027FFFF U-Boot Env Data (256k) - | \* 0x00280000 - 0x0077FFFF Kernel Image (5M) - | \* 0x00780000 - 0x08000000 File System - - - Block size = 0x00020000 (128k) - \* Page size = 0x00000800 (2k) - \*/ - - | - - - diff --git a/source/linux/How_to_Guides/Target/How_to_Change_dtb_File.rst b/source/linux/How_to_Guides/Target/How_to_Change_dtb_File.rst index a464f1878..f4157a818 100644 --- a/source/linux/How_to_Guides/Target/How_to_Change_dtb_File.rst +++ b/source/linux/How_to_Guides/Target/How_to_Change_dtb_File.rst @@ -6,7 +6,7 @@ How to change dtb files .. rubric:: Introduction :name: introduction-change-dtb-file -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') In some scenarios, it is required to manually change the dtb file used by the target. For example, AM437X GP EVM uses LCD display by default. @@ -22,7 +22,7 @@ How to change dtb files .. rubric:: Specify dtb File :name: specify-dtb-file -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') The dtb files are located on the target filesystem under "/boot/dtb" directory. First, identify the dtb file to be used, e.g., diff --git a/source/linux/Overview/Processor_SDK_Linux_create_SD_card_script.rst b/source/linux/Overview/Processor_SDK_Linux_create_SD_card_script.rst index 15f1d96a7..39c76506e 100644 --- a/source/linux/Overview/Processor_SDK_Linux_create_SD_card_script.rst +++ b/source/linux/Overview/Processor_SDK_Linux_create_SD_card_script.rst @@ -208,33 +208,6 @@ custom file paths. | -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: Choose rootfs tarball for K2G - :name: choose-rootfs-tarball-for-k2g - - For K2G, you should now see a prompt like: - - :: - - ################################################################################ - - Multiple rootfs Tarballs found - - ################################################################################ - - 1:tisdk-server-extra-rootfs-image-k2g-evm.tar.gz - 2:tisdk-server-rootfs-image-k2g-evm.tar.gz - - Enter Number of rootfs Tarball: - - | Choose option **1** to create an SD card using the complete filesystem - image from the SDK. Option **2** provides the base filesystem image of - smaller size, and it can be used when the SD card does not have - sufficient space. - - | - .. rubric:: Enter SDK Path :name: enter-sdk-path @@ -370,23 +343,3 @@ The script will show you the contents of the directory given and ask you to verify that the tarballs are present in that directory. The SD card will then be populated with the contents of the tarballs and be ready for inclusion in the box with the EVM. - -| - -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. rubric:: Additional Step for OMAPL138 after SD Card Creation - :name: additional-step-for-omapl138-after-sd-card-creation - - For OMAP-L138 LCDK, boot loader needs to be updated after the SD card is - created as above. The pre-built u-boot-omapl138-lcdk.ais needs to be - written to the SD card using the **dd** command. /dev/sd below - corresponds to the SD card device listed from the host machine. - - :: - - $ cd /board-support/prebuilt-images - $ sudo dd if=u-boot-omapl138-lcdk.ais of=/dev/sd seek=117 bs=512 conv=fsync - -| - diff --git a/source/linux/Overview/_Processor_SDK_Building_The_SDK.rst b/source/linux/Overview/_Processor_SDK_Building_The_SDK.rst index 4a57be3db..6525c1858 100644 --- a/source/linux/Overview/_Processor_SDK_Building_The_SDK.rst +++ b/source/linux/Overview/_Processor_SDK_Building_The_SDK.rst @@ -100,104 +100,102 @@ Please refer to :ref:`here ` for the layer configuration ``oeconfig-file`` for a particular release of |__SDK_FULL_NAME__|. The MACHINE can be set to |__SDK_BUILD_MACHINE__|, for example. -.. ifconfig:: CONFIG_part_family not in ('General_family') - - .. ifconfig:: CONFIG_sdk in ('SITARA') +.. ifconfig:: CONFIG_sdk in ('SITARA') - .. ifconfig:: CONFIG_part_variant in ('AM62AX') + .. ifconfig:: CONFIG_part_variant in ('AM62AX') - The final command below will build the **tisdk-edgeai-image**, which is the - Processor SDK image with Arago + EdgeAI filesystem. See `Build Options`_ for a list of - additional targets. + The final command below will build the **tisdk-edgeai-image**, which is the + Processor SDK image with Arago + EdgeAI filesystem. See `Build Options`_ for a list of + additional targets. - .. tabs:: + .. tabs:: - .. tab:: Build Linux SD card Image + .. tab:: Build Linux SD card Image - .. code-block:: console + .. code-block:: console - $ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk - $ cd tisdk - $ ./oe-layertool-setup.sh -f configs/processor-sdk-analytics/ - $ cd build - $ . conf/setenv - $ MACHINE=am62axx-evm bitbake -k tisdk-edgeai-image + $ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk + $ cd tisdk + $ ./oe-layertool-setup.sh -f configs/processor-sdk-analytics/ + $ cd build + $ . conf/setenv + $ MACHINE=am62axx-evm bitbake -k tisdk-edgeai-image - .. tab:: Build RT-Linux SD card Image + .. tab:: Build RT-Linux SD card Image - .. code-block:: console + .. code-block:: console - $ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk - $ cd tisdk - $ ./oe-layertool-setup.sh -f configs/processor-sdk-analytics/ - $ cd build - $ . conf/setenv - $ MACHINE=am62axx-evm ARAGO_RT_ENABLE=1 bitbake -k tisdk-edgeai-image + $ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk + $ cd tisdk + $ ./oe-layertool-setup.sh -f configs/processor-sdk-analytics/ + $ cd build + $ . conf/setenv + $ MACHINE=am62axx-evm ARAGO_RT_ENABLE=1 bitbake -k tisdk-edgeai-image - .. ifconfig:: CONFIG_part_variant not in ('AM62AX') + .. ifconfig:: CONFIG_part_variant not in ('AM62AX') - The final command below will build the :file:`tisdk-default-image`, which is the - Processor SDK image with arago filesystem. See `Build Options`_ for a list of - additional targets. + The final command below will build the :file:`tisdk-default-image`, which is the + Processor SDK image with arago filesystem. See `Build Options`_ for a list of + additional targets. - .. tabs:: + .. tabs:: - .. tab:: Build Linux SD card Image + .. tab:: Build Linux SD card Image - .. code-block:: console + .. code-block:: console - $ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk - $ cd tisdk - $ ./oe-layertool-setup.sh -f configs/processor-sdk/ - $ cd build - $ . conf/setenv - $ MACHINE= bitbake -k tisdk-default-image + $ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk + $ cd tisdk + $ ./oe-layertool-setup.sh -f configs/processor-sdk/ + $ cd build + $ . conf/setenv + $ MACHINE= bitbake -k tisdk-default-image - .. tab:: Build RT-Linux SD card Image + .. tab:: Build RT-Linux SD card Image - .. code-block:: console + .. code-block:: console - $ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk - $ cd tisdk - $ ./oe-layertool-setup.sh -f configs/processor-sdk/ - $ cd build - $ . conf/setenv - $ MACHINE= ARAGO_RT_ENABLE=1 bitbake -k tisdk-default-image + $ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk + $ cd tisdk + $ ./oe-layertool-setup.sh -f configs/processor-sdk/ + $ cd build + $ . conf/setenv + $ MACHINE= ARAGO_RT_ENABLE=1 bitbake -k tisdk-default-image - .. ifconfig:: CONFIG_part_variant in ('AM62X','AM62PX','AM62LX') + .. ifconfig:: CONFIG_part_variant in ('AM62X','AM62PX','AM62LX') - * The final command below will build the :file:`tisdk-jailhouse-image`, which is the - Processor SDK image with arago filesystem and Jailhouse support. + * The final command below will build the :file:`tisdk-jailhouse-image`, which is the + Processor SDK image with arago filesystem and Jailhouse support. - .. ifconfig:: CONFIG_part_variant in ('AM62X') + .. ifconfig:: CONFIG_part_variant in ('AM62X') - * :file:`tisdk-jailhouse-image` is not applicable for am62xxsip-evm and beagleplay-ti. + * :file:`tisdk-jailhouse-image` is not applicable for am62xxsip-evm and beagleplay-ti. - .. tabs:: + .. tabs:: - .. tab:: Build Jailhouse Linux SD card Image + .. tab:: Build Jailhouse Linux SD card Image - .. code-block:: console + .. code-block:: console - $ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk - $ cd tisdk - $ ./oe-layertool-setup.sh -f configs/processor-sdk/ - $ cd build - $ . conf/setenv - $ echo 'TI_EXTRAS="tie-jailhouse"' >> conf/local.conf - $ MACHINE= bitbake -k tisdk-jailhouse-image + $ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk + $ cd tisdk + $ ./oe-layertool-setup.sh -f configs/processor-sdk/ + $ cd build + $ . conf/setenv + $ echo 'TI_EXTRAS="tie-jailhouse"' >> conf/local.conf + $ MACHINE= bitbake -k tisdk-jailhouse-image - .. tab:: Build Jailhouse RT-Linux SD card Image + .. tab:: Build Jailhouse RT-Linux SD card Image - .. code-block:: console + .. code-block:: console - $ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk - $ cd tisdk - $ ./oe-layertool-setup.sh -f configs/processor-sdk/ - $ cd build - $ . conf/setenv - $ echo 'TI_EXTRAS="tie-jailhouse"' >> conf/local.conf - $ MACHINE= ARAGO_RT_ENABLE=1 bitbake -k tisdk-jailhouse-image + $ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk + $ cd tisdk + $ ./oe-layertool-setup.sh -f configs/processor-sdk/ + $ cd build + $ . conf/setenv + $ echo 'TI_EXTRAS="tie-jailhouse"' >> conf/local.conf + $ MACHINE= ARAGO_RT_ENABLE=1 bitbake -k tisdk-jailhouse-image .. ifconfig:: CONFIG_sdk in ('JACINTO','j7_foundational') @@ -652,30 +650,6 @@ The "Build Output" is given relative to the | am62lxx-evm | AM62L EVM - HS-FS | +---------------+-----------------------------------------------+ - .. ifconfig:: CONFIG_part_variant in ('Gen') - - +---------------+---------------------------------------------------------------------------------------+ - | **MACHINE** | **Supported EVMs** | - +---------------+---------------------------------------------------------------------------------------+ - | k2hk-evm | 66AK2Hx EVM , K2K EVM | - +---------------+---------------------------------------------------------------------------------------+ - | k2e-evm | K2Ex EVM | - +---------------+---------------------------------------------------------------------------------------+ - | k2l-evm | 66AK2L06 EVM | - +---------------+---------------------------------------------------------------------------------------+ - | k2g-evm | K2G EVM | - +---------------+---------------------------------------------------------------------------------------+ - | omapl138-lcdk | OMAP-L138 LCDK | - +---------------+---------------------------------------------------------------------------------------+ - - .. rubric:: RT Support - :name: RT Support - - Processor SDK Linux supports RT Linux Kernel for the following - machines/EVMs. Use the command below to make the RT builds: - - ``MACHINE= ARAGO_RT_ENABLE=1 bitbake `` - .. ifconfig:: CONFIG_part_variant in ('AM335X') +--------------+---------------------------------------------------------------------------------------+ @@ -745,20 +719,6 @@ The "Build Output" is given relative to the | am62lxx-evm | AM62L EVM - HS-FS | +---------------+-----------------------------------------------+ - .. ifconfig:: CONFIG_part_variant in ('Gen') - - +---------------+--------------------------------------------------------------------------------------+ - | **MACHINE** | **Supported EVMs** | - +---------------+--------------------------------------------------------------------------------------+ - | k2hk-evm | 66AK2Hx EVM , K2K EVM | - +---------------+--------------------------------------------------------------------------------------+ - | k2e-evm | K2Ex EVM | - +---------------+--------------------------------------------------------------------------------------+ - | k2l-evm | 66AK2L06 EVM | - +---------------+--------------------------------------------------------------------------------------+ - | k2g-evm | K2G EVM | - +---------------+--------------------------------------------------------------------------------------+ - .. _building-the-sdk-recipes: Recipes diff --git a/source/linux/Overview/_Processor_SDK_Linux_Software_Developers_Guide.rst b/source/linux/Overview/_Processor_SDK_Linux_Software_Developers_Guide.rst index 90df33760..cba791ca3 100644 --- a/source/linux/Overview/_Processor_SDK_Linux_Software_Developers_Guide.rst +++ b/source/linux/Overview/_Processor_SDK_Linux_Software_Developers_Guide.rst @@ -44,37 +44,6 @@ suggestions at `E2E `__. - -.. ifconfig:: CONFIG_part_family in ('General_family') - - .. list-table:: - :header-rows: 1 - - * - Foundational Components - - - - - - - * - :ref:`U-Boot ` - - :ref:`Boot Monitor ` - - :ref:`Kernel ` - - :ref:`Filesystem ` - * - :ref:`Tools ` - - `OpenCL `__ - - :ref:`OpenCV ` - - :ref:`Graphics & Display ` - * - :ref:`Multimedia ` - - :ref:`Examples, Demos ` - - :ref:`PRU Subsystem ` - - :ref:`Virtualization ` - * - :ref:`IPC ` - - :ref:`OpenVX ` - - :ref:`CMEM ` - - :ref:`Machine Learning ` - * - :ref:`ATF ` - - :ref:`OPTEE ` - - - - - - .. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. list-table:: diff --git a/source/linux/Overview/_Processor_SDK_Linux_Software_Stack.rst b/source/linux/Overview/_Processor_SDK_Linux_Software_Stack.rst index da412ae51..0dfb1f42a 100644 --- a/source/linux/Overview/_Processor_SDK_Linux_Software_Stack.rst +++ b/source/linux/Overview/_Processor_SDK_Linux_Software_Stack.rst @@ -11,7 +11,7 @@ components provided with the Processor SDK for Linux. Availability of certain applications are platform dependent and clarified in the associated User Guides. -.. ifconfig:: CONFIG_part_family in ('General_family', 'AM335X_family', 'AM437X_family', 'AM57X_family') +.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family', 'AM57X_family') .. Image:: /images/Processor_SDK_linux_stack_v3.png diff --git a/source/linux/Release_Specific.rst b/source/linux/Release_Specific.rst index c063cec70..11fbb3c86 100644 --- a/source/linux/Release_Specific.rst +++ b/source/linux/Release_Specific.rst @@ -5,12 +5,8 @@ Release Specific .. toctree:: :maxdepth: 5 - Release_Specific_CoreSDK_Release_Notes Release_Specific_PLSDK_Release_Notes - Release_Specific_CoreSDK_Performance_Guide Release_Specific_Performance_Guide - Release_Specific_CoreSDK_Yocto_layer_Configuration Release_Specific_Yocto_layer_Configuration - Release_Specific_CoreSDK_Migration_Guide Release_Specific_Migration_Guide Release_Specific_Supported_Platforms_and_Versions diff --git a/source/linux/Release_Specific/_CoreSDK_Layer_Configuration.rst b/source/linux/Release_Specific/_CoreSDK_Layer_Configuration.rst deleted file mode 100644 index bd18aa87b..000000000 --- a/source/linux/Release_Specific/_CoreSDK_Layer_Configuration.rst +++ /dev/null @@ -1,24 +0,0 @@ -************************** -Yocto Layer Configuration -************************** - -Processor SDK uses the following oe-layersetup configs to configure the -meta layers. These are the used in the command: - -``$ ./oe-layersetup.sh -f `` - - - | - | The following config files located in the **configs/coresdk** - directory of the `oe-layersetup git repo `_. - - +-----------------------------------+----------------------------------+----------------------------------------------------------------------------+ - | Config File | Description | Supported machines/platforms | - +===================================+==================================+============================================================================+ - | coresdk-11.01.05-config.txt | CoreSDK 11.01 Sitara Release | am64x 2.0, am62x, am62sip, am62x-lp, am62px 1.0, am62px 1.1, am62d | - +-----------------------------------+----------------------------------+----------------------------------------------------------------------------+ - | coresdk-11.01.07-config.txt | CoreSDK 11.01 Sitara Release | am62a | - +-----------------------------------+----------------------------------+----------------------------------------------------------------------------+ - | coresdk-11.01.16-config.txt | CoreSDK 11.01 Sitara Release | am62lx 1.1, am62px 1.1, am62px 1.2 | - +-----------------------------------+----------------------------------+----------------------------------------------------------------------------+ - diff --git a/source/linux/Release_Specific_CoreSDK_Migration_Guide.rst b/source/linux/Release_Specific_CoreSDK_Migration_Guide.rst deleted file mode 100644 index a2c705bd6..000000000 --- a/source/linux/Release_Specific_CoreSDK_Migration_Guide.rst +++ /dev/null @@ -1,93 +0,0 @@ -***************************** -CoreSDK Linux Migration Guide -***************************** - -.. rubric:: Overview - -This page covers migration information for applications built on top -of the Processor SDK for Linux. - -Processor CoreSDK 11.xx Releases -================================ - - -Processor CoreSDK Sitara 11.01 ------------------------------- - -- Tag Info: 11.01.16 -- This is the Fifth Reference release in the 2025 LTS stream, with new stable versions of Kernel, U-boot, toolchain and Yocto Distribution. -- Platforms Supported : AM62L SR1.1 (HS-FS, HS-SE), AM62Px SR1.1 (HS-FS, HS-SE) , AM62Px SR1.2 (HS-FS, HS-SE) -- Kernel 6.12.43 -- U-Boot 2025.01 -- ATF 2.13+ (For AM62Px), 2.12+ (For AM62Lx) -- OPTEE 4.7.0+ -- Toolchain GCC 13.4 -- Yocto Scarthgap/5.0 - - -Processor CoreSDK Sitara 11.01 ------------------------------- - -- Tag Info: 11.01.07 -- This is the Fourth Reference release in the 2025 LTS stream, with new stable versions of Kernel, U-boot, toolchain and Yocto Distribution. -- Platforms Supported : AM62A (HS-FS, HS-SE) -- Kernel 6.12.35 -- U-Boot 2025.01 -- ATF 2.13+ -- OPTEE 4.6.0 -- Toolchain GCC 13.4 -- Yocto Scarthgap/5.0 - - -Processor CoreSDK Sitara 11.01 ------------------------------- - -- Tag Info: 11.01.05 -- This is the Third Reference release in the 2025 LTS stream, with new stable versions of Kernel, U-boot, toolchain and Yocto Distribution. -- Platforms Supported : AM62Px SR1.0 (HS-FS, HS-SE), AM62Px SR1.1 (HS-FS, HS-SE), AM62x ( GP, HS-FS, HS-SE), AM62x LP (HS-FS, HS-SE), AM64x 2.0 (HS-FS), AM62SIP (HS-FS, HS-SE) , AM62D (HS-FS) -- Kernel 6.12.35 -- U-Boot 2025.01 -- ATF 2.13+ -- OPTEE 4.6.0 -- Toolchain GCC 13.4 -- Yocto Scarthgap/5.0 -- Graphics DDK 24.2 - - -Processor CoreSDK Sitara 11.00 ------------------------------- - -- Tag Info: 11.00.15 -- This is the Second Reference release in the 2025 LTS stream, with new stable versions of Kernel, U-boot, toolchain and Yocto Distribution. -- Platforms Supported : AM62Lx 1.0 (HS-FS, HS-SE) -- Kernel 6.12.24 -- U-Boot 2025.01 -- ATF 2.12+ -- Toolchain GCC 13.3 -- Yocto Scarthgap/5.0 - - -Processor CoreSDK Sitara 11.00 ------------------------------- - -- Tag Info: 11.00.09 -- This is the First Reference release in the 2025 LTS stream, with new stable versions of Kernel, U-boot, toolchain and Yocto Distribution. -- Platforms Supported : AM62Px (HS-FS, HS-SE), AM62x ( GP, HS-FS, HS-SE), AM62x LP (HS-FS, HS-SE), AM64x 2.0 (HS-FS), AM62A (HS-FS, HS-SE) -- Kernel 6.12.17 -- U-Boot 2025.01 -- ATF 2.12+ -- OPTEE 4.5.0 -- Toolchain GCC 13.3 -- Yocto Scarthgap/5.0 -- Graphics DDK 24.2 - - -.. note:: - - - For U-Boot builds, k3-image-gen and core-secdev-k3 are no longer needed - as **binman** is used instead. Please refer to :ref:`U-Boot build - instructions` for the updated steps. - - - For Linux builds, generic ``defconfig`` is used instead of custom - fragments. Please refer to :ref:`linux users guide ` - for build instructions. diff --git a/source/linux/Release_Specific_CoreSDK_Release_Notes.rst b/source/linux/Release_Specific_CoreSDK_Release_Notes.rst deleted file mode 100644 index 4d0417df8..000000000 --- a/source/linux/Release_Specific_CoreSDK_Release_Notes.rst +++ /dev/null @@ -1,80 +0,0 @@ -************************************ -Release Notes -************************************ - -Overview -======== - -The **Processor-CoreSDK for Linux** -provides a fundamental software platform for development, deployment and -execution of Linux based applications and includes the following: - - * Bootloaders and Filesystems. - * Prebuilt Binaries. - * Detailed Release Notes. - -Licensing -========= - -Please see software manifest, which outlines the licensing -status for all packages included in the prebuilt binaries location. - - -Release 11.01 -============= - -Released July 2025, October 2025 ( For AM62Lx SR1.1, AM62Px SR 1.2) - -.. rubric:: What's New - :name: whats-new - -**Processor SDK 11.01 Sitara Release supports the following platforms** - * tag: 11.01.16 - * AM62L SR1.1 (HS-FS, HS-SE), AM62Px 1.1,1.2 (HS-FS, HS-SE) - * tag: 11.01.07 - * AM62A (HS-FS, HS-SE) - * tag: 11.01.05 - * AM62Px 1.0,1.1 (HS-FS, HS-SE) - * AM62x ( GP, HS-FS, HS-SE) - * AM62x LP (HS-FS, HS-SE) - * AM62SIP (HS-FS, HS-SE) - * AM64x 2.0 (HS-FS) - * AM62D (HS-FS) - -.. _release-specific-build-information: - -Release Tag Information ------------------------ - -.. list-table:: - :header-rows: 1 - :widths: 15, 30, 30, 30 - - * - Component - - Branch Info - - Tag Info - - Config Info - * - U-Boot - - `ti-u-boot-2025.01 `__ - - `11.01.16 `__ - - `Board Configs `__ - * - TF-A - - AM62Lx `ti-master `__ , All other K3 `master `__ - - AM62Lx `v2.12+ `__, All other K3 `v2.13 `__ - - - * - OPTEE - - `master `__ - - `4.7.0+ `__ - - - * - Linux Kernel - - `ti-linux-6.12.y `__ - - `11.01.16 `__ - - `non-RT `__ , `RT `__ - * - meta-ti - - `scarthgap `__ - - `11.01.16 `__ - - `Board Configs `__ - * - meta-arago - - `scarthgap `__ - - `11.01.16 `__ - - diff --git a/source/linux/Release_Specific_CoreSDK_Yocto_layer_Configuration.rst b/source/linux/Release_Specific_CoreSDK_Yocto_layer_Configuration.rst deleted file mode 100644 index 17eb66269..000000000 --- a/source/linux/Release_Specific_CoreSDK_Yocto_layer_Configuration.rst +++ /dev/null @@ -1,6 +0,0 @@ -.. _yocto-layer-configuration: - -.. ************************************ -.. Layer Configuration -.. ************************************ -.. include:: Release_Specific/_CoreSDK_Layer_Configuration.rst