Skip to end of metadata
Go to start of metadata

 

Operating SystemLinux
BSP Release Status

RELEASED

Release Date

   

RepositoryPHYTEC Public Repos
BinariesBSP-Yocto-TISDK-AM57xx-PD18.1.0
Source Archive
Release Notes

Click Here




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

Linux Kernel4.9.41 (Based on TI SDK 04.01)
U-boot2017.01 (Based on TI SDK 04.01)
Yocto2.2 (Morty) (Based on TI SDK 04.01)
Host OSTested on 64-bit Ubuntu 16.04 LTS
Qt5.7.1
OpenCL1.1.14
OpenCV3.1
Wayland1.11
Gstreamer1.8.3

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.


Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...
Yocto Machine ConfigKit Part Number

SOM Part Number

(Click Here for description)

ModulesU-Boot defconfigKernel Device Tree File
am572x-phycore-rdk

KPCM-057-L,

KPCM-057-SYS

PCM-057-41300111I

LCD-018-070-KAP

PCM-949

PCM-957

VM-009-M12

am572x_phycore_rdk_defconfig

am572x_phycore_rdk_256M16_x2_defconfig

am572x_phycore_rdk_256M16_x4_defconfig

am572x_phycore_rdk_512M16_x4_defconfig

am572x-phycore-rdk.dtb

am572x-phycore-rdk-41300111i.dtb

am5728-phycore-rdk

KPCM-057-L,

KPCM-057-SYS

PCM-057-10200110I,

PCM-057-40200110C,

PCM-057-41300111I,

PCM-057-50500111I,

LCD-018-070-KAP

PCM-949

PCM-957

VM-009-M12

am572x_phycore_rdk_defconfig

am572x_phycore_rdk_256M16_x2_defconfig

am572x_phycore_rdk_256M16_x4_defconfig

am572x_phycore_rdk_512M16_x4_defconfig

am572x-phycore-rdk.dtb

am572x-phycore-rdk-10200110i.dtb

am572x-phycore-rdk-40200110c.dtb

am572x-phycore-rdk-41300111i.dtb

am572x-phycore-rdk-50500111i.dtb

am5726-phycore-rdkNon-standard Kit

PCM-057-40201111I,

PCM-057-41201111I,

PCM-057-50201111I,

PCM-949

PCM-957

VM-009-M12

am572x_phycore_rdk_defconfig

am572x_phycore_rdk_256M16_x2_defconfig

am572x_phycore_rdk_256M16_x4_defconfig

am572x_phycore_rdk_512M16_x4_defconfig

am572x-phycore-rdk-40201111i.dtb

am572x-phycore-rdk-41201111i.dtb

am572x-phycore-rdk-50201111i.dtb

am572x-pcm-057-10200110iNon-standard Kit

PCM-057-10200110I

LCD-018-070-KAP

PCM-949

PCM-957

VM-009-M12

am572x_phycore_rdk_defconfig

am572x_phycore_rdk_256M16_x2_defconfig

am572x_phycore_rdk_256M16_x4_defconfig

am572x_phycore_rdk_512M16_x4_defconfig

am572x-phycore-rdk-10200110i.dtb

am572x-pcm-057-40200110cNon-standard Kit

PCM-057-40200110C

LCD-018-070-KAP

PCM-949

PCM-957

VM-009-M12

am572x_phycore_rdk_defconfig

am572x_phycore_rdk_256M16_x2_defconfig

am572x_phycore_rdk_256M16_x4_defconfig

am572x_phycore_rdk_512M16_x4_defconfig

am572x-phycore-rdk-40200110c.dtb
am572x-pcm-057-40201111iNon-standard Kit

PCM-057-40201111I

PCM-949

PCM-957

VM-009-M12

am572x_phycore_rdk_defconfig

am572x_phycore_rdk_256M16_x2_defconfig

am572x_phycore_rdk_256M16_x4_defconfig

am572x_phycore_rdk_512M16_x4_defconfig

am572x-phycore-rdk-40201111i.dtb
am572x-pcm-057-41201111iNon-standard Kit

PCM-057-41201111I

PCM-949

PCM-957

VM-009-M12

am572x_phycore_rdk_defconfig

am572x_phycore_rdk_256M16_x2_defconfig

am572x_phycore_rdk_256M16_x4_defconfig

am572x_phycore_rdk_512M16_x4_defconfig

am572x-phycore-rdk-41201111i.dtb
am572x-pcm-057-41300111iNon-standard Kit

PCM-057-41300111I

LCD-018-070-KAP

PCM-949

PCM-957

VM-009-M12

am572x_phycore_rdk_defconfig

am572x_phycore_rdk_256M16_x2_defconfig

am572x_phycore_rdk_256M16_x4_defconfig

am572x_phycore_rdk_512M16_x4_defconfig

am572x-phycore-rdk-41300111i.dtb
am572x-pcm-057-50201111iNon-standard KitPCM-057-50201111I

PCM-949

PCM-957

VM-009-M12

am572x_phycore_rdk_defconfig

am572x_phycore_rdk_256M16_x2_defconfig

am572x_phycore_rdk_256M16_x4_defconfig

am572x_phycore_rdk_512M16_x4_defconfig

am572x-phycore-rdk-50201111i.dtb
am572x-pcm-057-50500111iNon-standard KitPCM-057-50500111I

LCD-018-070-KAP

PCM-949

PCM-957

VM-009-M12

am572x_phycore_rdk_defconfig

am572x_phycore_rdk_256M16_x2_defconfig

am572x_phycore_rdk_256M16_x4_defconfig

am572x_phycore_rdk_512M16_x4_defconfig

am572x-phycore-rdk-50500111i.dtb




Linux Device Tree Summary

Hardware TargetDevice Tree File DescriptionsFilename
phyCORE-AM572x RDKDefault dts Build Targetam572x-phycore-rdk.dts






SOM (superset) - enables all SOM featuresam572x-phycore-som.dtsi
SOM Variant - excludes features not supported by the BOM population options for PCM-057-41300111Iam572x-pcm-057-41300111i.dtsi
Carrier Boardam572x-pcm-948.dtsi
LCD-018 display - 7" display with capacitive toucham57xx-phytec-lcd-018.dtsi
WiLink8 WiFi Moduleam57xx-phytec-wlan-wilink8.dtsi
VM-009 Camera Moduleam57xx-phytec-vm-0xx.dtsi

Compatible Hardware

Supported Hardware Versions

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...
Hardware DescriptionPart Number

Configuration Details

(DDR3 / DDR ECC / eMMC or NAND / QSPI NOR / Controller / EEPROM / Ethernet PHY / RTC / Temp)

PCB Version
phyCORE-AM572x SOM





PCM-057-10200110I.A01GB (1 bank) / No / 4GB eMMC / No / AM5728 / Yes / Yes / No / Industrial1428.3
PCM-057-40200110C.A02GB (2 banks) / No / 4GB eMMC / No / AM5728 / Yes / Yes / No / Commercial1428.3
PCM-057-41300111I.A12GB (2 banks) / Yes / 8GB eMMC / No / AM5728 / Yes / Yes / Yes / Industrial1428.3

PCM-057-41300111I.A2

2GB (2 banks) / Yes / 8GB eMMC / No / AM5728 / Yes / Yes / Yes / Industrial1428.3
PCM-057-41201111I.A12GB (2 banks) / Yes / 4GB eMMC / No / AM5726 / Yes / Yes / Yes / Industrial

1428.3

PCM-057-40201111I.A02GB (2 banks) / No / 4GB eMMC / No / AM5726 / Yes / Yes / Yes / Industrial1428.3
PCM-057-50201111I.A04GB (2 banks) / No / 4GB eMMC / No / AM5726 / Yes / Yes / Yes / Industrial1428.3
PCM-057-50500111I.A04GB (2 banks) / No / 32GB eMMC / No / AM5728 / Yes / Yes / Yes / Industrial1428.3
phyCORE-AM572x Carrier Board

PCM-948.A3


1435.2

PCM-948.A4
1435.2

Compatible Expansion Boards and Accessories

Module NamePart NumberPCB VersionDescription
7" Display with Capacitive Touch

LCD-018-070-KAP


1365.1EDT ETM0700G0DH6 TTL 7" display with capacitive touch
Expansion Bus Prototyping BoardPCM-9571351.0

Expansion Bus Breakout and Prototype Board


WiFi/Bluetooth ModulePCM-9491418.0

TI WiLink8 Module

Camera ModuleVM-009-M121339.0ON Semi MT9M131 Module


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


InterfaceDetail

Implemented

TestedStatus in Device tree

Notes

UART






uart3YesYesOkayConnector X18 (default serial console)
uart4YesNoDisabled1
uart5YesYesOkayConnector X17
uart6YesNoDisabled1
uart7YesNoDisabled1
uart8YesNoDisabled1
uart9YesNoDisabled1
uart10YesNoDisabled1
I2C



i2c1YesYesOkayAvailable on expansion Connector X28
i2c2YesYesOkayConnected to HDMI1_DDC
i2c3YesNoDisabled1
i2c4YesYesOkayUsed for Audio Codec - available on expansion Connector X28
i2c5YesNoDisabled1
Ethernetcpsw_emac0 (RGMII0 on SoM)YesYesOkay

RGMII0 - KSZ9031RNX SoM PHY

Connector X7

cpsw_emac1 (RGMII1 on CarrierBoard)YesYesOkay

RGMII1 - KSZ9031RNX Connector X8

Display and TouchAnalog Touch Control 1YesYesOkayCapacitive: ETM-FT5x06 (on LCD-018), I2C4
Analog Touch Control 2NoNoDisabledResistive: STMPE811 (on CB), I2C4
PWM BacklightYesYesOkayehrpwm0 (EHRPMW1A on CB)
24-bit LCD InterfaceYessee Known IssuesOkay

LVDS Connector X25

requires LCD-018

HDMIYessee Known IssuesOkay

hdmi1_ddc

Connector X24 (encoder TPD12S on carrier board)

McASP




mcasp1YesYesOkay
mcasp2YesNoDisabled1
mcasp5YesNoDisabled1
mcasp6YesNoDisabled1
mcasp7YesNoDisabled1
mcasp8YesNoDisabled1
eMMC/SD/SDIO

mmc1YesYesOkayConnector X2
mmc2YesYesOkayeMMC on SOM
mmc3YesYesOkayConnector X26 (WiFi/BT connector)
USBusb1YesYesOkayUSB 3.0 Standard-A Connector X30 (Host only)
usb2YesYesOkayUSB 2.0 Mini-AB Connector X9 (device default); signals may also be routed to X19 (Standard-A)
CANcan1YesYesOkayDB9 Connector X6
can2YesYesOkayPin Header Connector X5
MCSPI


spi1YesYesOkayConnector X28 (Expansion connector) enabled using spidev on X_SPI1_nCS0
spi2YesNoDisabled1
spi3YesNoDisabled1
spi4YesNoDisabled1
QSPIqspi1Yessee Known IssuesOkayNOR Serial Flash on SOM
SATAsata1YesYesOkayConnector X11 (SATA) and X12 (power connector)
PCIepcie1YesYesOkayConnector X27 (PI6C557 4x PCIe connector)
IPUipu1YesYesOkay
ipu2YesYesOkay
DSPdsp1YesYesOkay
dsp2YesYesOkay
GPIO

User Buttons and LEDs

YesYesOkay
MemoryEEPROMYesYesOkayM24C32 on I2C1
NAND (8/16 bit)YesNoDisabledNo NAND populated
QSPI NOR FlashYessee Known IssuesOkayN25Q128A connected to QSPI1_CS2
eMMCYesYesOkaymmc2 on SOM
RTCInternal AM57xxYesYesOkayInternal to processor
PMIC TPS659037 YesYesOkayTPS659037 I2C1
External RTCYesYesOkayRV-4162-C7 on I2C1
Audio

Stereo Codec on CarrierBoard

YesYesOkayTLV320AIC3007 codec; connected to McASP1 and I2C4
CommunicationTiWi-BLE WiFiNoNoDisabledConnector X26
TiWi-BLE BluetoothNoNoDisabledConnector X26
WiLink8 WiFiYesYesOkayConnector X26
Parallel CameraVIN3 on i2c3YesYesOkayVM-009 at Connector X23 (phyCAM-P connector)
Hardware AccelerationGraphics (PowerVR SGX544)YesYesOkay

[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