Booting from OSPI / QSPI¶

• Table of contents
• Booting from OSPI / QSPI
  • OSPI Boot
  • QSPI Boot
    • Steps

NOTE: Booting from OSPI is a different boot config than QSPI

OSPI Boot¶

To boot the Dev Kit from OSPI using a CL supplied image, set the boot pins as follows:

B9	B8	B7	B6	B5	B4	B3
Reserved (0)	lclk (1)	Csel (0)	0	0	0	1

QSPI Boot¶

To boot the Dev Kit from QSPI using a CL supplied image, set the boot pins as follows:

B9	B8	B7	B6	B5	B4	B3
Reserved (0)	lclk (1)	Csel (0)	0	0	1	0

Steps¶

• boot to linux (i.e. from SD card).
• cd to boot partition (the directory containing tibot3.bin, etc.../run/media/mmcblk1p1 in my case.)
• copy the boot files to their respective locations in SPI NOR
  

  root@mitysom-am62x:~# cp tiboot3.bin /dev/mtd0
  root@mitysom-am62x:~# cp tispl.bin /dev/mtd1
  root@mitysom-am62x:~# cp u-boot.img /dev/mtd2
  root@mitysom-am62x:~# dd if=/dev/mmcblk0boot0 bs=512 skip=13312 count=256 of=uboot.env
  root@mitysom-am62x:~# cp uboot.env /dev/mtd3
  
        0x0 +----------------------------+
            |     ospi.tiboot3(512k)     |
            |                            |
    0x80000 +----------------------------+
            |     ospi.tispl(2m)         |
            |                            |
   0x280000 +----------------------------+
            |     ospi.u-boot(4m)        |
            |                            |
   0x680000 +----------------------------+
            |     ospi.env(128k)         |
            |                            |
   0x6c0000 +----------------------------+
            |   ospi.env.backup(128k)    |
            |                            |
   0x740000 +----------------------------+
            |      padding (768k)        |
   0x800000 +----------------------------+
            |     ospi.rootfs(ubifs)     |
            |                            |
  0xffc0000 +----------------------------+
            |   ospi.phypattern (256k)   |
            |                            |
            +----------------------------+