In the U-Boot log, the names of the Ethernet interfaces are printed in the format <name>@<interface type>, for example, DPMAC2@xgmii. DPMAC is a DPAA2 object that identifies the physical interface.  For Linux, in TinyDistro as well as in Ubuntu distribution, by default, only one MAC is enabled as a standard Kernel Ethernet Interface. This interface is named eth0 by default (or eth1 if PCI Express network interface card is discovered first). For details regarding creation of a DPAA2 network interface (DPNI) in Linux, refer to LS1088ARDB/LS1088ARDB-PB - How to create a DPAA2 network interface (DPNI) in Linux The table below shows the mapping of Ethernet port names appearing on the chassis front panel with the port names in U-Boot and Linux for LS1088ARDB.  Port name on chassis Port name in U-Boot Port name in Linux (tinyDistro and Ubuntu userland) Description ETH0 DPMAC2@xgmii not enabled by default XFI optical interface ETH1 DPMAC1@xgmii not enabled by default XFI copper interface ETH2 DPMAC7@qsgmii  not enabled by default QSGMII copper interface ETH3 DPMAC8@qsgmii  not enabled by default QSGMII copper interface ETH4 DPMAC9@qsgmii  not enabled by default QSGMII copper interface ETH5 DPMAC10@qsgmii  not enabled by default QSGMII copper interface ETH6 DPMAC3@qsgmii  not enabled by default QSGMII copper interface ETH7 DPMAC4@qsgmii  not enabled by default QSGMII copper interface ETH8 DPMAC5@qsgmii  eth0 by default (or eth1 if PCI Express network interface card is discovered first) QSGMII copper interface ETH9 DPMAC6@qsgmii  not enabled by default QSGMII copper interface The table below shows the mapping of Ethernet port names appearing on the chassis front panel with the port names in U-Boot and Linux for LS1088ARDB-PB. Port name on chassis Port name in U-Boot Port name in Linux (tinyDistro and Ubuntu userland) Description DPMAC1 DPMAC1@xgmii not enabled by default XFI optical interface DPMAC2 DPMAC2@xgmii not enabled by default XFI copper interface DPMAC3 DPMAC3@qsgmii not enabled by default QSGMII copper interface DPMAC4 DPMAC4@qsgmii not enabled by default QSGMII copper interface DPMAC5 DPMAC5@qsgmii eth0 by default (or eth1 if PCI Express network interface card is discovered first) QSGMII copper interface DPMAC6 DPMAC6@qsgmii not enabled by default QSGMII copper interface DPMAC7 DPMAC7@qsgmii not enabled by default QSGMII copper interface DPMAC8 DPMAC8@qsgmii not enabled by default QSGMII copper interface DPMAC9 DPMAC9@qsgmii not enabled by default QSGMII copper interface DPMAC10 DPMAC10@qsgmii not enabled by default QSGMII copper interface

#lx2160a‌ #lx2160a reference design board‌ #edge_devices‌ #edge-node‌

EdgeScale solution provides a secure mechanism for developers to leverage cloud-computing frameworks for their applications, it helps users easily connect IoT things, manage devices and deploy container based applications. Please refer to the following Layerscape products in the cloud computing system. The user could access cloud service from https://portal.edgescale.org. EdgeScale client is a set of software agents running on device side which connects to the cloud services. This document introduces EdgeScale supported major features as registering user account, secure device enrolment, provisioning/connecting the EdgeSacle end devices, generate EdgeScale client images in LSDK, OTA firmware update (LS1043 or LS1046), running EdgeScale demo applications and dynamic deployment of container-based applications.

QorIQ LSDK is NXP new generation of SDK for Layerscape productions, consists of a set of disaggregated components based on Linux distributions, meets market demand to more Linux distributions of more types, and satisfy the requirement from a wide variety of customers. In LSDK we use Flexbuild to build all packages from LSDK, make root filesystem and generate the installer. This document introduces the basic concept of LSDK, comparison between LSDK and Yocto SDK, how to use LSDK, plan and roadmap of LSDK. 1. Basic Concept of LSDK 1.1 LSDK Specific features 1.2 LSDK Components 1.3 LSDK Images Memory Map 2. Comparison Between Layerscape SDK and QorIQ Yocto SDK 3. How to Usage LSDK 3.1 LSDK Flexbuild Utility 3.2 Build LSDK using Flexbuild 3.3 Deploy LSDK Images on the Target Board 3.4 Add a Package using Flexbuild 4. Layerscape SDK Roadmap

LS1012A integrates a hardware packet forwarding engine to provide high performance Ethernet interfaces. This document introduces PFE hardware and software decomposition and data flow, setting up two PFE Ethernet ports to implement Ethernet packets forwarding through PFE, how to modify PFE driver and dts file to set up single PFE Ethernet port on LS1012A custom boards. PFE hardware Structure PFE Software Decomposition and Data Flow Setting up Two PFE Ethernet Ports to Implement Ethernet Packets Forwarding Set up Single PFE Ethernet Port on LS1012A Custom Boards

Recently some customers are porting SDK 2.0 u-boot for LS1021ATWR to their custom boards. They intended to use GPIO lines to turn on/off LEDs for diagnostics and other various purposes. However GPIO driver is not supported in SDK 2.0 u-boot for LS102xa platform. The attached patch is used to add GPIO driver on LS1021ATWR platform based on SDK 2.0 u-boot code. Please use it in SDK 2.0 as the following: $ source ./fsl-setup-env -m ls1021atwr $ bitbake u-boot -c cleansstate $ bitbake u-boot -c patch Go to the folder build_ls1021atwr/tmp/work/ls1021atwr-fsl-linux-gnueabi/u-boot-qoriq/2016.01+fslgit-r0/git, apply the attached patch $ patch -p1<0001-ls1021xa-gpio.patch Go back to build_ls1021atwr folder to rebuild u-boot $ bitbake u-boot

DPDK(Data Plane Development Kit) provides a simple, complete framework for fast packet processing in data plane applications. This IPsec security gateway application demonstrates the implementation of a security gateway using DPDK cryptodev framework with crypto protocol offloading support. This document introduces DPDK IPsec gateway application architecture, DPAA2 SEC driver and ipsec-secgw application implementation for crypto protocol offloading, running ipsec-secgw application on LS2088ARDB.

IEEE Std 1588 standard is for a precision clock synchronization protocol for networked measurement and control, define a Precision Time Protocol (PTP) designed to synchronize real-time clocks in a distributed system. This document introduces IEEE 1588 related basic concept and Precision Time Protocol, hardware assist for 1588 compliant time stamping on QorIQ  LS1021 platform, Linux Kernel PTP framework device driver implementation working with ptpd stack, IEEE 1588 test setup on LS1021ATSN platform and results. IEEE 1588 Introduction and Precision Time Protocol Hardware Assist for 1588 Compliant Time Stamping on QorIQ LS1021 Platform      2.1 Accessing Timer Registers      2.2. Time-Stamping on Ethernet Frame Reception for eTSEC      2.3. Time-Stamping on Ethernet Frame Transmission for eTSEC IEEE 1588 PTP Linux Device Driver and PTPd Application     3.1 IEEE 1588 Linux Software Structure     3.2 IEEE 1588 Linux Device Driver 3.3 PTPd Application Setup IEEE 1588 test on LS1021ATSN Platform    4.1 Build Images with OpenIL    4.2 Setup IEEE 1588 test environment on LS1021ATSN    4.3 Test result

The Layerscape LS1028A industrial applications processor includes a TSN-enabled Ethernet switch and Ethernet controllers to support converged IT and OT networks. Two powerful 64-bit ARM v8 cores support real-time processing for industrial control, as well as virtual machines for edge computing in the IoT. The integrated GPU and LCD controller enable Human Machine Interface (HMI) systems with next-generation interfaces. Integrated Trust Architecture with crytographic offload provide a trusted platform with encrypted communications for secure applications and services. Product Page Reference Design KEY ELEMENTS Dual 64-bit ARM v8 processors for real-time processing Full virtualization support for IoT edge computing TSN-enabled switch for industrial TSN bridge applications TSN-enabled Ethernet controllers for TSN endpoint applications Support Human Machine Interface applications with integrated GPU and LCD controller Trust architecture provides root of trust as a basis for trusted applications and services The LS1028A will be a part of the NXP 15-year product longevity program TARGET APPLICATIONS Factory Automation Process Automation Programmable Logic Controller Motion Controller Industrial IoT gateway Human Machine Interface (HMI)

Getting RCW image: Getting UEFI image:                              Getting PPA image: Getting Linux kernel and DTB, and Root FS images: - Download Image , fsl-ls1043a-uefi-rdb.dtb and fsl-image-core-ls1043ardb.ext2.gz . - Copy Image and fsl-image-core-ls1043ardb.ext2.gz to the TFTP server directory. Getting GRUB2 image for AARCH64 and sample GRUB configuration: - Download grub image from this location. - Download sample grub configuration from here . Placing GRUB image on FAT formatted SD card: Install FAT32 file system on SD card - Use the DISKPART utililty on windows command prompt to format a SD card with FAT32 file system. Use the following snapshot for reference - Copy grubaa64.efi and ls1043a-grub.cfg to the SD card. Booting to UEFI prompt on LS1043a RDB Board: Boot to u-boot prompt from NOR flash bank 0 on LS1043a RDB.  Setup serial port connection on host machine, to capture logs from the target LS1043a RDB board.. Reset the board to boot u-boot on bank 0, assuming that there is a valid u-boot image flashed on the primary bank 0. Copy Images to NOR flash alternate bank using u-boot commands sete uefi 'tftp 80000000 LS1043ARDB_EFI.fd; erase 0x64400000 0x644FFFFF ; cp.b 80000000 0x64400000 $filesize' sete rcw 'tftp 80000000 rcw_uefi_1500.bin; erase 0x64000000 0x640FFFFF ; cp.b 80000000 0x64000000 $filesize' sete ppa 'tftp 80000000 ppa.itb; erase 0x64500000 0x645FFFFF ; cp.b 80000000 0x64500000 $filesize' sete dtb 'tftp 80000000 fsl-ls1043a-uefi-rdb.dtb; erase 0x65B00000 0x65BFFFFF; cp.b 80000000 65B00000 $filesize' run uefi run ppa run rcw run dtb Note: The host machine is assumed to be having tftp server running, with the relevant files in place. The rcw, uefi, dtb and ppa images can also be found at compass link shared above. Note: Make sure SD card is inserted into the SD card slot on the board. Reset RDB to boot from NOR flash bank 4 => cpld reset altbank You should get UEFI boot prompt, as shown in the image below. Enter 2 to load Shell. On the Shell prompt run the following commands Shell> FS0:   Shell> ls You should see a list of the grub executable and configurations files present on SD card. Booting Linux via PXE on LS1043a RDB: Note: atftpd or tftpd-hpa, is required as tftp server for PXE boot to work. tftpd is not supported.  Load grub by entering the name of the grub executable. Shell> grubaa64.efi On the grub prompt, setup the server and client IPs for TFTP transfer. grub> set net_default_server=<server_ip> grub> net_add_addr eno0 efinet0 <client_ip> Load the grub configuration. grub> configfile (hd3,msdos1)/ls1043a-grub.cfg Grub menu is listed. Choose the entry for liinux boot. See the snapshot below for reference. Linux boot should start in around 7-8 minutes. Data transfer speed is around 100 KB/s.

OpenWrt is a highly extensible GNU/Linux distribution for embedded devices (typically wireless routers), OpenWrt is built from the ground up to be a full-featured, easily modifiable operating system for your router. LEDE is based on OpenWrt, targeting a wide range of wireless SOHO routers and non-network device. This document introduces how to porting and running OpenWrt/LEDE on QorIQ LS1012/LS1043 platform. 1. Porting OpenWrt/LEDE Source on QorIQ Layerscape Platforms 2. Deploy OpenWrt/LEDE Images to Boot up the System 3. Verify VLAN Interface and PFE in LEDE System

This document introduces porting TDM Linux driver working in internal loopback mode to do verification during custom boards bringing up and verification stage. 1. TDM Interface Configuration to Support Internal Loopback Mode 2. Modify Linux Kernel Driver to Make TDM Working in Internal Loopback Mode 3. Build TDM Driver into Linux Kernel and do verification on the target board

The integrated flash controller (IFC) is used to interface with external asynchronous/synchronous NAND flash, asynchronous NOR flash, SRAM, generic ASIC memory and EPROM. This document introduces how to configure IFC controller on QorIQ LS, T and P series custom boards, uses LS1043 custom board integrating NAND Flash MT29F64G08CBCBBH1 as an example to demonstrate IFC flash timing parameters calculation and control registers configuration, CodeWarrior initialization file customization and u-boot source code porting. 1. IFC Memory Mapped Registers Introduction 2. Calculate IFC Flash Timing Values and Configure Control Registers 3. Customize CodeWarrior Initialization File with the Calculated IFC Timing 4. Porting U-BOOT Source with the Calculated IFC Timing

This document introduces a method to separate control plane and data plane between GPP(ARM) and AIOP based on different L4 protocols implemented in the AIOP software. So far, in the current MC version, this scenario could not be implemented from WRIOP using DPDMUX, so it is a good choice for users to separate the traffic in AIOP.   1. Basic Concept of DPAA2 Objects   2. AIOP Application to Implement Control in ARM and Data Plane in AIOP   3. Build AIOP Application Project with CodeWarrior   4. Running AIOP Application Program on LS2085ARDB

The u-boot in SDK2.0 has a bug on SGMII2.5 support. Need to add the patch.

This document introduces how to configure RCW to support GPIO on LS1043 platform, how to configure Linux Kernel to load Linux GPIO driver to access GPIO from SYSFS and using loopback method to do verification on the target board. RCW configuration to support GPIO Configure GPIO driver in Linux Kernel Verify GPIO on the target board

This file shows up LS1024A GMAC2 debug, no software support in barebox only workable in kernel. and If using RTL Phy need to add TX_CLK and RX_CLK delay.

This Documentation shows how to make a mass production NAND Flash image for QorIQ IFC NAND flash interface by external NAND Flash programmer.