1*4882a593SmuzhiyunKeymile kmeter1 Board 2*4882a593Smuzhiyun----------------------------------------- 3*4882a593Smuzhiyun1. Alternative Boot EEPROM 4*4882a593Smuzhiyun 5*4882a593Smuzhiyun Upon the kmeter1 startup the I2C_1 controller is used to fetch the boot 6*4882a593Smuzhiyun configuration from a serial EEPROM. During the development and debugging 7*4882a593Smuzhiyun phase it might be helpful to apply an alternative boot configuration in 8*4882a593Smuzhiyun a simple way. Therefore it is an alternative boot eeprom on the PIGGY, 9*4882a593Smuzhiyun which can be activated by setting the "ST" jumper on the PIGGY board. 10*4882a593Smuzhiyun 11*4882a593Smuzhiyun2. Memory Map 12*4882a593Smuzhiyun 13*4882a593Smuzhiyun BaseAddr PortSz Size Device 14*4882a593Smuzhiyun ----------- ------ ----- ------ 15*4882a593Smuzhiyun 0x0000_0000 64 bit 256MB DDR 16*4882a593Smuzhiyun 0x8000_0000 8 bit 256KB GPIO/PIGGY on CS1 17*4882a593Smuzhiyun 0xa000_0000 8 bit 256MB PAXE on CS3 18*4882a593Smuzhiyun 0xe000_0000 2MB Int Mem Reg Space 19*4882a593Smuzhiyun 0xf000_0000 16 bit 256MB FLASH on CS0 20*4882a593Smuzhiyun 21*4882a593Smuzhiyun 22*4882a593Smuzhiyun DDR-SDRAM: 23*4882a593Smuzhiyun The current realization is made with four 16-bits memory devices. 24*4882a593Smuzhiyun Mounting options have been foreseen for device architectures from 25*4882a593Smuzhiyun 4Mx16 to 512Mx16. The kmeter1 is equipped with four 32Mx16 devices 26*4882a593Smuzhiyun thus resulting in a total capacity of 256MBytes. 27*4882a593Smuzhiyun 28*4882a593Smuzhiyun3. Compilation 29*4882a593Smuzhiyun 30*4882a593Smuzhiyun Assuming you're using BASH shell: 31*4882a593Smuzhiyun 32*4882a593Smuzhiyun export CROSS_COMPILE=your-cross-compile-prefix 33*4882a593Smuzhiyun cd u-boot 34*4882a593Smuzhiyun make distclean 35*4882a593Smuzhiyun make kmeter1_config 36*4882a593Smuzhiyun make 37*4882a593Smuzhiyun 38*4882a593Smuzhiyun4. Downloading and Flashing Images 39*4882a593Smuzhiyun 40*4882a593Smuzhiyun4.0 Download over serial line using Kermit: 41*4882a593Smuzhiyun 42*4882a593Smuzhiyun loadb 43*4882a593Smuzhiyun [Drop to kermit: 44*4882a593Smuzhiyun ^\c 45*4882a593Smuzhiyun send <u-boot-bin-image> 46*4882a593Smuzhiyun c 47*4882a593Smuzhiyun ] 48*4882a593Smuzhiyun 49*4882a593Smuzhiyun 50*4882a593Smuzhiyun Or via tftp: 51*4882a593Smuzhiyun 52*4882a593Smuzhiyun tftp 10000 u-boot.bin 53*4882a593Smuzhiyun => run load 54*4882a593Smuzhiyun Using UEC0 device 55*4882a593Smuzhiyun TFTP from server 192.168.1.1; our IP address is 192.168.205.4 56*4882a593Smuzhiyun Filename '/tftpboot/kmeter1/u-boot.bin'. 57*4882a593Smuzhiyun Load address: 0x200000 58*4882a593Smuzhiyun Loading: ############## 59*4882a593Smuzhiyun done 60*4882a593Smuzhiyun Bytes transferred = 204204 (31dac hex) 61*4882a593Smuzhiyun => 62*4882a593Smuzhiyun 63*4882a593Smuzhiyun4.1 Reflash U-Boot Image using U-Boot 64*4882a593Smuzhiyun 65*4882a593Smuzhiyun => run update 66*4882a593Smuzhiyun ..... done 67*4882a593Smuzhiyun Un-Protected 5 sectors 68*4882a593Smuzhiyun 69*4882a593Smuzhiyun ..... done 70*4882a593Smuzhiyun Erased 5 sectors 71*4882a593Smuzhiyun Copy to Flash... done 72*4882a593Smuzhiyun ..... done 73*4882a593Smuzhiyun Protected 5 sectors 74*4882a593Smuzhiyun Total of 204204 bytes were the same 75*4882a593Smuzhiyun Saving Environment to Flash... 76*4882a593Smuzhiyun . done 77*4882a593Smuzhiyun Un-Protected 1 sectors 78*4882a593Smuzhiyun . done 79*4882a593Smuzhiyun Un-Protected 1 sectors 80*4882a593Smuzhiyun Erasing Flash... 81*4882a593Smuzhiyun . done 82*4882a593Smuzhiyun Erased 1 sectors 83*4882a593Smuzhiyun Writing to Flash... done 84*4882a593Smuzhiyun . done 85*4882a593Smuzhiyun Protected 1 sectors 86*4882a593Smuzhiyun . done 87*4882a593Smuzhiyun Protected 1 sectors 88*4882a593Smuzhiyun => 89*4882a593Smuzhiyun 90*4882a593Smuzhiyun5. Notes 91*4882a593Smuzhiyun 1) The console baudrate for kmeter1 is 115200bps. 92