Introduction

This BSP provides a basis for development, deployment and execution of Linux based applications on the phyCORE-AM57x System on Module (SOM). For detailed information on the various software components included in the release and how to use them, please refer to the Quickstart.

Versioning

Software

Yocto Machine Configuration Table

This BSP releases supports the phyCORE-AM57xx Rapid Development Kit (RDK) and also allows configuration options for different SOMs to be used with the RDK carrier board (PCM-948). By default, only the standard kit configuration will be in the table. If you have a different SOM, use the filters below to search by the SOM part number. The U-Boot defconfig and kernel device tree file names are important when creating custom U-Boot and Linux kernel images outside of Yocto development, or modifying Yocto source for further use.

Linux Device Tree Summary

This is a summary of how the device tree files and the various includes are broken down, using the am57xx-phycore-rdk (minimal configuration) as an example.

Compatible Hardware

Supported Hardware Versions

Compatible Expansion Boards and Accessories

BSP Download 

Prebuilt images of BSP-Yocto-TISDK-AM57xx-PD18.2.0 can be downloaded from the link below:

BSP-Yocto-TISDK-AM57xx-PD18.2.0 Release

Quickstart

Quickstarts for BSP-Yocto-TISDK-AM57xx-PD18.2.0:

BSP Features

[1]  It may be possible to change the software configuration to utilize this interface even if it is not being set in the board's default configuration.
[2] Only enabled on AM5728 silicon variants
[3] Only enabled on AM572x silicon variants
[4] Only enabled with the PCM-057-40A00111I configuration, but would be possible with other PCM-057-xxAxxxxxx variants.

New In This Release

• General
  • The default prebuilt images and Yocto MACHINE target am57xx-phycore-rdk now represents a minimal configuration (PCM-057-10203110C).
    • This enables the same default images to be flashed to every SOM with eMMC, without triggering a hardware issue related to unsupported silicon features.
    • The settings for DDR and the enabled interfaces follow this configuration accordingly, on the first boot (before the EEPROM is written), and if the EEPROM data is invalid.
  • Support for phyCORE-AM57xx with AM5716 Silicon
  • Support for Additional SOM Variants:
    
    • PCM-057-10203111I.A0
    • PCM-057-40A00111I.A0
• Yocto
  
  • MACHINE: Additional machine targets
    
    • am5716-phycore-rdk
    • am571x-pcm-057-10203110c
    • am571x-pcm-057-10203111i
    • am572x-pcm-057-40a00111i
• Kernel
  
  • Devicetree:
    • Split am57xx-phycore-som.dtsi (SOM) into common and silicon-specific dtsi files:
      • am57xx-phycore-common.dtsi
      • am571x-phycore-som.dtsi
      • am572x-phycore-som.dtsi
    • Split am57xx-pcm-948.dtsi (carrier board) into silicon-specific dtsi files:
      • am571x-pcm-948.dtsi
      • am572x-pcm-948.dtsi
    • Added support for additional SOMs and dtb targets for them in conjunction the phyCORE-AM57xx carrier board (PCM-948)
      
      • am571x-pcm-057-10203111i.dtsi → am571x-phycore-rdk-10203111i.dtb
      • am572x-pcm-057-10201111i.dtsi → am572x-phycore-rdk-10201111i.dtb
      • am572x-pcm-057-40a00111i.dtsi → am572x-phycore-rdk-40a00111i.dtb
• U-Boot
  • General:
    • Support for phyCORE-AM57xx with NAND
  • Build:
    • New defconfig targets
      
      • am572x_phycore_rdk_nand_defconfig: PCM-057-40A00111I SOM variant (2GiB DDR with NAND)
      • am571x_phycore_rdk_256M16_x2_defconfig: PCM-057-1xxx3xxxx SOM variants (1GiB DDR with AM5716 silicon)
  • Devicetree:
    • Split am57xx-phycore-som.dtsi (SOM) into common and silicon-specific dtsi files:
      • am57xx-phycore-common.dtsi
      • am571x-phycore-som.dtsi
      • am572x-phycore-som.dtsi
    • Split am57xx-pcm-948.dtsi (carrier board) into silicon-specific dtsi files:
      • am571x-pcm-948.dtsi
      • am572x-pcm-948.dtsi
    • Added support for additional SOMs and dtb targets for them in conjunction the phyCORE-AM57xx carrier board (PCM-948)
      
      • am571x-pcm-057-10203111i.dtsi → am571x-phycore-rdk-10203111i.dtb
      • am572x-pcm-057-10201111i.dtsi → am572x-phycore-rdk-10201111i.dtb
      • am572x-pcm-057-40a00111i.dtsi → am572x-phycore-rdk-40a00111i.dtb

Fixed In This Release

• Kernel
  • cpufreq driver is failing to load
• U-Boot
  • When building for any MACHINE target beside am572x-phycore-rdk, unless the SOM EEPROM is loaded with valid identification information, it will attempt and fail to load the am572x-phycore-rdk.dtb from <rootfs>/boot/.
  • PHYTEC EEPROM board strings are incorrectly returning the first result for a partial match

Known Issues

• Yocto
  • AM57X6: All MACHINE targets for the AM5726- and AM5716-based SOMs are incompatible with building for the arago-core-tisdk-image image target.
    • Workaround: use the phytec-tisdk-image image target instead.
  • Chromium: Although enabled in the TISDK, Chromium has been disabled for all phyCORE-AM572x builds due to the large amount of swap memory required for linking, and the time required to successfully build it.
    • Workaround to build Chromium (for am5728-based SOMs only):
      • Pay close attention to the information provided in the Chromium developer's guide prerequisites section and adjust your system accordingly.
      • Remove the line 'MULTIMEDIA_remove = "chromium-wayland"' from ${YOCTO_DIR}/sources/meta-phytec/conf/machine/include/am572x-phytec.inc before building.
• Kernel
  
  • Display: TI's Matrix-GUI demo only outputs to a single display. If both HDMI and a parallel display are connected, it will display on the parallel display, but the resolution may not be correct–behavior is inconsistent.
    • Workaround: only connect the one display that will be used, or do not use the matrix-gui demo.
  • QSPI: Possible read failures on flash devices with HOLD function (Erratum i916). A software workaround has been implemented to limit QSPI to DIO-SPI mode. The hardware workaround is to disable internal pull-ups and add 10k pull-ups on X_QSPI1_D2 & X_QSPI1_D3
  • PCIe: With cpufreq properly supported again, some PCIe x2 devices are hanging the system during boot.

    • Workaround: prevent frequency changes by disabling the CPUFREQ_DT in the kernel menuconfig, or remove the following code block from the am57xx-phycore-common.dtsi file:

      &cpu0 {
      	vdd-supply = <&smps12_reg>;
      };

      This is a temporary fix and should be resolved with the next release.
      
      

Texas Instruments Known Issues (Kernel)

Texas Instruments Known Issues (U-Boot)

Technical Support

For further support please visit PHYTEC's Support Portal