projects / people / ms / u-boot.git / blame
| Commit | Line | Data |
|---|---|---|
| 1f4bb37d WD |
1 | LYNX KDI SUPPORT |
| 2 | ||
| 3 | Last Update: July 20, 2003 | |
| 4 | ======================================================================= | |
| 5 | ||
| 6 | This file describes support for LynuxWorks KDI within U-Boot. Support | |
| 7 | is enabled by defining CONFIG_LYNXKDI. | |
| 8 | ||
| 9 | ||
| 10 | LYNXOS AND BLUECAT SUPPORTED | |
| 11 | ============================ | |
| 12 | Both LynxOS and BlueCat linux KDIs are supported. The implementation | |
| 13 | automatically detects which is being booted. When you use mkimage | |
| 14 | you should specify "lynxos" for both (see target-specific notes). | |
| 15 | ||
| 16 | ||
| 17 | SUPPORTED ARCHITECTURE/TARGETS | |
| 18 | ============================== | |
| 19 | The following targets have been tested: | |
| 20 | ||
| 21 | -PowerPC MPC8260ADS | |
| 22 | ||
| 23 | ||
| 24 | FILES TO LOOK AT | |
| 25 | ================ | |
| 26 | include/lynxkdi.h -defines a simple struct passed to a kdi. | |
| 27 | common/lynxkdi.c -implements the call to the kdi. | |
| 28 | common/cmd_bootm.c -top-level command implementation ("bootm"). | |
| 29 | ||
| 30 | ||
| 31 | ==================================================================== | |
| 32 | TARGET SPECIFIC NOTES | |
| 33 | ==================================================================== | |
| 34 | ||
| 35 | MPC8260ADS | |
| 36 | =========== | |
| 37 | The default LynxOS and BlueCat implementations require some | |
| 38 | modifications to the config file. | |
| 39 | ||
| 40 | Edit include/configs/MPC8260ADS.h to use the following: | |
| 41 | ||
| 6d0f6bcf JCPV |
42 | #define CONFIG_SYS_IMMR 0xFA200000 |
| 43 | #define CONFIG_SYS_BCSR 0xFA100000 | |
| 44 | #define CONFIG_SYS_BR1_PRELIM 0xFA101801 | |
| 1f4bb37d WD |
45 | |
| 46 | When creating a LynxOS or BlueCat u-boot image using mkimage, | |
| 47 | you must specify the following: | |
| 48 | ||
| 49 | Both: -A ppc -O lynxos -T kernel -C none | |
| 50 | LynxOS: -a 0x00004000 -e 0x00004020 | |
| 51 | BlueCat: -a 0x00500000 -e 0x00507000 | |
| 52 | ||
| 53 | To pass the MAC address to BlueCat you should define the | |
| 54 | "fcc2_ether_addr" parameter in the "bootargs" environment | |
| 55 | variable. E.g.: | |
| 56 | ||
| 57 | ==> setenv bootargs fcc2_ether_addr=00:11:22:33:44:55:66 |