LS1046ARDB - How to update U-Boot binary in QSPI NOR flash

[#1]

This how-to topic is applicable for only LSDK 18.09 and older releases.

Follow these steps to update the U-Boot binary in QSPI NOR flash. 

Prerequisites 

• Ubuntu 18.04 64-bit should be installed on the Linux host machine for building LSDK 18.06 or LSDK 18.09 U-Boot binary.

cpld reset boots the board from QSPI NOR flash0 and cpld reset altbank boots the board from QSPI NOR flash1.

sf probe 0:1 means that the alternate bank will be written to. So, if the board boots from QSPI NOR flash0 and sf probe 0:1 is entered at the U-Boot prompt, the commands that follow will program QSPI NOR flash1.

Compiling U-Boot binary

Clone the u-boot repository.

1. $ git clone https://source.codeaurora.org/external/qoriq/qoriq-components/u-boot.git
2. $ cd u-boot
3. $ git checkout -b <new branch name> LSDK-<LSDK version>. For example, $ git checkout -b LSDK-18.09 LSDK-18.09 
4. $ export ARCH=arm64
5. $ export CROSS_COMPILE=aarch64-linux-gnu-
6. $ make distclean
7. $ make ls1046ardb_qspi_defconfig
8. If required, make changes to the U-Boot files.
9. $ make

If the make command shows the error "*** Your GCC is older than 6.0 and is not supported", ensure that you are using Ubuntu 18.04 64-bit version for building LSDK 18.06 or LSDK 18.09 U-Boot binary. 

The compiled U-Boot image, u-boot.bin, is available in the directory u-boot/.

Flashing U-Boot binary to QSPI NOR flash

U-Boot image can be loaded to LS1046ARDB from a TFTP server or from a mass storage device (SD, USB, or SATA).

Option 1: Load image from the TFTP server

1. Boot LS1046ARDB from QSPI. Ensure that the switches are set to boot the board from QSPI. For booting from QSPI, SW5[1:8] = 00100010
2. Boot from QSPI NOR flash0: => cpld reset

   In boot log, you’ll see:

   Board: LS1046ARDB, boot from QSPI vBank 0

Set up Ethernet connection

When the board boots up, U-Boot prints a list of enabled Ethernet interfaces.

FM1@DTSEC3 [PRIME], FM1@DTSEC4, FM1@DTSEC5, FM1@DTSEC6, FM1@TGEC1, FM1@TGEC2

1. Set server IP to the IP of the host machine on which you have configured the TFTP server. 

   => setenv serverip <ipaddress1>

2. Set ethact and ethprime as the Ethernet interface connected to the TFTP server.

   See LS1046ARDB Ethernet port mapping for the mapping of Ethernet port names appearing on the chassis front panel with the port names in U-Boot and Linux.

   => setenv ethprime <name of interface connected to TFTP server>

   For example:

   => setenv ethprime FM1@DTSEC4

   => setenv ethact <name of interface connected to TFTP server>

   For example:

   => setenv ethact FM1@DTSEC4

3. Set IP address of the board. You can set a static IP address or, if the board can connect to a dhcp server, you can use the dhcp command.

   Static IP address assignment:
   => setenv ipaddr <ipaddress2>
   => setenv netmask <subnet mask>

   Dynamic IP address assignment:
   => dhcp

4. Save the settings.

   => saveenv

5. Check the connection between the board and the TFTP server.

=> ping $serverip

Using FM1@DTSEC4 device

host 192.168.1.1 is alive

Load U-Boot image from the TFTP server

1. Program QSPI NOR flash1: => sf probe 0:1

2. Flash U-Boot image:
   
   1. => tftp 0xa0000000 u-boot.bin
   2. => print filesize
      

      filesize=ae84a

3. Program U-Boot image to QSPI NOR flash: => sf erase 0x100000 +$filesize && sf write 0xa0000000 0x100000 $filesize

   Address 0x100000 is the location of U-Boot in QSPI NOR flash.  Refer Flash layout for boot flow with PPA – LSDK 18.09 and older releases for the complete flash memory layout.

4. Boot from QSPI NOR flash1: => cpld reset altbank

   In boot log, you’ll see:

   Board: LS1046ARDB, boot from QSPI vBank 4

   Ensure that SD card, USB flash drive, or SCSI hard disk installed with LSDK Ubuntu distribution is plugged into the board to boot the board to Ubuntu. If U-Boot does not find LSDK on a mass storage device, it will boot TinyDistro from lsdk_linux_arm64_ tiny.itb stored in QSPI NOR flash.

Option 2: Load image from partition on mass storage device (SD, USB, or SATA)

1. Boot LS1046ARDB from QSPI NOR flash. Ensure that the switches are set to boot the board from QSPI. For booting from QSPI, SW5[1:8] = 00100010
2. Boot from QSPI NOR flash0: => cpld reset

   In boot log, you’ll see:

   Board: LS1046ARDB, boot from QSPI vBank 0

3. Select mass storage device to use.

   => mmc rescan

   => mmc info

   Or

   => usb start
   => usb info

   Or

   => scsi scan

   => scsi info

4. Optional – List files on storage device

   => ls mmc <device:partition>

   For example:

   => ls mmc 0:3
   System Volume Information/
   714826 u-boot.bin

   1 file(s), 1 dir(s)

   Or

   => ls usb <device:partition>

   For example:

   => ls usb 0:1

   Or

   => ls scsi <device:partition>

   For example:

   => ls scsi 0:2

   If the ls command fails to run, check that U-Boot in QSPI NOR flash0 supports the command by typing ls at the U-Boot prompt:
   => ls
   ls - Lists files in a directory (default)
   Usage:
   ls <interface> [<dev[:part]> [directory]]
    
   - Lists files in directory [directory] of partition [part] on device type [interface] and instance [dev].
   If U-Boot does not support this command, then update the composite firmware image in QSPI NOR flash0.
   For steps to update composite firmware image in QSPI NOR flash, see LS1046ARDB - How to update composite firmware image in QSPI NOR flash.

5. Program QSPI NOR flash1: => sf probe 0:1
6. Load U-Boot image from the storage device.

   => load mmc <device:partition> a0000000 <image name>

   => print filesize

   For example:

   => load mmc 0:3 a0000000 u-boot.bin
   714826 bytes read in 52 ms (13.1 MiB/s)
   => print filesize
   filesize=ae84a

   Or

   => load usb <device:partition> a0000000 <image name>

   => print filesize

   Or

   => load scsi <device:partition> a0000000 <image name>

   => print filesize

7. Program U-Boot image to QSPI NOR flash: => sf erase 0x100000 +$filesize && sf write 0xa0000000 0x100000 $filesize
   

   Address 0x100000 is the location of U-Boot in QSPI NOR flash.  Refer Flash layout for boot flow with PPA – LSDK 18.09 and older releases for the complete flash memory layout.

8. Boot from QSPI NOR flash1: => cpld reset altbank

   In boot log, you’ll see:

   Board: LS1046ARDB, boot from QSPI vBank 4

   Ensure that SD card, USB flash drive, or SCSI hard disk installed with LSDK Ubuntu distribution is plugged into the board to boot the board to Ubuntu. If U-Boot does not find LSDK on a mass storage device, it will boot TinyDistro from lsdk_linux_arm64_ tiny.itb stored in QSPI NOR flash.

[js_park]

Hi,

I faced a serious problem about QSPI booting problem after update.

According to the guide, I did make QSPI flash#1 updated. 

And I tried to update QSPI flash#0 to keep the same version as the flash #1. I erased & wrote it. 

After that, my board can't boot from flash#0. It can only boot from flash#1 and SD card.

I copied the contents of flash#1 to memory and I wrote to flash#0.

I checked the content of flash#0 is the same as flash#1.

When I boot from flash#1 and then command "cpld reset" then it can boot from flash#0. That means the content of flash#0 is right to boot I guess.

Would you help me with that?

Thanks

[swati_gupta]

Hi, 

From the problem description, it seems that after booting from QSPI NOR flash1, if you enter the command “cpld reset” the board successfully boots from QSPI NOR flash0.  However, if you power on the board or reset the board, the board will not boot from QSPI NOR flash0. 

One item to check is that the switch settings are correct when trying to boot from QSPI NOR flash0.  The QorIQ LS1046A Reference Design Board Getting Started Guide has a table that lists the switch settings to use for the different boot sources (QSPI NOR flash0, QSPI NOR flash1, and SD card).  This table can be found in section 12 titled “LS1046ARDB boot sources.” This section also has a table that lists the CPLD commands that can be used to override the switch settings. 

Hope this resolves the issue.

Thanks.

[penman]

JS Park,

I have the same problem, I erased and wrote QSPI vBank0 and now LS1046A-RDB won't boot from vBank0. 

vBank4 and SD start with no problem using the switch positions detailed in the QorIQ LS1046A Reference Design Board Getting Started Guide.

vBank0 and vBank4 are identical copies, did you find a solution to boot vBank0?

[js_park]

Hi,

Penman

I don't have found any solutions by using switches, commands & codes.

I made the NOR flash normal after erasing it by Code Worrier.

And then, the flash is working properly. I just guess that the first sector of NOR flash was locked and Code Worrier was able to resolve the situation.

I hope it would be helpful to you.

[swati_gupta]

Hi, I flashed QSPI NOR flash 1 with a newly built U-Boot binary by following the documented steps and then I flahed QSPI NOR flash 0 with the same U-Boot binary. However, I am able to boot the board from both flash 0 and flash 1. The issue is not reproducing for me.

Thanks.

[penman]

Hi Swati, thank you for looking into this however my experience was similar to JS Park; despite following the steps above directed to NOR flash 0, I also noticed that the first 0x8000 bytes would silently fail to erase/write. It may not be a coincidence that this is also the first 8 4kB 'hybrid' sectors of S25F512S though I don't have drivers to lock/unlock the QSPI configuration register default settings. I was lucky to have access to a CodeWarrior and TAP/cable and recover this.