Skip to end of metadata
Go to start of metadata

Operating SystemLinux
BSP Release Status

RELEASED

Release Date

    

RepositoryPHYTEC Public Repos
BinariesBSP-Yocto-FSL-iMX7-PD17.2.1
Source Archive
Release Notes

Click Here


Introduction


This BSP provides a basis for development, deployment and execution of Linux based applications on the iMX7 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.1.15 (Based on NXP Release L4.1.15-2.0.1_ga)
U-Boot2016.03 (Based on NXP Release L4.1.15-2.0.1_ga)
Yocto2.1.1 Krogoth(Based on NXP Release L4.1.15-2.0.1_ga )
QtNot Supported (Click Here for more info)
Host OSTested on 64-bit Ubuntu 14.04 LTS


Yocto Machine Configuration Table

This BSP release supports various configurations of the phyBOARD-Zeta i.MX7. You will need to know which Yocto machine configuration corresponds to your kit in order to build the appropriate BSP. By default, only the standard kit configurations are shown in the table. If you have a different kit, use the filters below to search by Kit Part Number or SOM. The U-Boot defconfig and kernel device tree file names are important when creating custom U-Boot and kernel images outside of Yocto development.

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
imx7d-phyboard-zeta-001

PB-01910-001

(i.MX7Dual Kit)

PCM-061-2110111C

PEB-EVAL-02

PEB-WLBT-03

PEB-AV-02

mx7d_pcm061_21x_config

imx7d-phyboard-zeta-001.dtb
imx7s-phyboard-zeta-002

PB-01910-002

(i.MX7Solo Kit)

PCM-061-0502100E

PEB-EVAL-02

PEB-WLBT-03

mx7s_pcm061_05x_config

imx7s-phyboard-zeta-002.dtb
imx7d-pcm-061-2111101eNon-Standard Kit

PCM-061-2111101E

PEB-EVAL-02

PEB-WLBT-03

PEB-AV-02

mx7d_pcm061_21x_configimx7d-pcm-061-2111101e.dtb
imx7d-pcm-061-2111111eNon-Standard Kit

PCM-061-2111111E

PEB-EVAL-02

PEB-WLBT-03

PEB-AV-02

mx7d_pcm061_21x_config

imx7d-pcm-061-2111111e.dtb

imx7d-pcm-061-2211101eNon-Standard Kit

PCM-061-2211101E

PEB-EVAL-02

PEB-WLBT-03

PEB-AV-02

mx7d_pcm061_21x_configimx7d-pcm-061-2211101e.dtb



Linux Device Tree Summary

The following is an example describing the structure of the device tree for the standard phyBOARD-Zeta Kit (machine configuration imx7d-phyboard-zeta-001).

Please look at the dts file corresponding to your machine configuration for the included dtsi files.

Hardware TargetDevice Tree File DescriptionsFilename
i.MX7D phyBOARD-Zeta (PB-01910-001)Default dts build targetimx7d-phyboard-zeta-001.dts

SOM (Superset) - enables all SOM features.

imx7-phycore-som.dtsi

SOM Variant- excludes features that are not supported by the BOM population options for PCM-061-2110111C. imx7d-pcm-061-2110111c.dtsi
Carrier Boardimx7-pba-c-09.dtsi
LCD Display Adapterimx7-peb-av-02.dtsi
Evaluation Boardimx7-peb-eval-02.dtsi
WiFi/Bluetooth Moduleimx7-peb-wlbt-03.dtsi


Alternate dts  imx7d-phyboard-zeta-001-m4.dtbconfigure u-boot to use this DTS if running Linux on the Cortex-A7 while running FreeRTOS on the Cortex-M4

Compatible Hardware

Supported Hardware Versions

Hardware DescriptionPart Number

Configuration Details

(i.MX7 / DDR3 / eMMC or NAND / Ethernet PHY populated)

PCB Version
phyCORE-i.MX7 SOM

PCM-061.A4


Dual / 1GB / 4GB eMMC / Yes

1458.2



PCM-061-2110111C.A0

PCM-061-2110111C.A1

PCM-061-0502100E.A0 Solo / 256MB / 256MB NAND / No
PCM-061-2111101E.A0Dual / 1GB / 4GB eMMC / No
PCM-061-2211101E.A0Dual / 1GB / 8GB eMMC / No
PCM-061-2111111E.A0Dual / 1GB / 4GB eMMC / Yes
phyBOARD-Zeta Carrier Board

PBA-C-09.A4


1459.2

PBA-C-09.A5
1459.3

Device tree changes are required to support earlier SOM and Carrier Board revisions. Visit the PHYTEC Support Portal to open a support ticket for help on how to make the device tree changes.

Compatible Expansion Boards and Accessories

Module NamePart NumberPCB VersionDescription
LCD Display Adapter with 7'' capacitive display

PEB-AV-02-070W.A0

(Includes AV module, display, and cable)

1415.1ETM0700G0DH6 LCD Display/ Capacitive touch interface
Evaluation BoardPEB-EVAL-021460.0

Connects to expansion header and provides:

UART1, UART2, JTAG, I2C EEPROM, three user buttons, three user LEDs

WiFi/Bluetooth ModulePEB-WLBT-03-CA.A11478.1

LAIRD Sterling-LWB module, connects to phyBOARD expansion header

BSP Download


Prebuilt images of BSP-Yocto-FSL-iMX7-PD17.2.1 can be downloaded and extracted from the link below:

BSP-Yocto-FSL-iMX7-PD17.2.1

Quickstart


Quickstarts for BSP-Yocto-FSL-iMX7-PD17.2.1:

BSP Yocto FSL i.MX7 PD17.2.1 Quickstart

BSP Features


The following table lists the interfaces available from the phyCORE-iMX7 SOM. 

  • Implemented - driver support exists in the kernel. 
  • Tested  - the interface has been configured in the device tree and was tested by PHYTEC 
  • Enabled in DTS - the corresponding device tree nodes are enabled in the device tree. See Linux Device Tree Summary for more information.

    The "Enabled in DTS" column is specifically for the standard phyBOARD-Zeta kit (machine configuration imx7d-phyboard-zeta-001).

    Please look at the dts file corresponding to your machine configuration for differences.

InterfaceDetailImplementedTestedEnabled in DTSNotes
UARTuart1YesYesYesDB9 connector on PEB-EVAL-02
uart2YesYesYesDB9 connector on PEB-EVAL-02
uart3YesNo[click for info] expansion header
uart4YesNo[click for info]   
uart5YesYesYesRS232 default serial console at Connector X2
uart6YesNo[click for info]  expansion header
uart7YesYesYesexpansion header - Configured for BT on PEB-WLBT-03
I2Ci2c1YesYesYesexpansion header
i2c2YesYesYesAV Connector X4
i2c3YesNo[click for info]  
i2c4YesYesYesexpansion header
EthernetRGMII1YesYesYesKSZ9031RNX PHY on SOM, Connector X8
RGMII2YesYesYesKSZ9031RNX PHY on CarrierBoard, Connector X7
SAIsai1YesNo
Audio/Video Connector X4
sai2YesNo[click for info]  expansion header
sai3YesNo[click for info]  
MMC/SDIOSD1YesYesYesmicroSD slot connector X11
SD2YesNo[click for info]  expansion header
SD3YesYesYessignals routed to eMMC.
CommunicationMultiCore Communication with Cortex-M4 (RPMsg)YesYesYesSee FreeRTOS release for more info.
Laird Sterling LWB BluetoothYesYesYeson PEB-WLBT-03
Laird Sterling LWB WiFiYesYesYeson PEB-WLBT-03
USBusb1YesYesYesUSB-A Host Connector X9
usb2YesYesYesUSB-AB OTG Connector X10
usbh (HSIC)YesYesNoexpansion header
CANcan1YesYesYesHeader X1
can2YesNo[click for info]  
SPIspi1YesNo[click for info]  expansion header
spi2YesNo[click for info]  expansion header
spi3YesNo[click for info]   expansion header
spi4YesNo[click for info]  
ADCadc1YesYesYesexpansion header
Display and TouchLCD DisplayYesYesYesvia expansion board PEB-AV-02
Analog LCD TouchYesYesYes

Capacitive ETM-FT5x06

via expansion board PEB-AV-02

HDMINoNo

via expansion board PEB-AV-01

BacklightYesYesYes

PWM via pwm4

via expansion board PEB-AV-02

GPIO

User Buttons and LEDs

YesYesYes

User LED GPIO2_10 on CarrierBoard

Three user LEDs and three buttons on PEB-EVAL-02 

Memory

 
8/16-bit NAND Flash (GPMC)YesYesNoMT29F4G08 - not populated in default SOM configuration
SPI NOR FlashYesYesYesN25Q128A on QSPI_A
EEPROM on SOMYesYesYesM24C32 on i2c1
EEPROM on eval boardYesYesYesCAT24C32 on i2c4 PEB-EVAL-02 
eMMCYesYesYes

On SD3

PCM-061.A0 -.A4 SOMs: MTFC4GMDEA-4M

PCM-061-2110111C.A1: MTFC4GACAJCN-4M IT

RTCInternal i.MX7YesYesYesSNVS RTC
External RTCYesYesYesRV-4162-C7 on I2C1
Power ManagementPMICYesYesYesPF3000 on I2C1
JTAGJTAG


ARM JTAG 20 connector on PEB-EVAL-02
PCIemini-pcieYesYesYesconnector X12

[1] Interface requires additional configuration, such as pinmuxing. 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. Please see NXP's i.MX7D Technical Reference Manual for more information on the various modes each pin can be muxed to.

Fixed In This Release


  • Kit imx7s-phyboard-zeta-002: 

    • Communication with Cortex-M4: Linux failed to boot when RPMsg is enabled, the RPMSG driver hardcoded the location in memory used for RPMSG to be at the end of 1GB. 

  • Linux:
    • Optimized I2C and CAN1 drive strength

New In This Release


  • Linux
    • PCIe: switch to using internal reference clk for PCIe PHY instead of external oscillator.
      • Reason: NXP initially recommended an external oscillator be used but has since validated that the internal reference clock meets PCIe requirements.
  • Meta-phytec-extra:
    • New meta layer with machine configurations to support non-kit SOM variants:
      • PCM-061-2111101E
      • PCM-061-2111111E
      • PCM-061-2211101E

Not Tested


  • Booting via network
  • Qt5 - NXP includes "fsl-image-qt5" Yocto Image in the BSP but it is meant for i.MX SoCs with hardware graphics, and is not supported by NXP or PHYTEC for the i.MX7D.

Known Issues


PHYTEC Known Issues

  • Ethernet:
    • iperf3 is included with the Krogoth Yocto BSP. With UDP, this command reports much lower bandwidth than expected when compared with iperf command.
  • eMMC:

    • Flashing with U-Boot: 
      • fsl-image-gui-imx7d-phyboard-zeta.sdcard image is too large to be loaded into memory (1GB) from u-boot.
      • Workaround: Partition and flash eMMC from Linux instead. See Quickstart for instructions.
  • Linux IMX Busfreq driver:
    • Driver disabled by default due to impaired UART console functionality when the system is idle (Low frequency setpoint).
    • For dynamic bus frequency scaling and improved power consumption, the busfreq driver can be enabled in the device tree by removing the "fsl,freq_scaling_disabled" property in imx7-phycore-som.dtsi. It can also be controlled in Linux sysfs: 

      echo 1 > /sys/bus/platform/drivers/imx_busfreq/soc\:busfreq/enable 
  • 256MB NAND is too small to flash fsl-image-gui filesystem. Booting from NAND was tested with core-image-minimal Yocto image, which is included with release binaries.
  • Yocto kernel-module-laird-backports fetch error: LSR has released a new version of the package being fetched in this recipe, and replaced the tarball on their website with the same name. This is resulting in a checksum mismatch.
    • Workaround: See Quickstart section "Yocto Build Steps".

NXP Known Issues

See i.MX Linux Release Notes from NXP in  L4.1.15_2.0.0_LINUX_DOCS


Technical Support


For further information or to report any problems, visit the PHYTEC Support Portal