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.
Hardware Target | Device Tree File Descriptions | Filename |
phyCORE-AM57xx RDK | Default dts Build Target | am57xx-phycore-rdk.dts |
SOM (superset) - enables all SOM features | am57xx-phycore-common.dtsi | |
SOM (silicon-specific) - adds support and enables silicon-specific features | am571x-phycore-som.dtsi | |
SOM Variant - excludes features not supported by the BOM population options for PCM-057-10203110C | am571x-pcm-057-10203110c.dtsi | |
Carrier Board | am571x-pcm-948.dtsi | |
WiLink8 WiFi Module | am57xx-phytec-wlan-wilink8.dtsi |
Compatible Hardware
Supported Hardware Versions
Compatible Expansion Boards and Accessories
Module Name | Part Number | PCB Version | Description |
---|---|---|---|
7" Display with Capacitive Touch | LCD-018-070-KAP | 1365.1 | EDT ETM0700G0DH6 TTL 7" display with capacitive touch |
Expansion Bus Prototyping Board | PCM-957 | 1351.0 | Expansion Bus Breakout and Prototype Board |
WiFi/Bluetooth Module | PCM-949 | 1418.0 | TI WiLink8 Module |
Camera Module | VM-009-M12 | 1339.0 | ON Semi MT9M131 Module |
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:
There is no content with the specified labels
BSP Features
Interface | Detail | Implemented | Tested | Status in Device tree | Notes |
---|---|---|---|---|---|
UART | uart3 | Yes | Yes | Okay | Connector X18 (default serial console) |
uart4 | Yes | No | Disabled1 | ||
uart5 | Yes | Yes | Okay | Connector X17 | |
uart6 | Yes | No | Disabled1 | ||
uart7 | Yes | No | Disabled1 | ||
uart8 | Yes | No | Disabled1 | ||
uart9 | Yes | No | Disabled1 | ||
uart10 | Yes | No | Disabled1 | ||
I2C | i2c1 | Yes | Yes | Okay | Available on expansion Connector X28 |
i2c2 | Yes | Yes | Okay | Connected to HDMI1_DDC | |
i2c3 | Yes | No | Disabled1 | ||
i2c4 | Yes | Yes | Okay | Used for Audio Codec - available on expansion Connector X28 | |
i2c5 | Yes | No | Disabled1 | ||
Ethernet | cpsw_emac0 (RGMII0 on SoM) | Yes | Yes | Okay | RGMII0 - KSZ9031RNX SoM PHY Connector X7 |
cpsw_emac1 (RGMII1 on CarrierBoard) | Yes | Yes | Okay | RGMII1 - KSZ9031RNX Connector X8 | |
Display and Touch | Analog Touch Control 1 | Yes | Yes | Okay | Capacitive: ETM-FT5x06 (on LCD-018), I2C4 |
Analog Touch Control 2 | No | No | Disabled | Resistive: STMPE811 (on CB), I2C4 | |
PWM Backlight | Yes | Yes | Okay2 | ehrpwm0 (EHRPMW1A on CB) | |
24-bit LCD Interface | Yes | see Known Issues | Okay2 | LVDS Connector X25 requires LCD-018 | |
HDMI | Yes | see Known Issues | Okay | hdmi1_ddc Connector X24 (encoder TPD12S on carrier board) | |
McASP | mcasp1 | Yes | Yes | Okay | |
mcasp2 | Yes | No | Disabled1 | ||
mcasp5 | Yes | No | Disabled1 | ||
mcasp6 | Yes | No | Disabled1 | ||
mcasp7 | Yes | No | Disabled1 | ||
mcasp8 | Yes | No | Disabled1 | ||
eMMC/SD/SDIO | mmc1 | Yes | Yes | Okay | Connector X2 |
mmc2 | Yes | Yes | Okay | eMMC on SOM | |
mmc3 | Yes | Yes | Okay | Connector X26 (WiFi/BT connector) | |
USB | usb1 | Yes | Yes | Okay | USB 3.0 Standard-A Connector X30 (Host only) |
usb2 | Yes | Yes | Okay | USB 2.0 Mini-AB Connector X9 (device default); signals may also be routed to X19 (Standard-A) | |
CAN | can1 | Yes | Yes | Okay | DB9 Connector X6 |
can2 | Yes | Yes | Okay | Pin Header Connector X5 | |
MCSPI | spi1 | Yes | Yes | Okay | Connector X28 (Expansion connector) enabled using spidev on X_SPI1_nCS0 |
spi2 | Yes | No | Disabled1 | ||
spi3 | Yes | No | Disabled1 | ||
spi4 | Yes | No | Disabled1 | ||
QSPI | qspi1 | Yes | see Known Issues | Okay | NOR Serial Flash on SOM |
SATA | sata1 | Yes | Yes | Okay | Connector X11 (SATA) and X12 (power connector) |
PCIe | pcie1 | Yes | Yes | Okay | Connector X27 (PI6C557 4x PCIe connector) |
IPU | ipu1 | Yes | Yes | Okay | |
ipu2 | Yes | Yes | Okay | ||
DSP | dsp1 | Yes | Yes | Okay | |
dsp2 | Yes | Yes | Okay3 | ||
GPIO | User Buttons and LEDs | Yes | Yes | Okay | |
Memory | EEPROM | Yes | Yes | Okay | M24C32 on I2C1 |
NAND (8/16 bit) | Yes | Yes | Okay4 | MT29F8G08ABACAWP connected to GPMC | |
QSPI NOR Flash | Yes | see Known Issues | Okay | N25Q128A connected to QSPI1_CS2 | |
eMMC | Yes | Yes | Okay | mmc2 on SOM | |
RTC | Internal AM57xx | Yes | Yes | Okay | Internal to processor |
PMIC TPS659037 | Yes | Yes | Okay | TPS659037 I2C1 | |
External RTC | Yes | Yes | Okay | RV-4162-C7 on I2C1 | |
Audio | Stereo Codec on CarrierBoard | Yes | Yes | Okay | TLV320AIC3007 codec; connected to McASP1 and I2C4 |
Communication | TiWi-BLE WiFi | No | No | Disabled | Connector X26 |
TiWi-BLE Bluetooth | No | No | Disabled | Connector X26 | |
WiLink8 WiFi | Yes | Yes | Okay | Connector X26 | |
Parallel Camera | VIN3 on i2c3 | Yes | Yes | Okay3 | VM-009 at Connector X23 (phyCAM-P connector) |
Hardware Acceleration | Graphics (PowerVR SGX544) | Yes | Yes | Okay2 |
[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
- The default prebuilt images and Yocto MACHINE target am57xx-phycore-rdk now represents a minimal configuration (PCM-057-10203110C).
- Yocto
- MACHINE: Additional machine targets
- am5716-phycore-rdk
- am571x-pcm-057-10203110c
- am571x-pcm-057-10203111i
- am572x-pcm-057-40a00111i
- MACHINE: Additional machine targets
- 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
- Split am57xx-phycore-som.dtsi (SOM) into common and silicon-specific dtsi files:
- Devicetree:
- 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)
- New defconfig targets
- 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
- Split am57xx-phycore-som.dtsi (SOM) into common and silicon-specific dtsi files:
- General:
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.
- Workaround to build Chromium (for am5728-based SOMs only):
- AM57X6: All MACHINE targets for the AM5726- and AM5716-based SOMs are incompatible with building for the arago-core-tisdk-image image target.
- 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.
- 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.
Texas Instruments Known Issues (Kernel)
Texas Instruments Known Issues (U-Boot)
Technical Support
For further support please visit PHYTEC's Support Portal