[meta-xilinx] u-boot SPL from QSPI flash

[Alan DuBoff]

On Mon, February 24, 2014 12:09 am, Mike Looijmans wrote:
> Has anyone tried booting SPL from QSPI flash yet, or should this "just work"?

Mike,


Obviously I haven't done it with the zedboard, but I have used the SPI on the
Enclustra SoC I was using last year.

Did you produce a u-boot.mcs ? The addresses might be different than they are
for the SD card.

The first thing I did was to write the u-boot.mcs with the Vivado tools.

Then I would go through the procedure below to write the u-boot.bin, kernel,
devicetree, ubifs, etc...and these were the addresses I was using. Note the
u-boot.bin address is different than you were using for booting the sd card,
I'm not sure if that could make a difference on zedboard or not.

I'm posting this for reference, as all devices are difference as you know. But
the Mars3 Starter was also a zynq 7020, so the same family.

Maybe you'll see something that will help you.

-- 
Cheers,
Alan


setenv ipaddr '175.6.1.220'
setenv serverip '175.6.1.225'

mw.b 0x200000 0xFF 0x450000
tftp 0x200000 u-boot.bin
sf probe
sf erase 0 0x450000
sf write 0x200000 0 0x450000

### Powercycle the system. ###

setenv ipaddr '175.6.1.220'
setenv serverip '175.6.1.225'

mw.b 0x00200000 0xFF ${kernel_size}
tftp 0x200000 ${kernel_image}
sf probe
sf erase 0x00600000 ${kernel_size}
sf write 0x00200000 0x600000 ${kernel_size}

mw.b 0x00200000 0xFF ${devicetree_size}
tftp 0x200000 ${devicetree_image}
sf probe
sf erase 0x900000 ${devicetree_size}
sf write 0x200000 0x900000 ${devicetree_size}

mw.b 0x00200000 0xFF ${ramdisk_size}
tftp 0x200000 ${ramdisk_image}
sf probe
sf erase 0x00A00000 ${ramdisk_size}
sf write 0x00200000 0x00A00000 ${ramdisk_size}

### Powercycle the system. ###

setenv ipaddr '175.6.1.220'
setenv serverip '175.6.1.225'

nand erase.part nand-linux
ubi part nand-linux
ubi create kernel

nand erase.part nand-device-tree
ubi part nand-device-tree
ubi create dtb

tftp 0x200000 ${kernel_image}
ubi part nand-linux
ubi write 0x200000 kernel ${filesize}

tftp 0x200000 ${devicetree_image}
ubi part nand-device-tree
ubi write 0x200000 dtb ${filesize}

### Powercycle the system. ###

run rescboot

You need to login as root. There is no password.

The device will do DHCP on the network. You need to check and make sure the
IPs do in fact match.

cd /tmp
tftp -g -r ice-dev.rootfs.ubi  175.6.1.225
ubiformat /dev/mtd2 -y -f /tmp/ice-dev.rootfs.ubi
ubiattach /dev/ubi_ctrl -m 2

tftp -g -r ice-dev.rootfs.ubifs  175.6.1.225
ubiupdatevol /dev/ubi0_0 /tmp/ice-dev.rootfs.ubifs
ubidetach /dev/ubi_ctrl -m 2

### Powercycle the system. ###

The following will boot the root filesystem of the image you have flashed.

run prodboot

Login as root. Again, there is no password and there is no security on this
device. You will be responsible for installing and configuring a fiirewall,
removing any unwanted files, tools, access, etc...this is up to you to solve
on your own. It is assumed there has been NO security installed or configured
other than Secure Shell and Secure Copy (ssh/scp).

The following will transfer a file from your /tftpboot/ directory from inside
the device:

# cd /home/root
# tftp -g -r program  175.6.1.225
# chmod 777 program