releasenotes.txt

Marvell SheevaPlug U-Boot needed for Board Dev

02-Mar-2009

Release notes for MV88F6281A/MV88F6192A/MV88F6180A U-Boot, release: 3.4.16
============================================================================

Table of Contents
-----------------
1.    Contents of Release
2.    Supported boards/CPU's/
3.    How to build and burn U-Boot.
4.    Changes from Previous Releases
5.    Known Issues
6.    Disclaimer	



1. Contents of Release (n)
==========================

  Included in current release:
 
  -) U-Boot source code patch (for u-boot-1.1.4) version 3.4.16
 
  -) Support
        - Little/Big endian
        - Uart 0
        - Auto detect of PEX 0 
        - Reset.
        - RTC.
        - Gigabit Ethernet ports. 
		Port 0 and 1 in RGMII mode
	- XOR.
        - SPI Flash
	- NAND Flash
	- JFFS over SPI or NAND
	- SATA IDE and SATA port multiplier
	- EXT2 files system
	- Exceptions

	

2.    Supported boards/CPU's
============================

   This U-Boot version supports the following boards:
 
   Boards
   ======
	DB-88F6281A-BP
	DB-88F6192A-BP
	RD-88F6281A
	RD-88F6192A
	DB-88F6180A-BP
        DB-88F6281A-SHEEVA_PLUG
	
3. How to build and Burn U-Boot
===============================

   Building U-Boot
   ===============

   -) Download U-Boot release 1.1.4 from ftp://ftp.denx.de/pub/u-boot/.

   -) Update the U-Boot 1.1.4 release by copying the patch of this release.
   
   -) Update the U-Boot Makefile to point to the cross compiler in your host
      machine, arm-none-linux-gnueabi cross compiler.

   -) Build the U-Boot binaries as follows:

 
   -) For DB-88F6281-BP LE
   > make mrproper
   -) NAND
   > make db88f6281abp_config NBOOT=1 LE=1
   -) SPI
   > make db88f6281abp_config SPIBOOT=1 LE=1
   -) SPI with NAND support
   > make db88f6281abp_config SPIBOOT=1 LE=1 NAND=1
   > make -s

   -) For DB-88F6192A-BP LE
   > make mrproper
   -) NAND
   > make db88f6192abp_config NBOOT=1 LE=1
   -) SPI
   > make db88f6192abp_config SPIBOOT=1 LE=1
   -) SPI with NAND support
   > make db88f6192abp_config SPIBOOT=1 LE=1 NAND=1
   > make -s

   -) For RD-88F6281A LE
   > make mrproper
   -) NAND
   > make rd88f6281a_config NBOOT=1 LE=1
   -) SPI
   > make rd88f6281a_config SPIBOOT=1 LE=1
   -) SPI with NAND support
   > make rd88f6281a_config SPIBOOT=1 LE=1 NAND=1
   > make -s

   -) For RD-88F6192A LE
   > make mrproper
   -) SPI
   > make rd88f6192a_config SPIBOOT=1 LE=1
   > make -s

   -) For DB-88F6180-BP LE
   > make mrproper
   -) NAND
   > make db88f6180abp_config NBOOT=1 LE=1
   -) SPI
   > make db88f6180abp_config SPIBOOT=1 LE=1
   -) SPI with NAND support
   > make db88f6180abp_config SPIBOOT=1 LE=1 NAND=1
   > make -s


* For BE use BE=1

   -) The BootRom header files are located in the source root directory:
	-> dramregs_400rd_A.txt
	-> dramregs_400db_A.txt
	-> dramregs_200rd_A.txt
	-> dramregs_200db_A.txt
	-> dramregs_200db619x_A.txt

      The files have predefined register settings for the different SDRAM configurations and required errata. 
      The matching header file is appended to the U-boot image during the make process according to the device
      and board type, using the doimage utility which is located in the /tools directory. The output file to be
      burnt on boot ROM depends on the make parameters:
	-> NBOOT=1 : u-boot-<board name>_<SDRAM clock frequency>_nand.bin
	-> SPIBOOT=1 : u-boot-<board name>_<SDRAM clock frequency>_flash.bin
	
      The file u-boot-<board name>_<SDRAM clock frequency>_uart.bin is used for debug purposes for booting the 
      U-boot image through the UART port. 

   Burning U-Boot
   ==============

   If burning the new U-Boot image to an board the already runs a previous U-Boot image the following sequence
   can be used to load the image using tftp to the board and burn it:
	1. Start a tftp server on the host PC, whose directory is set to point to the directory contaning the 
	   new U-Boot bin image.
	2. Connect an Ethernet cable to the RJ-45 connector of the board.
	3. Configure the U-Boot environment parameters using the following commands:
		> setenv serverip xx.xx.xx.xx	(xx.xx.xx.xx should be the IP address of the PC runing the tftp server)
		> setenv ipaddr yy.yy.yy.yy     (yy.yy.yy.yy should be some IP address with the same subnet as the server)
	4. run the bubt command to load and burn the U-Boot image:
		> bubt u-boot-<board name>_<SDRAM clock frequency>_<boot device>.bin
	5. Once the image is loaded the user is asked whether the environment parameters should be overwritten or not
	   , and answering y or n to thios question will start the burn process.
	6. Once the burn is complete the board can be restarted, and the new U-Boot image will be run.
	
	*** When upgrading U-boot from an older revision than 3.4.10, then after step 6 is done and U-boot 3.4.10 is up and running
	    need to repeat steps 3-6 again on the same image of U-boot 3.4.10 (and up) and re-burn it. The reason is that from U-boot
            3.4.10 and on NAND ECC uses 4-bit for the U-boot image and environment in the NAND, and when using an older U-boot to burn
            it, it is written using 1-bit ECC, which is not correct. Using the newly burnt U-boot 3.4.10 (and on) to burn the image 
            again will use 4-bit ECC.

   In case the original U-Boot image was damaged, or when whishing to burn a different boot device than the current one, 
   the U-Boot command cannot be used, and a debugger is required to load the U-Boot ELF image into the SDRAM, using the 
   following procedure:
	1. Connect a debugger (Marvell uses a Lauterbach debugger, so the supplied scripts are written for this type of debugger)
	   to the debugger port of the board.
	2. From the file menue of the debugger SW choose the "run batch file" option and load the cmm file suiting the system:
		- kw_dimm400.cmm for 88F6281 running at frequencies above 200MHz.
		- kw_dimm200.cmm for all other options.
	3. From the file menue of the debugger SW choose the "load" option and load the U-Boot ELF file (The one without any extension).
	4. Once the loading is done change the following using the debugger SW:
		- CPU PC to 0x670000.
		- Configure the required MPPs to either NAND or SPI according to the required boot method using the debugger SW command line:
			+ For NAND boot:
				- D.S SD:0xD0010000 %LE %LONG 0x01111111
				- D.S SD:0xD0010008 %LE %LONG 0x551111
			+ For SPI boot:
				- For DB-6180 and RD-6192:
					+ D.S SD:0xD0010000 %LE %LONG 0x01112222