openwrt/target/linux/layerscape
Petr Štetiar 9ba09653ad treewide: remove maintainer variable from targets
There is no such role as target maintainer anymore, one should always
send corresponding changes for the review and anyone from the commiters
is allowed to merge them or eventually use the hand break and NACK them.

Lets make it clear, that it is solely a community doing the maintenance
tasks.

Signed-off-by: Petr Štetiar <ynezz@true.cz>
Acked-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Acked-by: Piotr Dymacz <pepe2k@gmail.com>
2020-03-16 22:21:45 +01:00
..
armv7 layerscape: remove CONFIG_LEGACY_PTY from kernel config 2019-12-09 20:15:02 +01:00
armv8_64b layerscape: ls1012afrdm: introduce dynamic partitioning 2020-03-12 12:59:44 +01:00
base-files layerscape: sysupgrade: require metadata 2020-03-12 12:59:44 +01:00
files/arch/arm64/boot/dts/freescale layerscape: dts: Unify naming of gpio-keys nodes 2019-01-24 15:53:04 +01:00
image kernel: make kmod-i2c-mux selected by dependent modules 2020-03-16 16:26:29 +01:00
patches-4.14 kernel: bump 4.14 to 4.14.171 2020-02-24 14:18:59 +01:00
Makefile treewide: remove maintainer variable from targets 2020-03-16 22:21:45 +01:00
modules.mk
README layerscape: drop armv8_32b support 2019-06-06 15:40:08 +02:00

Layerscape Quick Start

1. Layerscape target support
----------------------------
* ARMv8 64-bit
  LS1012ARDB LS1012AFRWY LS1043ARDB LS1046ARDB LS1088ARDB LS2088ARDB
  (SD card boot support on LS1043ARDB/LS1046ARDB/LS1088ARDB)

* ARMv7
  LS1021ATWR LS1021AIOT
  (SD card boot support on LS1021ATWR/LS1021AIOT)


2. Build
--------
Before configuration and build, update and install package feeds.

$ ./scripts/feeds update -a
$ ./scripts/feeds install -a

* make menuconfig
  Target System:   "NXP Layerscape"
  Subtarget:       (Select subtarget)
  Target Profile:  (Select device, or "Multiple devices")
  Target Devices:  (Select devices. Available when Target Profile is "Multiple devices")
  Target Images:   (Disable "GZip images" if don't want to unzip manually to use the images.)

  Note: The first time make menuconfig would create a .config file which
  would include all dependencies for selected target. After that, make
  menuconfig still could be used to modify packages. If want to change
  other target, please remove .config and make menuconfig to select again.
  Otherwise the packages selected in .config would be a mess.

* make download (or make download -j<n>)

* make (or make -j<n>)

* Final firmware/image
  Path: bin/targets/layerscape/<subtarget>/
  Firmware for flash: openwrt-layerscape-<subtarget>-<device>-<rootfs>-firmware.bin
  Image for SD card: openwrt-layerscape-<subtarget>-<device>-<rootfs>-sdcard.img


3. Program NOR/QSPI flash or SD card
------------------------------------
The firmware.bin or sdcard.img is an all-in-one image including all things for
OpenWrt staring up. (except LS1012AFRWY. Refer to 3.3.)
If you want to install all things into flash, please use firmware.bin.
If you want to install all things into SD card, please use sdcard.img.

3.1 Program sdcard.img to SD card
---------------------------------
sdcard.img could be programmed to SD card in either u-boot environment
or linux environment. After programming, configure the board to boot
from SD card.

* u-boot environment

  => tftp a0000000 <image_name>-sdcard.img
  => mmc write a0000000 0 a0000

  Note: The default sdcard.img size is 320MB. a0000 is the block number for 320MB.
  blk_num = filesize / 512.

* linux environment

  $ dd if=./<image_name>-sdcard.img of=/dev/mmcblkx

  Note: Need to check the SD card device name to replace "mmcblkx".

3.2 Program firmware.bin to flash
---------------------------------
* LS1012ARDB (QSPI flash)
  Start up from bank1, and program firmware to bank2 with below commands.
  Switch to bank2 to start up OpenWrt.

  => tftp a0000000 <firmware_name>-firmware.bin
  => i2c mw 0x24 0x7 0xfc;i2c mw 0x24 0x3 0xf5
  => sf probe 0:0
  => sf erase 0 +$filesize
  => sf write a0000000 0 $filesize
  => reset

* LS1043ARDB (NOR flash)
  Start up from bank0, and program firmware to bank4 with below commands.
  Switch to bank4 to start up OpenWrt.

  => tftp a0000000 <firmware_name>-firmware.bin
  => protect off all
  => erase 64000000 +$filesize
  => cp.b a0000000 64000000 $filesize
  => cpld reset altbank

* LS1046ARDB (QSPI flash)
  Start up from bank1, and program firmware to bank2 with below commands.
  Switch to bank2 to start up OpenWrt.

  => tftp a0000000 <firmware_name>-firmware.bin
  => sf probe 0:1
  => sf erase 0 +$filesize
  => sf write a0000000 0 $filesize
  => cpld reset altbank

* LS1088ARDB (QSPI flash)
  Start up from bank0, and program firmware to bank1 with below commands.
  Switch to bank1 to start up OpenWrt.

  => tftp a0000000 <firmware_name>-firmware.bin
  => sf probe 0:1
  => sf erase 0 +$filesize
  => sf write a0000000 0 $filesize
  => qix altbank

  Note: old version u-boot of ls1088ardb may use below commands to switch to
  bank1 instead of 'qix altbank'.
  => i2c mw 66 50 20;i2c mw 66 10 20;i2c mw 66 10 21

* LS2088ARDB (NOR flash)
  Start up from bank0, and program firmware to bank4 with below commands.
  Switch to bank4 to start up OpenWrt.

  => tftp a0000000 <firmware_name>-firmware.bin
  => protect off all
  => erase 584000000 +$filesize
  => cp.b a0000000 584000000 $filesize
  => qix altbank

3.3 Program LS1012AFRWY
-----------------------
* LS1012AFRWY (QSPI flash + SD card)
  LS1012AFRWY only supports 2MB QSPI flash. We have to put u-boot, and
  some firmwares on QSPI flash, and kernel/dtb/rootfs on SD card.
  So both firmware.bin and sdcard.img are needed for OpenWrt starting up.

  To program sdcard.img, please use linux command described in 3.1 on a
  linux machine.
  To program firmware.bin, start up board from QSPI flash, and program
  firmware with below commands. Reset to start up OpenWrt. (LS1012AFRWY
  supports only one bank.)

  => tftp 96000000 <firmware_name>-firmware.bin
  => sf probe 0:0
  => sf erase 0 +$filesize
  => sf write 96000000 0 $filesize
  => reset


4. Known issues and limitation
------------------------------
* u-boot may fail to read MAC addresses from EEPROM on some boards and there
  won't be MAC addresses set in environment. This may cause kernel fails to
  probe these network interfaces. The workaround is to set MAC addresses
  manually, for example,

  => setenv ethaddr 00:04:9F:04:65:4b
  => setenv eth1addr 00:04:9F:04:65:4c


5. Other references
-------------------
- NXP LSDK site: https://lsdk.github.io/
- OpenWrt documentation: https://openwrt.org/docs/start