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-AM572x 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

Compatible Hardware

Supported Hardware Versions

Compatible Expansion Boards and Accessories

BSP Download 

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

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

Quickstart

Quickstarts for BSP-Yocto-TISDK-AM57xx-PD18.1.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. 

New In This Release

• General
  • Support for additional SOM Variants:
    • PCM-057-10200110I.A0
    • PCM-057-40200110C.A0
• Yocto
  • SDK: Ported to TI's Processor SDK v04.01
  • MACHINE: Additional machine targets for specific SOM configurations
    • am572x-pcm-057-10200110i
    • am572x-pcm-057-40200110c
    • am572x-pcm-057-40201111i
    • am572x-pcm-057-41201111i
    • am572x-pcm-057-41300111i
    • am572x-pcm-057-50201111i
    • am572x-pcm-057-50500111i
• Kernel
  • Version: Migrated from Linux Kernel v4.4.32 to v4.9.41
  • Devicetree: Support for additional SOMs and dtb targets for them in conjunction the phyCORE-AM572x carrier board (PCM-948)
    • am572x-pcm-057-10200110i.dtsi → am572x-phycore-rdk-10200110i.dtb
    • am572x-pcm-057-40200110c.dtsi → am572x-phycore-rdk-40200110c.dtb
• U-Boot
  • Version: Migrated from U-Boot v2016.05 to v2017.01
  • DDR: Support for 1 GiB (2x MT41K256M16HA-125) configurations
    • Additional CONFIG_PCM_057_256M16_x2_DDR to build for 1 GiB configurations
  • Build:
    • New defconfig option that includes the CONFIG_PCM_057_256M16_x2_DDR option by default
      
      • am572x_phycore_rdk_256M16_x2_defconfig: PCM-057-1xxxxxxxx SOM variants (1GiB)
    • Moving towards a driver model for u-boot akin to Linux, and utilizing more dts nodes for configuration to enable and control interfaces. This began with PD17.1.0 and the infrastructure will continue to evolve as both TI and u-boot move fully towards this model.
  • Devicetree:
    • New method for detecting the proper board configuration based on an EEPROM-based kit option string, and an option to override this if wanted, or necessary (e.g. the EEPROM is either not populated or does not contain the appropriate information).
      • See [application note coming soon]
    • FIT: Support for additional SOMs and dtb targets for them in conjunction the phyCORE-AM572x carrier board (PCM-948)
      • am572x-pcm-057-10200110i.dtsi → am572x-phycore-rdk-10200110i.dtb
      • am572x-pcm-057-40200110c.dtsi → am572x-phycore-rdk-40200110c.dtb

Fixed In This Release

• Yocto
  • Package ccs6 fetch fails due to TI export approval requirement. ccs6 is no longer included in the TISDK build by default and can be downloaded and utilized separately.
  • -dirty is no longer appended when u-boot or kernel sources are built with uncommitted changes due to the addition of additional version information.
  • Gstreamer encoding pipelines fail. New multimedia firmware for both the IPUs and DSPs, along with additional support for the codec-engine and libdce, have been added for the appropriate phyCORE-AM57x build targets.
• Kernel
  • ETH1 fails to transfer large files (200MB)
  • MCASP2_AXR0_OUT IOdelay configuration targeting wrong CFG register

Known Issues

• Yocto
  • AM5726: All MACHINE targets for the AM5726-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.
• 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/.
    • Workaround: write the proper information to the EEPROM or set the override_board u-boot environment variable. See [application note coming soon]

Texas Instruments Known Issues (Kernel)

Texas Instruments Known Issues (U-Boot)

Technical Support

For further support please visit PHYTEC's Support Portal