projects / J-u-boot.git / blame
| Commit | Line | Data |
|---|---|---|
| de044361 HS |
1 | Keymile kmeter1 Board |
| 2 | ----------------------------------------- | |
| 3 | 1. Alternative Boot EEPROM | |
| 4 | ||
| 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. | |
| 10 | ||
| 11 | 2. Memory Map | |
| 12 | ||
| 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 | |
| 20 | ||
| 21 | ||
| 22 | DDR-SDRAM: | |
| 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. | |
| 27 | ||
| 28 | 3. Compilation | |
| 29 | ||
| 30 | Assuming you're using BASH shell: | |
| 31 | ||
| 32 | export CROSS_COMPILE=your-cross-compile-prefix | |
| 33 | cd u-boot | |
| 34 | make distclean | |
| 35 | make kmeter1_config | |
| 36 | make | |
| 37 | ||
| 38 | 4. Downloading and Flashing Images | |
| 39 | ||
| 40 | 4.0 Download over serial line using Kermit: | |
| 41 | ||
| 42 | loadb | |
| 43 | [Drop to kermit: | |
| 44 | ^\c | |
| 45 | send <u-boot-bin-image> | |
| 46 | c | |
| 47 | ] | |
| 48 | ||
| 49 | ||
| 50 | Or via tftp: | |
| 51 | ||
| 52 | tftp 10000 u-boot.bin | |
| 53 | => run load | |
| 54 | Using FSL UEC0 device | |
| 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: ############## | |
| 59 | done | |
| 60 | Bytes transferred = 204204 (31dac hex) | |
| 61 | => | |
| 62 | ||
| 63 | 4.1 Reflash U-boot Image using U-boot | |
| 64 | ||
| 65 | => run update | |
| 66 | ..... done | |
| 67 | Un-Protected 5 sectors | |
| 68 | ||
| 69 | ..... done | |
| 70 | Erased 5 sectors | |
| 71 | Copy to Flash... done | |
| 72 | ..... done | |
| 73 | Protected 5 sectors | |
| 74 | Total of 204204 bytes were the same | |
| 75 | Saving Environment to Flash... | |
| 76 | . done | |
| 77 | Un-Protected 1 sectors | |
| 78 | . done | |
| 79 | Un-Protected 1 sectors | |
| 80 | Erasing Flash... | |
| 81 | . done | |
| 82 | Erased 1 sectors | |
| 83 | Writing to Flash... done | |
| 84 | . done | |
| 85 | Protected 1 sectors | |
| 86 | . done | |
| 87 | Protected 1 sectors | |
| 88 | => | |
| 89 | ||
| 90 | 5. Notes | |
| 91 | 1) The console baudrate for kmeter1 is 115200bps. |