Mirrors/u-boot
2
0
Fork 0
mirror of https://github.com/AsahiLinux/u-boot synced 2024-11-25 22:20:45 +00:00
Code Issues Projects Releases Packages Wiki Activity
u-boot/board/keymile/km83xx
History
Simon Glass e895a4b06f fdt: Allow ft_board_setup() to report failure 
This function can fail if the device tree runs out of space. Rather than
silently booting with an incomplete device tree, allow the failure to be
detected.

Unfortunately this involves changing a lot of places in the code. I have
not changed behvaiour to return an error where one is not currently
returned, to avoid unexpected breakage.

Eventually it would be nice to allow boards to register functions to be
called to update the device tree. This would avoid all the many functions
to do this. However it's not clear yet if this should be done using driver
model or with a linker list. This work is left for later.

Signed-off-by: Simon Glass <sjg@chromium.org>
Acked-by: Anatolij Gustschin <agust@denx.de>
2014-11-21 04:43:15 +01:00
..
Kconfig kconfig: remove redundant "string" type in arch and board Kconfigs 2014-09-13 16:43:55 -04:00
km83xx.c fdt: Allow ft_board_setup() to report failure 2014-11-21 04:43:15 +01:00
km83xx_i2c.c Add GPL-2.0+ SPDX-License-Identifier to source files 2013-07-24 09:44:38 -04:00
MAINTAINERS Add board MAINTAINERS files 2014-07-30 08:48:06 -04:00
Makefile Makefile: make directories by Makefile.build 2013-11-17 14:11:31 -05:00
README.kmeter1 doc: cleanup - move board READMEs into respective board directories 2012-07-29 15:42:02 +02:00

README.kmeter1 

Keymile kmeter1 Board
-----------------------------------------
1.	Alternative Boot EEPROM

    Upon the kmeter1 startup the I2C_1 controller is used to fetch the boot
    configuration from a serial EEPROM. During the development and debugging
    phase it might be helpful to apply an alternative boot configuration in
    a simple way. Therefore it is an alternative boot eeprom on the PIGGY,
    which can be activated by setting the "ST" jumper on the PIGGY board.

2.	Memory Map

    BaseAddr    PortSz  Size  Device
    ----------- ------  -----  ------
    0x0000_0000 64 bit  256MB  DDR
    0x8000_0000  8 bit  256KB  GPIO/PIGGY on CS1
    0xa000_0000  8 bit  256MB  PAXE on CS3
    0xe000_0000           2MB  Int Mem Reg Space
    0xf000_0000 16 bit  256MB  FLASH on CS0


    DDR-SDRAM:
    The current realization is made with four 16-bits memory devices.
    Mounting options have been foreseen for device architectures from
    4Mx16 to 512Mx16. The kmeter1 is equipped with four 32Mx16 devices
    thus resulting in a total capacity of 256MBytes.

3. Compilation

	Assuming you're using BASH shell:

		export CROSS_COMPILE=your-cross-compile-prefix
		cd u-boot
		make distclean
		make kmeter1_config
		make

4. Downloading and Flashing Images

4.0 Download over serial line using Kermit:

	loadb
	[Drop to kermit:
	    ^\c
	    send <u-boot-bin-image>
	    c
	]


    Or via tftp:

	tftp 10000 u-boot.bin
    => run load
    Using UEC0 device
    TFTP from server 192.168.1.1; our IP address is 192.168.205.4
    Filename '/tftpboot/kmeter1/u-boot.bin'.
    Load address: 0x200000
    Loading: ##############
    done
    Bytes transferred = 204204 (31dac hex)
    =>

4.1 Reflash U-boot Image using U-boot

    => run update
    ..... done
    Un-Protected 5 sectors

    ..... done
    Erased 5 sectors
    Copy to Flash... done
    ..... done
    Protected 5 sectors
    Total of 204204 bytes were the same
    Saving Environment to Flash...
    . done
    Un-Protected 1 sectors
    . done
    Un-Protected 1 sectors
    Erasing Flash...
    . done
    Erased 1 sectors
    Writing to Flash... done
    . done
    Protected 1 sectors
    . done
    Protected 1 sectors
    =>

5. Notes
	1) The console baudrate for kmeter1 is 115200bps.