| Message ID | 1478576399-2362-1-git-send-email-yao.yuan@freescale.com |
|---|---|
| State | Superseded |
| Headers | show |
On 11/08/2016 12:46 PM, York Sun wrote: > On 11/07/2016 07:52 PM, Yuan Yao wrote: > > From: Yuan Yao <yao.yuan@nxp.com> > > > > Signed-off-by: Yuan Yao <yao.yuan@nxp.com> > > --- > > Changed in v2: > > Move the readme for QSPI deploy out of only for ls2080aqds. > > --- > > .../arm/cpu/armv8/fsl-layerscape/doc/README.deploy | 44 > > ++++++++++++++++++++++ > > 1 file changed, 44 insertions(+) > > create mode 100644 > > arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy > > > > diff --git a/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy > > b/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy > > new file mode 100644 > > index 0000000..25813b3 > > --- /dev/null > > +++ b/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy > > @@ -0,0 +1,44 @@ > > +Boot source support Overview > > +------------------- > > + 1. LS1043A > > + LS1043AQDS:QSPI, SD, NOR, NAND > > + LS1043ARDB:SD, NOR, NAND > > + 2. LS2080A > > + LS2080AQDS:QSPI, SD, NOR, NAND > > + LS2080ARDB:NOR, NAND > > + 3. LS1012A > > + LS1012AQDS:QSPI > > + LS1012ARDB:QSPI > > + 4. LS1046A > > + LS1046AQDS:QSPI, SD, NOR, NAND > > + LS1046ARDB:QSPI, SD > > + > > If you plan to add all SD/NAND/QSPI into this document, it is OK to call it > README.deploy. Otherwise it may be better to name as README.qspi. > I'm not be familiar with SD/NAND boot. So should I rename as README.qspi? Or just keep it but waiting for some others to add SD/NAND boot in another patch?
On 11/07/2016 09:44 PM, Yao Yuan wrote: > On 11/08/2016 12:46 PM, York Sun wrote: >> On 11/07/2016 07:52 PM, Yuan Yao wrote: >>> From: Yuan Yao <yao.yuan@nxp.com> >>> >>> Signed-off-by: Yuan Yao <yao.yuan@nxp.com> >>> --- >>> Changed in v2: >>> Move the readme for QSPI deploy out of only for ls2080aqds. >>> --- >>> .../arm/cpu/armv8/fsl-layerscape/doc/README.deploy | 44 >>> ++++++++++++++++++++++ >>> 1 file changed, 44 insertions(+) >>> create mode 100644 >>> arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy >>> >>> diff --git a/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy >>> b/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy >>> new file mode 100644 >>> index 0000000..25813b3 >>> --- /dev/null >>> +++ b/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy >>> @@ -0,0 +1,44 @@ >>> +Boot source support Overview >>> +------------------- >>> + 1. LS1043A >>> + LS1043AQDS:QSPI, SD, NOR, NAND >>> + LS1043ARDB:SD, NOR, NAND >>> + 2. LS2080A >>> + LS2080AQDS:QSPI, SD, NOR, NAND >>> + LS2080ARDB:NOR, NAND >>> + 3. LS1012A >>> + LS1012AQDS:QSPI >>> + LS1012ARDB:QSPI >>> + 4. LS1046A >>> + LS1046AQDS:QSPI, SD, NOR, NAND >>> + LS1046ARDB:QSPI, SD >>> + >> >> If you plan to add all SD/NAND/QSPI into this document, it is OK to call it >> README.deploy. Otherwise it may be better to name as README.qspi. >> > I'm not be familiar with SD/NAND boot. So should I rename as README.qspi? > Or just keep it but waiting for some others to add SD/NAND boot in another patch? > We already have NAND boot explained in other document. Stick with the procedure you are trying to explain. Keep it simple and we can expand it when necessary. York
On 11/09/2016 02:10 AM, York Sun wrote: > On 11/07/2016 09:44 PM, Yao Yuan wrote: > > On 11/08/2016 12:46 PM, York Sun wrote: > >> On 11/07/2016 07:52 PM, Yuan Yao wrote: > >>> From: Yuan Yao <yao.yuan@nxp.com> > >>> > >>> Signed-off-by: Yuan Yao <yao.yuan@nxp.com> > >>> --- > >>> Changed in v2: > >>> Move the readme for QSPI deploy out of only for ls2080aqds. > >>> --- > >>> .../arm/cpu/armv8/fsl-layerscape/doc/README.deploy | 44 > >>> ++++++++++++++++++++++ > >>> 1 file changed, 44 insertions(+) > >>> create mode 100644 > >>> arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy > >>> > >>> diff --git a/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy > >>> b/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy > >>> new file mode 100644 > >>> index 0000000..25813b3 > >>> --- /dev/null > >>> +++ b/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy > >>> @@ -0,0 +1,44 @@ > >>> +Boot source support Overview > >>> +------------------- > >>> + 1. LS1043A > >>> + LS1043AQDS:QSPI, SD, NOR, NAND > >>> + LS1043ARDB:SD, NOR, NAND > >>> + 2. LS2080A > >>> + LS2080AQDS:QSPI, SD, NOR, NAND > >>> + LS2080ARDB:NOR, NAND > >>> + 3. LS1012A > >>> + LS1012AQDS:QSPI > >>> + LS1012ARDB:QSPI > >>> + 4. LS1046A > >>> + LS1046AQDS:QSPI, SD, NOR, NAND > >>> + LS1046ARDB:QSPI, SD > >>> + > >> > >> If you plan to add all SD/NAND/QSPI into this document, it is OK to > >> call it README.deploy. Otherwise it may be better to name as README.qspi. > >> > > I'm not be familiar with SD/NAND boot. So should I rename as README.qspi? > > Or just keep it but waiting for some others to add SD/NAND boot in another > patch? > > > > We already have NAND boot explained in other document. Stick with the > procedure you are trying to explain. Keep it simple and we can expand it when > necessary. > York Get it. I will send v3 soon. Thanks. Yao.
diff --git a/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy b/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy new file mode 100644 index 0000000..25813b3 --- /dev/null +++ b/arch/arm/cpu/armv8/fsl-layerscape/doc/README.deploy @@ -0,0 +1,44 @@ +Boot source support Overview +------------------- + 1. LS1043A + LS1043AQDS:QSPI, SD, NOR, NAND + LS1043ARDB:SD, NOR, NAND + 2. LS2080A + LS2080AQDS:QSPI, SD, NOR, NAND + LS2080ARDB:NOR, NAND + 3. LS1012A + LS1012AQDS:QSPI + LS1012ARDB:QSPI + 4. LS1046A + LS1046AQDS:QSPI, SD, NOR, NAND + LS1046ARDB:QSPI, SD + +Booting from QSPI +------------------- +Booting from QSPI requires two images, RCW and u-boot-dtb.bin. +The difference between QSPI boot RCW image and NOR boot image is the PBI +command sequence for setting the boot location pointer. It's should point +to the address for u-boot in QSPI flash. + +RCW image should be written to the beginning of QSPI flash device. +Example of using u-boot command + +=> sf probe 0:0 +SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiB +=> sf erase 0 +<size of rcw image> +SF: 65536 bytes @ 0x0 Erased: OK +=> sf write <rcw image in memory> 0 <size of rcw image> +SF: 164 bytes @ 0x0 Written: OK + +To get the QSPI image, build u-boot with QSPI config, for example, +<board_name>_qspi_defconfig. The image needed is u-boot-dtb.bin. +The u-boot image should be written to 0x10000(but 0x1000 for LS1043A, LS2080A). + +=> sf probe 0:0 +SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiB +=> sf erase 10000 +<size of u-boot image> +SF: 589824 bytes @ 0x10000 Erased: OK +=> sf write <u-boot image in memory> 10000 <size of u-boot image> +SF: 580966 bytes @ 0x10000 Written: OK + +With these two images in QSPI flash device, the board can boot from QSPI.