2 -----------------------------------------
3 1. Alternative Boot EEPROM
5 Upon the kmeter1 startup the I2C_1 controller is used to fetch the boot
6 configuration from a serial EEPROM. During the development and debugging
7 phase it might be helpful to apply an alternative boot configuration in
8 a simple way. Therefore it is an alternative boot eeprom on the PIGGY,
9 which can be activated by setting the "ST" jumper on the PIGGY board.
13 BaseAddr PortSz Size Device
14 ----------- ------ ----- ------
15 0x0000_0000 64 bit 256MB DDR
16 0x8000_0000 8 bit 256KB GPIO/PIGGY on CS1
17 0xa000_0000 8 bit 256MB PAXE on CS3
18 0xe000_0000 2MB Int Mem Reg Space
19 0xf000_0000 16 bit 256MB FLASH on CS0
23 The current realization is made with four 16-bits memory devices.
24 Mounting options have been foreseen for device architectures from
25 4Mx16 to 512Mx16. The kmeter1 is equipped with four 32Mx16 devices
26 thus resulting in a total capacity of 256MBytes.
30 Assuming you're using BASH shell:
32 export CROSS_COMPILE=your-cross-compile-prefix
38 4. Downloading and Flashing Images
40 4.0 Download over serial line using Kermit:
45 send <u-boot-bin-image>
55 TFTP from server 192.168.1.1; our IP address is 192.168.205.4
56 Filename '/tftpboot/kmeter1/u-boot.bin'.
57 Load address: 0x200000
58 Loading: ##############
60 Bytes transferred = 204204 (31dac hex)
63 4.1 Reflash U-boot Image using U-boot
67 Un-Protected 5 sectors
74 Total of 204204 bytes were the same
75 Saving Environment to Flash...
77 Un-Protected 1 sectors
79 Un-Protected 1 sectors
83 Writing to Flash... done
91 1) The console baudrate for kmeter1 is 115200bps.