diff --git a/configs/AM335X/AM335X_linux_config.txt b/configs/AM335X/AM335X_linux_config.txt index e2fe88243..8c94cd08c 100644 --- a/configs/AM335X/AM335X_linux_config.txt +++ b/configs/AM335X/AM335X_linux_config.txt @@ -24,7 +24,6 @@ Replacement Variables '__SDK_DOWNLOAD_URL__' : '`AM335X-Linux-SDK-Download-page `__' '__LINUX_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__LINUX_UBUNTU_VERSION_SHORT__' : '22.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' @@ -36,7 +35,7 @@ Configuration Values 'CONFIG_sdk' : 'SITARA' 'CONFIG_image_type' : 'default' 'CONFIG_icss_support' : 'yes' -'CONFIG_rt_linux_support' : 'yes' +'CONFIG_rt_linux_support' : 'no' 'CONFIG_gpu_ip' : 'SGX' 'CONFIG_crypto' : 'omap' diff --git a/configs/AM335X/AM335X_linux_toc.txt b/configs/AM335X/AM335X_linux_toc.txt index 4e47ef257..b8e1411f9 100644 --- a/configs/AM335X/AM335X_linux_toc.txt +++ b/configs/AM335X/AM335X_linux_toc.txt @@ -132,10 +132,6 @@ linux/How_to_Guides/Target/How_to_fix_y2k38 linux/How_to_Guides/Target/How_to_Change_dtb_File linux/How_to_Guides/Target/How_to_Boot_Beagle_Bone_Black_with_Processor_SDK_Linux linux/How_to_Guides/Target/How_to_Program_Beaglebone_Black_eMMC_via_SD_Card -linux/How_to_Guides_Hardware_Setup_with_CCS -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_Board_Port linux/How_to_Guides/Board_Port/U-Boot linux/How_to_Guides/Board_Port/Linux @@ -154,7 +150,6 @@ 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/AM437X/AM437X_linux_config.txt b/configs/AM437X/AM437X_linux_config.txt index 9f38443a3..04178de84 100644 --- a/configs/AM437X/AM437X_linux_config.txt +++ b/configs/AM437X/AM437X_linux_config.txt @@ -24,7 +24,6 @@ Replacement Variables '__SDK_DOWNLOAD_URL__' : '`AM437X-Linux-SDK-Download-page `__' '__LINUX_UBUNTU_VERSION_LONG__' : '22.04 (64-bit)' '__LINUX_UBUNTU_VERSION_SHORT__' : '22.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' @@ -36,7 +35,7 @@ Configuration Values 'CONFIG_sdk' : 'SITARA' 'CONFIG_image_type' : 'default' 'CONFIG_icss_support' : 'yes' -'CONFIG_rt_linux_support' : 'yes' +'CONFIG_rt_linux_support' : 'no' 'CONFIG_gpu_ip' : 'SGX' 'CONFIG_crypto' : 'omap' diff --git a/configs/AM437X/AM437X_linux_toc.txt b/configs/AM437X/AM437X_linux_toc.txt index 61d83d590..e5bce67d2 100644 --- a/configs/AM437X/AM437X_linux_toc.txt +++ b/configs/AM437X/AM437X_linux_toc.txt @@ -126,8 +126,6 @@ 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_fix_y2k38 -linux/How_to_Guides_Hardware_Setup_with_CCS -linux/How_to_Guides/Hardware_Setup_with_CCS/EVMK2H_Hardware_Setup linux/How_to_Guides_Board_Port linux/How_to_Guides/Board_Port/U-Boot common/PRU-ICSS/Getting_Started_with_PSSP @@ -145,7 +143,6 @@ 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/source/common/EVM_Hardware_Setup/_EVMK2H_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_EVMK2H_Hardware_Setup.rst deleted file mode 100644 index 2b31e2807..000000000 --- a/source/common/EVM_Hardware_Setup/_EVMK2H_Hardware_Setup.rst +++ /dev/null @@ -1,656 +0,0 @@ - -EVMK2H Hardware Setup Guide -============================ - -Hardware Setup -------------------- - -.. note:: The EVM board is sensitive to electrostatic discharges (ESD). Use a grounding strap or other device to prevent damaging the board. Be sure to connect communication cables before applying power to any equipment. - -FTDI Driver Installation on PC Host -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The K2 EVM has a FTDI FT2332HL device on board. A driver must be -installed on the PC Host in order to be able to communicate with the EVM -using the FTDI mini-USB connector located under the mini-USB connector -of the emulator daughter card. The driver can be downloaded from here -`FTDI Driver `__. - -.. note:: Before testing the usb connection, make sure that the mini-usb cable is plugged into the port on the base board. (and not connected to the daughter card). - -After installing the driver and connecting the USB cable, two COM ports -should be visible in the list of COM ports available to connect to in -the PC Host terminal console. The lower COM port corresponds to the SoC -UART and the higher one corresponds to the MCU UART. - -BMC Version Check and Update -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Read -`BMC\_In-Field\_Update `__ -to check BMC version and update if necessary. - -UCD Power Management Modules In-Field Update -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -There are three power management modules (sometimes called the UCDs) -located on the EVM. Each module can be identified by it's address: -104(68h), 52(34h), and 78(4Eh). Each module contains non-volatile -registers that determine it's operation. It may be necessary to update -these registers after the board has been shipped. This update can be -performed through the BMC, which can issue commands to the UCD modules -to update the register settings. The **Power Management Configuration -Update Tool** (bmc\_tool.py) performs the task of sending commands to -the BMC to get the current module versions, and perform updates using -configuration files. Instructions for executing the update tool -(bmc\_tool.py) are available here: :download:`BMC Tool UCD Update Guide <../../../files/Bmc_tool_ucd_update_guide_v2.pdf>` - -The latest version of the tool is available -`here `__. -The latest configuration files (txt files) are available -`here `__. -Please follow the instructions provided to check the current module -versions, and update them accordingly. - -.. note:: The DIP switch configuration of the board when running the update is irrelevant. - -.. note:: BMC versions 1.0.1.3a and earlier will not work properly with the **Get Versions** feature of the Update Tool. Upgrade to a more recent version of the BMC to use this functionality. - -| - -| - -Attach the Ethernet cable -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Using the Ethernet cable supplied, connect one end of the cable to the -Ethernet Port 0 (marked ENET0 on the board) on the EVM and the other end -to your PC. - -This picture shows which Ethernet Port is 0: - -.. image:: /images/K2H_ENET0.jpg - -Connect the JTAG interface -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Use the USB to USB mini-B cable provided. Connect the USB mini-B -connector to the USB mini-B interface on the XDS-2xx daughter card on -the EVM, and the USB connector to your PC. This enables XDS-2xx -emulation and is directly useable by CCS. If you are using a different -JTAG, connect it now. - -K2H Set the boot mode switch SW1 -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -.. rubric:: K2H No Boot/JTAG DSP Little Endian Boot mode - :name: k2h-set-no-boot-mode - -For **Rev 0B EVM**, the setting is as follows - -:: - - SW1 - 4(ON) 3(ON) 2(ON) 1(OFF) - -For **Rev 1.0 EVM**, the setting is as follows: - -:: - - SW1 - 1(OFF) 2(OFF) 3(OFF) 4(ON) - -| - -.. rubric:: K2H SPI Little Endian Boot mode - :name: k2h-spi-le-boot-mode - -For **Rev 0B EVM**, the setting is as follows: - -:: - - SW1 - 4(ON) 3(ON) 2(OFF) 1(ON) - -For **Rev 1.0 EVM**, the setting is as follows: - -:: - - SW1 - 1(OFF) 2(OFF) 3(ON) 4(OFF) - -DDR Configuration (Rev 0B EVM only) -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -For **Rev 0B EVM**, the following procedure is required for proper DDR -configuration: - -- Connect the MCU UART port to PC using the serial cable provided with - the EVM. The MCU UART port is the 4-pin white connector farthest from - the edge of the EVM. Alternatively it is also possible to connect a - mini-USB cable to the FTDI mini-USB connector of the EVM. This will - provide access to both the SoC and the MCU UART ports. -- Start Tera Term or Hyper terminal and set to 115200 board rate, 8-bit - data, 1-bit stop and no parity/flow control. -- Power on the EVM. MCU UART console will show user prompt once MCU - boot up is complete. Type the following commands at the console to - setup DDR3A. Ethernet requires DDR3A and will not work with DDR3B - which is default in Rev 0B EVMs. - -:: - - BMC> setboot 100001 - BMC> fullrst - -Attach the serial port cable to the SoC UART port -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Connect the SoC UART port to PC using the serial cable provided with the -EVM. The SoC UART port is the 4-pin white connector closest to the edge -of the EVM. - -Start Tera Term or Hyper terminal and set to 115200 board rate, 8-bit -data, 1-bit stop and no parity/flow control. - -Connect the power cable -^^^^^^^^^^^^^^^^^^^^^^^^ - -Connect the power cable to the EVM power jack on the board. To be ESD -safe, plug in the other end of the power cable only after you have -connected the power cord to the board. Then turn on the board. - -BMC In-Field Update --------------------- - -BMC, or Board Management Controller, takes care of the power, clocks, -resets, bootmodes, etc. of the EVM. - -For Rev1.0 EVMs an in-field update may be necessary as a very small -quantity were delivered with an old revision of the BMC. If your EVM is -using version 1.0.1.3 then it should be updated to version 1.0.1.3a. The -update corrects the way that the boot mode pins are interpreted. - -You can check the version by: - -**1. Opening a hyperterminal or another similar type of console -application.** - -**2. Set COM Port to higher value** - -- When you connect to FTDI mini-USB on the EVM it will provide 2 COM - port connections, one to the SOC UART and one to BMC UART. -- The SOC UART will always be the lowest value COM port, for example - COM5, and the BMC UART will always be the higher value COM port, for - example COM6. (Actual COM PORT values will vary). - -**3. Set COM port properties appopriately:** - -- Baud Rate or Bits per second: 115200 -- Data Bits: 8 -- Parity: None -- Stop Bits: 1 -- Flow Control: None - -**4. At BMC prompt typer 'ver' (no quotes)** - -**5. Check BMC Version** - -| - -.. image:: /images/Bmc_ver_screenshot.JPG - - -| -| - -If an in-field update is needed, downloaded the latest version -`here `__ -(labeled **Board Management Controller Binaries (BMC)**) and continue -with the following steps. - -| - -**Prepare EVM for in-field update:** - -#. Remove power to the EVM. -#. Set boot mode to "No Boot mode" -#. Remove the MCU\_BOOTSELECT (CN9) jumper (see picture below for - location of jumper: Referred as "**G: MCU Reset Jumper for BMC field - update**\ "). -#. Make sure your USB cable is connected to FTDI mini-USB (not XDS200 - Emulator USB) OR connect 4pin UART cable to COM1: MCU UART connector. -#. Make sure no HyperTerminal/Console connected to BMC COM port are open - or active. -#. Use the LM Flash Programmer (available - `here `__) to update the - firmware, as detailed in the steps below. - -| - -**Perform in-field update:** - -#. Apply power to the EVM. No LED's will be illuminated and no LCD - backlight or characters will be on because the BMC is waiting for a - command rather than executing from Flash. -#. Open the LM Flash programmer utility. (Default location Start Menu -> - All Programs -> Texas Instruments -> Stellaris -> LM Flash Programmer - -> LM Flash Programmer ) -#. In the LM Flash Programmer Utility ‘Configuration’ tab, in the - interface section, select ‘Serial (UART)’ from the drop-down box on - the left. -#. Select the BMC COM Port (the same COM port used to issue the ver - command earlier), and set the ‘Baud Rate’ to 115200. -#. Set ‘Transfer Size’ to 60, and make sure ‘Disable Auto Baud Support’ - is unchecked. - - .. image:: /images/LMflashProg_Config.png - -#. In the ‘Program’ tab, Browse to the location of the binary file - containing the firmware update, and select it. -#. Leave all other options as default, and press the ‘Program’ button. -#. After the programming is complete, power off the board. -#. Reconnect the jumper. -#. Open the HyperTerminal/Console for the BMC COM port. -#. Apply power to the EVM. When BMC completes initialization of board it - will show latest version of BMC in Console. -#. If step 9 was done after power was applied, just type "ver" at BMC - prompt. - -.. image:: /images/K2EVM.jpg - -DIP Switch and Bootmode Configurations ------------------------------------------ - -.. _BootModeConfiguration: - -Rev 1.0 EVM SW1 switch Bootmode Configuration -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -| The table below shows the bootmode combinations for the BMC v1.0.1.3a. - -+--------------------+------------------------+ -| DIP Switch | Bootmode | -| (p1, p2, p3, p4) | | -+====================+========================+ -| 0000 | ARM NAND | -+--------------------+------------------------+ -| 0001 | DSP no-boot | -+--------------------+------------------------+ -| 0010 | ARM SPI | -+--------------------+------------------------+ -| 0011 | ARM I2C | -+--------------------+------------------------+ -| 0100 | ARM UART | -+--------------------+------------------------+ -| 0101 | Reserved | -+--------------------+------------------------+ -| 0110 | Reserved | -+--------------------+------------------------+ -| 0111 | Reserved | -+--------------------+------------------------+ -| 1000 | Reserved | -+--------------------+------------------------+ -| 1001 | Reserved\ :sup:`[1]` | -+--------------------+------------------------+ -| 1010 | Reserved | -+--------------------+------------------------+ -| 1011 | Reserved | -+--------------------+------------------------+ -| 1100 | Reserved | -+--------------------+------------------------+ -| 1101 | Reserved | -+--------------------+------------------------+ -| 1110 | Reserved | -+--------------------+------------------------+ -| 1111 | Reserved | -+--------------------+------------------------+ - -:sup:`[1]`\ In revision BMC v1.0.1.4 this is 10 MHz SPI NOR. This will -not continue in future versions. - -Changing the Bootmode -^^^^^^^^^^^^^^^^^^^^^^^ - -In BMC v1.0.1.x the only way to use a bootmode that is not supported by -the DIP switch combinations is to use the 'setboot' and 'fullrst' -commands. To set the bootmode use the setboot command, which takes a 32 -bit value in hex as its only argument: - -:: - - setboot 00110CE7 - -Then use the fullrst command to boot the SoC into this bootmode: - -:: - - fullrst - -This process is volatile, and will have to be repeated every time the -board is power cycled. - -In BMC v1.0.2.x the setboot command has been removed. It has been -replaced with the bootmode command, which performs various functions -depending on the way in which the command is used. The command works -with 16 bootmodes, which are representative of the various DIP switch -combinations; the bootmodes are numbered 0 - 15. Bootmodes 8 - 15 are -User-Defined, and may be altered and stored using the command (explained -below). Each bootmode consists of a title, a high value, and a low -value. The high value is currently not used. The low value is a 32 bit -value in hex, and is the same as the value previously used by setboot. -The bits of low value (and the setboot argument) are shown in the table -below). - -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| Bit | Devstat Bit | Config Pin Function | Normal Pin Function | Comments | -+=======+===============+=======================+=======================+================================================================+ -| 31 | | | | Reserved | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 30 | | | | Reserved | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 29 | | | | Reserved | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 28 | | | | Reserved | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 27 | | | | Reserved | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 26 | | | | Reserved | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 25 | | PACLKSEL | PACLKSEL | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 24 | | CORECLKSEL | CORECLKSEL | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 23 | | | | Reserved | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 22 | | AVSIFSEL1 | TIMI1 | Reserved: EVM forces these bits to strap values during reset | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 21 | | AVSIFSEL0 | TIMI0 | Reserved: EVM forces these bits to strap values during reset | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 20 | | DDR3\_REMAP\_EN | GPIO16 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 19 | | ARM\_LENDIAN | GPIO15 | 0 = little, 1 = is not supported; do in SW | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 18 | | MAINPLLODSEL | CORESEL3 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 17 | | ARMAVSSHARED | CORESEL2 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 16 | 16 | BOOTMODE15 | CORESEL2 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 15 | 15 | BOOTMODE14 | CORESEL1 | Element | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 14 | 14 | BOOTMODE13 | CORESEL0 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 13 | 13 | BOOTMODE12 | GPIO13 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 12 | 12 | BOOTMODE11 | GPIO12 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 11 | 11 | BOOTMODE10 | GPIO11 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 10 | 10 | BOOTMODE9 | GPIO10 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 9 | 9 | BOOTMODE8 | GPIO9 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 8 | 8 | BOOTMODE7 | GPIO8 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 7 | 7 | BOOTMODE6 | GPIO7 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 6 | 6 | BOOTMODE5 | GPIO6 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 5 | 5 | BOOTMODE4 | GPIO5 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 4 | 4 | BOOTMODE3 | GPIO4 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 3 | 3 | BOOTMODE2 | GPIO3 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 2 | 2 | BOOTMODE1 | GPIO2 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 1 | 1 | BOOTMODE0 | GPIO1 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ -| 0 | 0 | LENDIAN | GPIO0 | | -+-------+---------------+-----------------------+-----------------------+----------------------------------------------------------------+ - -There are 5 different formats to the bootmode command: - -:: - - bootmode - -When the command is entered with no arguments the current bootmode will -be displayed. - -:: - - bootmode all - -This format will display all 16 bootmodes and mark the currently -selected bootmode. - -:: - - bootmode #x - -This will change the currently selected bootmode to the bootmode -represented by x. For example, if the board is booted with DIP switch -setting 1(OFF) 2(OFF) 3(OFF) 4(ON) then the bootmode would be 1 - DSP -NO-BOOT. If 'bootmode #2' is entered, the bootmode represented by DIP -switch setting 1(OFF) 2(OFF) 3(ON) 4(OFF) would become the current -bootmode (ARM SPI-NOR BOOT). If the 'reboot' command is given, the SoC -will be rebooted using this new bootmode. This format is volatile, -meaning once power is removed, the bootmode at the next power up will be -determined by the DIP switch. - -:: - - bootmode read - -This format reads the current value of the DIP switch, and changes the -current bootmode to this value. For example, if the board is booted with -DIP switch setting 1(OFF) 2(OFF) 3(OFF) 4(ON) then the bootmode would be -1 - DSP NO-BOOT. If the DIP switch is changed to 1(OFF) 2(OFF) 3(ON) -4(OFF) and then the command 'bootmode read' is given, the board will -change to bootmode 2 - ARM SPI-NOR BOOT. If the 'reboot command is then -given, the SoC will be rebooted using this new bootmode. - -:: - - bootmode [#]x hi_value lo_value title - -This bootmode is used to alter User-Defined bootmodes (bootmodes 8 - -15). x is the index of the bootmode to be set, as such its appropriate -value range is 8 - 15, any other value will return an error. hi\_value -is not currently used, and should always be set to 0. lo\_value is a 32 -bit hex value whose bits are representative of the table above. title is -a given string that is displayed by the bootmode command to help better -understand what the bootmode does, it has no purpose within the actual -booting of the board. The option '#' is used to determine whether the -bootmode will be saved. If # is used, the bootmode will be saved to -flash, meaning the new value is tied to the DIP switch, and will remain -even if power is removed from the board. If # is not given, then the -change will be lost as soon as power is removed. Some examples with -descriptions are given below: - -:: - - bootmode 8 0 112005 ARM_SPI - -bootmode 8 will be set to 112005 and given the title ARM\_SPI. To boot -into this bootmode, the command 'bootmode #8' followed by 'reboot' would -be given (or changing the DIP switch to 1(ON) 2(OFF) 3(OFF) 4(OFF) -without removing power, then entering 'bootmode read' followed by -'reboot'). Once power is removed, this change is lost. - -:: - - bootmode #10 0 12cba1 RANDOM_BOOT - -bootmode 10 will be set to 12cba1 and given the title RANDOM\_BOOT. This -is now the permanent value of bootmode 10; the change will persist even -if power is removed. - -Connect to EVMK2H using CCS --------------------------------- - -**Step 1:** Configure the EVM hardware - -- Setup the EVM to DSP no boot using SW1 as described in the section BootModeConfiguration_ - -- Connect mini USB cable to the XDS2xx MIPI adapter card marked J1 or - connect external emulator to the MIPI connector on J3 - -.. note:: - For newer versions of CCS, a XDS200 firmware update is recommended which user can perform using instruction on the article - `Updating XDS200 Firmware `__ - -**Step 2:** Create CCS Target configuration - -Launch CCS on your host machine. Select View Tab and select the "Target -configuration" - -.. image:: /images/New_TargetConfig.png - -| - -Create New Target configuration in CCS by selecting appropriate -emulator. For Default on board emulator select "Texas instruments XDS2xx -Debug Probe" and select the target device as 66AK2H12. - -.. image:: /images/K2H_TargetConfig.png - -Go to the Advanced Tab where you will see all the cores on the SOC -listed. In order to initialize the clocks and external DDR memory on the -device, users are required to use a initialization Gel scripts. To -populate the Gel Select A15\_0 and then hit Browse and locate the GEL in -the CCS installation under the following path: -CCS\_INSTALL/ccs\_base/emulation/boards/xtcievmk2x/gel - -.. image:: /images/ARM_GEL.png - -DSP developers, can also select C66x\_0 and populate the DSP GEL file -that is found in the same location. - -.. image:: /images/DSP_GEL.png - -Going back to the Basic Tab, Save the configuration. For additional -sanity check, you can also test connection. - -| - -**Step 3:** Connect to the cores - -Right click on the target configuration and Select "Launch Target -configuration". Wait for CCS debug View to launch and display the eight -C66x cores and 4 A15 cores. - -.. image:: /images/Launch_TargetConfig.png - -.. image:: /images/Connect_A15.png - -Start by connecting to A15\_0 and C66x\_0. when you connect to the -cores, you will see the GEL script logs in the console window, which -indicates that device clocks, PSC and external DDR memory has been -initialized. The GEL log from target connect is provided below for -reference. - -:: - - arm_A15_0: GEL Output: Disabling MMU - arm_A15_0: GEL Output: Disabling Caches - arm_A15_0: GEL Output: Invalidate Instruction Caches - arm_A15_0: GEL Output: Enabling non-secure access to cp10 and cp11 - arm_A15_0: GEL Output: Enabled non-secure access to cp10 and cp11 - arm_A15_0: GEL Output: Enabling SMP bit in ACTLR - arm_A15_0: GEL Output: Enabled SMP bit in ACTLR - arm_A15_0: GEL Output: Entering NonSecure Mode - arm_A15_0: GEL Output: Entered NonSecure Mode - arm_A15_0: GEL Output: Disabling MMU - arm_A15_0: GEL Output: Disabling Caches - arm_A15_0: GEL Output: Invalidate Instruction Caches - arm_A15_0: GEL Output: - -Connecting Target... - -:: - - arm_A15_0: GEL Output: Disabling MMU - arm_A15_0: GEL Output: Disabling Caches - arm_A15_0: GEL Output: Invalidate Instruction Caches - arm_A15_0: GEL Output: Enabling non-secure access to cp10 and cp11 - arm_A15_0: GEL Output: Enabled non-secure access to cp10 and cp11 - arm_A15_0: GEL Output: Enabling SMP bit in ACTLR - arm_A15_0: GEL Output: Enabled SMP bit in ACTLR - arm_A15_0: GEL Output: Entering NonSecure Mode - arm_A15_0: GEL Output: Entered NonSecure Mode - arm_A15_0: GEL Output: Disabling MMU - arm_A15_0: GEL Output: Disabling Caches - arm_A15_0: GEL Output: Invalidate Instruction Caches - arm_A15_0: GEL Output: TCI6638K2K GEL file Ver is 1.89999998 - arm_A15_0: GEL Output: Disabling MMU - arm_A15_0: GEL Output: Disabling Caches - arm_A15_0: GEL Output: Invalidate Instruction Caches - arm_A15_0: GEL Output: Enabling non-secure access to cp10 and cp11 - arm_A15_0: GEL Output: Enabled non-secure access to cp10 and cp11 - arm_A15_0: GEL Output: Enabling SMP bit in ACTLR - arm_A15_0: GEL Output: Enabled SMP bit in ACTLR - arm_A15_0: GEL Output: Entering NonSecure Mode - arm_A15_0: GEL Output: Entered NonSecure Mode - arm_A15_0: GEL Output: Disabling MMU - arm_A15_0: GEL Output: Disabling Caches - arm_A15_0: GEL Output: Invalidate Instruction Caches - arm_A15_0: GEL Output: Detected PLL bypass disabled: SECCTL[BYPASS] = 0x00000000 - arm_A15_0: GEL Output: (3a) PLLCTL = 0x00000040 - arm_A15_0: GEL Output: (3b) PLLCTL = 0x00000040 - arm_A15_0: GEL Output: (3c) Delay... - arm_A15_0: GEL Output: (4)PLLM[PLLM] = 0x0000000F - arm_A15_0: GEL Output: MAINPLLCTL0 = 0x07000000 - arm_A15_0: GEL Output: (5) MAINPLLCTL0 = 0x07000000 - arm_A15_0: GEL Output: (5) MAINPLLCTL1 = 0x00000040 - arm_A15_0: GEL Output: (6) MAINPLLCTL0 = 0x07000000 - arm_A15_0: GEL Output: (7) SECCTL = 0x00090000 - arm_A15_0: GEL Output: (8a) Delay... - arm_A15_0: GEL Output: PLL1_DIV3 = 0x00008002 - arm_A15_0: GEL Output: PLL1_DIV4 = 0x00008004 - arm_A15_0: GEL Output: PLL1_DIV7 = 0x00000000 - arm_A15_0: GEL Output: (8d/e) Delay... - arm_A15_0: GEL Output: (10) Delay... - arm_A15_0: GEL Output: (12) Delay... - arm_A15_0: GEL Output: (13) SECCTL = 0x00090000 - arm_A15_0: GEL Output: (Delay... - arm_A15_0: GEL Output: (Delay... - arm_A15_0: GEL Output: (14) PLLCTL = 0x00000041 - arm_A15_0: GEL Output: PLL has been configured (CLKIN * PLLM / PLLD / PLLOD = PLLOUT): - arm_A15_0: GEL Output: PLL has been configured (122.879997 MHz * 16 / 1 / 2 = 983.039978 MHz) - arm_A15_0: GEL Output: Switching on ARM Core 0 - arm_A15_0: GEL Output: Switching on ARM Core 1 - arm_A15_0: GEL Output: Switching on ARM Core 2 - arm_A15_0: GEL Output: Switching on ARM Core 3 - arm_A15_0: GEL Output: ARM PLL has been configured (125.0 MHz * 16 / 2 = 1000.0 MHz) - arm_A15_0: GEL Output: DISABLESTAT ---> 0x00000000 - arm_A15_0: GEL Output: Power on all PSC modules and DSP domains... - arm_A15_0: GEL Output: Power on all PSC modules and DSP domains... Done. - arm_A15_0: GEL Output: WARNING: SYSCLK is the input to the PA PLL. - arm_A15_0: GEL Output: Completed PA PLL Setup - arm_A15_0: GEL Output: PAPLLCTL0 - before: 0x0x09080500 after: 0x0x09080500 - arm_A15_0: GEL Output: PAPLLCTL1 - before: 0x0x00002040 after: 0x0x00002040 - arm_A15_0: GEL Output: DDR begin - arm_A15_0: GEL Output: XMC setup complete. - arm_A15_0: GEL Output: DDR3 PLL (PLL2) Setup ... - arm_A15_0: GEL Output: DDR3 PLL Setup complete, DDR3A clock now running at 666 MHz. - arm_A15_0: GEL Output: DDR3A initialization complete - arm_A15_0: GEL Output: DDR3 PLL Setup ... - arm_A15_0: GEL Output: DDR3 PLL Setup complete, DDR3B clock now running at 800MHz. - arm_A15_0: GEL Output: DDR3B initialization complete - arm_A15_0: GEL Output: DDR done - arm_A15_0: GEL Output: Entering A15 non secure mode .. - arm_A15_0: GEL Output: Disabling MMU - arm_A15_0: GEL Output: Disabling Caches - arm_A15_0: GEL Output: Invalidate Instruction Caches - arm_A15_0: GEL Output: Enabling non-secure access to cp10 and cp11 - arm_A15_0: GEL Output: Enabled non-secure access to cp10 and cp11 - arm_A15_0: GEL Output: Enabling SMP bit in ACTLR - arm_A15_0: GEL Output: Enabled SMP bit in ACTLR - arm_A15_0: GEL Output: Entering NonSecure Mode - arm_A15_0: GEL Output: Entered NonSecure Mode - arm_A15_0: GEL Output: Disabling MMU - arm_A15_0: GEL Output: Disabling Caches - arm_A15_0: GEL Output: Invalidate Instruction Caches - arm_A15_0: GEL Output: A15 non secure mode entered - -Users can now load and run code on the cores by using Run -> Load -Program. Happy Debugging !! - diff --git a/source/common/EVM_Hardware_Setup/_ICE_AM335x_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_ICE_AM335x_Hardware_Setup.rst deleted file mode 100644 index c767314b2..000000000 --- a/source/common/EVM_Hardware_Setup/_ICE_AM335x_Hardware_Setup.rst +++ /dev/null @@ -1,157 +0,0 @@ - -AM335x ICE EVM Hardware Setup -============================= - -Description ------------- - -The low-cost ICE EVM can be used for evaluation and development of -industrial communication type applications. It has been equipped with a -TI AM3359 processor and a defined set of features to allow the user to -experience specifically industrial communication solutions using serial -or Ethernet based interfaces. It is not intended as a generic -development platform as some of the features and interfaces supplied by -the AM335x are not accessible from the ICE board. Using standard -interfaces, the ICE board may interface to other processors or systems -and act as a communication gateway in this case. In addition it can -directly operate as a standard remote I/O system or simple sensor -connected to an industrial communication network. The embedded emulation -logic allows emulation and debug using standard development tools such -as TI’s Code Composer Studio by just using the supplied USB cable. - -EVM Layout and Key Components ------------------------------- - -.. Image:: /images/ICE_V2_marked.png - :scale: 50% - -Quick Start Guide --------------------- - -This section details how to quickly setup the AM3359 ICE. - -1. Unbox the board and identify the various components and connectors -shown above. - -2. Connect the power cable to the power jack on the board and plug it -into an AC power source. - -.. Image:: /images/ICE335924V.png - :scale: 50% - -Once powered on, the POWER ON LED (D16) and Industrial Output LEDs -(D6-D10, D12, D14, and D15) will turn on. - - -.. Note:: When powering the AM335x ICE, always use the supplied power supply (CUI/V-Infinity Part Number EMSA240075) or equivalent model having output voltage of +24VDC and output current max 0.75 Amps and that complies with applicable regional safety standards such as (by example) UL, CSA, VDE, CCC, PSE, etc. - -3. Connect the microUSB cable to the USB JTAG/Console port on the ICE board and connect to the USB on the host. Connect an Ethernet cable to -ETH0 if network connectivity is required. - -.. Image:: /images/ICE3359USB.png - :scale: 50% - -.. Note:: The serial port will not show up on the host PC until the board is powered on. - -4. Users can now connect to UART and the on-board XDS100v2 emulator from -the host machine. For UART port connections, set the serial terminal -software baud rate to 115200 to view the log messages. Connecting to the -target using the on-board emulator is discussed in the section below. - - -.. Image:: /images/Serial_connect.jpg - :scale: 50% - -.. Image:: /images/Baudrate.jpg - :scale: 50% - -Boot Configuration --------------------- - -The various boot configurations are discussed in the `Hardware User -Guide. `__ - -| - -Connecting the AM3359 ICE to Code Composer Studio ------------------------------------------------------- - -1. Download Code Composer Studio and the AM335x Sitara Device Support -package as described in the `Processor SDK RTOS Getting Started -Guide. `__ - -2. Connect the AM3359 ICE as described above in the -Quick Start Guide. - -3. Launch CCS and create a new target configuration file -(File->New->Target Configuration File) as shown below. Select the Texas -Instruments XDS100v2 USB Debug Probe and the ICE\_AM3359 as shown below. - - -.. Note:: If the ICE\_AM3359 target is not listed, make sure the latest Sitara Device Support package is installed by going to Help->Check for Updates. - -.. Image:: /images/ICE3359TargetConfig.png - :scale: 50% - -4. Click Save to save the target configuration. Then press Test -Connection to test the connection. If successful, a message should be -seen similar to the one below. - -.. Image:: /images/ICE3359Test.png - :scale: 50% - -5. Launch the target configuration and connect -to the ARM Cortex-A8. - -The complete GEL log from the Cortex A8 is provided below. - -:: - - CortxA8: Output: **** AM3359_ICE Initialization is in progress .......... - CortxA8: Output: **** AM335x ALL PLL Config for OPP == OPP100 is in progress ......... - CortxA8: Output: Input Clock Read from SYSBOOT[15:14]: 24MHz - CortxA8: Output: **** Going to Bypass... - CortxA8: Output: **** Bypassed, changing values... - CortxA8: Output: **** Locking ARM PLL - CortxA8: Output: **** Core Bypassed - CortxA8: Output: **** Now locking Core... - CortxA8: Output: **** Core locked - CortxA8: Output: **** DDR DPLL Bypassed - CortxA8: Output: **** DDR DPLL Locked - CortxA8: Output: **** PER DPLL Bypassed - CortxA8: Output: **** PER DPLL Locked - CortxA8: Output: **** DISP PLL Config is in progress .......... - CortxA8: Output: **** DISP PLL Config is DONE .......... - CortxA8: Output: **** AM335x ALL ADPLL Config for OPP == OPP100 is Done ......... - CortxA8: Output: **** AM335x DDR3 EMIF and PHY configuration is in progress... - CortxA8: Output: EMIF PRCM is in progress ....... - CortxA8: Output: EMIF PRCM Done - CortxA8: Output: DDR PHY Configuration in progress - CortxA8: Output: Waiting for VTP Ready ....... - CortxA8: Output: VTP is Ready! - CortxA8: Output: DDR PHY CMD0 Register configuration is in progress ....... - CortxA8: Output: DDR PHY CMD1 Register configuration is in progress ....... - CortxA8: Output: DDR PHY CMD2 Register configuration is in progress ....... - CortxA8: Output: DDR PHY DATA0 Register configuration is in progress ....... - CortxA8: Output: DDR PHY DATA1 Register configuration is in progress ....... - CortxA8: Output: Setting IO control registers....... - CortxA8: Output: EMIF Timing register configuration is in progress ....... - CortxA8: Output: EMIF Timing register configuration is done ....... - CortxA8: Output: PHY is READY!! - CortxA8: Output: DDR PHY Configuration done - CortxA8: GEL Output: Turning on EDMA... - CortxA8: GEL Output: EDMA is turned on... - CortxA8: Output: **** AM3359_ICE Initialization is Done ****************** - -| - -Running Board Diagnostics ------------------------------ - -The Processor SDK RTOS Diagnostic package is designed to be a set of -baremetal tests to run on a given board to provide data path continuity -testing on peripherals. - -To run diagnostics on the AM335x ICE, follow the procedure given in the -`RTOS Software Developer -Guide `__ diff --git a/source/common/EVM_Hardware_Setup/_ICE_AMIC110_EVM_Hardware_Setup.rst b/source/common/EVM_Hardware_Setup/_ICE_AMIC110_EVM_Hardware_Setup.rst deleted file mode 100644 index c8af2275e..000000000 --- a/source/common/EVM_Hardware_Setup/_ICE_AMIC110_EVM_Hardware_Setup.rst +++ /dev/null @@ -1,147 +0,0 @@ - -AMIC110 ICE EVM Hardware Setup -=============================== - -Description ---------------- - -The AMIC110 ICE is a high-performance, low-power platform that enables -users to evaluate and develop industrial communications applications for -the Sitara AMIC110 ARM Cortex-A8 processor SoC from Texas Instruments.™ - -EVM Layout and Key Components ------------------------------- - -.. Image:: /images/ICEAMIC110TopLayout.PNG - :scale: 50% - -.. Image:: /images/ICEAMIC110BottomLayout.PNG - :scale: 50% - -Quick Start Guide --------------------- - -This quick start guide can be found in the `Hardware User's -Guide `_. - - -1. Unbox the board and identify the various components -and connectors shown above. - -2. To download a bootable image into the onboard SPI Flash, connect a 20-pin JTAG emulator to J1 on the ICE board. For example, the XDS110 -or the XDS200 emulators may be used for this purpose and can be purchased from -the TI store: `XDS200 `__ and `XDS110 `__. - -.. Image:: /images/ICEAMIC110JTAG.PNG - :scale: 50% - -3. Connect the pin header connector of the included TTL-232R-3V3 serial cable to J3 on the ICE board. Ensure that pin 1 of the serial cable (black wire, marked with a triangle) is connected to pin 1 of J3, which is indicated by a dot on the silk screen. Connect the -USB connector of the serial cable to a PC host port. The datasheet for this cable can found at http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232R_CABLES.pdf - -.. Image:: /images/ICEAMIC110TTL.PNG - :scale: 50% - -4. Connect a CAT5 Ethernet cable from a PC running TwinCAT software to ECAT IN/PHY1 (J6) of the ICE board. If you have multiple ICE boards in a -chain, please connect another CAT5 Ethernet cable from ECAT OUT/PHY2 (J7) to PHY1 of the next ICE board. PHY2 of the last ICE board in the chain is left open. - -.. Image:: /images/ICEAMIC110ETHERNET.PNG - :scale: 50% - -5. Connect the recommended power supply (CUI Inc. SMI18-5-V-P5, procurable at: http://www.digikey.com/product-detail/en/cui-inc/SMI18-5-V-P5/102-3571-ND/5415042) or equivalent (Output voltage/current: 5 Volts DC +/- 10% @ 1.2 Amps; Output connector: 2.1-mm ID, 5.5-mm OD barrel plug, center positive) power supply to J8 on the ICE board. -Apply power to the power supply to power up the ICE board. Do not hot plug the 5-V supply into the ICE board. - -.. Image:: /images/ICEAMIC1105V.PNG - :scale: 50% - -Once the ICE board is powered on, the ON LED (D15) and LED4 (D19) will -turn on. - -6. The AMIC110 ICE can now be connected to from the host machine via -UART. The serial port should be setup as shown below. - -.. Image:: /images/Baudrate.jpg - :scale: 50% - -Boot Configuration ---------------------- - -The various boot configurations are discussed in the `Hardware User -Guide. `__ - -Connecting the AMIC110 ICE to Code Composer Studio ----------------------------------------------------- - -1. Download Code Composer Studio and the AMIC110 Sitara Device Support package as -described in the `Processor SDK RTOS Getting Started Guide `_. - -2. Connect the AMIC110 ICE as described in the -Quick Start Guide. - -3. Launch CCS and create a new target configuration file (File->New->Target Configuration File) as shown below. Select -the appropriate emulator and the ICE\_AMIC110 as the target as shown below. - - -.. Note:: If the ICE\_AMIC110 target is not listed, make sure the Sitara Device Support package v1.3.6 or greater is installed. - -.. Image:: /images/ICEAMIC110TargetConfig.PNG - :scale: 50% - -4. Click Save to save the target configuration. Then press Test Connection to test the connection. If successful, a message should be -seen similar to the one below. - -.. Image:: /images/ICEAMIC110Test.PNG - :scale: 50% - -5. Launch the target configuration and -connect to the ARM Cortex-A8. - -The complete GEL log from the Cortex A8 is provided below. - -:: - - CortxA8: Output: **** AMIC110_ICE & BoosterPack Initialization is in progress ...... - CortxA8: Output: **** AMIC110 & Booster Pack ALL PLL Config for OPP == OPP100 is in progress ........ - CortxA8: Output: Input Clock Read from SYSBOOT[15:14]: 25MHz - CortxA8: Output: **** Going to Bypass... - CortxA8: Output: **** Bypassed, changing values... - CortxA8: Output: **** Locking ARM PLL - CortxA8: Output: **** Core Bypassed - CortxA8: Output: **** Now locking Core... - CortxA8: Output: **** Core locked - CortxA8: Output: **** DDR DPLL Bypassed - CortxA8: Output: **** DDR DPLL Locked - CortxA8: Output: **** PER DPLL Bypassed - CortxA8: Output: **** PER DPLL Locked - CortxA8: Output: **** DISP PLL Config is in progress .......... - CortxA8: Output: **** DISP PLL Config is DONE .......... - CortxA8: Output: **** AMIC110 BoosterPack ALL ADPLL Config for 25 MHz OPP == OPP100 25MHz is Done ......... - CortxA8: Output: **** AMIC110 DDR3 EMIF and PHY configuration is in progress... - CortxA8: Output: EMIF PRCM is in progress ....... - CortxA8: Output: EMIF PRCM Done - CortxA8: Output: DDR PHY Configuration in progress - CortxA8: Output: Waiting for VTP Ready ....... - CortxA8: Output: VTP is Ready! - CortxA8: Output: DDR PHY CMD0 Register configuration is in progress ....... - CortxA8: Output: DDR PHY CMD1 Register configuration is in progress ....... - CortxA8: Output: DDR PHY CMD2 Register configuration is in progress ....... - CortxA8: Output: DDR PHY DATA0 Register configuration is in progress ....... - CortxA8: Output: DDR PHY DATA1 Register configuration is in progress ....... - CortxA8: Output: Setting IO control registers....... - CortxA8: Output: EMIF Timing register configuration is in progress ....... - CortxA8: Output: EMIF Timing register configuration is done ....... - CortxA8: Output: PHY is READY!! - CortxA8: Output: DDR PHY Configuration done - CortxA8: GEL Output: Turning on EDMA... - CortxA8: GEL Output: EDMA is turned on... - CortxA8: Output: **** AMIC110_ICE Initialization is Done ****************** - -Running Board Diagnostics ---------------------------- - -The Processor SDK RTOS Diagnostic package is designed to be a set of -baremetal tests to run on a given board to provide data path continuity -testing on peripherals. - -To run diagnostics on the AMIC110 ICE, follow the procedure given in the -`RTOS Software Developer -Guide `__ 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 eb394a1c6..7aa5ee221 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 @@ -20,17 +20,6 @@ SDK. | Ubuntu | | 22.04 (64-bit) | +---------------------------+-------------------------+ - - **RTOS SDK** - - +---------------------------+-------------------------+ - | **Operating System** | | **Version** | - +---------------------------+-------------------------+ - | Windows | | 7 (64-bit) | - +---------------------------+-------------------------+ - | Ubuntu | | 14.04 (64-bit) | - | | | 16.04 (64-bit) | - +---------------------------+-------------------------+ - .. ifconfig:: CONFIG_sdk in ('JACINTO','j7_foundational') - **Linux SDK** @@ -58,49 +47,41 @@ The following platforms and EVMs are supported with Processor SDK. .. ifconfig:: CONFIG_part_family in ('AM335X_family') - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+ - |**Platform** |**EVM** |**Tested |**Document** |**Processor SDK |**Processor SDK |**Processor SDK | - | | |Version** | |Linux** |RT Linux** |RTOS** | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+ - |`AM335x `__ |tmdxevm3358>`__ | |General_Purpose_EVM_HW_User_Guide>`__ | | | | - | +--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+ - | |`AM335x SK | 1.2 |`Hardware User's Guide `__ | |AM335xStarterKitHardwareUsersGuide>`__ | | | | - | +--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+ - | |`BeagleBone Black | B6 |`Hardware User's Guide `__ | |master/BBB_SRM.pdf?raw=true>`__ | | | | - | +--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+ - | |`AM335x ICE | 2.1A |`Hardware User's Guide `__ | |Communication_Engine_%28ICE%29_EVM_HW_ | | | | - | | | |User_Guide>`__ | | | | - | | | |`Hardware Setup with CCS `__ | | | | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+ + +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+ + |**Platform** |**EVM** |**Tested |**Document** |**Processor SDK | + | | |Version** | |Linux** | + +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+ + |`AM335x `__ |tmdxevm3358>`__ | |General_Purpose_EVM_HW_User_Guide>`__ | | + | +--------------------------------------+----------+--------------------------------------------+----------------+ + | |`AM335x SK | 1.2 |`Hardware User's Guide `__ | |AM335xStarterKitHardwareUsersGuide>`__ | | + | +--------------------------------------+----------+--------------------------------------------+----------------+ + | |`BeagleBone Black | B6 |`Hardware User's Guide `__ | |master/BBB_SRM.pdf?raw=true>`__ | | + | +--------------------------------------+----------+--------------------------------------------+----------------+ + | |`BeagleBone Grren Eco | 1.0 |`Hardware User's Guide `__ | | + | |BEAGL-BONE-GRN-ECO>`__ | | | | + +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+ .. ifconfig:: CONFIG_part_family in ('AM437X_family') - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+ - |**Platform** |**EVM** |**Tested |**Document** |**Processor SDK |**Processor SDK |**Processor SDK | - | | |Version** | |Linux** |RT Linux** |RTOS** | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+ - |`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>`__ | | | | | | - +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+----------------+----------------+ + +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+ + |**Platform** |**EVM** |**Tested |**Document** |**Processor SDK | + | | |Version** | |Linux** | + +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+ + |`AM437x `__ |TMDXEVM437X>`__ | |General_Purpose_EVM_HW_User_Guide>`__ | | + | +--------------------------------------+----------+--------------------------------------------+----------------+ + | |`AM437x SK | 1.1A |`Hardware User's Guide `__ | | + | |TMDXSK437X>`__ | | | | + +--------------------------------------+--------------------------------------+----------+--------------------------------------------+----------------+ .. ifconfig:: CONFIG_part_family in ('J7_family') diff --git a/source/files/Bmc_tool_ucd_update_guide_v2.pdf b/source/files/Bmc_tool_ucd_update_guide_v2.pdf deleted file mode 100755 index 6d9b4a919..000000000 Binary files a/source/files/Bmc_tool_ucd_update_guide_v2.pdf and /dev/null differ diff --git a/source/images/ARM_GEL.png b/source/images/ARM_GEL.png deleted file mode 100644 index 7a4ffd688..000000000 Binary files a/source/images/ARM_GEL.png and /dev/null differ diff --git a/source/images/Bmc_ver_screenshot.JPG b/source/images/Bmc_ver_screenshot.JPG deleted file mode 100644 index 92c9bf70a..000000000 Binary files a/source/images/Bmc_ver_screenshot.JPG and /dev/null differ diff --git a/source/images/Connect_A15.png b/source/images/Connect_A15.png deleted file mode 100644 index 5e7bf229f..000000000 Binary files a/source/images/Connect_A15.png and /dev/null differ diff --git a/source/images/DSP_GEL.png b/source/images/DSP_GEL.png deleted file mode 100644 index 24f38132c..000000000 Binary files a/source/images/DSP_GEL.png and /dev/null differ diff --git a/source/images/ICE335924V.png b/source/images/ICE335924V.png deleted file mode 100644 index 8615919ed..000000000 Binary files a/source/images/ICE335924V.png and /dev/null differ diff --git a/source/images/ICE3359TargetConfig.png b/source/images/ICE3359TargetConfig.png deleted file mode 100644 index 8b5ff7e58..000000000 Binary files a/source/images/ICE3359TargetConfig.png and /dev/null differ diff --git a/source/images/ICE3359Test.png b/source/images/ICE3359Test.png deleted file mode 100644 index 257a87b12..000000000 Binary files a/source/images/ICE3359Test.png and /dev/null differ diff --git a/source/images/ICE3359USB.png b/source/images/ICE3359USB.png deleted file mode 100644 index 1f9b29f5e..000000000 Binary files a/source/images/ICE3359USB.png and /dev/null differ diff --git a/source/images/ICEAMIC1105V.PNG b/source/images/ICEAMIC1105V.PNG deleted file mode 100644 index a81c2e410..000000000 Binary files a/source/images/ICEAMIC1105V.PNG and /dev/null differ diff --git a/source/images/ICEAMIC110BottomLayout.PNG b/source/images/ICEAMIC110BottomLayout.PNG deleted file mode 100644 index 90fa0336a..000000000 Binary files a/source/images/ICEAMIC110BottomLayout.PNG and /dev/null differ diff --git a/source/images/ICEAMIC110ETHERNET.PNG b/source/images/ICEAMIC110ETHERNET.PNG deleted file mode 100644 index 7c3117f22..000000000 Binary files a/source/images/ICEAMIC110ETHERNET.PNG and /dev/null differ diff --git a/source/images/ICEAMIC110JTAG.PNG b/source/images/ICEAMIC110JTAG.PNG deleted file mode 100644 index eec180694..000000000 Binary files a/source/images/ICEAMIC110JTAG.PNG and /dev/null differ diff --git a/source/images/ICEAMIC110TTL.PNG b/source/images/ICEAMIC110TTL.PNG deleted file mode 100644 index 6458b685d..000000000 Binary files a/source/images/ICEAMIC110TTL.PNG and /dev/null differ diff --git a/source/images/ICEAMIC110TargetConfig.PNG b/source/images/ICEAMIC110TargetConfig.PNG deleted file mode 100644 index c16061b34..000000000 Binary files a/source/images/ICEAMIC110TargetConfig.PNG and /dev/null differ diff --git a/source/images/ICEAMIC110Test.PNG b/source/images/ICEAMIC110Test.PNG deleted file mode 100644 index 5fe031bbd..000000000 Binary files a/source/images/ICEAMIC110Test.PNG and /dev/null differ diff --git a/source/images/ICEAMIC110TopLayout.PNG b/source/images/ICEAMIC110TopLayout.PNG deleted file mode 100644 index c8c71448d..000000000 Binary files a/source/images/ICEAMIC110TopLayout.PNG and /dev/null differ diff --git a/source/images/ICE_V2_marked.png b/source/images/ICE_V2_marked.png deleted file mode 100644 index 6a359fd80..000000000 Binary files a/source/images/ICE_V2_marked.png and /dev/null differ diff --git a/source/images/K2EVM.jpg b/source/images/K2EVM.jpg deleted file mode 100644 index e014dd3fd..000000000 Binary files a/source/images/K2EVM.jpg and /dev/null differ diff --git a/source/images/K2H_ENET0.jpg b/source/images/K2H_ENET0.jpg deleted file mode 100644 index 2a3953ca9..000000000 Binary files a/source/images/K2H_ENET0.jpg and /dev/null differ diff --git a/source/images/K2H_TargetConfig.png b/source/images/K2H_TargetConfig.png deleted file mode 100644 index 83f85b999..000000000 Binary files a/source/images/K2H_TargetConfig.png and /dev/null differ diff --git a/source/images/LMflashProg_Config.png b/source/images/LMflashProg_Config.png deleted file mode 100644 index 1d4b85433..000000000 Binary files a/source/images/LMflashProg_Config.png and /dev/null differ diff --git a/source/images/Launch_TargetConfig.png b/source/images/Launch_TargetConfig.png deleted file mode 100644 index fd2e207dd..000000000 Binary files a/source/images/Launch_TargetConfig.png and /dev/null differ diff --git a/source/images/New_TargetConfig.png b/source/images/New_TargetConfig.png deleted file mode 100644 index 2c7da82a1..000000000 Binary files a/source/images/New_TargetConfig.png and /dev/null differ diff --git a/source/linux/Foundational_Components/Tools/Pin_Mux_Tools.rst b/source/linux/Foundational_Components/Tools/Pin_Mux_Tools.rst index ddedb0e6b..af259994d 100644 --- a/source/linux/Foundational_Components/Tools/Pin_Mux_Tools.rst +++ b/source/linux/Foundational_Components/Tools/Pin_Mux_Tools.rst @@ -129,26 +129,6 @@ configurations while the MLO file (secondary bootloader) executes from OCMC RAM. This guide will include how to convert the generic format for U-boot. - -.. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family') - - .. rubric:: Processor SDK RTOS - :name: processor-sdk-rtos - - After updating the files in the directories below you will need to - recompile the **board\_lib** and **sbl** components of the Processor SDK - Platform Development Kit (PDK). Follow this guide on `Rebuilding The - PDK `__. - - .. rubric:: AM3, AM4, AMIC - :name: am3-am4-amic - - Replace files in this directory - - ${PDK\_INSTALL\_DIR}\\packages\\ti\\starterware\\board\\${SOC}\\ - 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. - .. rubric:: Processor SDK Linux :name: processor-sdk-linux diff --git a/source/linux/How_to_Guides/Hardware_Setup_with_CCS/EVMK2H_Hardware_Setup.rst b/source/linux/How_to_Guides/Hardware_Setup_with_CCS/EVMK2H_Hardware_Setup.rst deleted file mode 100644 index 7728f0283..000000000 --- a/source/linux/How_to_Guides/Hardware_Setup_with_CCS/EVMK2H_Hardware_Setup.rst +++ /dev/null @@ -1 +0,0 @@ -.. include:: ../../../common/EVM_Hardware_Setup/_EVMK2H_Hardware_Setup.rst diff --git a/source/linux/How_to_Guides/Hardware_Setup_with_CCS/ICE_AM335x_Hardware_Setup.rst b/source/linux/How_to_Guides/Hardware_Setup_with_CCS/ICE_AM335x_Hardware_Setup.rst deleted file mode 100644 index 274bd0511..000000000 --- a/source/linux/How_to_Guides/Hardware_Setup_with_CCS/ICE_AM335x_Hardware_Setup.rst +++ /dev/null @@ -1 +0,0 @@ -.. include:: ../../../common/EVM_Hardware_Setup/_ICE_AM335x_Hardware_Setup.rst diff --git a/source/linux/How_to_Guides/Hardware_Setup_with_CCS/ICE_AMIC110_EVM_Hardware_Setup.rst b/source/linux/How_to_Guides/Hardware_Setup_with_CCS/ICE_AMIC110_EVM_Hardware_Setup.rst deleted file mode 100644 index 8a678e381..000000000 --- a/source/linux/How_to_Guides/Hardware_Setup_with_CCS/ICE_AMIC110_EVM_Hardware_Setup.rst +++ /dev/null @@ -1 +0,0 @@ -.. include:: ../../../common/EVM_Hardware_Setup/_ICE_AMIC110_EVM_Hardware_Setup.rst diff --git a/source/linux/How_to_Guides/Target/How_to_fix_y2k38.rst b/source/linux/How_to_Guides/Target/How_to_fix_y2k38.rst index 67b6bb7d7..37948c912 100644 --- a/source/linux/How_to_Guides/Target/How_to_fix_y2k38.rst +++ b/source/linux/How_to_Guides/Target/How_to_fix_y2k38.rst @@ -21,31 +21,17 @@ and functions, it makes the whole filesystem vulnerable. To understand how the problem was fixed in Scarthgap filesystem, refer: https://static.sched.com/hosted_files/osseu2024/8b/EOSS%20Vienna%202024%20-%20Surviving%20Y2038.pdf -******************************* -Building a Y2K38-friendly Image -******************************* +********************* +Y2K38 Issue Resolved +********************* -In SDK 9.3, TI's 32-bit platforms are still based on Kirkstone filesystem, which is NOT Y2K38-friendly. The Y2K38 issue -is fixed in OE-core Scarthgap, on which the next release will be based. +**The current SDK release is based on Scarthgap filesystem, which has the Y2K38 issue fixed.** -Until then, if a Y2K38-friendly filesystem is required, obtain a :file:`tisdk-thinlinux-image` from the latest -`cicd.scarthgap.x`: - -.. ifconfig:: CONFIG_part_variant in ('AM335X') - - https://software-dl.ti.com/cicd-report/linux/index.html?section=platform&platform=am335x - -.. ifconfig:: CONFIG_part_variant in ('AM437X') - - https://software-dl.ti.com/cicd-report/linux/index.html?section=platform&platform=am437x - -The above images are based on the 6.6 Kernel and Scarthgap filesystem, and thus has the Y2K38 issue fixed. +TI's 32-bit platforms now use OE-core Scarthgap, which includes the necessary updates to data structures and functions +to handle dates beyond 2038. The filesystem images provided in this SDK are Y2K38-compliant out of the box. .. note:: - While the above images are Y2K38-friendly, it must be ensured that even the code introduced to it from other sources - is Y2K38-friendly. Any code that is not Y2K38-friendly will break the Y2K38-compatibility of the filesystem. Thus it - is important to be intentional about writing Y2K38-friendly code, and to test this code to ensure that the final - image remains Y2K38-friendly. - -To build a Y2K38-friendly image on the 6.6 Kernel and Scarthgap filesystem baseline, follow the "Build Instructions" -section present in the above link. + While the SDK images are Y2K38-friendly, it must be ensured that any code introduced from other sources + is also Y2K38-friendly. Any code that is not Y2K38-compliant will break the Y2K38-compatibility of the filesystem. + Thus it is important to be intentional about writing Y2K38-friendly code, and to test this code to ensure that the + final image remains Y2K38-compliant. diff --git a/source/linux/How_to_Guides_Hardware_Setup_with_CCS.rst b/source/linux/How_to_Guides_Hardware_Setup_with_CCS.rst index 49c1a3382..b31d5f715 100644 --- a/source/linux/How_to_Guides_Hardware_Setup_with_CCS.rst +++ b/source/linux/How_to_Guides_Hardware_Setup_with_CCS.rst @@ -10,9 +10,6 @@ Hardware EVM Setup How_to_Guides/Hardware_Setup_with_CCS/TMDX654_EVM_Hardware_Setup How_to_Guides/Hardware_Setup_with_CCS/AM572x_GP_EVM_Hardware_Setup How_to_Guides/Hardware_Setup_with_CCS/TMDXIDK5728_Hardware_Setup - How_to_Guides/Hardware_Setup_with_CCS/EVMK2H_Hardware_Setup - How_to_Guides/Hardware_Setup_with_CCS/ICE_AM335x_Hardware_Setup - How_to_Guides/Hardware_Setup_with_CCS/ICE_AMIC110_EVM_Hardware_Setup How_to_Guides/Hardware_Setup_with_CCS/J721E_EVM_Hardware_Setup How_to_Guides/Hardware_Setup_with_CCS/J7200_EVM_Hardware_Setup How_to_Guides/Hardware_Setup_with_CCS/J721S2_EVM_Hardware_Setup diff --git a/source/linux/Overview/_Processor_SDK_Building_The_SDK.rst b/source/linux/Overview/_Processor_SDK_Building_The_SDK.rst index f680f0312..ffa2ed2f2 100644 --- a/source/linux/Overview/_Processor_SDK_Building_The_SDK.rst +++ b/source/linux/Overview/_Processor_SDK_Building_The_SDK.rst @@ -132,7 +132,7 @@ The MACHINE can be set to |__SDK_BUILD_MACHINE__|, for example. $ . 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', 'AM335X', 'AM437X') 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 @@ -162,6 +162,21 @@ The MACHINE can be set to |__SDK_BUILD_MACHINE__|, for example. $ . conf/setenv $ MACHINE= ARAGO_RT_ENABLE=1 bitbake -k tisdk-default-image + .. ifconfig:: CONFIG_part_variant in ('AM335X', 'AM437X') + + 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. + + .. 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 + .. ifconfig:: CONFIG_part_variant in ('AM62X','AM62PX','AM62LX') * The final command below will build the :file:`tisdk-jailhouse-image`, which is the