blob: 15a1549e564c70b684b84d7a8cb279a0991c24e7 [file] [log] [blame]
York Suna84cd722014-06-23 15:15:54 -07001#
2# Copyright 2014 Freescale Semiconductor
3#
4# SPDX-License-Identifier: GPL-2.0+
5#
6
7Freescale LayerScape with Chassis Generation 3
8
9This architecture supports Freescale ARMv8 SoCs with Chassis generation 3,
York Sun7b08d212014-06-23 15:15:56 -070010for example LS2085A.
Bhupesh Sharmac08d3562015-03-19 09:20:44 -070011
12Flash Layout
13============
York Sun03017032015-03-20 19:28:23 -070014
15(1) A typical layout of various images (including Linux and other firmware images)
16 is shown below considering a 32MB NOR flash device present on most
17 pre-silicon platforms (simulator and emulator):
Bhupesh Sharmac08d3562015-03-19 09:20:44 -070018
19 -------------------------
York Sun03017032015-03-20 19:28:23 -070020 | FIT Image |
21 | (linux + DTB + RFS) |
Bhupesh Sharmac08d3562015-03-19 09:20:44 -070022 ------------------------- ----> 0x0120_0000
York Sun03017032015-03-20 19:28:23 -070023 | Debug Server FW |
Bhupesh Sharmac08d3562015-03-19 09:20:44 -070024 ------------------------- ----> 0x00C0_0000
York Sun03017032015-03-20 19:28:23 -070025 | AIOP FW |
Bhupesh Sharmac08d3562015-03-19 09:20:44 -070026 ------------------------- ----> 0x0070_0000
27 | MC FW |
28 ------------------------- ----> 0x006C_0000
York Sun03017032015-03-20 19:28:23 -070029 | MC DPL Blob |
Bhupesh Sharmac08d3562015-03-19 09:20:44 -070030 ------------------------- ----> 0x0020_0000
York Sun03017032015-03-20 19:28:23 -070031 | BootLoader + Env|
Bhupesh Sharmac08d3562015-03-19 09:20:44 -070032 ------------------------- ----> 0x0000_1000
33 | PBI |
34 ------------------------- ----> 0x0000_0080
35 | RCW |
36 ------------------------- ----> 0x0000_0000
37
York Sun03017032015-03-20 19:28:23 -070038 32-MB NOR flash layout for pre-silicon platforms (simulator and emulator)
39
40(2) A typical layout of various images (including Linux and other firmware images)
York Sune12abcb2015-03-20 19:28:24 -070041 is shown below considering a 128MB NOR flash device present on QDS and RDB
York Sun03017032015-03-20 19:28:23 -070042 boards:
43 ----------------------------------------- ----> 0x5_8800_0000 ---
44 | .. Unused .. (7M) | |
45 ----------------------------------------- ----> 0x5_8790_0000 |
46 | FIT Image (linux + DTB + RFS) (40M) | |
47 ----------------------------------------- ----> 0x5_8510_0000 |
48 | PHY firmware (2M) | |
49 ----------------------------------------- ----> 0x5_84F0_0000 | 64K
50 | Debug Server FW (2M) | | Alt
51 ----------------------------------------- ----> 0x5_84D0_0000 | Bank
52 | AIOP FW (4M) | |
53 ----------------------------------------- ----> 0x5_8490_0000 (vbank4)
54 | MC DPC Blob (1M) | |
55 ----------------------------------------- ----> 0x5_8480_0000 |
56 | MC DPL Blob (1M) | |
57 ----------------------------------------- ----> 0x5_8470_0000 |
58 | MC FW (4M) | |
59 ----------------------------------------- ----> 0x5_8430_0000 |
60 | BootLoader Environment (1M) | |
61 ----------------------------------------- ----> 0x5_8420_0000 |
62 | BootLoader (1M) | |
63 ----------------------------------------- ----> 0x5_8410_0000 |
64 | RCW and PBI (1M) | |
65 ----------------------------------------- ----> 0x5_8400_0000 ---
66 | .. Unused .. (7M) | |
67 ----------------------------------------- ----> 0x5_8390_0000 |
68 | FIT Image (linux + DTB + RFS) (40M) | |
69 ----------------------------------------- ----> 0x5_8110_0000 |
70 | PHY firmware (2M) | |
71 ----------------------------------------- ----> 0x5_80F0_0000 | 64K
72 | Debug Server FW (2M) | | Bank
73 ----------------------------------------- ----> 0x5_80D0_0000 |
74 | AIOP FW (4M) | |
75 ----------------------------------------- ----> 0x5_8090_0000 (vbank0)
76 | MC DPC Blob (1M) | |
77 ----------------------------------------- ----> 0x5_8080_0000 |
78 | MC DPL Blob (1M) | |
79 ----------------------------------------- ----> 0x5_8070_0000 |
80 | MC FW (4M) | |
81 ----------------------------------------- ----> 0x5_8030_0000 |
82 | BootLoader Environment (1M) | |
83 ----------------------------------------- ----> 0x5_8020_0000 |
84 | BootLoader (1M) | |
85 ----------------------------------------- ----> 0x5_8010_0000 |
86 | RCW and PBI (1M) | |
87 ----------------------------------------- ----> 0x5_8000_0000 ---
88
York Sune12abcb2015-03-20 19:28:24 -070089 128-MB NOR flash layout for QDS and RDB boards
J. German Riveraf4fed4b2015-03-20 19:28:18 -070090
91Environment Variables
92=====================
93mcboottimeout: MC boot timeout in milliseconds. If this variable is not defined
94 the value CONFIG_SYS_LS_MC_BOOT_TIMEOUT_MS will be assumed.
95
96mcmemsize: MC DRAM block size. If this variable is not defined, the value
97 CONFIG_SYS_LS_MC_DRAM_BLOCK_MIN_SIZE will be assumed.
Scott Wood8e728cd2015-03-24 13:25:02 -070098
99Booting from NAND
100-------------------
101Booting from NAND requires two images, RCW and u-boot-with-spl.bin.
102The difference between NAND boot RCW image and NOR boot image is the PBI
103command sequence. Below is one example for PBI commands for QDS which uses
104NAND device with 2KB/page, block size 128KB.
105
1061) CCSR 4-byte write to 0x00e00404, data=0x00000000
1072) CCSR 4-byte write to 0x00e00400, data=0x1800a000
108The above two commands set bootloc register to 0x00000000_1800a000 where
109the u-boot code will be running in OCRAM.
110
1113) Block Copy: SRC=0x0107, SRC_ADDR=0x00020000, DEST_ADDR=0x1800a000,
112BLOCK_SIZE=0x00014000
113This command copies u-boot image from NAND device into OCRAM. The values need
114to adjust accordingly.
115
116SRC should match the cfg_rcw_src, the reset config pins. It depends
117 on the NAND device. See reference manual for cfg_rcw_src.
118SRC_ADDR is the offset of u-boot-with-spl.bin image in NAND device. In
119 the example above, 128KB. For easy maintenance, we put it at
120 the beginning of next block from RCW.
121DEST_ADDR is fixed at 0x1800a000, matching bootloc set above.
122BLOCK_SIZE is the size to be copied by PBI.
123
124RCW image should be written to the beginning of NAND device. Example of using
125u-boot command
126
127nand write <rcw image in memory> 0 <size of rcw image>
128
129To form the NAND image, build u-boot with NAND config, for example,
130ls2085aqds_nand_defconfig. The image needed is u-boot-with-spl.bin.
131The u-boot image should be written to match SRC_ADDR, in above example 0x20000.
132
133nand write <u-boot image in memory> 200000 <size of u-boot image>
134
135With these two images in NAND device, the board can boot from NAND.